Ubuntu 7.10 beta failed to reboot after successful installation on Acer Aspire 5520 G

Bug #147955 reported by Auckland
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

First of all, I couldn't install Ubuntu 7.04 (neither i386 nor amd 64) "official release" on my new notebook (Acer Aspire 5520 G), thus I tried to install the beta version of Ubuntu 7.10 i386 (the amd 64 version doesn't work at all). The live cd was loaded very slowly but I finally managed to install Ubuntu successfully. I was asked to reboot the system and remove the live cd. I did as I was told but Ubuntu failed to start. The following error message appeared on the screen:
"Busy Box V1.1.3 (Debian 1:1.1.3-5 Ubuntu 4) Built-in Shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off (initramfs)"

I suspect that it's a hardware compatibility issue i.e PCI bug. I have noticed a PCI error message while the machine was booting but I couldn't write it down; the message appeared and vanished within a second!

I'll provide you with the following hardware information:
Acer Aspire 5520 G
AMD Turion 64 Mobile Technology MK-38 (2.2 GHz, 512 KB L2 cache)
Up to 384 MB Nvidia Ge Force 8400M G Turbo Cache
1 GB DDR2
15.4 WXGA Acer Crystal Brite LCD (8ms 1220 nits)
120 GB HDD
DVD-Super Multi double layer
802.11 b/g WLAN

I hope that developers will be able to sort out this hardware compatibility and software installation issues. I truly wish I could run Ubuntu 7.10 on my new acer notebook.

Thanks for your co-operation.

Revision history for this message
Adam Niedling (krychek) wrote :

Have you tried Hardy already?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

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 the current status, under the Status column, and change the Status back to "New". Thanks again!.

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.