LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 11-07-2013, 11:05 PM   #1
Mobile1
Member
 
Registered: Jun 2006
Location: Abbotsford, B.C.
Distribution: Slackware64 14.1
Posts: 101

Rep: Reputation: 6
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.

Last edited by Mobile1; 11-07-2013 at 11:20 PM.
 
Old 11-07-2013, 11:49 PM   #2
jprzybylski
Member
 
Registered: Apr 2011
Location: Canada
Distribution: Slackware
Posts: 86

Rep: Reputation: 21
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

Last edited by jprzybylski; 11-07-2013 at 11:51 PM. Reason: Clarifications
 
Old 11-07-2013, 11:53 PM   #3
jon lee
Member
 
Registered: Jul 2013
Posts: 81

Rep: Reputation: Disabled
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?)
 
Old 11-08-2013, 12:02 AM   #4
Mobile1
Member
 
Registered: Jun 2006
Location: Abbotsford, B.C.
Distribution: Slackware64 14.1
Posts: 101

Original Poster
Rep: Reputation: 6
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
 
Old 11-08-2013, 12:30 AM   #5
jprzybylski
Member
 
Registered: Apr 2011
Location: Canada
Distribution: Slackware
Posts: 86

Rep: Reputation: 21
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"?
 
Old 11-08-2013, 01:54 AM   #6
Mobile1
Member
 
Registered: Jun 2006
Location: Abbotsford, B.C.
Distribution: Slackware64 14.1
Posts: 101

Original Poster
Rep: Reputation: 6
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.
 
Old 11-08-2013, 03:02 AM   #7
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 145Reputation: 145
Quote:
Originally Posted by Mobile1 View Post
... 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 View Post
It's not a perfect solution but it works now.
There is no perfect solution given the crap philosophy of NetworkManager.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Wireless gets IP, but cannot ping, wired works fine analogrival Linux - Wireless Networking 15 11-10-2011 04:05 AM
bridging a wireless and wired network causes wired to stop working royce2020 Linux - Networking 0 04-21-2009 04:48 PM
Wireless router: works wired, fails wireless TotalLinuxNoob Linux - Networking 8 01-12-2009 12:56 PM
Wired Linksys router - works...wireless-g no go. mynameshagop Linux - Newbie 11 01-11-2006 05:10 AM
Wired network works for a few seconds and then stops paulbutcher Linux - Networking 7 07-05-2005 07:54 AM


All times are GMT -5. The time now is 12:00 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration