LinuxQuestions.org
Visit Jeremy's Blog.
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-30-2019, 10:04 AM   #16
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,592

Rep: Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010

Before installing broadcom-sta did you check whether the "b43" kernel driver which is part of the Slackware kernel works with your wireless card?
When you install broadcom-sta, the package post-install script blacklists "b43" so that the two won't conflict.

Perhaps your card works with b43. Also, perhaps the "wl" driver requires a firmware file you do not have installed. Just guessing.
 
1 members found this post helpful.
Old 06-30-2019, 10:49 AM   #17
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Alien Bob View Post
Before installing broadcom-sta did you check whether the "b43" kernel driver which is part of the Slackware kernel works with your wireless card?
When you install broadcom-sta, the package post-install script blacklists "b43" so that the two won't conflict.

Perhaps your card works with b43. Also, perhaps the "wl" driver requires a firmware file you do not have installed. Just guessing.
No, I don't think I did check, how do you check whether it works with it?

running lspci -v tells me that the ethernet controller has the b44 kernel module and the network controller has the ssb and wl modules but neither the ethernet nor the network controller have any kernel drivers in use apparently.

Also, could you clear something up for me? A few people, as well as some man pages seem to imply that when slackware says "ethernet", it's not just referring to directly wired internet connection between a computer and a router through an ethernet cable as opposed to wireless connection. Like, I think I remrmber someone saying Eth0 doesn't necessarily have to be a wired connection? So, when Slackware says "ethernet", is it just talking about ethernet in the wired sense? or is it just a stand in for any method of connecting to the net?
 
Old 06-30-2019, 12:44 PM   #18
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,592

Rep: Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010
Quote:
Originally Posted by 700 View Post
No, I don't think I did check, how do you check whether it works with it?
Well, by not installing broadcom-sta, booting the computer and inspecting your OS log files as well as output from "ifconfig -a" and "iwconfig". Depending on your hardware, you may have to obtain a Broadcom firmware file as well. Also, I do not think that the "wl" driver loads automatically, but the "b43" driver should. And using the "dmesg" command you should find evidence of that.

Quote:
running lspci -v tells me that the ethernet controller has the b44 kernel module and the network controller has the ssb and wl modules but neither the ethernet nor the network controller have any kernel drivers in use apparently.
The "ssb" driver is actually one of the dependencies for "b43". Run "modprobe -n --show-depends b43" to see that.

Quote:
Also, could you clear something up for me? A few people, as well as some man pages seem to imply that when slackware says "ethernet", it's not just referring to directly wired internet connection between a computer and a router through an ethernet cable as opposed to wireless connection. Like, I think I remrmber someone saying Eth0 doesn't necessarily have to be a wired connection? So, when Slackware says "ethernet", is it just talking about ethernet in the wired sense? or is it just a stand in for any method of connecting to the net?
Read more on the OSI model if you want to understand this. It is something else than you think; it has nothing to do with the difference between wired and wireless cards. And yes, the network device naming is pretty erratic. A wireless interface can start with "eth". If your OS would run systemd then the network device naming becomes crazy wild.

Ethernet is one of several hardware protocols in Layer 1 and also one of the network protocols in Layer 2. See https://en.wikipedia.org/wiki/OSI_model to start with.
 
1 members found this post helpful.
Old 06-30-2019, 02:18 PM   #19
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Alien Bob View Post
Well, by not installing broadcom-sta, booting the computer and inspecting your OS log files as well as output from "ifconfig -a" and "iwconfig". Depending on your hardware, you may have to obtain a Broadcom firmware file as well. Also, I do not think that the "wl" driver loads automatically, but the "b43" driver should. And using the "dmesg" command you should find evidence of that.


The "ssb" driver is actually one of the dependencies for "b43". Run "modprobe -n --show-depends b43" to see that.


Read more on the OSI model if you want to understand this. It is something else than you think; it has nothing to do with the difference between wired and wireless cards. And yes, the network device naming is pretty erratic. A wireless interface can start with "eth". If your OS would run systemd then the network device naming becomes crazy wild.

Ethernet is one of several hardware protocols in Layer 1 and also one of the network protocols in Layer 2. See https://en.wikipedia.org/wiki/OSI_model to start with.
Thanks, I'll take a look at the OSI model.
I just find it confusing because there were options in a particular file, I think it was the /etc/rc.d/rc.inet1.conf file? where it lists numbered Eth interfaces but also lists WLAN interfaces. So if Eth can mean wired as well as wireless, then how would WLAN be distinct from that? Sorry if the OSI model explains it, I'll read it later.

