I've just bought a Fujitsu Memorybird,
a memory unit that is attached to the
usb-port.
I have mounted it successfully on my
stationary computer with just the command:
mount -t vfat /dev/sda1 /mnt/mbird
But, when I try to do exactly the same thing on
my laptop computer, it says
mount: /dev/sda1 : unknown device
(I tried several other /dev/sda's, but the
same answer.)
I have the same distro, RH7.1, installed on both
systems. Anybody have an idea what could be the problem?
Caj Zell
The laptop and desktop obviously differ in some way. You need to do an
"lsmod" on the laptop and make sure that all the appropriate modules are
loaded when the USB storage device is plugged in. For these memory card
readers, the appropriate modules are:
usbcore
usb-uhci (NOTE: may be usb-ohci)
usb-storage
scsi_mod (NOTE: Redhat may have this built in to the kernel)
sd_mod (NOTE: Redhat may have this built in to the kernel)
ide-scsi (shouldn't be necessary, but might be useful)
If all that junk is there, make sure that /dev/sda and /dev/sda1 exist
on your laptop system. If they don't, then Redhat's installer was
remiss in its duties, and you'll have to create them. The commands are
as follows:
mknod /dev/sda b 8 0
mknod /dev/sda1 b 8 1
HTH, sorry about this taking so long....
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /
http://www.brainbench.com / "He is a rhythmic movement of the
-----------------------------/ penguins, is Tux." --MegaHAL
Thank you very much!
I just loaded this module and everything went smooth
mounting /dev/sda1.
Is there some way of telling the kernel to load
that module when I try to mount /dev/sda1?
Caj Zell
You can stick the command
modprobe usb-uhci
into /etc/init.d/boot.local (/etc/rc.d/rc.local for Redhat users) and
the module will be loaded automagically when you boot the machine. Or
you could stick the line
alias usb-hostadapter usb-uhci
into /etc/modules.conf and run "depmod -a" so that the module is loaded
when any USB activity takes place.
This is surprising; I thought that most distros' installation managers
detected these bits of hardware and made sure that the correct modules
were set to load automagically.