Thread: [Ndiswrapper-general] RE: Problem on 2.4 kernel
Status: Beta
Brought to you by:
pgiri
From: Ken M. <km...@ma...> - 2004-09-24 15:43:12
|
On 2004-08-29 20:24 Chris E posted: >However, when running the 2.4.26 kernel (I did remember to build >ndiswrapper separately for >each kernel), all versions from 0.9 onwards result in a keventd oops and a keyboard lockup. > Version 0.8 loads fine, but causes the above problem when unloaded if ifconfig has been >called on any ndiswrapper-managed interface. I have had exactly the same experience, and my "oops" listing looks the same too. I'm running on a Fujitsu 6210 with a builtin Intel 2200BG. Is there any resolution? -- Ken Mandelberg <km...@ma...> |
From: M. B. <sb...@fe...> - 2004-09-25 01:05:42
|
On Fri, 2004-09-24 at 16:43, Ken Mandelberg wrote: > On 2004-08-29 20:24 Chris E posted: >=20 > >However, when running the 2.4.26 kernel (I did remember to build > >ndiswrapper separately for > >each kernel), all versions from 0.9 onwards result in a keventd oops and= a keyboard lockup. > > Version 0.8 loads fine, but causes the above problem when unloaded if i= fconfig has been > >called on any ndiswrapper-managed interface. >=20 > I have had exactly the same experience, and my "oops" listing looks the s= ame too. >=20 > I'm running on a Fujitsu 6210 with a builtin Intel 2200BG. >=20 > Is there any resolution? I don't know if it the better advise but version 0.9 can be the resolution for kernels 2.4. --=20 S=E9rgio M. B. --=20 S=E9rgio M. B. |
From: Ken M. <km...@ma...> - 2004-09-25 01:21:08
|
On Fri, 2004-09-24 at 21:05, Sérgio Monteiro Basto wrote: \ > I don't know if it the better advise but version 0.9 can be the > resolution for kernels 2.4. > -- > Sérgio M. B. > My experience is that both 0.9 and 0.10 fail in the same way on 2.4. The kernel gets a null pointer moments after ndiswrapper loads. This doesn't happen on 0.8 and the wlan0 device actually works, but is fragile. I can induce the null pointer on 0.8 by purposely removing the module, and various ways not on purpose. This is the same behavior Chris E reported. -- Ken Mandelberg <km...@ma...> |