On Sat, Jun 09, 2018 at 08:56:16PM +0200, Jarom?r Dole?ek wrote:
> I had a look, the driver has also second match routine, which needs to
> be updated too.
> I've committed change on -current to match several Yukon variants
> including yours, can you check if it would work for you by chance?
> But I suspect you might hit the same problem as Chris did in
> kern/53301. Unfortunately I don't have the hardware, so can't really
> work on this further.
Ok, I got it updated to current.
The device seems to have detected, however when I attempt to connect over DHCP
it locks up the machine,
and I have to do a cold reboot to get it going again.
[ 1.045467] mskc0 at pci1 dev 0 function 0, Yukon-2 Extreme rev. B0 (0x2):
ioapic0 pin 16
[ 1.045467] msk0 at mskc0 port A: Ethernet address 00:1d:72:eb:86:41
[ 1.045467] makphy0 at msk0 phy 0: Marvell 88E1149 Gigabit PHY, rev. 1
[ 1.002124] mskc0 at pci1 dev 0 function 0, Yukon-2 Extreme rev. B0 (0x2):
ioapic0 pin 16
[ 1.002124] msk0 at mskc0 port A: Ethernet address 00:1d:72:eb:86:41
[ 1.002124] makphy0 at msk0 phy 0: Marvell 88E1149 Gigabit PHY, rev. 1
^ The output from dmesg shows the device but the model number is incorrect. It
is an 88E8071.
I appreciate the effort and difficulty in amending a driver for a device in
someone else's machine.
I'm planning on getting a usb<>ethernet adapter but will leave it on current
for a while if there's any
more info you might need. No worries if not though.
Thanks for the effort!
SDF Public Access UNIX System - http://sdf.org