[Lucid] Asus EEE 904HD doesn't shut down

Bug #511436 reported by Anders Sjölander
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

My computer doesn't shut down. I use the shut down function in Ubuntu and it starts to log out, Plymouth displays (using the Solar theme) but the computer doesn't turn itself off. The animation in Plymouth keeps rolling so the system doesn't seem to have locked up. None of the ttys show any error messages.

Not sure of what info might be relevant here. Suggestions are welcome.

OS: Ubuntu 10.04
Computer: Asus EEE 904HD, 1Mb RAM, Intel 915 chipset
Kernel: 2.6.32-10-generic

Revision history for this message
Mitch Towner (kermiac) wrote :

Is this on an installed system or are you using the live cd?

Revision history for this message
Anders Sjölander (thezood) wrote :

This is on a freshly installed (not upgraded) system with all the latest updates.

Revision history for this message
Seth (seth-hollen) wrote :

I get the same problem.
If I go to another console while the shutdown screen is frozen, then press ctrl-alt-del I get
some error messages about pulse audio and then plymouth, then the message that the system will reboot.

anyone know how I can see or enable looging at shutdown so I can post an exact message?

Revision history for this message
Mitch Towner (kermiac) wrote :

thezood --> Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.
Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:

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 -vnvn > lspci-vnvn.log" and attach the resulting file "lspci-vnvn.log" to this bug report.
4. Please run the command "sudo dmidecode >dmidecode.out" and add the resulting file "dmidecode.out" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Mitch Towner (kermiac) wrote :

Seth --> The symptom of this particular bug, failure to power off when shutting down, is specific to the hardware and BIOS used. So while many people may have the same symptom each should be a separate bug. The bug report should contain the information requested at http://wiki.ubuntu.com/KernelTeamBugPolicies and the output of 'sudo dmidecode'. A new bug report's title should contain information about either your motherboard or system make and model.

summary: - Computer doesn't shut down
+ [Lucid] Asus EEE 904HD doesn't shut down
Revision history for this message
Seth (seth-hollen) wrote :

OK here's my info:
Thinkpad T43 with ATI X300 graphics card.

Revision history for this message
Seth (seth-hollen) wrote :

dmesg log

Revision history for this message
Seth (seth-hollen) wrote :
Revision history for this message
Seth (seth-hollen) wrote :

Linux sparrow 2.6.32-11-generic #15-Ubuntu SMP Tue Jan 19 18:16:27 UTC 2010 i686 GNU/Linux

Revision history for this message
Anders Sjölander (thezood) wrote :

Here is the output of dmidecode on my computer.

Revision history for this message
Anders Sjölander (thezood) wrote :

$ uname -a
Linux entropia 2.6.32-10-generic #14-Ubuntu SMP Thu Jan 7 17:38:40 UTC 2010 i686 GNU/Linux

Revision history for this message
Anders Sjölander (thezood) wrote :
Revision history for this message
Anders Sjölander (thezood) wrote :
Revision history for this message
Mitch Towner (kermiac) wrote :

Thankyou for posting the requested information thezood!
Whilst going through these logs, I noticed that you are not running the latest version of the BIOS for your laptop (you are running "Version 0902"). Are you able to update your BIOS to the latest version ("Version 1401" as reported on http://support.asus.com/download/download.aspx?model=Eee%20PC%20904HD/Linux&SLanguage=en-us) & check to see if you are still experiencing this issue?
Thanks in advance!

Revision history for this message
Anders Sjölander (thezood) wrote :

Sharply spotted! I've upgraded the bios now but the issue remain. I have noticed that there seem to be something weird with my installation, though. Not all startup applications are being executed (like Empathy and nm-applet), I have to run them manually. Maybe this is related to startup and shutdown scripts. There was a problem after installing the live CD, I had to manually make the user the installation program created into administrator and superuser. Also, there is a program called "Install RELEASE" in System -> Administration. Is my installation running like a live CD?

Revision history for this message
Mitch Towner (kermiac) wrote :

It seems like you may have an issue with your installation as you noted above. Did you check the MD5 SUM of the iso you downloaded? Perhaps there is an issue with your installation media due to the issues you have described above - it certainly sounds like something is not right as you should not be experiencing these issues on a fresh install of Lucid.
Please try downloading the latest daily image from http://cdimage.ubuntu.com/daily-live/current/ & performing a fresh install to see if you still experience these issues. Please note that the MD5 SUM's are available at that link to verify that your iso is ok.
Thanks in advance!

Revision history for this message
Anders Sjölander (thezood) wrote :

Yep, reinstall with a daily CD solved the problem!

Revision history for this message
Mitch Towner (kermiac) wrote :

This bug report is being closed due to your last comment regarding this being fixed after re-installing using the latest daily Lucid iso. This confirms that the original image you downloaded was corrupt.
For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better.
Please submit any future bugs you may find.

Changed in ubuntu:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.