Umm... what does
ls -l /dev/sda*
look like?
Also, "mount /dev/sda" isn't a valid command unless you have an entry for
/dev/sda in your /etc/fstab. From the looks of things, you have an entry
for /dev/sda5 there, so that command _should_ work, tho it doesn't.
Adding to your /etc/modules.conf file the line:
alias block-major-8 sd_mod.o
might help also. However, if it does, then that's a sign that your
modutils are out of date and should be upgraded.
Matt
On Fri, Oct 26, 2001 at 10:32:28PM -0400, Chris Kratz wrote:
> Thanks again Matt,
>
> Unfortunately, the "should" doesn't happen.
>
> -- Snip
> [root@localhost]# mount /dev/sda
> mount: can't find /dev/sda in /etc/fstab or /etc/mtab
> [root@localhost]# mount /dev/sda5
> mount: special device /dev/sda5 does not exist
> [root@localhost]# modprobe sd_mod
> [root@localhost]# mount /dev/sda5
> [root@localhost]# ls /mnt/orb...
> -- Snip
>
> As you suggested, the presence of the USB device doesn't force the sd_mod
> module to load. But, trying to mount /dev/sda5 doesn't either. So there is
> some link or configuration that I don't quite have right yet to convince that
> module to load when I try to mount the drive. Unless someone has a
> suggestion, I'll probably just live with loading it by hand for the time
> being. Hey, it works which is a major step from where I was a week ago.
>
> -Chris
>
> On Friday 26 October 2001 03:43 pm, Matthew Dharm wrote:
> > It will get auto-loaded when you attempt to access the /dev/sdX node -- or
> > at least it should be auto-loaded when you do that.
> >
> > It is _not_ auto-loaded by the presence of the USB device.
> >
> > Matt
> >
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
It was a new hope.
-- Dust Puppy
User Friendly, 12/25/1998
PGP signature