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.
When I shutdown my laptop the wireless goes down (it is normal) but when I reopen my laptop and enter Linux it does not activate the wireless card again.(I have windows xp on it and it self activates)
Therefore I need help.If possible simple steps is easier to understand because I'm a newbie.
thank you in advance!!
Last edited by rssn6; 10-09-2008 at 07:00 PM.
Reason: add some more information
You can put your settings in /etc/rc.d/rc.inet1.conf. You'll probably need to uncomment some lines (i.e. remove the # at the start of the lines) and will need to edit the file as root.
Read Configuring your network in Slackware by Alien Bob.
He's the one who maintains those files for Slackware. If
you still have problems afterwards, post back what you did
and what the new problem might be.
If you are not comfortable doing your configuration from
the command line in a terminal, you might want to install
wicd, a package with a GUI interface for configuring your
network. Really, CLI is easy if you follow the directions,
and we'll help if you stumble.
Sorry that mod closed your thread in Slackware rather than
closing this one. Use the Report button on your first post
and report it and ask a mod to move this to Slackware.
Thank you for reply I will do some modification in /etc/rc.d/rc.inet1.conf and I will read Read "Configuring your network in Slackware" concerning wicd I installed but it does not open it self i see just the bouncing icon and then it just does not show me anything.
I will get back
(yes i commented all other array[x] that would intefear with my wlan0[1])
and nothing !!
I found out that there is a problem with b43 frimware
Code:
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4).
input: b43-phy0 as /devices/virtual/input/input14
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is off for TX and off for RX.
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4).
input: b43-phy0 as /devices/virtual/input/input15
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4).
input: b43-phy0 as /devices/virtual/input/input16
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4).
input: b43-phy0 as /devices/virtual/input/input17
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4).
could it be the problem ? If so how do you repair?
ok, I fixed the error b43-phy0 ERROR, it was just the driver that was not there when to http://linuxwireless.org/ and installed.
Now I'm stuck on this:
Code:
b43-phy0: Broadcom 4311 WLAN found
input: b43-phy0 as /devices/virtual/input/input13
Registered led device: b43-phy0:tx
Registered led device: b43-phy0:rx
Registered led device: b43-phy0:radio
b43-phy0: Radio hardware status changed to DISABLED
input: b43-phy0 as /devices/virtual/input/input14
Registered led device: b43-phy0:tx
Registered led device: b43-phy0:rx
Registered led device: b43-phy0:radio
b43-phy0: Radio hardware status changed to DISABLED
input: b43-phy0 as /devices/virtual/input/input15
Registered led device: b43-phy0:tx
Registered led device: b43-phy0:rx
Registered led device: b43-phy0:radio
b43-phy0: Radio hardware status changed to DISABLED
but my wifi Led is on !!!
and
how do I configure Fn+F2 fore activate/deactivate Wifi
help!
Error for wireless request "Set Nickname" (8B1C) :
SET failed on device wlan0 ; Operation not supported.
Polling for DHCP server on interface wlan0:
dhcpcd: MAC address = 00:16:cf:8c:9f:27
and other time my wireless is on and when I try to restart it with /etc/rc.d/rc.inet1 wlan0.restart it goes down and then gives me the same msg.
my inet1
Code:
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""
IFNAME[4]="wlan0"
IPADDR[4]=""
NETMASK[4]=""
USE_DHCP[4]="yes"
DHCP_HOSTNAME[4]=""
WLAN_ESSID[4]="5656"
WLAN_MODE[4]=Managed
WLAN_RATE[4]="54M auto"
WLAN_CHANNEL[4]="4"
#WLAN_KEY[4]=1037857793
# Config information for eth1:
#IPADDR[1]=""
#NETMASK[1]=""
#USE_DHCP[1]=""
#DHCP_HOSTNAME[1]=""
# Config information for eth2:
#IPADDR[2]=""
#NETMASK[2]=""
#USE_DHCP[2]=""
#DHCP_HOSTNAME[2]=""
# Config information for eth3:
#IPADDR[3]=""
#NETMASK[3]=""
#USE_DHCP[3]=""
#DHCP_HOSTNAME[3]=""
# Default gateway IP address:
GATEWAY="192.168.1.1"
# 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"
my dmesg:
Code:
input: b43-phy0 as /devices/virtual/input/input29
Registered led device: b43-phy0:tx
Registered led device: b43-phy0:rx
Registered led device: b43-phy0:radio
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:03:2f:07:fe:1f
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:03:2f:07:fe:1f
wlan0: RX authentication from 00:03:2f:07:fe:1f (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:03:2f:07:fe:1f
wlan0: RX AssocResp from 00:03:2f:07:fe:1f (capab=0x41 status=0 aid=3)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
input: b43-phy0 as /devices/virtual/input/input30
Registered led device: b43-phy0:tx
Registered led device: b43-phy0:rx
Registered led device: b43-phy0:radio
ADDRCONF(NETDEV_UP): wlan0: link is not ready
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.