Need help with setting up wireless on HP notebook using Slackware
Hi,
I'm running Slackware 12.2 on HP dv6t notebook. I have configured my wired network to DHCP which was pretty straight forward. Now I'm trying to setup my wireless and not sure and not sure if I'm doing this right. My understanding after reading some information here on LQ and Slackbook, is that modifying just rc.inet1.conf should suffice (rc.wireless.conf is deprecated). So I modified it and ran rc.inet1. Code:
# /etc/rc.d/rc.inet1 wlan0_start rc.inet1.conf Code:
# Config information for eth0: Code:
02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01) Code:
Module Size Used by Thanks in advance, Ash. |
Hello Ash,
Have a look at the Slackbuilds.org site, they have what you need to get up and running: http://slackbuilds.org/result/?search=BCM43&sv=12.2 That particular NIC causes headaches in more than one distro :rolleyes: Kind regards, Eric |
Thanks for the information. I appreciate it. It appears that my wireless card is not supported (or rather in progress) at this time.
Regards, Ash. |
You could look into a ndiswrapper driver.
|
Actually, there is a broadcom driver for it, it's just that I've heard not so good things about it:
http://linuxwireless.org/en/users/Drivers/b43 http://wiki.archlinux.org/index.php/Broadcom_BCM4312 |
I got the 802.11 Linux STA driver from Broadcom, built it and did the following.
Code:
# cp /tmp/wl/wl.ko /lib/modules/2.6.27.7-smp/kernel/net/wireless If you look at my first post with the rc.inet1.conf, I tried to define wlan0 for my wireless. How did it pick up eth1? What do I have to do next to connect to the wireless? Thanks, Ash. |
Try
iwconfig wlan0 ash iwconfig wlan0 key KEY_HERE dhcpcd wlan0 |
Hi,
My Dell is now using Slackware 13 X86_64, 2.6.30.5 and experimenting with 2.6.32-rc7. I've spent a lot of time trying the Broadcom propriety drivers. Sometimes the recognition is eth1 for the wireless device. Tried the B43 SlackBuilds too no avail on the Dell Inspiron Laptop with this chipset. It seems to be cursed. I built the firmware for the 2.6.29.6 kernel using the BroadCom driver & patch. It worked but I did need to move to a newer kernel for other reasons, video and I/O. Of course the thing broke and I couldn't get the wireless to work with newer kernels. Frustrated! I then grabbed the firmware to see if that would work for me. It did for a while but then became unstable. I was about to turn to 'ndiswrapper' but would do anything to not do this since it has caused other problems in the past. I found a Ubuntu firmware for the b43/b43legacy drivers and thought 'what the hell', tried it and it's still working. Why the Slackbuilds or the other drivers wouldn't function is on a 'to-do' list but real low priority for now. Give it a try. I'm going to be re-working the Laptops configurations after the new year. It's working for now but the hdd needs are demanding a upgrade to a '72k' at least. Or a newer SSD? So I'm sure that things will be in the works again. :hattip: |
Guess I'm confused. Please bear with me if my questions sound silly.
I built the Broadcom drivers and loaded it. iwconfig and iwlist seems to indicate that the wireless card is functional. It's even showing the correct ESSID etc. Is it just picking up this information from one of my conf files? If it's still not connecting, does it mean that the device is actually not working even though iwconfig shows some legitimate looking output? Based on Onebuck's suggestion, I wanted to try the b43/b43legacy drivers. Where do I get the b43 drivers? Now that I have loaded the Broadcom driver, could someone tell me how to unload that and load the b43 drivers instead? Thanks, Ash. |
Hi,
'Configuring your network in Slackware'. :hattip: The above links and others can be found at 'Slackware-Links'. More than just SlackwareŽ links! |
The wireless is just not associating with access point.
iwlist eth1 scan finds the access point correctly. So I tried to to set the essid explicitly with iwconfig eth1 essid "ash". But a subsequent iwconfig still shows the essid as empty. Any suggestions. Thanks, Ash. |
Ash,
Out of curiosity, are you using any encryption on your wireless network? WEP isn't so hard to connect to, but WPA can be a real beast in linux. Also, have you tried taking down/back up your wireless network device. It's been a while, but I think: # ifconfig wlan0 down # ifconfig wlan0 up Will do it. I had a similar problem a long time ago and I just had to do the above to get the last bit working. -Emrys |
I just tried bringing the wireless down and up but it didn't make a difference.
Yes, my wireless is encrypted. When I see the properties in windows, it shows that it's WEP. Is there any other way to tell? Also is there a way to turn off the encryption so that I can at least see if it associates? Thanks, Ash. |
Hi,
Quote:
'Slackware 13.0 RC2 X86_64 Broadcom bcm4312 problems' & '[SOLVED] Configure wireless driver for Dell Wireless 1397(bcm 4312)' are threads that may help. :hattip: |
Turning off the WEP encryption on your wireless network should be easy. Have you ever logged in to your router? In windows, you can go to a command prompt (windows key + r, then CMD, enter) and put in: > ipconfig /all
This should bring up your computer's ip address and gateway. The 'default gateway' will be your router's address. Put that into your router as 'http://192.168.x.x' and you should be able to administer your router from that. This will work with about 90% of routers out there. Anyways, once you're in the router's software, you just need to disable the WEP. Also, while you're in there, you can see if it recognizes your wireless card as having connected before. This is a little more complex and I don't have time to go into it right now, but just suffice it to say that ifconfig can give you the MAC address of your wireless card in linux, and the router _should_ record those somewhere. It would be good to know if it had _ever_ connected, or at least been recognized by the router as existing. -Rigor |
All times are GMT -5. The time now is 02:15 PM. |