-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 02 May 2003 15:53, Rikard Johnels wrote:
Hello all!
I run a 2.4.19-SMP "home brewed" kernel on 8.1. My GRUB menu.lst states:
title linux kernel (hd0,0)/vmlinuz root=/dev/hde3 hdc=ide-scsi vga=788 initrd (hd0,0)/initrd
But i cant seem to get the IDE CD-RW to work. i get all these ide-scsi: hdc: unsupported command in request queue (0) end_request: I/O error, dev 16:00 (hdc), sector 64 ide-scsi: hdc: unsupported command in request queue (0) end_request: I/O error, dev 16:00 (hdc), sector 66 ide-scsi: hdc: unsupported command in request queue (0) end_request: I/O error, dev 16:00 (hdc), sector 68 ide-scsi: hdc: unsupported command in request queue (0) end_request: I/O error, dev 16:00 (hdc), sector 70 ide-scsi: hdc: unsupported command in request queue (0) end_request: I/O error, dev 16:00 (hdc), sector 72 ide-scsi: hdc: unsupported command in request queue (0) end_request: I/O error, dev 16:00 (hdc), sector 74 ide-scsi: hdc: unsupported command in request queue (0) end_request: I/O error, dev 16:00 (hdc), sector 76 ide-scsi: hdc: unsupported command in request queue (0) end_request: I/O error, dev 16:00 (hdc), sector 78 cdrom: open failed.
I *think* i have the right mudules installed, atleast a lsmod gives me:
ide-scsi 8912 0
I have VmWare installed, but even without it running it fails. Any clues? As it is now, i still run a Windows2000 box just to be able to burn CD's. I would like to retire that beast (or turn it into something more useful)
I get the same thing. Do you have a cd in the drive? I'm betting you do.
There were a few threads about this and I believe that this can also be found
in the SuSE sbd. IIRC it's all about trying to read the drive in a similar
fashion as a hard drive - which of course it isn't. Hence, the messages your
recieveing.
Now as to the problem of not being able to get the cd-rw to work...
Let's first look at a couple of things to see of your "allow" by way of
symlinks and persmission sets to access/use the cd-rw.
Run "la /dev/cdron" and/or "la /dev/cdrecorder" and see what it tells you.
Mine says this.
crrey@Crusher-1:~> la /dev/cdrom
lrwxrwxrwx 1 crrey disk 3 2003-01-30 20:14 /dev/cdrom -> hdc
crrey@Crusher-1:~> la /dev/cdrecorder
lrwxrwxrwx 1 crrey disk 3 2003-01-10 12:43 /dev/cdrecorder ->
sr0
As it should be the symlink cdrom is pointing to /dev/hdc and the symlink
cdrecorder is pointing to /dev/sr0 (scsi recorder 0 = 1st scsi recorder
device). [forgive me if I'm over simplifying - I don't know your level of
experience :)]
Now, look at the "real" devices, hdc and sr0 and see what it says.
crrey@Crusher-1:~> la /dev/hdc
brw------- 1 crrey cdrecording 22, 0 2002-10-14 09:53 /dev/hdc
crrey@Crusher-1:~> la /dev/sr0
brw------- 1 crrey cdrecording 11, 0 2002-10-14 09:53 /dev/sr0
Note that I have a special group called cdrecording. This is not necessary
and your will most likely say "disk" or "user". If any of the users ( the
first group - crrey) is set to root then only root can access the device.
Otherwise run, as root, chown