im having trouble extracting the files from a batch because i need the wifi to work, even though i have wget and zip installed.
1 Like
What WiFi hardware do you have? As mentioned in the User Guide, this script is not needed unless you have some extremely old WiFi hardware; otherwise, the firmwares are bundled.
2 Likes
Once you have confirmed that your hardware indeed needs this script, the next step is to follow the instructions printed by the script: you need to download and install wget.exe and zip.exe from the provided links, and make sure the script can find them (probably by adding them to the PATH on your Windows machine).
2 Likes
an Acer aspire 4520g
That’s the model of your laptop, not the model of WiFi.
Google searches seem to indicate it has an Atheros card. This will not be helped by installing these additional WiFi firmwares; the problem lies elsewhere.
1 Like
Yes, there may be some problem that prevented the driver from starting, or perhaps it does not support your specific hardware. Check the syslog.
2 Likes
https://drive.google.com/file/d/1olGhX1UGilARPOzb5zR14Rfv9cv5WKxO/view?usp=drive_link try checking the syslog, i dont understand it
I can’t access this file.
Thanks. The relevant lines are:
KERN: pci_reserve_device(4, 0, 0, atheroswifi)
KERN: [atheroswifi] (ath) bus_alloc_resource(3, [16], 0x0, 0xffffffffffffffff, 0x1,0x2)
KERN: [atheroswifi] (ath) bus_alloc_resource(1, [0], 0x0, 0xffffffffffffffff, 0x1,0x6)
KERN: [atheroswifi] (ath) unable to attach hardware; HAL status 3
KERN: pci_unreserve_device(4, 0, 0, atheroswifi)
This looks like #14521 which was closed a while back due to lack of replies. Seems it’s not fixed, after all.
[dom 0, bus 4] bus 4, device 0, function 0: vendor 168c, device 001c, revision 01
KERN: PCI: class_base 02, class_function 00, class_api 00
KERN: PCI: vendor 168c: Qualcomm Atheros
KERN: PCI: device 001c: AR242x / AR542x Wireless Network Adapter (PCI-Express) (AR5BXB63 802.11bg NIC)
KERN: PCI: info: Network controller (Ethernet controller)
KERN: PCI: line_size 10, latency 00, header_type 00, BIST 00
KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000
KERN: PCI: cardbus_CIS 00005001, subsystem_id 0428, subsystem_vendor_id 1468
KERN: PCI: interrupt_line 0b, interrupt_pin 01, min_grant 00, max_latency 00
KERN: PCI: base reg 0: host 00000000f0200000, pci 00000000f0200000, size 00010000, flags 04 00
KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI: Capabilities: PM, MSI, PCIe, MSI-X
KERN: PCI: Extended capabilities: Advanced Error Reporting, Virtual Channel
That is what is in their syslog…
KERN: PCI: cardbus_CIS 00005001, subsystem_id 0428, subsystem_vendor_id 1468
Does this mean it is actually a CardBus device? Or is just extraneous data here? Searching for the device id/name turns up mini-PCIe cards?
Looks like the Atheros AR5BXB63 might have worked for someone at one point (according to an entry from this compatibility list → Haiku Hardware Database )
247 | Aspire R3600 | Acer | Intel Atom 1,60 GHz | 2 GB | no | Atheros AR5BXB63 | 51795
Entry, Name, Manufacturer, Processor, Memory (qty), vesa, Wireless Card, Haiku hrev
Does the “HAL status 3” (HAL_EIO; Hardware didn’t respond as expected) actually indicate anything useful about whether the hardware is supported/not supported or is it just some sort of generic IO Error?
Bit of a tangent here, but it would probably be helpful if better information was available on supported/unsupported hardware.
https://dev.haiku-os.org/wiki/HardwareInfo
https://dev.haiku-os.org/wiki/HardwareInfo/FreeBSD_Wlan
The above pages appear to be out of date, first (2 years ago) and second (11 years ago?!)
This site → Haiku Hardware Database (at hardware.besly.de) is probably a better place to look, although it’s not perfect.
I realize that it’s not exactly a high priority to update the wiki, but it does seem a bit misleading for the second page to say, under the section for atheros, that “This driver supports all Atheros PCI cards, except those that are based on the AR5005VL chipset” – especially considering the last time that page was modified…
the laptop is an acer aspire 4520g, not an r3600
it worked fine with windows 7 and kde neon
I agree, that sounds like something OP (@Lcaser) should try.
https://www.freebsd.org/releases/12.0R/hardware/#support
" The ath(4) driver supports all Atheros Cardbus and PCI cards, except those that are based on the AR5005VL chipset."
https://man.freebsd.org/cgi/man.cgi?query=ath&sektion=4&format=html
Some web sources list the AR5BXB63 along with the identifier AR5007EG. The FreeBSD 12.0-release hardware support llinks to the man page for ath(4), which says
The ath driver provides support for wireless network adapters based on
the Atheros AR5210, AR5211, AR5212, AR5416 and AR9300 programming APIs.
These APIs are used by a wide variety of chips; most all chips with a
PCI, PCIe and/or CardBus interface are supported.
https://man.freebsd.org/cgi/man.cgi?query=ath_hal&sektion=4&apropos=0&manpath=FreeBSD+12.0-RELEASE+and+Ports
The manual page ath_hal(4) list a slightly more extensive set of devices that are presumably supported by the APIs noted above.
I mentioned the entry for an Acer Aspire R3600 because it would seem to have the same wireless card. So if it worked for the person that submitted that entry to the list for hrev 51795 then it should probably still work okay…
P.S.
The answer given on this thread from 2015 indicates that it should have worked under Linux at the time, with the ath5k kernel module.
theres the lines of
KERN: pci_reserve_device(4, 0, 0, atheroswifi)
KERN: [atheroswifi] (ath) bus_alloc_resource(3, [16], 0x0, 0xffffffffffffffff, 0x1,0x2)
KERN: [atheroswifi] (ath) bus_alloc_resource(1, [0], 0x0, 0xffffffffffffffff, 0x1,0x6)
KERN: [atheroswifi] (ath) unable to attach hardware; HAL status 3
KERN: pci_unreserve_device(4, 0, 0, atheroswifi)
does it seem off?