I think I found the problem. I have to use acpi=force in menu.lst. Apparently a recent update re-wrote menu.lst and removed that parameter. I did not realize that updates do that. I put that back in and it appears to be stable + it shuts down properly. I guess not shutting down should have been my clue, as I have had to make that change one time before in Feisty and when the Gutsy upgrade was done.
For future reference, is there a way of predicting when an update will overwrite menu.lst or is this just a routine thing to have to check? Doesn't seem like detail that a Linux for regular people should have happen. Thanks for responding. Lyle On Wed, 20 Feb 2008 03:26:51 -0000 Parthan <[EMAIL PROTECTED]> wrote: > Thank you for taking the time to report this bug and >helping to make > Ubuntu better. Unfortunately we can't fix it, because >your description > does not yet have enough information. > > Please include the following additional information, if >you have not already done so (pay attention to lspci's >additional options): > 1. Please include the output of the command "uname -a" >in your next response. It should be one, long line of >text which includes the exact kernel version you're >running, as well as the CPU architecture. > 2. Please run the command "dmesg > dmesg.log" after a >fresh boot and attach the resulting file "dmesg.log" to >this bug report. > 3. Please run the command "sudo lspci -vvnn > >lspci-vvnn.log" and attach the resulting file >"lspci-vvnn.log" to this bug report. > > ** Changed in: ubuntu > Status: New => Incomplete > > -- > Gutsy "faints", usually recovers. > https://bugs.launchpad.net/bugs/193566 > You received this bug notification because you are a >direct subscriber > of the bug. > > Status in Ubuntu: Incomplete > > Bug description: > Nobilis notebook, PIII, 256 MB RAM. Since 2 updates ago, >Gutsy "faints" - screen goes blank, fan stops. Usually >recovers after 2-3 sec. Sometimes it doesn't and have to >switch off to reboot. Fiesty did this a few months ago >after an update. A couple updates later, the problem went >away. Updated to Gutsy, no problem. Then Gutsy started >the problem after an update. Wireless does not loose >connection when it faints. Lyle & Sue Luzum -- Gutsy "faints", usually recovers. https://bugs.launchpad.net/bugs/193566 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
