fresh install Slackware 12 with BCM4318 problems
i have read a million posts on here and other places about how to set up the bcm4318 cards with ndiswrapper.... i have succeeded with that part... my card is up and it works, BUT after tooling around with wpa_supplicant for a week, i still cant get connected to anything... im not getting an IP, i dont know if its because my configs are screwed up or if its a dhcpcd problem (pretty sure its wpa though).
so i guess what im asking is this: does anyone care to tell me the steps to take from a fresh slackware 12 installation to get the bcm4318 card up and connected to a WEP network? (going without wep/wpa support is not a possibility since i need it at school and in other networks i am on often, including my home) all the info i can find so far is pieced together and assuming too many things, or it simply doesnt apply to me and my case... but a ground up install tutorial from a FRESH slackware 12 installation would benefit many i think... so, can anyone help out? |
Hi.
I have a Quote:
Quote:
Connected to a network using WPA-PSK-TKIP. The procedure I followed was: - I installed the firmware of the wireless card, I used the bcm43xx-fwcutter.tar.bz2 util and the wl_apsta-3.130.20.0.o file. I installed the firmware extracted to /lib/firmware - I configured the wpa_supplicant.conf, something like this. Quote:
I run wpa with Quote:
When it connects, I used Quote:
If you think that your problem is wpa, try using wpa_gui: Start the wpa_supplicant first, then use wpa_gui and look for the network you need. Put your password and hit connect. Luck. LinX |
The 4318 chipset has difficulties under the bcm43xx driver, so ndiswrapper may be a better choice. However, if you haven't blacklisted bcm43xx (it is part of some of the stock Slackware kernels) then you may be seeing conflicts between ndiswrapper and bcm43xx.
So first thing to do is blacklist bcm43xx by editing your /etc/modprobe.d/blacklist file. Then compile and install ndiswrapper. To be honest, the instructions on the ndiswrapper wiki are pretty foolproof, provided you have the kernel source package installed. You could also post your wpa_supplicant.conf file and maybe we can give some pointers. You are using the wpa_supplicant that comes with Slackware, right? |
Quote:
also, i cant get the wpa_gui to run... i added it into the make file as i was instructed to in another tutorial, but it wont run... i also havent set up my ethernet card yet, so i have NO networking on my laptop right now... (havnt gotten around to figuring that out yet, but the netconfig utility doesnt work for me with my ethernet card... so i need to look into that more too) ill get you some log output later tonight on anything i think may help... iwconfig, ifconfig, dmesg, and the like... |
Quote:
Hope that works for you. I also ask Hangdog42 to check it out and see what you think. Blessed be! Pappy |
I feel your pain.
Hi, looks like the guys above have given you some great advice. I'm only adding because I have a bcm4318 and got it working with wpa in Slack 12. It is possible! This is how I have been doing wireless with Slackware: I always get the ndiswrapper and wpa_supplicant source and build it (use removepkg to remove anything you already installed from .tgz). I don't know why I can't get the slack-packages that come with the install disk to work, but building these from source seems to be necessary for me. I have the bcmwl5.sys and bcmwl5a.inf files 'cause I have done this through the last few iterations of Slackware. I don't remember where I got them, but I do remember having to try several versions of these files obtained from various sources before finding the ones that worked -- and then I held on to them. (I can send these to you if you need them.) Anyway, I put the driver files in /usr/local/wifi/ for safe-keeping. Once you have these drivers installed with ndiswrapper, I edit /etc/rc.d/rc.inet1.conf. In the 'wlan0' section, I uncomment IFNAME, IPADDR, NETMASK, USE_DHCP,DHCP_HOSTNAME and add entries as appropriate. I don't know how much of that is necessary, but it doesn't seem to break anything. I think I have to add the following in the same section:
WLAN_WPA[4]="wpa_supplicant" WLAN_WPADRIVER[4]="wext" WLAN_WPACONF[4]="/etc/wpa_supplicant.conf" My wpa_supplicant.conf looks like this: ap_scan=2 network={ ssid="network-name" scan_ssid=1 proto=WPA2 key_mgmt=WPA-PSK pairwise=CCMP group=CCMP psk="your wpa passphrase goes here" } The types of encryption listed in the .conf file correspond to the settings on my router. And like the other guys said, I blacklist the bcm43xx module and add the ndiswrapper module so everything works on boot. I should mention that while this works great at home, where I use this machine 99% of the time, I have to edit config files by hand if I want to log into someone else's network. So I will be interested to see if there are tools (like the WPA gui thing) that make this easier. It just doesn't come up often enough to motivate me to seek another solution... Also I used to use ndiswrapper as the driver for wpa_supplicant, but that didn't work with the Slack 12 install so I used the wext driver. I probably did something differently this time. I hope this helps. I'm no expert, but I've gotten pretty good at installing Slackware on my hardware (due to lots of practice.) :-) Jay. |
All times are GMT -5. The time now is 01:18 AM. |