Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have seen many other threads about this, but apparently the outs given won't work for me. I have been trying to solve the problem for a long time but I can't find a solution. That's why I'm here and I hope so could help me.
I am using gentoo 2.6.17, my ethernet card (Realtek RTL-8139) used to work but since I recompiled the kernel (menuconfig not genkernel) to use my wireless network card (Broadcom BCM4318), neither one or the other will work. I tried to load bcm43xx as a module for the wireless network, but the module couldn't be loaded. Since ethernet was a priority, I gave up on wireless and tried to make it work again. I tried to recompile without bcm43xx, with rtl-8139 built-in or as a module.
I would gladly appreciate some help, and give you more information since what's here certainly won't be enough.
Thanks a lot and happy Christmas.
Strange thing that you're using gentoo and have such an old kernel but I doubt that's the issue.
Module for 8139 is indeed called 8139too, and if you've compiled it and all subfeatures it has make sure you installed all the modules with "make modules_install" and boot the right kernel. "modprobe 8139too" should be invoked if you use module.
Also make sure adapter isn't showing under "ifconfig -a" since udev can call it anything it likes, not eth0.
Finally, verify that you have the right device with "lspci"... just can't think of any other issues that can be there)
Strange thing that you're using gentoo and have such an old kernel but I doubt that's the issue.
Actually, it was the last kernel available when my network was still working. I said it was a long time ago
Quote:
Module for 8139 is indeed called 8139too, and if you've compiled it and all subfeatures it has make sure you installed all the modules with "make modules_install" and boot the right kernel. "modprobe 8139too" should be invoked if you use module.
I indeed used make modules_install and I checked the booting kernel too. Yet, I don't remember wether I tested with modprobe when I was compiling as a module
Here's the error message it gives me:
Quote:
FATAL: Error inserting 8139too (/lib/modules/2.6.17-gentoo-r4/kernel/drivers/net/8139too.ko): Invalid module format
Quote:
Also make sure adapter isn't showing under "ifconfig -a" since udev can call it anything it likes, not eth0.
ifconfig -a only shows lo (local loopback)
Quote:
Finally, verify that you have the right device with "lspci"...
Now that's a weird kind of error I've never encountered, but I've never used modules much.
Looks to me either the modules were not installed, their support is not compiled or sources are inconsistent, prehaps make compiles modules against wrong kernel's headers... I'm afraid all I can suggest is getting newer sources, trying to enable everything that looks related anyhow and starting from there.
Prehaps you should also make sure you have all the flags set to right values in /etc/make.conf, like "-march=prescott" (in my case) and pentium4/amd/core2/pc-compatible arch in kernel and looking for any suspicious enviroment vars which can make your kernel install fresh modules somewhere else. Another thing that comes to mind is to try copying module by hand and running depmod to tell kernel to refresh it's info about modules.
Worst thing that comes to mind is that your compiler itself is broken, not that there's any evidence of that...
This is just a wild guess but since your date and time is waayyy off I'd try to see what dates are on the kernel files and set some date later than that.
I am downloading the last release and installing it tonight. If the problem is due to kernel date, this should solve the problem. I'll update the info if the problem still occur.
Thanks for your help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.