Results 1 to 10 of 20
I have kernels 2.4.20 and 2.6.0 installed on my system.
When I boot through 2.4.20 I get a message saying
8139too device eth0 does not seem to be present, delaying ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 01-05-2004 #1Linux User
- Join Date
- May 2003
- Location
- CA
- Posts
- 370
kernels 2.4 qnd 2.6.0
I have kernels 2.4.20 and 2.6.0 installed on my system.
When I boot through 2.4.20 I get a message saying
8139too device eth0 does not seem to be present, delaying initialization.
and my ehternet card is not loaded.
This used to work earlier. I installed module-init-tools for 2.6.0 and something got screwed up.
The eth0 card comes up successfully if I boot through 2.6.0
After booting thru 2.4 if I do a insmod 8139too i get errors saying "unresolved symbol in some .o files".
Any idea wats wrong? I removed the module-init-tools package and re-installed modutil package but still no luck.
- 01-05-2004 #2Linux User
- Join Date
- Jun 2003
- Location
- Huntington Beach, CA
- Posts
- 390
I was led to believe that module-init-tools was backwards compatible with the old modules. Maybe recompile module-init-tools and remake the 2.4 modules?
- 01-05-2004 #3Linux Engineer
- Join Date
- Nov 2002
- Location
- Queens, NY
- Posts
- 1,319
Are they backward compatible? I thought that they weren't which was the reason why I still kept modutils.
The best things in life are free.
- 01-05-2004 #4Linux Engineer
- Join Date
- Dec 2002
- Location
- New Zealand
- Posts
- 766
yeah it is.
i only have module-init-tools and ive got 2.4.23 running fine. (i know, i should be using 2.4.24 but i havent been stuffed downloading it yet.)
- 01-06-2004 #5Linux User
- Join Date
- May 2003
- Location
- CA
- Posts
- 370
yeah but the problem is after I downloaded and installed module-init-tools
somehow I screwed up my eth0 interface while booting thru 2.4
When I boot thru 2.4 I get a message saying
"8139too does not seem to be present..delaying initialization"...
i tried everything...re-installed modutils, installed 8139 again as a module
but nothg works...i'm stumped totally!!
- 01-07-2004 #6Why not compile it directly into the kernel?
Originally Posted by nikhil
- 01-07-2004 #7Linux User
- Join Date
- May 2003
- Location
- CA
- Posts
- 370
yes...thats wat i'll do...i jus wanted to know if there was any easy way out...jus by compilin it again using insmod or somethg...but i guess not!!
- 01-08-2004 #8Linux Guru
- Join Date
- Oct 2001
- Location
- Täby, Sweden
- Posts
- 7,578
module-init-tools is not compatible with modutils. However, if you install it correctly, it will back up the modutils programs to names like /sbin/modprobe.old. Then, if they discover that a 2.4 kernel is running, they will exec the modutils version instead. However, module-init-tools themselves aren't backward compatible; they just exec the modutils version instead.
- 01-08-2004 #9Linux User
- Join Date
- May 2003
- Location
- CA
- Posts
- 370
yes, module-init-tools did create .old files for the other module
executables but still no luck....
i guess i'll jus re-compile the whole thing again and hopefully it'll work.
- 01-09-2004 #10Linux Guru
- Join Date
- Oct 2001
- Location
- Täby, Sweden
- Posts
- 7,578
What happens if you modprobe 8139too?


Reply With Quote
