Slackware - Installation This forum is for the discussion of installation issues with Slackware.
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.
#31
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858
Oh, yes. I'd uninstall wicd. I haven't had any problems with networkmanager when I used it in 14.1 or 14.2.
#32
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858
Quote:
Originally Posted by
scythempress
Let me correct me. The wireless is up and running not the cable.
You're connected via wireless?
Now I'm afraid to tell you to touch anything.
#33
Member
Registered: Dec 2012
Location: Tradinghouse Lake, Texas
Distribution: Slackware
Posts: 116
Original Poster
Rep:
I agree. Yes I am wireless. Again wicd and nw are or were executable. Since wicd is not connecting wireless should I dump it? Or at least change it from executable? And if so how? ah seen your post. Will uninstall WICD
#34
Member
Registered: Dec 2012
Location: Tradinghouse Lake, Texas
Distribution: Slackware
Posts: 116
Original Poster
Rep:
Ok went to "root@scythempress:/etc/xdg/autostart" and did "rm wicd-tray.desktop" will that do it or is there something else I should do?
#35
Member
Registered: Dec 2012
Location: Tradinghouse Lake, Texas
Distribution: Slackware
Posts: 116
Original Poster
Rep:
I want to reboot and see if it works but I am afraid too. I am going to anyway, standby.
#36
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858
Did you also uninstall the wicd package?
#37
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858
Quote:
Originally Posted by
scythempress
I want to reboot and see if it works but I am afraid too. I am going to anyway, standby.
Heh. You'll have to do it eventually. Grasp the nettle!
#38
Member
Registered: Dec 2012
Location: Tradinghouse Lake, Texas
Distribution: Slackware
Posts: 116
Original Poster
Rep:
Ok, well wicd is still there. I had to restart NW but once I put my KDE wallet password in, it hooked right up
#39
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858
At this point, you can reconfigure NW to manage both your wired and wireless connections. Then again, you may want to go to bed.
Please run the command
Code:
cat /etc/udev/rules.d/70-persistent-net.rules
and provide the output.
On my machine, the output looks like...
Code:
root@hp635:~# cat /etc/udev/rules.d/70-persistent-net.rules
# PCI device 0x10ec:0x8176 (rtl8192ce)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="9c:b7:0d:a5:53:ca", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
# PCI device 0x10ec:0x8136 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:9c:02:1e:54:7b", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
root@hp635:~#
When you compare it against the output of
ifconfig ...
Code:
root@hp635:~# ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:9c:02:1e:54:7b txqueuelen 1000 (Ethernet)
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
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 1 (Local Loopback)
RX packets 5 bytes 249 (249.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5 bytes 249 (249.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.16.0.11 netmask 255.255.255.0 broadcast 172.16.0.255
inet6 fe80::9eb7:dff:fea5:53ca prefixlen 64 scopeid 0x20<link>
ether 9c:b7:0d:a5:53:ca txqueuelen 1000 (Ethernet)
RX packets 143137 bytes 94635360 (90.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 135309 bytes 23481955 (22.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@hp635:~#
...you can see how the ifconfig
ether entries match what is in 70-persistent-net.rules.
#40
Member
Registered: Dec 2012
Location: Tradinghouse Lake, Texas
Distribution: Slackware
Posts: 116
Original Poster
Rep:
Ok used the following:
Code:
/etc/rc.d/rc.wicd stop
Now will that do it or do I need to do something else?
#41
Member
Registered: Dec 2012
Location: Tradinghouse Lake, Texas
Distribution: Slackware
Posts: 116
Original Poster
Rep:
Code:
root@scythempress:~# cat /etc/udev/rules.d/70-persistent-net.rules
# PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0/ssb1:0 (b44)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:70:6e:fe:ab", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
root@scythempress:~# ifconfig
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.0.8 netmask 255.255.255.0 broadcast 10.0.0.255
inet6 fe80::216:44ff:fee1:1c2b prefixlen 64 scopeid 0x20<link>
ether 00:16:44:e1:1c:2b txqueuelen 1000 (Ethernet)
RX packets 1879 bytes 342745 (334.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 40517
TX packets 595 bytes 106103 (103.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17 base 0xc000
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 4 bytes 288 (288.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4 bytes 288 (288.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
#42
Member
Registered: Dec 2012
Location: Tradinghouse Lake, Texas
Distribution: Slackware
Posts: 116
Original Poster
Rep:
BTW I am in rural Texas on a satellite feed if that has any bearing
#43
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858
If you run (as root)
, that would solve the problem.
The other option would be to run (as root)
Code:
chmod -x /etc/rc.d/rc.wicd
. If you think that you might want to wicd later, then choose this option.
#44
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858
Quote:
Originally Posted by
scythempress
Code:
root@scythempress:~# cat /etc/udev/rules.d/70-persistent-net.rules
# PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0/ssb1:0 (b44)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:70:6e:fe:ab", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
root@scythempress:~# ifconfig
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.0.8 netmask 255.255.255.0 broadcast 10.0.0.255
inet6 fe80::216:44ff:fee1:1c2b prefixlen 64 scopeid 0x20<link>
ether 00:16:44:e1:1c:2b txqueuelen 1000 (Ethernet)
RX packets 1879 bytes 342745 (334.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 40517
TX packets 595 bytes 106103 (103.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17 base 0xc000
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 4 bytes 288 (288.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4 bytes 288 (288.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Hmm. Ok. As root, run the command
and then run
ifconfig to see if your ethernet card magically appears.
EDIT: If the insmod command fails, please give me the error message. I didn't run it locally.
Last edited by Richard Cranium; 07-20-2016 at 10:43 PM .
#45
Member
Registered: Dec 2012
Location: Tradinghouse Lake, Texas
Distribution: Slackware
Posts: 116
Original Poster
Rep:
Code:
insmod ERROR could not load module b44: no such file or directory
Am on other machine again.
Code:
As root typed /etc/rc.d/rc.networkmanager restart and got -su: /etc/rc.d/rc.networkmanager: Permission denied
But Wicd is gone!
All times are GMT -5. The time now is 06:19 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 .
