Re: Cannot configure Sound Card, RH9, New Box
From: Juhan Leemet (juhan_at_logicognosis.com)
Date: 08/27/04
- Previous message: Ed Skinner: "Adding new USB Storage device?"
- In reply to: Dances With Crows: "Re: Cannot configure Sound Card, RH9, New Box"
- Next in thread: Joseph Michael Daigle: "Re: Cannot configure Sound Card, RH9, New Box"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 27 Aug 2004 15:25:13 -0200
On Fri, 27 Aug 2004 13:03:27 +0000, Dances With Crows wrote:
> On Thu, 26 Aug 2004 23:51:03 -0400, Nico Kadel-Garcia staggered into the
> Black Sun and said:
>> "Dances With Crows" <danSPANceswitTRAPhcrows@usa.net> wrote in message
>> news:slrncit3uj.hq9.danSPANceswitTRAPhcrows@samantha.crow202.dyndns.org...
>>> > I was able to install and configure drivers for my SATA controller
>>> > card. And it works when I initially loaded the module. However, I
>>> > cannot get RH to detect the device and load the module on startup.
>>> Redhat and derived distros have a script that's always executed on boot.
>>> It's /etc/rc.d/rc.local . Add the modprobe command you need to that
>>> script, and the module will be loaded.
>> Don't muck with rc.local. Honest.
>
> Huh? rc.local or boot.local is explicitly there to *be* mucked with.
>
>> If you want to hand-load it at boot time, create an init script in
>> /etc/init.d/{whatever}, and use the "chkconfig" command to enable or
>> disable it at certain runlevels. That way you can turn it on or off at
>> will by running the same init command after the sytem is running. This
>
> ...is overkill. chkconfig is a Redhat-specific command, and most
> newbies get confused when you try to explain the SysV init setup to
> them. The stated goal for this ("modprobe sata-foo && mount /dev/blah
> /mnt/somewhere") certainly doesn't require a full init script.
SuSE-9.1 has /sbin/chkconfig program. I have found it useful for easily
turning services on/off, once you get the hang of it. The problem with
tinkering with rc.local and boot.local is that it is really easy to get
things wrong and then get snarled up on irrelevant trivia. The chkconfig
checks its arguments and changes "states" (er, configurations) cleanly.
The init script approach is the "standard" way to start up (and shut down)
services. Might be good for the OP to learn how to do that?
BTW, I've been computing (including some real-time embedded stuff) for a
_long_ time. I still find Linux sound to be much harder than one would
think it should be. I think it's a problem of "combinatorial explosion"
with all the options and choices, and most (arbitrary ones) don't work.
>> That way, if you have a problem with the driver, you can unload it in
>> a well-defined fashion without hand-editing a critical system file,
>> namely rc.local.
>
> rc.local / boot.local isn't a critical system file. It's a shell script
> that's run when the system boots. In a default distribution, it has
> nothing in it but #!/bin/bash and a bunch of comments describing its
> function. /etc/inittab and /etc/fstab are critical system files. If
> you have a problem with a kernel module, you'll have to rmmod it.
Maybe "critical" was a little extremer? Still, you don't want to get them
wrong or you'll get really snarled up (usually with something maddening).
-- Juhan Leemet Logicognosis, Inc.
- Previous message: Ed Skinner: "Adding new USB Storage device?"
- In reply to: Dances With Crows: "Re: Cannot configure Sound Card, RH9, New Box"
- Next in thread: Joseph Michael Daigle: "Re: Cannot configure Sound Card, RH9, New Box"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
