On a SCSI system, is there a different place to look for USB block devices?
 

I have the 2.6.6 kernel. I compiled as much SCSI stuff in it as I could. I cannot link my FujiFinepix camera to /dev/sdd1, or for that matter, /dev/sd*. Indications are that the kernel is finding the hardware when I turn it on, but it says it can't locate the "modules." I assume that it's not talking about modules compiled along with the kernel build. I didn't compile anything SCSI as modules. They all went straight in.

Could there be a different device linking with my camera and I just don't know it? I tried a simple "df" but it shows me my SCSI hard drives and CDROM (when I mount it). Of course it won't show my camera as a SCSI mass storage device since I haven't found it to mount it.

(I am keeping reserved problems with my USB devices and the kernel. I saw that the 2.6.3 kernel had some problems with USB, but they were supposedly taken care of.)

That reminds me. The hardware is fine. When I was running my 2.4.2x kernel, I was able to connect to /dev/sdd1 quite sweetly. I went back and tried again, however, and I cannot. (2.4.20 is a backup kernel for me).

Also, my desktop computer is half Winsux. The XP applications find, connect, and download pix just fine.

/var/log/messages says the following:
May 24 23:13:25 harley -- MARK --
May 24 23:29:36 harley kernel: usb 2-1: new full speed USB device using address 2
May 24 23:29:37 harley usb.agent[1514]: ... no modules for USB product 4cb/11a/1000
May 24 23:29:37 harley kernel: scsi1 : SCSI emulation for USB Mass Storage devices

Is there any other place to look for a block device to mount my camera to?

Aerich the Rocket Scientist
Alexandria, VA

PS: On a side note, and maybe related... I have a Handspring Visor (like a palm pilot) that I USB to my computer too. I have tried running JPilot to control the data, but I cannot seem to HotLink the Visor to the computer. It just fails.

That's exactly what it's talking about; there are no other "modules" but loadable modules compiled along with the kernel build. That is what the term "modules" means.

Why are you assuming that it would be something else? Because you did not compile anything as modules? It would seem that the kernel is looking for loadable modules, however. Perhaps compiling everything in directly was not the best plan, especially when upgrading from a 2.4 series kernel. Don't forget, your initialization files haven't changed (modules.conf, for example, which is specifying modules to load which no longer exist) unless you changed them.

You might want to read lsscsi utility for Linux which explains quite a bit about how SCSI is set up under the new device system in the 2.6 kernel, and if you don't have the utility already installed, you can install it from there too.

Hope this helps.

Thanks for the suggestion. I will investigate the lsscsi utility later today when I get home from work. I have often wondered (over the many years) whether some apps and libraries don't assume (without directly ordering you to do it) that you are making modules out of some of your kernel options. Unfortunately, I've had more direct experience with needing to jam modules into my kernel build to actually get them to activate. For the 2.6.6 kernel, for example, I couldn't get my SCSI CDROM to work. I wanted the kernel option to be a "module" but that failed. In a fit of desperation, I included it into my kernel build and it works just fine.

Maybe this lsscsi utility (which I don't have yet) would allow me to keep the CDROM option as a module.

RE: module. Here's why I questioned the location of my "missing modules." The English language is such a powerful thing. Without specifically defining a word, the readers can interpret the writer's intent anyway they choose. Each option given in a kernel build is a "module," specifically designed to work with the kernel once it's built. And so, I have a SCSI mass storage "module" that I want to use with the 2.6.6 kernel. This "module" can be included within the kernel, in which case, it's an _embedded_ "module." Or, I can choose to keep it outside the kernel and usable, in which case, it's an _insertable_ "module."

I didn't mean the above paragraph as a lesson in Linux, but as an explanation of why I can't understand what my /var/log/messages means. (I was the only engineer in all my classes that did VERY well in grammar class...)

I *think* that what is happening is that I need to include something more, not from the SCSI folder and not from the USB folder to finish my build and allow me to use my camera with Linux again. Hopefully lsscsi will educate me on that!

Thanks again for your help

Aerich the Rocket Scientist
Alexandria, VA

Well, OK (and thanks for the lesson; I'm always happy to learn), but who ever really talks about "embedded modules"? Either we talk about loadable modules (the term used in the kernel option), or we have things directly compiled into the kernel.

I recognize that most likely the proper technical term for ALSA's current status with regards to the 2.6 kernels, or the status of ide-cd with regards to same would now be "embedded modules", but if you trawl the web trying to find out how to use or enable these modules, you'll more likely see everyone saying that "this module/functionality/whatever is now part of the kernel," or "this is now directly compiled into the kernel," either of which statements would lead an ordinary speaker of English (or me, at least), to consider the term "module" to be obsolete for these items (because that was their designation before they underwent a major status change).

But actually, it's good to know what the proper term is, since saying "blah blah blah is now directly compiled into the kernel" is a bit long-winded, even for me.

:)

I took your advice and installed lsscsi. It's a great little tool! Now... how am I supposed to interpret the following? I see my camera under usb-storage.

ae@harley:/$ lsscsi
[0:0:0:0] disk SEAGATE ST318451LW 0003 /dev/sda
[0:0:1:0] disk SEAGATE ST318416W 0010 /dev/sdb
[0:0:5:0] disk IOMEGA ZIP 100 J.03 /dev/sdc
[0:0:6:0] cd/dvd TEAC CD-ROM CD-532S 1.0A /dev/sr0
ae@harley:/$
ae@harley:/$ lsscsi -H
[0] aic7xxx
[2] usb-storage

ae@harley:/$ lsscsi -Hl
[2] usb-storage
cmd_per_lun=1 host_busy=0 sg_tablesize=255 unchecked_isa_dma=0

ae@harley:/$ lsscsi -Hlv
[2] usb-storage
cmd_per_lun=1 host_busy=0 sg_tablesize=255 unchecked_isa_dma=0
dir: /sys/class/scsi_host/host2
device dir: /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/host2

Aerich the Rocket Scientist
Alexandria, VA

PS: I cropped my lsscsi messages.

Well, one disk is /dev/sda, the second is /dev/sdb and the third is /dev/sdc; your CD-RW is /dev/sr0

So, though I'm not all that familiar with USB storage devices and how they are partitioned, I would suggest creating a mount point for the devices you want to mount and seeing what happens when you try to mount /dev/sda1, for example. No idea what the filesystems are, but you might be able to find that using cfdisk /dev/sd*, or some version of the df command.

Hope this helps.