Port-amd64 archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Problems with re driver under amd64
(I haven't received a copy of this yet, apologies if it's a duplicate).
Hello,
I had a weird problem with a few identical machines that I installed
amd64 w/UEFI on. (The guide was a huge help!) The machines are not
standard PC's — they boot off ld0 and are very SFF (4" x 3" x 2").
They're older computers made by a company called Liva.
I could get network connectivity on the re0 interface via dhclient but
not via a static IP (or dhcpcd). The box would respond to 1 in 70 pings
(1 per second).
It turned out that adding:
/sbin/ifconfig re0 down
/sbin/ifconfig re0 up
to rc.local fixed the problem with static IP addresses. Once I got that
working, I didn't test dhcpcd on the re0 interface but dhcpcd worked
fine on a USB adapter (cdce0).
I tried the latest (at the time) NetBSD-8 STABLE kernel and modules, but
not current.
Linux identifies this as an r8169g/8111g, but FreeBSD and NetNSD
identify it as an r8168/8111. Both FreeBSD and Linux work without any
trick or modification. Here's the relevant part of the dmesgs:
Linux MontyPython 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[ 2.674382] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 2.684065] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have
ASPM control
[ 2.697297] r8169 0000:03:00.0 eth0: RTL8168g/8111g at 0x
(ptrval), b8:ae:ed:3f:b6:39, XID 0c000800 IRQ 88
[ 2.700151] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200
bytes, tx checksumming: ko]
[ 2.807990] r8169 0000:03:00.0 enp3s0: renamed from eth0
[ 8.150272] r8169 0000:03:00.0 enp3s0: link down
[ 8.150293] r8169 0000:03:00.0 enp3s0: link down
[ 10.629720] r8169 0000:03:00.0 enp3s0: link up
FreeBSD 11.1-RELEASE
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port
0xe000-0xe0ff mem 0xd0604000-0xd0604fff,0xd0600000-0xd0603fff at device
0.0 on pci1
re0: Using 1 MSI-X message
re0: ASPM disabled
re0: Chip rev. 0x4c000000
re0: MAC rev. 0x00000000
miibus0: <MII bus> on re0
rgephy0: <RTL8251 1000BASE-T media interface> PHY 1 on miibus0
rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX, 1000baseT-FDX-master,
1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
re0: Using defaults for TSO: 65518/35/2048
re0: Ethernet address: b8:ae:ed:31:ed:68
re0: netmap queues/slots: TX 1/256, RX 1/256
re0: link state changed to DOWN
re0: link state changed to UP
NetBSD 8.0_STABLE (GENERIC) #0: Tue Nov 13 16:57:45 UTC 2018
NetBSD liva2.bigjar.com 8.0_STABLE NetBSD 8.0_STABLE (GENERIC) #0: Tue
Nov 13 16:57:45 UTC 2018
mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/amd64/compile/GENERIC amd64
re0 at pci3 dev 0 function 0: RealTek 8168/8111 PCIe Gigabit Ethernet
(rev. 0x0c)
re0: interrupting at msi2 vec 0
re0: Ethernet address b8:ae:ed:31:ee:31
re0: using 256 tx descriptors
rgephy0 at re0 phy 7: RTL8251 1000BASE-T media interface, rev. 0
rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX,
auto
Anyway, I don't have an issue now with the up/down trick, but I'm
thinking/hoping there might be an easy fix so that I don't have to do
this. It would probably help others as well.
Please let me know if this belongs elsewhere (netbsd-users?) and please
copy me on any replies as I'm not subscribed to port-amd64.
Thanks for reading!
Jason M.
Home |
Main Index |
Thread Index |
Old Index