Thanks Larry, > [EMAIL PROTECTED] wrote: >> Hi, >> >> I've been trying this for several days now with no success. >> >> I'm building the softmac layers with the daily snapshot each time and >> also >> the BCM43xx driver from the daily snapshot. >> >> I get warnings when compiling but no errors. >> >> I've got eth1 aliased to bcm43xx in my modprobe.conf >> >> The modules ieee80211_crypt ieee80211 and ieee80211softmace and bcm43xx >> all load with no errors (see my earlier posts) >> >> NOTE: I don' get the firmware_class module bt I'm using Fedora 4 and I >> believe that FC4 doesn't use firmware_class. >> >> I can ifconfig eth1 up with no errors but I get nothing further from >> dmesg. >> >> Looking at other peoples posts, they all get Softmac lines in their >> dmesg. >> I don't get any of these. >> >> There is a process which starts bcm43xx_wx/0 >> >> Whenever I unload the modules, they are automatically loaded again. Can >> I >> stop this action? > > Unplug the card. Unfortunately the card is integral to the laptop. It does have a switch on the front (integrated with the Link LED) so I'll try that. > >> How can I check that my firmware is loading? > > At or near line 2267 of bcm43xx_main.c is where the firmware is loaded. If > loading failed, you would > get a message in your logs from the printk statement contained there. Have > you checked > /var/log/messages for any bcm43xx messages?
Cool, I don't get any error messages loading the driver so I presume the firmware is getting loaded. (extracted with latest revision of fwcutter to answer your later question). > > >> I don't get the LED on the front lighting up which indicates the >> wireless >> is on. >> >> BTW this works fine under 2.6.14 with Ndiswrapper, but of course >> Ndiswrapper is broken under 2.6.15. > > I don't understand this statement. On my system, 2.6.15 works with > ndiswrapper. I don't use it > anymore but keep one kernel so that I can use it if necessary. > I cant' get Ndiswrapper to work under this kernel (it's a custom 2.6.15 kernel with the DSDT patches 'cos the DSDT is broken on this laptop). I'm wondering after reading a few more posts if this is to do with the stack size. Will need to check this. Would this make a difference to the bcm43xx driver? >> Any ideas, a list of basic things to check please. >> Other people seem to have got this working fine so I don't know where >> I'm >> going wrong :-( > > Did you use fwcutter on the driver version that you used to use with > ndiswrapper? Yup. Only came up with the usual messages about microcode.dll and latest revision but fwcutter -i "file" says the driver revision is supported. > My main worry is that I'm not getting any of the softmac messages after the bcm43xx module looks like it's loaded fine. I realise that there are problems with the module and this chipset at the moment but most seem to be gettig further with this than me. I'm at work at the moment so I can't post any debug but i'm not getting anything new with the latest builds than I got in my earlier posts. Thanks Simon. > Larry > > _______________________________________________ Bcm43xx-dev mailing list [email protected] http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
