Red Hat Bugzilla – Bug 467579
Installer fails to connect with Broadcom BCM4401
Last modified: 2008-10-28 18:13:41 EDT
Description of problem:
During installtion, F10 beta does not connect to network either via DHCP or via static configuration.
Version-Release number of selected component (if applicable):
During the installation.
Steps to Reproduce:
1. Run installer
2. Try to connect to network via DHCP or using static adderss
does not connect
01:09.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)
After installation I can use system-config-network to connect successfully.
I've installed other Fedora versions from FC3 through F8 without encountering this problem.
Don't seem to be able to edit the last comment. Just wanted to add that those installations were on the same hardware. Dell Dimension 2400.
if s-c-network works, why is this a bug then?
It does not work *during installation*.
When I tried to connect to additional repositories, it failed to secure a network connection. I tried repeatedly using both DHCP and static assignments. I thought it might have been a hardware failure (unlikely, though, since the machine worked fine before I tried upgrading) or a driver problem (which also doesn't seem true since s-c-network works after installation from the command line).
As I say, I've installed lots of copies of Fedora and never had a problem with this machine getting a network connection. (I've often used NFS installs without a hitch, for instance.) In this case I was installing from the DVD and found I was unable to connect when adding repositories at the end of the installation sequence.
assigning to anaconda due to "during installation".
Can you copy log files from /tmp (*.log) during installation and attach them to this bug? Copy them to a USB flash drive or something similar.
You mean rerun the installer and capture them during the installation process? Right now all I have is firstboot.X.log and an empty yum.log in /tmp and install.log and install.log.syslog in /root. I take it there's some other log that gets written during installation and then deleted?
If I can mount an NFS share as /tmp during installation I'll give that a try. We had a USB key floating around here at one point, but I haven't seen it lately. Any hints on what log I'm looking for and when I might be able to capture it?
If you can perform the installation again passing loglevel=debug as a boot: parameter, that would generate log files that are most useful to us.
The install.log and install.log.syslog files are the most useful to us.
If you can provide the data requested in comment #8, please reopen the bug and I'll take a look at it.