So any idea how I can get the firmware for the BCM4311? Broadcom doesn't list it on their site, or at least I can't seem to find it. I think I remember using a file called b43 fwcutter or something for ubuntu when I had similar problems with the wireless card. I used that along with a b43 firmware installer but I'm not sure how different the process would be on slackware or if there even is a same process for wl rather than b43.

edit: ah, I just realized. b43 is compatible with my wireless card. So with that in mind, seeing as how far I've got (or how far I haven't got) with using the wl module, what would you say would be easier for me to do now? get it working with b43? or wl? I think I'm just missing the firmware for the wl driver.

Last edited by 700; 06-30-2019 at 02:22 PM.
 
Old 06-30-2019, 02:40 PM   #20
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,592

Rep: Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010
Getting the firmware file: https://slackbuilds.org/repository/1.../b43-fwcutter/
 
1 members found this post helpful.
Old 06-30-2019, 07:09 PM   #21
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Alien Bob View Post
Thanks, so after I run this, I should unblacklist the b43 stuff right? Or will this extract the firmware I need from wl as well despite the "b43" in the name of the fwcutter file? (I might just be being thick in asking that but what the hell, no harm in checking).
 
Old 07-01-2019, 03:03 AM   #22
Labinnah
Member
 
Registered: May 2014
Location: Łódź, Poland
Distribution: Slackware-current
Posts: 81

Rep: Reputation: 38
I cannot help you any more. This binary blob error has no solution in net.

My only advice is you can try b43 open source driver. Only remember to install firmware https://slackbuilds.org/repository/1.../b43-firmware/

Edit:
Sorry, for some reason I did't see Eric responses.

Last edited by Labinnah; 07-01-2019 at 04:44 AM. Reason: Duplicate answer
 
1 members found this post helpful.
Old 07-01-2019, 05:49 AM   #23
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,592

Rep: Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010Reputation: 6010
Quote:
Originally Posted by 700 View Post
Thanks, so after I run this, I should unblacklist the b43 stuff right? Or will this extract the firmware I need from wl as well despite the "b43" in the name of the fwcutter file? (I might just be being thick in asking that but what the hell, no harm in checking).
Remove the broadcom-sta package, remove the blacklist file /etc/modprobe.d/b43_blacklist.conf and reboot.
Then examine the output of the "dmesg" command to see whether the b43 driver is loading and whether it does indeed complain about a missing firmware file. In that case, install the b43-firmware and b43-fwcutter packages (b43-fwcutter first) - the b43-firmware package will extract the firmware file and install it into your computer.
 
2 members found this post helpful.
Old 07-01-2019, 07:50 AM   #24
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Alien Bob View Post
Remove the broadcom-sta package, remove the blacklist file /etc/modprobe.d/b43_blacklist.conf and reboot.
Then examine the output of the "dmesg" command to see whether the b43 driver is loading and whether it does indeed complain about a missing firmware file. In that case, install the b43-firmware and b43-fwcutter packages (b43-fwcutter first) - the b43-firmware package will extract the firmware file and install it into your computer.
Ok, so I removed broadcom-sta-6.30.223.271_4.4.14_smp-i586-2_SBo.tgz (the thing outputted by running the slackbuild script), but that's not the same as uninstalling the package is it? It looks like slackware docs only cover installing and upgrading packages, so how would I go about uninstalling it? And how do I find out the exact name of the package so I can uninstall it? because the package name is going to be different to the name of the file isn't it?
 
Old 07-01-2019, 08:02 AM   #25
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Alien Bob View Post
Remove the broadcom-sta package, remove the blacklist file /etc/modprobe.d/b43_blacklist.conf and reboot.
Then examine the output of the "dmesg" command to see whether the b43 driver is loading and whether it does indeed complain about a missing firmware file. In that case, install the b43-firmware and b43-fwcutter packages (b43-fwcutter first) - the b43-firmware package will extract the firmware file and install it into your computer.
After removing the blacklist and rebooting, even though I still haven't uninstalled the broadcom package, I ran dmesg again and I skimmed it for any mention of b43 and this is what I found:
Code:
b43-phy0: Broadcom 4311 WLAN found (core revision 10)
b43-phy0: Found Phy: Analog 4, Type 2 (G), Revision 8
b43-phy0: Found Radio: Manuf 0x17F, ID 0x2050, Revision 2, Version 0
Broadcom 43xx driver loaded [Features: PNLS ]
b43 ssb0:0: Direct firmware load for b43/ucode5.fw failed with error -2
b43 ssb0:0: Direct firmware load for b43/ucode5.fw failed with error -2
b43 ssb0:0: Direct firmware load for b43-open/ucode5.fw failed with error -2
So I'm guessing "error -2" means I have to install the firmware.
 
