From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1IeAVC-0003dV-86 for garchives@archives.gentoo.org; Sat, 06 Oct 2007 14:19:34 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.1/8.14.0) with SMTP id l96E86qt010919; Sat, 6 Oct 2007 14:08:06 GMT Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.186]) by robin.gentoo.org (8.14.1/8.14.0) with ESMTP id l96E85pP010905 for ; Sat, 6 Oct 2007 14:08:05 GMT Received: by fk-out-0910.google.com with SMTP id 19so1400895fkr for ; Sat, 06 Oct 2007 07:08:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=mE31GySVgV20KdYG0QcSXaw8X8qG2PnEUF8/2wGvlS4=; b=GiC6CQRDFytDTzTQwt/HYyAAovg6xIj64ynQpqG0qJbw0pb94UQvkRwoK9Bo6s0Y726HGiS/rdYhFkpzA+26miz7MP21i9Gcin0Y1t+Yv/8Si0HJBOsrS3YgsSahlpKA9ZcLV3yOzM9dcjc8gyiX00KSThhQiZ72CCxQjxUa+Dc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=PgDMHgrhMui1arCOL8uUINOpDQySd5DKJAcE2yRSEHWgN4dR/fUIBQMMhib27GMcj25i3wwWGcnYwPJWcTEr9uC0BzUH0Pp+jcWDpwL3YxDhVtR2wALK+4wTTLVS9u+P74isnzMiknrlG/YnOX9GYLD1JaHd4+YqIzjJ1uUHK0I= Received: by 10.82.170.2 with SMTP id s2mr9485002bue.1191679684531; Sat, 06 Oct 2007 07:08:04 -0700 (PDT) Received: by 10.82.135.4 with HTTP; Sat, 6 Oct 2007 07:08:04 -0700 (PDT) Message-ID: Date: Sat, 6 Oct 2007 16:08:04 +0200 From: Beso To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] latest kernel and ndiswrapper In-Reply-To: <47078B2D.7020400@ercbroadband.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_37671_17230977.1191679684526" References: <47078B2D.7020400@ercbroadband.org> X-Archives-Salt: a369b35b-baa8-41e7-93ee-7e97d03abf07 X-Archives-Hash: 4a89e2697709e4e9749e3c7f8dbb07b7 ------=_Part_37671_17230977.1191679684526 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 : > > 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 ------=_Part_37671_17230977.1191679684526 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 ------=_Part_37671_17230977.1191679684526-- -- gentoo-amd64@gentoo.org mailing list