Otto Wyss wrote:
Ooh! modconf! It wasn't installed (how would I know?).
After each install of a Debian system I always install "modconf", "vim"
and "fbset" since I can't believe any sensible system is usable without
them. Especially modconf is a must. Most of the time I add "most" to get
rid o
> Ooh! modconf! It wasn't installed (how would I know?).
>
After each install of a Debian system I always install "modconf", "vim"
and "fbset" since I can't believe any sensible system is usable without
them. Especially modconf is a must. Most of the time I add "most" to get
rid of "more" and "les
ction?
In any event, I'm much further ahead than I was before. Thanks.
/icebiker
- Original Message -
From: "s. keeling" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 09, 2004 02:00
Subject: Re: Loading kernel modules at startup
> In
Incoming from John Van Lierde:
>
> I'm trying to get lm_sensors working. I'm at the point where it works when I
> manually load the modules:
>
> modprobe i2c_sensor
> modprobe i2c_piix4
> modprobe w83781d
>
> and I can read temperatures and voltages and everything.
>
> But I'm absolutely
John Van Lierde wrote:
But I'm absolutely baffled as to how to get the modules to load
automagically at boot. There are a bunch of utilities (some apparently
obsolescent) and files (all of which seem to say that they are generated and
not to be edited). I've poked through all the man pages that see
5 matches
Mail list logo
