Thinkpad T60 with Atheros working only after restart from Windows
Lyubomir Yotov
l.yotov at gmail.com
Mon Jun 24 20:01:37 UTC 2013
Hi Adrian,
I will try to get -HEAD on my T60 and will report back.
Regards,
Lyubomir
On 24 June 2013 20:21, Adrian Chadd <adrian at freebsd.org> wrote:
> Hi,
>
> Would you be willing to try a -HEAD snapshot on your laptop?
>
> Maybe I've fixed it as part of the other driver work that I've done as
> part of development in -HEAD.
>
> But right now I really have no idea. I don't have a T60 here that has
> that chip in it. If all the T60 BIOSes allow AR5418 NICs then I can
> try it out, but all of the T60's I've played with thus far have the
> intel hardware in it.
>
>
>
> Adrian
>
>
> On 21 June 2013 02:02, Lyubomir Yotov <l.yotov at gmail.com> wrote:
> > Hello Adrian,
> >
> > Do you have any feedback on the matter?
> >
> > Regards,
> >
> > Lyubomir
> >
> >
> > On 13 June 2013 10:09, Lyubomir Yotov <l.yotov at gmail.com> wrote:
> >>
> >> Hello Adrian,
> >>
> >> I enabled acpi_ibm.ko but this didn't help and after "halt" the wifi is
> >> not working again.
> >>
> >> Regards,
> >>
> >> Lyubomir
> >>
> >>
> >> On 13 June 2013 08:03, Lyubomir Yotov <l.yotov at gmail.com> wrote:
> >>>
> >>> Hello Adrian,
> >>> I did some tests and discovered that the problem is related to
> >>> "halt"/"shutdown" of system. If "reboot" is carried out than there is
> no
> >>> problem and the wifi works properly (even if done from Gnome - Gnome
> seems
> >>> to have no relation to the problem). So what could lead to "ath0: time
> out"
> >>> after shutting down or halting the system? I noticed that there are irq
> >>> storms on irq 17 which is the wifi irq (interrupt storm detected on
> >>> "irq17:"; throttling interrupt source). Something else that I am not
> sure to
> >>> have relevance - after shutdown during the start-up ath0 is reported
> to use
> >>> autoselect mode 11g:
> >>> (below is from dmesg)
> >>>
> >>> ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
> >>> 2290
> >>>
> >>> ether 00:19:7e:91:xx:xx
> >>> nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> >>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
> >>> status: associated
> >>>
> >>> After the boot has finished the mode changes to 11a:
> >>>
> >>> #ifconfig ath0
> >>>
> >>> ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
> >>> 2290
> >>> ether 00:19:7e:91:xx:xx
> >>> nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> >>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11a
> >>> status: associated
> >>>
> >>> Do you have any idea where to look for now?
> >>>
> >>> Regards,
> >>>
> >>>
> >>> Lyubomir
> >>> P.S. I will try to play with acpi_ibm.ko and see if things change if I
> >>> make it auto-load.
> >>>
> >>>
> >>> On 10 June 2013 16:06, Lyubomir Yotov <l.yotov at gmail.com> wrote:
> >>>>
> >>>> Hello Adrian,
> >>>>
> >>>> Attached are files with consecutive vmstat -i when the wlan is working
> >>>> (vmstat-i_working.txt) and when the wlan is not working
> >>>> (vmstat-i_not_working.txt). There is also output from ifconfig when
> the wlan
> >>>> is not working (ifconfig.txt).
> >>>> After some more deeper investigation it seems to me that the problem
> >>>> appears after starting X with Gnome. I will continue investigating
> with
> >>>> "reboot"/"halt -p" and inform you.
> >>>> BTW do you think that starting Gnome session (using startx, as I
> haven't
> >>>> set auto start of X if this is of any importance) can cause problems
> - in
> >>>> Gnome I have no settings for the network in the "System->Network"
> >>>> application and I start it with normal user?
> >>>>
> >>>> Regards,
> >>>>
> >>>> Lyubo
> >>>>
> >>>>
> >>>> On 9 June 2013 18:28, Adrian Chadd <adrian at freebsd.org> wrote:
> >>>>>
> >>>>> Can you please paste the vmstat -i output?
> >>>>>
> >>>>>
> >>>>>
> >>>>> adrian
> >>>>>
> >>>>> On 9 June 2013 06:53, Lyubomir Yotov <l.yotov at gmail.com> wrote:
> >>>>> > Hi,
> >>>>> >
> >>>>> > After restart from Windows and working wireless the number of
> >>>>> > interrupts
> >>>>> > increases and the rate increases. After next restart (the ath0
> times
> >>>>> > out)
> >>>>> > the interrupts increase but the rate is going down.
> >>>>> > I noticed that after restart from Windows and working wifi if I
> >>>>> > restart
> >>>>> > /etc/rc.d/netif the wifi is working again. If I shutdown wlan0 and
> >>>>> > bring it
> >>>>> > up again then I wlan0 doesn't get address but ath0 is not timing
> out.
> >>>>> > I can
> >>>>> > still get a list with the available APs around.
> >>>>> >
> >>>>> > Regards,
> >>>>> >
> >>>>> > Lyubo
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> > On 8 June 2013 18:28, Adrian Chadd <adrian at freebsd.org> wrote:
> >>>>> >>
> >>>>> >> Hm!
> >>>>> >>
> >>>>> >> Ok, this should be working. I frequently test (read: every other
> >>>>> >> day)
> >>>>> >> with the AR5416. But you're not the first person to report this
> bug.
> >>>>> >>
> >>>>> >>
> >>>>> >> Unfortunately when this happens, the interrupts aren't actually
> >>>>> >> making
> >>>>> >> it to the OS.
> >>>>> >>
> >>>>> >> Can you check the output of vmstat -i whilst you're doing it? The
> >>>>> >> ath0
> >>>>> >> counter should be increasing.
> >>>>> >>
> >>>>> >>
> >>>>> >>
> >>>>> >> adrian
> >>>>> >>
> >>>>> >> On 8 June 2013 06:49, Lyubomir Yotov <l.yotov at gmail.com> wrote:
> >>>>> >> > Hello,
> >>>>> >> > I have a Thinkpad T60 with dual boot between Windows XP and
> >>>>> >> > FreeBSD
> >>>>> >> > 9.1-Release:
> >>>>> >> >
> >>>>> >> > uname -a
> >>>>> >> > FreeBSD T60.workgroup 9.1-RELEASE FreeBSD 9.1-RELEASE #0
> r243826:
> >>>>> >> > Tue
> >>>>> >> > Dec
> >>>>> >> > 4 06:55:39 UTC 2012
> >>>>> >> > root at obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
> >>>>> >> > i386
> >>>>> >> >
> >>>>> >> > I am trying to use my wifi card which is:
> >>>>> >> >
> >>>>> >> > dmesg
> >>>>> >> > ....
> >>>>> >> > ath0: <Atheros 5416> mem 0xedf00000-0xedf0ffff irq 17 at device
> >>>>> >> > 0.0 on
> >>>>> >> > pci3
> >>>>> >> > ath0: AR5418 mac 12.10 RF5133 phy 8.1
> >>>>> >> > ....
> >>>>> >> >
> >>>>> >> > pciconf -lv
> >>>>> >> > ....
> >>>>> >> > ath0 at pci0:3:0:0: class=0x028000 card=0x0033168c
> >>>>> >> > chip=0x0024168c
> >>>>> >> > rev=0x01 hdr=0x00
> >>>>> >> > vendor = 'Atheros Communications Inc.'
> >>>>> >> > device = 'AR5008 Wireless Network Adapter'
> >>>>> >> > class = network
> >>>>> >> > .....
> >>>>> >> >
> >>>>> >> > I followed several HOW-TOs in order to make it work.
> Unfortunately
> >>>>> >> > I it
> >>>>> >> > is
> >>>>> >> > working only after I reboot from my Windows installation
> >>>>> >> > (regardless of
> >>>>> >> > the
> >>>>> >> > position of the wifi switch on the front panel of the notebook).
> >>>>> >> > After
> >>>>> >> > restart from Windows everything is fine - the wifi associates
> with
> >>>>> >> > the
> >>>>> >> > AP
> >>>>> >> > and I can use it. If I reboot the system during the boot and
> >>>>> >> > afterwards
> >>>>> >> > I
> >>>>> >> > constantly get:
> >>>>> >> >
> >>>>> >> > ath0: device timeout
> >>>>> >> >
> >>>>> >> > When I get the device status through ifconfig I can see that
> ath0
> >>>>> >> > is
> >>>>> >> > associated but wlan0 is not associated.
> >>>>> >> >
> >>>>> >> > ifconfig ath0
> >>>>> >> > ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric
> 0
> >>>>> >> > mtu
> >>>>> >> > 2290
> >>>>> >> > ether 00:19:7e:91:xx:xx
> >>>>> >> > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> >>>>> >> > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
> >>>>> >> > status: associated
> >>>>> >> >
> >>>>> >> > ifconfig wlan0
> >>>>> >> > wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
> metric 0
> >>>>> >> > mtu
> >>>>> >> > 1500
> >>>>> >> > ether 00:19:7e:91:xx:xx
> >>>>> >> > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> >>>>> >> > media: IEEE 802.11 Wireless Ethernet autoselect
> >>>>> >> > (autoselect)
> >>>>> >> > status: no carrier
> >>>>> >> > ssid "" channel 5 (2432 MHz 11g)
> >>>>> >> > regdomain 98 indoor ecm authmode WPA privacy ON deftxkey
> >>>>> >> > UNDEF
> >>>>> >> > txpower 20 bmiss 7 scanvalid 450 bgscan bgscanintvl 300
> >>>>> >> > bgscanidle
> >>>>> >> > 250
> >>>>> >> > roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming
> >>>>> >> > MANUAL
> >>>>> >> >
> >>>>> >> >
> >>>>> >> > In /var/log/messages I get:
> >>>>> >> >
> >>>>> >> > Jun 8 16:39:16 PC wpa_supplicant[3463]: Trying to associate
> with
> >>>>> >> > 54:e6:fc:ae:xx:xx (SSID='access1' freq=2432 MHz)
> >>>>> >> > Jun 8 16:39:20 PC kernel: ath0: device timeout
> >>>>> >> > Jun 8 16:39:26 PC wpa_supplicant[3463]: Authentication with
> >>>>> >> > 54:e6:fc:ae:xx:xx timed out.
> >>>>> >> >
> >>>>> >> > If I scan for wireless networks I get a list and my ap is in the
> >>>>> >> > list
> >>>>> >> >
> >>>>> >> > ifconfig wlan0 scan
> >>>>> >> > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS
> >>>>> >> > net1 00:11:11:01:xx:xx 6 54M -68:-96 100 EP
> >>>>> >> > 5edf9c 70:71:bc:26:xx:xx 11 54M -68:-96 100 EP
> WPS
> >>>>> >> > WPA
> >>>>> >> > WME
> >>>>> >> > access1 54:e6:fc:ae:xx:xx 5 54M -66:-96 100 EP WPA
> >>>>> >> > HTCAP
> >>>>> >> > WME
> >>>>> >> >
> >>>>> >> >
> >>>>> >> > In rc.local I have:
> >>>>> >> >
> >>>>> >> > wlans_ath0="wlan0"
> >>>>> >> > ifconfig_wlan0="WPA DHCP"
> >>>>> >> >
> >>>>> >> > In wpa_supplicant I have:
> >>>>> >> >
> >>>>> >> > ctrl_interface=/var/run/wpa_supplicant
> >>>>> >> > eapol_version=2
> >>>>> >> > ap_scan=1
> >>>>> >> > fast_reauth=1
> >>>>> >> >
> >>>>> >> > network={
> >>>>> >> > ssid="access1"
> >>>>> >> > psk="secret1"
> >>>>> >> > priority=5
> >>>>> >> > }
> >>>>> >> > network={
> >>>>> >> > ssid="access2"
> >>>>> >> > psk="secret2"
> >>>>> >> > priority=5
> >>>>> >> > }
> >>>>> >> >
> >>>>> >> > I searched the net for solution to my problem but I couldn't
> find
> >>>>> >> > one.
> >>>>> >> > Can
> >>>>> >> > you help me with this?
> >>>>> >> >
> >>>>> >> >
> >>>>> >> > Regards,
> >>>>> >> >
> >>>>> >> > Lyubomir
> >>>>> >> > _______________________________________________
> >>>>> >> > freebsd-mobile at freebsd.org mailing list
> >>>>> >> > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
> >>>>> >> > To unsubscribe, send any mail to
> >>>>> >> > "freebsd-mobile-unsubscribe at freebsd.org"
> >>>>> >
> >>>>> >
> >>>>
> >>>>
> >>>
> >>
> >
>
More information about the freebsd-wireless
mailing list