LM14 and Gigabit Ethernet not working

[BarkingGhostar]

Yesterday I swapped out an old WRT54GL router limited to Fast Ethernet to a TP-Link AC1200. It works perfectly under Windows 7, the 2.4/5 GHz wifi works great with tablets and cell phones, but when I reboot my desktop W7-->LM14 the Ethernet adapter cannot connect.

In Windows I can choose to not to auto-negotiate bandwidth and select 1 Gbps Ethernet. In Linux Mint I cannot find any option to tell the eth0 adapter how to behave in this context. I can't even tell what speed it is trying to work at--only that it will not work with this new router.

Anyone know how to go about this forcing the adapter to configure at a lower bandwidth (e.g. Fast Ethernet) in order to come online? I know it isn't the hardware because I booted back into Windows to post this and its working just dandy at Gbps speeds.

 

[lxskllr]

try installing ethtool(if it's not already installed), open up a terminal and try man ethtool(to read the man pages). Looks like there's some interesting stuff in there, but I haven't personally used it.

 

[BarkingGhostar]

I can have a look at the manual pages on the topic of ethtool, but I have zero network connectivity in the present condition so I can't really install anything if it needs Internet access.

 

[lxskllr]

If ethtool isn't installed, it may or may not be a trivial sneakernet fix depending on dependencies, but if it is installed, you won't need anything else to tweak the interface.

 

[manly]

I think dmesg usually states the link speed when a NIC port comes up.

If not, ifconfig should show quite a bit of interface info.

Gig-E is autonegotiate by design so I'm not sure why forcing link speed would be necessary.

 

[manly]

Actually ifconfig won't do it, but you have a couple different options:
https://www.cyberciti.biz/faq/howto-determine-ethernet-connection-speed/

 

[BarkingGhostar]

OK, this is even stranger. I gave up on that night in which I posted and replied. Let it go for a day while booted into Windows. I then booted the next day into LM and it came up working without a complaint. While I will always enjoy problems that fix themselves, I hate it not knowing what the issue was or what the implemented solution was.

 

[BarkingGhostar]

Hmm, oit did it again this morning. I rebooted and the problem wasn't there. Something is amiss.