Fedora 15 boot fails -- Drops into debug shell

[edward_c]

I just purchased a new ASUS desktop computer and want to run Fedora on it but when I try to boot Fedora-15-x86_64-Live-Desktop.iso which I have burned to a CD it fails. It boots the Fedora splash screen and I get something that looks like a balloon which is filling. That screen drops and I get a black screen with the following in the upper left corner:

[ 2.354154] ata2.01: failed to resume link (SControl0)
[ 2.355118] ata1.01: failed to resume link (SControl0)
[ 8.800356] ata2.01: failed to resume link (SControl0)
[21.710701] ata2.01: failed to resume link (SControl0)

Dropping to debug shell

sh: can't access tty; jobcontrol turned off
dracut:/#


I can execute various linux shell commands such as 'ls' but can't figure out what to do.
Anybody seen anything like this and more importantly how do you get the system to boot?

---------- Post added at 08:08 PM ---------- Previous post was at 06:29 PM ----------

After some more investigation, I find that I can run dmesg. So looking at the boot messages it appears that I fail with message:

dracut Warning: No root device "live:/dev/disk/by-label/Fedora-15-x86-64-Live-Desktop.is" found

And when I look in the dev directory I only see directories "DATA", "Recovery", and "WIN7".

Further studying the dmesg output I don't see the CDROM drive being identified. It is using a SATA CDROM drive.

Anyone know how to make Linux see the CDROM, since the BIOS obviously sees it and boots to it?:confused:

[edward_c]

FYI!!!

The new systlem I purchased is as I mentioned an ASUS, more specifically an ASUS CM6850-05, Intel Core i5-2310, 12GB memory, SATA6 and SATA3 ports, USB 3.0 and 2.0 ports. The DVD/CD is a DH24ABS drive that was connected to SATA6G_2 port and it would boot the CD but then couldn't see the drive when linux initialized and discovered the hardware.

Not sure why this makes a difference, but I connected the DVD drive to SATA3G_1 port and linux now boot and I'm able to run the live CD.

I haven't been able to find any documented case like this, not saying they aren't there just in my googling I haven't found one. So I thought it was worth mentioning. If anyone knows why this works and the other doesn't I would appreciate the knowledge.

Thanks

[Wraukon]

Although this applied to a CD, I wanted to say a very big THANK YOU for posting this, as it told me what I should be looking for -- I had unknowingly created a label mismatch between the kernel load (root=) and what label I had actually given the root filesystem *on my hard drive*.

Thanks again!

Cheers,

Wraukon the Excellent

[axel2078]

This is exactly the same problem I'm having with my brand new Dell XPS laptop I just got yesterday. I get the exact same error message. How would your fix apply to a laptop though? I can't connect the cd-drom drive to something else.