block-major-33

block-major-33

[Tiemo Krüger - mycable GmbH]

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
-------------------------------------------------------

Re: block-major-33

[Heimo Claasen]

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 pertinent line for that CF card adapter into the
configuration file for mounting of the various filesystems, fstab.
I have it there as
/def/hde1    /[cf-card]    msdos   ...(noauto and olther spec.s)
    ^^^^^                  ^^^^^
Basicly, CF cards _would_ behave like vfat formatted hard disks - and
do that, if wanted, in a CF-to-IDE _adapter_(*) - but for whatever
reason don't do that when used in those PCMCIA slots.

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" which obviously watches one of those pins.)

// Heimo Claasen // <hammer at revobild dot net> // Brussels 2002-09-
The WebPlace of ReRead - and much to read  ==>  http://www.revobild.net

(*) Those CF cards have specifications which make them rather directly
pin-compatible with HD or floppy drive connectors on the mainboard.
Theoretically they then behave like just any "(hard) disk drive" -
though note that this is very _different_ from the PCMCIA setup !
I'm just ordering one (<20 USD) and will be curous how it behaves
in the Linux box. That one is even announced as "hot swappable";
though I assume this is comparable to "media changes" with floppies
and Zipdrives, so it would mean to mount/umount the cards with swapping.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

block-major-33

[Tiemo Krüger - mycable GmbH]

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
-------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-config" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: block-major-33

[Ray Olszewski]

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, errno = 2
>mount: /dev/hde is not a valid block device

what actual command are you entering? The "hdxx" in your command line is 
inconsistent with the "hde" in the result. I'm *guessing* that when you 
write "hdxx", you mean you actually type something like "hde1". But that 
should return an error with respect to (in my example) hde1, not hde.

Second, I'm uncertain as to why you are getting a modprobe message (you 
seem to be saying that you did everything right but it still doesn't work, 
and that's not the sort of description that anyone can intelligently 
troubleshoot), but the block-major-33 just refers to hde, hdf,  and the 
various hde* and hdf* devices (which differ by their minor number). 
Simliarly, block-major-22 is hdc and hdd, and 3 is hda and hdb. Do you have 
an /etc/modules.conf file in your root filesystem? If yes, what is 
block-major-33 an alias for?

All this suggests to me that either your kernel lacks IDE support, or your 
hardware uses a non-standard IDE controller.

During the boot/init process, does the kernel report finding any of the IDE 
devices? (For that matter, are there any IDE devices other than the CF? 
What is the kernel loading from? What is your root filesystem on, or loaded 
from if it is a RAM disk)

A standard Linux kernel (I just checked 2.4.17) should need only these 
choices included

          <*> Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
         <*>   Include IDE/ATA-2 DISK support

to support regular IDE drives. So if you have a hard disk on the system 
that you cannot access, as your mention of block-major-3 seems to suggest, 
then you have a basic problem with the kernel's IDE support. If the devices 
in question are all CFs (or the same CF moved fom one IDE channel to 
another), then your problem may be specific to the CF stuff, an area I am 
not familiar with.

I don't know is this sort of response is helpful or not. If not, I'm sorry.

At 12:58 PM 9/28/02 +0930, Tiemo Krüger - mycable GmbH wrote:
>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




--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: block-major-33

[Elias Athanasopoulos]

On Sun, Sep 29, 2002 at 09:31:25AM +0000, 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" which obviously watches one of those pins.)

The kernel hasn't load the appropriate module when fstab is parsed
during the boot process, so you get the error.

Elias

-- 
http://gnewtellium.sourceforge.net			MP3 is not a crime.	
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: block-major-33

[Heimo Claasen]

> 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]" message appears.

On a similar issue, but on the Zip-Drives's "exchangeable medium":
In the manuals, Iomega advises to _not_ have a Zipdisk inserted when
booting up. However, depending on the setting in fstab (with or
without auto-mounter) you would get a "[FAILED]" for this too.

Which would be only logical. Though as with floppies too, the
traditional wisdom is to _not_ have them inserted when starting up a
machine, as the start-up and self-tests could cause an initial current
in the divices which _could_ be harmful for data on the inserted media.

So why starting up Linux _does_ demand to have them insterted ?
I found numbers of such indications in articles, Howtos etc.

// Heimo Claasen //<revobild at revobild dot net>// Brussels 2002-10-07
The WebPlace of ReRead - and much to read  ==>  http://www.revobild.net

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: block-major-33

[Elias Athanasopoulos]

On Mon, Oct 07, 2002 at 01:54:11PM +0000, 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  to
the  big file tree. Conversely, the umount(8) command will detach it again.
		   
So, as you can see you have to have a *file system* to mount. Keep in mind,
that mount has nothing to do with hardware identification of the device 
(this is done by the kernel using probe routines).

Elias

-- 
http://gnewtellium.sourceforge.net			MP3 is not a crime.	
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs