cdrom not detected in feisty

[André FL Ribeiro]

in the feisty daily build of 19-12-2006 the install process goes smooth until it tries to get access to the cd. and it fails saying that "there's no media or no cdrom inserted in drive".

dmesg output shows drive as if it was correctly loaded.

(this is happening on a hp/compaq nc6320, if that matters)

If someone needs more help/output on this, just ask.

cheers,
flai

[towsonu2003 (towsonu2003)]

were you using the liveCD or the alternative installation CD? sorry if the answer is too obvious :)

[André FL Ribeiro (andre-fl-ribeiro)]

i'm using the alternate install cd downloaded from http://cdimage.ubuntu.com/daily/current/

i dont thnik there's a liveCD for the daily builds

[André FL Ribeiro (andre-fl-ribeiro)]

just fount that the mount command is failing with some error like this:

mount failed: /dev/scd0 no such device

still no error on dmesg or /var/log/syslog
I'm lost and don't know where to get a cause/solution for this

(this is happening on a hp/compaq nc6320 with a PIONEER DVDRW DVR-K17)

[towsonu2003 (towsonu2003)]

sorry, you will probably not going to receive help from a bug report. best case scenario: developers will ask for more input. try ubuntuforums.org for geting help. here is a resource on where to go for help: https://help.ubuntu.com/community/HowToGetHelp

[Tom Shaw (firephoto)]

Same thing happened here today with a daily kubuntu alternate install cd from 20061229.

At first I expected it with the Intel DG965SS board and known issues there with the marvell pata, but then I tried the cd on my Athlon system and it had the same behavior, there was a long delay when it reached the point where it should be mounting the cdrom and just acted like I had removed the media. It was also impossible to mount the cdrom or any media manually and would only say "Invalid option".

I ended up installing Edgy from the athlon system to the new hard drive and dist-upgrading it to Feisty then moved the drive to the i965 system and it worked ok then.

[Sero (sero4linux)]

I have the same problem with the feisty hord1 x86 Destop CD.

This problem is not limited to Ubuntu but is a general kernel problem in the >= 2.6.18 kernel series. They introduced a new error handling for libata which disables my DVD drive at boot (I have the same Pioneer model as you on a Dell I6000 notebook with intel 915gm chipset). Maybe this problem was fixed in kernel 2.6.20rc2 - I didn't have the chance to test it yet.

For more information confer e.g. http://bugzilla.kernel.org/show_bug.cgi?id=7608

There is still enough time to get this fixed upstream and include a working kernel in feisty I'd say ;)

[Bruce Cowan (bruce89-deactivatedaccount)]

I also have this bug using the latest AMD64 daily CD, with a LG LSA-4163B DVD±RW drive.

[cestuila (cestuila)]

Same thing here.
My config :
asus p5b de luxe (dvd + dvdrw on jmicron mode ahci).
in /dev i can see /dev/scd0 and /dev/scd1 but if i want to mount manually
my feisty cd:
- ......... the medium is read-only .......(so the cd is detected).
- mount: bad option (something like this).
This appen for feisty daily 291206 301206 311206 010107 020107
When i try with herd1 it works, but stops at 82%.

[Martin Visser (martinvisser99)]

Using 05-Jan-2007 Daily alternate feisty to do install on Vmware Workstation 5.5.3 (Windows XP host).

I get the same result as above - after selecting keyboard, the installer goes to redetect the CD-ROM, but it is not found.

Alt-F4 shows lots of "kernel: not found" messages interspersed with the occasional "Intel ISA PCIC probe: not found" messages.

[cestuila (cestuila)]

Same thing with herd2.
My config :
asus p5b de luxe (dvd + dvdrw on jmicron mode ahci).

[Dennis Schmitz (deezid)]

Same problem here with the alternate-cd (x86):
date: kernel, not found
date: kernel, not found
date: kernel, not found
date: kernel, not found
...
on tty4

My config:
asus p5w dh delux
core 2 duo e6600
2GB Ram Dualchannel
DVD-RW on Intel-Ich7-Controller. I checked the jmicron-controller, too, but got the same error.

[elaveriao (elaveriao)]

Same problem with herd2 server CD installation.

Two completely distinct configurations
Pentium II+128 RAM
Presario 2500:Pentium IV+512 RAM

More details if needed.

IMHO importance is more than medium. I can use nearly any other distribution, but Feisty is today uninstallable (besides upgrading)

[elaveriao (elaveriao)]

Sorry if the following is nonsense

First of all, I try to mount hdc on cdrom

mount -t iso9660 /dev/hdc /cdrom -o ro

says

mount:Mounting /dev/hdc on cdrom failed: No such device

I can't see /dev/hdc, as

ls /dev/hdc

says

brw-rw---- 1 root rooot 22, 0 Jan 24 21:37 /dv/hdc

But I cannot see iso9660

dmesg -s100000|grep "9660" says nothing

And I can't find iso9660 module in /lib/modules/2.6.20-5-generic

[Sero (sero4linux)]

I did not quite understand your post - cdrom drives are managed by libata in the newer kernels and do not appear as hdX anymore but as sdX now. Furthermore I would bet support for the cdrom filesystem iso9660 is build in the kernel and NOT as a module.

I am quite sure that the herd3 CD will boot on our machines again - the problem is fixed (at least for me and another bug reporter in kernel bugzilla) in kernel-2.6.20-rc5.

[Sero (sero4linux)]

WORKSFORME with Feisty Herd5.

$ uname -r
2.6.20-10-generic

[Jens Abraham (jens-abraham)]

It seems that my report #96639 describes the same bug. But it occures with the actuel beta of feisty. So please have a short look on that

[Colin Watson (cjwatson)]

For the record, everyone referring to "kernel: not found" was suffering from a different bug in a PCMCIA bridge driver, fixed a while back.

[Colin Watson (cjwatson)]

flai, could you retry with the Feisty beta release and see if you can still reproduce this?

I would prefer it if anyone else experiencing this problem could file a new bug at this point. This bug log has got pretty confused and there seem to be a number of different issues at work.

Most issues like this are going to be kernel bugs or conceivably udev bugs, although there's a slim possibility of an installer bug. These days, the installer's involvement in figuring out where to find the CD device is limited to a pretty thin layer over programs in udev that tell us the type of a device.

[André FL Ribeiro (andre-fl-ribeiro)]

its not happening anymore! :)

cheers,
flai