Hi Kevin! It is indeed a tg3. I have another two machines using this driver and there's a package installed for the firmware. I really don't recall if the firmware was installed.
The strange thing that happened on this machine was that the NIC sent packets but never received the replies. I know this because I pinged the default gateway from this machine and was seeing the ARP requests and replies on default gateway for its IP address. Then I added a static ARP mapping and pinged an outside IP address (8.8.8.8). Again, on the default gateway I would see packets going out and returning but never reaching the machine. Odd... I will reinstall again to see if the package with the firmware is installed or not. Thanks! 2015-03-13 21:30 GMT+00:00 Kevin Kwan <kkwan....@gmail.com>: > Eh...this won't happen to be a Broadcom Tigon (tg3), would it? I remember > that due to some licensing quirk, more than a few Linux distros do not > bundle the firmware to make certain NICs work out of the box, at least not > until you explicitly install firmware-bad or whatever the heck the Linux > guys call it. The old Intel e100s and their busted checksumming also comes > to mind. Also, do you have the dmesg/lspci -v off the centos or the Ubuntu > in both cases? > On Mar 13, 2015 3:40 PM, "Miguel Barbosa Gonçalves" <m...@mbg.pt> wrote: > >> Hi! >> >> Installed Ubuntu 14.04.2 (amd64) and the NIC does not work: it does not >> configure through DHCP and it simply does not work if I set a static IP >> address. >> >> Ran FreeBSD 10.1 (amd64) Live CD and the network worked fine. >> >> It seems this machine does not like Linux. >> >> I have no more ideas about what might be wrong. >> >> Anyone has more ideas? >> >> 2015-03-13 16:30 GMT+00:00 Kevin Kwan <kkwan....@gmail.com>: >> >>> Try booting it up using a more modern OS live image (like, say, Ubuntu 14 >>> or Fedora 21), and then go back to CentOS. CentOS itself is kind of old >>> even as far as Linux is concerned. It could be as simple as some >>> internal >>> register not being re-initialized properly after the swap. What does the >>> relevant boot lines look like in the CentOS dmesg? >>> On Mar 13, 2015 12:21 PM, "Steven McDonald" < >>> ste...@steven-mcdonald.id.au> >>> wrote: >>> >>> > On Fri, 13 Mar 2015 15:48:02 +0000 >>> > Miguel Barbosa Gonçalves <m...@mbg.pt> wrote: >>> > >>> > > I recently installed OpenBSD 5.6 on an amd64 platform. Everything >>> went >>> > > smoothly. After installation, at the first boot, OpenBSD updated the >>> > > firmware of some devices. I found this strange... >>> > >>> > OpenBSD runs fw_update(8) on first boot. fw_update simply downloads >>> > firmware packages and installs firmware onto the filesystem (not >>> > directly into the devices that use it) for drivers that need to load it >>> > at runtime. Linux has a similar firmware-loading mechanism, but it >>> > typically ships the firmware embedded in the kernel. >>> > >>> > > I had to reinstall this machine with CentOS and now the NIC does not >>> > > work. >>> > >>> > Did the machine work with CentOS previously? It seems extremely >>> > unlikely that fw_update would be able to break Linux's use of the >>> > hardware, since that firmware is loaded on every boot by the relevant >>> > driver in both operating systems. >>> > >>> > > I reinstalled OpenBSD again and it works. I tried to reflash the >>> NIC's >>> > > firmware and the installer does not recognize the NIC. At the moment, >>> > > the machine only works with OpenBSD... >>> > >>> > Some details as to specifically what you did and what failed, as well >>> as >>> > a dmesg, would be useful here. All I can say with the information given >>> > is that, if your Broadcom NIC requires non-free firmware to be loaded >>> by >>> > the driver, the OpenBSD installer would not be able to use it because >>> > it does not include non-free firmware. >>> > >>> > If fw_update was able to run on first boot, though, it sounds like your >>> > NIC is usable without firmware. Again, a dmesg would help (I'm not even >>> > sure which of the three Broadcom NIC drivers in OpenBSD you're using).
