All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Gennerat <christian.gennerat@vz.cit.alcatel.fr>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Jeffrey Rose <Jeffrey.Rose@t-online.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0 config breaks /dev/fd0* major/minor ?
Date: Wed, 17 Jan 2001 11:10:23 +0100	[thread overview]
Message-ID: <3A656F8F.2E9450CD@vz.cit.alcatel.fr> (raw)
In-Reply-To: <3A656749.ACF3F01A@t-online.de> <3A6567CF.E10FDEBD@mandrakesoft.com>

Jeff Garzik a écrit :

> Jeffrey Rose wrote:
> > I get a wrong major/minor reported when attempting
> > to mount /dev/fd0 ...
>
> Sounds like it can't find the floppy driver, for whatever reason...
>

I have seen this message, new with 2.4.0-2mdk
(before I have 2.4.0-0.15mdk)
but only on one PC.
I have 2 PC, with same hardware, same PCMCIA config

The first have mandrake 7.2 Odissey, and the modules
floppy and floppy_cs are loaded, and /mnt/floppy is mounted
modutils-2.4.1-1mdk

The second have mandrake 7.1 Helium, and the modules
fail during init. and I have this message:
'mount: /dev/fd0 has wrong major or minor number'
modutils-2.3.21-2mdk (the last rpm-3)


Problem of compatibility of some library?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-17 10:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-17  9:35 2.4.0 config breaks /dev/fd0* major/minor ? Jeffrey Rose
2001-01-17  9:37 ` Jeff Garzik
2001-01-17 10:05   ` Christian Gennerat
2001-01-17 10:11     ` Jeffrey Rose
2001-01-17 10:10   ` Christian Gennerat [this message]
2001-01-17 10:34   ` 2.4.0 config breaks /dev/fd0* major/minor ? Fixed Christian Gennerat
2001-01-17 11:04     ` 2.4.0 config breaks /dev/fd0* major/minor ? *not* Fixed Jeffrey Rose

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=3A656F8F.2E9450CD@vz.cit.alcatel.fr \
    --to=christian.gennerat@vz.cit.alcatel.fr \
    --cc=Jeffrey.Rose@t-online.de \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.