Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Auto-negotiation between the Ethernet adapter on my Dell Optiplex and my Linksys E2500 router. Actually they do negotiate only one side decides on 10M and the other on 100M which does not work so well.
Therefore I have to issue the following command with the associated program in place as root to successfully connect to the Linksys router.
ethtool -s eth0 speed 10 autoneg off duplex full
My question is how to automate this process at startup at the proper time. It must occur after the network manager has begun negotiation.
I did not wish to loose the Network Manager applet in the Gnome GUI and I assume I would without Network Manager in place.
A brief note on how to remove Network Manager and what happens with the interface when I make "eth0" active in the "interfaces" file as well as what happens with the Gnome Network Manager applet would be helpful.
In reality I'd think the negotiation is failing due to poor wiring or interference.
Agree on wiring or interference. Fixing the problem is probably a better solution than implementing a workaround
Problem with using a NM add-in script (I think) is that NM runs in the user context and ethtool needs to run as root - it'd probably work, but it'd also prompt him for a password unless he does a little sudoers magic
Last edited by wizard10000; 08-09-2014 at 06:23 AM.
As for being a hardware interface media issue all that is involved here is the on mother board Ethernet RJ-45 adapter on a Dell Optiplex GX620, a 6' Cat-5 RJ-45 to RJ-45 patch cable and an RJ-45 Ethernet port on a Linksys E2500. I believe the problem to be internal to the Dell Ethernet and it's API with the Linux OS.
I had previously been told by someone who makes his living running and maintaining Linux servers with no GUI that Ethernet negotiation failure in Linux although not common is not that unusual either. More specifically I was told that if I wanted an Ethernet interface on a Linux system to come up after a power failure or a power on reset I had better set the speed of the Ethernet interface manually.
I could do away with Network Manager and figure out how that works. Specifics on how to accomplish that so I could try it would be appreciated. I do not think that it is that complex but I do not know what it means to the system in terms of connectivity after the change has been made.
Writing the script for Network Manager indicated is currently out of scope for my skill set although I am willing to work on changing that.
I assume the script would do nothing if the interface were up and would set the speed and other options if the interface were down.
One question would be, when the interface is trying to come up based on the Network Manager applet is the interface in some pending state and neither up nor down?
A starting point for learning the applicable scripting capability would be helpful.
Thanks for the help.
At least I know how to possibly solve the problem with the correct resources.
The NM applet, upper right normally, only allows one to disable or enable all interfaces or just specific interfaces like eth0. The interface of the NM Applet in Gnome provides no options other than the ability to configure a VPN.
Interestingly enough the NM applet when it's menu is active takes full control of the keyboard not even allowing one to issue a command to capture a screen image.