Date: Sat, 20 Sep 2014 12:45:40 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Kevin Oberman <rkoberman@gmail.com> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI Message-ID: <20140920124540.76a9abae.ohartman@zedat.fu-berlin.de> In-Reply-To: <CAN6yY1vP-CCOy8aWp8m1z2ijkRH5pm-UeXKf9i-QKf4jesCKUA@mail.gmail.com> References: <20140915233833.5bdd0725.ohartman@zedat.fu-berlin.de> <CAN6yY1vP-CCOy8aWp8m1z2ijkRH5pm-UeXKf9i-QKf4jesCKUA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/Y2b9rJzbwFe2mlhYDW_TE95 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Mon, 15 Sep 2014 18:19:32 -0700 Kevin Oberman <rkoberman@gmail.com> schrieb: > On Mon, Sep 15, 2014 at 2:38 PM, O. Hartmann <ohartman@zedat.fu-berlin.de> > wrote: >=20 > > > > Trying to install and run FreeBSD 11.0-CURRENT > > (FreeBSD-11.0-CURRENT-amd64-20140903-r270990-memstick.img) on a new Len= ovo > > 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 ge= t 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=3D26 ttl=3D64 time=3D0.114 ms > > 64 bytes from 192.168.0.130: icmp_seq=3D41 ttl=3D64 time=3D0.130 ms > > 64 bytes from 192.168.0.130: icmp_seq=3D60 ttl=3D64 time=3D0.119 ms > > 64 bytes from 192.168.0.130: icmp_seq=3D80 ttl=3D64 time=3D0.119 ms > > 64 bytes from 192.168.0.130: icmp_seq=3D100 ttl=3D64 time=3D0.105 ms > > 64 bytes from 192.168.0.130: icmp_seq=3D116 ttl=3D64 time=3D0.135 ms > > 64 bytes from 192.168.0.130: icmp_seq=3D136 ttl=3D64 time=3D0.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@pci0:3:0:0: class=3D0xff0000 card=3D0x502817aa chip=3D0x522= 710ec > > rev=3D0x01 hdr=3D0x00 > > > > > > vendor =3D 'Realtek Semiconductor Co., Ltd.' > > > > > > bar [10] =3D type Memory, range 32, base 0xf1e00000, size 4096, e= nabled > > > > > > cap 01[40] =3D powerspec 3 supports D0 D1 D2 D3 current D0 > > > > > > cap 05[50] =3D MSI supports 1 message, 64 bit > > > > > > cap 10[70] =3D PCI-Express 2 endpoint max data 128(128) link x1(x1) > > > > > > speed 2.5(2.5) ASPM L0s/L1(L0s/L1) > > > > > > ecap 0001[100] =3D AER 2 0 fatal 0 non-fatal 0 corrected > > > > > > ecap 0003[140] =3D Serial 1 00000001004ce000 > > > > > > re0@pci0:4:0:0: class=3D0x020000 card=3D0x502817aa chip=3D0x816810ec re= v=3D0x10 > > hdr=3D0x00 > > > > > > subclass =3D ethernet > > > > > > cap 01[40] =3D powerspec 3 supports D0 D1 D2 D3 current > > D0 > > di sabled(L0s/L1) > > > > > > cap 11[b0] =3D MSI-X supports 4 messages, enabled > > > > ecap 0001[100] =3D AER 2 0 fatal 0 non-fatal 4 corrected > > > > > > > > ecap 001e[178] =3D unknown 1 > > > > > > class =3D network > > > > > > cap 05[d0] =3D MSI supports 1 message, 64 bit > > > > > > ecap 0003[140] =3D Serial 1 ac7ba1ffffa06fd6 > > >=20 > I can't comment on the WiFi, I have little Asus box using an 8111/8168B a= nd > 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-CU= RRENT. 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 st= range actions. In Guido's case a setting/resetting of NIC features helps, in my case I hav= e to bring down the device first via "ifconfig re0 down" and then bring it up. After t= hat, 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 leas= t 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 --Sig_/Y2b9rJzbwFe2mlhYDW_TE95 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJUHVraAAoJEOgBcD7A/5N8qzUIAJWake6B6rO7uj4FPQa4a7pG +lxP38T26h/+3z6Kc+oc/W4FQv4/eQRRS1DOSGvoS92Fg8lTBP4JrSXXA2wxVLUj QbtKzb1WrdezomA6w1FbsAoYIZB6Kqn9C6uvmLkgstiIDhy8UeSaBoGyy4DHcqH3 mYyFEooaAbpVVHqH3moiiTmfABSiELoLK6Lc3MSKgevwYWINHa2srfK9y7zzZ/TQ Wsy0s1RCRe57711Ca+sHPihhxGgpRQVbEm0FHfa/1sf5uyHwgmf0D+8FdLd0ikAv HQMNigabz+lGN6Oy5qVKizWWxsfTRGT+m2lpByMip3SxnNVqCav0/EPjoij1jwQ= =EIfl -----END PGP SIGNATURE----- --Sig_/Y2b9rJzbwFe2mlhYDW_TE95--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140920124540.76a9abae.ohartman>