[Bug 367048] Re: upgrade from 8.10 to 9.04 resulted in unusable machine

2009-06-02 Thread PetriL
The 9.04 server which I installed fresh from CD become unbootable when I added the following modules to /etc/modules: padlock_sha padlock_aes via_rng These worked fine on 8.10, and I assume that they were the reason why the original update failed, too, as they were present on the upgraded image.

[Bug 367048] Re: upgrade from 8.10 to 9.04 resulted in unusable machine

2009-05-14 Thread PetriL
I can confirm that reinstalling from CD produced a working 9.04 setup on my VIA EPIA EN board as well. So only the update goes AWOL. I can live with that. Thanks for the Ubuntu team for another great package! PS: for antoiner: I have that message too and tells me that my system is at -273

[Bug 366961] Re: odt2txt starts automaticly, using 23% cpu doing nothing, after closing files

2009-05-09 Thread PetriL
Updated one laptop from 8.10 to 9.04 yesterday. A moment ago I noticed huge CPU usage on system monitor. odt2txt was traversing a big directory tree. Parent process number was 1. I am pretty sure I have not used any OO tools since last restart. -- odt2txt starts automaticly, using 23% cpu

[Bug 367048] Re: upgrade from 8.10 to 9.04 resulted in unusable machine

2009-05-09 Thread PetriL
I see the same kind of symptoms with the server version on VIA EPIA EN board. Worked flawlessly with 8.10, update went without errors, now at boot, the system stops at row: Loading manual drivers... It does not crash, just sits there forever. I have a TrendNet KVM switch that causes harmless

[Bug 132403] Re: Cpu frequency scaling is limited to stock speeds

2009-04-14 Thread PetriL
Does this mean that the BIOS upgrade fixed your problems? Yes, it does. My working assumption (read: guess, based on observed behavior) is that the available steps are read through some BIOS calls, and when your CPU is newer than your BIOS, the data is incomplete and Speedstep can't therefore

[Bug 132403] Re: Cpu frequency scaling is limited to stock speeds

2009-03-08 Thread PetriL
I have to pull back my earlier astonishment a bit: I upgraded the BIOS on the system, and now Speedstep is back. So ignore the rant-ish above. Clearly there are deeper issues than just Linux kernel at play... -- Cpu frequency scaling is limited to stock speeds

[Bug 132403] Re: Cpu frequency scaling is limited to stock speeds

2009-03-05 Thread PetriL
Could anyone please explain what happened to this bug, and why? This problem occurs with NON-overclocked Core 2 Duo 8500 (3.16 GHz) on a stock Intel board that does not even support overclocking in the first place. Just updating the CPU to a spiffier one (on fully-patched Hardy Heron x86)

[Bug 312968] Re: rng-tools fails to create device files in jaunty alpha 2

2009-01-17 Thread PetriL
I went back to 8.10, and looks like my memory of running this OK on 8.10 false, it was 8.04 with a patched kernel. On 8.10 I get the same error message as I got with Jaunty Alpha 2, but it looks like it does not matter after all: what is needed is to activate the following line in

[Bug 310301] Re: Jaunty alpha 2 black screen after ubuntu progress bar

2009-01-01 Thread PetriL
Addendum to previous note: Got myself a working system by doing the following steps via another computer (moving the memory stick over and editing its contents): Removing S30gdm in /etc/rc2.d Adding the following lines to rc.local: apt-get install ssh EOF Y Y Y EOF (probably just one Y would

[Bug 312968] [NEW] rng-tools fails to create device files in jaunty alpha 2

2009-01-01 Thread PetriL
Public bug reported: apt-get install rng-tools fails to create the devices on VIA EPIA EN1200EG motherboard on Jaunty alpha 2 alternate server package. This uses VIA C7 CPU that has the VIA Padlock HW random number generator. Worked ok on 8.10 with the same motherboard. Command output: #

[Bug 310301] Re: Jaunty alpha 2 black screen after ubuntu progress bar

2008-12-30 Thread PetriL
Installed Jaunty Alpha 2 server from the alternate CD on EPIA EN1200EG motherboard based system. The target hard disk was a 4GB USB memory stick. Also 2 x 1.5 TB SATA drives were connected, but not used as part of the installation. The installation went without incidents, the system boots OK,