From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JR5ix-0000sb-2H for garchives@archives.gentoo.org; Mon, 18 Feb 2008 13:07:59 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C732DE013E; Mon, 18 Feb 2008 13:07:57 +0000 (UTC) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by pigeon.gentoo.org (Postfix) with ESMTP id 819F4E013E for ; Mon, 18 Feb 2008 13:07:57 +0000 (UTC) Received: by wa-out-1112.google.com with SMTP id k34so3056625wah.10 for ; Mon, 18 Feb 2008 05:07:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=gCi53ptD9DyjHji+iaEMM99AquP+KZhOiPrEx7j6Lxg=; b=o5S7OLcxmvuWeii9g/Yqh8phJqcB+O8O70SnLTxr6N0ntqZX2Qpf7qZvBOfspABcrIkdf2nzLGlSCzY30f90Y2tkUn3mGOS2sFu4ZBhmQSi7fHxBUa3gZJJcVUhKb+GQacUI0zCp00mY5tvdU3I24VKQc56UTmwCUUUo5bfm5iI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=n6+qjY1xOXxwj0NKjS1ODE6CG/l5nYKLtgVwq0Pv5oRXvZgAYDiJLdre0Xw0C6hXRiv9NZMBOqjbOmkuKp9n7Um9AdJ67kSkWtbE0V9iTA+pPpLA1QwqyR/4FhcltEd+NhRy+VbPKVWUSj6w+7sV92UbFDqFAwJuxD9NsgJhDYo= Received: by 10.115.88.1 with SMTP id q1mr2979282wal.64.1203340077078; Mon, 18 Feb 2008 05:07:57 -0800 (PST) Received: by 10.115.109.11 with HTTP; Mon, 18 Feb 2008 05:07:57 -0800 (PST) Message-ID: Date: Mon, 18 Feb 2008 18:37:57 +0530 From: "dell core2duo" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper In-Reply-To: <1203337798.25888.79.camel@orpheus> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_15611_32393403.1203340077070" References: <200802091312.40836.shrdlu@unlimitedmail.org> <200802091328.39793.shrdlu@unlimitedmail.org> <20080209154720.450dc857@pascal.spore.ath.cx> <1203083881.15472.1.camel@orpheus> <1203337798.25888.79.camel@orpheus> X-Archives-Salt: ea23db18-7381-4c21-8532-39288305d22a X-Archives-Hash: d7124f76113e4b084ee9724311798fbd ------=_Part_15611_32393403.1203340077070 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Feb 18, 2008 5:59 PM, Iain Buchanan wrote: > > On Fri, 2008-02-15 at 23:31 +0530, dell core2duo wrote: > > > > > > On Fri, Feb 15, 2008 at 7:28 PM, Iain Buchanan > > wrote: > > > > On Sat, 2008-02-09 at 15:47 -0600, Dan Farrell wrote: > > > On Sat, 9 Feb 2008 13:28:39 +0100 > > > Etaoin Shrdlu 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 !! > > > > 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. thanks, flukebox > so no more ndis it seems! > > thanks, > -- > Iain Buchanan > > An engineer is someone who does list processing in FORTRAN. > > -- > gentoo-user@lists.gentoo.org mailing list > > ------=_Part_15611_32393403.1203340077070 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On Feb 18, 2008 5:59 PM, Iain Buchanan <iaindb@netspace.net.au> wrote:

On Fri, 2008-02-15 at 23:31 +0530, dell core2duo wrote:
>
>
> 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.

Oh, I thought you meant ndis with 2.4.26.

I mean kernel 2.6.24 !!
 


> 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.

thanks,
flukebox




so no more ndis it seems!

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

An engineer is someone who does list processing in FORTRAN.

--

------=_Part_15611_32393403.1203340077070-- -- gentoo-user@lists.gentoo.org mailing list