Adam, thanks for the update on the bug fix, hopefully they'll get it worked out soon so others don't have to deal with this mess! :-)adame wrote:Thanks for the correction. I've edited my original post to include that.BrianW wrote:Okay, so it dawned on me that everyone says the problem is auto negotiation, but the command I was running didn't seem to be doing anything to set that attribute.
You should be able to. See if 100 full duplex works.After plugging the WD drive back in to the router it now links(blue light) and I can access the drive again via my computer!!! :-)
I wonder if I can rerun the command with 100 as the speed and improve performance? Any thoughts?
I've checked in with Pace on the status of the bug, and they are still waiting on their vendor to finish rewriting the necessary driver to fix this. I'm sorry for the length of the delay fixing this.
I SSH'd back in and ran the config for 100 full autoneg off and it was successful per the new ethtool eth0 output! :-)
So this is the new command I issued.
ethtool -s eth0 speed 100 duplex full autoneg off
I've seen it mentioned in other threads that this setting might get reset after a power cycle. I haven' tried it yet to test that out. Do you happen to know if that's the case? If not I'll find out by chance or by choice and let everyone know! :-)
B.