[Bug 367048] Re: upgrade from 8.10 to 9.04 resulted in unusable machine
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. So the problem on EPIA boards seems to be related to the encryption/HW random number support. -- upgrade from 8.10 to 9.04 resulted in unusable machine https://bugs.launchpad.net/bugs/367048 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367048] Re: upgrade from 8.10 to 9.04 resulted in unusable machine
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 Celsius (rather cold isn't it ?)" Isn't it just that coolness that keeps us hitting our heads against these quirks with Via's CPUs? ;) Too bad Intel seems to wipe them out with their incoming Atoms. I grew fond of these nice, low-power buggers over the years... -- upgrade from 8.10 to 9.04 resulted in unusable machine https://bugs.launchpad.net/bugs/367048 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367048] Re: upgrade from 8.10 to 9.04 resulted in unusable machine
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 complaints from usbhid every time I switch windows over, and those comments pop up if I switch away from and back to EPIA. So it looks like it is alive, and waiting for something magic to happen... Managed to boot 9.04 Alpha on same HW earlier after some tinkering with GDM. Other new symptoms at boot are: "ohci1394: fw-host0: Get PHY Reg timeout [varying numbers]" lines (a couple of them) And a new comment in the beginning: "longhaul: APIC detected: Longhaul is currently broken in this configuration" The system boots from USB stick, no other drives connected. -- upgrade from 8.10 to 9.04 resulted in unusable machine https://bugs.launchpad.net/bugs/367048 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366961] Re: odt2txt starts automaticly, using 23% cpu doing nothing, after closing files
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 doing nothing, after closing files https://bugs.launchpad.net/bugs/366961 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132403] Re: Cpu frequency scaling is limited to stock speeds
"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 work. Everything has worked "by the book" on that box after I updated the BIOS. Things run cooler and faster than before, and idling is *very* cool indeed. -- Cpu frequency scaling is limited to stock speeds https://bugs.launchpad.net/bugs/132403 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132403] Re: Cpu frequency scaling is limited to stock speeds
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 https://bugs.launchpad.net/bugs/132403 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132403] Re: Cpu frequency scaling is limited to stock speeds
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) brought up the warning dialog box and forced the box to run on 100% CPU speed on both CPUs, effectively nulling the original upgrade goal (get a cooler-idling 45 nm technology CPU which still gives you the extra punch over the previous generation CPU when needed). Ignoring such a relevant feature on top-end HW and top-end SW (Ubuntu) seems like a bad idea, especially when same board with Windows works just fine, even in overclocked situations (based on comments above). Quick search did not bring up any guidance on how to work around this using manual config of speedstep, except by minimizing daily Ubuntu usage on dual-boot boxes. Installing cpufrequtils did not help either. -- Cpu frequency scaling is limited to stock speeds https://bugs.launchpad.net/bugs/132403 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 312968] Re: rng-tools fails to create device files in jaunty alpha 2
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 /etc/default/rng-tools: RNGDOPTIONS="--hrng=viakernel --fill-watermark=90% --feed-interval=1" In an older, working setup, that used to be just "--hrng=via" The HW random generator starts fine thereafter. Note also, that the other alternative in /etc/default/rng-tools: RNGDOPTIONS="--hrng=viapadlock --fill-watermark=90% --feed-interval=1" does NOT work. There is very little information on the VIA Padlock in general and especially about that and Ubuntu. For those searching for "VIA PADLOCK UBUNTU /dev/hwrng", here are some links that helped me along the way, for Google to pick up: http://ubuntuforums.org/archive/index.php/t-710243.html https://www.grounation.org/index.php?2008/07/02/6-via-c7-padlock-on- debian-etch http://www.logix.cz/michal/devel/padlock/ http://a110wiki.de/wiki/VIA_Padlock Right now I can not continue further with Jaunty Alpha 2, but if the code base for rng-tools is same on that as it was on 8.10, the assumption is that the error I saw there was just the same as the one I fixed on 8.10 with the steps above. So as far as I am concerned, this bug can be closed. -- rng-tools fails to create device files in jaunty alpha 2 https://bugs.launchpad.net/bugs/312968 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 312968] [NEW] rng-tools fails to create device files in jaunty alpha 2
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: # apt-get install rng-tools Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: rng-tools 0 upgraded, 1 newly installed, 0 to remove and 110 not upgraded. Need to get 0B/43.5kB of archives. After this operation, 209kB of additional disk space will be used. Selecting previously deselected package rng-tools. (Reading database ... 106762 files and directories currently installed.) Unpacking rng-tools (from .../rng-tools_2-unofficial-mt.12-1_i386.deb) ... Processing triggers for man-db ... Setting up rng-tools (2-unofficial-mt.12-1) ... Trying to create /dev/hwrng device inode... udev active, devices will be created in /dev/.static/dev/ rm: cannot remove `hwrng-': Read-only file system mknod: `hwrng-': Read-only file system makedev hwrng c 10 183 root root 0600: failed rm: cannot remove `hwrng-': Read-only file system Starting Hardware RNG entropy gatherer daemon: (Hardware RNG device inode not found) /etc/init.d/rng-tools: Cannot find a hardware RNG device to use. invoke-rc.d: initscript rng-tools, action "start" failed. ** Affects: ubuntu Importance: Undecided Status: New -- rng-tools fails to create device files in jaunty alpha 2 https://bugs.launchpad.net/bugs/312968 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 310301] Re: Jaunty alpha 2 black screen after ubuntu progress bar
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
[Bug 310301] Re: Jaunty alpha 2 black screen after ubuntu progress bar
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, the progress indicator goes all the way to the end, then the attached 1024x768 LCD screen seems to reset itself twice and the system apparently dies. The system asks for IP from local DHCP during boot, but does not respond to pings against the given address. Tried logging in blind via an attached keyboard and running "sudo apt- get install ssh", but got no indication of success, and neither was I able to connect to the box via ssh after reboot. These seem to indicate that the system is dead right after the bootup is completed. EPIA motherboards are a product of VIA, so it certainly has VIA display HW, hence probably we are talking about the same bug as the one above. EN1200EG uses C7 processor, which should be supported by Ubuntu. I connected the "hard disk" memory stick to another box: here's the contents of /var/log/syslog: Dec 31 01:10:23 sol2 syslogd 1.5.0#5ubuntu2: restart. Dec 31 01:10:24 sol2 kernel: Inspecting /boot/System.map-2.6.28-3-generic Dec 31 01:10:24 sol2 kernel: Cannot find map file. Dec 31 01:10:24 sol2 kernel: Loaded 48392 symbols from 68 modules. Dec 31 01:10:24 sol2 kernel: [0.00] BIOS EBDA/lowmem at: 0009f800/0009f800 Dec 31 01:10:24 sol2 kernel: [0.00] Initializing cgroup subsys cpuset Dec 31 01:10:24 sol2 kernel: [0.00] Initializing cgroup subsys cpu Dec 31 01:10:24 sol2 kernel: [0.00] Linux version 2.6.28-3-generic (bui...@palmer) (gcc version 4.3.3 20081210 (prerelease) (Ubuntu 4.3.2-2ubuntu8) ) #4-Ubuntu SMP Fri Dec 12 22:48:15 UTC 2008 (Ubuntu 2.6.28-3.4-generic) Dec 31 01:10:24 sol2 kernel: [0.00] KERNEL supported cpus: Dec 31 01:10:24 sol2 kernel: [0.00] Intel GenuineIntel Dec 31 01:10:24 sol2 kernel: [0.00] AMD AuthenticAMD Dec 31 01:10:24 sol2 kernel: [0.00] NSC Geode by NSC Dec 31 01:10:24 sol2 kernel: [0.00] Cyrix CyrixInstead Dec 31 01:10:24 sol2 kernel: [0.00] Centaur CentaurHauls Dec 31 01:10:24 sol2 kernel: [0.00] Transmeta GenuineTMx86 Dec 31 01:10:24 sol2 kernel: [0.00] Transmeta TransmetaCPU Dec 31 01:10:24 sol2 kernel: [0.00] UMC UMC UMC UMC Dec 31 01:10:24 sol2 kernel: [0.00] BIOS-provided physical RAM map: Dec 31 01:10:24 sol2 kernel: [0.00] BIOS-e820: - 0009f800 (usable) Dec 31 01:10:24 sol2 kernel: [0.00] BIOS-e820: 0009f800 - 000a (reserved) Dec 31 01:10:24 sol2 kernel: [0.00] BIOS-e820: 000f - 0010 (reserved) Dec 31 01:10:24 sol2 kernel: [0.00] BIOS-e820: 0010 - 3bff (usable) Dec 31 01:10:24 sol2 kernel: [0.00] BIOS-e820: 3bff - 3bff3000 (ACPI NVS) Dec 31 01:10:24 sol2 kernel: [0.00] BIOS-e820: 3bff3000 - 3c00 (ACPI data) Dec 31 01:10:24 sol2 kernel: [0.00] BIOS-e820: fec0 - fec01000 (reserved) Dec 31 01:10:24 sol2 kernel: [0.00] BIOS-e820: fee0 - fee01000 (reserved) Dec 31 01:10:24 sol2 kernel: [0.00] BIOS-e820: - 0001 (reserved) Dec 31 01:10:24 sol2 kernel: [0.00] DMI 2.3 present. Dec 31 01:10:24 sol2 kernel: [0.00] last_pfn = 0x3bff0 max_arch_pfn = 0x10 Dec 31 01:10:24 sol2 kernel: [0.00] Scanning 2 areas for low memory corruption Dec 31 01:10:24 sol2 kernel: [0.00] modified physical RAM map: Dec 31 01:10:24 sol2 kernel: [0.00] modified: - 2000 (usable) Dec 31 01:10:24 sol2 kernel: [0.00] modified: 2000 - 6000 (reserved) Dec 31 01:10:24 sol2 kernel: [0.00] modified: 6000 - 7000 (usable) Dec 31 01:10:24 sol2 kernel: [0.00] modified: 7000 - 0001 (reserved) Dec 31 01:10:24 sol2 kernel: [0.00] modified: 0001 - 00092800 (usable) Dec 31 01:10:24 sol2 kernel: [0.00] modified: 0009f800 - 000a (reserved) Dec 31 01:10:24 sol2 kernel: [0.00] modified: 000f - 0010 (reserved) Dec 31 01:10:24 sol2 kernel: [0.00] modified: 0010 - 3bff (usable) Dec 31 01:10:24 sol2 kernel: [0.00] modified: 3bff - 3bff3000 (ACPI NVS) Dec 31 01:10:24 sol2 kernel: [0.00] modified: 3bff3000 - 3c00 (ACPI data) Dec 31 01:10:24 sol2 kernel: [0.00] modified: fec0 - fec01000 (reserved) Dec 31 01:10:24 sol2 kernel: [0.00] modified: fee0 - fee01000 (reserved) Dec 3
