| 1 |
One of the problems I had with ndiswrapper is that it would just suck 100% |
| 2 |
of the CPU and literally do nothing. iwlist scan would show nothing. |
| 3 |
|
| 4 |
I just tried bcm43xx and it worked, so I never tried to get ndiswrapper |
| 5 |
back |
| 6 |
|
| 7 |
On Sat, 6 Oct 2007, Beso wrote: |
| 8 |
|
| 9 |
> Date: Sat, 6 Oct 2007 16:08:04 +0200 |
| 10 |
> From: Beso <givemesugarr@×××××.com> |
| 11 |
> Reply-To: gentoo-amd64@l.g.o |
| 12 |
> To: gentoo-amd64@l.g.o |
| 13 |
> Subject: Re: [gentoo-amd64] latest kernel and ndiswrapper |
| 14 |
> |
| 15 |
> 1. if you don't have a 4318 and you won't need to connect to wpa_enterprise |
| 16 |
> networks with ca certs and so on switch to the kernel drivers. are a lot |
| 17 |
> better than ndiswrapper. the only things that fails is the 4318 module when |
| 18 |
> trying to connect to a wpa_enterprise network that don't broadcast essid, |
| 19 |
> cause it has some flux control that is not ok. it connects but you'd risk |
| 20 |
> disconection and core failures that would have you to restart the system. |
| 21 |
> all the other boards, for what i know work pretty well and with 54mbit/s |
| 22 |
> speeds. |
| 23 |
> 2. ndiswrapper was rebuilt pointing to /usr/srclinux which now pointed to |
| 24 |
> r8. now, the modules should be ok, since you've already build and installed |
| 25 |
> them, but you may have to rebuild ndiswrapper after pointing /usr/src/linux |
| 26 |
> to the r5. i don't know if that would fix your issue, since you didn't |
| 27 |
> provided any log or dmesg message to see what really happens when |
| 28 |
> ndiswrapper loads. so first of all try "dmesg > /root/dmesg.txt-r5 && cat |
| 29 |
> /var/log/messages > /root/messages-r5.txt" and "dmesg > /root/dmesg.txt-r8 |
| 30 |
> && cat /var/log/messages > /root/messages-r8.txt" after booting with r5 and |
| 31 |
> respectively r8 and attach them to see what happens. |
| 32 |
> 3. how did you compiled the new r8? have you made a "cp /usr/src/linux- |
| 33 |
> 2.6.22-gentoo-r5/.config /usr/src/linux" to copy the old config from the r5 |
| 34 |
> to r8 or did you configured the r8 by hand again? |
| 35 |
> 4. switch to bcm43xx since it is always better using native drivers than |
| 36 |
> wrappers when you can. you should at least try them and see how they behave |
| 37 |
> before saying that they don't work. compiling them don't cost you nothing. |
| 38 |
> then you can blacklist them from loading so you can use ndiswrapper if you |
| 39 |
> don't like them. |
| 40 |
> |
| 41 |
> 2007/10/6, Mark Haney <mhaney@××××××××××××.org>: |
| 42 |
>> |
| 43 |
>> I just upgraded to 2.6.22-r8 and when I booted into it (after |
| 44 |
>> re-emerging ndiswrapper) I got a hardware error saying it couldn't set |
| 45 |
>> the device up (wlan0). I figured something was flaky with ndiswrapper, |
| 46 |
>> so I booted back into -r5 and tried loading my wireless again and I got |
| 47 |
>> the same error. I've been consistently using my wireless under this |
| 48 |
>> kernel for weeks and not had a problem. Is this an ndiswrapper issue? |
| 49 |
>> Or a kernel issue with -r8 that's screwed up my wireless? |
| 50 |
>> |
| 51 |
>> I know most of you aren't fans of ndiswrapper, but it's been absolutely |
| 52 |
>> rock solid for me and I won't change to the new mac drivers for my |
| 53 |
>> broadcom card until I have to. |
| 54 |
>> |
| 55 |
>> -- |
| 56 |
>> Mark Haney |
| 57 |
>> Sr. Systems Administrator |
| 58 |
>> ERC Broadband |
| 59 |
>> |
| 60 |
>> |
| 61 |
>> -- |
| 62 |
>> gentoo-amd64@g.o mailing list |
| 63 |
>> |
| 64 |
>> |
| 65 |
> |
| 66 |
> |
| 67 |
> |
| 68 |
-- |
| 69 |
gentoo-amd64@g.o mailing list |
Archives