[Bug 93243] Re: edgy shutdown unexpected

2009-01-30 Thread Michele Mangili
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on t

[Bug 93243] Re: edgy shutdown unexpected

2008-08-28 Thread Leann Ogasawara
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test: 1) If you are comfortable

[Bug 93243] Re: edgy shutdown unexpected

2008-04-25 Thread Andrew Starr-Bochicchio
Hi Evan, The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue

[Bug 93243] Re: edgy shutdown unexpected

2007-05-20 Thread geoffrey
By, now, I've upgraded to feisty, and still require the acpi=off noacpi parameters to get the fan running. for my machine, which is a very common chipset, this problem is still at large. this isn't the kind of thing I like to explain to new/prospective linux/ubuntu users. -- edgy shutdown unexp

[Bug 93243] Re: edgy shutdown unexpected

2007-03-26 Thread geoffrey
** Attachment added: "of course, uname after fix" http://librarian.launchpad.net/6991607/uname.log -- edgy shutdown unexpected https://launchpad.net/bugs/93243 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 93243] Re: edgy shutdown unexpected

2007-03-26 Thread geoffrey
** Attachment added: "lspci after fix" http://librarian.launchpad.net/6991605/lspci-vvnn.log -- edgy shutdown unexpected https://launchpad.net/bugs/93243 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 93243] Re: edgy shutdown unexpected

2007-03-26 Thread geoffrey
temporary fix: after some online reading, I tried the solution described here: http://www.vmware.com/community/message.jspa?messageID=332390 In my case, the BIOS of my machine controls the fan, and upon boot up, when ACPI kicks in, the fan shuts off. I edited /boot/grub/menu.lst and found the li

[Bug 93243] Re: edgy shutdown unexpected

2007-03-19 Thread geoffrey
Okay, the CPU fan definitely Does Not run with Edgy. >From the time that I choose Edgy from the Grub menu, the CPU promptly stops. >If I let the system boot up, log in, and let the GUI and desktop load, the fan >remains motionless. Otherwise, the fans runs on Dapper and Windows XP. I haven't al

[Bug 93243] Re: edgy shutdown unexpected

2007-03-19 Thread Brian Murray
** Changed in: Ubuntu Sourcepackagename: None => linux-source-2.6.17 Assignee: Brian Murray => (unassigned) Status: Needs Info => Unconfirmed -- edgy shutdown unexpected https://launchpad.net/bugs/93243 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.co

[Bug 93243] Re: edgy shutdown unexpected

2007-03-17 Thread geoffrey
** Attachment added: "lspci" http://librarian.launchpad.net/6850162/lspci-vvnn.log -- edgy shutdown unexpected https://launchpad.net/bugs/93243 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 93243] Re: edgy shutdown unexpected

2007-03-17 Thread geoffrey
Linux geoffrey-desktop 2.6.17-10-386 #2 Fri Oct 13 18:41:40 UTC 2006 i686 GNU/Linux ** Attachment added: "dmesg" http://librarian.launchpad.net/6850160/dmesg.log -- edgy shutdown unexpected https://launchpad.net/bugs/93243 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://li

[Bug 93243] Re: edgy shutdown unexpected

2007-03-17 Thread Brian Murray
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information. Please include the following additional information, if you have not already done so (please pay attention to lspci's addi