On Sun, Jan 3, 2016 at 5:33 PM, jungle Boogie <[email protected]> wrote: > On 2 January 2016 at 23:59, Sepherosa Ziehau <[email protected]> wrote: >> I have pushed some changes to the re's PHY initialization, you could >> try latest usb image; hope it works for you. >> >> Thanks, >> sephe > > > The build is finished and I don't see re0 with ifconfig. I checked > your commits against mine just to make sure I did the build correctly > and I see the changes you made.
Pull the latest master w/ at least d7c373a44888285dd1fe95c1dafd678126722b96 And apply the following patch: https://www.dragonflybsd.org/~sephe/re_cfg.diff curl -o ~/re_cfg.diff https://www.dragonflybsd.org/~sephe/re_cfg.diff patch -p 1 -i ~/re_cfg.diff Rebuild and reinstall kernel. Thanks, sephe > > I was on: > DragonFly fly.in.lylie.net 4.5-DEVELOPMENT DragonFly > v4.5.0.263.g9261e-DEVELOPMENT #0: Thu Dec 31 16:13:10 UTC 2015 > [email protected]:/usr/obj/usr/src/sys/X86_64_GENERIC > x86_64 > > Now on: > DragonFly fly.in.lylie.net 4.5-DEVELOPMENT DragonFly > v4.5.0.282.g5b1a5-DEVELOPMENT #0: Sun Jan 3 01:11:07 PST 2016 > [email protected]:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64 > > > I see the same dmesg: > % dmesg | grep re0 > re0: <RealTek 8111/8168 PCIe Gigabit Ethernet> port 0x3000-0x30ff mem > 0xb2100000-0xb2103fff,0xb2104000-0xb2104fff irq 18 at device 0.0 on > pci2 > re0: Hardware rev. 0x50800000; PCI-E 125MHz > re0: PHY write failed > re0: PHY write failed > re0: MII without any phy! > device_probe_and_attach: re0 attach returned 6 > re0: <RealTek 8111/8168 PCIe Gigabit Ethernet> port 0x3000-0x30ff mem > 0xb2100000-0xb2103fff,0xb2104000-0xb2104fff irq 18 at device 0.0 on > pci2 > re0: Hardware rev. 0x50800000; PCI-E 125MHz > re0: PHY write failed > re0: PHY write failed > re0: MII without any phy! > device_probe_and_attach: re0 attach returned 6 > > > % ifconfig > ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2290 > ether 30:52:cb:a3:cf:a7 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng > status: associated > faith0: flags=8002<BROADCAST,MULTICAST> mtu 1500 > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > options=3<RXCSUM,TXCSUM> > inet 127.0.0.1 netmask 0xff000000 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 > sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552 > wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet6 fe80::3252:cbff:fea3:cfa7%wlan0 prefixlen 64 scopeid 0x6 > inet 192.168.0.56 netmask 0xffffff00 broadcast 192.168.0.255 > ether 30:52:cb:a3:cf:a7 > ssid somuch_ channel 6 (2437 MHz 11g ht/20) bssid 64:70:02:32:c2:48 > regdomain 108 indoor ecm authmode WPA privacy ON deftxkey UNDEF > TKIP 3:128-bit txpower 20 bmiss 7 scanvalid 60 protmode CTS > ampdulimit 64k shortgi wme burst roaming MANUAL > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng > status: associated > urtwn0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2290 > ether 80:1f:02:68:5d:39 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > > pciconf -lv: > re0@pci0:2:0:0: class=0x020000 card=0x200f1043 chip=0x816810ec rev=0x10 > hdr=0x00 > vendor = 'Realtek Semiconductor Co., Ltd.' > device = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller' > class = network > subclass = ethernet > > Any ideas? > > -- > ------- > inum: 883510009027723 > sip: [email protected] > xmpp: [email protected] -- Tomorrow Will Never Die
