getting rid of modules again

marder7 · n00b Joined: 15 Nov 2002 Posts: 56

Hi!
Maybe this is a stupid question but there is one thing I really haven't understood yet:
An entry in m/etc/modules.autoload (like "ide-scsi" e.g.) loads the module at boot time. Ok so far.
BUT: Deleting the entry again (or putting "#" in front of the line) seems to have no effect! The module still loads on booting.... forever! Even deleting the module from /lib/modules/... doesn't help (leads to error messages).
Where's the trick? I really don't think that I can be the admin of my system if I can only DO things but not UNDO them again...

Thanks for helping
Martin

rac · Posted: Sun Dec 15, 2002 8:44 pm Post subject:

Is something in /etc/modules.d causing the problem?
_________________
For every higher wall, there is a taller ladder

marder7 · n00b Joined: 15 Nov 2002 Posts: 56

That's where I looked, too, but I couldn't see any problem there.
Yesterday I tried to change modules.autoload in a different way: I reactivated the entries for modules I'd like to get rid of, and I commented out the new entries for modules I currently use.
Result: Of course the old modules still loaded like before, but the new modules didn't.
So it seems that is has something to do with the dependencies between the modules themselves, deps which are detected by depmod at boot time.
Could this be true?
If so, how can I control it?

Regards
Martin

rac · Posted: Mon Dec 16, 2002 9:51 am Post subject:

Two things you could try running are "update-modules" and "env-update".
_________________
For every higher wall, there is a taller ladder