Hardware > USB / BootUsb


In order to retrace the steps that I did to use the "usb mass storage" device on my Compaq Armada 1500c Laptop. SYSTEM: Debian/GNU (sarge/testing/unstable in May 2004) last software upgrade February 2004 KERNEL: 2.4.18 DEVICE: LEXAR JUMPDRIVE ?250MB

I think that this should also apply for any 2.4 kernel but might be problematic with 2.6 kernel (which has something better...) I was confident that I could make it work.

Then I had many trials and did not succeed with it. I have checked the USB-Digital-Camera HOWTO and tried to use this as a starting point after not succeeding by mounting it just as an ordinary drive.

I recommend reading this USB-Digital-Camera-HOWTO first because most of my efforts were based on this work by Dave Kelly.

In the process of this I created a directory as mountpoint for the storage-device-filesystem. I called it "usbstore" as root it might as well be called "/mnt/camera" or "/mnt/flash"

see also: USBCamera

However the USB-storage stick did not work in the same way. I have tried the scripts but I only got a message that this is not a valid block-device if I tried to mount it with the same commands.

I read up on some articles:

which indicated that the flash is not so easy to do under debian additionally the second article describes someone having similar problems with a similar device:

or


After playing around for a while with the same error messages, I tried the recommendations from the Documentation that I found in my Kernel-source tree: /usr/src/kernel-source-2.4.18/Documentation/usb/proc_usb_info.txt this was helpful and provided me with another indication:

?bash/# mount -t usbdevfs none /proc/bus/usb ?bash/# mount none /proc/bus/usb type usbdevfs (rw)

I found in /proc/bus/usb the following three files: 001/001 (001 in directory 001) devices drivers

the content of devices:



so this was basically empty...

drivers/modules that I had installed (first with modprobe, later with modconf):


         usbdevfs
         hub
         usb-storage


information in /proc/scsi/scsi:


attached devices: none



so this did not work at all, but I have used the same entry in fstab and I mounted the thing, before. what happened? I remember that I loaded some modules with modprobe, before it worked, there were the modules:



the next day

?bash\# mount /mnt/usbstore

an item on the desktop showed up: usbstore which let me open a nautilus window on doubleclick. excellent!


So why did it not work before?

I started the computer with the device plugged in (and my entry in fstab for the device being:

However when I typed "mount" it showed something like

none on /proc/bus/usb type usbdevfs (rw)

I found a section in /etc/init.d/mountkernfs that is automatically loading a usbdevfs in /proc/bus/usb on startup if there is one available, but this is not useful, because I cannot read or write to it this way. I have now commented out this section of the file so that on startup instead the fstab should be used which is now:



So, it worked, but when plugging the USBStorageDevice into port, it did not always mount. opening the normal shell tty1 (Alt-Ctrl F1) gave some more information: it sometimes said that the device was not accepting the device-number. but I cannot always reproduce this information (of course not now, when I want to show it).... plugging and unplugging several times worked, until the message:

 hub.c: New device detected on bus 1/1 assigned bus number /3/4/5/ (any number)

2