Is this an MSI motherboard? a 6378? If so they had
a onboard firmware issue that causes linux to misread
what kind of interface it is, and uses the wrong driver.
Below is the response I received from Admtek:
For the Lan design in MSI-6378 motherboard, the device ID for AN983B stored
in the EEPROM that embedded in MSI's motherboard is wrong. I attached an
utility that can use to correct this error. Please run this program under
the DOS prompt, power off your machine, then reboot your machine. The
device ID will be updated. Then you can follow the normal procedure to
install the Linux driver. AN983B's Linux driver has been embedded in Linux
kernel version after 2.4.2., or you can visit
www.scyld.com/networks/tulip.html to download the newest released driver.
Please feel free to contact me whether it solve your problem.
My problem at home was with RH 7.3, but chances are 7.2 reads it the same way.
I'm not attaching the utility, as I don't know how this list will handle
attachments.
George
>-----Original Message-----
>From: Keith Mastin [mailto:kmastin beechtree ca]
>Sent: Thursday, November 14, 2002 10:44 AM
>To: enigma-list redhat com
>Subject: Re: Results of On-board NIC...any suggestions?
>
>
>>results of netstat -ar
>>
>>Destination Gateway Genmask Flags MSS
>>Window irrt Iface
>>192.168.0.0 * 255.255.255.0 U 40 0
>> 0 eth0
>>127.0.0.0 * 255.0.0.0 U 40 0
>> 0 lo
>>default 192.168.0.1 0.0.0.0 UG 40 0
>> 0 ehto
>
>routing looks fine
>
>>results of netstat -nr
>>
>>The same as -ar except The Desination columns end with
>>0.0.0.0.0 instead of default
>
>yup...
>
>>results of cat network
>>
>>NETWORKING=yes
>>HOSTNAME=localhost.localdomain
>>
>>
>>I am connection directly to the router. No hub
>>involved. Recently the light on the router has
>>remained on. I changed the setting in the bios to
>>networking=yes and now the light stays on.
>
>... you have an onboard nic... what happened to the 3c509? I
>would just
>work with one of them. rtl8139 is a decent chip for most
>applications, but
>3c509 is rock solid... just needs to be configured on the
>card. Get the
>config tools from the 3com site
>
>>The router is a D-Link DI-614+
>
>Thats a wireless router with 4 LAN ports... which LAN port are you
>connecting to? Try one of the middle ones, just to ensure you're not
>trying an uplink or WAN port.
>
>>i'm only trying to connect to a local machine...for
>>now.
>
>... and you didn't mess with the default configs on the router at all?
>Check the cables, and if they seem to be working fine, then
>replace them
>and test again... could be a physical layer thing happening here.
>
>The other machine you are trying to connect to, is it connected to the
>router with a cable or wireless card? Could be a router config issue
>too... I trust you've been on the phone with dlink's techies?
>
>A note about crossover cables... they are necessary only when
>running a
>line directly between two machines, optional when running an uplink
>between routers, hubs and switches, and a possible point of
>confusion when
>attaching a machine directly into a router, hub or switch.
>
>Could you send an ascii diagram of the network layout so we
>have a better
>idea of what you're dealing with here?
>
>*note to others on the list*: I'm not the one with the problem, Brent
>is... :)
>
>
>
>_______________________________________________
>enigma-list mailing list
>enigma-list redhat com
>https://listman.redhat.com/mailman/listinfo/enigma-list
>