Hello,

I'm running SLES 10 on a PowerEdge 1300 server that has a Intel EtherExpress PRO/100+ Server Adapter (PILA8470B) in it AND I added a 3Com 3C905B Fast Etherlink XL 10/100.

At the beginning, I started using only the EtherExpress and I was able to see it in YaST, but when I was doing a ifconfig, I only see my lo that is my loopback. I'm a noob and I tried many thing and searching the web and anything. I know that SLES 10 is fully compatible with a PowerEdge 1300 server.

I setup this EtherExpress DHCP and static with our network configuration, but I'm never able to see it when I do a ifconfig... I think my hub that I have is only a 10mbit... is there anyway to change the link speed and duplex in YaST somewhere?

This is my reason why I installed after that a 3Com 905B that is one of the most standard network card and compatible. I can see it in YaST and when I do a ifconfig, I see a eth0 that is that one.

There is one thing that I suspect is that it's not installed properly or something because the MAC of my 2 network cards are the following (they don't seems to be right MAC):
0000:00:0e.0 for my 3Com
0000:00:10.0 for my EhterExpress
(I took those MAC from my "Network Card Configuration Overview" in YaST)

I know that MAC addresses usually start the first 4 hex digits are for the company and both are 0000 and I got a 3Com and a Intel so they should be different...

Anyway, when I setup my 3Com DHCP, in my /var/log/messages I got messages like:
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11

I never have any DHCPOFFER

Oh yeah, by the way, I'm using too another station that I have a P4 with 512SDRAM running SUSE 10.1 and I never had those problems ...and it's working DHCP and Static.

If I forgot any infos, just write me back I will give them to you...I'm not use with saying all the details!

Thanks,
Philippe

1. Likely scenario is the cards aren't being configured by the kernel. This was an acpi-related issue for me. Try turning acpi=off on your grub options. You should be checking logs in /var/log/kernel, /var/log/messages and so on too.

2. Less likely: Depending on the chipset used on the cards, you may not have a reliable driver. I've had that happen too with NIC's.

thanks mpapet!

turning off the acpi worked for me! I just never knew where to turn off the acpi ...now I found out..!!

Philippe