Click to See Complete Forum and Search --> : SCSI burners not detected.


Antipode
02-17-2004, 07:29 PM
I can't mount, or even detect, my SCSI burners whatsoever. I just got them yesterday, and have read pretty much everything possible, but all I come up with are IDE-SCSI emulation answers. I have these plugged into an Adaptec 2930 SCSI card, which gets detected via the aic7xxx module just fine... yet running a test to find the burners only yields the following from cdrecord -scanbus
[root@crono scsi]# cdrecord -scanbus
Cdrecord-Clone 2.01a23 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

I'm running a 2.6.3-rc3 kernel. My kernel is compiled properly to the best of my knowledge, with the modules for aic7xxx (the card itself), CD-ROM, and generic (which is apparently used for burners?). This being my first attempt with SCSI hardware, it took me a while before I realized about termination. The last drive on the cable is terminated via the jumper in the back, but I've seen several other setups as well. The card is the other end of the chain, obviously, which self-terminates.

As for assigning each device an ID, I see no way of doing so. I've seen diagrams where HDDs have a number of sorts that can be changed on the back, but these don't on the burners. I hate to noob up the place with what is probably a simple fix, but I'm stumped and all of my manuals for the card and burners are for Windows, so I'm SOL there.

mdwatts
02-18-2004, 12:26 PM
Some of the JL forum search results for 'cannot open /dev/pg scsi' (http://justlinux.com/forum/search.php?s=&action=showresults&searchid=886905&sortby=lastpost&sortorder=descending). Changing the search criteria will find loads more since it's a very popular error message posted here.

Did you include ALL the required scsi support including cdrom's when compiling the kernel?

michaelk
02-19-2004, 10:27 AM
When the SCSI controller BIOS scans the bus it should list each device by SCSI ID and device name. There should be a jumper block similar to hard drives to configure SCSI IDs. What kind of drives are they?

BTW what distro are you running?

Make sure the SCSI modules are loading.
Check the output of dmesg to see of the OS is detecting the drives.
If everything is loading the following will display all SCSI devices.
cat /proc/scsi/scsi

banzaikai
02-20-2004, 07:42 PM
Howdy.


from: antipode
I'm running a 2.6.3-rc3 kernel. My kernel is compiled properly to the best of my knowledge, with the modules for aic7xxx (the card itself), CD-ROM, and generic (which is apparently used for burners?)


Actually, there's more to SCSI than that. You'll need the following (/sbin/lsmod to check if they're loaded):
Module Size Used by Tainted: P
sr_mod 16632 0 (autoclean)
cdrom 32128 0 (autoclean) [sr_mod]
aic7xxx 133248 0
sd_mod 12828 2
scsi_mod 107548 4 [sr_mod usb-storage aic7xxx sd_mod]

Me thinks the "sr_mod" means "scsi removable", and the "sd_mod" means "scsi disk". Since the cdroms are also considered to be scsi removable, ya might want that bugger in there. Note: the links listed after scsi_mod pointing to what it's hooked to - in my case, sr_mod, usb-storage, aic7xxx, and sd_mod.


As for assigning each device an ID, I see no way of doing so. I've seen diagrams where HDDs have a number of sorts that can be changed on the back, but these don't on the burners.


Look again. ALL scsi devices have ID jumpers. Even my Zip has a 5/6 switch (my other devices have the full 0-7 settings). However, not all are jumpers! My scanner (Astra 600S) has a switch wheel that points to the ID, and my EZ-Flyer uses a flash-write technique where you hold the eject button down on power-up, count the number of flashes until it's the ID you want, then cycle the power. Everything else has jumpers. They'll be labeled "ID0, ID1, ID2, and on SCSI wide devices, ID3. These stand for the bits of the address. If no jumpers, then the address is 0. If ID0 is set, then it's 1, and follows binary like so:
ID0 set = add 1
ID1 set = add 2
ID2 set = add 4
ID3 set = add 8

So, if you want your first cd set to address 2, set ID1. To put the second cd at 3, then set ID0 and ID1 (1+2 = 3).
Of course, if you see a small wheel in there, then just stick a small screwdriver in it and rotate the arrow to 2 or 3. Why not 0 or 1? Most BIOSs prefer that bootable HDs sit at those addresses, but there's nothing stopping you from using them (my cd is at 3, my scanner at 4, my zip at 5, and my ezflyer is at 6 - which leaves 0-2 for any HDs I have lying around).

michaelk also has it right. The scsi card should give you a boot description of whatever it finds on the bus. If you've got an address conflict, it should show up or give you some weird displays (sometimes, it'll ID a drive on all addresses if it's set to the same ID as the controller, usually 7).

Hope this helps...

banzai "scsi-san" kai