| 1 |
On Sunday 26 May 2002 22:59, Rowboat wrote: |
| 2 |
> Hanez, |
| 3 |
> Thanks for this important suggestion. I made sure alsa was removed from |
| 4 |
> all runlevels using rc-update, then added alsasound to the boot runlevel. |
| 5 |
> I rebooted and still get the same errors. I DID find a module in |
| 6 |
> /etc/modules.d called 'alsa.old' that was getting loaded during boot. (I |
| 7 |
> found its entry in modules.conf, and traced it back to modules.d) I removed |
| 8 |
> that file completely to a different location, but still get the exact same |
| 9 |
> errors on boot or 'modprobe -a'. |
| 10 |
> |
| 11 |
> If an old version of ALSA is still on my system, where would it be? I |
| 12 |
> would like to delete it, or else 'emerge unmerge alsa' as a last resort. |
| 13 |
> |
| 14 |
|
| 15 |
Your alsa modules are somewhere in the /lib/modules/2.4.18/ tree. Probably in |
| 16 |
/lib/modules/2.4.18/kernel/sound/ |
| 17 |
|
| 18 |
The easiest thing to do is to remove the whole 2.4.18 tree and do a new |
| 19 |
make modules_install in your linux source tree again. That ensures there are |
| 20 |
no modules lingering around (taken you didn't clean your build tree, in which |
| 21 |
case you of course first need to make the modules again). |
| 22 |
|
| 23 |
After that you need to do a depmod -a |
| 24 |
|
| 25 |
BTW. modprobe and depmod only look to modules.conf (which is generated by |
| 26 |
modules-update) so check that file wheter it is up to date, if not check the |
| 27 |
modules.d dir. |
| 28 |
|
| 29 |
Paul |
| 30 |
|
| 31 |
-- |
| 32 |
Paul de Vrieze |
| 33 |
Junior Researcher |
| 34 |
Mail: pauldv@××××××.nl |
| 35 |
Homepage: http://www.devrieze.net |
Archives