LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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
  Search this Thread
Old 06-27-2019, 04:48 PM   #1
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Rep: Reputation: Disabled
Unhappy Just installed a slackbuild package for my wireless card drivers. iwconfig says the NIC doesn't exist?


I installed the slackbuild package for the drivers for my wireless card and now I'm trying to set up the network settings by following these 2 guides:
https://wiki.alienbase.nl/doku.php?i...eless_networks
https://docs.slackware.com/slackware:beginners_guide

I uncommented the 5 lines in the /etc/rc.d/rc.wireless.conf by removing the hashes between those 2 dashed borders and I ran
Code:
 /etc/rc.d/rc.inet1 eth0_start
before doing iwconfig but it still says

Code:
lo        no wireless extensions
eth0        no wireless extensions
How do I get it to detect my wireless card? I thought I did everything the guide told me to
 
Old 06-27-2019, 05:28 PM   #2
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, arch, ubuntu, others
Posts: 3,091

Rep: Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510
You most likely missing the kernel driver for you wireless adaptor and will have to build from source, as root what is the output of
Code:
lspci
The links you posted are for configuration of a working wireless adaptor for use with networking,

Quote:
I installed the slackbuild package
What slackbuild package did you install and what steps did you take to install it?

Last edited by colorpurple21859; 06-28-2019 at 05:32 AM.
 
1 members found this post helpful.
Old 06-27-2019, 05:32 PM   #3
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware 14.2 current / ArcoLinux / Void Linux
Posts: 8,864

Rep: Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851
among the kernel driver for you wireless adaptor. set your /etc/rc.d/rc.networkmanager to executable first then start it, or just reboot that for me takes care of wifi.

Last edited by BW-userx; 06-27-2019 at 05:35 PM.
 
1 members found this post helpful.
Old 06-28-2019, 04:09 AM   #4
Labinnah
Member
 
Registered: May 2014
Location: Łódź, Poland
Distribution: Slackware-current
Posts: 79

Rep: Reputation: 37
There is possibility that your network device name is not eth0. You can run:
Code:
dmesg
and search there for real interface name or:
Code:
ifconfig -a
to list all available devices in your system. If you find right name, you just use it instead of "eth0".
 
1 members found this post helpful.
Old 06-28-2019, 06:45 AM   #5
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
You most likely missing the kernel driver for you wireless adaptor and will have to build from source, as root what is the output of
Code:
lspci
The links you posted are for configuration of a working wireless adaptor for use with networking,

What slackbuild package did you install and what steps did you take to install it?
bottom 2 lines of lspci:
Code:
02:0e.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
10.00.0 Network Controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)
https://slackbuilds.org/repository/1.../broadcom-sta/
This was the slackbuild package I installed, I followed the instructions, added source files into the slackbuild file, ran it, then installed the package and then moved the package to my home folder for safekeeping afterwards.
 
Old 06-28-2019, 06:55 AM   #6
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Labinnah View Post
There is possibility that your network device name is not eth0. You can run:
Code:
dmesg
and search there for real interface name or:
Code:
ifconfig -a
to list all available devices in your system. If you find right name, you just use it instead of "eth0".
it seems the output of dmesg is so much that it won't allow me to scroll up all the way to the beginning of it?
I'm doing shift + pg up, for future reference, is there another, better way of scrolling up the console?

running ifconfig -a outputs:
Code:
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 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
 
Old 06-28-2019, 07:18 AM   #7
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware 14.2 current / ArcoLinux / Void Linux
Posts: 8,864

Rep: Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851Reputation: 1851
DMESG

Sometimes I just redirect dmesg into a file then open it up in a text editor so I can read it. It also keeps it for further reference, after next boot.
Code:
sudo dmesg > dmess
something like that. Makes it a bit easier. If your text editor too has word search, that too can be used for faster finding stuff. in lue of grep or awk 'ing its output.

Last edited by BW-userx; 06-28-2019 at 08:07 AM.
 
1 members found this post helpful.
Old 06-28-2019, 09:42 AM   #8
Labinnah
Member
 
Registered: May 2014
Location: Łódź, Poland
Distribution: Slackware-current
Posts: 79

