ndiswrapper-general

Hi Geeks
I was using ndiswrapper with the Netgear WPN111 USB adapter for quite=20
some time on SuSE 10.0 32-bit. When I upgraded to SuSE 10.1 things went=20
bad and so far the only thing I see is that loading the drivers=20
(athwpn.inf and netwpn11.inf) fail with that message:
(alternate driver: conflict)
Loading the module with modprobe fails with a segmentation fault. =93dmes=
g=20
| grep nids=94 does not reveal any issues that would help me to narrow th=
e=20
problem down.
Could you explain what this error message means and what I can do in=20
order to investigate that problem further?
Thanx =96 Andy Schaefer

Hi Geeks
After starting to add debug statements into the /utils/ndiswrapper perl
script I finally figured out what is going wrong.
ndiswrapper creates a *.<bus type>.conf file which is then used to see
in the listing of the drivers to determine the bus type. Now inside the
parse_install() method there is a line where the rest of the conf file
name is created. Right now (at least for 1.24) there is a line using
"%X" inside sprintf to insert the bus type into the file name. Now, and
I am guessing here, this converts a number in Hex making the USB bus
type from 15 to F and that is why the entire thing goes bad.
Converting the "%X" into "%s" and everything works fine including
avoiding the seg-fault when I modprobe ndiswrapper.
-Andy
Andreas Schaefer wrote:
> Hi Geeks
>
>
> I was using ndiswrapper with the Netgear WPN111 USB adapter for quite=20
> some time on SuSE 10.0 32-bit. When I upgraded to SuSE 10.1 things went=
=20
> bad and so far the only thing I see is that loading the drivers=20
> (athwpn.inf and netwpn11.inf) fail with that message:
>
> (alternate driver: conflict)
>
> Loading the module with modprobe fails with a segmentation fault. =93dm=
esg=20
> | grep nids=94 does not reveal any issues that would help me to narrow =
the=20
> problem down.
>
> Could you explain what this error message means and what I can do in=20
> order to investigate that problem further?
>
> Thanx =96 Andy Schaefer
>
>
> -----------------------------------------------------------------------=
--
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share=
your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Ndiswrapper-general mailing list
> Ndiswrapper-general@...
> https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general
> =20

Hi Geeks
I investigated that issue a little bit more and figure out that even
though I can load ndiswrapper now it is not going to load the drivers.
There is something wrong in 1.24 from what I see (bus type used to
create the ".conf" file and the bus constant to check against are out of
sink). Probably that did not surface yet because most people are not
using USB devices and there it does not matter because the bus type
number is below 10.
Now I reverted back to 1.10 and everything works again.
I will check later if I can fix 1.24 by setting the USB bus constant
from 15 to F will do the trick.
-Andy
Andreas Schaefer wrote:
> Hi Geeks
>
> After starting to add debug statements into the /utils/ndiswrapper perl
> script I finally figured out what is going wrong.
> ndiswrapper creates a *.<bus type>.conf file which is then used to see
> in the listing of the drivers to determine the bus type. Now inside the
> parse_install() method there is a line where the rest of the conf file
> name is created. Right now (at least for 1.24) there is a line using
> "%X" inside sprintf to insert the bus type into the file name. Now, and
> I am guessing here, this converts a number in Hex making the USB bus
> type from 15 to F and that is why the entire thing goes bad.
> Converting the "%X" into "%s" and everything works fine including
> avoiding the seg-fault when I modprobe ndiswrapper.
>
> -Andy
>
> Andreas Schaefer wrote:
> =20
>> Hi Geeks
>>
>>
>> I was using ndiswrapper with the Netgear WPN111 USB adapter for quite=20
>> some time on SuSE 10.0 32-bit. When I upgraded to SuSE 10.1 things wen=
t=20
>> bad and so far the only thing I see is that loading the drivers=20
>> (athwpn.inf and netwpn11.inf) fail with that message:
>>
>> (alternate driver: conflict)
>>
>> Loading the module with modprobe fails with a segmentation fault. =93d=
mesg=20
>> | grep nids=94 does not reveal any issues that would help me to narrow=
the=20
>> problem down.
>>
>> Could you explain what this error message means and what I can do in=20
>> order to investigate that problem further?
>>
>> Thanx =96 Andy Schaefer
>>
>>
>> ----------------------------------------------------------------------=
---
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to shar=
e your
>> opinions on IT & business topics through brief surveys -- and earn cas=
h
>> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
>> _______________________________________________
>> Ndiswrapper-general mailing list
>> Ndiswrapper-general@...
>> https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general
>> =20
>> =20
>
>
> -----------------------------------------------------------------------=
--
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share=
your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Ndiswrapper-general mailing list
> Ndiswrapper-general@...
> https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general
> =20