You are not logged in.

#1 2011-09-15 08:39:49

gnarliprime
Member
Registered: 2011-09-01
Posts: 11

wlan can scan but cannot connect

I'm setting up arch, have everything working except wlan. I have installed the b43 drivers, the wireless card can see the surrounding networks but cannot connect, whether with or without encryption With wpa2 personal it keeps asking for the password although it is the correct passphrase(this is for the network and not the su pass), without encryption it stays at 'trying to connect.'
dmesg says the connection has timed out

[m1k3y@m1k3y ~]$ dmesg | grep wlan0
[ 2863.705657] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 6622.329414] wlan0: direct probe to 00:18:f8:dc:40:0f (try 1/3)
[ 6622.529367] wlan0: direct probe to 00:18:f8:dc:40:0f (try 2/3)
[ 6622.729368] wlan0: direct probe to 00:18:f8:dc:40:0f (try 3/3)
[ 6622.929364] wlan0: direct probe to 00:18:f8:dc:40:0f timed out


[m1k3y@m1k3y ~]$ lspci -vnn | grep 14e4
01:07.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)
    Subsystem: Broadcom Corporation Device [14e4:0418]

Any ideas on how to get wireless working?

EDIT: Using gnome3 networkmanager
EDIT2: Removing excess probe timeout spam

Last edited by gnarliprime (2011-09-15 09:19:40)

Offline

#2 2011-09-15 11:53:29

bernarcher
Forum Fellow
From: Germany
Registered: 2009-02-17
Posts: 2,281

Re: wlan can scan but cannot connect

Moving to Networking.


To know or not to know ...
... the questions remain forever.

Offline

#3 2011-09-15 17:17:51

ehabreda
Member
From: Qatar
Registered: 2011-07-22
Posts: 52
Website

Re: wlan can scan but cannot connect

Try to do the following (gnome3)

1- Make sure you installed the following:

pacman -S  --needed usb_modeswitch  wvdial  ifplugd network-manager-applet  polkit-gnome  polkit  consolekit gome-keyring  libgnome-keyring  pyxdg

2- Add networkmanager in daemons at the /etc/rc.conf and put ! before network. (DAEMONS=(hwclock syslog-ng !network netfs crond dbus networkmanager gdm)

3- Remove eth0 from /etc/rc.conf  "INTERFACE"

Restart and it should be fine.

Last edited by ehabreda (2011-09-15 17:18:27)

Offline

#4 2011-09-21 10:44:37

gnarliprime
Member
Registered: 2011-09-01
Posts: 11

Re: wlan can scan but cannot connect

Hey, thanks for responding. I have done what you suggested, but it does not appear to have worked. I disabled authentication at the router, however it still cannot connect. Could it be a driver issue? or permissions? I haven't fixed the permissions for a normal user, so it still asks for su pass when it tries to connect through cli or gnome. Ethernet connects fine for standard user

rc.conf infos
INTERFACES=(!eth0 !wlan0)
DAEMONS=(hwclock syslog-ng !network sshd dbus networkmanager slim netfs crond)
MODULES=()


my lsmod

Module                  Size  Used by
fuse                   58597  2 
ipv6                  249881  10 
ext2                   55595  1 
lm63                    4867  0 
radeon                910895  3 
arc4                    1086  2 
ttm                    45269  1 radeon
drm_kms_helper         21997  1 radeon
drm                   147750  5 radeon,ttm,drm_kms_helper
b43                   297353  0 
mac80211              191317  1 b43
cfg80211              138492  2 b43,mac80211
rfkill                 12406  2 cfg80211
i2c_algo_bit            4423  1 radeon
snd_wavefront          28274  0 
snd_cs4236             22327  0 
snd_wss_lib            18044  2 snd_wavefront,snd_cs4236
ssb                    42291  1 b43
snd_opl3_lib            7314  2 snd_wavefront,snd_cs4236
mmc_core               65185  2 b43,ssb
pcmcia                 31438  2 b43,ssb
snd_hwdep               4942  2 snd_wavefront,snd_opl3_lib
skge                   33972  0 
pcmcia_core            10082  1 pcmcia
serio_raw               3390  0 
snd_mpu401              3760  0 
shpchp                 22529  0 
snd_mpu401_uart         4943  3 snd_wavefront,snd_cs4236,snd_mpu401
pci_hotplug            22322  1 shpchp
ppdev                   4814  0 
firewire_ohci          25944  0 
sg                     20982  0 
evdev                   7278  4 
snd_intel8x0           22364  2 
snd_ac97_codec         90021  1 snd_intel8x0
firewire_core          43387  1 firewire_ohci
crc_itu_t               1069  1 firewire_core
snd_rawmidi            15196  2 snd_wavefront,snd_mpu401_uart
ac97_bus                 810  1 snd_ac97_codec
snd_seq_device          4252  2 snd_opl3_lib,snd_rawmidi
pcspkr                  1375  0 
psmouse                56431  0 
ns558                   1831  0 
gameport                6644  2 ns558
snd_pcm                60015  4 snd_cs4236,snd_wss_lib,snd_intel8x0,snd_ac97_codec
parport_pc             27806  0 
nvidia_agp              4160  1 
agpgart                22096  3 ttm,drm,nvidia_agp
parport                25939  2 ppdev,parport_pc
processor              21876  0 
button                  3646  0 
snd_timer              15374  3 snd_wss_lib,snd_opl3_lib,snd_pcm
snd                    43561  17 snd_wavefront,snd_cs4236,snd_wss_lib,snd_opl3_lib,snd_hwdep,snd_mpu401,snd_mpu401_uart,snd_intel8x0,snd_ac97_codec,snd_rawmidi,snd_seq_device,snd_pcm,snd_timer
soundcore               4986  1 snd
i2c_nforce2             4328  0 
i2c_core               16625  6 lm63,radeon,drm_kms_helper,drm,i2c_algo_bit,i2c_nforce2
snd_page_alloc          5837  3 snd_wss_lib,snd_intel8x0,snd_pcm
forcedeth              47299  0 
ext4                  337790  2 
mbcache                 4249  2 ext2,ext4
jbd2                   59488  1 ext4
crc16                   1069  1 ext4
sr_mod                 13244  0 
sd_mod                 26147  5 
cdrom                  31277  1 sr_mod
pata_acpi               2388  0 
sata_sil                6360  0 
pata_amd                8155  4 
libata                154449  3 pata_acpi,sata_sil,pata_amd
ohci_hcd               19226  0 
ehci_hcd               34935  0 
scsi_mod              111801  4 sg,sr_mod,sd_mod,libata
usbcore               119612  3 ohci_hcd,ehci_hcd



When I iwconfig the wlan0 interface I can get it to recognize the essid but it will not associate. dhcpcd wlan0 times out. I found this in my everything log:

Sep 21 05:10:50 localhost NetworkManager[747]: <info> Config: added 'ssid' value 'Teradactyle.com'
Sep 21 05:10:50 localhost NetworkManager[747]: <info> Config: added 'scan_ssid' value '1'
Sep 21 05:10:50 localhost NetworkManager[747]: <info> Config: added 'key_mgmt' value 'NONE'
Sep 21 05:10:50 localhost NetworkManager[747]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Sep 21 05:10:50 localhost NetworkManager[747]: <info> Config: set interface ap_scan to 1
Sep 21 05:10:50 localhost NetworkManager[747]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Sep 21 05:10:51 localhost NetworkManager[747]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Sep 21 05:10:51 localhost kernel: [   97.380075] wlan0: direct probe to 00:18:f8:dc:40:0f (try 1/3)
Sep 21 05:10:52 localhost kernel: [   97.580025] wlan0: direct probe to 00:18:f8:dc:40:0f (try 2/3)
Sep 21 05:10:52 localhost kernel: [   97.780025] wlan0: direct probe to 00:18:f8:dc:40:0f (try 3/3)
Sep 21 05:10:52 localhost kernel: [   97.980019] wlan0: direct probe to 00:18:f8:dc:40:0f timed out
Sep 21 05:10:58 localhost kernel: [  104.363393] wlan0: direct probe to 00:18:f8:dc:40:0f (try 1/3)
Sep 21 05:10:59 localhost kernel: [  104.563361] wlan0: direct probe to 00:18:f8:dc:40:0f (try 2/3)
Sep 21 05:10:59 localhost kernel: [  104.763351] wlan0: direct probe to 00:18:f8:dc:40:0f (try 3/3)
Sep 21 05:10:59 localhost kernel: [  104.963349] wlan0: direct probe to 00:18:f8:dc:40:0f timed out
Sep 21 05:11:05 localhost kernel: [  111.353404] wlan0: direct probe to 00:18:f8:dc:40:0f (try 1/3)
Sep 21 05:11:06 localhost kernel: [  111.553349] wlan0: direct probe to 00:18:f8:dc:40:0f (try 2/3)
Sep 21 05:11:06 localhost kernel: [  111.753350] wlan0: direct probe to 00:18:f8:dc:40:0f (try 3/3)
Sep 21 05:11:06 localhost kernel: [  111.953350] wlan0: direct probe to 00:18:f8:dc:40:0f timed out
Sep 21 05:11:12 localhost kernel: [  118.350081] wlan0: direct probe to 00:18:f8:dc:40:0f (try 1/3)
Sep 21 05:11:13 localhost kernel: [  118.550023] wlan0: direct probe to 00:18:f8:dc:40:0f (try 2/3)
Sep 21 05:11:13 localhost kernel: [  118.750020] wlan0: direct probe to 00:18:f8:dc:40:0f (try 3/3)
Sep 21 05:11:13 localhost kernel: [  118.950014] wlan0: direct probe to 00:18:f8:dc:40:0f timed out
Sep 21 05:11:15 localhost NetworkManager[747]: <warn> Activation (wlan0/wireless): association took too long, failing activation.
Sep 21 05:11:15 localhost NetworkManager[747]: <info> (wlan0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
Sep 21 05:11:15 localhost NetworkManager[747]: <warn> Activation (wlan0) failed for access point (Teradactyle.com)
Sep 21 05:11:15 localhost NetworkManager[747]: <info> Marking connection 'Auto Teradactyle.com' invalid.
Sep 21 05:11:15 localhost NetworkManager[747]: <warn> Activation (wlan0) failed.
Sep 21 05:11:15 localhost NetworkManager[747]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Sep 21 05:11:15 localhost NetworkManager[747]: <info> (wlan0): deactivating device (reason: 0).
Sep 21 05:11:15 localhost NetworkManager[747]: <info> Policy set 'Wired connection 2' (eth0) as default for IPv4 routing and DNS.
Sep 21 05:11:15 localhost NetworkManager[747]: <info> Policy set 'Wired connection 2' (eth0) as default for IPv4 routing and DNS.
Sep 21 05:11:15 localhost NetworkManager[747]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Sep 21 05:11:15 localhost NetworkManager[747]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.

I'm not sure what other infos would be helpful. I appreciate any suggestions.

Offline

#5 2011-09-21 11:42:42

satanselbow
Member
Registered: 2011-06-15
Posts: 538

Re: wlan can scan but cannot connect

gnarliprime wrote:

rc.conf infos
INTERFACES=(!eth0 !wlan0)


Shouldn't that line just be empty? By negating both eth/wlan0 you are flagging them as unusable... I'm not on my box so can't check it - maybe someone can confirm this?

Last edited by satanselbow (2011-09-21 11:42:58)

Offline

#6 2011-09-21 11:56:05

gnarliprime
Member
Registered: 2011-09-01
Posts: 11

Re: wlan can scan but cannot connect

Hey! I appreciate the response

That should work. My laptop has no networking issues with the rc.conf set up the same way
grep INTERFACES /etc/rc.conf
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
INTERFACES=(!eth0 !wlan0)

I think i got this from the networkmanager wiki.
https://wiki.archlinux.org/index.php/NetworkManager

However, now that I look it up, it does say:
"Edit /etc/rc.conf and where you defined DHCP or a static IP address, comment them out:
Note: Following settings are obsolete in the most recent rc.conf.
#eth0="dhcp"                                                                   
#wlan0="dhcp"                                                                   
INTERFACES=(!eth0 !wlan0)"

Do you think this would cause it? I just ran pacman -Syu on this laptop (last time it was ran was a month or so ago) to get everything up to par with the desktop i'm currently working with, however the rc.conf hasn't changed so I'm not sure if this is where the issue is stemming from

Last edited by gnarliprime (2011-09-21 12:05:44)

Offline

#7 2011-09-29 06:13:40

gnarliprime
Member
Registered: 2011-09-01
Posts: 11

Re: wlan can scan but cannot connect

To alleviate possible random issues of me being drunk and installing duplicate drivers etc, I ran chakra live w/restricted drivers and received the same results. Grepping the kernel.log for wlan0 gave a "wlan0 not ready" message and grepping everything.log for wlan0 displayed similar messages... At this point I'm not sure what could be causing the issue. The card worked fine in winxp prior to installing arch, so the hardware seems to be acceptable.

Last edited by gnarliprime (2011-09-29 09:11:36)

Offline

#8 2011-11-12 18:07:49

liaowang11
Member
Registered: 2011-10-25
Posts: 6

Re: wlan can scan but cannot connect

I have the same issue.
No solution after one month trying..

Offline

Board footer

Powered by FluxBB