[atheroswifi] (ath_pci) unable to attach hardware; HAL status 3

[LeapingFrog]

haiku-master-hrev52357-x86_gcc2_hybrid-anyboot

Failure in Setting up Atheros Wireless Network Adapter (WIFI on PC: FM V-Bibilo Loox U50X/V)

installed on PC (FM V-Bibilo Loox U50X/V) via USB
fails to set-up WIFI.
In the Terminal, I could not configure WIFI:
ifconfig does not detect WIFI.
However, listdev knows the device for WIFI.
In the syslog, an error is reported in the process of setting up atheroswifi .

~/documents/enter_Haiku> ls /dev/net
rtl8139
~/documents/enter_Haiku> ifconfig -a
loop    Hardware type: Local Loopback, Address: none
        inet addr: 127.0.0.1, Mask: 255.0.0.0
        inet6 addr: ::1, Prefix Length: 128
        MTU: 16384, Metric: 0, up loopback link
        Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
        Transmit: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
        Collisions: 0

/dev/net/rtl8139/0
        Hardware type: Ethernet, Address: 00:17:42:8a:ec:78
        inet addr: --, Bcast: --, Mask: --
        MTU: 1500, Metric: 0, up broadcast
        Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
        Transmit: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
        Collisions: 0

~/documents/enter_Haiku> listdev 
...
device Network controller (Ethernet controller) [2|0|0]
  vendor 10ec: Realtek Semiconductor Co., Ltd.
  device 8139: RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
...
device Network controller (Ethernet controller) [2|0|0]
  vendor 168c: Qualcomm Atheros
  device 001c: AR242x / AR542x Wireless Network Adapter (PCI-Express)
...

---

...
KERN: package_daemon [30308584:   337] Volume::InitialVerify(): volume at "/boot/home/config" is consistent
KERN: [atheroswifi] (ath_pci) bus_alloc_resource(3, [16], 0x0, 0xffffffff, 0x1,0x2)
KERN: add_memory_type_range(4011, 0xf0000000, 0x10000, 0)
KERN: set MTRRs to:
KERN:   mtrr:  0: base: 0x3f670000, size:    0x10000, type: 0
KERN:   mtrr:  1: base: 0x3f680000, size:    0x80000, type: 0
KERN:   mtrr:  2: base: 0xf0000000, size: 0x10000000, type: 0
KERN:   mtrr:  3: base: 0x80000000, size: 0x80000000, type: 1
KERN: [atheroswifi] (ath_pci) bus_alloc_resource(1, [0], 0x0, 0xffffffff, 0x1,0x6)
KERN: [atheroswifi] (ath_pci) unable to attach hardware; HAL status 3
KERN: remove_memory_type_range(4011, 0xf0000000, 0x10000, 0)
KERN: set MTRRs to:
KERN:   mtrr:  0: base: 0x3f670000, size:    0x10000, type: 0
KERN:   mtrr:  1: base: 0x3f680000, size:    0x80000, type: 0
KERN:   mtrr:  2: base: 0xf0000000, size: 0x10000000, type: 0
KERN:   mtrr:  3: base: 0x80000000, size: 0x80000000, type: 1
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/input/usb_hid
...

I verified the WIFI by rebooting Windows Vista.
Windows Vista detects WIFI and routers.
After that I rebooted to Haiku again.
Then, I collected the data and included in this bug-report.

[LeapingFrog]

I missed the entry "Platform". Should I put the machine's type in this entry?

[diver]

Please attach your full syslog.

[LeapingFrog]

I clean installed Haiku OS again and took syslog.

Process was: Booting from HD (ended up in black screen) --> rebooting from USB --> backing-up syslog --> rebooting from HD (with fail-safe-video-mode) --> copied syslog to USB.

WIFI is not functioning yet.

Syslog of first booting (witout fail-safe-video-mode)

[LeapingFrog]

Second Booting (with fail-safe-video-mode set in the booting process).

[LeapingFrog]

If it is sensible to create new ticket for "black screen after rocket is lit in the Haiku splash" on my machine, I will do it. Before that I will try to find some information in the forum. So, take these two syslogs as two examples of failure in setting up WIFI.

[LeapingFrog]

I take this opportunity of participating Haiku project. I admit I can assign only limited time to this project. On the other hand, I can manage 2 or may be 3 partitions of different revisions of Haiku. I can compare syslogs of those revisions with varying debugging options. Of course I can report the result.

[korli]

"attach" meant attach a syslog file to the ticket.

[LeapingFrog]

syslog of failure of wifi

[LeapingFrog]

another syslog of failure of wifi

[LeapingFrog]

Yes, I managed attach syslogs.

[michaelvoliveira]

BETA 1, same bug here

device Network Controller [ 2/80/0 ]
vendor 168c: Qualcomm Atheros
device 002e: AR9287 Wireless
Network Adapter (PCI-Express)

KERN: [atheroswifi] (ath_pci) bus_alloc_resource(3,[16],0x0,0xffffffffffffffff,0x1,0x2)
KERN: add_memory_type_range(10779,0xdfc00000,0x10000,0)
KERN: set MTRRs to:
(...)
KERN: [atheroswifi] (ath_pci) bus_alloc_resource(1,[0],0x0,0xffffffffffffffff,0x1,0x6)
KERN: [atheroswifi] (ath_pci) unable to attach hardware; HAL status 3
KERN: remove_memory_type_range(10779,0xdfc00000,0x10000,0)

the source is on the tree

[​​https://github.com/haiku/haiku/blob/master/src/add-ons/kernel/drivers/network/wlan/atheroswifi/dev/ath/ath_hal/ar9002/ar9287.ini]

[waddlesplash]

Does this device work on FreeBSD?

[waddlesplash]

Please retest after hrev52726.

[waddlesplash]

No replies.

[liss21]

Netbook Lenovo S10-3. No UEFI, just BIOS
Atheros AR9285 Wireless Adapter (AR5B95). In haiku-master-hrev54010-x86_gcc2h-anyboot, panic disappeared when a card was recognized.

However, the card did not start. But should it?

syslog and listdev in attachment. In native Windows 7 starter it works fine.

[korli]

Please check on a current nightly.

[waddlesplash]

Ping again; please retest under a recent nightly, it's possible the powerstate changes may have affected this.

[waddlesplash]

No replies, again.