Thanks Chris.
I can't find a file called usbmgr.conf, or usb*.conf for that matter. There is a script call /etc/init.d/usb, though. Should I look for something else instead ?


Something I just thought of: The drive is a USB 2.0 device, but my USB ports are USB 1.1 (AFAICT). Could this be causing my problems ?

Dave

Cunningly disguised as a responsible adult



Chris Day wrote:

OK - can't be sure this will fix it, but have a read of the following stuff I found in my files for an old USB drive DSE used to sell - I would have tested it on an old version of MDK that supported USB AND its written for the average non-Linux person:

"The xxx is considered to be a Mass Storage Device. Linux uses a so-called "USB Manager", which does automatically kernel modules (drivers) for USB devices. It loads only drivers for devices that are present on the USB bus to reduce memory usage. Per default, the USB Manager does not come preconfigured for the xxxx, but you can easily configure the USB Manager to automatically recognise the xxxx Drive yourself. Just add the following to the configuration file, usbmgr.conf (usually in /etc/usbmgr):

vendor 0xd7d product 0x100 module scsi_mod, usb-storage

This line identifies the xxx Drive and tells the USB Manager to load the SCSI as well as the USB storage module. The SCSI module is needed in order to talk to both SCSI and USB storage devices, while the usb-storage module is needed to talk to USB storage devices. Do not forget to either reload the USB Manager's configuration or to restart the USB Manager (for instance, do as root: /etc/init.d/usbmgr reload)."

It may or may not be what you are after and vendor & product ID's will probably not be the same - use usbview to find this out for your drive. And as I say, it will be for an older version of MDK - possibly 8.2? Anyway, we didn't get many support calls (maybe no Linux users purchased one?).

Rgds, Chris...




Reply via email to