From: "Mihai Donțu" <mihai.dontu@gmail.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ndiswrapper 1.54-2.6.27 released
Date: Thu, 27 Nov 2008 14:40:15 +0200 [thread overview]
Message-ID: <200811271440.15661.mihai.dontu@gmail.com> (raw)
In-Reply-To: <492DE3BD.9010802@shaw.ca>
On Thursday 27 November 2008, Robert Hancock wrote:
> jmerkey@wolfmountaingroup.com wrote:
> > ndiswrapper with the 2.6.27 breakage corrected. The current maintainers
> > have not put out a release for 2.6.27 or later kernels, so I went ahead
> > and fixed it for 2.6.27.
> >
> > ftp://ftp.wolfmountaingroup.org/pub/ndiswrapper/ndiswrapper-1.54-2.6.27.7
> >.tar.gz
> >
> > Linux wireless drivers still do not work on most of my laptops and USB
> > wireless devices due to lack of firmware drivers and other problems with
> > native Linux wireless. Anyone else with busted laptop wireless who need
> > ndiswrapper might as well be able to get it since the maintainers have
> > not posted recent releases for recent kernels.
>
> What devices are there left these days that are still not working with
> native drivers?
Broadcom Corporation BCM4312 802.11a/b/g (rev 01)
The driver works only if I don't subject it to high traffic. If I begin a
large transfer (like a DVD ISO) the card looses the connection with the AP
and behaves erratically in a way that interferes with my wireless mouse (I
have to unplug the mouse receiver and plug it back in several times, which is
very annoying).
--
Mihai Donțu
prev parent reply other threads:[~2008-11-27 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 6:02 ndiswrapper 1.54-2.6.27 released jmerkey
2008-11-26 7:13 ` Justin P. Mattock
2008-11-26 7:53 ` jmerkey
2008-11-26 8:52 ` Justin P. Mattock
2008-11-27 0:03 ` Robert Hancock
2008-11-27 12:40 ` Mihai Donțu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200811271440.15661.mihai.dontu@gmail.com \
--to=mihai.dontu@gmail.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox