[driverloader] Driverloader on embedded linux (prism2_hostapd: unknown cmd=14)

[Mattias Seeman]

Hi,

DriverLoader does seem to be properly configured on my embedded system, 
but still does not work...

About the dldrconfig dummy script, I wrote one that just return 0, but I 
don't really know what I'm doing here (any further pointers?).

"iwlist eth1 scan" finds the AP but the Belkin F5D7050 is unable to 
negotiate an IP address, I wonder if there are further prerequisites 
(s/w or h/w) on DriverLoader that are not listed in any documentation 
and that are not fulfilled on my embedded system. I've read the FAQ (of 
course) but no issues raised there seem to apply here.

The following is an "iwevent" log from the _host_ system, when doing 
"ifconfig eth1 up" and the device associates with the AP. This does 
/not/ happen on the _embedded_ system...

16:37:23.279958    eth1     Custom driver 
event:ASSOCINFO(ReqIEs=000772617466616365010402040b1632080c1218243048606c 
RespIEs=010882848b960c18304832041224606cdd0600032f010001dd0c00037f020101010002a34000)
16:37:23.280065    eth1     New Access Point/Cell address:00:11:95:01:5D:52

Regards,
\Mattias Seeman

Linuxant support (Jonathan) wrote:

> Hi,
>
> you are able to get this far on the embedded system, then DriverLoader 
> is correctly installed. After the Windows XP driver is installed, 
> DriverLoader only needs write access to the '/etc/driverloader'.
>
> For the use of the 'dldrconfig' script, you no longer need it but you 
> should replace this script with a dummy shell script because the 
> DriverLoader module will attempt to call this script.
>
> On the embedded system, did you tried to use DriverLoader without WPA 
> to see if WPA is the source of the problem? Did you compiled the 
> kernel on your embedded system with the same options and same kernel 
> source as on the development machine? The 
> "ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported" error message 
> is returned by the kernel.
>
> Regards,
>
>
> Jonathan
> Technical specialist / Linuxant
> www.linuxant.com
> support at linuxant.com
>
>
> Mattias Seeman wrote:
>
>> Hello!
>>
>> A little background: I'm working on a robot project and need to get 
>> wireless networking on an embedded linux system. This "embedded linux 
>> distribution" (built with HLinux by www.hectronic.se) is based on a 
>> Debian "host system". Driverloader is installed on the host system 
>> and works perfectly (TYVM :-) with a Belkin F5D7050 (USB 2.0 Adaptor 
>> 802.11g 54Mbps). WPA with wpa_supplicant is also used without problems.
>>
>> So I'm trying to migrate the driverloader to the embedded system. 
>> I've built a custom kernel (2.4.26) and compiled driverloader.o with 
>> this kernel-source.
>> <important>
>> What I'm looking for is really a way to configure driverloader 
>> without the need for perl interpreter or web browser (i.e. w/o 
>> running dldrconfig??).
>> </important>
>>
>> modules.dep is not preserved in the migration but I can "insmod 
>> /lib/modules/2.4.26-xxx/extra/driverloader.o" just as well as on the 
>> host system. <hack>I've manually edited /etc/driverloader/config/* 
>> files to reflect the embedded system (and placed them on a read/write 
>> fs).</hack>
>> As you can see from output below wpa_supplicant finds the AP but 
>> fails to complete key negotiation. Problems seem to arise at the call 
>> "ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported" (i.e 
>> "prism2_hostapd: unknown cmd=14").
>>
>> Do any other special files be on a read/write fs (since the root fs 
>> is read-only)?
>>
>> <dmesg output>
>> hub.c: new USB device 00:13.0-2, assigned address 4
>> driverloader: prismaxp.sys: 0xc4a59000..0xc4aab3a0 entry = c4a7511f 
>> (pbase = 0x10000)
>> eth1: New link status: Disconnected (0002)
>> eth1: WPA, AES, TKIP, WEP128, WEP64 supported
>> eth1: GlobespanVirata, Inc. at 00:13.02 (MAC address 
>> 00:30:BD:AF:AE:BE) ready
>> prism2_hostapd: unknown cmd=14
>> prism2_hostapd: unknown cmd=14
>> prism2_hostapd: unknown cmd=14
>> </dmesg output>
>>
>> <ifconfig output>
>> $ ifconfig eth1
>> eth1      Link encap:Ethernet  HWaddr 00:30:BD:AF:AE:BE
>>          UP BROADCAST MULTICAST  MTU:1500  Metric:1
>>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>> </ifconfig output>
>>
>> <wpa_supplicant output>
>> $ wpa_supplicant -ieth1 -d -c/etc/wpa_supplicant.conf
>> Configuration file '/etc/wpa_supplicant.conf' -> 
>> '/etc/wpa_supplicant.conf'
>> Reading configuration file '/etc/wpa_supplicant.conf'
>> wpa_driver_hostap_set_wpa: enabled=1
>> wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 
>> key_len=0
>> wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 
>> key_len=0
>> wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 
>> key_len=0
>> wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 
>> key_len=0
>> wpa_driver_hostap_set_countermeasures: enabled=0
>> wpa_driver_hostap_set_drop_unencrypted: enabled=1
>> Setting scan request: 0 sec 100000 usec
>> Starting AP scan (specific SSID)
>> Scan SSID - hexdump_ascii(len=7):
>>     72 61 74 66 61 63 65                              ratface
>> ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
>> Failed to initiate AP scan.
>> Scan timeout - try to get results
>> Received 269 bytes of scan results (1 BSSes)
>> Scan results: 1
>> 0: 00:11:95:01:5d:52 ssid='ratface' wpa_ie_len=24 rsn_ie_len=0
>> Trying to associate with 00:11:95:01:5d:52 (SSID='ratface' freq=2437 
>> MHz)
>> Cancelling scan request
>> WPA: using IEEE 802.11i/D3.0
>> </wpa_supplicant output>
>>
>>
>> ANY help much appreciated..., thanks in advance!
>> \Mattias Seeman
>>
>> _______________________________________________
>> driverloader mailing list
>> driverloader at lists.linuxant.com
>> https://www.linuxant.com/mailman/listinfo/driverloader
>
>
>

-------------- next part --------------
16:37:23.279958    eth1     Custom driver event:ASSOCINFO(ReqIEs=000772617466616365010402040b1632080c1218243048606c RespIEs=010882848b960c18304832041224606cdd0600032f010001dd0c00037f020101010002a34000)
16:37:23.280065    eth1     New Access Point/Cell address:00:11:95:01:5D:52