public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "dell core2duo" <gentoomail.dell@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper
Date: Fri, 15 Feb 2008 23:31:22 +0530	[thread overview]
Message-ID: <e5e065050802151001t2cf10b89wc9a2a7948e09b973@mail.gmail.com> (raw)
In-Reply-To: <1203083881.15472.1.camel@orpheus>

[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]

On Fri, Feb 15, 2008 at 7:28 PM, Iain Buchanan <iaindb@netspace.net.au>
wrote:

>
> On Sat, 2008-02-09 at 15:47 -0600, Dan Farrell wrote:
> > On Sat, 9 Feb 2008 13:28:39 +0100
> > Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:
> >
> > > > BTW,
> > > >   I am more interested to get things working. Quality would be my
> > > > second priority.
> > >
> > > As I said before, I did not have any problem (unfortunately, I cannot
> > > access the hardware now and check the bandwidth issue).
> >
> > I have not yet gotten the new driver to work, though admittedly I
> > didn't have much time to try and so went for ndiswrapper pretty
> > quickly.
>
> how did you get ndiswrapper to work?  It worked for me for 2.6.23, but
> not for 2.6.24.  I have a BCM4306 and I'm having some trouble getting
> the kernel driver to work, so I'd like to use ndiswrapper in the mean
> time.
>

I guess there are some problems with ndiswrapper on kernel-2.4.26.  I didn't
get ndiswraper worked with kernel-2.4.26.
did you tried kernel b43 module ??  Read below links, these may help you.

http://gentoo-wiki.com/HARDWARE_BCM43xx
http://linuxwireless.org/en/users/Drivers/b43?action=show&redirect=en%2Fusers%2FDrivers%2Fbcm43xx

regards,
flukebox





>
> When I load ndiswrapper (yes I've rebuilt it :) I get no wlan0 like I
> used to.
>
> thanks,
> --
> Iain Buchanan <iaindb at netspace dot net dot au>
>
> Wash: "Oh my god, it's grotesque! Oh, and there's something in a jar."
>                                --Episode #12, "The Message"
>
> --
> gentoo-user@lists.gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 2685 bytes --]

  reply	other threads:[~2008-02-15 18:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09 11:17 [gentoo-user] [query] kernel-2.6.24 + ndiswrapper dell core2duo
2008-02-09 11:32 ` Ian Lee
2008-02-09 11:37   ` dell core2duo
2008-02-09 11:54 ` Etaoin Shrdlu
2008-02-09 11:40   ` dell core2duo
2008-02-09 12:12     ` Etaoin Shrdlu
2008-02-09 12:02       ` dell core2duo
2008-02-09 12:28         ` Etaoin Shrdlu
2008-02-09 21:47           ` Dan Farrell
2008-02-12 17:08             ` dell core2duo
2008-02-12 18:57               ` dell core2duo
2008-02-12 23:11                 ` Etaoin Shrdlu
2008-02-13 21:28                   ` dell core2duo
2008-02-13 22:18                     ` Etaoin Shrdlu
2008-02-13 22:37                       ` dell core2duo
2008-02-13 22:47                     ` Etaoin Shrdlu
2008-02-15 13:58             ` Iain Buchanan
2008-02-15 18:01               ` dell core2duo [this message]
2008-02-18 12:29                 ` Iain Buchanan
2008-02-18 13:07                   ` dell core2duo
2008-02-19  1:05                     ` Iain Buchanan

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=e5e065050802151001t2cf10b89wc9a2a7948e09b973@mail.gmail.com \
    --to=gentoomail.dell@gmail.com \
    --cc=gentoo-user@lists.gentoo.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