Redhat 9 Onboard LAN
 

I've been having trouble getting the onboard LAN on the P4P800 to work correctly on my new Redhat 9 system. I downloaded the ASUS drivers off of their website and followed their directions precisely, which basically said to unzip, and run a make load. After entering "insmod 3c2000", the hardware still isn't detected and doesn't come up anywhere. I dual-boot the machine with Win2k and the network seems to work fine there, so I know it's not a hardware problem... anyone know of a remedy? Thanks a lot.

System specs:
ASUS P4P800 Mobo
Intel P4 @ 2.6 GHz
Kernel version 2.4.20-8smp

i have the same problem, and also i cant make the soundmax (digital integrated audio) work. can anyone tell what to do in detail? i am a newbie. thanks...

The 3com problem got pretty big there for a while, haven't heard of anyone having a problem with it on insmod...

What's the output of "dmesg" right after insmod?

Did it get assigned and ethX device number? Gotta remember, RH isn't going to apply settings to it automagically.

The sound is a little different, I can't remember what the module was on this board, can you post the output of:

/sbin/lspci

Cheers,

Finegan

I figured out how to get ethernet working, and I figured I might as well share if anyone else is having the same problem...

I'm not exactly a Linux veteran so feel free to correct me on some stuff (e.g. if my method isn't "safe" or whatnot), but this is how it works for me:

1) Run "make load" and insmod on the driver that comes on the motherboard CD... it's called 3c2000.o.

2) Go to network device controls, and delete all network cards, then add one that's called "eth0" and for the type of card, choose "3Com 3c590/3c595/3c90x/3c980".

3) Select it from the listbox and activate it.

4) In your /etc/rc.d/rc.local file, add the line "insmod <directory which stores>/3c2000.o"

Now, on boot, Redhat will always load the file and internet *should* work.

Keep in mind that during the boot sequence it will still say that "determining IP information for device eth0" failed. That's OK... it'll still work once X starts.