Thread: [Madwifi-users] Fujitsu Lifebook S2020, HAL Status 13 (ath_pci.o won't load)
Status: Beta
Brought to you by:
otaku
From: Hunter L. C. <li...@tr...> - 2003-12-20 20:16:27
|
Hello- I apologize if I'm missing something that's documented someplace; I've been looking for a couple days, and can't figure this out. Anyway, the subject pretty much says it all; I'm getting *exactly* the same errors reported by Nirmal Govind a scant 20 hours ago. So I won't bother posting the same information. But anyway, it seems ath_pci.o doesn't want to load on these Fujitsu laptops. I've tried both the tar.gz and the cvs version. So far in my searching I've seen lots of folks complaining about "status 13" but I haven't yet found one of their questions answered... could somebody just give a quick explanation of what usually causes that error? Thanks a lot for everybody's time, Hunter Cook p.s. I accidentally sent this from my other email address a second ago, so it's pending approval. Please don't approve it. Sorry about that. |
From: Hunter L. C. <hu...@tr...> - 2003-12-20 20:12:38
|
Hello- I apologize if I'm missing something that's documented someplace; I've been looking for a couple days, and can't figure this out. Anyway, the subject pretty much says it all; I'm getting *exactly* the same errors reported by Nirmal Govind a scant 20 hours ago. So I won't bother posting the same information. But anyway, it seems ath_pci.o doesn't want to load on these Fujitsu laptops. I've tried both the tar.gz and the cvs version. So far in my searching I've seen lots of folks complaining about "status 13" but I haven't yet found one of their questions answered... could somebody just give a quick explanation of what usually causes that error? Thanks a lot for everybody's time, Hunter Cook |
From: <kri...@ne...> - 2003-12-20 21:51:25
|
Hi Hunter, > So far in my searching I've seen lots of folks complaining about "status > 13" but I haven't yet found one of their questions answered... could > somebody just give a quick explanation of what usually causes that error? the explanation of HAL Status 13 is IIRC "hardware not supported by HAL" (yet). This probably means that you got an incompatible configuration of the atheros chips on your board. I don't know which chips that have not support yet, but I'm sure the madwifi-guys are working on it. Hold out! BR Kristoffer |
From: Hunter L. C. <li...@tr...> - 2003-12-20 22:37:24
|
Thanks for the quick reply... That seems odd...my chip matches pretty well with some that folks have said are working...here's the output of my lspci -vv (only the pertinent bit): 00:11.0 Ethernet controller: Unknown device 168c:0013 (rev 01) Subsystem: Fujitsu Limited.: Unknown device 1235 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin A routed to IRQ 11 Region 0: Memory at dc000000 (32-bit, non-prefetchable) [size=64K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=2 PME- I sure hope it isn't really unsupported; I got this lappy with that chipset specifically because of its linux abilities... Luckily, it looks like this driver is under breakneck-speed development (thanks guys!) so even if it is, it may not be the longest wait (no, the longest wait was for those nvidia drivers...i was waiting in 1997!) Thanks for the help, I'm just going to quit messing with this and go on to the next thing until someone tells me different. Hunter. p.s. one thing that may matter (in both my case and Nirmal's) is that these Fujitsu laptops put about 6 devices on irq 11. Is that a problem? kri...@ne... wrote: >Hi Hunter, > > > >>So far in my searching I've seen lots of folks complaining about >> >> >"status > > >>13" but I haven't yet found one of their questions answered... could >>somebody just give a quick explanation of what usually causes that >> >> >error? > >the explanation of HAL Status 13 is IIRC "hardware not supported by HAL" >(yet). This probably means that you got an incompatible configuration of >the atheros chips on your board. > >I don't know which chips that have not support yet, but I'm sure the >madwifi-guys are working on it. Hold out! > >BR > >Kristoffer > > |
From: Hunter L. C. <li...@tr...> - 2003-12-21 19:30:54
|
Greg- Thanks a lot for that info; good to know I'm pointed in the right direction. Yes, I bought this laptop from Fujitsu direct with integrated atheros minipci...I'm pretty sure that almost all their notebooks (well, all that don't have centrino wlan) use this chipset now; they switched from the broadcom .11g a couple months ago. That was definately the last straw that pushed me to buy it. The laptop also has an antenna built into the screen that ups the range significantly (I know because it has an antenna on/off switch)...in windows this thing really cooks; I can walk around the block from my dlink DI-624. In other words, this is *awesome* hardware. Good job, guys...and kudos to Fujitsu too for recognizing a good thing. But anyway, back to the problem at hand, my HAL version appears to be 0.9.6.3; or at least that's what it said at the bottom of "version.h" in the hal/ directory of the cvs source. I checked everything out from cvs yesterday, so I'm pretty sure it's current. When you said it needed to be at 0.9.6.2, you did mean "or higher", right? As a side note, before I checked out the cvs, I did use the tarball found on sourceforge, with hal version 0.9.5.3; this produced the same result. If there is anything else I can tell you, or tests I can run here to help identify this problem, by all means let me know; I'm no guru, but I can make my way around most of the time... And mostly, thanks a lot for the help on this; I think it's really cool that your company sees the value in hiring someone like you who can both hack code *and* handle service/support on a platform with limited users. Of course, that means you have your work cut out for you...but thanks, I for one really appreciate it. Hunter. Greg Chesson wrote: > 0x0168c:0013 should definitely work. > You ordered the notebook with a factory-installed miniPCI? > > Many laptops put all their devices on irq 11. > Sometimes it causes a problem and sometimes not - difficult to know > for sure. > However, that would not account for your "unsupported hardware" problem. > > If the right people are in the office on monday, I'll ask if Fujitsu > or their suppliers > have done something odd with the rev numbers on the card, or if > there's a new > version of the rf chip, or if they've done something to the bios, or > if they've > implemented a hard rf-kill switch and it's messing up the attach() > procedure. > > Can't tell exactly from your email what went wrong, but the device driver > does support all production Atheros chipset combinations. > > BTW, it would be good to check the version number on your hal. > I didn't see that in your email or in Nirmal's email > (please forgive me if it was there and I missed it). > The hal should be at 0.9.6.2 for supporting all released hardware. > > g > > Hunter L. Cook wrote: > >> Thanks for the quick reply... >> >> That seems odd...my chip matches pretty well with some that folks >> have said are working...here's the output of my lspci -vv (only the >> pertinent bit): >> >> 00:11.0 Ethernet controller: Unknown device 168c:0013 (rev 01) >> Subsystem: Fujitsu Limited.: Unknown device 1235 >> Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV+ VGASnoop- >> ParErr- Stepping- SERR- FastB2B- >> Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >> >TAbort- <TAbort- <MAbort- >SERR- <PERR- >> Interrupt: pin A routed to IRQ 11 >> Region 0: Memory at dc000000 (32-bit, non-prefetchable) >> [size=64K] >> Capabilities: [44] Power Management version 2 >> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA >> PME(D0-,D1-,D2-,D3hot-,D3cold-) >> Status: D0 PME-Enable- DSel=0 DScale=2 PME- >> >> I sure hope it isn't really unsupported; I got this lappy with that >> chipset specifically because of its linux abilities... >> >> Luckily, it looks like this driver is under breakneck-speed >> development (thanks guys!) so even if it is, it may not be the >> longest wait (no, the longest wait was for those nvidia drivers...i >> was waiting in 1997!) >> >> Thanks for the help, I'm just going to quit messing with this and go >> on to the next thing until someone tells me different. >> >> Hunter. >> >> p.s. one thing that may matter (in both my case and Nirmal's) is that >> these Fujitsu laptops put about 6 devices on irq 11. Is that a problem? >> >> kri...@ne... wrote: >> >>> Hi Hunter, >>> >>> >>> >>>> So far in my searching I've seen lots of folks complaining about >>>> >>> >>> >>> "status >>> >>> >>>> 13" but I haven't yet found one of their questions answered... could >>>> somebody just give a quick explanation of what usually causes that >>>> >>> >>> >>> error? >>> >>> the explanation of HAL Status 13 is IIRC "hardware not supported by >>> HAL" >>> (yet). This probably means that you got an incompatible >>> configuration of >>> the atheros chips on your board. >>> >>> I don't know which chips that have not support yet, but I'm sure the >>> madwifi-guys are working on it. Hold out! >>> >>> BR >>> >>> Kristoffer >>> >>> >> >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: IBM Linux Tutorials. >> Become an expert in LINUX or just sharpen your skills. Sign up for >> IBM's >> Free Linux Tutorials. Learn everything from the bash shell to sys >> admin. >> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click >> _______________________________________________ >> Madwifi-users mailing list >> Mad...@li... >> https://lists.sourceforge.net/lists/listinfo/madwifi-users > > > |
From: Michael L. <mi...@sl...> - 2003-12-21 20:24:43
|
Spake Hunter L. Cook: > Greg Chesson wrote: > > >0x0168c:0013 should definitely work. > >You ordered the notebook with a factory-installed miniPCI? > > > >Can't tell exactly from your email what went wrong, but the device driver > >does support all production Atheros chipset combinations. I also have a Fujitsu laptop, but a different model: the P5020D. It also has a chip idenfiying itself as 168c:0013, which does not work. Up until recently, I got the HAL error 13 as well, but as of about 2 weeks ago, I get a different message: ath_hal: module license 'Proprietary' taints kernel. ath_hal: 0.9.6.3 wlan: 0.7.2.0 BETA ath_pci: 0.8.4.0 BETA ath%d: unable to collect channel list from hal I get this same message whether the antenna switch is on or off. This is with the very latest from the anon-CVS - I just tested. Sam Leffler said something about sending me a debug version of the HAL to try to figure out what happened, but I haven't heard back from him on that yet. -- michael |
From: Nirmal G. <ni...@ps...> - 2003-12-22 08:29:48
|
> ath%d: unable to collect channel list from hal > > I get this same message whether the antenna switch is on or off. This is > with the very latest from the anon-CVS - I just tested. Oh I just saw this - guess we're both at the same stage now... hopefully the debug version solves it. nirmal |