Re: Console error messages on start up.
From: Glenn Meehan (dump-your-spam-here_at_sco.com)
Date: 06/08/04
- Next message: Christoph Nickschick: "transcode export_mpeg missing"
- Previous message: Tristan Miller: "Re: Convert Farsi (Arabic) PDF to plain text"
- In reply to: matthieu imbert: "Re: Console error messages on start up."
- Next in thread: Glenn Meehan: "Re: Console error messages on start up."
- Reply: Glenn Meehan: "Re: Console error messages on start up."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 08 Jun 2004 21:23:41 +1000
On Tue, 08 Jun 2004 12:13:11 +0200, matthieu imbert wrote:
> this is not really the kernel that tries to load these modules. This is
> the startup scripts that try to load them. Usually, linux distributions
> come with startup scripts that try to probe for your hardware, and then
> automatically load the corresponding modules. This assumes that the
> drivers are compiled as modules rather than included in the kernel. So
> you can - edit the startup scripts to force them to not load these
> modules - recompile your kernel and enable these drivers as modules
> rather than included in the kernel
Do I really need my start up scripts to probe my hardware?
Should I load the modules manually myself or compile them into the kernel.
Debian seems to use a script called discover to probe hardware.
Do I really need to run discover on startup?
- Next message: Christoph Nickschick: "transcode export_mpeg missing"
- Previous message: Tristan Miller: "Re: Convert Farsi (Arabic) PDF to plain text"
- In reply to: matthieu imbert: "Re: Console error messages on start up."
- Next in thread: Glenn Meehan: "Re: Console error messages on start up."
- Reply: Glenn Meehan: "Re: Console error messages on start up."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|