6.10 Live cd problem

Bug #91434 reported by Ilian Mitev
10
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I tried to start my ubuntu live cd. So I configure my Bios and the cd starts. When I try to start the OS it starts loading and shows an error. I`m an amateur and don`t understand it. It shows the following:

BusyBox v1.1.3 (Debian 1:1.1.3-2ubuntu3) Built-In Shell(ash)
/bin/sh; can`t access tty; job control turned off

Can someone help me? This didn`t happen on my old pc when i tried to start the OS from the live cd. I tried Kubuntu and Xubuntu but it showed the same thing. My pc works with a 250 gb hard drive a pentium 4 dual core processor (3.00 ghz) and a GeForce 7600 gs and has 2 gb Ram? some help please

description: updated
Revision history for this message
Dan O'Huiginn (daniel-ohuiginn) wrote :

Hi,

I'm not sure what's happening, but there are some other people having similar problems. Have a look:

* In the Ubuntu forums: http://ubuntuforums.org/showthread.php?t=292533

* In the bug tracking system: https://launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/89380

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

Thanks for taking the time to report this bug and helping to make Ubuntu better. With which version of Ubuntu did you notice this issue? Thanks in advance.

Revision history for this message
Ilian Mitev (forsakensoul) wrote :

Well with the 6.10 and it happened to kubuntu and exubuntu and edubuntu ... I recieved the official cd`s today and tried with the cd i got from the mail it was the same thing.

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

If you happen to have a working version of Ubuntu at all could you please include the following additional information, if you have not already done so (please 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' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command '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 http://wiki.ubuntu.com/DebuggingKernelProblems . Thanks in advance!

Revision history for this message
Budman (dhinckle) wrote :

I am having this exact problem with Fiesty Herd 5. Edgy works fine in 64, and 32bit, but fiesty won't boot, and i get this same error in both 32 and 64. I am attaching my working edgy logs. I am new to linux, but if there is anything i can do please email me. Thanks for everything you guys do.

Revision history for this message
GabrielGrant (gabrielgrant) wrote :

Budman: Based on that output, this appears to be a duplicate of https://launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/84964

It does not immediately seem to be related to the problems with Edgy, as your problem first appeared in later kernel releases, so please track bug 84964 regarding your problem.

Thanks!

Changed in linux-source-2.6.20:
status: Confirmed → Unconfirmed
Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

Hi,

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 - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. If the issue still exists, please add the Hardy kernel "linux" task to the bug report. This can be done by clicking on the "Also affects distribution" link in the Actions area on left hand side of the bug report. Select "Ubuntu" as the Distribution and type in "linux" for the Source Package Name. Thanks.

Changed in linux-source-2.6.17:
status: New → Won't Fix
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.