Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI
Am Mon, 15 Sep 2014 18:19:32 -0700 Kevin Oberman rkober...@gmail.com schrieb: On Mon, Sep 15, 2014 at 2:38 PM, O. Hartmann ohart...@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@pci0:3:0:0: class=0xff card=0x502817aa chip=0x522710ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' bar [10] = type Memory, range 32, base 0xf1e0, 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 0001004ce000 re0@pci0:4:0:0: class=0x02 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 ac7ba1a06fd6 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 signature.asc Description: PGP signature
Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI
Am Tue, 16 Sep 2014 08:40:25 -0700 Adrian Chadd adr...@freebsd.org schrieb: Ah, jumbo frames. Maybe you got lucky and some ethernet drivers default to accepting larger frames even if the MTU is 1500. -a After all, I managed to get the NIC up and running. But the culprit is that I have to take the NIC down and then up to make it working once the system has bootet. That is annoying. Lucckily, I can provide better informations since the box s now attached to the network. Here we go: LAN: re0@pci0:4:0:0: class=0x02 card=0x502817aa chip=0x816810ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' class = network subclass = ethernet bar [10] = type I/O Port, range 32, base 0x3000, size 256, enabled bar [18] = type Memory, range 64, base 0xf1d04000, size 4096, enabled bar [20] = type Memory, range 64, base 0xf1d0, size 16384, 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 IRQ 1 max data 128(128) link x1(x1) speed 2.5(2.5) ASPM disabled(L0s/L1) cap 11[b0] = MSI-X supports 4 messages, enabled Table in map 0x20[0x0], PBA in map 0x20[0x800] cap 03[d0] = VPD ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected ecap 0002[140] = VC 1 max VC0 ecap 0003[160] = Serial 1 0100684ce000 ecap 0018[170] = LTR 1 ecap 001e[178] = unknown 1 PCI-e errors = Correctable Error Detected Corrected = Receiver Error WiFi (supposed to be Intel ): none2@pci0:5:0:0: class=0x028000 card=0x42628086 chip=0x08b28086 rev=0x73 hdr=0x00 vendor = 'Intel Corporation' class = network bar [10] = type Memory, range 64, base 0xf1c0, size 8192, enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[40] = PCI-Express 2 endpoint max data 128(128) FLR link x1(x1) speed 2.5(2.5) ASPM L1(L0s/L1) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected ecap 0003[140] = Serial 1 ac7ba1a06fd6 ecap 0018[14c] = LTR 1 ecap 000b[154] = Vendor 1 ID 51966 The WiFi NIC isn't recognized by any driver in CURRENT (11.0-CURRENT #5 r271728: Thu Sep 18 01:18:25 CEST 2014 amd64) Maybe this is of help. Oliver signature.asc Description: PGP signature
Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI
On 09/18/14 09:58, O. Hartmann wrote:
Am Tue, 16 Sep 2014 08:40:25 -0700
Adrian Chadd adr...@freebsd.org schrieb:
Ah, jumbo frames. Maybe you got lucky and some ethernet drivers
default to accepting larger frames even if the MTU is 1500.
-a
After all, I managed to get the NIC up and running. But the culprit is that I
have to
take the NIC down and then up to make it working once the system has bootet.
That is
annoying. Lucckily, I can provide better informations since the box s now
attached to the
network. Here we go:
I have a similar situation with my nick on a tower system.
I need to change at least one flag on the card to have it working, I can
also just set the flag to the value it already has.
I'm using a small startup script which actually does this:
start_cmd=ifconfig ${refix_if} tso
LAN:
re0@pci0:4:0:0: class=0x02 card=0x502817aa chip=0x816810ec rev=0x10
hdr=0x00
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller'
class = network
subclass = ethernet
bar [10] = type I/O Port, range 32, base 0x3000, size 256, enabled
bar [18] = type Memory, range 64, base 0xf1d04000, size 4096, enabled
bar [20] = type Memory, range 64, base 0xf1d0, size 16384, 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 IRQ 1 max data 128(128) link x1(x1)
speed 2.5(2.5) ASPM disabled(L0s/L1)
cap 11[b0] = MSI-X supports 4 messages, enabled
Table in map 0x20[0x0], PBA in map 0x20[0x800]
cap 03[d0] = VPD
ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected
ecap 0002[140] = VC 1 max VC0
ecap 0003[160] = Serial 1 0100684ce000
ecap 0018[170] = LTR 1
ecap 001e[178] = unknown 1
PCI-e errors = Correctable Error Detected
Corrected = Receiver Error
re0@pci0:3:0:0: class=0x02 card=0x11c01734 chip=0x816810ec rev=0x07
hdr=0x00
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller'
class = network
subclass = ethernet
bar [10] = type I/O Port, range 32, base 0xd000, size 256, enabled
bar [18] = type Prefetchable Memory, range 64, base 0xf2104000,
size 4096, enabled
bar [20] = type Prefetchable Memory, range 64, base 0xf210,
size 16384, 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 IRQ 1 max data 128(128) link x1(x1)
speed 2.5(2.5) ASPM disabled(L0s/L1)
cap 11[b0] = MSI-X supports 4 messages, enabled
Table in map 0x20[0x0], PBA in map 0x20[0x800]
cap 03[d0] = VPD
ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected
ecap 0002[140] = VC 1 max VC0
ecap 0003[160] = Serial 1 01000401
PCI-e errors = Correctable Error Detected
Unsupported Request Detected
Corrected = Advisory Non-Fatal Error
it's similar hardware, same chip, different revision. I already reported
this on net@ but no patch could really solve the issue.
--
Guido Falsi m...@madpilot.net
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI
Am Thu, 18 Sep 2014 10:17:08 +0200
Guido Falsi m...@madpilot.net schrieb:
On 09/18/14 09:58, O. Hartmann wrote:
Am Tue, 16 Sep 2014 08:40:25 -0700
Adrian Chadd adr...@freebsd.org schrieb:
Ah, jumbo frames. Maybe you got lucky and some ethernet drivers
default to accepting larger frames even if the MTU is 1500.
-a
After all, I managed to get the NIC up and running. But the culprit is that
I have to
take the NIC down and then up to make it working once the system has
bootet. That is
annoying. Lucckily, I can provide better informations since the box s now
attached to
the network. Here we go:
I have a similar situation with my nick on a tower system.
I need to change at least one flag on the card to have it working, I can
also just set the flag to the value it already has.
I'm using a small startup script which actually does this:
start_cmd=ifconfig ${refix_if} tso
LAN:
re0@pci0:4:0:0: class=0x02 card=0x502817aa chip=0x816810ec rev=0x10
hdr=0x00
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller'
class = network
subclass = ethernet
bar [10] = type I/O Port, range 32, base 0x3000, size 256, enabled
bar [18] = type Memory, range 64, base 0xf1d04000, size 4096, enabled
bar [20] = type Memory, range 64, base 0xf1d0, size 16384, 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 IRQ 1 max data 128(128) link x1(x1)
speed 2.5(2.5) ASPM disabled(L0s/L1)
cap 11[b0] = MSI-X supports 4 messages, enabled
Table in map 0x20[0x0], PBA in map 0x20[0x800]
cap 03[d0] = VPD
ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected
ecap 0002[140] = VC 1 max VC0
ecap 0003[160] = Serial 1 0100684ce000
ecap 0018[170] = LTR 1
ecap 001e[178] = unknown 1
PCI-e errors = Correctable Error Detected
Corrected = Receiver Error
re0@pci0:3:0:0: class=0x02 card=0x11c01734 chip=0x816810ec rev=0x07
hdr=0x00
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller'
class = network
subclass = ethernet
bar [10] = type I/O Port, range 32, base 0xd000, size 256, enabled
bar [18] = type Prefetchable Memory, range 64, base 0xf2104000,
size 4096, enabled
bar [20] = type Prefetchable Memory, range 64, base 0xf210,
size 16384, 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 IRQ 1 max data 128(128) link x1(x1)
speed 2.5(2.5) ASPM disabled(L0s/L1)
cap 11[b0] = MSI-X supports 4 messages, enabled
Table in map 0x20[0x0], PBA in map 0x20[0x800]
cap 03[d0] = VPD
ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected
ecap 0002[140] = VC 1 max VC0
ecap 0003[160] = Serial 1 01000401
PCI-e errors = Correctable Error Detected
Unsupported Request Detected
Corrected = Advisory Non-Fatal Error
it's similar hardware, same chip, different revision. I already reported
this on net@ but no patch could really solve the issue.
Hello.
Well, it seems the same here with taht specific NIC. Changing ANYTHING, even
already
enabled features, or bringing the NIC down and then up seem to solve this
problem.
I guess, I file a PR to make this issue memorized.
Regards,
Oliver
signature.asc
Description: PGP signature
Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI
Am Mon, 15 Sep 2014 18:25:34 -0700 Adrian Chadd adr...@freebsd.org schrieb: Hi, Try updating to the latest -HEAD. It at least makes dhclient behave better. -a On 15 September 2014 18:19, Kevin Oberman rkober...@gmail.com wrote: On Mon, Sep 15, 2014 at 2:38 PM, O. Hartmann ohart...@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@pci0:3:0:0: class=0xff card=0x502817aa chip=0x522710ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' bar [10] = type Memory, range 32, base 0xf1e0, 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 0001004ce000 re0@pci0:4:0:0: class=0x02 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 ac7ba1a06fd6 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 In my local network (the laptop is working/getting installed in) I use jumbo frames on several server system including the gateway (also FBSD CURRENT). After I manually set mtu 1500 (in my case: mtu 6121) the NIC worked as expected. My lab's Dell Latitude E6510 laptop (em0) works without setting explicit jumbo frames. This is a kind of weird ... Thanks for your patience. Oliver signature.asc Description: PGP signature
Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI
Ah, jumbo frames. Maybe you got lucky and some ethernet drivers default to accepting larger frames even if the MTU is 1500. -a ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI
Am Tue, 16 Sep 2014 08:40:25 -0700 Adrian Chadd adr...@freebsd.org schrieb: Ah, jumbo frames. Maybe you got lucky and some ethernet drivers default to accepting larger frames even if the MTU is 1500. -a It is not the jumbo frame that makes this specific NIC work, I have to set the mtu explicitely to make it work. To make this notebook work in different departments, I need to use DHCP. At the moment I have to set the mtu manually, disbaling and reenabling the NIC (ifconfig re0 down, ifconfig re0 mtu , ifconfig re0 up). This seems to be strange. After that, the NIC seems to work as expected and the Laptop has connection. Oliver signature.asc Description: PGP signature
11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI
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@pci0:3:0:0: class=0xff card=0x502817aa chip=0x522710ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' bar [10] = type Memory, range 32, base 0xf1e0, 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 0001004ce000 re0@pci0:4:0:0: class=0x02 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 ac7ba1a06fd6 signature.asc Description: PGP signature
Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI
On Mon, Sep 15, 2014 at 2:38 PM, O. Hartmann ohart...@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@pci0:3:0:0: class=0xff card=0x502817aa chip=0x522710ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' bar [10] = type Memory, range 32, base 0xf1e0, 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 0001004ce000 re0@pci0:4:0:0: class=0x02 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 ac7ba1a06fd6 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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI
Hi, Try updating to the latest -HEAD. It at least makes dhclient behave better. -a On 15 September 2014 18:19, Kevin Oberman rkober...@gmail.com wrote: On Mon, Sep 15, 2014 at 2:38 PM, O. Hartmann ohart...@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@pci0:3:0:0: class=0xff card=0x502817aa chip=0x522710ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' bar [10] = type Memory, range 32, base 0xf1e0, 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 0001004ce000 re0@pci0:4:0:0: class=0x02 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 ac7ba1a06fd6 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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
