Hi Folks, Here's a silly question that's been bugging me for a while now. I've tried a bit of google hunting, but there's either very little relevant info out there or I haven't stumbled upon the right key words to find it.
In the old days, I always had to load kernel modules explicitly. Then, when slack 10.0 came along, I was surprised to find that on a fresh install it managed to load everything all by itself. But, the moment I switched over to my own kernel, that stopped happening. At the time I wasn't willing to put any time into figuring out what happened, since it was easy enough to just load things by hand. (And I had a suspicion it had something to do with switching to the 2.6 series.) Today I just installed slack 10.1 on a new (to me) machine, and it happened again. Everything was magically auto-detected. Then I built a new kernel (by copying the 2.4.29 source, adding an extra-version suffix, building as usual, and adding a new lilo entry). Once again, all the nifty auto-loading of modules stopped happening. If I boot the original kernel, it still works fine. Anyone understand what's happening? How does the stock kernel automatically load modules in the first place, and why does switching to a new kernel cause it to stop working? - Erik _______________________________________________ Slackware mailing list [email protected] http://www.kurtwerks.com/mailman/listinfo/slackware