Old 07-01-2019, 09:50 AM   #26
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, arch, ubuntu, others
Posts: 3,114

Rep: Reputation: 512Reputation: 512Reputation: 512Reputation: 512Reputation: 512Reputation: 512
Quote:
So I'm guessing "error -2" means I have to install the firmware.
you will need the windows driver and the bwcutter will extract the firmware from it
 
1 members found this post helpful.
Old 07-01-2019, 10:24 AM   #27
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
you will need the windows driver and the bwcutter will extract the firmware from it
Windows driver? Bwcutter? Do you mean the wl driver and the fwcutter? Or are those separate things altogether?
 
Old 07-01-2019, 10:33 AM   #28
Paulo2
Member
 
Registered: Aug 2012
Distribution: Slackware64 -current (started with 13.37(32))
Posts: 466

Rep: Reputation: 163Reputation: 163
The OP has a Broadcom cable interface that uses b44 driver, but that driver is
blacklisted by the broadcom-sta wl driver.

In this case, is there a way to both b44 and wl coexist?
Since each one will control a different card.

I have a notebook with Broadcom 4312 and the b43 driver works ok.
From SBo install both b43-firmware and b43-fwcutter, then run
'modprobe -r b43 bcma ssb' and then run 'modprobe b43 bcma ssb'
to reload. This works here.

edit-
Quote:
Originally Posted by 700 View Post
Ok, so I removed broadcom-sta-6.30.223.271_4.4.14_smp-i586-2_SBo.tgz (the thing outputted by running the slackbuild script), but that's not the same as uninstalling the package is it? It looks like slackware docs only cover installing and upgrading packages, so how would I go about uninstalling it? And how do I find out the exact name of the package so I can uninstall it? because the package name is going to be different to the name of the file isn't it?
You have to run
Code:
removepkg <pkg name>
to uninstall a package from the system.
In this case, 'removepkg broadcom-sta'

Last edited by Paulo2; 07-01-2019 at 10:37 AM.
 
1 members found this post helpful.
Old 07-01-2019, 10:55 AM   #29
700
Member
 
Registered: Jun 2019
Distribution: Slackware
Posts: 46

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Paulo2 View Post
The OP has a Broadcom cable interface that uses b44 driver, but that driver is
blacklisted by the broadcom-sta wl driver.

In this case, is there a way to both b44 and wl coexist?
Since each one will control a different card.

I have a notebook with Broadcom 4312 and the b43 driver works ok.
From SBo install both b43-firmware and b43-fwcutter, then run
'modprobe -r b43 bcma ssb' and then run 'modprobe b43 bcma ssb'
to reload. This works here.

edit-

You have to run
Code:
removepkg <pkg name>
to uninstall a package from the system.
In this case, 'removepkg broadcom-sta'
Thanks, quick question, do I need to extract/decompress the source before I run the slack build script? Or is it fine just putting it in there as a bz2?
 
Old 07-01-2019, 11:07 AM   #30
Paulo2
Member
 
Registered: Aug 2012
Distribution: Slackware64 -current (started with 13.37(32))
Posts: 466

Rep: Reputation: 163Reputation: 163
Quote:
Originally Posted by 700 View Post
Thanks, quick question, do I need to extract/decompress the source before I run the slack build script? Or is it fine just putting it in there as a bz2?
No need to decompress, the slackbuild will do it, just put the tarball
side by side with the SBo files.

Better way, install sbopkg, it downloads and installs automatically
with dependencies too.


edit-
sbopkg https://www.sbopkg.org/

You didn't say (at least I couldn't find) if you're
running -current or -stable,
if -current https://www.linuxquestions.org/quest...ls-4175561999/

Last edited by Paulo2; 07-01-2019 at 11:16 AM. Reason: provide links
 
1 members found this post helpful.
  


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 12:36 AM.

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