Well, okay. The assumption is OpenBSD might/might not have done this to the hardware. Okay, I am an SA, I am a Linux old-hand and an OpenBSD newb, I like solving problems, let's take this on - frankly, the Linux guys will most likely send him back here if he asks it on their lists.
Okay, first of all, the reason why I bought up the Broadcom Tigons - they are temperamental as a family. They are under-engineered and over-featured, and I had a history with them dealing with the Dell hardware in my gigs. They are one of the first Gigabit NICs in the consumer market, it's one of the first to power down for power saving (ask any Windows helpdesk and they'll tell you it's a common issue with seemingly "dead" NICs coming back after a power cycle, due to some weird ACPI don't-wanna-get-out-of-bed issue. It's a frustrating one for sales guys and execs on the road), they are one of the first to implement auto MDI-X, which does not always work the way it's expected. The Tigons also require the 3rd party firmware so some Linux distros don't work with them out of the box. Even if it does it could be a hit-or-miss based on the machine's BIOS, its power state, the specific Linux kernel release, the firmware present, all sorts of factors. Hell, I have even seen a busted PoE switch zap the ESD fuses on the switchport (seen that happen too). Frankly, I am not surprised by this. Okay, in order for us to help, we need you to provide us with a few things. For example - dmesg logs on the Linux distributions that you have tried (so we can tell if it's started up/drivers loaded properly), lspci logs (to see if there is a weird issue on the card itself), and poke around with ethtool -T on the Linux side (to see if there is an issue layer-2 downwards). I am more than willing to say that this is a Linux issue, but just like back at work, it's much more satisfying to trace the issue back in someone else's court and point that finger irrefutably back in the other direction. On Sat, Mar 14, 2015 at 8:20 AM, Stuart Henderson <s...@spacehopper.org> wrote: > On 2015-03-14, Miguel Barbosa Gonçalves <m...@mbg.pt> wrote: > > No dia 14/03/2015, às 01:50, Nick Holland > ><n...@holland-consulting.net> escreveu: > > > >>> On 03/13/15 15:38, Miguel Barbosa Gonçalves 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. > >> ... > >> > >> *looking around* As this is an OpenBSD list, I think it sounds like it > >> is working just fine. ;) > > that's not *entirely* helpful..but since the problem only exhibits itself > on other OS, they might be better placed to help diagnose the problem. > > > It was working fine before installing OpenBSD, it works with OpenBSD > > and now it does not work with Linux. > > Have you tried using the exact same Linux version that was working before? > > > After this I am afraid of running OpenBSD on any machine. I will > > surely not do it. > > > > I am not trying to create a war here. This is just how I feel because > > I have a 1U brick now. > > Can you use a PCI/PCIE nic to get it on the net to make it easier for > Linux people to try and help you? > > I've been reading the openbsd lists for quite a long time, to put this > in perspective I never heard of a problem like this before, though > to be fair this isn't something most people would notice. > > > I am leaving this list after this. > > > > Many thanks for all the suggestions you gave me to solve this issue. > > > > Bye!
