From: "Tiemo Krüger - mycable GmbH" <tiemo.krueger@mycable.de>
To: linux-config@vger.kernel.org
Subject: block-major-33
Date: Thu, 26 Sep 2002 11:11:29 +0200 [thread overview]
Message-ID: <3D92CF41.6010909@mycable.de> (raw)
Hi,
I'm not sure if I found the right group to place my request, so pls
apologize
for any inconvenience.
I'm busy porting 2.4.17 and .18 to a MIPS 32 board.
There is a PCMCIA slot and I want to access a CompactFlash Card in a
belonging "CF to PCMCIA" adapter.
Hotplugging 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 don't have modprobe in my root filesystem and during testing I want to
work just with in-kernel-compiled modules and not loadable modules.
So it seems that I missed to compile the belonging modules
for hda/hdb hdc/hdd hde/hdf into my kernel.
I've tried already some options but didn't found out a correct setting.
Is there any essential module which has to be activated?
As far as I've seen there are for the above named devices the
block-major 3, 22 and 33 responsible.
Do they correspond to any specific kernel config setting?
If I remove the "loadable-modules" option from the kernel I just get
the message:
mount: /dev/hdx is not a valid block device
kind regards
Tiemo
--
-------------------------------------------------------
Tiemo Krueger Tel: +49 48 73 90 19 86
mycable GmbH Fax: +49 48 73 90 19 76
Boeker Stieg 43
D-24613 Aukrug eMail: tk@mycable.de
Public Kryptographic Key is available on request
-------------------------------------------------------
reply other threads:[~2002-09-26 9:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D92CF41.6010909@mycable.de \
--to=tiemo.krueger@mycable.de \
--cc=linux-config@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).