with the release version of ndiswrapper i'm able to insert ndiswrapper
and set the essid of the interface .
if i also specify the channel iwconfig reports the correct mac address
for the AP
i've also tried with cvs and debugging enabled... (see the attached log)
what can i do to help resolv this?
i've been lurking a while but haven't seen anything about this
serialized driver issue. nothing explanitory in the archive or the faq
either. What is the problem with "serialized" drivers - and what does
"serialized" mean in this context?
ndiswrapper version 0.6+CVS loaded
ndiswrapper adding ar5211.sys
PCI: Found IRQ 11 for device 0000:02:02.0
PCI: Sharing IRQ 11 with 0000:00:1d.2
PCI: Sharing IRQ 11 with 0000:00:1f.1
ndiswrapper: Driver ar5211.sys is serialized. This might not work!
Unable to handle kernel NULL pointer dereference at virtual address
*pde = 00000000
Oops: 0000 [#1]
EIP: 0060:[<f99901de>] Tainted: P
EFLAGS: 00010296 (2.6.5)
EIP is at KeInitializeTimer+0xe/0x40 [ndiswrapper]
eax: fdf1f7c0 ebx: fdf1f7e0 ecx: 00000fff edx: 00000000
esi: f99901d0 edi: dcb16220 ebp: e645a000 esp: d45c5d5c
ds: 007b es: 007b ss: 0068
Process loadndisdriver (pid: 9588, threadinfo=d45c4000 task=f6adf460)
Stack: dcb16220 ca820000 e645a000 fdf1839c 00000001 fdf183a9 fdf1f7e0
fdefa143 00000000 f7ebf800 dcb16220 dcb16000 00000000 00180016
00180016 fdef9bd8 f998c43d d45c5dc0 ede4fdb0 dcb16220 00000000
[<f998c43d>] call_init+0xad/0xc0 [ndiswrapper]
[<f998d6df>] ndis_init_one+0x2df/0x3b0 [ndiswrapper]
[<f998c4e6>] call_entry+0x36/0x40 [ndiswrapper]
[<f998da56>] start_driver+0x146/0x180 [ndiswrapper]
[<f998e345>] misc_ioctl+0x135/0x261 [ndiswrapper]
Code: 8b 42 10 89 44 24 0c 8b 42 0c 89 14 24 89 44 24 08 31 c0 89
ndiswrapper: Driver calling NdisSetTimer on an uninitilized timer
Brad Langhorst schrieb:
> with the release version of ndiswrapper i'm able to insert ndiswrapper
> and set the essid of the interface .
> if i also specify the channel iwconfig reports the correct mac address
> for the AP
> i've also tried with cvs and debugging enabled... (see the attached log)
> what can i do to help resolv this?
> i've been lurking a while but haven't seen anything about this
> serialized driver issue. nothing explanitory in the archive or the faq
> either. What is the problem with "serialized" drivers - and what does
> "serialized" mean in this context?
I'm also trying to get the internal Atheros-based a/b/g card of my R30
work. A few weeks ago I developed a patch to fix the problem with the
timers you described. It works, but then the driver chrashes as soon as
you try to send some data. And you can still not switch it to ad-hoc
mode (that's my personal requirement).
My patch is currently under examination by the maintainers. One of them
have access to similar hardware now, and I'm also trying to look at this
issue again. So we may see a solution soon - hopefully :)