Rep: Reputation: 37
Quote:
Originally Posted by 700 View Post
it seems the output of dmesg is so much that it won't allow me to scroll up all the way to the beginning of it?
I'm doing shift + pg up, for future reference, is there another, better way of scrolling up the console?
You can redirect output to some pager application like more, less or most. I prefer most
Code:
dmesg | most
Quote:
Originally Posted by 700 View Post
running ifconfig -a outputs:
Code:
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 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
Strange. Even no eth0. It should list all devices available to your system. It seems that kernel drivers are not loaded. For PCI devices this should be done automatically.
Run:
Code:
lspci -v
and search for "Kernel driver in use" and "Kernel modules" lines for devices you are interested in.
 
1 members found this post helpful.
Old 06-29-2019, 09:42 AM   #9
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Labinnah View Post
You can redirect output to some pager application like more, less or most. I prefer most
Code:
dmesg | most


Strange. Even no eth0. It should list all devices available to your system. It seems that kernel drivers are not loaded. For PCI devices this should be done automatically.
Run:
Code:
lspci -v
and search for "Kernel driver in use" and "Kernel modules" lines for devices you are interested in.
it says in the bottom-most lines for the ethernet controller and the network controller respectively:
Code:
kernel modules: b44
and
Code:
kernel modules: ssb, wl
The first (and only) thing I notice is that for those two devices, unlike all of the other devices in that list, these are the only ones that don't have a "Kernel driver in use" line.

Any idea why that is?
 
Old 06-29-2019, 09:56 AM   #10
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, arch, ubuntu, others
Posts: 3,091

Rep: Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510
did you do a
Code:
modprobe wl
 
1 members found this post helpful.
Old 06-29-2019, 02:58 PM   #11
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Original Poster
Rep: Reputation: Disabled
Unhappy

Quote:
Originally Posted by colorpurple21859 View Post
did you do a
Code:
modprobe wl
no but I just tried it now and nothing happened. No text, nothing.
Tried iwconfig again, said no wireless extensions.
 
Old 06-29-2019, 10:09 PM   #12
Labinnah
Member
 
Registered: May 2014
Location: Łódź, Poland
Distribution: Slackware-current
Posts: 79

Rep: Reputation: 37
Modprobe usually don't output anything. To check if something happen run dmesg just after modprobe. Last lines in output should be connected with your action.

For sure before modprobe you can run
Code:
depmod -a
It refresh module dependency. If they are nonexistent or outdated module can be not loaded.
 
Old 06-29-2019, 10:53 PM   #13
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, arch, ubuntu, others
Posts: 3,091

Rep: Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510
modprobe -v wl
 
1 members found this post helpful.
Old 06-30-2019, 09:47 AM   #14
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Labinnah View Post
Modprobe usually don't output anything. To check if something happen run dmesg just after modprobe. Last lines in output should be connected with your action.

For sure before modprobe you can run
Code:
depmod -a
It refresh module dependency. If they are nonexistent or outdated module can be not loaded.
ah ok, thanks
 
Old 06-30-2019, 09:52 AM   #15
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Labinnah View Post
Modprobe usually don't output anything. To check if something happen run dmesg just after modprobe. Last lines in output should be connected with your action.

For sure before modprobe you can run
Code:
depmod -a
It refresh module dependency. If they are nonexistent or outdated module can be not loaded.
ok, so in the dmesg; it said:
Code:
wl driver 6.30.223.271 (r587334) failed with code 21
ERROR @wl_cfg80211_detach : NULL ndev->ieee80211ptr, unable to deref wl
 
  


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



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] No package 'x11' found No package 'xext' found No package 'xdamage' found No package 'xfixes' found No package 'x11-xcb' found Jigsaw Linux From Scratch 12 04-25-2019 07:33 AM
[SOLVED] I've just installed a program but my terminal says it's not installed. Moeman Linux - Newbie 18 08-03-2017 12:42 PM
RPM package manager says package needs to be installed. But I already installed it! nick623 Linux - Software 2 05-24-2005 02:15 AM
rpm -ivh says installed rpm -e says not installed ??? skog Fedora 3 12-22-2004 03:52 PM
Just Installed Mandrake 10.0 but no iwconfig wcn Linux - Wireless Networking 1 05-08-2004 08:30 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:28 PM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration