SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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:
Code:
# lspci -vv
# ifconfig -a
# lsmod
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.
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.
# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").
# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.
# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.
# =============================================================================
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""
# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]="yes"
DHCP_HOSTNAME[1]=""
# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]="yes"
DHCP_HOSTNAME[2]=""
# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]="yes"
DHCP_HOSTNAME[3]=""
# Default gateway IP address:
GATEWAY=""
# Change this to "yes" for debugging output to stdout. Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="no"
## Example config information for wlan0. Uncomment the lines you need and fill
## in your info. (You may not need all of these for your wireless network)
IFNAME[4]="wlan0"
#IPADDR[4]=""
#NETMASK[4]="255.255.255.0"
USE_DHCP[4]="yes"
#DHCP_HOSTNAME[4]="next.door"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
#WLAN_ESSID[4]=house
#WLAN_MODE[4]=Managed
##WLAN_RATE[4]="54M auto"
##WLAN_CHANNEL[4]="auto"
##WLAN_KEY[4]="D5AD1F04ACF048EC2D0B1C80C7"
##WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
#WLAN_WPA[4]="wpa_supplicant"
#WLAN_WPADRIVER[4]="ndiswrapper"
## Some examples of additional network parameters that you can use.
## Config information for wlan0:
#IFNAME[4]="wlan0" # Use a different interface name nstead of
# the default 'eth4'
#HWADDR[4]="00:01:23:45:67:89" # Overrule the card's hardware MAC address
#MTU[4]="" # The default MTU is 1500, but you might need
# 1360 when you use NAT'ed IPSec traffic.
#DHCP_KEEPRESOLV[4]="yes" # If you dont want /etc/resolv.conf overwritten
#DHCP_KEEPNTP[4]="yes" # If you don't want ntp.conf overwritten
#DHCP_KEEPGW[4]="yes" # If you don't want the DHCP server to change
# your default gateway
#DHCP_IPADDR[4]="" # Request a specific IP address from the DHCP
# server
#WLAN_ESSID[4]=DARKSTAR # Here, you can override _any_ parameter
# defined in rc.wireless.conf, by prepending
# 'WLAN_' to the parameter's name. Useful for
# those with multiple wireless interfaces.
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=thekey"
# Some drivers require a private ioctl to be
# set through the iwpriv command. If more than
# one is required, you can place them in the
# IWPRIV parameter (separated with the pipe (|)
# character, see the example).
RESOLV.CONF
Code:
search laptop
Last edited by gaza222; 06-16-2008 at 12:13 PM.
Reason: my mistake
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.
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??
I would setup a static IP first, do as root from cli;
Code:
~#ifconfig -a #get recognized devices
~#ifconfig wlan0 192.168.0.10 #set to a available IP
~#route add default gw 192.168.0.1 #set to your gateway
~#route -n #show the route table
~#ifconfig wlan0 up #should be up already
~#ping 192.168.0.1 #ping your gateway
~#ping 208.69.32.130 #google.com IP
~#ping google.com #test DNS, if fail then
#check /etc/resolv.conf
You should have your '/etc/resolv.conf' setup with your 'ISP DNS' nameservers.
You could use a third level DNS from verizon;
Code:
4.2.2.1
4.2.2.2
4.2.2.3
4.2.2.4
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.