mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bongani Hlope <bonganilinux@mweb.co.za>
To: detlef.grittner@t-online.de (Detlef Grittner)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.1: modprobe behaves strange
Date: Mon, 12 Jan 2004 22:25:08 +0200	[thread overview]
Message-ID: <20040112222508.04054b59.bonganilinux@mweb.co.za> (raw)
In-Reply-To: <4002FF88.3000303@t-online.de>

[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]

On Mon, 12 Jan 2004 21:11:52 +0100
detlef.grittner@t-online.de (Detlef Grittner) wrote:

> Hello,
> 
> I'm using the x86_64 architecture branch and have simply copied the 
> kernel into my configuration of a 2.4.21 kernel.
> 
> I have the following lines in /etc/modules.conf:
> 
> alias eth0 r8169
> 
> alias snd-card-0 snd-via82xx
> 
> With the 2.4.21 kernel everything worked fine, with the 2.6.1 kernel I 
> get the following behavior:
> 
> modprobe eth0
> (no error, but r8169 not loaded)
> 
> modprobe r8169
> (module r8169 is loaded and works)
> 
> modprobe snd-card-0
> (FATAL: Modul snd_card_0 not found)
> 
> modprobe snd-via82xx
> (module snd-via82xx is loaded and works)
> 
> 
> I'm not really a kernel expert and so I have to ask:
> Am I right, that this could be a problem of the kernel?
> Is this the wildcard problem that was fixed in mm1?
> Should I try mm1 or where should I begin to search for the problem?
> 
> Detlef
> 

you have to install module-init-tools it has a modprobe that works with 2.6 modules. See Document/Changes under your linux 2.6 sorce

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-01-12 21:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-12 20:11 Detlef Grittner
2004-01-12 20:19 ` David T Hollis
2004-01-12 20:25 ` Bongani Hlope [this message]

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=20040112222508.04054b59.bonganilinux@mweb.co.za \
    --to=bonganilinux@mweb.co.za \
    --cc=detlef.grittner@t-online.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®