SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I would like to try kernel 2.6.17-rc5 on my laptop because it has build-in support for my WLAN card. Apart from that, I'd like to stick as much as possible with Slackware-stable and not use Slackware-current.
IIRC from some posts here on LQ, udev needs to be upgraded from -stable for kernels 2.6.14 and above. Is the udev package from -current the right one to use?
Is udev the only package that I would need to pull from -current to get the latest kernel to work?
I have a PCMCIA card with a Broadcom 43xx chip which is why I wanted to try 2.6.17.
I've downloaded and tried to setup rc5 but I just cannot seem to find the relevant option for the bcm43xx driver. I've compiled a kernel with just about every option checked and there's no bcm43xx module.
Can you perhaps point me to the correct option in menuconfig?
If the patch has applied correctly, then you first need to get into Networking and enable Generic IEEE 802.11 Networking Stack. Once that is checked, then you should be able to see the bcm43xx driver in Device Drivers > Network Device Support > Wireless LAN (non-hamradio). You do have to have the generic IEEE stack selected before you can see the bcm43xx driver.
If you don't see the generic IEEE stack, then odds are the patch didn't apply correctly.
Ah, now I get where you're stuck. The 2.6.17-rcX kernels aren't distributed as a full kernel source package. In other words, if you download 2.6.17-rc5, you should be getting a file called patch-2.6.17-rc5.bz2, and you can't compile that into a functional kernel. Instead, you have to download the full source for 2.6.16 (NOT 2.6.16.x) and apply the 2.6.17-rc5 patch. It is actually pretty easy. Download both the full 2.6.16 kernel source and the 2.6.17-rc5 patch and uncompress them both. Next, drop into the linux-2.6.16 directory and run
patch -p1 < /path/to/patch-2.6.17-rc5
As long as you don't get any errors, you should be able to configure and compile the kernel as you normally would.
Hmmm I downloaded a full -rc5, the file name is linux-2.6.17-rc5.tar.bz2, 40MB in size. That should be all, and the kernel does work. But I have found the bcm43xx option now, the problem was probably the missing "Generic IEEE 802.11 Networking Stack". Thanks.
Yes, udev-064 sort of works for newer kernels, but it is very broken regarding input devices (check the contents of /dev/input on a newer kernel if you are still using the old udev).
udev-071 is the minimum specified in the kernel ChangeLog, and 072 provides a few more bugfixes to make 071 useable.
uselpa, if you're trying to use this driver with a BCM4318, you might run into problems (the fix is expected in 2.6.18-rc if you do run into problems). Other BCM43xx chipsets are fine. You also need the firmware for this device installed in /lib/firmware. Don't use your Windows drivers for them, Google for a file called "wl_apsta.o" and rip the firmware out of that (apparently it has the latest firmware version).