Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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.
Hello. I installed Slackware 12 on my laptop with a wifi card that is supported in the 2.6.24 kernel (b43 driver).
From the fresh install, I upgraded to -current and after that, I upgraded the kernel to 2.6.24.2, with all the drivers I need.
The module b43 loads fine, but no wireless device is present in ifconfig or iwconfig. I assume this has something to do with the rc scripts, but I can't figure it out.
./rc.inet1 start, restart, etc., doesn't do anything for the wireless, and ./rc.wireless start tells me it can only be started by rc.inet1.
A few days ago I tried Slackware 12 with a 2.6.24 kernel (not upgrading to -current), and also the b43 module loaded fine, and wlan0 was added automatically, I didn't have to do anything. So it's definitely something with the scripts, when upgrading to -current.
Location: East Coast, USA (in "the great northeast")
Distribution: Custom / from source; Fedora, Debian, CentOS, Scientific; LFS.
Posts: 94
Rep:
Quote:
Originally Posted by Daemon-
Hello. I installed Slackware 12 on my laptop with a wifi card that is supported in the 2.6.24 kernel (b43 driver).
...
Any hints?? Thanks!
What card are you using, and what chipset, etc. does it have on it? Given that you're using the b43 module, I'm assuming it's a Broadcom of some sort; do you have a 4306? 4308? Also, what kind of machine (brand, processor, chipset) are you using it in?
Have you dealt with a Broadcom NIC before? At this point in history (2.6.23 kernels and up, more or less), it's (usually) a matter of running the appropriate firmware cutter (b43-fwcutter or bcm43xx-fwcutter), then loading the appropriate module (b43 or bcm43xx), and doing whatever network configuration is necessary on your distribution.
Quote:
The module b43 loads fine, but no wireless device is present in ifconfig or iwconfig. I assume this has something to do with the rc scripts, but I can't figure it out.
What are you seeing in dmesg, and in /var/log/messages or whatever the slackware equivalent of that is? Also, what does lspci (eg., "lspci -vv") show the card to be in the first place?
From the sound of it, you don't have the correct firmware in /usr/lib/firmware; the dmesg output is pretty blunt about what it's not able to find, etc.
Make sure your chip is supported first and see if you can figure out which of the three (b43, legacy, or bcm43xx) combinations of fwcutter, firmware, and driver you're going to need to use; at worst, you can use the process of elimination...
Well, thanks for the answer. The card is a broadcom 4311 rev 02. I know about the b43 driver, and the firmware.. as I said, I already tried the card with the same kernel on a fresh slack 12 install a few days ago, in the same laptop.. and it worked like a charm. I kept all the files I needed (firmware, etc.), followed the same instructions as before, but nothing happens this time..
lspci -v shows:
03:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 02)
Subsystem: Hewlett-Packard Company Unknown device 1375
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at b8000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information
Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [d0] Express Endpoint IRQ 0
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 1a-00-da-ff-ff-73-3d-4d
Capabilities: [16c] Power Budgeting
Nothing happens in dmesg when I load/unload the b43 module..
I really have no idea, because I tell you, I tried this with the same kernel, firmware, etc., a few days ago..
Actually, what I DO notice from lspci -v is that the IRQ 11 is already taken by the video card and an USB controller. I'm not sure about how these IRQ sharing thing works, anyway USB and video card are working fine.
as I said, I already tried the card with the same kernel on a fresh slack 12 install a few days ago, in the same laptop.. and it worked like a charm. I kept all the files I needed (firmware, etc.), followed the same instructions as before, but nothing happens this time..
Unless I'm very mistaken, a stock Slackware install would have been a 2.6.21 kernel, and I believe that had the bcm43xx driver, not the b43 driver. The reason this would be important is that the b43 driver seems to need different firmware, so if you just kept the firmware from the original install, it might not work with b43.
Yes, I meant to say a fresh Slackware 12 install plus a custom kernel, 2.6.24, compilated by myself.
What I mean is that the only thing that could have messed this up is the upgrade to -current, and not a kernel issue, but more likely an rc.d issue.
I will reinstall everything, being fresh installs I don't have any important data and it takes just a few minutes.. first I will install slackware 12 from the dvd, upgrade the kernel and if everything works, I will see then what to do. I'm not too much into upgrading to current, it's the first time I do it; I wonder if I can keep a custom kernel in the process..
I am really sorry for my stupidity. I was doing everything ok. The problem is that my card is "rev 02", and it needs a 2.6.24 special patch to work.. I did that a few days ago but I completely forgot about it now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.