[ILUG] Recovering from module problems, debian etch

[Cathal A. Ferris]

I did something silly. I managed to break my debian etch system very 
effectively today.

I made the mistake of installing a second wireless card (rt2460pci), and 
in the process of getting it running I ran the make install script in the 
sourceforge module source code download, without thoroughly reading the 
instructions. I'm not entirely sure *exactly* what happened, but the end 
result is that the vast majority of the previously installed madules 
refuse to modprobe, with various warnings and complaints about unknown 
symbols and such like.

I managed to get my first wireless card back up and working, but that is 
as far as my success so far has gotten me.

My usb mouse no longer gets activated (usbhid is in alright), nvidia's 
binaries no longer want to go in, my alsa modules complain to 2 pages 
worth of output of missing stuff before failing, and various other things 
appear to be wrong. Instead of the 50 or so modules that were in and 
working this morning, I have about 15.

Of course I didn't have a copy of the lsmod output from before, nor had I 
/etc backed up anywhere useful.

How should I go about rebuilding my modules.autoload and what else do I 
need to do?

I'm feeling a bit silly!

Other relevant details; amd64 system, debian etch amd64 SMP.

Thanks,
Cathal.

--
Cathal Ferris			+353 87 6438725
pio at csn.ul.ie			http://www.swibble.com