On Mon, 2008-02-18 at 18:37 +0530, dell core2duo wrote:
> 
> 
> On Feb 18, 2008 5:59 PM, Iain Buchanan <[EMAIL PROTECTED]> wrote:
>         
>         
>         On Fri, 2008-02-15 at 23:31 +0530, dell core2duo wrote:
>         >
>         >
>         > On Fri, Feb 15, 2008 at 7:28 PM, Iain Buchanan
>         > <[EMAIL PROTECTED]> wrote:
>         >
>         >         On Sat, 2008-02-09 at 15:47 -0600, Dan Farrell wrote:
>         >         > On Sat, 9 Feb 2008 13:28:39 +0100
>         >         > Etaoin Shrdlu <[EMAIL PROTECTED]> 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.
>         
>         
>         Oh, I thought you meant ndis with 2.4.26.
> 
> I mean kernel 2.6.24 !! 

Whoops, that's what I meant I thought you meant :S


>         > did you tried kernel b43 module ??  Read below links, these may help
>         > you.
>         
>         
>         I use b44 for my eth0 (always have).  The problem with ndiswrapper was
>         that b44 was grabbing wlan0 before ndis could.  I couldn't ping over 
> the
>         wlan so I assumed b44 didn't work, but I was just playing around with
>         routes, and I have managed to get both eth0 and wlan0 working with b44
>         together (no ndis).
>         
>         If you understood that sentence, congratulations!
> 
> I understand little bit not fully. I didn't get how you managed
> without b43 module ? would be great if you could explain that.

OK, I made a mistake there too.  b44 I use for eth0, *b43* was grabbing
wlan0 before ndiswrapper could.

I tried playing with b43 and the cutter tool, but it didn't work as I
mentioned before.

I had to use the old bcm43xx module.  There were some kernel options to
change, and a different cutter tool.  I followed the instructions here:
http://gentoo-wiki.com/HARDWARE_BCM43xx

cya,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

Perl is designed to give you several ways to do anything, so
consider picking the most readable one.
             -- Larry Wall in the perl man page

-- 
gentoo-user@lists.gentoo.org mailing list

Reply via email to