From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Tony Lill <ajlill@tardis.ajlc.waterloo.on.ca>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: generate modprobe.conf
Date: Thu, 28 Aug 2003 14:21:55 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0308281417580.3807@chaos> (raw)
In-Reply-To: <200308281702.h7SH2uql011425@spider.ajlc.waterloo.on.ca>
On Thu, 28 Aug 2003, Tony Lill wrote:
> Bas Mevissen <ml@basmevissen.nl> writes:
> > Hmmm. Strange. But it doesn't look like a kernel problem, but a system
> > configuration problem. So I'll take this off LKML and see if I can
> > help you by private e-mail.
>
> Unless there's a linux-kernel-broke-my-sytem-but-its-not-really-its-fault
> mailing list I can subscribe to, please keep the discussion here. I've
> got simmilar problems, and any solution may be enlightening.
> --
> Tony Lill, Tony.Lill@AJLC.Waterloo.ON.CA
> President, A. J. Lill Consultants fax/data (519) 650 3571
> 539 Grand Valley Dr., Cambridge, Ont. N3H 2S2 (519) 241 2461
> --------------- http://www.ajlc.waterloo.on.ca/ ----------------
> "Welcome to All Things UNIX, where if it's not UNIX, it's CRAP!"
Well, to start, become root and execute `modprobe -c >junk`.
The file, junk, now contains everything modprobe 'knows' about.
You can use this as a reference.
Let's say that you have a new device, a character device with
a major number of 177. You want a module to be automatically
loaded upon the first access to that device. You simply insert
the following lines in /etc/modules.conf.
path[my-module]=/complete/path/to/where/you/put/it
alias char-major-177 my-module
Normally, you keep all the paths together and the aliases
sorted to make sense to humans. The software doesn't care.
Also, "my-module" is the module file-name without the ".o"
You only need paths if the module is not in a standard
place like 'lib/modules/`uname -r`/kernel. The file
/lib/modules/`uname -r`/modules.dep, contains all the
dependency information for everything, generated with
the `depmod -a` command.
Maybe somebody has a script that configures this auto-magically,
however I've never seen it and haven't had to use it. Problems
with finding modules with new kernel versions usually are the
result of a change in the directory structure under
/lib/modules/`uname -r`/ so you might want to make several
/etc/modules.conf files if you boot several widely-different
kernel versions. Just fix up the paths where required.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
Note 96.31% of all statistics are fiction.
prev parent reply other threads:[~2003-08-28 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 9:42 Michal Semler (volny.cz)
2003-08-27 10:03 ` Bas Mevissen
2003-08-27 10:06 ` Michal Semler (volny.cz)
2003-08-27 10:34 ` Bas Mevissen
2003-08-28 17:02 ` Tony Lill
2003-08-28 18:21 ` Richard B. Johnson [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=Pine.LNX.4.53.0308281417580.3807@chaos \
--to=root@chaos.analogic.com \
--cc=ajlill@tardis.ajlc.waterloo.on.ca \
--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®