[SOLVED] Just installed a slackbuild package for my wireless card drivers. iwconfig says the NIC doesn't exist?
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.
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.
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.
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?
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.
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
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.
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.
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.
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.
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.