Broadcom 4318 & Slack 12.1
 

Hi guys i have been working on this for ages i have used linux before but want to get my hands dirty so slackware was the choice. I have been trying on and off for a month now when i have free time to get wireless working.
I have a dell insipiron 1300 with brodcom 4318 wireless. There are a fe things. firstly the drivers i have tried do not work. After investigating the hardware in lib/modules/2.6.24.5-smp indicate that the pci address is using ssb as drivers this card has worked before under BT2 & 3 and obviously distros such as ubuntu. I have tried using the FW from these distros and reconfiguring.Also have tried a recompile and using bcm43xx drivers i think this may have worked too late to tell now reformatted since. Can anyone confirm that the hardware is being mis-identified in slcak 12.1 and that the correct modules are not being loaded. I can then at least focus my time on getting it to work, this could also be the issue wuth some no-hope wireless cards not sure if it has been explored yet there is only so many backposts i can go through thanks in advance for any replies.

Post the output of the following commands as root:
Please wrap the output in [_CODE] and [_/CODE] tags (without the _) to make it easier to read. You should probably also post your /etc/rc.d/rc.inet1.conf and /etc/resolv.conf files.

If you search the forums, you'll discover that Broadcom cards are not the nicest to work with. There are some drivers in the kernel that may work -- but they may not. There is also ndiswrapper if you can't get the native Broadcom drivers (the b43 module) working. I have heard that the 2.6.25.x kernel is a little better than the 2.6.24.x kernel shipped with Slackware, so you may have better luck recompiling. However, it is entirely possible that you can get your card working without resorting to such tactics. Please post the output of the above commands to make it easy to see what's going on. If the b43 module is not automatically loaded (ie it's not in your lsmod output), try loading it manually with `modprobe b43` and then see if `ifconfig -a` outputs a correct interface for your wireless card.

Hi,

I would like to add that you should run the 'netconfig' if you haven't already configured the system.

I would like you too post the output of 'dmesg |grep -i eth' and 'dmesg |grep -i wireless' along with T3s' requests.

The 2.6.24.5-smp kernel uses the; '/lib/modules/2.6.24.5-smp/kernel/drivers/net/wireless/b43/b43.ko' module for broadcom wireless. You did try it?

I would probably use the '/etc/rc.d/rc.inet1.conf' to work with your wireless configuration. Remember to edit and work with the configuration as 'root'. You can restart the inet with '/etc/rc.d/rc.inet1 restart'.

Ok guys thank you for the prompt reply. In order to keep this post useful I will put the additional outputs in a separate post. Here are the outputs you requested. Thanks again for your time.

LSPCI
IFCONFIG
LSMOD
RC.INET1.CONF
RESOLV.CONF

Ok i have used netconfig tool to try and setup, with the drivers i was using i could scan but i could not connect. A little while back now obviously as i found today i've changed something as i cant even get the wlan0 if up. Here are the outputs you asked for buck thanks for your time.

ETH
WIRELESS - got no response.

WLAN - tried and got a reply

appologies i had blaclisted b43 drivers forgot to take them off of the list for this exercise i will repost the logs again if needs be unless you can figure much out from those already posted??

Correct output is now up.

Hi,

I would setup a static IP first, do as root from cli;

You should have your '/etc/resolv.conf' setup with your 'ISP DNS' nameservers.

You could use a third level DNS from verizon;
If the static works then you can apply this to your '/etc/rc.rc.inet1.conf'. Your current setup doesn't have a defined 'Gateway ='.

this did work for me until i rebooted looking at logs the boot up was different when it worked from when it didnt i blacklisted b43 and ssb like i tried before and it seems to work now before though i think i changed a file which mapped the drivers to the pci address (i assume thats what it did) i cant remember what that file was though. but i didnt have to blacklist anything then.