SUSE 10.0 scsi device missing
 

I just did a fresh install of SUSE 10.0 and it didn't install scsi for my jaz scsi card. :cry: There isn't a scsi in /dev at all. There was one when I had SUSE 9 and when I've had Mandrake on the machine. (Under 9 It recognized my jaz, zip, and Bernoulli drives, but without scsi in dev I can't get any sd devices!:mad: )Any ideas on how to get the scsi device there? Thanks much! :)

Any idea on the make / model of the SCSI controller? Is this the controller that came with the drive?

Look at the output of the console command lspci. Post the line that references anything about a SCSI controller. If you have Iomega card that was sold with the drive I think it is an Adaptec controller.

Once we know the controller we can see if its module is loading via the lsmod command.

The output of the lspci command has nothing about scsi. When booting, the scsi announces itself as "Jaz Jet pci Ultra SCSI." It is the original scsi controller for the Jaz drive. The module does not seem to be loading. The only references to scsi from lsmod is the following:

scsi_mod 142952 2 libata,sd_mod

and following the references to other modules:

sd_mod 23808 0
libata 55428 1 ata_piix
ata_piix 13956 0

Is this any help with figuring out my situation? I can boot into Windows and get that info on the scsi card, as well. I did boot into Windows and I have the Advansys SCSI Host Adapter.

On another path, I reinstalled the devs package to get scsi and sd back in /dev. I checked and they were there, rebooted, and they were gone. So far the only reference to this behavior is udev. It seems that udev will dynamically remove and install device driver for removable equipment (e.g. usb/firewire devices). It seems that since the module isn't loading, it is removing scsi. But I may just be heading down the wrong path there.

If any more information would be helpful, please let me know. This is driving me nuts. Thanks for your help.

So you have the Advanced Systems SCSI controller. Try load the module advansys:
modprobe advansys

This might not work because I saw a SuSE note where the module is broken in the 2.6.7 kernel.
http://www.users.bigpond.com/vkelim/...es/node29.html

howto:
http://www.faqs.org/docs/Linux-HOWTO...ive-HOWTO.html

That's okay, SuSE 10.0 doesn't use 2.6.7 it uses 2.6.13-15, And the 10.1 will use 2.6.15.3 or 2.6.16(we will see when it hits release.) That probably applies to 9.2, if memory serves, not SuSE 10.0.

Otherwise you could always recompile the kernel module and do a kernel install.

I may have to do a recompile of the kernel, because modprobe advansys say, in essence that the module isn't there. michaelk, the link to the broken advansys says that it is with non-Intel processors but mine is an Intel Pentium 4 2.6 GHz processor. Of course, that doesn't say that a broken driver still isn't the problem. I'll have to check into the links there and the HOWTO to see if anything there will help. Thanks, I'll let you know if I get it going.:)

Well, I ended up finding info on Novell's site about enabling generic scsi, and did that. I also enabled boot.scsidev on boot in runlevel setup from YaST. Now when I run lspci the scsi card is listed as:
01:07.0 SCSI storage controller: Advanced System Products, Inc ABP940-U / ABP960 -U (rev 03)
In my boot log I now see "Scanning SCSI devices and filling /dev/scsi/ done" but /dev/scsi is empty. /var/log/warn has "Feb 7 07:50:00 <machinename> kernel: aha152x: invalid module params io=0x340, irq=10,scsiid=7,reconnect=1,parity=1,sync=0,delay=1000,exttrans=0"

Using YaST Hardware Information, resources have now appeared under ASC1300 SCSI adapter. The irq listed here is 11. Curiouser and curiouser.

I loaded another scsi card I had, with an adapter for the JAZ drive and now the drives are all there, so it is confirmed that somewhere between SUSE 9.0 and 10.0 support for advansys drivers have been removed. You would think that my problems were over now, but no! I can't seem to get all of the drives to mount other than manually. I've gotten the Bernoulli 150 and JAZ to mount when there is a fat16 formatted drive in the drive, but not when a drive I reformatted as a Linux drive unless I manually specify using the mount command. Putting ext3 as the filesystem in fstab doesn't seem to work. I've also modified fstab several ways and can't get the zip drive to mount at all, other than manually. It doesn't seem to matter whether it has a fat16 or ext3 formatted disk, it can't be mounted at startup using fstab. I've even tried using subfs in automount to get the drives to mount, but it isn't working either. Here is my latest fstab attempt (I know it isn't optimal, but I'm still learning about submount.):

BTW, just stating the obvious the noauto option in fstab means you do not want to automatically mount the filesystem boot up.

If that doesn't work you might have to include the SCSI modules in the initrd.

Don't worry about stating the obvious, it may not be so obvious to everyone. I didn't necessarily want the drives to load at boot. Previously in SUSE 9.0 they did, but had to be in the drives at boot to mount automatically at all. So not mounting at boot isn't a problem. They wouldn't mount unless I mounted them manually at a terminal as root. Now I believe that I've got it licked, though. Previously SUSE 9.0 automagically recognized when the Zip or Jaz was there and put a device link icon on the desktop, but for some reason SUSE 10.0 isn't doing that. I put the device link icons on the desktop and configured them, but then got an error that only root could mount the device whenever I clicked on the link. I had read instructions somewhere about submount that said not to use the "users" option, but apparently it is necessary. I added the "users" option to all three lines in fstab and now the disks will mount when I click on the icon (if there is a disk in the drive that is...) The only quirk I see now is my Jaz and Bernoulli won't eject when I right-click the icon and select eject. I can right-click and choose unmount and then press the button to eject though, so it isn't that big a deal. The lines in fstab as they not are:
I just wish I could get my Advansys card to work without compiling the kernel. Well when I have time I'll probably do that, but not just yet.