2007/8/8, Peter Davoust <[EMAIL PROTECTED]>: > > I'm going to try really hard to reply to all three of these > conflicting messages. First, I didn't get Beso's last e-mail, but I > think another reason many linux newbs are repelled are abrupt > responses on forums and messages like 'you're wrong'. Not to poke a > stick in anyone's cage, but ouch. However, that's not what we're > talking about. the 4310 isn't even on Broadcom's website, I have no > clue how to get it working. Beso, does WPA work with your 4310?
yep, i currently work with wpa_supplicant and network manager. I also have a friend that is in the bcm43xx developer list, so i'm quite a bit informed on the matter. The main issue that you may have is that the bcm driver has problems with the power management which currently causes you to disconnect randomly. another problem with this driver is connecting to wireless ap which don't distribute the network name. in these cases you may experience some delay connecting and some connection issues. but for what i know the ndiswrapper version is worse, at least on a amd64 compiled system. if i don't recall badly, the 4310 has entered full support from may of this year. the list on the broadcom site is quite old as it is not greatly mantained. you should also look for changes in the kernel source. an example of this functioning is: http://gentoo-wiki.com/HARDWARE_Gentoo_on_HP_Compaq_nx6325#Onboard_Wireless_.28802.11.29 the main problem with broadcom chips is that they're bugged, there aren't specs around, and that you'll always have to upgrade to the latest wpa_supplicant/wireless tools/kernel to have patched and working drivers. I > didn't buy the card specifically, and if I had a choice I would have > gotten something that was better supported and didn't die on me every > 3 minutes. I even tried an airport pc card, but I have an express pc > card slot/whatever, so it didn't work. I would really appreciate if > someone could send me said excruciating steps so I could give it a > try. I hope I didn't offend anyone, but I know that, being only a > lowly highschool student and not a system administrator, I would > really appreciate if people would take a little more time to answer > the stupid questions. now, the steps for a broadcom to work under linux is: 1. download the latest kernel 2. unzip kernel in /usr/src 3. go the kernel dir 4. make menuconfig and chose: iee802.11 stack and softmac stack from "networking -> wireless"; and bcm43xx from "device drivers -> network device support -> wireless lan" 5. compile kernel: "make && make modules_install && make install" 6. download wl_apsta.o firmware from this link: http://svit.epfl.ch/stuff/wl_apsta.o or use your distro firmware if it's given to you (for example gentoo gives it from sabayon overlay, kubuntu gives it too) 7. if you downloaded the file from internet you have to cut it with bcm43xx_fwcutter (which normally is in the distro installation repo) and then copy the .fw files to /lib/firmware and the do a chmor +r+x /lib/firmware/*.fw 8. reboot with the new kernel and the chip will get up quite smoothly. On 8/7/07, Dustin J. Mitchell <[EMAIL PROTECTED]> wrote: > > On Tue, Aug 07, 2007 at 09:35:58PM +0000, Duncan wrote: > > > OK, this is a bit of a rant, but anyway... > > > > Always good fun :) > > > > > I'm a pretty die-hard Linux supporter, I doubt anyone would argue > that, > > > but the above is /certainly/ one reason Linux doesn't have a greater > > > share than it does. > > > > I agree, but I would offer: > > - Gentoo is, among the many great things it is, not for those who don't > > get a visceral thrill from following long series of scary steps. > > Especially if you're looking to eek out good performance by using > > "better" drivers. > > - Things have gotten a lot better, and continue to do so. > > > > Dustin > > -- > > [EMAIL PROTECTED] mailing list > > > > > -- > [EMAIL PROTECTED] mailing list > > -- dott. ing. beso
