Ok, this makes sense. However, I seem to have the cd and cdr assigned to the same device /dev/hdc. I have posted an earlier mail a couple of minutes ago with a little more detail. Cheers, Curtis On Sunday 02 September 2001 03:47 pm, Anders Johansson wrote:

Hi,

The fstab entry has no effect on koncd, since that works directly on the device.

And you're using /dev/hdc! I think this is the problem. You should be using scsi emulation, shouldn't you. add "hdc=ide-scsi" to lilo.conf, and modprobe ide-scsi to some bootup file like /etc/rc.d/boot.local

regards Anders

On Sunday 02 September 2001 21.13, Curtis Rey wrote:

...

I can't seem to get the cdrw to be recognized by KOnCD.

I get several error massages. I will inlcuded them here:

Sep 2 13:43:51 cb952536-a kernel: pg: pg version 1.02, major 97 Sep 2 13:43:51 cb952536-a modprobe: modprobe: Can't locate module paride_protocol Sep 2 13:43:51 cb952536-a kernel: pg0: Autoprobe failed Sep 2 13:43:51 cb952536-a kernel: pg: No ATAPI device detected Sep 2 13:43:51 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Sep 2 13:43:51 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Sep 2 13:43:51 cb952536-a kernel: paride: version 1.06 installed (parport) Sep 2 13:43:51 cb952536-a kernel: pg: pg version 1.02, major 97 Sep 2 13:43:51 cb952536-a modprobe: modprobe: Can't locate module paride_protocol Sep 2 13:43:51 cb952536-a kernel: pg0: Autoprobe failed Sep 2 13:43:51 cb952536-a kernel: pg: No ATAPI device detected Sep 2 13:43:51 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Sep 2 13:43:51 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Sep 2 13:43:51 cb952536-a kernel: paride: version 1.06 installed (parport) Sep 2 13:43:51 cb952536-a kernel: pg: pg version 1.02, major 97 Sep 2 13:43:51 cb952536-a modprobe: modprobe: Can't locate module paride_protocol Sep 2 13:43:51 cb952536-a kernel: pg0: Autoprobe failed Sep 2 13:43:51 cb952536-a kernel: pg: No ATAPI device detected Sep 2 13:43:51 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Sep 2 13:43:51 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Sep 2 13:43:51 cb952536-a kernel: paride: version 1.06 installed (parport) Sep 2 13:43:51 cb952536-a kernel: pg: pg version 1.02, major 97 Sep 2 13:43:51 cb952536-a modprobe: modprobe: Can't locate module paride_protocol Sep 2 13:43:51 cb952536-a kernel: pg0: Autoprobe failed Sep 2 13:43:51 cb952536-a kernel: pg: No ATAPI device detected Sep 2 13:43:51 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Sep 2 13:43:51 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Sep 2 13:45:30 cb952536-a kernel: paride: version 1.06 installed (parport) Sep 2 13:45:30 cb952536-a kernel: pg: pg version 1.02, major 97 Sep 2 13:45:30 cb952536-a modprobe: modprobe: Can't locate module paride_protocol Sep 2 13:45:30 cb952536-a kernel: pg0: Autoprobe failed Sep 2 13:45:30 cb952536-a kernel: pg: No ATAPI device detected Sep 2 13:45:30 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Sep 2 13:45:30 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Sep 2 13:45:30 cb952536-a kernel: paride: version 1.06 installed (parport) Sep 2 13:45:30 cb952536-a kernel: pg: pg version 1.02, major 97 Sep 2 13:45:30 cb952536-a modprobe: modprobe: Can't locate module paride_protocol Sep 2 13:45:30 cb952536-a kernel: pg0: Autoprobe failed Sep 2 13:45:30 cb952536-a kernel: pg: No ATAPI device detected Sep 2 13:45:30 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Sep 2 13:45:30 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Sep 2 13:45:30 cb952536-a kernel: paride: version 1.06 installed (parport) Sep 2 13:45:30 cb952536-a kernel: pg: pg version 1.02, major 97 Sep 2 13:45:30 cb952536-a modprobe: modprobe: Can't locate module paride_protocol Sep 2 13:45:30 cb952536-a kernel: pg0: Autoprobe failed Sep 2 13:45:30 cb952536-a kernel: pg: No ATAPI device detected Sep 2 13:45:30 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Sep 2 13:45:30 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Sep 2 13:45:30 cb952536-a kernel: paride: version 1.06 installed (parport) Sep 2 13:45:30 cb952536-a kernel: pg: pg version 1.02, major 97 Sep 2 13:45:31 cb952536-a modprobe: modprobe: Can't locate module paride_protocol Sep 2 13:45:31 cb952536-a kernel: pg0: Autoprobe failed Sep 2 13:45:31 cb952536-a kernel: pg: No ATAPI device detected Sep 2 13:45:31 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Sep 2 13:45:31 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Sep 2 13:47:41 cb952536-a kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Sep 2 13:47:41 cb952536-a kernel: hdc: command error: error=0x50 Sep 2 13:47:41 cb952536-a kernel: end_request: I/O error, dev 16:00 (hdc), sector 0 Sep 2 13:47:41 cb952536-a kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Sep 2 13:47:41 cb952536-a kernel: hdc: command error: error=0x50 Sep 2 13:47:41 cb952536-a kernel: end_request: I/O error, dev 16:00 (hdc), sector 0 Sep 2 13:47:41 cb952536-a kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Sep 2 13:47:41 cb952536-a kernel: hdc: command error: error=0x50 Sep 2 13:47:41 cb952536-a kernel: end_request: I/O error, dev 16:00 (hdc), sector 0 Sep 2 13:47:41 cb952536-a kernel: FAT bread failed Sep 2 13:47:41 cb952536-a kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Sep 2 13:47:41 cb952536-a kernel: hdc: command error: error=0x50 Sep 2 13:47:41 cb952536-a kernel: end_request: I/O error, dev 16:00 (hdc), sector 128 Sep 2 13:47:41 cb952536-a kernel: read_super_block: unable to read superblock on dev 16:00 Sep 2 13:47:41 cb952536-a kernel: read_old_super_block: try to find super block in old location Sep 2 13:47:41 cb952536-a kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Sep 2 13:47:41 cb952536-a kernel: hdc: command error: error=0x50 Sep 2 13:47:41 cb952536-a kernel: end_request: I/O error, dev 16:00 (hdc), sector 16 Sep 2 13:47:41 cb952536-a kernel: read_old_super_block: unable to read superblock on dev 16:00 Sep 2 13:47:41 cb952536-a kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Sep 2 13:47:41 cb952536-a kernel: hdc: command error: error=0x50 Sep 2 13:47:41 cb952536-a kernel: end_request: I/O error, dev 16:00 (hdc), sector 0 Sep 2 13:47:41 cb952536-a kernel: FAT bread failed Sep 2 13:47:41 cb952536-a kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Sep 2 13:47:41 cb952536-a kernel: hdc: command error: error=0x50 Sep 2 13:47:41 cb952536-a kernel: end_request: I/O error, dev 16:00 (hdc), sector 0 Sep 2 13:47:41 cb952536-a kernel: FAT bread failed Sep 2 13:47:41 cb952536-a kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Sep 2 13:47:41 cb952536-a kernel: hdc: command error: error=0x50 Sep 2 13:47:41 cb952536-a kernel: end_request: I/O error, dev 16:00 (hdc), sector 128 Sep 2 13:47:41 cb952536-a kernel: read_super_block: unable to read superblock on dev 16:00 Sep 2 13:47:41 cb952536-a kernel: read_old_super_block: try to find super block in old location Sep 2 13:47:41 cb952536-a kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Sep 2 13:47:41 cb952536-a kernel: hdc: command error: error=0x50 Sep 2 13:47:41 cb952536-a kernel: end_request: I/O error, dev 16:00 (hdc), sector 16 Sep 2 13:47:41 cb952536-a kernel: read_old_super_block: unable to read superblock on dev 16:00

