Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    HELP: ath0: unable to attach hardware; HAL status 7

    Wireless
    6
    9
    5.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      rneily
      last edited by

      Anyone know whats going on here?  I found this in dmesg on a previously working wireless WRAP setup using a CM9 Card:

      ath_hal: 0.9.16.16 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
      ath0: <atheros 5212="">mem 0x80000000-0x8000ffff irq 12 at device 13.0 on pci0
      ath0: unable to attach hardware; HAL status 7
      device_attach: ath0 attach returned 6

      The box was humming along beautifully, and now it's hosed.  I cant get wireless working at all???  Everything else is fine.  I also downloaded RC2 in case it was my RC1 compact flash had gotten corrupted for some reason.</atheros>

      1 Reply Last reply Reply Quote 0
      • S
        sullrich
        last edited by

        Thats very strange.  I would say it may be hardware related.

        Perhaps LSF knows, I believe he has access to the the ATH code?

        1 Reply Last reply Reply Quote 0
        • R
          rneily
          last edited by

          Yah, not sure what happened. I think we might of had a storm tonight where the box was located. It migt be possible that the card has been zapped, although everything else seems fine on the box.

          1 Reply Last reply Reply Quote 0
          • L
            lsf
            last edited by

            I'm 99% sure that you fried your card or your mini.pci slot.

            There is no other reason this would happen. exchange the card and pray you mini-pci slot survived ;-)

            -lsf

            1 Reply Last reply Reply Quote 0
            • G
              gilf
              last edited by

              @rneily:

              Anyone know whats going on here?  I found this in dmesg on a previously working wireless WRAP setup using a CM9 Card:

              ath_hal: 0.9.16.16 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
              ath0: <atheros 5212="">mem 0x80000000-0x8000ffff irq 12 at device 13.0 on pci0
              ath0: unable to attach hardware; HAL status 7
              device_attach: ath0 attach returned 6

              The box was humming along beautifully, and now it's hosed.  I cant get wireless working at all???  Everything else is fine.  I also downloaded RC2 in case it was my RC1 compact flash had gotten corrupted for some reason.</atheros>

              Some wrap bios had issues detecting the wireless card on first boot. It would work on a warm boot. This was fixed in current warp bios.

              Gil

              1 Reply Last reply Reply Quote 0
              • D
                dracunciliasis
                last edited by

                @gilf:

                @rneily:

                Anyone know whats going on here?  I found this in dmesg on a previously working wireless WRAP setup using a CM9 Card:

                ath_hal: 0.9.16.16 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
                ath0: <atheros 5212="">mem 0x80000000-0x8000ffff irq 12 at device 13.0 on pci0
                ath0: unable to attach hardware; HAL status 7
                device_attach: ath0 attach returned 6

                The box was humming along beautifully, and now it's hosed.  I cant get wireless working at all???  Everything else is fine.  I also downloaded RC2 in case it was my RC1 compact flash had gotten corrupted for some reason.</atheros>

                Some wrap bios had issues detecting the wireless card on first boot. It would work on a warm boot. This was fixed in current warp bios.

                Gil

                Well I had the same problem and it wasn’t a wrap, it was a ASUS P4S800D-X 655 motherboard with 3 mini-PCI atheros, the solution was to test several pci slots randomly changing the place of the mini-PCI until it detected all radios.

                1 Reply Last reply Reply Quote 0
                • Z
                  ZGamer
                  last edited by

                  @dracunciliasis:

                  Well I had the same problem and it wasn’t a wrap, it was a ASUS P4S800D-X 655 motherboard with 3 mini-PCI atheros, the solution was to test several pci slots randomly changing the place of the mini-PCI until it detected all radios.

                  IRQ or P-IRQ problems.

                  –------------------------------------------------------------------------------------
                  pfSense Documentation Wiki
                  Need Commercial Support?
                  Personal Blog

                  1 Reply Last reply Reply Quote 0
                  • D
                    dracunciliasis
                    last edited by

                    @ZGamer:

                    @dracunciliasis:

                    Well I had the same problem and it wasn’t a wrap, it was a ASUS P4S800D-X 655 motherboard with 3 mini-PCI atheros, the solution was to test several pci slots randomly changing the place of the mini-PCI until it detected all radios.

                    IRQ or P-IRQ problems.

                    Well it wasnt an IRQ problem since on boot they had different IRQ's.
                    Whats P-IRQ??

                    1 Reply Last reply Reply Quote 0
                    • Z
                      ZGamer
                      last edited by

                      nevermind about the P-IRQ, your using a WRAP setup…....P-IRQ is the prioity IRQ assignments....can get this problem with atx PIII/Socket A motherboards which use PC133 memory. Only found this problem in a 5 PCI slot asus board with using 3 pci cards + agp card....needed to shuffle the cards around as they had a P-IRQ conflict causing the above problem.

                      –------------------------------------------------------------------------------------
                      pfSense Documentation Wiki
                      Need Commercial Support?
                      Personal Blog

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post
                      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.