Re: [Ndiswrapper-general] Need help to create driver for Netgear WN111v2
Status: Beta
Brought to you by:
pgiri
From: Pavel R. <pr...@gn...> - 2009-09-30 00:52:01
|
On Tue, 2009-09-29 at 06:57 +0200, Malte Gell wrote: > Hello, > > Pavel Roskin <pr...@gn...> wrote > > > On Tue, 2009-09-29 at 03:59 +0200, Malte Gell wrote: > > > kernel: ndiswrapper (import:242): unknown symbol: > > > ntoskrnl.exe:'NlsMbCodePageTag' > > > > NlsMbCodePageTag is defined in the current ndiswrapper to 0, and the > > code in driver/pe_linker.c would consider the symbol as missing. > > > > get_export() doesn't distinguish the case when the symbol is missing and > > when it's present and set to 0. I believe it's a bug, not an intended > > behavior. In other words, NlsMbCodePageTag is supposed to resolve to 0. > > Please try the attached patch. > > The patch works well with ndiswrapper 1.55 the module loaded perfectly, no > crash, no trouble. Good to know. Thank you for testing! I have committed a similar fix. > But, now I see an issue I saw before with an AVM Fritz USB N stick: the stick > cannot connect to the access point. The ar9170 driver does not show this > issue, the error looks like this: > > ndiswrapper (iw_get_scan:1243): getting BSSID list failed (C0010016) The message comes from iw_get_scan() in driver/iw_ndis.c. C0010016 is NDIS_STATUS_BUFFER_TOO_SHORT. It looks like the driver wants to write more than 8 entries and requests a longer buffer, but even the longer buffer is too short. I think it's a fair game to ignore that error. The patch is attached. > The adapther can see the access point and can connect for a second, but loses > connection. My wpa_supplicant.conf works well with ar9170. I see it too, and I also have different problem with USB. For instance, I cannot unload ndiswrapper without a kernel panic. -- Regards, Pavel Roskin |