Thanks for that helpful info.

Now maybe I should just wait,
(until there is a native driver I can
 use with Ubuntu 6.06)
partly since I have another laptop
PC (running - ahem - another OS)
issued to me by my employer,
(on Sept. 18, 2006 -
  when I started my new job),
and the [internal] wifi there, seems OK.

>> [...]  Perhaps in a few months a native driver will work.

that would be great.
Thanks,
-- 
Mike Schwartz
Glendale  AZ
schwartz@acm.org
Mike.L.Schwartz@gmail.com

On 10/3/06, Joseph Sinclair <plug-discussion@stcaz.net> wrote:
>
> The Broadcom 4318 has a severely reduced transmit power as a means of
> reducing power consumption.  What this means is that under Linux it's
> connection to the access point tends to be limited (NDISWrapper works, but
> it will still have issues, the kernel.org driver can only listen at this
> time).  The BCM driver team is working on a fix to the kernel.org driver
> to get the Tx power issue fixed, until then, you'll have to use NDISWrapper,
> and accept that connectivity won't be too reliable.
>
> ==Joseph++
>
> Eric "Shubes" wrote:
> > JT Moree wrote:
> >> Mike Schwartz wrote:
> >>
> >>> * Chipset: Broadcom Corporation BCM4318 802.11/g Wireless LAN
> >>> * pciid: 14e4:4318
> >> we dealt with that chipset at the last installfest.  It doesn't quite
> >> work with the built in kernel driver yet.  Ndiswrapper is your only
> >> solution for now.  Perhaps in a few months a native driver will work.
> >>
> > FWIW, to verify your chipset (they can and do vary w/in model/version
> numbers):
> > # lspci -n -v
> > will show you the pciid.
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change  you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>