SlackwareThis Forum is for the discussion of Slackware 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.
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.
I'm having problems with wireless so I'm using a wired connection. The problem is it keeps dropping my wired connection. If tell it to start I get the message that it's already connected so I have to restart and then it works and then it drops the connection again. H
Code:
bash-4.3# /etc/rc.d/rc.inet1 restart
sending signal ARLM to pid 24329
waiting for pid 24329 to exit
Polling for DHCP server on interface eth0:
eth0: adding address fe80::8eef:b7ac:592e:6d56
eth0: waiting for carrier
eth0: carrier acquired
DUID 00:01:00:01:20:9a:2c:ce:20:47:47:4f:fd:8d
eth0: IAID 47:4f:fd:8d
eth0: carrier lost
eth0: deleting address fe80::8eef:b7ac:592e:6d56
eth0: carrier acquired
eth0: adding address fe80::8eef:b7ac:592e:6d56
eth0: IAID 47:4f:fd:8d
eth0: soliciting an IPv6 router
eth0: rebinding lease of 192.168.0.4
eth0: Router Advertisement from fe80::d2b2:c4ff:fe4c:1c09
eth0: adding address 2605:6001:f180:ad00:ebe4:d72b:70ca:7a53/64
eth0: adding route to 2605:6001:f180:ad00::/64
eth0: adding default route via fe80::d2b2:c4ff:fe4c:1c09
eth0: soliciting a DHCPv6 lease
eth0: REPLY6 received from fe80::d2b2:c4ff:fe4c:1c09
eth0: adding address 2605:6001:f180:ad00::2/128
eth0: renew in 900 seconds, rebind in 1350 seconds
forked to background, child pid 25072
It can be a connector not securely fixed. Also, if you always use the same IP address you could consider setting this fixed IP in netconfig. Or use NetworkManager that automatically reconnects if you plug off then on the Ethernet connector.
This is a new laptop so I would have no idea how to check a connector. Network Manager is not working properly. The icon shows up in the task bar but it shows no connections. I went to start it and I got the message that it was already connected. But it shows no connection or any of my networks. As far as my ip my ISP uses dhcp. But now that you mention it I wonder about network manager. Any idea how to troubleshoot it? Thanks
The oldest hardware troubleshooting trick I know is to swap out the suspect cable (or mouse or whatever) with a device is known to work properly. That tends to provide a certainty about hardware that mucking about with software cannot.
I'm having problems with wireless so I'm using a wired connection. The problem is it keeps dropping my wired connection.
My wired connection would drop out continuously until I changed the default DHCP client from dhcpcd to dhclient. Might be worth a try? The setting is in /etc/NetworkManager/conf.d/00-dhcp-client.conf. You'd have to do a;
My wired connection would drop out continuously until I changed the default DHCP client from dhcpcd to dhclient. Might be worth a try? The setting is in /etc/NetworkManager/conf.d/00-dhcp-client.conf. You'd have to do a;
Code:
/etc/rc.d/rc.networkmanager restart
after making any changes I think.
Thanks but that's not the problem anymore. I can't see any of my connections including the wired one. I don't know why network manager can't detect them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.