I have seen this behaviour for the first time today. I've had Jaunty
running for a couple of weeks on my Compaq Armada M700 (PIII-800). Today
I installed the latest batch of updates (I usually update whenever it
tells me, so it should only be the last day or so's worth of updates)
and then noticed
OK, after a cool down and reboot:
It was /proc/acpi/thermal_zone/C19A/something it was popping up and
complaining about. After the reboot it hasn't been warning me. It also
seems to be running cooler, and I've felt the fan running.as well.
I guess the update left it in an odd state.
I've now
I have a Compaq Armada M700 PIII-800 which booted fine with 9.04 using
kernel 2.6.27-11, failed to boot with 2.6.28-11 and now it boots
successfully again with 2.6.30-rc4.
I do have the radio_maestro module enabled and loaded, NOT blacklisted.
This laptop doesn't have built in wireless, I don't
I finally found time to try this again.. and thought I'd install the
latest kernel before generating the log files.
I installed 2.6.30-rc4 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v2.6.30-rc4/ and it now appears to boot successfully under
9.04.
Looks like a drive-by fix, so thanks to
I have just updated my own Compaq Armada M700 with the Jaunty release
(not the Alpha as above), using the 'New distribution available' button
on Update Manager. It all seemed to go smoothly but I have the same
issue, It fails to boot with many messages scrolling past too quick to
catch before
I saw the same issue (although it was with python2.6.1-0ubuntu7 not 3).
It was difficult to see what was going on because the dist-upgrade
terminal window is too small and not resizeable. I noticed debconf
complaining that it wanted at least a 31x13 window as well.
--
package python
