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 1IeDaZ-0004fi-EX for garchives@archives.gentoo.org; Sat, 06 Oct 2007 17:37:19 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.1/8.14.0) with SMTP id l96HQ9aD010532; Sat, 6 Oct 2007 17:26:09 GMT Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by robin.gentoo.org (8.14.1/8.14.0) with ESMTP id l96HQ9Gx010515 for ; Sat, 6 Oct 2007 17:26:09 GMT Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IeDPJ-0006GP-37 for gentoo-amd64@lists.gentoo.org; Sat, 06 Oct 2007 17:25:41 +0000 Received: from ip68-230-96-73.ph.ph.cox.net ([68.230.96.73]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 Oct 2007 17:25:41 +0000 Received: from 1i5t5.duncan by ip68-230-96-73.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 Oct 2007 17:25:41 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: latest kernel and ndiswrapper Date: Sat, 6 Oct 2007 17:25:18 +0000 (UTC) Message-ID: References: <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: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ip68-230-96-73.ph.ph.cox.net User-Agent: Pan/0.132 (Waxed in Black) Sender: news X-Archives-Salt: 88501b89-d656-4d1b-83db-64926daeb8ca X-Archives-Hash: 2b0859e3ec400ebc809f83b12e109817 "Mark Haney" posted 47078B2D.7020400@ercbroadband.org, excerpted below, on Sat, 06 Oct 2007 09:18:37 -0400: > 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'm guessing the wrapper has to be compiled to the kernel it's running with. It may be that the -r5 and -r8 kernels are far enough apart to trigger that. Since you remerged the wrapper with -r8 and it didn't work (for whatever reason), it wouldn't necessarily work with -r5 either, even tho it was before, since it had been freshly merged against -r8 and not - r5. So... try booting into -r5, remerging ndiswrapper again there, and then loading /that/ version. Next time, since ndiswrapper is partially proprietary, it's probably worth saving your known-working package (using quickpkg) before trying to upgrade anything involving it. If you had done that with the working version built against -r5, when you returned to -r5, you could have remerged the working binary package you saved manually. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- gentoo-amd64@gentoo.org mailing list