| 1 |
"Mark Haney" <mhaney@××××××××××××.org> posted |
| 2 |
47078B2D.7020400@××××××××××××.org, excerpted below, on Sat, 06 Oct 2007 |
| 3 |
09:18:37 -0400: |
| 4 |
|
| 5 |
> I just upgraded to 2.6.22-r8 and when I booted into it (after |
| 6 |
> re-emerging ndiswrapper) I got a hardware error saying it couldn't set |
| 7 |
> the device up (wlan0). I figured something was flaky with ndiswrapper, |
| 8 |
> so I booted back into -r5 and tried loading my wireless again and I got |
| 9 |
> the same error. I've been consistently using my wireless under this |
| 10 |
> kernel for weeks and not had a problem. Is this an ndiswrapper issue? |
| 11 |
> Or a kernel issue with -r8 that's screwed up my wireless? |
| 12 |
|
| 13 |
I'm guessing the wrapper has to be compiled to the kernel it's running |
| 14 |
with. It may be that the -r5 and -r8 kernels are far enough apart to |
| 15 |
trigger that. Since you remerged the wrapper with -r8 and it didn't work |
| 16 |
(for whatever reason), it wouldn't necessarily work with -r5 either, even |
| 17 |
tho it was before, since it had been freshly merged against -r8 and not - |
| 18 |
r5. |
| 19 |
|
| 20 |
So... try booting into -r5, remerging ndiswrapper again there, and then |
| 21 |
loading /that/ version. |
| 22 |
|
| 23 |
Next time, since ndiswrapper is partially proprietary, it's probably |
| 24 |
worth saving your known-working package (using quickpkg) before trying to |
| 25 |
upgrade anything involving it. If you had done that with the working |
| 26 |
version built against -r5, when you returned to -r5, you could have |
| 27 |
remerged the working binary package you saved manually. |
| 28 |
|
| 29 |
-- |
| 30 |
Duncan - List replies preferred. No HTML msgs. |
| 31 |
"Every nonfree program has a lord, a master -- |
| 32 |
and if you use the program, he is your master." Richard Stallman |
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-amd64@g.o mailing list |
Archives