Bugzilla – Bug 151826
FSC Lifebook S7020 doesn't get DHCP address during SLP installation attempt
Last modified: 2006-02-21 13:52:26 UTC
In the R&D network I am trying to install an FSC Notebook with Broadcom Gigabit ethernet card (tg3 driver) via SLP. The installation ends with a generic error message: Some debugging info: Console 3 says (only relevant output): insmod /modules/tg3.ko Ok, that seems to have worked. :-) [...] Sending DHCP request to eth0... no/incomplete answer. [...] I think I pretty much have ruled out network problems. I cross-changed the ethernet cable with another machine, and things didn't change. The other machine gets a DHCP address during installation, the FSC machine doesn't. Manual installation with step-by-step configuration of an FTP installation source works fine.
This tg3-module appears to be some sort of a hacked driver, there was at least one report about this besides yours. Are you sure the driver does support your card? Please attach boot.msg and check out the messages in the syslog.
Yes, obviously the driver supports the chipset. I can install via FTP after manual setup. During manual setup I click on "configure via DHCP", and that works fine. It's only during installation in graphical mode (staring from the mini ISO) that things don't work. So boot.msg and syslog of the running system probably don't help much, right?
Not sure if that's in any way related, but the network card has problems getting a DHCP lease with Network Manager. I've seen the same issue on an HP with the same chipset. Good old ifup-based configuration works fine though. I'll report the NetworkManager bug later, after some more testing.
Joachim, it would be nice if you could attach some more debug information, specially kernel messages output by tg3.ko while it is loaded. If the driver works fine with ifconfig, it might not be a problem with the module itself, though.
Appears to be the same problem as in #151187
Yes, #151187 sounds familiar. As I've pointed out in comment #2, I can get a DHCP lease if I use the ncurses step-by-step installation, not the one started from the grub installation screen. Also, later in the running system I don't see problems with DHCP. So it must be some strange combination of issues that only become obvious during installation.
Let's ask the kernel maintainers for help - seems to be an issue with the initrd. Also check out #151187
I do not think it is any kernel/initrd problem, since it works in manual mode. I do not think this will help in that case,but does it work better with apic as additional boot parameter ?
OK then our new APIC handling is successful.