I went into fstab and changed the parameters for the cdrecorder as such:

/dev/hdb2 / ext2 defaults 1 1 /dev/cdrecorder /media/cdrecorder auto rw,noauto,user,exec 0 0 # the line above previously read "ro,noauto,user,exec 00" /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 devpts /dev/pts devpts defaults 0 0 /dev/hdb3 /home ext2 defaults 1 2 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/hde1 /opt2 ext2 defaults 1 2 proc /proc proc defaults 0 0 /dev/hdb4 /usr ext2 defaults 1 2 /dev/hda1 /windows/C vfat noauto,user 0 0 /dev/hda5 /windows/D vfat noauto,user 0 0 /dev/hde5 /windows/E vfat noauto,user 0 0 /dev/hde6 /windows/F vfat noauto,user 0 0 /dev/hde7 /windows/G vfat noauto,user 0 0 /dev/hdb1 swap swap pri=42 0 0 /dev/sda4 /media/zip auto noauto,user,sync 0 0

It is a Samsung CDR/RW model SW-208 8x4x32 speed.

Any help will be "Greatly" appreciated. TIA Curtis :-/

I don't see what the paride module has to do with anything. This CD-RW isn't connected to the parallell port is it? I think those messages are unrelated. If cdrecord -scanbus can see the drive, you should be able to work with it. Does koncd give you any messages? Don't you see the drive when you go into setup? If not, do you have proper permissions on the device it was assigned? Anders On Monday 03 September 2001 00.59, Curtis Rey wrote:

Well, went to the SuSE db online and followed some things as well as the suggestions from the list. Here's what I've done so far and the results

I appended lilo with hdc=ide-scsi. then I gave the command after boot: insmod.static ide-scsi Oh, and I read the boot.msg and found this"On Sunday 02 September 2001 02:13 <4>hda: Maxtor 91366U4, ATA DISK drive <4>hdb: WDC AC310200R, ATA DISK drive <4>hdc: SAMSUNG CD-R/RW DRIVE SW-208B, ATAPI CD/DVD-ROM drive <4>hdd: CD-ROM Drive/F5B, ATAPI CD/DVD-ROM drive <4>hde: Maxtor 2B020H1, ATA DISK drive

