Start a Conversation

Unsolved

This post is more than 5 years old

S

8673

November 4th, 2003 09:00

PE650 & no network

Hi,

I'm using under linux RH8.0 a Power Edge 650 with Intel EtherExpress 1000 ethernet card.

The card is detected, network is green and well configured but it seems that no data is going out...

My questions :

- are the drivers form RH8.0 work ?

- are the drivers work with ethernet 100Mo ?

Thx

Simon

November 4th, 2003 12:00

I just install RH9.0, same issue

Will it change anything if I patch the kernel ? (actually : 2.4.20-8) I read thart the patch correct an IDE bug on PE650

Thx for any response

November 4th, 2003 13:00

The lastest e1000 drivers seems to be design also fort 82546EB

I'll try them.

November 4th, 2003 13:00

My NIC is Intel 82546EB, but I do not found any drivers for this card for Linux.

RH9 use e1000.o driver

Does anynone knows where can I download these drivers ??

Thx,

Simon

November 4th, 2003 14:00

found & resolved, link corrupt :((((((

Simon

1 Message

November 18th, 2003 13:00

My 650s were a VERY interesting issue, and I thought you guys should be aware -- Originally (as the machine came from Dell), the SCSI card was in the top PCI slot, while the Intel e1000 NIC was in the bottom slot.  Red Hat 9 detected the card during installation, but Red Hat 7.3 did not detect it until the Linux Kernel was upgraded.  Upgrading the driver to the newest one had no effect in either case.
 
eth0 was set to IP 128.241.245.x, subnet 255.255.255.224, GW 128.241.245.97, Broadcast 128.241.245.127, and was plugged into a Cisco Catalyst 2924XL switch.  e
 
eth1 was set to 192.168.0.x, subnet 255.255.255.0, and plugged into a 3COM OfficeConnect 16 port switch.
 
eth0 could neither ping out, nor be pinged.  eth1 could ping other Linux servers, but not Win2K or NT machines, and they could not ping it either. 
 
After I swapped the location of the NIC from the top PCI slot to the bottom, everything works perfectly!  No driver updates, nothing.  This sounds really bizarre, and I can't explain it fully, but I'm sure another Dell client will experience a similar issue and wanted to make you aware of it, and was wondering if there was an explanation as to why this might be.
 
No Events found!

Top