kern/98162: [feature request] AcerHK driver port needed for
enabling WiFi on Acer's laptops
AT Matik
asstec at matik.com.br
Sun Jun 4 13:15:50 PDT 2006
On Saturday 03 June 2006 16:00, Mark Linimon wrote:
> Old Synopsis: AcerHK driver port needed for enabling WiFi on Acer's laptops
> New Synopsis: [feature request] AcerHK driver port needed for enabling WiFi
> on Acer's laptops
>
> State-Changed-From-To: open->suspended
> State-Changed-By: linimon
> State-Changed-When: Sat Jun 3 18:59:13 UTC 2006
> State-Changed-Why:
> 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?
>
Hi
I am not so sure if this problem is well expressed. I reported this before but
the PR did not found so much attention.
Anyway, what William said is not exactly correct. May be this helps:
There is no software enabling of the WL card or the driver.
Acer NBs do have a button which en|disable the internal antena *and* switch
the buttom LED on or off. This LED is blinking when not associated to an AP
and stays lid when connected (carrier indication)
The Acer Broadcom WL Driver works very good with NDIS.
Now. Until 6.0-Beta5 the LED on the button still worked fine. Soon the ndis
driver was kldloaded the LED blinked and was ON when had carrier.
Since then the LED is dead but the hardware is fully functional and the antena
still can be en|disabled by pressing the WL-Button on the frontside.
Like I understand the Linux AcerHK project they like to load|unload the driver
by pressing the button what BTW on my Fedora 4 and 5 does also still do not
work. But this is an aditional feature what windows also do not do, the
button simply en|disables the antena by default.
To get the LED on|off|blinking is a very nice feature to see if the driver is
loaded or has carrier.
Since 6.1-Pre another "bad" issue came up, that when the NB crashes then the
antena do not get enabled by default (even by kldload/unload the driver) and
need some fiddeling with the WL-button and ifconfig up|down to get it up to
work again.
On my NB (aspire 3000) I can check the key codes with
214 WLbutton off
213 WLbutton on
which I can associate with `ifconfig ndis0 up|down` in order to disconnect or
reconnect.
I believe the bluetooth interface is not working at all under FreeBSD and
Linux but I didn't tried it.
João
A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br
More information about the freebsd-bugs
mailing list