Bug 98162 - [new driver] [request] AcerHK driver port needed for enabling WiFi on Acer's laptops
Summary: [new driver] [request] AcerHK driver port needed for enabling WiFi on Acer's ...
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 6.1-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: Adrian Chadd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-30 19:30 UTC by William Anderle
Modified: 2018-05-28 19:47 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description William Anderle 2006-05-30 19:30:14 UTC
On Acer laptops, we need a special driver to "software enable" some
peripherals like WiFi and Bluetooth, otherwise the peripheral won't work
even if the correct driver is loaded and recognizes it.

For better understanding, I copy here a part of AcerHK documentation:

"Q: I know that wireless hardware is supported on my Aspire
1690/TravelMate4600, but I cannot get it to work, why?

A: On these model (and similar) the wireless hardware is controlled on two
different levels. One is controlled by acerhk's xxxled file, the other level
is controlled by the key itself. To actually activate the hardware you need to
write '1' to the xxled file and you need to press the corresponding button.
Example:
echo 1 > /proc/driver/acerhk/wirelessled
<if still not working, press Wlan button>"

Fix: 

The problem is already fixed on Linux on i386 and AMD64 platforms through
the following drivers:
AcerHK for i386
http://www.informatik.hu-berlin.de/~tauber/acerhk/
Acer_Acpi for AMD64
http://www.archernar.co.uk/acer_acpi/acer_acpi_main.html
How-To-Repeat: The problem can be repeated on any recent Acer's laptop.
Comment 1 WillyTP 2006-05-31 01:00:40 UTC
As far as I know, FreeBSD's kernels seems to lack the feature of 
enabling-disabling wireless radio.
I think this bug is connected with i386/94141
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2006-06-03 19:59:13 UTC
State Changed
From-To: open->suspended

Mark this as a feature request and suspend it awaiting a patch from an 
interested party. 

To submitter: have you tried running the Windows drivers under the 
NDISulator?
Comment 3 WillyTP 2006-06-04 02:37:15 UTC
Hi, actually I haven't tried with NDISulator, but I don't think it will 
help.
Even in Windows, for enabling/disabling WiFi radio we have to install a 
program from Acer, called "Launch Manager".
Under FreeBSD, I tried this trick for making WiFi driver (in my case, 
if_ath) working:
1)Launch Linux
2)Enable wireless radio through AcerHK driver (echo 1 > 
/proc/driver/acerhk/wirelessled)
3)*Soft* reboot into FreeBSD
If WiFi configuration is correct, it will work as it should be.

For discovering if the WiFi radio is actually on, I followed this procedure:
1)AP turned on
2)Run this command:

ifconfig ath0 list ap

If nothing is shown, WLAN hardware is disabled.
Next days I'll try with NDISulator and report.
Comment 4 William Anderle 2006-06-06 14:03:06 UTC
Even with NDISulator I think it won't work.
Here is it a little HowTo from Gentoo Linux:

http://gentoo-wiki.com/HARDWARE_Acer_Aspire_5024#WiFi

Even with NDISWrapper, acerhk / acer_acpi are always needed for enabling 
wireless hardware.
I just hope some developer will make a port for FreeBSD.
Best regards
Comment 5 artur 2006-08-23 22:29:55 UTC
The same thing is neccessery with Fujitsu-Siemens AMILO A1650G Turion64
same driver - acer_acpi is needed for enabling atheros chipset
So for now i cant use bsd on my laptop with network.

regards Artur
Comment 6 Adrian Chadd freebsd_committer freebsd_triage 2011-10-23 16:51:39 UTC
Responsible Changed
From-To: freebsd-bugs->adrian

I'll take a crack at this; I have some relevant hardware.
Comment 7 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:47:35 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.