mathman--Are you using a 2.6.x kernel? If so, you can write a udev rule to take care of all that stuff.

chrisknight--Check your kernel config. You might be able enable a camera driver in the kernel that would enable gphoto to handle all of the mounting etc. Otherwise, start trying to mount sda1,sda2,sda3,sda4. My guess would be sda4, but one never knows.

If you use a multiple card reader, the first slot should be seen as /dev/sda
and then the first partition /dev/sda1

You can see partitions table:
cat /proc/partitions

But for the other slot of card you should pas this parameter:
max_scsi_luns=4
In the append of your boot loader (cf: lilo.conf for lilo or /boot/grub/menu.lst for grub)

So that kernel could detect your slots as scsi luns

Nb: you can have a try with knoppix at boot: prompt (in live-cd mode):

knoppix26 lang=fr max_scsi_luns=4

Good info JoDay. For the sake of any newbie reading through this (and for my own personal knowledge!) can you explain what are scsi luns and does it have an impact on the fstab? Thanks!

The howto is very helpfull and most everything seems to be working. However the link of the USB stick to SCSI does not appear to be working. The stick is recognized. Does anyone have any pointers on why the scsi link is not happening?

Dmesg outputs:

usb 1-1: new full speed USB device using uhci_hcd and address 3
uba: device 3 capacity nsec 503808 bsize 512
uba: device 3 capacity nsec 503808 bsize 512
uba: uba1

The 'successful' howtos show a scsi connection here. lsmod shows:

[600e linux-2.6.11.2]# lsmod |grep scsi
scsi_mod 94504 2 sd_mod,sg

so scsi_mod, sd_mod, and sg are successfully loaded.

/proc/parttions shows:

180 0 251904 uba
180 1 251888 uba1

Does anyone have a pointer as to why scsi is not picking up the mount?

Thanks,
Dan

What about mass storage? Is that enabled/loaded? Also, what is the output when you try and mount the drive?I'll do my best to help once you post that info. Also, I've never seen uba before. Are you using a BSD?

Hello,

There is a config parameter UA that supports an older USB driver. That was configured and took control of the device. I turned that off and now the card works. Thanks for your offer. It was a configuration conflict.

Dan

Great--congrats!

I've just read this HOW-TO and I'm having trouble with two points of this. I welcome any suggestions to those reading this.

First, the article mentions " legacy /proc/scsi/ support" in the kernel config step. I've been through every possible menu and do not see this anywhere. I'm running 2.4.26 from Slackware 10; is that part of the problem?

Then, later, the article says "First, lets see if the kernel sees your reader:" and we look at proc/scsi/scsi. If I cat that, I only see my CDRW. Nothing else. However, if I look at /proc/scsi there are two sub directories that catch my attention. One is usb-storage-0 and the other is usb-storage-1. In -0, there's a file called 0 which says:

Host scsi0: usb-storage
Vendor: SOYO Technologies Corp.
Product: SOYO USB Storage Device
Serial Number: 0AEC501000001A002
Protocol: Transparent SCSI
Transport: Bulk
GUID: 0aec5010aec501000001a002
Attached: No

And in -1, there's a file called 2, which says:

Host scsi2: usb-storage
Vendor: SOYO Technologies Corp.
Product: SOYO USB Storage Device
Serial Number: 0AEC501000001A003
Protocol: Transparent SCSI
Transport: Bulk
GUID: 0aec5010aec501000001a003
Attached: Yes

And (finally?) dmesg, trimmed only lines about USB or SCSI:

