Date: Thu, 29 Jan 2009 22:28:03 +0100 From: "Paul B. Mahol" <onemda@gmail.com> To: Lars Engels <lme@freebsd.org> Cc: current@freebsd.org Subject: Re: ath cannot find my wireless network any more Message-ID: <3a142e750901291328w537b2070t216e393a0fd5b8ba@mail.gmail.com> In-Reply-To: <20090129204323.GB60948@e.0x20.net> References: <20090129192241.GZ60948@e.0x20.net> <20090129192830.GE73709@citylink.fud.org.nz> <20090129194826.GA60948@e.0x20.net> <49820EAC.5090400@freebsd.org> <20090129204323.GB60948@e.0x20.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/29/09, Lars Engels <lme@freebsd.org> wrote: > On Thu, Jan 29, 2009 at 12:16:44PM -0800, Sam Leffler wrote: >> Lars Engels wrote: >> >On Thu, Jan 29, 2009 at 11:28:30AM -0800, Andrew Thompson wrote: >> > >> >>On Thu, Jan 29, 2009 at 08:22:41PM +0100, Lars Engels wrote: >> >> >> >>>Hi all, >> >>>hi Sam, >> >>> >> >>>I just build world && kernel from todays sources. >> >>>Now my Atheros 5212 pccard cannot find my wireless network any more, >> >>> but >> >>>still sees other networks: >> >>> >> >>>lars@pts/3 # ifconfig wlan0 up scan >> >>>SSID BSSID CHAN RATE S:N INT CAPS >> >>>Arcor-C6DE58 00:1a:2a:c6:de:56 9 54M -95:-96 100 EPS RSN WPA >> >>> WME >> >>>WLAN-AFCB47 00:1d:19:af:cb:e0 1 54M -96:-96 100 EPS WPS RSN >> >>> WPA WME >> >>>0x0000 00:03:c9:54:18:bb 8 54M -94:-96 100 EP WPA >> >>> >> >>>In contrast to this, the internal wpi chip still finds and connects to >> >>> the network: >> >>>lars@pts/3 # ifconfig wlan1 scan >> >>>SSID BSSID CHAN RATE S:N INT CAPS >> >>>dd-wrt 00:18:39:c7:6a:dd 6 54M 22:0 100 EP RSN WME >> >>> >> >>>I also don't know why wpi only finds my own network. If such behavior was from start(not regression) it can means only wpi problem/feature. >> >>> >> >> If you go 'ifconfig wlan0 list chan' does it show #6 as available? >> >> >> > >> > >> >Yes, it's there: >> >lars@pts/3 # ifconfig wlan0 list chan >> >Channel 1 : 2412 Mhz 11g Channel 48 : 5240 Mhz 11a Turbo >> >Channel 2 : 2417 Mhz 11g Channel 50 : 5250 Mhz 11a Turbo >> >Channel 3 : 2422 Mhz 11g Channel 52 : 5260 Mhz 11a >> >Channel 4 : 2427 Mhz 11g Channel 56 : 5280 Mhz 11a Turbo >> >Channel 5 : 2432 Mhz 11g Channel 58 : 5290 Mhz 11a Turbo >> >Channel 6 : 2437 Mhz 11g Turbo Channel 60 : 5300 Mhz 11a >> >Channel 7 : 2442 Mhz 11g Channel 64 : 5320 Mhz 11a >> >Channel 8 : 2447 Mhz 11g Channel 149 : 5745 Mhz 11a >> >Channel 9 : 2452 Mhz 11g Channel 152 : 5760 Mhz 11a Turbo >> >Channel 10 : 2457 Mhz 11g Channel 153 : 5765 Mhz 11a Turbo >> >Channel 11 : 2462 Mhz 11g Channel 157 : 5785 Mhz 11a >> >Channel 36 : 5180 Mhz 11a Channel 160 : 5800 Mhz 11a Turbo >> >Channel 40 : 5200 Mhz 11a Turbo Channel 161 : 5805 Mhz 11a Turbo >> >Channel 42 : 5210 Mhz 11a Turbo Channel 165 : 5825 Mhz 11a >> >Channel 44 : 5220 Mhz 11a >> > >> > >> >> Not sure about the wpi complaint. For ath I need mac+phy revs and any >> regulatory setting (output sysctl dev.ath.0 will show it). You might >> also enable scan debug to see if the ap shows up but isn't recorded >> for some reason; e.g. wlandebug -i ath0 scan. > > Here is the output for sysctl: > > ars@pts/3 # sysctl dev.ath.0 > dev.ath.0.%desc: Atheros 5212 > dev.ath.0.%driver: ath > dev.ath.0.%location: slot=0 function=0 > dev.ath.0.%pnpinfo: vendor=0x168c device=0x0013 subvendor=0x1385 > subdevice=0x4610 class=0x020000 > dev.ath.0.%parent: cardbus0 > dev.ath.0.smoothing_rate: 95 > dev.ath.0.sample_rate: 10 > dev.ath.0.sample_stats: 0 > dev.ath.0.countrycode: 0 > dev.ath.0.regdomain: 0 > dev.ath.0.slottime: 9 > dev.ath.0.acktimeout: 48 > dev.ath.0.ctstimeout: 48 > dev.ath.0.softled: 0 > dev.ath.0.ledpin: 0 > dev.ath.0.ledon: 0 > dev.ath.0.ledidle: 2700 > dev.ath.0.txantenna: 0 > dev.ath.0.rxantenna: 2 > dev.ath.0.diversity: 1 > dev.ath.0.txintrperiod: 5 > dev.ath.0.diag: 0 > dev.ath.0.tpscale: 0 > dev.ath.0.tpc: 0 > dev.ath.0.tpack: 63 > dev.ath.0.tpcts: 63 > dev.ath.0.fftxqmin: 2 > dev.ath.0.fftxqmax: 50 > dev.ath.0.intmit: 1 > dev.ath.0.monpass: 24 > > > lars@pts/3 # wlandebug -i ath0 scan > wlandebug: expecting a wlan interface name > > So I ran > # wlandebug -i wlan0 scan > net.wlan.0.debug: 0x0 => 0x200000<scan> > > But nothing new then: Interesting output is not available from ifconfig it is printed by kernel on console. > lars@pts/3 # ifconfig wlan0 up scan > SSID BSSID CHAN RATE S:N INT CAPS > WLAN-AFCB47 00:1d:19:af:cb:e0 1 54M -93:-96 100 EPS RSN WPA WME > WPS > neumann 00:1b:2f:db:4f:dc 11 54M -95:-96 100 EPS > 0x0000 00:03:c9:54:18:bb 8 54M -94:-96 100 EP WPA > Arcor-C6DE58 00:1a:2a:c6:de:56 9 54M -93:-96 100 EPS RSN WPA WME > > >> I committed major hal changes as a single commit so you can easily >> back it out to see if it's the reason. The other recent changes to >> net80211 should not matter if you rebuilt world to match the kernel >> (the size of the channel structure changed so kernel+apps need to >> match). > > I re-built world, so the net80211 commit should not be the issue. > The ath device worked with sources from last week, so if there was no > other wireless related commit, I guess the new hal changes caused the > problem. I can back out the hal commit if you don't see anything obvious > in my configuration. > > Lars > -- Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750901291328w537b2070t216e393a0fd5b8ba>