Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI

Am Mon, 15 Sep 2014 18:19:32 -0700
Kevin Oberman <rkoberman_at_gmail.com> schrieb:

> On Mon, Sep 15, 2014 at 2:38 PM, O. Hartmann <ohartman_at_zedat.fu-berlin.de>
> wrote:
> 
> >
> > Trying to install and run FreeBSD 11.0-CURRENT
> > (FreeBSD-11.0-CURRENT-amd64-20140903-r270990-memstick.img) on a new Lenovo
> > E540 notebook
> > fails in activating the NIC (Realtek RTL8111/8168B, driver re[0]). The NIC
> > shows up as
> > active and with carrier when issuing "ifconfig re0".
> >
> > From a desktop machine, I tried to ping the system in question and I get a
> > result with
> > missing packets:
> >
> > ping: sendto: Host is down
> > ping: sendto: Host is down
> > ping: sendto: Host is down
> > 64 bytes from 192.168.0.130: icmp_seq=26 ttl=64 time=0.114 ms
> > 64 bytes from 192.168.0.130: icmp_seq=41 ttl=64 time=0.130 ms
> > 64 bytes from 192.168.0.130: icmp_seq=60 ttl=64 time=0.119 ms
> > 64 bytes from 192.168.0.130: icmp_seq=80 ttl=64 time=0.119 ms
> > 64 bytes from 192.168.0.130: icmp_seq=100 ttl=64 time=0.105 ms
> > 64 bytes from 192.168.0.130: icmp_seq=116 ttl=64 time=0.135 ms
> > 64 bytes from 192.168.0.130: icmp_seq=136 ttl=64 time=0.091 ms
> >
> > DHCP configuration fails, since no DHCP offer is discovered.
> >
> > I swapped the switches, the cabling and I had always the same results. I
> > used another
> > Laptop, Dell Latitude E6510 with the same configuration (/etc/rc.conf) and
> > that system
> > gets DHCP offer and is online.
> >
> > Since the notebook is brandnew, the last thing I'll "suspect" is a
> > defective NIC, so I'll
> > ask whether this phenomenon is known - or, if not, the results
> > definititely would
> > indicate a broken NIC.
> >
> > Another point is the WiFI adaptor. This notebook is supposed to have a
> > WiFi NIC, but it
> > doesn't get revealed by FreeBSD (I tried iwn/iwi without success).
> >
> > pciconf output below, sorry for the messy shape, it is a copy-and-paste
> > from that immature
> > vt() terminal.
> >
> > Has anyone successfully installed that type of Notebook with FreeBSD
> > CURRENT using NIC
> > and Wifi?
> >
> > Please CC me.
> >
> >
> > Regards
> > oh
> >
> >
> > [...]
> >
> > none1_at_pci0:3:0:0:       class=0xff0000 card=0x502817aa chip=0x522710ec
> > rev=0x01 hdr=0x00
> >
> >
> >     vendor     = 'Realtek Semiconductor Co., Ltd.'
> >
> >
> >     bar   [10] = type Memory, range 32, base 0xf1e00000, size 4096, enabled
> >
> >
> >     cap 01[40] = powerspec 3  supports D0 D1 D2 D3  current D0
> >
> >
> >     cap 05[50] = MSI supports 1 message, 64 bit
> >
> >
> >     cap 10[70] = PCI-Express 2 endpoint max data 128(128) link x1(x1)
> >
> >
> >                  speed 2.5(2.5) ASPM L0s/L1(L0s/L1)
> >
> >
> >     ecap 0001[100] = AER 2 0 fatal 0 non-fatal 0 corrected
> >
> >
> >     ecap 0003[140] = Serial 1 00000001004ce000
> >
> >
> > re0_at_pci0:4:0:0: class=0x020000 card=0x502817aa chip=0x816810ec rev=0x10
> > hdr=0x00
> >
> >
> >     subclass   = ethernet
> >
> >
> >     cap 01[40] = powerspec 3  supports D0 D1 D2 D3  current
> > D0
> > di sabled(L0s/L1)
> >
> >
> >     cap 11[b0] = MSI-X supports 4 messages, enabled
> >
> >     ecap 0001[100] = AER 2 0 fatal 0 non-fatal 4 corrected
> >
> >
> >
> >     ecap 001e[178] = unknown 1
> >
> >
> >     class      = network
> >
> >
> >     cap 05[d0] = MSI supports 1 message, 64 bit
> >
> >
> >     ecap 0003[140] = Serial 1 ac7ba1ffffa06fd6
> >
> 
> I can't comment on the WiFi, I have little Asus box using an 8111/8168B and
> it works fine with the driver in 10.1-BETA. The driver in 10.0 recognizes
> the device, but did not work. I do notice that your NIC has a rev of 0x10
> while mine is 0x0c.
> --
> Kevin Oberman, Network Engineer, Retired

I tried a 10.1-BETA also and it shows the very same symptomes as in 11.0-CURRENT. As
Guido Falsi stated later in this thread, the device gets recognized but is inoperable
after initialized and setup by the OS until the administrator takes some strange actions.
In Guido's case a setting/resetting of NIC features helps, in my case I have to bring
down the device first via "ifconfig re0 down" and then bring it up. After that, the NIC
works as expected. This seems clearly to be a bug in the driver code and it might indeed
have to do something with a new revision used, but the NIC is since at least a year on
the market and floating around (my laptop was manufactured in April of this year).

Well, I hope this report doesn't get lost, so I filed a PR.

Oliver