# dmesg | grep scsi request_module[scsi_hostadapter]: Root fs not mounted request_module[scsi_hostadapter]: Root fs not mounted scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.4 (scsi0:A:3): 10.000MB/s transfers (10.000MHz, offset 15) (scsi0:A:4): 10.000MB/s transfers (10.000MHz, offset 8) (scsi0:A:6): 10.000MB/s transfers (10.000MHz, offset 15) scsi0:A:6:0: Tagged Queuing enabled. Depth 253 Attached scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0 Attached scsi CD-ROM sr1 at scsi0, channel 0, id 4, lun 0 Attached scsi disk sda at scsi0, channel 0, id 6, lun 0 sr0: scsi-1 drive sr1: scsi3-mmc drive: 20x/20x writer cd/rw xa/form2 cdda tray Attached scsi generic sg2 at scsi0, channel 0, id 5, lun 0, type 6 # cdrecord -scanbus Cdrecord 1.11a05 (i686-suse-linux) Copyright (C) 1995-2001 Jörg Schilling Linux sg driver version: 3.1.20 Using libscg version 'schily-0.5' scsibus0: 0,0,0 0) * 0,1,0 1) * 0,2,0 2) * 0,3,0 3) 'PLEXTOR ' 'CD-ROM PX-40TS ' '1.05' Removable CD-ROM 0,4,0 4) 'PLEXTOR ' 'CD-R PX-W4220T' '1.04' Removable CD-ROM 0,5,0 5) 'Nikon ' 'LS-2000 ' '1.31' Removable Scanner 0,6,0 6) 'SEAGATE ' 'ST36530N ' '1444' Disk 0,7,0 7) * Chad Whitten wrote:
also what does dmesg | grep scsi show
here is my output chadwick@newton:~> dmesg | grep scsi scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.4 scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.4 (scsi0:A:4): 8.333MB/s transfers (8.333MHz, offset 31) (scsi0:A:6): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit) scsi0:A:6:0: Tagged Queuing enabled. Depth 253 (scsi1:A:6): 10.000MB/s transfers (10.000MHz, offset 15) Attached scsi disk sda at scsi0, channel 0, id 6, lun 0 Attached scsi CD-ROM sr0 at scsi0, channel 0, id 4, lun 0 Attached scsi CD-ROM sr1 at scsi1, channel 0, id 4, lun 0 Attached scsi CD-ROM sr2 at scsi1, channel 0, id 6, lun 0 sr0: scsi3-mmc drive: 16x/16x writer cd/rw xa/form2 cdda tray (scsi1:A:4): 20.000MB/s transfers (20.000MHz, offset 15) sr1: scsi3-mmc drive: 16x/16x xa/form2 cdda tray sr2: scsi-1 drive (scsi0:A:6:0): Locking max tag count at 128
i have two scsi cards (2940 and 19160) with a hard drive and cdrw on the 19160 and two cdroms on the 2940 as well as a scsi tape drive (external) on occasion.
On Thursday 04 April 2002 02:16 pm, you wrote:
then why do I get when I start xcdroast (sorry for the long mail):
kernel: paride: version 1.06 installed (parport) kernel: pg: pg version 1.02, major 97 modprobe: modprobe: Can't locate module paride_protocol kernel: pg0: Autoprobe failed kernel: pg: No ATAPI device detected insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed kernel: paride: version 1.06 installed (parport) kernel: pg: pg version 1.02, major 97 modprobe: modprobe: Can't locate module paride_protocol kernel: pg0: Autoprobe failed kernel: pg: No ATAPI device detected insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed kernel: paride: version 1.06 installed (parport) kernel: pg: pg version 1.02, major 97 modprobe: modprobe: Can't locate module paride_protocol kernel: pg0: Autoprobe failed kernel: pg: No ATAPI device detected insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed kernel: paride: version 1.06 installed (parport) kernel: pg: pg version 1.02, major 97 modprobe: modprobe: Can't locate module paride_protocol kernel: pg0: Autoprobe failed kernel: pg: No ATAPI device detected insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted insmod: /lib/modules/2.4.16-4GB/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed kernel: I/O error: dev 0b:00, sector 0 kernel: I/O error: dev 0b:00, sector 0 kernel: FAT: unable to read boot sector kernel: I/O error: dev 0b:00, sector 0 kernel: FAT: unable to read boot sector kernel: I/O error: dev 0b:00, sector 0 kernel: FAT: unable to read boot sector
Chad Whitten wrote:
well, your hard drive is gonna be /dev/sda (with partitions sda1, sda2, etc) your cdrom will be /dev/sr0 and your cdrw will be /dev/sr1 and i have no idea about the scanner
On Thursday 04 April 2002 01:58 pm, PR wrote:
scsi-card adaptec 2930 harddisk (scsi) address: 6 plextor 40ts (cdrom-scsi) address: 3 plextor 4220RW (cd-writer-scsi) address: 4 nikon coolscan ls2000 (scsi) address: 5
which is which it only appeared after running "scsidev" for the first time should I change links to my cdrom &writer? # ls -l /dev/scsi/ totaal 50 drwxr-xr-x 2 root root 351 apr 4 21:14 . drwxr-xr-x 19 root root 51551 apr 4 14:15 .. brw------- 1 root root 8, 0 apr 4 21:01 sdh0-0c0i6l0 brw------- 1 root root 8, 1 apr 4 21:01 sdh0-0c0i6l0p1 brw------- 1 root root 8, 5 apr 4 21:01 sdh0-0c0i6l0p5 brw------- 1 root root 8, 6 apr 4 21:01 sdh0-0c0i6l0p6 brw------- 1 root root 8, 7 apr 4 21:01 sdh0-0c0i6l0p7 crw------- 1 root root 21, 0 apr 4 21:01 sgh0-0c0i3l0 crw------- 1 root root 21, 1 apr 4 21:01 sgh0-0c0i4l0 crw------- 1 root root 21, 2 apr 4 21:01 sgh0-0c0i5l0 crw------- 1 root root 21, 3 apr 4 21:01 sgh0-0c0i6l0 br-------- 1 root root 11, 0 apr 4 21:01 srh0-0c0i3l0 br-------- 1 root root 11, 1 apr 4 21:01 srh0-0c0i4l0
which is which it only appeared after running "scsidev" for the first time should I change links to my cdrom &writer? # ls -l /dev/scsi/ totaal 50 drwxr-xr-x 2 root root 351 apr 4 21:14 . drwxr-xr-x 19 root root 51551 apr 4 14:15 .. brw------- 1 root root 8, 0 apr 4 21:01 sdh0-0c0i6l0 brw------- 1 root root 8, 1 apr 4 21:01 sdh0-0c0i6l0p1 brw------- 1 root root 8, 5 apr 4 21:01 sdh0-0c0i6l0p5 brw------- 1 root root 8, 6 apr 4 21:01 sdh0-0c0i6l0p6 brw------- 1 root root 8, 7 apr 4 21:01 sdh0-0c0i6l0p7 crw------- 1 root root 21, 0 apr 4 21:01 sgh0-0c0i3l0 crw------- 1 root root 21, 1 apr 4 21:01 sgh0-0c0i4l0 crw------- 1 root root 21, 2 apr 4 21:01 sgh0-0c0i5l0 crw------- 1 root root 21, 3 apr 4 21:01 sgh0-0c0i6l0 br-------- 1 root root 11, 0 apr 4 21:01 srh0-0c0i3l0 br-------- 1 root root 11, 1 apr 4 21:01 srh0-0c0i4l0
Isn't scsidev used only for devfs? If so and you are not using it doesn't the above means nothing? It would appear from the rest of your posts that you are not using devfs. I think you need to be carefull and start reading some manuals. I'm sure this list can provide you with a start of where to start reading. I've been using scsi for a long time and have never had a need to run that command. I'm not or ever have as yet used devfs so I may be incorrect in my assumption. But appears that you are running amock with your box and need to go back to the basics and regroup. No flame intended here, really. It's just my opinion. Regards Mark
participants (2)
-
Mark Hounschell
-
PR