Broadcom drivers.
Apparently, Broadcom now offers what they call "hybrid" broadcom drivers for Linux. I am trying to install them, but I am getting an error. I am following the instructions from this txt file:
http://www.broadcom.com/docs/linux_sta/README.txt and when I go to step 5 to make a Linux loadable kernel module (LKM) this is what happens: Code:
root@l3n0v0:~/hybrid_wl# make -C /lib/modules/2.6.29.6-smp/build M='pwd' |
M='pwd' <-- note the quotes;
Is that a typo or something, or are you actually using '''' <-- those single quotes, instead of ```` <-- backticks? Sasha |
Quote:
|
No reason to feel stupid -- sillier things have stumped lots of people, lots of times :)
Let us know.. |
Ok, I fixed the command, but now this is what I get:
Code:
root@l3n0v0:~/hybrid_wl# make -C /lib/modules/2.6.29.6/build M=`pwd` |
Generally speaking, the above happens when either:
1-- the build process can't find the header files it's looking for, or 2-- something else really weird, like the driver and kernel version are incompatible. Possible other causes too, perhaps.. You DO have the kernel headers package installed, right? One thing I will suggest though, which may or may not help THIS problem, but may make things work more cleanly in general, would be: Where you use this command: make -C /lib/modules/2.6.29.6/build M=`pwd` I would replace the 2.6.29.6 with `uname -r` instead (don't omit the backticks). At least that way, you know the build is looking in the right place for your kernel's build directory (the symlink). NOTE THOUGH: I don't know how the word "linux-" is getting prepended (on the next line: make: Entering directory `/usr/src/linux-2.6.29.6') onto the kernel version you are supplying, so if `uname -r` gives you more trouble, such as it starts looking for "linux-linux-2.6.29.6") you'll need to switch back. Not sure at this moment what else to suggest, but more suggestions will come :) so not to worry. At this point (regarding your earlier comment) I would definitely not switch to ndiswrapper; it looks so far like this is a little buggy, but all in all, it should work for you eventually. Good luck! Sasha |
I will try what you are suggesting, and I have no clue whether the kernel headers package is installed. I have not installed anything since the initial setup of slackware. So if the kernel headers package is not part of the "full" install option in the initial setup, then no, its not installed. If it is part of it, then yes, it is.
|
Yep, the headers should be installed if you did the full meal deal.
Keep fiddling, and if you get really screwed up, I'd be keen on trying to build the driver myself too, for the heck of it -- provided I don't actually need a Broadcom NIC to do so ;) Also, there's another thread on the go around here, where username mobinskariya is building a different Broadcom driver. You may find either some tips in that thread, OR a different version of the Broadcom driver that may work for you. Sasha |
I think you forgot to patch the driver. I have a blog entry about this... would you mind testing the instructions to see if they work for you?
|
Ok, so I did what you told me to do with the `uname -r` and got the same issue.
jimx86, I did not patch it. Maybe that's my issue. I will do that next. And yes, I will follow the directions in your blog entry and let you know what happened. |
Ok, so I patched the drivers, and now it allows me to create the LKM, however, when I try to load it with modprobe, I get this:
Code:
root@l3n0v0:~/hybrid_wl# modprobe wl EDIT: Edited out a theory that I answered myself. |
I'm not sure... are you using a custom kernel? Is the kernel source the same version as the running kernel?
|
Only time(s) I have gotten into that situation, was when using a driver that was too old for the kernel version I was trying to build it for (or the kernel is too new for it, or otherwise incompatible with the kernel). And trying to work around it is a hellish ordeal.
My suggestion is either upgrade to a newer kernel, or more preferably, downgrade/upgrade to a different version of the driver (maybe not a "hybrid", if possible -- that word's not usually good ;) ) |
I'm running Slackware64, but it works here with the stock 2.6.29.6 kernel and matching kernel headers. GrapefruiTgirl, you might be on to something... I'm pretty sure that this driver won't work yet with a 2.6.30 kernel.
edit... gentoo has a patch for newer kernels. |
Quote:
Methinks I'm missing something here :scratch: :) The time(s) I ran into this issue, were always when trying to build the Intel 536 modem driver on a new kernel. I always had to wait until a newer version of the modem driver came out, before I could update the kernel on that machine -- I was stuck at 2.6.24.4 for the LONGest time :| Sasha |
All times are GMT -5. The time now is 11:44 PM. |