USB flash memory

laryy · 07-14-2007, 11:33 AM

I got problem with my USB flash memory.
When I insert the USB flash memory, nothing happens.

Nylex · 07-14-2007, 12:14 PM

You need to mount the partition on it to be able to access the files. After you plug the device in, run dmesg in a terminal and that will help you find out what the kernel is calling it. For example, here's the output after I plug mine in:

USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 2:0:0:0: Direct-Access Sony Storage Media 0100 PQ: 0 ANSI: 0 CCS
SCSI device sdb: 1966080 512-byte hdwr sectors (1007 MB)
sdb: Write Protect is off
sdb: Mode Sense: 43 00 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 1966080 512-byte hdwr sectors (1007 MB)
sdb: Write Protect is off
sdb: Mode Sense: 43 00 00 00
sdb: assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: Attached scsi removable disk sdb
sd 2:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete

The bit in bold tells me that the kernel's calling it /dev/sdb and that there's 1 partition on it (sdb1), which is the one I need to mount.

Once you find out this information you can then mount it with "mount device mount point -t filesystem type -o options"

For example, I can mount mine with "mount /dev/sdb1 /mnt/memory -t vfat", since the partition is formatted FAT32. You may not need to specify the filesystem type or any options. The mount point (/mnt/memory in my example) must exist before you try and mount, otherwise you'll get an error telling you it doesn't exist. You will need to be root to mount.

One thing to note: the device may not always be called the same thing. Say I have two memory sticks and I plug them in in different orders at different times. The one I plugged in first the first time will be sdb, but will be sdc the second time (I also have an SATA hard drive in my machine, which is sda). You'd probably like to assign meaningful, persistent names to your removable devices (for example, my memory sticks end up being called /dev/flash, rather than /dev/sdb), which you can do with udev and a 2.6.15.x kernel (or later).

happyslacker · 07-14-2007, 02:11 PM

Try this program:
Using USB memory sticks with Slackware Linux

Boow · 07-15-2007, 06:27 PM

in slackware 12 make sure dbus and hal are running.

chmod +x /etc/rc.d/rc.messagebus
chmod +x /etc/rc.d/rc.hal

reboot

randomsel · 07-15-2007, 08:27 PM

Quote:

Originally Posted by Boow

in slackware 12 make sure dbus and hal are running.

chmod +x /etc/rc.d/rc.messagebus
chmod +x /etc/rc.d/rc.hal

reboot

and add your users to the appropriate groups (check out the sticky in the forum)

laryy · 07-17-2007, 03:21 PM

Quote:

Originally Posted by Boow

in slackware 12 make sure dbus and hal are running.

chmod +x /etc/rc.d/rc.messagebus
chmod +x /etc/rc.d/rc.hal

reboot

Quote:

Originally Posted by randomsel

and add your users to the appropriate groups (check out the sticky in the forum)

Code:

larry@darkstar:~$ groups 
users floppy audio video cdrom plugdev
larry@darkstar:~$

Now USB work fine after "chmod +x rc.messagebus ; chmod +x rc.hal" and installation of vsupdfstab-0.1-noarch-0.tgz.

Quote:

The vsupdfstab automatically adds to fstab USB mass storage devices when they are plugged in, and removes them from fstab when they are removed. This program don't automatically mount devices, because this is incompatible with KDE.

rkelsen · 07-17-2007, 05:46 PM

Quote:

Originally Posted by laryy

Now USB work fine after "chmod +x rc.messagebus ; chmod +x rc.hal" and installation of vsupdfstab

You shouldn't need vsupdfstab for HAL to work properly. I don't have it installed, and everything works for me.

naflan · 07-17-2007, 07:24 PM

-Add required users to the group plugdev

-As root /etc/rc.d/rc.messagebus restart

-As root /etc/rc.d/rc.hald restart

rworkman · 07-17-2007, 07:35 PM

Quote:

Originally Posted by rkelsen

You shouldn't need vsupdfstab for HAL to work properly. I don't have it installed, and everything works for me.

More importantly, I personally don't want anything but *me* editing /etc/fstab. I don't see the need for it anyway -- what's the point?

I've got ivman and pmount for 12.0 ready to commit at SlackBuilds.org, so I'll try to go ahead and get those pushed out tonight or tomorrow -- it seems that a lot of people are wanting that sort of functionality.