I have downloaded a hybrid bcm43xx driver from Broadcom and I am trying to compile it, per the instructions they provided using the 'make' command. I have never done this before.

I have managed to work through a couple of issues, broken symbolic links, missing source code, etc, but keep running into more issues.

Below is the copy of the error messages I am now running into.

*********************************************************************
[root@localhost hybrid_wl]# make -C /lib/modules/2.6.18-128.7.1.el5/build M=`pwd`
make: Entering directory `/usr/src/kernels/2.6.18-128.7.1.el5-x86_64'
CC [M] /home/ferrell/Downloads/hybrid_wl/src/wl/sys/wl_linux.o
In file included from /home/ferrell/Downloads/hybrid_wl/src/wl/sys/wl_linux.c:33:
/home/ferrell/Downloads/hybrid_wl/src/include/typedefs.h:83: error: conflicting types for ‘bool’
include/linux/types.h:36: error: previous declaration of ‘bool’ was here
make[1]: *** [/home/ferrell/Downloads/hybrid_wl/src/wl/sys/wl_linux.o] Error 1
make: *** [_module_/home/ferrell/Downloads/hybrid_wl] Error 2
make: Leaving directory `/usr/src/kernels/2.6.18-128.7.1.el5-x86_64'

***********************************************************************
Could someone point me in the right direction so I can getting the wireless card working.

Much Thanks,
Ferrell

Hi!

You may want to follow us on this other page here: http://www.linuxquestions.org/questi...ivers.-754512/

I know it's a different OS, but we're having similar difficulties. You may learn something there, and/or eventually be able to help over there too

Sasha

Thanks, I'll check it out.

Ferrell

And, of course, if you're still stuck after reading that other thread, then by all means bring us up to speed on your situation, and we'll see what we can come up with

Sasha

I am not have much luck with the install of this broadCom hybrid driver install at all. I am now getting 'bool' errors when I run the "make" command. See below:
*********************************************************************
[root@localhost hybrid_wl]# make -C /lib/modules/`uname -r`/build M=`pwd`
make: Entering directory `/usr/src/kernels/2.6.18-128.7.1.el5-x86_64'
CC [M] /home/ferrell/Downloads/hybrid_wl/src/wl/sys/wl_linux.o
In file included from /home/ferrell/Downloads/hybrid_wl/src/wl/sys/wl_linux.c:33:
/home/ferrell/Downloads/hybrid_wl/src/include/typedefs.h:83: error: conflicting types for ‘bool’
include/linux/types.h:36: error: previous declaration of ‘bool’ was here
make[1]: *** [/home/ferrell/Downloads/hybrid_wl/src/wl/sys/wl_linux.o] Error 1
make: *** [_module_/home/ferrell/Downloads/hybrid_wl] Error 2
make: Leaving directory `/usr/src/kernels/2.6.18-128.7.1.el5-x86_64'
[root@localhost hybrid_wl]#
**********************************************************************

I did read the other post you suggested, but did not find anything helpful. I did try using 'uname -r' for the kernel but I got the same response.

I was able to create a debug.log and have listed the beginning entries for you to review. Maybe you can point me in the right direction after you or someone else looks at it.

***********************************************************************
This program built for x86_64-redhat-linux-gnu
Reading makefiles...
Reading makefile `Makefile'...
Reading makefile `/usr/src/kernels/2.6.18-128.7.1.el5-x86_64/scripts/Kbuild.include' (
search path) (no ~ expansion)...
Reading makefile `include/config/auto.conf' (search path) (don't care) (no ~ expansion
)...
Reading makefile `/usr/src/kernels/2.6.18-128.7.1.el5-x86_64/arch/x86_64/Makefile' (se
arch path) (no ~ expansion)...
Updating makefiles....
Considering target file `/usr/src/kernels/2.6.18-128.7.1.el5-x86_64/arch/x86_64/Makef
ile'.
Looking for an implicit rule for `/usr/src/kernels/2.6.18-128.7.1.el5-x86_64/arch/x8
6_64/Makefile'.
Trying pattern rule with stem `Makefile'.
Trying implicit prerequisite `/usr/src/kernels/2.6.18-128.7.1.el5-x86_64/arch/x86_64
/Makefile.o'.
Trying pattern rule with stem `Makefile'.
Trying implicit prerequisite `/usr/src/kernels/2.6.18-128.7.1.el5-x86_64/arch/x86_64
/Makefile.c'.
************************************************************************
Please help if you can. the frustration is building I need this wireless up and running.

Much thanks,

Ferrell

At this stage, I am going to venture a guess (and that's ALL it is, as I have no proof) that your kernel might be too old for the hybrid driver. Any chance there is documentation either included with the driver, or on the website where you got it, that tells you what kernel(s) or range of kernels this driver will work with?

Also, if you ultimately decide that this driver will not work for you, there are other Broadcom drivers, and other means of using these drivers, one of which might help.

Hopefully someone else can shed more light on your situation -- sorry I can't be of more specific help.

Do let us know what if anything you find in the documentation about the kernel versions that this driver supports.

Sasha

Hey GrapefruiTgirl,

There was a lot more to the debug log. I was having problems attaching it the the forum. The rest of the log was pretty much the same response, but for different files. The Kernel I am using is 2.6.18-128.7.1.el5 which I believe may be a bit old. CentOS is about stability, not cutting-edge. So you are right.

Since BroadCom came out with this driver in May of this year, and my kernel's original release date was Sept 20, 2006, it begs to reason that age may have something to do with it.

It looks like I may need to pursue another means of getting this or another wireless to work with my Dell D630.

Do you have any suggestions on what brands of wireless pcmcia cards are known to work well with most types of Linux versions?

Much Thanks / Ferrell

Personally, I don't know much about PCMCIA cards, period but the package of the working varieties is less important than the chipsets inside them.

To my knowledge, based just on what I read around this forum and when doing Google searches on wireless devices, it seems that Broadcam, RaLink, and Atheros make the most Linux-compatible wireless devices.

However, don't take my word on that -- check the HCL here: http://www.linuxquestions.org/hcl/ and see if there's anything helpful, and do some Googling while awaiting maybe someone to come in with a really good 'known to work' device.

Best regards,
Sasha

PS - this page is rather dated, but probably still relevant, especially as PCMCIA is a bit older now, and also because these older devices are probably (possibly??) cheaper to obtain than a newer device: http://pcmcia-cs.sourceforge.net/ftp/SUPPORTED.CARDS

And here: http://www.goonda.org/archive/wireless/

If I come up with anything more, I'll post it here

You can use ndiswrapper with the windows driver. That is what I have done with my dell (a little older than yours) bcm4306. I fought fwcutter on mine for about a week and then went to ndiswrapper and it is hard also. In the newer distros you have to blacklist all of the native broadcom drivers.