Linux version 2.4.26 (root@vengeance) (gcc version 3.3.4) #7 Fri Mar 18 16:19:05 MST 2005
Kernel command line: BOOT_IMAGE=LinuxSCSI ro root=307 hdc=ide-scsi
ide_setup: hdc=ide-scsi
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
scsi0 : SCSI emulation for USB Mass Storage devices
hdc: attached ide-scsi driver.
scsi1 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: MITSUMI Model: CR-48XGTE Rev: 1.0K
Type: CD-ROM ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
hub.c: new USB device 00:11.2-1, assigned address 2
usb-uhci.c: interrupt, status 3, frame# 1019
input: USB HID v1.00 Mouse [Microsoft Microsoft Trackball Optical®] on usb3:2.0
hub.c: new USB device 00:11.2-2, assigned address 3
hub.c: USB hub found
hub.c: 4 ports detected
usb.c: registered new driver usbmouse
usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
ehci_hcd 00:0e.2: VIA Technologies, Inc. USB 2.0
ehci_hcd 00:0e.2: irq 10, pci mem f903d000
usb.c: new USB bus registered, assigned bus number 5
ehci_hcd 00:0e.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Dec-29/2.4
usb.c: USB disconnect on device 00:0e.0-1 address 2
hub.c: USB hub found
hub.c: 4 ports detected
uhci.c: USB Universal Host Controller Interface driver v1.1 [edit: repeated 20 m
ore times]
hub.c: new USB device 00:0e.0-1, assigned address 3
uhci.c: USB Universal Host Controller Interface driver v1.1
scsi2 : SCSI emulation for USB Mass Storage devices
uhci.c: USB Universal Host Controller Interface driver v1.1
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
uhci.c: USB Universal Host Controller Interface driver v1.1 [edit: repeated 24 m
ore times]
Attached scsi CD-ROM sr0 at scsi1, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 54x/54x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12

I'm stumped. I'm frustrated. I'm ready to go play Solitaire. *grin* Okay, maybe not _that_ frustrated yet. If anyone has any suggestions, I'm definitely willing to give them a try.

Thanks,
Anne.

Hello,
I am a new linux user and I am facing the same probleme mounting my usb flash drive.
running dmesg, that's what I am getting and I don't know what to do next:

hub.c: new USB device 00:1d.2-1, assigned address 2
usb.c: USB device 2 (vend/prod 0xc45/0x1060) is not claimed by any active driver.
SCSI subsystem driver Revision: 1.00
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: 64MB Model: FLASH Rev: 64 f
Type: Direct-Access ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
usb.c: USB disconnect on device 00:1d.2-1 address 2


I am using a pink tie, Linux version 2.4.20-6 (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)

Thanks for any help

__________________
Welcome to my L-Word

for both of you guys, you can tell by the output of dmesg that the kernel is not assigning your usb drive (for example, it will say something like sda4 or whatever). On the command line, under the root command, type lsmod.. If you put M instead of Y under kernel configuration, then you need to make sure that the modules are loaded. THe only other thing that I can think of is something funny going on with either hotplug or udev.

That's what I thought.

I set the SCSI options as "built-in". I suspect that is where the problem is, as opposed to it being USB problems. I cannot find the option in the menuconfig for legacy /proc/scsi/scsi support---could that be part of the problem?

Thanks for your reply. I've been struggling so much with this and I was wondering if I was missing something obvious.
Anne.

Hi,
From the article we can access the usb devices as a root(super user).
To access usb devices like "Memory stick" as a non-root("guest") user
what are the changes we need to make .

Regards
Harsha

in your /etc/fstab file, you need to add the user or users option to the device line. THe difference is, user means that only the person (user) who mounted it can unmount it. Users means that anyuser can unmount the mounted device. So the line should look like this:
I hope that helps. I assume your memory stick is formatted as vfat, otherwise you need to put the approrpriate filesystem in that slot.

hi,
Thanks for ur reply.
now i have one more query ,
how can i make my usb ports to be accesible by a non-root user.
i have changed the permissions of /proc/bus/usb but when i restart my PC the changes are resetting to original one.
i need this because i want to run my hardware circuit as a non-root user,it is running as a root but not as a non-root.
or
is it possible to autologin as a root. if yes how?
i am using Federa core 3.
any of the above problems will solve my problems.

thanks in advance
regards
harsha

You should not have to be root to mount the device. What kernel are your running? If you are running a 2.6 kernel, you could follow this link and write a udev rule for your device, to make the mounting easier. I'm sorry, but I don't know what's getting in the way of the user mounting it. Once you've mounted it as root, log out of root and try as user. I guess the only other suggestion I would have is to make sure that your user is part of the users group.