next up previous contents home.gif
Next: Firewire Up: Hardware Previous: Built in memory stick   Contents

USB Memory stick

I have a Kanguru USB 2.0 with 512 MB of memory. As root you should use tail to look at /var/log/messages to see where the system puts the drive.
bash-2.05b# tail -f /var/log/messages
Mar 15 18:23:04 sony-lap kernel: input0: USB HIDBP Mouse 0461:4d03 on usb3:2.0
Mar 15 18:23:04 sony-lap kernel: usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
Mar 15 18:23:04 sony-lap kernel: usb.c: registered new driver hiddev
Mar 15 18:23:04 sony-lap kernel: usb.c: registered new driver hid
Mar 15 18:23:04 sony-lap kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik<vojtech@suse.cz>
Mar 15 18:23:04 sony-lap kernel: hid-core.c: USB HID support drivers
Mar 15 18:23:04 sony-lap kernel: mice: PS/2 mouse device common for all mice
Mar 15 18:23:04 sony-lap sshd[1301]: Server listening on 0.0.0.0 port 22.
Mar 15 18:43:03 sony-lap -- MARK --
Mar 15 19:03:03 sony-lap -- MARK --
Mar 15 19:07:12 sony-lap kernel: hub.c: new USB device 00:0c.2-1, assigned address 2
Mar 15 19:07:16 sony-lap kernel: Initializing USB Mass Storage driver...
Mar 15 19:07:16 sony-lap kernel: usb.c: registered new driver usb-storage
Mar 15 19:07:16 sony-lap kernel: scsi1 : SCSI emulation for USB Mass Storage devices
Mar 15 19:07:16 sony-lap kernel:  sda: sda1
Mar 15 19:07:16 sony-lap kernel: USB Mass Storage support registered.

As you can see from the output above the kernel found the device started SCSI emulation and assigned it to /dev/sda1. You can also see your new drive with a fdisk -l.

Once you know the drive letter/number just alter /etc/fstab

/dev/sda1       /mnt/usbstick     vfat    user,noauto,umask=0   0 0

If the device doesn't show up in the messages files, you probably don't have the usb modules loaded. Try the lsmod commands suggested here.



Douglas Dawson 2004-03-31