Ubuntu
linux package

[Gutsy Final] Crash after clicking "Restart Now"

Bug #156006 reported by Aaron Whitehouse
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

I just tried to install Gutsy Final on a Dell Inspiron 510m with 256MB RAM.

After ubiquity has installed all the files, it prompts the user to either Reboot Now or to continue using the live system. When I click "Reboot Now", the system appears to shut down, but hangs with a black screen (the Bluetooth lights etc. remain on). Ctrl+Alt+Backspace does nothing.

My machine uses the -Intel driver and appears to be running Compiz by default.

Let me know if there is anything further that I can do to help.

Revision history for this message
TerryG (tgalati4) wrote :

Triaged to Incomplete. The Live CD needs ~384 MB of RAM to install successfully. Intel graphics tends to steal RAM for video use. It's possible that you ran out of RAM during install causing a hard crash. You can reinstall, but add a swap partition first. There are tutorials on the forums for how to build a swap partition. Swap gives you extra memory that should allow the install to proceed normally.

Changed in ubiquity:
status: New → Incomplete
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Does your installed system power off? If not could you please include as attachments the following additional information 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' 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.
4. Please run the command 'sudo dmidecode > dmidecode.log' and attach the resulting file 'dmidecode.log' to this bug report.
Thanks in advance!

Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

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

Other bug subscribers

Remote bug watches

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