[SOLVED] No wifi in kernel 3.18.0-rc4 - /proc files
Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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.
I had to do a kernel 'git bisect' and have tried to build a current kernel. It fails to deliver wifi, and complains of /proc/net/wireless file being missing.
Where the <expletive deleted> do I set that? I'm running slackware-current dated 09/14. The wifi is a B43 using the standard kernel driver. It is a usb chip somehow linked to the pci bus via SSB, and that is appearing on the lspci output, which is a fair sign of kernel recognition.
bash-4.3# cat /proc/net/wireless
Inter-| sta-| Quality | Discarded packets | Missed | WE
face | tus | link level noise | nwid crypt frag retry misc | beacon | 22
Seems like when I had a laptop that used the b43 module I had to take it through a process to get it to work. As I recall I found it on SBO / Slackbuilds.org.
I just lsmod | grep b43 to see if the kernel sees it and has loaded the module, otherwise I could find references to it in messages when it was detected during boot.
Will get to that box and double check module loading. It looks good - showing in lspci. I will check firmware too. That thing is offline due to the wifi issue.
Slackbuilds b43-firmware and b43-fwcutter were the packages, maintained by none other than r.workman (who is likely lurking about giggling at our ineptitude...)
Thanks for the replies, guys. This is not a newbie question.
This box has run b43 for years and ran it on this install. This is a kernel issue. That's all that changed. The details:
lsmod |grep b43 shows
b43
bcma
ssb
According to logs, it's loading firmware version 666.2.
ifconfig wlan0 up does just that. (No bytes ever sent/received, etc).
iwconfig shows wlan0 as having no wireless extensions, and shows sit0 that I know nothing about.
cat /proc/net/wireless shows "No such file or directory"
The logs show it finds the Broadcom 4311 WLAN, the PHY, and the Radio and loads the b43xx driver [ Features: PL ]. But nothing works. All the wireless utilities give me the middle finger :-(.
On a reboot, it throws these errors
Error for wireless request "Set Mode" <blah>
Error for wireless request "Set Frequency" <blah>
set failed on wlan0: invalid argument
followed by a string of ioctl errors as it tailspins.
I'm thinking either
Some files have been moved to sys and my software wants them in /proc and I have to rebuild with some "keep those old files in /proc" setting
The b43 modules or part of it is incorrigibly knackered by all this git bisecting that has gone on.
Right -sending this from the offending box. We are sorted. It's singing on wifi, so I presume all the files are correct enough.
In the config, mac80211=y is not good enough, apparently. It's now a module. I also added FUSE_FS=m as well, and that sorted it out.
The git bisect did mess around whether something was set to module, or in the case of fuse, at all. I never had a good .config for this box before on such a late kernel, so that's good. (Hmmm, better check sound and the other stuff before I crow).
Thanks. I ran off and checked other stuff - sound notably and sound id good, as far as that goes (not very far).
The powersaving seems ok also, so the only untested item is bluetooth, and I really don't care. Bluetooth was always dependent on the sun not being behind a cloud (Rare in Ireland), balancing forces from the correct coordination of planets & galaxies, and a complete lack of disturbance in the Space/Time continuum. :-P.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.