public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jos Hulzink <josh@stack.nl>
To: "Randy.Dunlap" <rddunlap@osdl.org>, ocsy@yandex.ru
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to use module in 2.6
Date: Wed, 1 Oct 2003 18:14:25 +0200	[thread overview]
Message-ID: <200310011814.25330.josh@stack.nl> (raw)
In-Reply-To: <20031001083021.125e817d.rddunlap@osdl.org>

On Wednesday 01 Oct 2003 17:30, Randy.Dunlap wrote:
> On 01 Oct 2003 15:54:00 +0400 ocsy <ocsy@yandex.ru> wrote:
> | Yes i make it))Kernel comile and modules was done (make modules after
> | that make modules_install)And than reboot....
> | But after that I type insmod <module_name> and I see on a screen a
> | LITTLE warning (fatal error) that talk to me module can be load to the
> | kernel becouse it have old format))
>
> insmod module.ko, not insmod module.o
>
> Or (preferable) use modprobe module
>
> | I think than I must look for modutils (witch can support kernell 2.6 new
> | modules format) but I can't find it...
>
> modutils are for before 2.6.
> 2.6 uses module-init-tools only.

Not really an improvement IMHO. The returned errors are unclear, the tools 
seem to ignore the verbose command line option. As a result I have been 
fighting with ALSA modules, modprobe.conf and modules.conf for days now. I've 
not managed to get all dependancies right yet, the only way to get my SB Live 
working is loading 20 modules by hand, one at a time... Somehow modprobe 
remains complaining about unresolved symbols.

FWIW: 2.6.0 test 6, module-init-tools 0.9.14, mandrake 9.1 with modutils 
deinstalled.

Jos

      reply	other threads:[~2003-10-01 16:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01 11:10 How to use module in 2.6 ocsy
2003-10-01  9:36 ` johann lombardi
2003-10-01 11:58   ` ocsy
2003-10-01 14:46     ` Oscar Peredo
2003-10-01 15:01       ` Sam Ravnborg
2003-10-01 11:29 ` Andreas Schwarz
2003-10-01 11:54   ` ocsy
2003-10-01 15:30     ` Randy.Dunlap
2003-10-01 16:14       ` Jos Hulzink [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=200310011814.25330.josh@stack.nl \
    --to=josh@stack.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ocsy@yandex.ru \
    --cc=rddunlap@osdl.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