According to Tom Allison,
> Tony Godshall wrote:
> >According to Tom Allison,
> >
> >>Tony Godshall wrote:
> >>
> >>>According to Kent West,
> >>>
> >>>
> >>>>Tom Allison wrote:
> >>>>
> >>>>
> >>>>
> >>>>>Hello,
> >>>>>
> >>>>>I replaced my motherboard after an accident.
> >>>>>
> >>>>>Everything mostly works, but a lot of the on board hardware (sound in
> >>>>>particular) isn't the same as the old board.
> >>>>>
> >>>>>I know the installation process (sarge installer) does a great job
> >>>>>finding out what I have and setting it up.
> >>>>>
> >>>>>How can I "re-discover" the hardware on this machine and remove/add
> >>>>>modules accordingly?
> 
> 
> <snip>
> 
> 
> >>While systems may do some kind of auto-detect of the hardware when they 
> >>start, I find it difficult to believe that they would actually go 
> >>through and rebuild the modules conf files at every boot (auto config 
> >>rather then auto-detect).
> >
> >
> >1. comment out everything in /etc/modules (those entries
> >have nothing to do with this system)
> >
> 
> I already have discover installed.  IFAIK it came with the initial 
> installation (sarge installer RC2 based) and has been there ever since.
> 
> I should expect discover to rebuild the modules.conf file?
> (sounds like "Yes").

That is not its function.  Its function is to match pci 
self-identification ids to kernel modules and load them.

At the top of my modules.conf, I have this line...
### This file is automatically generated by update-modules"

modules.conf is rebuild by update-modules, which is run
automagically when you install kernel modules from a debian 
package.  If you install kernel modules manually, you need 
to run update-modules manually.

> I take it discover is not able (ever or yet) to modify the modules.conf 
> file based on new/different hardware detected?  This is a bit of a 
> stretch and won't apply to 99% of the userbase, but I just thought I 
> would ask.

discover is not intended to update modules.conf.  It doesn't
AFAIK change any config files at all.  Discover runs typ. after 
/etc/modules is processed and so whatever you customize is not 
affected.  But I'm no expert here: I've not had much need to 
customize because I've had good luck by updating kernels and 
discover anytime some new card doesn't work... if the kernel 
supports it discover has generally been able to load the right 
module.

-- Tony Godshall 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to