8.10 throws me to busybox on an Acer Aspire 5050-5410.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Hi, I have an Acer Aspire 5050-5410 with Intrepid Ibex. The problem is that whenever I boot it it throws me to the busybox prompt everyone hates. It gives me all kinds of errors or warnings or whatever they are. Sometimes try driver 8139 instead (or something like that), something about the cdrom driver version something, that some dev/disk/by UUID file doesn't exist blah blah blah. Every time I boot there's something different.
I'm able to boot after I type exit. It gives me something like this:
exit
kinit: unable to find resume image. Starting normal boot...
Then it boots like it's supposed to do.
Ubuntu 7.10 didn't do this but Hardy Heron and Intrepid Ibex do it. I've tried different distros, like openSUSE, Mandriva, Fedora, PCLinux and Mint, all of these distros work well except Mint because it's Ubuntu derived.
The weird thing is that when I load up the live disc it boots very normal. I've tried several times to test it, but it never fails. When I install the system it gives me the busybox thing.
Thank you.
Changed in linux: | |
status: | In Progress → Confirmed |
Changed in linux (Ubuntu): | |
status: | Confirmed → Invalid |
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 -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https:/ /wiki.ubuntu. com/KernelTeamB ugPolicies Thanks in advance!