Hi Andres,
I will try to clarify things as requested.
Andres wrote:
On Fri, 2006-05-19 at 00:12 +0200, Silvério Santos wrote:
wlagsall (generic Agere) is reported to have the driver installed.
Win-driver-URI:
http://www.agere.com/mobility/docs/windows_drivers_sr02-2.3.zip
Command:
ndiswrapper -i WLAGSALL.INF
wltos48 (special Toshiba Tecra 9000) is still an invalid driver.
Win-driver-URI:
http://support.toshiba-tro.de/tools/Tecra/t9000/windows-2000/wireless-network-driver/wlesslan_t9000_win2k_641187_en.zip
Command:
ndiswrapper -i WLTOS48.INF
Will test the next days though, as I had to change the AP to WEP due to
the lack of wpa_supplicant compatible drivers.
The test with command
wpa_supplicant -Dndiswrapper -ieth2 -d -c/etc/wpa_supplicant.conf
does lead to a connection. The conf-file is configured to use WEP, which
works fine with the native orinoco-driver (aka HERMES I; which does not
support WPA, being the reason why I try to use the NDIS driver). As the
wpa_supplicant file is based on a example from the package and the
values are used to configure the orinoco-driver I assume my
ndiswrapper-installation does not work.
I'm not really sure what you're saying. Please provide the exact
commands that you're running, and links to the drivers, so that I can
attempt to reproduce the problem.
Done above.
BTW: the command ndiswrapper reports "Error: no versions of ndiswrapper
found!", while ndiswrapper-1.8 works fine from the path since the update
to 1.16. But maybe this is subject of another bug report...
What ndis packages do you have installed?
COLUMNS=200 dpkg -l |grep ndiswrapper
Output:
ii ndiswrapper-common 1.16-1
Userspace utilities for ndiswrapper
ii ndiswrapper-modules-2.6.16-1-686 1.16-1+2.6.16-12
Ndiswrapper linux kernel module
ii ndiswrapper-source 1.16-1
Source for the ndiswrapper linux kernel module
ii ndiswrapper-utils 1.8-2
Userspace utilities for ndiswrapper
ii ndiswrapper-utils-1.7 1.8-2
Userspace utilities for ndiswrapper
ii ndiswrapper-utils-1.8 1.16-1
Userspace utilities for ndiswrapper
The only time this should happen is if you have ndiswrapper-common but
no ndiswrapper-utils-* packages installed. If it's happening
otherwise.. yes, that would be a separate bug.
Although I used a workaround for me by entering the ndiswrapper-1.8
command as a fixed one into /usr/sbin/ndiswrapper I think I will report
it separately in the next days and will not bother you further in this
thread.
Thanks and best regards
Silvério