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 On Thu, 1 Mar 2001, Steven T. Hatton wrote:
On Wednesday 28 February 2001 23:03, Matthew wrote:
I take it when you said modprobe eth0 you meant modprobe 3c59x?
Have you tried using Yast2 to rediscover the card? Sometimes that works...Has for me on weird issues like this.
Matt
Matt,
I specifically *did* mean *eth0*. That doesn't mean it's the right thing to do. It just means that's what I understand to be the right thing. Based upon my hazy understanding of all this, I believe something is using the eth0 to load the network driver(s). This is why the 'alias eth0 3c5x9' is in the /etc/modules.conf. As regards running YaST to fix this. I seek to know. At this point I would not be happy with merely getting things working. I want to know how they work. That's the whole glory of Open Source. We shall not be subject to black boxs.
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