[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.
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'
Ok, I've installed the firmware and fwcutter packages now. But I can't do the first modprobe command; it says:
Code:
modprobe: FATAL: module ssb is in use.
I could do the second one you told me though, the one without the -r argument.
I tried iwconfig and its added a wlan0. So I think it's working? Though it says encryption key is set to off.
The OP has a Broadcom cable interface that uses b44 driver, but that driver is
blacklisted by the broadcom-sta wl driver.
I think that that is a bug in the broadcom-sta.SlackBuild. The 'b44' does not support wireless devices, it is meant for PCI ethernet.
The b43 and b44 modules both depend on the ssb driver. The 'ssb' driver is also blacklisted by the broadcom-sta package which is also incorrect.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
I never saw that error.
My wireless connection is pretty stable, working for months,
but sometimes it just doesn't connect and stays trying to connect.
What I do (and works) is, at console, run nmtui and delete the saved
wireless connection, and recreate it. Maybe you could try this.
edit- or what Richard Cranium said.
I just saw my dhcp client and it is the Slackware recommended (dhcpcd),
not the NetworkManager recommended (dhclient).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.