Bugzilla – Bug 132472
Recognised network card failing to initialise properly
Last modified: 2005-12-19 22:05:35 UTC
Fresh install 10.0 on IBMThinkpad 600X previously running 9.2 Cardbus Network card (RTL8139 chipset) auto detected and configured as per 9.2. However DHCP request appearing to not be responded to, so no IP, but DHCP server log shows request received and IP allocated, and interface lights do blink as if there is activity. ifconfig -a shows zero bytes in and out on eth0. Performing ifdown eth0 ; ifup eth0 and then ifconfig -a shows no change to the byte count for eth0, *but* the byte count for lo goes up by about the amount I would expect for a DHCP request. lspci shows the card listed as I would expect. Interestingly enough booting with a live eval copy of Kubuntu gives similar results, but Knoppix 4.02 works perfectly. Knoppix 4.02 uses the older kernel 2.6.12, so is this a .13 kernel issue? I also notice that hotplug seems ineffective, is this related?
Please run hwinfo and attach the output to this report. Please also check which driver is being used for this card. This smells like a PCMCIA issue... assigning to the Mobile devices team
What do you mean with "hotplug seems ineffective"?
Tim, please attach the output of hwinfo --netcard ifstatus eth0 getcfg eth0 And please answer the question from comment 2
I have the card set to initialse on "hotplug" but it only seems to initialse on boot up. Also USB memory sticks don't seem to be noticed (baaed on tail -f /var/log/messages for both instances) N.B. this thinkpad does not have full ACPI, but only APM. Previous versions of SuSE have noticed this but 10 doesn't seem to (based on scanning through dmesg) Will try to get the requested info, but given the lack of pen drives being recognised etc, its difficult to get the info out to a machine with a network connection!
Created attachment 59777 [details] requested shell dumps These files are the requested outputs of the shell commands. The Static-ping op shows the before and after state of issuing a ping once an ip has been set statically. Note the byte count increase on the loopback if and nothing on the eth0!!
try also to boot from Failsafe boot menu or try to add pci=noacpi as additional parameter on boot prompt.
Tried pci=noacpi Card initially not shown, but after changing parameters in Yast all came good. However does using this option mean that I cannot hotplug pcmcia cards now?
No, it only ignores the BIOS ACPI tables for IRQ routing information. If this option is working, it is usually a sign for a incorrect BIOS IRQ routing table, we cannot do so much against such problems, ask your notebook manufacturer for a BIOS update.
Shame is, once I had got a network connection, I performed an online update, and now it wont even boot :(......
Also failsafe Mode does not boot ? Since this is independ of the network card issue, please open a new bug and supply more infos about the HW and when exactly the booting process stop (Press ESC after the boot menu).
You could also try acpi=force with the new kernel.
acpi=force pci=acpi enables the system to boot with network connectivity, However hotplug still does not work (i.e. plugging in pcmci card does not cause system to initialse it, no lights no log messages)
You can try apic as additional boot option.