I’m trying to install Suse 11 on a Gateway Profile 4 computer which has an integrated Intel PRO/100 VE network card.
I am able to perform a network install of Suse 11 with no problem using the boot CD. However, the resulting new, as-installed Suse 11 installation is unable to connect to the internet.
The network card is identified, and the e100 module is loaded. However, DHCP times out, and I am unable to ping any address.
Any help is appreciated.
The logical place to start is in Yast - Network Devices - Network Settings
and check your device in there. But I’m guessing you have already done that?
Yes, I have tried.
Actually, my symptoms are exactly like the ones described a couple of posts later in this list by supernova7. His email has drawn a lot of people looking at it, so I think we are not the only ones.
I have tried setting up static routing in YAST, using DHCP, with and without IPV6. None of that makes a difference. I’ve also tried re-enabling the network using ‘rcnetwork restart’. When I do this, the network card comes up, but dhcp times out.
The trouble with DHCP failures is that they are often caused by simpler networking failures.
The first step would be to configure an address on the interface manually and see if you can ping the default router. Alternatively (if your admin does not like that test idea), look at ‘man arping’, and try using it to see if you can get ARP responses for other devices on the wire.
If you can’t arping other hosts, then something is wrong at the link layer (bad cable, bad nic, bad driver).
After searching through lots of posts (not on this site) on the e100 driver, I found the following fix:
in the bootloader, set the following option
acpi=off
Everything works fine when I do this.
hi,
i got the same probleme with a ibm thinkpad x30 but i wouldn’t miss acpi, the bootloader option irqpoll workes fine for me.