I have a Dell Latitude D600, as i see, when i boot SliTaz 4.0 RC2, it loads all the drivers that i need, included the wireless card, when i put iwconfig it says that the driver is loadedd. But here's my problem, when i try to search for a wireless interface, no one is detected! With another linux OS (Slax), it loads the driver module and i can connect to wireless, it detects the networks, but SliTaz doesn't! Do you know of any program that i should need?
Thanks
SliTaz Wireless Problem
(9 posts) (3 voices)- Started 12 years ago by TheBen96
- Latest reply from michaelbischof
- This topic is not resolved
-
TheBen96
offlineMemberPosted 12 years ago # -
TheBen96
offlineMemberHere's the output of what you asked me:
root@slitaz:/home/tux# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O Controller [8086:3340] (rev 03)
00:01.0 PCI bridge [0604]: Intel Corporation 82855PM Processor to AGP Controller [8086:3341] (rev 03)
00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01)
00:1d.1 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 01)
00:1d.2 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 01)
00:1d.7 USB controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 01)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 81)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge [8086:24cc] (rev 01)
00:1f.1 IDE interface [0101]: Intel Corporation 82801DBM (ICH4-M) IDE Controller [8086:24ca] (rev 01)
00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 01)
00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller [8086:24c6] (rev 01)
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] [1002:4c66] (rev 01)
02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5702X Gigabit Ethernet [14e4:16a6] (rev 02)
02:01.0 CardBus bridge [0607]: O2 Micro, Inc. OZ711EC1 SmartCardBus Controller [1217:7113] (rev 20)
02:01.1 CardBus bridge [0607]: O2 Micro, Inc. OZ711EC1 SmartCardBus Controller [1217:7113] (rev 20)
02:03.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11a/b/g [14e4:4324] (rev 02)
root@slitaz:/home/tux# tazhw detect-usbDetected USB devices Kernel modules
================================================================================
================================================================================root@slitaz:/home/tux# tazhw detect-pci
Detected PCI devices Kernel modules
================================================================================
> Module in use: intel_agp
> Module in use: snd_intel8x0
> Module in use: snd_intel8x0m
> Module in use: radeon
> Module in use: tg3
> Module in use: yenta_socket
> Module in use: yenta_socket
> Module in use: ssb
================================================================================root@slitaz:/home/tux# lsmod
Module Size Used by Not tainted
button 3602 0
video 9783 0
output 1144 1 video
parport_pc 16061 0
parport 20983 1 parport_pc
b43legacy 79383 0
mac80211 145388 1 b43legacy
cfg80211 99896 2 b43legacy,mac80211
rfkill 10682 1 cfg80211
ssb 24436 1 b43legacy
pcmcia 24993 0
yenta_socket 16223 0
pcmcia_rsrc 6989 1 yenta_socket
pcmcia_core 8413 3 pcmcia,yenta_socket,pcmcia_rsrc
tg3 97545 0
libphy 11777 1 tg3
radeon 673881 1
ttm 35361 1 radeon
drm_kms_helper 18798 1 radeon
drm 111992 3 radeon,ttm,drm_kms_helper
hwmon 993 1 radeon
i2c_algo_bit 3479 1 radeon
i2c_core 12192 4 radeon,drm_kms_helper,drm,i2c_algo_bit
snd_intel8x0m 8083 0
snd_intel8x0 19786 1
snd_ac97_codec 77963 2 snd_intel8x0m,snd_intel8x0
ac97_bus 718 1 snd_ac97_codec
snd_pcm 43737 3 snd_intel8x0m,snd_intel8x0,snd_ac97_codec
snd_timer 12515 1 snd_pcm
snd 33394 7 snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore 3357 1 snd
snd_page_alloc 4853 3 snd_intel8x0m,snd_intel8x0,snd_pcm
intel_agp 7908 1
intel_gtt 9214 1 intel_agp
agpgart 18221 4 ttm,drm,intel_agp,intel_gtt
root@slitaz:/home/tux# iwconfig
lo no wireless extensions.dummy0 no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Now, what should i do?Posted 12 years ago # -
mojo
offlineKey MasterThe b43legacy driver has to be loaded after the firmware is installed.
Open terminal,login as root
#modprobe -r b43legacy
Download firmware : http://dl.dropbox.com/u/5197027/slitaz/b43legacy-firmware-3.130.20.0.tazpkg
#tazpkg install b43legacy-firmware-3.130.20.0.tazpkg
#modprobe b43legacy
Set the wireless router to broadcast ESSID slitaz won't connect if it's hidden.
Applications/System Tools/Wifi configuration
Enter root password in subox click ok
Your router should show under essid Name after a few seconds.
Double click the essid of router,enter your WPA password in box,click OK button to connect.
To set default network interface,static ip,other network configurations :
#leafpad /etc/network.conf
If you have problems:
Open a second terminal
tail -f /var/log/messages
Load/unload driver in other terminal while monitoring the messages in this terminal
Post any errors related to driver,firmware loading,association/connection issues.Posted 12 years ago # -
michaelbischof
offlineMemberAs far as I see (but I am an absolute WLAN-beginner) you have to connect to the net
02:03.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11a/b/g [14e4:4324] (rev 02)02:03.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11a/b/g [14e4:4324] (rev 02) <= this you see from lspci-output
Most likely, but this I do not know, the necessary module for it is radeon (=> output of lsmod), so the module is loaded. But it does not connect - yet: output if iwconfigNow I would try in a root konsole:
#iwconfig wlan0
and then
#udhcpc -i wlan0
, takes some seconds. Then with ifconfig you should see whether it is connected or not, like here with my machine:
wlan0 Link encap:Ethernet HWaddr 00:A0:C5:56:C4:99
inet addr:192.168.2.22 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11435 errors:0 dropped:0 overruns:0 frame:0
TX packets:9512 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13446022 (12.8 MiB) TX bytes:1359785 (1.2 MiB)That's the way as far as I know it. Attention: go on to post your results here but in the next days I will not be the person to take care of that. I am busy with other things - but to let you know: starting from zero knowledge I learned here, on this forum, how to get WLAN on Slitaz within about 14 days (and with difficult, rare, old hardware!).
Posted 12 years ago # -
TheBen96
offlineMemberWell, in fact i'm using the 4.0 stable installed on a 3 GB HDD Partition, i did what you told me, loaded the firmware and the wireless card was detected (Thanks!) But something strange happened, when i go to Applications/System Tools/Wifi Manager, and i double click the ESSID that i need, it closes the box! So i went to the TazPanel and chaged from there the wifi things, put the WEP key and nothing happened!
What should i do now?Posted 12 years ago # -
mojo
offlineKey MasterIf this doesn't work:
The big Wifi network box with access points is replaced by a smaller Wifi connection box where you enter the password and click OK button to connect to the a.p. you dbl-clicked on.
Try this:
Open terminal,su,password: root
#leafpad /etc/network.conf
Read the comments,add your wifi info.
File/Save/Quit
Go back to root terminal
/etc/init.d/network.sh restart
The network connection indicator in the upper right corner should turn from red to white.
Test if google dns server replys to your ping:
ping 8.8.8.8
Your connected!If this doesn't work try michaelbischofs directions.
wifibox WEP crash: http://forum.slitaz.org/topic/wifi-problem-1#post-9308Posted 12 years ago # -
TheBen96
offlineMemberDid what you said, but it connected to lo, loopback, so no wireless. Tried what michaelbischofs said, and also nothing happens, i still don't know what am i doing wrong, well, a thing that may be causing the trouble, when i go to the wifibox, it shows at least 4 interfaces with the same name that the mine, the 4 are called "TURBONETT", and i choose the one with the bes quality link, tried adding to the network.con file the channel 6, because in another linux with a program calledd "Wireless Assistant", it showed all the wireless ESSID's, Channel and the AP (WEP key) mine is WEP key, so i don't need (i guess) the wpa_supplicant. What should i do now?
The driver is loaded.
The firmwarer is loaded.
The wifi card show interfaces!
WHAT?Posted 12 years ago # -
michaelbischof
offlineMemberIn this case ,,... and also nothing happens" is not detailed enough. Mojo's idea is great - open 2 root konsoles. In one konsole you type
#tail -f /var/log/messages
<= That shows the reaction of your machine
and in the other one you type first
#/etc/init.d/network.sh stop
Now you check with
#iwconfig
whether your Broadcom somethng is recognized. Look at the output in the ,,/var/log/messages"-konsole.
If so you type
#iwconfig wlan0
(or wlan1? I do not know...)
Look at the output again. If correct you type
#udhcpc -i wlan0
Then you should see something like this:
Internet Systems Consortium DHCP Client V3.0.7
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/Listening on LPF/wlan0/00:a0:c5:56:c4:99
Sending on LPF/wlan0/00:a0:c5:56:c4:99
Sending on Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.2.1
bound to 192.168.2.22 -- renewal in 376157 seconds.If not show the output here, please.
In the most important file /etc/network.conf there is a section for Wifi. In case of trouble show please your section of this file here. Once I had the following trouble, do not laugh please:
the WEP code was 145WC-55W55- and it did not work. I changed it to 145WC55W55 wihtout those brakes -and it worked! ;-)Forgive me, but now we have sunshine here and I run to collect wild garlic (Allium ursinum) so for many hours I won't be here.
Posted 12 years ago #
Reply
You must log in to post.
