| 1 |
On Mon, 2008-02-18 at 18:37 +0530, dell core2duo wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> On Feb 18, 2008 5:59 PM, Iain Buchanan <iaindb@××××××××××××.au> wrote: |
| 5 |
> |
| 6 |
> |
| 7 |
> On Fri, 2008-02-15 at 23:31 +0530, dell core2duo wrote: |
| 8 |
> > |
| 9 |
> > |
| 10 |
> > On Fri, Feb 15, 2008 at 7:28 PM, Iain Buchanan |
| 11 |
> > <iaindb@××××××××××××.au> wrote: |
| 12 |
> > |
| 13 |
> > On Sat, 2008-02-09 at 15:47 -0600, Dan Farrell wrote: |
| 14 |
> > > On Sat, 9 Feb 2008 13:28:39 +0100 |
| 15 |
> > > Etaoin Shrdlu <shrdlu@×××××××××××××.org> wrote: |
| 16 |
> > > |
| 17 |
> > > > > BTW, |
| 18 |
> > > > > I am more interested to get things working. Quality |
| 19 |
> > would be my |
| 20 |
> > > > > second priority. |
| 21 |
> > > > |
| 22 |
> > > > As I said before, I did not have any problem |
| 23 |
> > (unfortunately, I cannot |
| 24 |
> > > > access the hardware now and check the bandwidth issue). |
| 25 |
> > > |
| 26 |
> > > I have not yet gotten the new driver to work, though |
| 27 |
> > admittedly I |
| 28 |
> > > didn't have much time to try and so went for ndiswrapper |
| 29 |
> > pretty |
| 30 |
> > > quickly. |
| 31 |
> > |
| 32 |
> > |
| 33 |
> > how did you get ndiswrapper to work? It worked for me for |
| 34 |
> > 2.6.23, but |
| 35 |
> > not for 2.6.24. I have a BCM4306 and I'm having some trouble |
| 36 |
> > getting |
| 37 |
> > the kernel driver to work, so I'd like to use ndiswrapper in |
| 38 |
> > the mean |
| 39 |
> > time. |
| 40 |
> > |
| 41 |
> > I guess there are some problems with ndiswrapper on kernel-2.4.26. I |
| 42 |
> > didn't get ndiswraper worked with kernel-2.4.26. |
| 43 |
> |
| 44 |
> |
| 45 |
> Oh, I thought you meant ndis with 2.4.26. |
| 46 |
> |
| 47 |
> I mean kernel 2.6.24 !! |
| 48 |
|
| 49 |
Whoops, that's what I meant I thought you meant :S |
| 50 |
|
| 51 |
|
| 52 |
> > did you tried kernel b43 module ?? Read below links, these may help |
| 53 |
> > you. |
| 54 |
> |
| 55 |
> |
| 56 |
> I use b44 for my eth0 (always have). The problem with ndiswrapper was |
| 57 |
> that b44 was grabbing wlan0 before ndis could. I couldn't ping over the |
| 58 |
> wlan so I assumed b44 didn't work, but I was just playing around with |
| 59 |
> routes, and I have managed to get both eth0 and wlan0 working with b44 |
| 60 |
> together (no ndis). |
| 61 |
> |
| 62 |
> If you understood that sentence, congratulations! |
| 63 |
> |
| 64 |
> I understand little bit not fully. I didn't get how you managed |
| 65 |
> without b43 module ? would be great if you could explain that. |
| 66 |
|
| 67 |
OK, I made a mistake there too. b44 I use for eth0, *b43* was grabbing |
| 68 |
wlan0 before ndiswrapper could. |
| 69 |
|
| 70 |
I tried playing with b43 and the cutter tool, but it didn't work as I |
| 71 |
mentioned before. |
| 72 |
|
| 73 |
I had to use the old bcm43xx module. There were some kernel options to |
| 74 |
change, and a different cutter tool. I followed the instructions here: |
| 75 |
http://gentoo-wiki.com/HARDWARE_BCM43xx |
| 76 |
|
| 77 |
cya, |
| 78 |
-- |
| 79 |
Iain Buchanan <iaindb at netspace dot net dot au> |
| 80 |
|
| 81 |
Perl is designed to give you several ways to do anything, so |
| 82 |
consider picking the most readable one. |
| 83 |
-- Larry Wall in the perl man page |
| 84 |
|
| 85 |
-- |
| 86 |
gentoo-user@l.g.o mailing list |
Archives