public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: latest kernel and ndiswrapper
Date: Sat, 6 Oct 2007 17:25:18 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.10.06.17.25.18@cox.net> (raw)
In-Reply-To: 47078B2D.7020400@ercbroadband.org

"Mark Haney" <mhaney@ercbroadband.org> 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



      parent reply	other threads:[~2007-10-06 17:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-06 13:18 [gentoo-amd64] latest kernel and ndiswrapper Mark Haney
2007-10-06 14:08 ` Beso
2007-10-06 15:25   ` Nuitari
2007-10-08 11:31     ` Mark Haney
2007-10-08 11:40       ` Barry Walsh
2007-10-08 13:33       ` Beso
2007-10-08 21:58         ` Mark Haney
2007-10-09 12:20           ` Beso
2007-10-09 12:37             ` Mark Haney
2007-10-09 13:03               ` Beso
2007-10-06 17:25 ` Duncan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pan.2007.10.06.17.25.18@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox