LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Wireless Works but Wired Network does not (http://www.linuxquestions.org/questions/slackware-14/wireless-works-but-wired-network-does-not-4175483819/)

Mobile1 11-08-2013 12:05 AM

Wireless Works but Wired Network does not
 
After doing a clean install of 14.1....This is a first, I have rarely ever had this problem in the past, usually it's the other way around. I've checked the network cable, tried a different one...but nothing. Any ideas?

I should also add, I did a clean install on my other Slackware Tower, and it to has network card issues, can't get an IP addy....weird.

jprzybylski 11-08-2013 12:49 AM

Questions:
- Are you using the network scripts, or NetworkManager?
- Can you post the output of (as root):
Code:

# ifconfig
If it is NetworkManager that you are using, can you also post the output of (also as root):
Code:

# nmcli device

jon lee 11-08-2013 12:53 AM

I think the newer kernels are deprecating some of the (older?) LAN and wi-fi modules...
You may want to look into firmware blobs as well. (Yuck. Since when did everything start using firmware blobs?)

Mobile1 11-08-2013 01:02 AM

I am using Networkmanager, and here is my ifconfig:

bash-4.2# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::ca0a:a9ff:fe66:8abf prefixlen 64 scopeid 0x20<link>
ether c8:0a:a9:66:8a:bf txqueuelen 1000 (Ethernet)
RX packets 439 bytes 43073 (42.0 KiB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 15 bytes 1869 (1.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.68 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::7ae4:ff:fe15:896 prefixlen 64 scopeid 0x20<link>
ether 78:e4:00:15:08:96 txqueuelen 1000 (Ethernet)
RX packets 979 bytes 582742 (569.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 612 bytes 115951 (113.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

And here is the other:

bash-4.2# nmcli device
DEVICE TYPE STATE
eth0 802-3-ethernet disconnected
wlan0 802-11-wireless connected

jprzybylski 11-08-2013 01:30 AM

Well, your ethernet port (eth0) is being recognized, so it's likely not a driver problem. NetworkManager sees it too, though it is not connected to it.

It is entirely possible that NetworkManager is simply deciding not to automatically connect to your ethernet. If you click on the NetworkManager status icon in KDE or XFCE (or whatever you use), are there any connections available that are named something like "Auto Ethernet"?

Mobile1 11-08-2013 02:54 AM

I have a workaround, sort of, thanks to the kids in IRC : )

NM was showing wired network NOT connected in KDE. I changed the DHCP to "" instead of "yes" in the rc.inet1.conf, and now NM says it's connected.

It's not a perfect solution but it works now.

guanx 11-08-2013 04:02 AM

Quote:

Originally Posted by Mobile1 (Post 5060558)
... I changed the DHCP to "" instead of "yes" in the rc.inet1.conf, and now NM says it's connected.

I vaguely remember this same solution is given in Slackware's welcome message.

Quote:

Originally Posted by Mobile1 (Post 5060558)
It's not a perfect solution but it works now.

There is no perfect solution given the crap philosophy of NetworkManager.


All times are GMT -5. The time now is 07:36 AM.