Hi Steve, offtopic Guess I am having an extra senstive day, it being Thursday and not quite Friday (beer sounds so good! But I cannot drink yet..). ontopic I believe I *may* have an answer in terms of the way the modules are laid out. The 2.4 Kernel is different sub-structure to the point that even some of the modules are a different name. I have not yet installed 7.1 (just got it today, if I can find it at my workplace :-)) and have also got an IBM 7200RPM 30GB HD too, so once I am up and running I can let you know if you have not found the answer by then :-). Matt On Thu, 1 Mar 2001, Steven T. Hatton wrote:
On Thursday 01 March 2001 15:49, Matthew wrote:
Steve,
I did not mean to be nasty, if you construed it that way than I apologise. I was really trying to help.
When you do a modprobe 3c59x it will query /usr/lib/<kernel version>/modules.dep, which is a file that points to where your module actually resides and then loads it. If modules.dep cannot find the module then it will give you that error, module not found.
Yast2 will do a lot of that work, which is why I suggested it. I agree, its very nice to know exactly how this works :-).
Again, sorry my original answer was too short.
Matt
Matt, <OT> A quick note on interpretation of the written word. I was, in no way offended. But your response highlights something we need to occasionally remind ourselves of. What we mean to say, and what others get from what we write can be very different. I could not spend nearly as much time on these lists if i could not joke around and express my feelings from time to time. There is always the danger of wording things in such a way as to offend others without meaning to.
I am always sensitive to this, but I don't always get it right. And yes, that little message to Philipp regarding the Radeon *was* a bit of taunting, but he asked for it. {;-)> All in fun, mind you. </OT>
Thanks for the feedback. What you state above is also my understanding of how all this module stuff works. I have been under the impression modprobe will also get information from the /etc/modules.conf and use that to "resolve" module locations. This is why I used the eth0 rather than 3c59x. This alias is difined in the /etc/modules.conf. One thing that gets very confusing about all this is that there seems to be differnt locations for files of the same name in the /lib/modues/<version> directory tree. SuSE put out their modules separately from the kernel, I believe, so as to provide all the possible moduels one might need for a system whose configuration cannot be known beforehand. Add to this the fact that ALSA provides modules, as does XF86, etc. There's got to be a way to get a handle on all this. But I haven't found it. {:-/>
Steve
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq