Date: Thu, 7 Aug 2008 06:13:57 -0700 (PDT) From: Alexander Sack <pisymbol@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Atheros (ath) MSI wireless embedded chipset fails to attach on 7.0-STABLE Message-ID: <18870155.post@talk.nabble.com> In-Reply-To: <20080617205053.20873zhqvlj7zles@intranet.casasponti.net> References: <3c0b01820806170757v5565b59ne0e9d5db06f26761@mail.gmail.com> <4857D8BB.1080901@gmail.com> <3c0b01820806170852t39a6346doa6d77a655469eed9@mail.gmail.com> <20080617135900.18654t73s6d7sfqc@intranet.casasponti.net> <48580EB9.7090701@gmail.com> <20080617143554.1808562gg94i8ikg@intranet.casasponti.net> <3c0b01820806171244g6f2ba46ybe0ba6d89eaab13b@mail.gmail.com> <3c0b01820806171417l2b054e15i5627d88827cc03b4@mail.gmail.com> <3c0b01820806171648g7cc01476l30df79831f9b9c6@mail.gmail.com> <20080617205053.20873zhqvlj7zles@intranet.casasponti.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Edwin L. Culp wrote: >=20 > "Alexander Sack" <pisymbol@gmail.com> escribi=C3=B3: >=20 >> Final update, I got everything working! I came home and connected by >> new notebook using the latest PCIe Atheros chipset to a WPA2 network >> using wpa_supplicant! Yippie! >> >> Hope this thread helps someone else, >> >> -aps >> >> On Tue, Jun 17, 2008 at 5:17 PM, Alexander Sack <pisymbol@gmail.com> >> wrote: >>> On Tue, Jun 17, 2008 at 3:44 PM, Alexander Sack <pisymbol@gmail.com> >>> wrote: >>>> On Tue, Jun 17, 2008 at 3:35 PM, Edwin L. Culp =20 >>>> <eculp@casasponti.net> wrote: >>>>> "Manolis Kiagias" <sonic2000gr@gmail.com> escribi=C3=B3: >>>>> >>>>>> Edwin L. Culp wrote: >>>>>>> >>>>>>> "Alexander Sack" <pisymbol@gmail.com> escribi=C3=B3: >>>>>>> >>>>>>>> On Tue, Jun 17, 2008 at 11:31 AM, Manolis Kiagias >>>>>>>> <sonic2000gr@gmail.com> wrote: >>>>>>>>> >>>>>>>>> Alexander Sack wrote: >>>>>>>>>> >>>>>>>>>> Hello: >>>>>>>>>> >>>>>>>>>> I have installed FreeBSD-7.0-amd64 stable on my new AMD X2 =20 >>>>>>>>>> Turon based >>>>>>>>>> notebook, a MSI-1710A (GX710Ax) which has a generic embedded >>>>>>>>>> controller. During boot up I notice that ATH complains with: >>>>>>>>>> >>>>>>>>>> ath_rate: version 1.2 <SampleRate bit-rate selection algorithm> >>>>>>>>>> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, >>>>>>>>>> RF2413, >>>>>>>>>> RF5413) >>>>>>>>>> ath0: <Atheros 5424/2424> mem 0xfd7f0000-0xfd7fffff irq 16 at >>>>>>>>>> device >>>>>>>>>> 0.0 >>>>>>>>>> on pci2 >>>>>>>>>> ath0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xfd7f0000 >>>>>>>>>> ath0: [MPSAFE] >>>>>>>>>> ath0: [ITHREAD] >>>>>>>>>> ath0: unable to attach hardware; HAL status 13 >>>>>>>>>> device_attach: ath0 attach returned 6 >>>>>>>>>> >>>>>>>>>> HAL status 13 from the header file seems to indicate that the >>>>>>>>>> 7.0-STABLE driver doesn't support my hardware revision. Here is >>>>>>>>>> my >>>>>>>>>> pciconf -l output: >>>>>>>>>> >>>>>>>>> >>>>>>>>> Maybe you could try compiling a kernel with a newer hal. This is >>>>>>>>> the >>>>>>>>> kind of >>>>>>>>> hack we use on the eeepc. Have a look at this: >>>>>>>>> >>>>>>>>> http://nighthack.org/wiki/EeeBSD >>>>>>>> >>>>>>>> Thank you SO much for this link. That's EXACTLY what I want to do >>>>>>>> because I realize that this is a HAL problem. I've been searching >>>>>>>> like MAD where I could get an updated binary HAL for this chipset >>>>>>>> (PCIe based). >>>>>>> >>>>>>> That makes two of us ;) >>>>>>> >>>>>>> My dmesg is very, very similar to yours and hoped that this would >>>>>>> work. >>>>>>> >>>>>>> ath0: <Atheros 5424/2424> mem 0xf2200000-0xf220ffff irq 19 at devic= e >>>>>>> 0.0 >>>>>>> on pci5 >>>>>>> ath0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xf2200000 >>>>>>> ioapic0: routing intpin 19 (PCI IRQ 19) to vector 64 >>>>>>> ath0: [MPSAFE] >>>>>>> ath0: [ITHREAD] >>>>>>> ath0: unable to attach hardware; HAL status 13 >>>>>>> device_attach: ath0 attach returned 6 >>>>>>> >>>>>>> I followed the instructions from the web page, recompiled and it >>>>>>> made no >>>>>>> difference which really worries me that I must have done =20 >>>>>>> something wrong. >>>>>>> >>>>>>> cd madwifi-ng-r2756+ar5007/hal >>>>>>> cp -R * /usr/src/sys/contrib/dev/ath/ >>>>>>> >>>>>>> I did not erase it previously but am going to try that. I made no >>>>>>> kern >>>>>>> configuration changes to find that the hal is from contrib. Is >>>>>>> there >>>>>>> nothing else I should do? >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>> >>>>>> Well, I have only tested this on the eeepc and can confirm it works. >>>>>> Maybe different atheros chipset have other problems not directly >>>>>> related >>>>>> to the hal version. >>>>>> You do not need to do anything more that what is shown in the =20 >>>>>> page: untar, >>>>>> replace the existing files, recompile / install kernel, reboot. =20 >>>>>> If you got >>>>>> no errors during the kernel compilation phase, you can safely =20 >>>>>> assume you did >>>>>> everything correctly, and the problem lies elsewhere. >>>>> >>>>> At least there was a ray of hope for the time it took to compile =20 >>>>> the kernel. >>>> >>>> Ed: >>>> >>>> I took recompiled and got the same issue. If I use the LATEST mad >>>> distro I get some compile bugs (ath_desc_status was moved into >>>> ath_desc structure in ah_desc.h) which I can't completely work around >>>> (apparently the API into the HAL has changed as well). What I'm >>>> trying to do is look at the Linux driver and understand the newer API >>>> in order to get past this compile issue and see if this works. >>>> Otherwise I believe we are SOL. >>>> >>>> Does anyone know if the CURRENT contains an updated ath HAL AND driver >>>> for support of newer PCIe based chipsets? >>>> >>>> If I get it to work I will let you know... >>>> >>> >>> Ok the trick is not to get it from the madfi project. Get it from the >>> author directly! >>> >>> If you grab: >>> >>> http://people.freebsd.org/~sam/ath_hal-20080528.tgz >>> >>> Copy the contents into the src/sys/contrib/dev/ath/* and recompile, >>> you should now see ath attach properly to the your NIC card. Thanks >>> go to my friend jkim for pointing this out since he has a similar >>> notebook/chipset and runs CURRENT successfully. I tried using CURRENT >>> ath but there is to much vap support in it and it turned out the >>> 7.0-RELEASE driver works. >>> >>> Now ath attaches properly and I'm going to test it out! (this is at >>> least much further than a bad attach status code from the HAL). >>> >>> Let me know how it goes, >=20 > Going G R E A T for the first time I see: >=20 > ath_hal: 0.10.5.6 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, =20 > RF2413, RF5413, RF2133, RF2425, RF2417) >=20 > ath0: <Atheros 5424/2424> mem 0xf2200000-0xf220ffff irq 19 at device =20 > 0.0 on pci5 > ath0: [ITHREAD] > ath0: WARNING: using obsoleted if_watchdog interface > ath0: mac 14.2 phy 7.0 radio 10.2 >=20 > and an ifconfig ath0 shows: >=20 > ath0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2= 290 > =09ether 00:1d:d9:27:5c:e5 > =09media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > =09status: no carrier >=20 > My problem is now the no carrier, I think that I'm very close but =20 > still no cigar. >=20 > Thanks soooooo much for your help. Gonna bang away and the manuals =20 > and google to find out why, no carrier. I have an AP a few feet away =20 > and iPhone works great. >=20 Did you get this to ever work? I am now running into the same issue. What had happened was I sent my notebook back to fix a plastic latch and at the sametime work changed the wireless AP settings. Now when the chipset comes up I constantly get no carrier and ifconfig ath0 scan list just hangs (sits there). Any idea what maybe the issue? This is highly frustrating because it WAS working (I'm using a new 7.0-STABLE, from yesterday freshly built against Sam's latest HAL). Thanks! -aps --=20 View this message in context: http://www.nabble.com/Atheros-%28ath%29-MSI-w= ireless-embedded-chipset-fails-to-attach-on-7.0-STABLE-tp17913515p18870155.= html Sent from the freebsd-questions mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18870155.post>