SlackwareThis Forum is for the discussion of Slackware Linux.
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have two ethernet cards. One runs the eepro100 module and the other needs the rtl8139 module. The eepro100 runs fine but I can't get the other up and adsl to work
I recently installed slackware w/ the 2.4.5 kernel. I used netconfig to configure eth0 which worked succesfully. So, rc.netdevice has the command in it to load the eepro100 module on startup. I installed rp-pppoe-3.5 and used adsl-setup to configure it properly. adsl-start works and I can connect to the internet.
Here comes the fun part.
My 2nd ethernet card uses the realtek 8139 chipset. So, I edited rc.modules to load rtl8139 on startup, but modprobe cannont find that driver. I am still not sure why it can't, but I tried a couple things to solve this problem.
1. I found the driver source and tried to get it to compile with no luck. I did this for several hours before giving up.
2. I decided to recompile the kernel with support built in. I also recompiled several other prior modules as part of the kernel.
The first time I did this and started my new kernel I got a lot of "module not found" errors on startup. Some of them having to do with ppp. The kernel still started and both of my ethernet cards where now detected and configurable. However, I could not get adsl to start up. And it doesn't give me an intelligable error message.
So I recompiled the kernel again and left some of the other modules alone but made sure to include support for my ethernet cards. Started that kernel and had some differnt "module not found messages having to do with iso88* or something like that. Anyway, both etherent cards still work but adsl does not start. I can still boot back into my 2.4.5 kernel and adsl works, but noly one of my ethernet cards.
If you are wondering, this will be a routing machine which is why I need two cards.
I would appreciate suggestions and will provide any specific information you guys might need to help. Thanks.
I would suggest, at least for now, to go back to the 2.4.5 kernel that worked with the Intel NIC and the adsl. Then "modprobe 8139too", you should then be able to config eth1. If all this works like you want, then you can use the "lsmod" command to determine what modules are loaded. That would provide some basic info on what support would be required for a custom kernel without the use of modules.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.