Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard
> The patch was not intended to address your issue. It was for > getting correct MAC revision number. So seeing no behavioral change > is normal. > The MAC revision number now indicates 0x0010 which means you > have slightly different variant. I'll let you know if I happen to > find more clue on that MAC revision. So now there is no advantage in building that kernel for my i386 USB-stick installation. Do I need to file a send-pr? > One last shot in the dark: > what if you reboot the router in front of the node in question? > Sometimes it was surprised, when managing different mac addresses > on the same adapter. > I might be missing some parts, but did the mobo work before? > Best regards >Zoran I believe I can power off the router, and after a minute or two, power back on. Sure the mobo works, even the Ethernet chip works, but not with FreeBSD. I could boot NetBSD-HEAD amd64, dhclient ran ok, and I was able to checkout the system source tree and pkgsrc tree with cvs. So if I can get past the snag in pkg-config, which was dropped by FreeBSD in favor of pkgconf, I could build subversion and checkout the FreeBSD-HEAD source tree. I wonder if my Ethernet chip is better supported in the upcoming FreeBSD-10.0. I also have the on-motherboard quasi-USB WiFi Atheros AR9271 and the Hiro USB-stick-type WiFi adapter, Realtek RTL8191SU chip. I could also try to boot my OpenBSD 5.3 live USB 8 GB, see if Ethernet chip or Wi-Fi works, but OpenBSD can't access my hard drive or GPT-partitioned USB sticks, since OpenBSD does not support GPT, or USB 3.0. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard
On Thu, Sep 26, 2013 at 08:09:36AM +, Thomas Mueller wrote: > I rebuilt the kernel while keeping the existing kernel, installing to > /boot/kernelre on the USB stick. > > Unfortunately all the modules were redundantly rebuilt. Maybe I should have > had "-D NO_MODULES" instead of "-DNO_MODULES"? > > I typed "unload" at the loader prompt, then "boot /boot/kernelre/kernel". > > I had the same problem as before with dhclient, looked like nothing different. The patch was not intended to address your issue. It was for getting correct MAC revision number. So seeing no behavioral change is normal. The MAC revision number now indicates 0x0010 which means you have slightly different variant. I'll let you know if I happen to find more clue on that MAC revision. > > Lines in /var/run/dmesg.boot relating to re0 were: > > re0: port > 0xe000-0xe0ff mem 0xf7d04000-0xf7d04fff,0xf7d0-0xf7d03fff irq 17 at > device 0.0 on pci2 > re0: Using 1 MSI-X message > re0: Chip rev. 0x2c80 > re0: MAC rev. 0x0010 > miibus0: on re0 > rgephy0: PHY 1 on miibus0 > rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, > 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, > 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, > 1000baseT-FDX-flow-master, auto, auto-flow > re0: Ethernet address: d4:3d:7e:97:17:e2 > > > Tom > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard
I rebuilt the kernel while keeping the existing kernel, installing to /boot/kernelre on the USB stick. Unfortunately all the modules were redundantly rebuilt. Maybe I should have had "-D NO_MODULES" instead of "-DNO_MODULES"? I typed "unload" at the loader prompt, then "boot /boot/kernelre/kernel". I had the same problem as before with dhclient, looked like nothing different. Lines in /var/run/dmesg.boot relating to re0 were: re0: port 0xe000-0xe0ff mem 0xf7d04000-0xf7d04fff,0xf7d0-0xf7d03fff irq 17 at device 0.0 on pci2 re0: Using 1 MSI-X message re0: Chip rev. 0x2c80 re0: MAC rev. 0x0010 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: d4:3d:7e:97:17:e2 Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard
On Thu, Sep 26, 2013 at 02:31:30AM +, Thomas Mueller wrote: > > It looks like 8168E-VL. > > Could you try attached patch and show me the dmesg output(re(4) and > > rgephy(4) only)? The patch was generated to support 8106E but it > > will correctly show MAC revision number. > > I assume I go to /usr/src and run > patch < /home/arlene/computer/re.8106.diff > Yes. > Then rebuild the kernel with -DNO_MODULES and install under a different name, > like kernelre? > Rebuilding kernel should be enough. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html for more information. > I would install this on USB-stick installation, could do this for i386 > USB-stick installation as well. > > > > Somewhat later I got > > > > Memory modified after free 0xfe0011546800(2048) val=977e3dd > > 4 @ 0xfe0011546800 > > > Memory modified after free 0xfe001153b800(2048) val= @ > > > 0xfe00115 > > 3b800 > > > Memory modified after free 0xfe0011524800(2048) val=977e3dd4 @ > > > 0xfe00115 > > 24800 > > > VESA: set_mode(): 24(18) -> 24(18) > > > Memory modified after free 0xfe0011594000(2048) val=977e3dd4 @ > > > 0xfe00115 > > 94000 > > > The size(2048) indicates mbuf cluster which in turn means bad > > things happened in re(4). I have no idea how this can happen > > though. > > If you assign static IP addressi to re(4), does the driver works as > > expected? > > I can try assigning a static address to re4, not really sure how to set up > manually, though I did it long ago in Slackware Linux. > > I wouldn't have known size 2048 indicated something bad, though the message's > presence and system crash indicated that something was fouled up in memory. > > Tom > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard
> It looks like 8168E-VL. > Could you try attached patch and show me the dmesg output(re(4) and > rgephy(4) only)? The patch was generated to support 8106E but it > will correctly show MAC revision number. I assume I go to /usr/src and run patch < /home/arlene/computer/re.8106.diff Then rebuild the kernel with -DNO_MODULES and install under a different name, like kernelre? I would install this on USB-stick installation, could do this for i386 USB-stick installation as well. > > Somewhat later I got > > Memory modified after free 0xfe0011546800(2048) val=977e3dd > 4 @ 0xfe0011546800 > > Memory modified after free 0xfe001153b800(2048) val= @ > > 0xfe00115 > 3b800 > > Memory modified after free 0xfe0011524800(2048) val=977e3dd4 @ > > 0xfe00115 > 24800 > > VESA: set_mode(): 24(18) -> 24(18) > > Memory modified after free 0xfe0011594000(2048) val=977e3dd4 @ > > 0xfe00115 > 94000 > The size(2048) indicates mbuf cluster which in turn means bad > things happened in re(4). I have no idea how this can happen > though. > If you assign static IP addressi to re(4), does the driver works as > expected? I can try assigning a static address to re4, not really sure how to set up manually, though I did it long ago in Slackware Linux. I wouldn't have known size 2048 indicated something bad, though the message's presence and system crash indicated that something was fouled up in memory. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard
On Sun, Sep 22, 2013 at 08:28:08PM +, Thomas Mueller wrote:
> I've been unable to establish Internet connection from a new computer with
> Realtek 811E Ethernet despite this Ethernet chip working on another computer
> with another MSI motherboard.
>
> Problem motherboard is MSI Z77 MPOWER.
>
> Older, by two years, motherboard is MSI Z68MA-ED55(B3).
>
> uname -a shows
>
> FreeBSD amelia2 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #17 r254196: Sun Aug 11
> 00:36:49 UTC 2013 root@amelia2:/usr/obj/usr/src/sys/SANDY amd64
>
> I get the same problem with FreeBSD 9.1_STABLE i386.
>
> These are USB-stick installations.
>
> I was able to connect to the Internet with (MSI) Winki 3 (Linux-based),
> included on a DVD included in the motherboard package.
>
> After nothing but frustration trying to boot USB-stick installations of
> NetBSD 6.1-STABLE and HEAD (i386), I successfully booted NetBSD-HEAD amd64
> from early last May, and "dhclient re0" was successful, whereupon I
> downloaded, by cvs, the HEAD source tree and pkgsrc tree.
>
> This proves or strongly suggests the Ethernet chip is healthy.
>
> Anything I can do (at loader prompt or loader.conf?) to make this Ethernet
> work in FreeBSD?
>
> I could update NetBSD-HEAD from source, update the packages through pkgsrc,
> and build subversion, then checkout the FreeBSD-HEAD source tree, ports and
> doc trees too, and build FreeBSD-HEAD from source on hard drive using
> USB-stick installation of FreeBSD 9.2 (prerelease or release).
>
> Related part of /var/run/dmesg.boot is
>
> re0: port
> 0xe000-0xe0f
> f mem 0xf7d04000-0xf7d04fff,0xf7d0-0xf7d03fff irq 17 at device 0.0 on pci2
> re0: Using 1 MSI-X message
> re0: Chip rev. 0x2c80
> re0: MAC rev. 0x
It looks like 8168E-VL.
Could you try attached patch and show me the dmesg output(re(4) and
rgephy(4) only)? The patch was generated to support 8106E but it
will correctly show MAC revision number.
> miibus0: on re0
> rgephy0: PHY 1 on miibus0
> rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
> 100baseTX-FDX
> , 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX,
> 1000baseT-FDX-
> master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
> re0: Ethernet address: d4:3d:7e:97:17:e2
>
>
> Log of "dhclient re0" was
>
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 3
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 3
> DHCPOFFER from 192.168.1.1
Driver got a response but it seems it was discarded.
> DHCPREQUEST on re0 to 255.255.255.255 port 67
> DHCPREQUEST on re0 to 255.255.255.255 port 67
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 6
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 13
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 14
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 17
> DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 11
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
>
>
> Somewhat later I got
>
> Memory modified after free 0xfe0011546800(2048) val=977e3dd
> 4 @ 0xfe0011546800
> Memory modified after free 0xfe001153b800(2048) val= @
> 0xfe00115
> 3b800
> Memory modified after free 0xfe0011524800(2048) val=977e3dd4 @
> 0xfe00115
> 24800
> VESA: set_mode(): 24(18) -> 24(18)
> Memory modified after free 0xfe0011594000(2048) val=977e3dd4 @
> 0xfe00115
> 94000
>
The size(2048) indicates mbuf cluster which in turn means bad
things happened in re(4). I have no idea how this can happen
though.
If you assign static IP addressi to re(4), does the driver works as
expected?
>
> In one case, when I went to bed on this, hours later the system crashed and
> went into the debugger (db>), where I was rather lost, couldn't kill
> dhclient, after some time types "reboot".
>
> Should I have posted this to a different list (hardware, questions?)?
>
> I would like to find if FreeBSD HEAD (10.0 alphas) would do better. Also,
> because of nearness of 10.0-RELEASE, I would rather go this track than 9.2
> and then update; I already have 9.2 prerelease on other computer.
>
> Motherboard also has Atheros Wi-Fi (Atheros AR9271 802.11n), and I also have
> a USB stick-type WLAN adapter (Hiro Inc H50191, Realtek RTL8191SU 802.11n
> chip).
>
> Tom
Index: sys/dev/re/if_re.c
===
--- sys/dev/re/if_re.c (revision 255757)
+++ sys/dev/re/if_re.c (working copy)
@@ -223,6 +223,7 @@
{ RL_HWREV_8402, RL_8169, "8402", RL_MTU },
{ RL_HWREV_8105E, RL_8169, "8105E", RL_MTU },
{ RL_HWREV_8105E_SPIN1, RL_8169, "8105E", RL_MTU },
+ { RL_HWREV_8106E, RL_8169, "8106E", RL_MTU },
{ RL_HWREV_8168B_SPIN2, RL_8169, "8168", RL_JUMBO_MTU },
{ RL_HWREV_8168B_SPIN3, RL_8169, "8168", RL_JUMBO_MTU },
{ RL_HWREV_8168C, RL_8169, "8168C/8111C", RL_JUMBO_MTU_6K },
@@ -1367,10 +1368,11 @@
break;
default:
device_printf(dev, "Chip r
Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard
for MSI Z77 MPOWER motherboard: re0@pci0:2:0:0: class=0x02 card=0x77511462 chip=0x816810ec rev=0x06 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' class = network subclass = ethernet ifconfig re0 shows re0: flags=8802 metric 0 mtu 1500 options=8209b ether d4:3d:7e:97:17:e2 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active dhclient re0 produces DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 12 DHCPOFFER from 192.168.1.1 DHCPREQUEST on re0 to 255.255.255.255 port 67 DHCPREQUEST on re0 to 255.255.255.255 port 67 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 8 DHCPOFFER from 192.168.1.1 DHCPREQUEST on re0 to 255.255.255.255 port 67 DHCPREQUEST on re0 to 255.255.255.255 port 67 DHCPREQUEST on re0 to 255.255.255.255 port 67 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 18 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 16 No DHCPOFFERS received. No working leases in persistent database - sleeping. Ethernet chip data for older motherboard, MSI Z68MA-ED55(B3), is re0@pci0:3:0:0: class=0x02 card=0x76761462 chip=0x816810ec rev=0x06 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' class = network subclass = ethernet So I still can not connect on the newer motherboard as I can with the older motherboard, despite the same chip; card has a different ID. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard
On Sun, 22 Sep 2013 20:28:08 + "Thomas Mueller" wrote: > I've been unable to establish Internet connection from a new computer with > Realtek 811E Ethernet despite this Ethernet chip working on another computer > with another MSI motherboard. In additiin to the information you have already provided, you should also provide relevant output from pciconf, like so: root@kg-core1# pciconf -lv | grep -A 4 re0 re0@pci0:2:0:0: class=0x02 card=0x84321043 chip=0x816810ec rev=0x06 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet (substitute the name of your interface for "re0") and also ifconfig output like this: root@kg-core1# ifconfig re0 re0: flags=8843 metric 0 mtu 1500 options=8209b ether 50:46:5d:8b:a2:ea inet 10.1.150.50 netmask 0x broadcast 10.1.255.255 media: Ethernet autoselect (1000baseT ) status: active (again, substitute the name of your interface for "re0") As far as fault-finding "tricks" go, here is one that have helped me on several occasions in the past: before doing anything with a network interface (in other words, before starting DHCP), try doing a 'ifconfig up' for example ifconfig re0 up After that, use the interface normally. If it works, you have found a bug related to the driver and the specific hardware revsion of you card. Create a PR for it. HTH -- Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard
> Related part of /var/run/dmesg.boot is > > re0: port > 0xe000-0xe0f f mem 0xf7d04000-0xf7d04fff,0xf7d0-0xf7d03fff irq 17 at > device 0.0 on pci2 re0: Using 1 MSI-X message re0: Chip rev. 0x2c80 re0: > MAC rev. 0x miibus0: on re0 rgephy0: 1000BASE-T media interface> PHY 1 on miibus0 rgephy0: none, 10baseT, > 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX , 100baseTX-FDX-flow, > 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX- master, > 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet > address: d4:3d:7e:97:17:e2 > Thomas: That NIC chip works for me and gets it's address information using DHCP. Aug 31 16:09:13 mail kernel: FreeBSD 9.2-PRERELEASE #1: Sat Aug 31 12:13:51 EDT 2013 Aug 31 16:09:13 mail kernel: re0: port 0x2000-0x20ff mem 0xf0004000-0xf0004fff,0xf000-0xf0003fff irq 16 at device 0.0 on pci1 Aug 31 16:09:13 mail kernel: re0: Using 1 MSI-X message Aug 31 16:09:13 mail kernel: re0: Chip rev. 0x2800 Aug 31 16:09:13 mail kernel: re0: MAC rev. 0x Aug 31 16:09:13 mail kernel: miibus0: on re0 Aug 31 16:09:13 mail kernel: rgephy0: PHY 1 on miibus0 Aug 31 16:09:13 mail kernel: rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master,1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow Aug 31 16:09:13 mail kernel: re0: Ethernet address: 70:71:bc:18:1b:97 Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
