Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a ASUS P4P800 On-board 3COM network card that I can't get the driver installed on RedHat 9 Linux.
The instructions say to:
Type "make load" to load the driver or "insmod 3c2000.o but all I get is
Function Declaration errors and parameter errors after typing it.
I am sure it is the correct driver, I retrieved it from ASUS website - Linux driver. (Should work for RedHat, right)
Okay, I uninstalled the driver and re-installed the driver without an error but it doesn't work.
After installing the driver, I have a link light. I had to use "ifconfig eth1 up" to start the driver, but it is not retrieving info from DHCP.
After running lspci I get:
ok, so you have the Dlink-card in addition in there. Is it possible that you plugged the cable into the wrong Ethernet port? It could be that the Dlink happens to eth1. That depends on the load order of the drivers.
I had wanted to see the output of
not just "lspci" which gives you the interpreted version (and that fails because your lspci database is older).
and while you are at it, also show us your lsmod output and your /etc/modules.conf file.
ok, my mistake, the command should have been lspci -x, but I got what I wanted.
Your eth1 is a 3com 9400 "Marvell" Gigabit interface.
I think I read your initial post right that you got a precompiled module from 3COM. I see that the source code is available. You may want to recompile it with your kernel.
And of course, for the time being you could just use the other Dlink interface eth0. The 8139too driver works. I know it's a workaround, but it'll get you going for now. Once online, you can download whatever you need much easier.
Did you ever post the actual error messages when you insmod the module? Did you try moving it to the right place in the kernel tree in /lib/modules/... , run depmod -a, and modprobe, not insmod it?
Maybe it's as simple as loading another module that brings in the missing functions, much like 8139too needs the mii module.
Okay, I will give that a try mlp.
In the meantime, I dropped in another hard drive and tried an installation of Fedora Core 4, just out of curiousity. Well, it detected both cards but only set up the Dlink properly and working. While Fedora loads, I get the following error:
Device eth0 has a different MAC address than expected, ignoring. [FAILED]
What do you suppose that means?
... actually, I found out what it means. I had to spoof/probe the MAC address for it to work properly. The On-board card seems to be working properly now. Hmmm... well... fedora looks and feels like RedHat, so maybe I'll just continue using Fedora. It seemed to do the trick. Actually, it was likely Fedora installed the driver properly... something I couldn't do with RedHat 9, manually.