#713: HAL status 13 on 168c/001c device
-------------------------------------+--------------------------------------
      Reporter:  [EMAIL PROTECTED]  |       Owner:                         
          Type:  defect              |      Status:  new                    
      Priority:  major               |   Milestone:                         
     Component:  madwifi: other      |     Version:  trunk                  
    Resolution:                      |    Keywords:  hal status 13 068c 001c
Patch_attached:  0                   |  
-------------------------------------+--------------------------------------
Comment (by [EMAIL PROTECTED]):

 I have the same problem here, on a BenQ Joybook T31E:

 {{{
 0000:08:00.0 Ethernet controller: Atheros Communications, Inc.: Unknown
 device 001c (rev 01)
         Subsystem: Unknown device 1a32:0100
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
 ParErr- Stepping- SERR- FastB2B-
         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
 <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0, Cache Line Size: 0x08 (32 bytes)
         Interrupt: pin A routed to IRQ 10
         Region 0: Memory at d0300000 (64-bit, non-prefetchable) [size=64K]
         Capabilities: [40] Power Management version 2
                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
 PME(D0-,D1-,D2-,D3hot-,D3cold-)
                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
         Capabilities: [50] Message Signalled Interrupts: 64bit- Queue=0/0
 Enable-
                 Address: 00000000  Data: 0000
         Capabilities: [60] #10 [0011]
         Capabilities: [90] #11 [0000]
 }}}

 as well as on a BenQ Joybook P41E: 168c:001c (Atheros:001c), subsystem ID
 144f:7108 (Askey:7108).

 I see that madwifi/hal/ah_devid.h has this defined:

 {{{
 #define AR5212_AR5424          0x001c          /* Condor (PCI express) */
 }}}

 But when trying to use ath_pci and ath_hal (as of 0.9.17.2), we see the
 same error:

  wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL
 status 13)

 This appear to be different from Ticket #370, and the WiFi is indeed
 turned on when I attempted to load the driver.  My friend was able to load
 ndiswrapper with the Windows driver and get it to work, but of course,
 getting the native Linux driver to work is best.  :-)

 Is it a known issue in the 0.9.17.2 binary Atheros HAL code?  Is there any
 other information I could provide?

 Thanks in advance!

 Yours sincerely,

 Anthony

-- 
Ticket URL: <http://madwifi.org/ticket/713>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets

Reply via email to