And then ran command: (which shows the cdrecorder is recognized)

bash-2.05# cdrecord -scanbus Cdrecord 1.9 (i686-suse-linux) Copyright (C) 1995-2000 Jörg Schilling Linux sg driver version: 3.1.17 Using libscg version 'schily-0.1' scsibus0: 0,0,0 0) * 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) 'IOMEGA ' 'ZIP 100 ' 'N.38' Removable Disk 0,6,0 6) * 0,7,0 7) * scsibus1: 1,0,0 100) 'SAMSUNG ' 'CD-R/RW SW-208B ' 'BS01' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) *

But the sys console gave some messages that were encouraging, until I ran KOnCD and a mod fail message came - the messages are as follows:

Sep 2 17:31:42 cb952536-a kernel: Vendor: SAMSUNG Model: CD-R/RW SW-208B Rev: BS01 Sep 2 17:31:42 cb952536-a kernel: Type: CD-ROM ANSI SCSI revision: 02 Sep 2 17:31:42 cb952536-a kernel: Detected scsi CD-ROM sr0 at scsi1, channel 0, id 0, lun 0 Sep 2 17:31:42 cb952536-a kernel: sr0: scsi3-mmc drive: 8x/32x writer cd/rw xa/form2 cdda tray Sep 2 17:37:45 cb952536-a kernel: paride: version 1.06 installed (parport) Sep 2 17:37:45 cb952536-a kernel: pg: pg version 1.02, major 97 Sep 2 17:37:45 cb952536-a modprobe: modprobe: Can't locate module paride_protocol Sep 2 17:37:45 cb952536-a kernel: pg0: Autoprobe failed Sep 2 17:37:45 cb952536-a kernel: pg: No ATAPI device detected Sep 2 17:37:45 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Sep 2 17:37:45 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Sep 2 17:37:45 cb952536-a kernel: paride: version 1.06 installed (parport) Sep 2 17:37:45 cb952536-a kernel: pg: pg version 1.02, major 97 Sep 2 17:37:45 cb952536-a modprobe: modprobe: Can't locate module paride_protocol Sep 2 17:37:45 cb952536-a kernel: pg0: Autoprobe failed Sep 2 17:37:45 cb952536-a kernel: pg: No ATAPI device detected Sep 2 17:37:45 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Sep 2 17:37:45 cb952536-a insmod: /lib/modules/2.4.4-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Sep 2 17:37:45 cb952536-a kernel: paride: version 1.06 installed (parport)

According to the SuSE online article I should further append lilo for the Max_scsi_lun to be 1.

I have given the command ln -s /dev/hdd /dev/cdrom and will also append the lilo for the max scsi luns. I will reboot and report the results. If anyone has any further suggestions, please feel free to submit (for my self and any others that my have this problem - I will submit a summary (if successful) to SuSE and the Portal for further references

TIA and wish me luck. Curtis

On Monday 03 September 2001 01.16, Curtis Rey wrote:

Your absolutely right (as usual :) ). Paride has nothing to do with it.

I'm frequently wrong :) See my debacle with Tim Butler for a recent example.

now I have to manually load the module with insmod.static "ide-scsi" and then KOnCD sees it (getting very close - :) ). I have appended the modules.conf file to change the scsi line from off to ide-scsi. How do I get the ide-scsi module to load automatically at boot time?

TIA again. Curits

I'm sure there are better ways, but I just put a 'modprobe ide-scsi' line in /etc/rc.d/boot.local Anders

You see, I am the only person in the world who can't configure ide-scsi in 7.2 My scsibus1 is absent. Peter On Sunday 02 September 2001 22:59, Curtis Rey wrote:

Well, went to the SuSE db online and followed some things as well as the suggestions from the list. Here's what I've done so far and the results

bash-2.05# cdrecord -scanbus Cdrecord 1.9 (i686-suse-linux) Copyright (C) 1995-2000 Jörg Schilling Linux sg driver version: 3.1.17 Using libscg version 'schily-0.1' scsibus0: 0,0,0 0) * 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) 'IOMEGA ' 'ZIP 100 ' 'N.38' Removable Disk 0,6,0 6) * 0,7,0 7) * scsibus1: 1,0,0 100) 'SAMSUNG ' 'CD-R/RW SW-208B ' 'BS01' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) *

Hi, Here's what I had to do to be able to use my CD-R in koncd. I first added the user to group disk, and then chmod g+w /dev/sg* Anders On Tuesday 04 September 2001 11.52, Kevin Donnelly wrote:

Hi Curtis

I had no luck at all getting the KOnCD with 7.2 to work. Rather than faff about with it, I used XCDRoast instead.

Best wishes

Kevin

On Sunday 02 September 2001 19:13, Curtis Rey wrote:

...

I can't seem to get the cdrw to be recognized by KOnCD.