On Mon, Oct 07, 2002 at 01:54:11PM +, Heimo Claasen wrote:
> So why starting up Linux _does_ demand to have them insterted ?
> I found numbers of such indications in articles, Howtos etc.
>From the man page of mount:
The mount command serves to attach the file system found on some device t
> The kernel hasn't load the appropriate module when fstab is parsed
> during the boot process, so you get the error.
I don't think this is the reason; the module _is_ loaded with the
kernel but if the adapter with a CF card is not present/inserted it's
with executing 'fstab' that the "[FAILED]"
On Sun, Sep 29, 2002 at 09:31:25AM +, Heimo Claasen wrote:
> With that fstab line I would get a "[Failed]" message with booting,
> but a manual 'mount /cf-card' when needed will indeed mount it, if it
> wouldn't mount automatically when the card is inserted or taken out
> (task of that "cs-mgr
With configuring a not-so-quite-new laptop I strugled with precisely
this problem. In the 2.2.x kernel based system it was rather a hassle,
the 2.4.x have the PCMCIA 'card service' management (IIRR it was the
earlier cs_mgr module) integrated. All what was needed on that laptop
then was to write a
Tiemo -- Please clarify what you are doing.
First, when you write --
>Then I try to mount the CF Card (which is VFAT and VFAT is in my kernel)
>with
>
>mount -t vfat /dev/hdxx /mnt
>
>The response is then:
>
>kmod: failed to exec /sbin/modprobe -s -k block-major-33, er
of the Card seems to work as I get belonging messages.
Then I try to mount the CF Card (which is VFAT and VFAT is in my kernel)
with
mount -t vfat /dev/hdxx /mnt
The response is then:
kmod: failed to exec /sbin/modprobe -s -k block-major-33, errno = 2
mount: /dev/hde is not a valid block device
I
