[SOLVED] broadcom-sta won't build with 2.6.33.1 kernel

mdynac · 04-12-2010, 09:59 PM

hi

running current on a Lenovo S10

the b43 driver craps out every few minutes.

so i decided to try the sta driver.

i downloaded the slackbuild but it crashes with the following
see attached

any help would be appreciated,
michael

rfernandez · 04-12-2010, 11:06 PM

Under the main directory of the hybrid untarred file (where the Makefile is), you'll have to go to the folder

Code:

src/include

And edit the file "linuxver.h" as fallows:

Code:

#include <linux/version.h>
#if (LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 0))
#include <linux/config.h>
#else
-#include <linux/autoconf.h>
+#include <generated/autoconf.h>
#endif
#include <linux/module.h>

And you should be ok.

mdynac · 04-13-2010, 09:11 AM

well i added that line and it made no difference

genhappyok · 04-13-2010, 01:49 PM

i also have had no luck with the sta driver. I have a dell laptop. I used ndiswrapper instead. just download the windows xp driver and installed using ndiswrapper (compile it from source). Use version 1.56, 1.55 requires a patch after 2.6.32. One bug i have found after 2.6.32 is it compiles the module into /lib/modules instead of /lib/modules/<kernel version>. what i do is copy the /lib/modules/misc folder it creates into the kernel modules i compiled it under and rerun depmod -a, then reboot. Hope this helps, if you dont like this option, and want the sta driver, let me know if you get it to work......good luck

slackwaredanny · 04-13-2010, 04:45 PM

have a lenovo s10e too and its seems that current and broadcom-sta needs a patch or fix,i run 13 and its working like a charm so you could always install stable,or another kernel.
But i too would wish for a broadcom-sta for current and touchpad support!.

mdynac · 04-13-2010, 05:50 PM

well i changed over from the huge kernel to the generic kernel and the b43 driver is working good for over an hour....
now i have slackware with wireless on my S10!!!!

life is good

mdynac · 04-13-2010, 06:04 PM

well i spoke too soon, it just quit.
back to wired for now.

this is the syslog message when b43 crashes:

Apr 13 16:34:50 vectra last message repeated 8 times
Apr 13 17:31:57 vectra kernel: hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Apr 13 17:33:47 vectra dhcpcd: dhcpcd not running
Apr 13 17:33:59 vectra last message repeated 3 times
Apr 13 17:54:47 vectra kernel: b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
Apr 13 17:54:47 vectra kernel: b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
Apr 13 17:54:47 vectra kernel: b43-phy0 ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration.
Apr 13 17:54:52 vectra kernel: b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
Apr 13 17:54:52 vectra kernel: b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
Apr 13 17:54:52 vectra kernel: b43-phy0 ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration.
Apr 13 17:54:52 vectra dhcpcd: dhcpcd not running
Apr 13 17:54:57 vectra kernel: b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
Apr 13 17:54:57 vectra kernel: b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
Apr 13 17:54:57 vectra kernel: b43-phy0 ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration.
Apr 13 17:55:18 vectra kernel: b43-phy0 ERROR: MAC suspend failed
Apr 13 17:55:18 vectra last message repeated 3 times

guess i'll try the ndiswrapper setup

thx
mdynac

woolz · 04-13-2010, 06:26 PM

edit line 23 of src/include/linuxver.h

original:
#include <linux/autoconf.h>

change to read:
#include <generated/autoconf.h>

I had the same problem when 2.6.33 came out.
I found the answer somewhere on the net , just cant remember where.

mdynac · 04-13-2010, 07:37 PM

okay woolz

that fixed it.

she built and installed fine, now to get it running.

klein.rfk · 05-10-2010, 07:20 AM

Someone can tell me why this is needed, I mean, that sed line?

And, I never had b43 working for this wireless card... is that a good option? is it working fin?

Klein

klein.rfk · 05-10-2010, 07:21 AM

ooops, sed line == sed -i -e '23s/linux/generated/' $WORKDIR/src/include/linuxver.h

rfernandez · 05-10-2010, 07:25 AM

That sed line will replace linux/autoconf.h by generated/autoconf.h (which is the needed action to build it on kernel 2.6.33 series).

'Till a week back, I could only use the broadcom-sta driver, I never made the b43 kernel driver to work properly. But, when I tried it with kernel 2.6.33.3, everything worked fine, and if you ask me, I prefer it that way, though I can't get statistics on Noise Level.

P.S.: From my tests, it also works with kernel 2.6.33.2. I have a BCM4312.

klein.rfk · 05-11-2010, 08:36 AM

ohh... I mean.. why we need to replace that thing...(with the sed line).

and, ok... b43 will not work for me since I have bcm4322

rfernandez · 05-11-2010, 01:27 PM

Because as from kernel 2.6.33 series, autoconf.h has been moved from linux/ to generated/, so in order to the driver be compiled correctly, it has to know where autoconf.h (and other headers) are, so we just edit that line so it could find the requested header. It's easier to edit that line than move the header because any other programs related to kernel headers already look for them in the right place, thus moving the header to compile the broadcom-sta driver (or any other driver) is not recommended. You should never move kernel headers from their places, always edit the files, if it is possible.

Isn't there a future release to support your card? I hope so.

klein.rfk · 05-11-2010, 11:24 PM

rfernandez,

thanks for the reply...
and I hope b43 support that card in future too...

thanks a lot