On Wed, 18 Apr 2007 01:35:50 -0400 "Constantine 'Gus' Fantanas" <[EMAIL PROTECTED]> dijo:
> John Jason Jordan wrote: > > On Tue, 17 Apr 2007 22:14:49 -0400 > > "Chris Delahousse" <[EMAIL PROTECTED]> dijo: > > I don't need to use WEP, so I haven't paid much attention to this. But > > I know I have read somewhere that the bcm43xx driver can't do WEP or > > has a problem with it or something. And I dimly recall that the > > solution was to blacklist the bcm43xx driver and use ndiswrapper > > instead. I would bet that I read this on Ubuntu forums, since Ubuntu > > amd64 is all I have ever run on my R3240. Personally I could never get > > the bcm43xx driver to work at all with the Broadcom 4306, so I just use > > ndiswrapper. Somewhere I have a bookmark to an Ubuntu how-to on > > installing ndiswrapper with the 4306. I'll dig it out if you need it. > > > Hmmmmm, maybe the solution is moving to a 2.6.20 kernel? Last Monday I > tried WEP *AND* WPA with a Linksys router, using the BCM43xx (built as > module) and I am happy to say it worked PERFECTLY. (The router, by the > way, had been loaded the openWrt "White Russian" Linux distro for > embedded devices. It is relatively easy to replace the original > firmware with OpenWrt on --at least some-- Linksys wireless routers. > More details at http://openwrt.org/ .) I got WPA to work on the very > first try (judging from the output of 'iwevent', running in a separate > window). Last time I tried to get WPA to work was about a year ago and > under ndiswrapper running under a 2.6.16 kernel. I had no success (WEP > was working fine, but I wanted WPA!). > > I run SuSE 10.2 64-bit, but I have upgraded to a plain vanilla kernel > 2.6.20.6 and I have enabled full preemption. With the latest "SuSEfied" > 2.6.18.2 kernel I have only tried unencrypted wifi connections (again > with the BCM43xx built as module, not in the kernel). It worked OK, BUT > I got flaky numbers, something like -170dBm for signal strength and > 100/100 signal quality (!!!!!) on each and every network detected (via > the 'iwlist wlan0 scanning' command --the wifi shows as 'eth?', but I > hacked the relevant file in '/etc/udev/rules.d/' to make it appear as a > symbolic link to wlan0, so I did not have to change my firewall > scripts). I saw none of these problems with the 2.6.20 kernel. > > Do you have all the necessary options enabled in your kernel? > > On March 26, 2007, Mr. Jose Carlos responded to one of my earlier > postings about the initial success I had with the BCM43xx driver, > suggesting that I go for an Atheros cardbus wifi. This was a very > insightful suggestion (thank you, Mr. Carlos!), but what if I need to > use the cardbus slot while being connected to a wifi network? The > BCM43xx does have its merits despite its shortcomings. If the BIOS > allowed the replacement of the Broadcom wifi with a better solution, it > would be great, but it doesn't, so we are stuck with the Broadcom wifi, > unless we can spare the cardbus slot and/or, perhaps, a USB port. I'm afraid I can't answer any of your questions. When I got my R3240 almost two years ago I tried various 64-bit distros on it. None could get the video right -- they all dumped me in Vesa 1024 x 768. With each one I tried and tried to get the video working properly, but had no luck, in spite of hands-on assistance from several local Linux gurus. Eventually I tried Ubuntu Hoary amd64. It found the video and autoconfigured it for 1680 x 1050 and I was in heaven. And everything else worked as well, except for the Broadcom 4306. I was brand new to Linux and it took me a week to do it, but I finally got wireless working with ndiswrapper. I haven't left Ubuntu ever since. When Breezy came out it broke ndiswrapper and I had to set it up all over again. This time it took me only a day. And after I got it working I wrote it up and put it on our wiki so that next time I would have my own personal documentation. Sure enough, when Dapper came out the upgrade killed ndiswrapper again. But with Dapper we finally had the bcm43xx driver. I tried and tried to get it to work, but the instructions I found in the Ubuuntu forums just wouldn't work. Eventually I said "screw it" and reinstalled ndiswrapper. This time reinstalling ndiswrapper took me less than 15 minutes. And again when I upgraded to Edgy I had to reinstall ndiswrapper once more. The only thing I use the wireless on this notebook for is when I go to the university or elsewhere. My home environment is all wired for ethernet, which is faster and more secure. I have never had a wireless router and wouldn't know anything about configuring it with the bcm43xx driver. I suppose I am going to have to do this all over again in a few days, as Feisty is scheduled for release this Thursday. It will probably be a few days late, though, because the release of the beta was three days late. _______________________________________________ LinuxR3000 mailing list [email protected] http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000 Wiki at http://prinsig.se/weekee/
