Help mounting USB flash drive in Slackware 12
 

What do I need to do to mount my flash drive in Slackware12.1

It seems like its not giving a mount point when I plug it in, I used "tail -f /var/log/messages" and plugged it in and got: "Nov 12 15:08:07 lolwut kernel: usb 1-3: new high speed USB device using ehci_hcd and address 5"

Google has failed me and the guys on the irc cant seem to help me... Any ideas?

Thanks,
Steven

You should get a mount point if you're running Xfce, KDE or GNOME.

Otherwise, don't expect one. Use "fdisk -l" (as root) to find out where your flash drive's device node is. Then mount that device node in whatever directory you want (I would advise /mnt).

As mentioned, if using KDE (or the others mentioned) it should mount automatically. Otherwise, you need to mount it manually. dmesg will also tell you the /dev/node after you plug it in.

If you use KDE, you might want to open the "Control Center",
look under Desktop - Behavior - Device Icons, and check the
appropriate boxes to see device icons on your desktop.
(which you can then right-click to get a mount/unmount menu)

If you don't use KDE, you should say what you do use. :)

The command
may also return the node in /dev corresponding to a USB drive (in addition to CDs and other removeable media, I think). `fdisk -l` as root should show it too, but it requires root priveleges.

The problem im getting is that it isn't mounting at all. Im using kde and it dosent show up under fdisk -l. It also isnt listed in dmesg...

bash-3.1# dmesg | tail -n20
usb 1-4: new high speed USB device using ehci_hcd and address 16
usb 1-4: device descriptor read/64, error -71
usb 1-4: device descriptor read/64, error -71
usb 1-4: new high speed USB device using ehci_hcd and address 17
usb 1-4: device descriptor read/64, error -71
usb 1-4: device descriptor read/64, error -71
usb 1-4: new high speed USB device using ehci_hcd and address 18
usb 1-4: device not accepting address 18, error -71
usb 1-4: new high speed USB device using ehci_hcd and address 19
usb 1-4: device not accepting address 19, error -71
usb 1-4: new high speed USB device using ehci_hcd and address 20
usb 1-4: device descriptor read/64, error -71
usb 1-4: device descriptor read/64, error -71
usb 1-4: new high speed USB device using ehci_hcd and address 21
usb 1-4: device descriptor read/64, error -71
usb 1-4: device descriptor read/64, error -71
usb 1-4: new high speed USB device using ehci_hcd and address 22
usb 1-4: device not accepting address 22, error -71
usb 1-4: new high speed USB device using ehci_hcd and address 23
usb 1-4: device not accepting address 23, error -71

I typed one of the error messages into Google (which you could have done, no offence), and a lot of interesting links came up. Here are two random ones from near the top:

http://www.guyrutenberg.com/2008/06/...ad64-error-71/
http://www.mepis.org/node/5860

My thumb drive is formatted with VFAT so the core is "windows like." And yes I have checked it on windows xp laptop next to me, on my windows partition on this computer and on my fedora partition on this computer and I can read and write in all. Ive also run checkdisk in windows and it came back with no errors.

Just to see if it would work I tried that line of code and it did not.

Did it fail differently, or did it fail in the same way as before?

Same way as before

Anything else we should know? What other courses of action (you mentioned that you've already researched the problem on IRC and Google) did you already investigate?

We didn't really change anything.

If you do not tell us what the people on IRC said, then we will say the same things.

If you do not tell us what you already found on Google, then we will post the same links.

To be clear on how important this is, let me point out that the first 4 responses you got were correct for the question you asked and the information you gave.

I'm at work right now, so I can't check the details, but you may have a conflict with OHCI vs EHCI drivers. That's the only thing that comes to mind right now...though I can't see how that would prevent the drive from even being recognized. You might want to try unloading the current USB driver and try loading the other (and vice versa) to see if that's the problem.

The guys on the ##slackware irc said that it was probably a driver issue but that the drivers were built in and that I needed to write a kernel for it or something... is there an easier way?