Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

efung

3 Posts

9632

March 7th, 2005 15:00

PowerEdge 1850 Does Not See USB Memory Key/Flash Drive

I've just installed a new PowerEdge 1850 to Red Hat Enterprise Linux V. 3 using the Dell Server Assistant CD.  Our system has 2 SCSI Hard Drives, which take the device names of SDA and SDB.  I inserted a USB Memory Key but the PE 1850 does not see it.  Can't mount it as /dev/sdc1 (Linux says "mount: /dev/sdc1 is not a valid block device), nor can the Hardware Browser see it.  I tried 2 different USB Memory Keys - (1) Sandisk Mini-Cruzer (256-MB) and (2) Kingston Data Traveler (512 MB) but neither one can be seen by Linux.
 
Am I missing something here?  Any suggestion will be tremendously appreciated; thanks in advance.

Faad

3 Posts

March 9th, 2005 12:00

Are you sure that /dev/sdc1 is the correct device? Check dmesg after you insert the key to find out which device to use

efung

3 Posts

March 9th, 2005 18:00

Dear Faad,
 
Thank you for your response.  Actually, I figured this out on my own yesterday, almost by accident:  I know that with some Dell Linux machines, in addition to the regular Red Hat RPM's, you need some Dell RPM's which are mostly drivers because some Dell hardware does not work properly with the generic Linux drivers.  Such is the case with the Intel Gigabit Ethernet adapters - the e1000.o from Red Hat does not work, you have to install "e1000-5.2.32-2dkms.noarch.rpm" which is provided by Dell.  Well, I suspect that was the case with the USB driver, and there is a Dell DKMS (Dynamic Kernel Module Support) RPM for the USB EHCI driver (ehci-hcd-2.4.21.15.dell1-2dkms.noarch.rpm), so I thought maybe installing this Dell DKMS RPM may work.  However, since the original Red Hat ehci-hcd.o module is automatically loaded, I did a "rmmod" to unload it.  As soon as I did this, my USB memory key's light came on.  And then indeed the machine sees it right away, and I was able to mount it.  I don't quite understand why, but somehow the original Red Hat ehci-hcd.o loadable module was the problem and that unloading it made the system see the USB memory key.  To make sure that the system will not automatically load the Red Hat ehci-hcd.o module at boot time, I commented out the line "alias usb-controller1 ehci-hcd" in /etc/modules.conf.  Indeed, when the machine reboots, it still sees my memory key.
 
... Edwin

Was this post helpful?

View All

No Events found!

Top