adding
/dev/sda1 /mnt/cruzer vfat noauto,users 0 0
to fstab worked perfectly with Fedora Core 1
hotplugging does not work, so everytime you have inserted a compact flash card you have to initialize the device:
modprobe usb-storage
mount /dev/sda1 /mnt
>
> The /etc/updfstab.conf.default file shipped with Fedora does not
> include the product id for the Sandisk Cruzer Mini USB flash
> rams. These things show up in /proc/bus/usb/devices as
>
> S: Product=Cruzer Mini
>
> I have tried to add either 'match hd Cruzer' or 'match hd "Cruzer
> Mini"' to the flash device section in /etc/updfstab.conf.default, but
> neither work. I tried on both FC1 and FC2 test 2. Updfstab will not
> put /mnt/flash in fstab with these settings, although the device is
> clearly present in /proc and the name matches. Another USB flash RAM
> that shows up as 'Product=Flash Disk' works just fine with the 'match
> hd Flash' that is included in the default file. The Sandisk device can
> be mounted and it works, so the kernel has apparently no problem with
> it, but updfstab just fails.
>
> I'm mystified. Why does updfstab hate the Sandisk unit?
Can you attach the hwconf stanza for the device?
Bill
Bill Nottingham writes:
> Mikko Huhtala (mhuhtala abo fi) said:
> >
> > I'm mystified. Why does updfstab hate the Sandisk unit?
>
> Can you attach the hwconf stanza for the device?
>
> Bill
I get the following in /etc/sysconfig/hwconf:
-
class: HD
bus: USB
detached: 0
driver: usb-storage
desc: "SanDisk Corporation Cruzer Mini"
usbclass: 8
usbsubclass: 6
usbprotocol: 50
usbbus: 1
usblevel: 1
usbport: 0
usbdev: 13
vendorId: 0781
deviceId: 7104
usbmfr: SanDisk Corporation
usbprod: Cruzer Mini
-
The machine I am using is a few years old and only has USB 1.1, but
the problem with updfstab occurs with USB 2.0 buses, too, on other
machines.
Mikko
Yes indeed. The SCSI entry is
-
class: HD
bus: SCSI
detached: 0
device: sda
driver: ignore
desc: "Generic STORAGE DEVICE"
host: 9
id: 0
channel: 0
lun: 0
generic: sg1
-
and adding 'match hd "Generic STORAGE DEVICE"' in the flash entry in
/etc/updfstab.conf.default works. Thanks a lot. Is there some logic to
why the USB product description works for some flash drives and not
for others?
Mikko
The /etc/updfstab.conf.default file shipped with Fedora does not
include the product id for the Sandisk Cruzer Mini USB flash
rams. These things show up in /proc/bus/usb/devices as
S: Product=Cruzer Mini
I have tried to add either 'match hd Cruzer' or 'match hd "Cruzer
Mini"' to the flash device section in /etc/updfstab.conf.default, but
neither work. I tried on both FC1 and FC2 test 2. Updfstab will not
put /mnt/flash in fstab with these settings, although the device is
clearly present in /proc and the name matches. Another USB flash RAM
that shows up as 'Product=Flash Disk' works just fine with the 'match
hd Flash' that is included in the default file. The Sandisk device can
be mounted and it works, so the kernel has apparently no problem with
it, but updfstab just fails.
I'm mystified. Why does updfstab hate the Sandisk unit?
Mikko
After reading this thread, I tried to get my SanDisk Cruzer working, and
all I did was add this:
device cruzer {
partition 1
match hd Cruzer
}
It creates a mount point called /mnt/cruzer in /etc/fstab and sets the
options correctly. The only problem I have is that it can only be
mounted by root unless I change the permissions and ownership of the
device, in this usual case it's /dev/sda1.
I'm trying to put work on a script in /etc/hotplug/usb that will
automaticly change the permissions and ownership of the device (copied
from /etc/hotplug/usb/usbcam) and then mount it, but I don't know how to
set up usb.distmap, usb.handmap, and usb.usermap in /etc/hotplug to
recognize the Cruzer. I can figure out what idVendor and idProduct are
(0x0781 and 0x8888) but I don't know where match_flags comes from.
Edward Hooper
> (0x0781 and 0x8888) but I don't know where match_flags comes from.
Take a look at /etc/security/console.perms. You should be able to add
the /dev/ entry and the /mnt entry there.
Forrest