Has anybody else had problems with modules in the 2.4.2 on the SuSE site? Just when I thought I had a clue, I realize I'm lost. I compiled the kernel with 3c59x as a module. I can see the 3c59x.o, and I have alias eth0 3c59x in the /etc/modules.conf. This works in the 2.4.0 kernel, but not in the 2.4.2 kernel. Is it possible that we need to upgrade the modutils to get this to work? TIA, Steve
The newest modutils is 2.4.2 which you can get from kernel.org. Check to the recent ac's on 2.4.2 (I believe its ac4) as these may point out any known issues. What problems are you getting? Matt On Wednesday 28 February 2001 05:37 pm, Steven T. Hatton wrote:
Has anybody else had problems with modules in the 2.4.2 on the SuSE site? Just when I thought I had a clue, I realize I'm lost. I compiled the kernel with 3c59x as a module. I can see the 3c59x.o, and I have alias eth0 3c59x in the /etc/modules.conf. This works in the 2.4.0 kernel, but not in the 2.4.2 kernel. Is it possible that we need to upgrade the modutils to get this to work?
TIA,
Steve
On Wednesday 28 February 2001 21:19, Matthew wrote:
The newest modutils is 2.4.2 which you can get from kernel.org. Check to the recent ac's on 2.4.2 (I believe its ac4) as these may point out any known issues.
What problems are you getting?
Matt
Hey matt, Thanks for the pointers. I'm actually trying to be a good boy and not take my system too far away from SuSE's design this time through. IIRC there are some dependency issues with the RPMs from ftp.kernel.org. I don't even know what I have on this 7.1 system as regards modutils. One of my problems is that when the system boots or when I do a modprobe eth0 I get an eth0 not found error. I looked and 3c59x.o is in a few differnet places under the 2.4.2 modules tree. I can't say I've been completely thorough, but I believe it corresponds 1-to-1 with the 2.4.0 instnaces. I'm using the same modules.conf for both boots (wouldn't it be nice to have different ones for different boots?) Of course the result of this is that the network connection doesn't work. I had been building this fine with 7.0, but I was using updated modutils. Steve
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 On Wednesday 28 February 2001 06:56 pm, Steven T. Hatton wrote:
On Wednesday 28 February 2001 21:19, Matthew wrote:
The newest modutils is 2.4.2 which you can get from kernel.org. Check to the recent ac's on 2.4.2 (I believe its ac4) as these may point out any known issues.
What problems are you getting?
Matt
Hey matt,
Thanks for the pointers. I'm actually trying to be a good boy and not take my system too far away from SuSE's design this time through. IIRC there are some dependency issues with the RPMs from ftp.kernel.org. I don't even know what I have on this 7.1 system as regards modutils.
One of my problems is that when the system boots or when I do a modprobe eth0 I get an eth0 not found error. I looked and 3c59x.o is in a few differnet places under the 2.4.2 modules tree. I can't say I've been completely thorough, but I believe it corresponds 1-to-1 with the 2.4.0 instnaces. I'm using the same modules.conf for both boots (wouldn't it be nice to have different ones for different boots?) Of course the result of this is that the network connection doesn't work.
I had been building this fine with 7.0, but I was using updated modutils.
Steve
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
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
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
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
participants (2)
-
Matthew
-
Steven T. Hatton