Re: [gentoo-amd64] latest kernel and ndiswrapper

[Beso <givemesugarr@gmail.com>]

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

1. if you don't have a 4318 and you won't need to connect to wpa_enterprise
networks with ca certs and so on switch to the kernel drivers. are a lot
better than ndiswrapper. the only things that fails is the 4318 module when
trying to connect to a wpa_enterprise network that don't broadcast essid,
cause it has some flux control that is not ok. it connects but you'd risk
disconection and core failures that would have you to restart the system.
all the other boards, for what i know work pretty well and with 54mbit/s
speeds.
2. ndiswrapper was rebuilt pointing to /usr/srclinux which now pointed to
r8. now, the modules should be ok, since you've already build and installed
them, but you may have to rebuild ndiswrapper after pointing /usr/src/linux
to the r5. i don't know if that would fix your issue, since you didn't
provided any log or dmesg message to see what really happens when
ndiswrapper loads. so first of all try "dmesg > /root/dmesg.txt-r5 && cat
/var/log/messages > /root/messages-r5.txt" and "dmesg > /root/dmesg.txt-r8
&& cat /var/log/messages > /root/messages-r8.txt" after booting with r5 and
respectively r8 and attach them to see what happens.
3. how did you compiled the new r8? have you made a "cp /usr/src/linux-
2.6.22-gentoo-r5/.config /usr/src/linux" to copy the old config from the r5
to r8 or did you configured the r8 by hand again?
4. switch to bcm43xx since it is always better using native drivers than
wrappers when you can. you should at least try them and see how they behave
before saying that they don't work. compiling them don't cost you nothing.
then you can blacklist them from loading so you can use ndiswrapper if you
don't like them.

2007/10/6, Mark Haney <mhaney@ercbroadband.org>:
>
> I just upgraded to 2.6.22-r8 and when I booted into it (after
> re-emerging ndiswrapper) I got a hardware error saying it couldn't set
> the device up (wlan0).  I figured something was flaky with ndiswrapper,
> so I booted back into -r5 and tried loading my wireless again and I got
> the same error.  I've been consistently using my wireless under this
> kernel for weeks and not had a problem.  Is this an ndiswrapper issue?
> Or a kernel issue with -r8 that's screwed up my wireless?
>
> I know most of you aren't fans of ndiswrapper, but it's been absolutely
> rock solid for me and I won't change to the new mac drivers for my
> broadcom card until I have to.
>
> --
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
>
>
> --
> gentoo-amd64@gentoo.org mailing list
>
>


-- 
dott. ing. beso

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