CD-R(W) not accessible with SuSE 7.3 (no answer found in recent threads !)
Hello, Can somebody please help me with my CD writer problem ? I have already studied many documents and discussion threads on this subject and (I think) I pretty well understand what needs to be done, and (I think) I did it. But still I have problems with accessing my CD reader/writer. I can get reading to work, but not writing ! Please bear with this long message, but I'm trying to give as much information as possible. I am using SuSE 7.3 Professional, and booting with Loadlin from my C:/drive. The loadlin process (choose between Linux and Windows) works fine. The problem I am having is that I can mount my combi CD - CD-RW drive for reading,but NOT for burning CD's. The drive is a LITE-ON LTR-24102B, ATAPI CD-ROM CD-R/RW drive. Message from KOnCD is : ====================== No cd writer found ! Do you have an ATAPI/IDE cd writer ? Enable the 'ide-scsi emulation' in the kernel ! etc. etc. ====================== However, I have extensively checked all available information from SuSE's Support Database (and other sources) and I believe everything is configured OK. I specifically followed the instructions in the "IDE CD Writer" document in SuSE's Support Knowledgebase. Nevertheless it seems that the CD-drive still is associated with hdc instead of sdc0 !! I have the following line in the boot configuration "appendline" : ======================= disableapic vga=0x0317 disableapic ide=nodma apm=off hdc=ide-scsi ======================= Note : the drive really IS on hdc !!! I have rerun mk_initrd -> seeing the following output : ======================= # mk_initrd using " /dev/hdb7" as root device (mounted on "/" as "reiserfs") creating initrd "//boot/initrd" for kernel "//boot/vmlinuz" (2.4.10-4GB) module ide-scsi is "/lib/modules/2.4.10-4GB/kernel/drivers/scsi/ide-scsi.o" -> insmod ide-scsi module reiserfs is "/lib/modules/2.4.10-4GB/kernel/fs/reiserfs/reiserfs.o" -> insmod reiserfs Concatenating splash picture size 1024x768 to initrd... done. creating initrd "//boot/initrd.suse" for kernel "//boot/vmlinuz.suse" (2.4.10-4GB) module ide-scsi is "/lib/modules/2.4.10-4GB/kernel/drivers/scsi/ide-scsi.o" -> insmod ide-scsi module reiserfs is "/lib/modules/2.4.10-4GB/kernel/fs/reiserfs/reiserfs.o" -> insmod reiserfs Concatenating splash picture size 1024x768 to initrd... done If you're using lilo as bootmanager, you may want to run 'lilo' now. # ======================= Next I have copied the new "initrd" from /boot to the C:/library where my Loadlin is running from. This to make sure that the ide-scsi emulation is loaded. Then I modified /etc/init.d/boot.local, which now contains the following : ======================= ... cut # script with local commands to be executed from init on system startup # . /etc/rc.config # # Here you should add things, that should happen directly after booting # before we're going to the first run level. # /sbin/modprobe ide-scsi ======================= Next I have created the new links for CD-ROM and CD-RECORDER by running the commands : ln -sf/dev/scd0 /dev/cdrecorder ln -sf/dev/scd0 /dev/cdrom Remember : both functions are combined in the same drive. In /dev I now have : ======================= cdrecorder 0 B Mime type 2001-09-24 03.54 rw------- root root /dev/scd0 cdrom 0 B Mime type 2001-09-24 03.54 rw------- root root /dev/scd0 ..cut scd0 0 B Mime type 2001-09-24 03.54 rw------- root root ======================= Then I modified /etc/fstab, which now contains : ======================= /dev/hdb7 / reiserfs defaults 1 1 /dev/hdb5 /boot ext2 defaults 1 2 /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 devpts /dev/pts devpts defaults 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 proc /proc proc defaults 0 0 usbdevfs /proc/bus/usb usbdevfs defaults,noauto 0 0 /dev/hdb1 /windows/C vfat noauto,user 0 2 /dev/hdb6 swap swap pri=42 0 0 ======================= Rebooting the system (via loadlin) gives the following messages (Excerpt from "boot.msg") : ======================= ...cut <4>Starting kswapd <5>VFS: Diskquotas version dquot_6.5.0 initialized <4>pty: 256 Unix98 ptys configured <6>Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI enabled <6>ttyS00 at 0x03f8 (irq = 4) is a 16550A <6>Real Time Clock Driver v1.10e <4>block: 128 slots per queue, batch=16 <4>RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize <6>Uniform Multi-Platform E-IDE driver Revision: 6.31 <4>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx <4>VP_IDE: IDE controller on PCI bus 00 dev 89 <4>VP_IDE: chipset revision 6 <4>VP_IDE: not 100%% native mode: will probe irqs later <4>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx <6>VP_IDE: VIA vt8231 (rev 10) IDE UDMA100 controller on pci00:11.1 <4> ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:DMA <4> ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:pio <4>hd1: C/H/S=0/0/0 from BIOS ignored <4>hdb: MAXTOR 6L040J2, ATA DISK drive <4>hdc: LITE-ON LTR-24102B, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <6>hdb: 78177792 sectors (40027 MB) w/1819KiB Cache, CHS=77557/16/63, UDMA(100) <4>hdc: ATAPI 16X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) <6>Uniform CD-ROM driver Revision: 3.12 <4>ide-floppy driver 0.97.sv <6>Partition check: <6> hdb: [PTBL] [4866/255/63] hdb1 hdb2 < hdb5 hdb6 hdb7 > <6>Floppy drive(s): fd0 is 1.44M <6>FDC 0 is a post-1991 82077 <6>loop: loaded (max 8 devices) <4>ide-floppy driver 0.97.sv <6>SCSI subsystem driver Revision: 1.00 <3>request_module[scsi_hostadapter]: Root fs not mounted <3>request_module[scsi_hostadapter]: Root fs not mounted <6>md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 <6>md: Autodetecting RAID arrays. <4>md: autorun ... <4>md: ... autorun DONE. .. cut ======================= On the KDE Desktop I have created two icons : 1. A CD-writer icon, with properties Device : /dev/cdrecorder Mount point : /media/cdrecorder FS Type : auto 2. A CDROM icon with properties Device : /dev/cdrom Mount point : /media/cdrom FS Type : auto When trying to mount the CDROM, I get : ======================= Error Could not mount device. The reported error was: mount:/dev/cdrom: unknown device ======================= The same happens with CD-writer. Also, when I run cdrecord -scanbus (as root), I get the message : ======================= Cdrecord 1.11a05 (i686-suse-linux) etc ..... cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets etc...... ======================= HOW CAN THIS BE ????????? AND HERE COMES THE MYSTERIOUS THING : If I change the following lines in /etc/fstab : /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 into /dev/hdc /media/cdrecorder auto ro,noauto,user,exec 0 0 /dev/hdc /media/cdrom auto ro,noauto,user,exec 0 0 then (after adapting the properties of CDROM and CD-writer accordingly, I can mount both devices (for read-only) !!!?? So apparently, it seems that the ide-scsi emulation is not working at all ??? And that is probably the reason that KOnCD does not recognize the writer ? Could the problem be in the following messages during boot ? <6>SCSI subsystem driver Revision: 1.00 <3>request_module[scsi_hostadapter]: Root fs not mounted <3>request_module[scsi_hostadapter]: Root fs not mounted How can I solve this ? Any help is very much appreciated. ------------------------------ Jan Elders Nuenen the Netherlands
The 03.01.01 at 22:50, Jan Elders wrote:
Next I have created the new links for CD-ROM and CD-RECORDER by running the commands : ln -sf/dev/scd0 /dev/cdrecorder ln -sf/dev/scd0 /dev/cdrom Remember : both functions are combined in the same drive.
Mmm... this could be the mistake. I have: /dev/cdrom -> scd1 /dev/cdrecorder -> sr1 It might be that, sr0 instead of scd0 :-?
<4>hd1: C/H/S=0/0/0 from BIOS ignored <4>hdb: MAXTOR 6L040J2, ATA DISK drive <4>hdc: LITE-ON LTR-24102B, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <6>hdb: 78177792 sectors (40027 MB) w/1819KiB Cache, CHS=77557/16/63, UDMA(100) <4>hdc: ATAPI 16X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) <6>Uniform CD-ROM driver Revision: 3.12
I think hdc should be ignored here, and instead you should have something like this further on: <6>scsi0 : SCSI host adapter emulation for IDE ATAPI devices <4> Vendor: IDE Model: DVD-ROM 16X Rev: 1.06 <4> Type: CD-ROM ANSI SCSI revision: 02 <4> Vendor: MITSUMI Model: CR-48X8TE Rev: 1.1E <4> Type: CD-ROM ANSI SCSI revision: 02 Look at the begining of that file for a line like this one: <4>Kernel command line: root=/dev/hdb6 hdc=ide-scsi hdd=ide-scsi vga=791 <4>ide_setup: hdc=ide-scsi <4>ide_setup: hdd=ide-scsi Check if the kernel is getting the correct command line.
Could the problem be in the following messages during boot ? <6>SCSI subsystem driver Revision: 1.00 <3>request_module[scsi_hostadapter]: Root fs not mounted <3>request_module[scsi_hostadapter]: Root fs not mounted
Perhaps :-? I get: <6>SCSI subsystem driver Revision: 1.00 <3>kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 <6>md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 -- Cheers, Carlos Robinson
Thanks Carlos for your reaction. It put me on the right track and now I have been able to solve the problem. The major issue was that, because of my usage of "loadlin", the parameter "hdX=ide-scsi" (where X=c in my case) should also be added by hand in the "loadlin parameter file" in the Windows partition.. I had only added it via YaST2 in the "appendline" for the bootloader configuration, but in that way it does not reach loadlin ! As a result, the ide-scsi emulation was NOT started. After having made that addition, the booting included the ide-scsi emulation all-right. And indeed, as you pointed out, the CD-drive is recognized as sr0 and NOT as sdc0 as is indicated in the documentation. After having done the appropriate settings for sr0 there was no problem anymore in mounting the writer. Bottom line, there are two flaws in the "IDE CD Writer" document from SuSE's Support Database : 1. The required manual action for loadlin users should be mentioned. 2. The mentioning of /dev/sdc0 should be replaced by /dev/sr0 That would save a lot of people a lot of nuisance (I believe).
Thanks again and kind regards,
------------------------------ Jan Elders Nuenen the Netherlands
The 03.01.02 at 15:13, Jan Elders wrote:
Thanks Carlos for your reaction.
Welcome!
The major issue was that, because of my usage of "loadlin", the parameter "hdX=ide-scsi" (where X=c in my case) should also be added by hand in the "loadlin parameter file" in the Windows partition.. I had only added it via YaST2 in the "appendline" for the bootloader configuration, but in that way it does not reach loadlin ! As a result, the ide-scsi emulation was NOT started.
I guessed something like that, but as I don't use loadlin I couldn't check :-)
And indeed, as you pointed out, the CD-drive is recognized as sr0 and NOT as sdc0 as is indicated in the documentation.
I did it that way following the advices in the "CD-Writing HOWTO" and the schily or xcdroast readmes - I'm not sure now. There are at least three types of devices for acessing the scsi drives, but I don't really know the differences. Let me see (they are documented in /usr/src/linux/Documentation/devices.txt): /dev/sg* (Mjr 21 char) generic SCSI device Some distros name these as sga, sgb, sgc... making a limit of 28 devices; but not suse, which uses numbers /dev/scd* (Mjr 11 blk) SCSI CD-ROMS /dev/sr* (Mjr 11 blk) The prefix /dev/sr (instead of /dev/scd) has been deprecated. /dev/sda (major 8) SCSI disk whole disk, numbers 0 to 15. /dev/sdq, (Mjr 65 blk) SCSI disk devices (16-31) as whole disks sdr... sdaf /dev/sdag..sdav (M66B) SCSI disk devices (32-47) as whole disks /dev/sdaw..sdbl (M67B) SCSI disk devices (48-63) as whole disks /dev/sdbm..sdcb (M68B) Idem 64-79 /dev/sdcc..sdcr (M69B) Idem 80-95 /dev/sdcs..sddh (M70B) Idem 96-11 /dev/sddi..sddx (M71B) Idem 112-127 And more - till "sdiv" - I got tired ;-) Thus /dev/sdcc is 81st SCSI disk whole disk Numbers are used for partitions (like /dev/sdcc1) with a limit of 15 /dev/st0 (major 9) First SCSI tape, mode 0 /dev/st0l (major 9) First SCSI tape, mode 1 /dev/st0m (9 char) First SCSI tape, mode 2 /dev/st0a (9) First SCSI tape, mode 3 /dev/nst0 (9) First SCSI tape, mode 0, no rewind /dev/nst0l (9) First SCSI tape, mode 1, no rewind /dev/nst0m (9) First SCSI tape, mode 2, no rewind /dev/nst0a (9) First SCSI tape, mode 3, no rewind /dev/sch0 (86 char) SCSI media changers So... we have both to change to scd, not sr, and certainly not sdc
Bottom line, there are two flaws in the "IDE CD Writer" document from SuSE's Support Database : 1. The required manual action for loadlin users should be mentioned.
It wouldn't harm :-)
2. The mentioning of /dev/sdc0 should be replaced by /dev/sr0 That would save a lot of people a lot of nuisance (I believe).
Er... actually, they mention both scd0 and sdc0 - look up the underscore mark (__) below :-) +++Support knowledgebase (tbraza_ide_brenner) Due to the SCSI emulation, the kernel does not recognize the CD drive as an IDE device (which is therefore no longer known as /dev/hdc but as __/dev/sdc0__). During the installation, a link will be automatically created letting the system know that the CD drive (at this stage CD writers are still viewed as such) is located at /dev/hdc. However, the CD drive icons on the KDE desktop point to /dev/cdrom -- not to the CD drive or CD writer, but to nowhere. To change this, proceed as follows: Enter the following command in the terminal: ln -sf __/dev/scd0__ /dev/cdrecorder ++- I believe there is an email for documentation typos :-?
Thanks again and kind regards,
Welcome again :-) -- Cheers, Carlos Robinson
At 03-01-03, Carlos E. R. wrote: // CUT
And indeed, as you pointed out, the CD-drive is recognized as sr0 and NOT as sdc0 as is indicated in the documentation.
I did it that way following the advices in the "CD-Writing HOWTO" and the schily or xcdroast readmes - I'm not sure now. There are at least three types of devices for acessing the scsi drives, but I don't really know the differences.
Let me see (they are documented in /usr/src/linux/Documentation/devices.txt):
/dev/sg* (Mjr 21 char) generic SCSI device Some distros name these as sga, sgb, sgc... making a limit of 28 devices; but not suse, which uses numbers /dev/scd* (Mjr 11 blk) SCSI CD-ROMS /dev/sr* (Mjr 11 blk) The prefix /dev/sr (instead of /dev/scd) has been deprecated. /dev/sda (major 8) SCSI disk whole disk, numbers 0 to 15. /dev/sdq, (Mjr 65 blk) SCSI disk devices (16-31) as whole disks sdr... sdaf /dev/sdag..sdav (M66B) SCSI disk devices (32-47) as whole disks /dev/sdaw..sdbl (M67B) SCSI disk devices (48-63) as whole disks /dev/sdbm..sdcb (M68B) Idem 64-79 /dev/sdcc..sdcr (M69B) Idem 80-95 /dev/sdcs..sddh (M70B) Idem 96-11 /dev/sddi..sddx (M71B) Idem 112-127 And more - till "sdiv" - I got tired ;-) Thus /dev/sdcc is 81st SCSI disk whole disk Numbers are used for partitions (like /dev/sdcc1) with a limit of 15 /dev/st0 (major 9) First SCSI tape, mode 0 /dev/st0l (major 9) First SCSI tape, mode 1 /dev/st0m (9 char) First SCSI tape, mode 2 /dev/st0a (9) First SCSI tape, mode 3 /dev/nst0 (9) First SCSI tape, mode 0, no rewind /dev/nst0l (9) First SCSI tape, mode 1, no rewind /dev/nst0m (9) First SCSI tape, mode 2, no rewind /dev/nst0a (9) First SCSI tape, mode 3, no rewind
/dev/sch0 (86 char) SCSI media changers
So... we have both to change to scd, not sr, and certainly not sdc
Well, I tried scd during my struggles to get things working, but that was not leading to anything ! Only sr does. As far as I can judge we have no choice because SuSE's kernel seems to link hdc to sr0; see excerpt from boot log below : <6>scsi0 : SCSI host adapter emulation for IDE ATAPI devices <4> Vendor: LITE-ON Model: LTR-24102B Rev: 5S0D <4> Type: CD-ROM ANSI SCSI revision: 02 <4>Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 <4>sr0: scsi3-mmc drive: 239x/40x writer cd/rw xa/form2 cdda tray <6>Uniform CD-ROM driver Revision: 3.12 I don't think it is possible to influence this linking. Right ?
Bottom line, there are two flaws in the "IDE CD Writer" document from SuSE's Support Database : 1. The required manual action for loadlin users should be mentioned.
It wouldn't harm :-)
2. The mentioning of /dev/sdc0 should be replaced by /dev/sr0 That would save a lot of people a lot of nuisance (I believe).
Er... actually, they mention both scd0 and sdc0 - look up the underscore mark (__) below :-)
+++Support knowledgebase (tbraza_ide_brenner) Due to the SCSI emulation, the kernel does not recognize the CD drive as an IDE device (which is therefore no longer known as /dev/hdc but as __/dev/sdc0__). During the installation, a link will be automatically created letting the system know that the CD drive (at this stage CD writers are still viewed as such) is located at /dev/hdc. However, the CD drive icons on the KDE desktop point to /dev/cdrom -- not to the CD drive or CD writer, but to nowhere. To change this, proceed as follows: Enter the following command in the terminal:
ln -sf __/dev/scd0__ /dev/cdrecorder ++- I believe there is an email for documentation typos :-?
Yes, I would expect so too, but I haven't been able to find it. :-( // CUT ------------------------------ Jan Elders Nuenen the Netherlands
By the way, don't send as html and text: you are lucky the mail list server removed the html part, or you'd be roasted alive! :-p (I got the html in the email you sent me directly) The 03.01.04 at 11:37, Jan Elders wrote:
So... we have both to change to scd, not sr, and certainly not sdc
Well, I tried scd during my struggles to get things working, but that was not leading to anything ! Only sr does.
Mmm, I don't know yet. I have changed my links to scd, and apparently, it works. The important thing is this: cer@nimrodel:~> l /dev/scd1 /dev/sr1 brw------- 1 cer disk 11, 1 2002-09-09 22:24 /dev/scd1 brw------- 1 cer disk 11, 1 2002-09-09 22:24 /dev/sr1 Notice the 11, 1 (major, minor)? That means that even with different names, the driver is the same one.
As far as I can judge we have no choice because SuSE's kernel seems to link hdc to sr0; see excerpt from boot log below : <6>scsi0 : SCSI host adapter emulation for IDE ATAPI devices <4> Vendor: LITE-ON Model: LTR-24102B Rev: 5S0D <4> Type: CD-ROM ANSI SCSI revision: 02 <4>Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 <4>sr0: scsi3-mmc drive: 239x/40x writer cd/rw xa/form2 cdda tray <6>Uniform CD-ROM driver Revision: 3.12 I don't think it is possible to influence this linking. Right ?
Don't worry for now, if it works for you use whichever one you like :-) Only keep it in mind somewhere, that it may change in some near future.
I believe there is an email for documentation typos :-?
Yes, I would expect so too, but I haven't been able to find it. :-(
I found it once, but don't remember where. [...] I found it: +++ CUT Errata in the SuSE Linux 8.1 Documentation Support knowledgebase (errata-81-d) Applies to SuSE Linux: Version 8.1 This WWW page provides a list of the bugs and printing errors found in the SuSE Linux 8.1 documentation. If you find further errors in the manuals, please contact our documentation team via an e-mail to documentation@suse.de. ++- CUT I don't know if this applies to erratas in the sdb, but it could be. Maybe someone from suse is reading this and can enlighten us? If they are not on holidays :-) -- Cheers, Carlos Robinson
At 04-01-03, Carlos E. R. wrote:
By the way, don't send as html and text: you are lucky the mail list server removed the html part, or you'd be roasted alive! :-p
OK thanks for the advice. (I'm rather new to this)
So... we have both to change to scd, not sr, and certainly not sdc
Well, I tried scd during my struggles to get things working, but that was not leading to anything ! Only sr does.
Mmm, I don't know yet. I have changed my links to scd, and apparently, it works. The important thing is this:
cer@nimrodel:~> l /dev/scd1 /dev/sr1 brw------- 1 cer disk 11, 1 2002-09-09 22:24 /dev/scd1 brw------- 1 cer disk 11, 1 2002-09-09 22:24 /dev/sr1
Notice the 11, 1 (major, minor)? That means that even with different names, the driver is the same one.
You lost me here. This is byond my Linux knowledge. ;-(
I believe there is an email for documentation typos :-?
Yes, I would expect so too, but I haven't been able to find it. :-(
I found it once, but don't remember where. [...] I found it:
+++ CUT Errata in the SuSE Linux 8.1 Documentation
Support knowledgebase (errata-81-d) Applies to
SuSE Linux: Version 8.1
This WWW page provides a list of the bugs and printing errors found in the SuSE Linux 8.1 documentation. If you find further errors in the manuals, please contact our documentation team via an e-mail to documentation@suse.de. ++- CUT
I don't know if this applies to erratas in the sdb, but it could be. Maybe someone from suse is reading this and can enlighten us? If they are not on holidays :-)
Anyway, I'll report to that mailbox. Thanks again. ------------------------------ Jan Elders Nuenen the Netherlands
The 03.01.05 at 22:50, Jan Elders wrote:
Notice the 11, 1 (major, minor)? That means that even with different names, the driver is the same one.
You lost me here. This is byond my Linux knowledge. ;-(
Don't assume I know much more! :-) We could say the major is an index to the software driver, and the minor indicates the device. Somewhere else the kernel will know that a write to a device with such a major number will have to be handled by such driver. The driver itself will differentiate the several devices it handles based on the minor number. So, what I know is that the software driver for the sr and scd devices is the same one, that's all - in theory, at least :-) -- Cheers, Carlos Robinson
participants (2)
-
Carlos E. R. -
Jan Elders