Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
10-12-2023, 12:28 AM
|
#1
|
LQ Newbie
Registered: Jan 2022
Distribution: Debian
Posts: 24
Rep:
|
Network card management command is good or bad
Hi guys!
I would like to know if there is any way to identify if the network card (RJ45) that is integrated into the board has suffered some physical damage or it is just a lack of system drivers.
I don't exactly remember when it stopped working, after a system update... maybe?
Any command where I can start stretching the threads?
At first glance I can see that it only has one (one) fixed green LED light without flashing. And without having the cable connected.
Now connecting the cable, the above is repeated. one Fixed green LED light.
any suggestion is welcome!
|
|
|
10-12-2023, 07:46 AM
|
#2
|
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 17,278
|
Certainly. Run If that somehow isn't enough, note the slot on the left. Then run lspci -n and search for the number.
|
|
|
10-12-2023, 08:04 AM
|
#3
|
Moderator
Registered: Aug 2002
Posts: 26,541
|
Not sure I understand your post. Is the green LED illuminated regardless if the cable is connected or not?
The ethtool utility will show if the link is detected and its settings but typically not installed by default.
|
|
|
10-12-2023, 04:01 PM
|
#4
|
Member
Registered: Sep 2015
Location: Australia
Distribution: Slackware, Devuan, Freebsd
Posts: 696
Rep: 
|
With a network cable, it takes two to tango.
The network switch (usually) and the desktop/laptop NIC
1. Telnet or ssh into the switch and watch the logs
2. On your desktop/laptop run this command dmesg -w as root and then plug the cable in.
Usually you see something in the logs above which helps
|
|
|
10-13-2023, 07:56 AM
|
#5
|
Moderator
Registered: Mar 2008
Posts: 22,290
|
Yes, you will have to identify the device. The make sure the drivers are loaded then usually put some tcp/ip configuration on it.
Used to have a loop back connector in my desk to test. It connects the input to output to diag in some cases.
|
|
|
All times are GMT -5. The time now is 05:34 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|