Summary: | wireless netowrk init script calls a few times scan procedure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | conexion2000 <vacant2005> |
Component: | [OLD] baselayout | Assignee: | Roy Marples (RETIRED) <uberlord> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
conexion2000
2005-11-12 10:43:08 UTC
It appears that it is not gentoo bug, but acx driver... Changing my mind. Net script at first modprobe, than it ups the interface, without setting essid first. It starts a scan, because default mode is "Managed" and we want to find an AP. Nov 15 15:55:37 localhost 01986432 ==> acxpci_e_open Nov 15 15:55:37 localhost module count++ Nov 15 15:55:37 localhost request_irq 10 successful Nov 15 15:55:37 localhost 01986443 ==> acxpci_s_up Nov 15 15:55:37 localhost 01986444 ==> enable_acx_irq Nov 15 15:55:37 localhost 01986444 <== enable_acx_irq Nov 15 15:55:37 localhost 01986444 ==> acx_set_status Nov 15 15:55:37 localhost acx_set_status(1):SCANNING Nov 15 15:55:37 localhost 01986444 ==> acx_set_timer Nov 15 15:55:37 localhost acx_set_timer(1000 ms) Nov 15 15:55:37 localhost 01986444 <== acx_set_timer Nov 15 15:55:37 localhost 01986444 <== acx_set_status ... And only then you sets essid, that restarts the scan, because probe requests contain essid, and we need to update it. Nov 15 15:55:42 localhost 01990245 ==> acx_ioctl_set_essid Nov 15 15:55:42 localhost Set ESSID ' kunow', length 6, flags 0x0001 Nov 15 15:55:42 localhost 01990245 <== acx_ioctl_set_essid: FFFFFF8D Nov 15 15:55:42 localhost 01990245 ==> acx_ioctl_commit Nov 15 15:55:42 localhost 01990245 ==> acx_s_update_card_settings ... Nov 15 15:55:42 localhost BSS_Type = 2 Nov 15 15:55:42 localhost JoinBSSID MAC:00:00:00:00:00:00 Nov 15 15:55:42 localhost caps updated from 0x0040 to 0x0040 Nov 15 15:55:42 localhost 01990256 <== acx_s_cmd_join_bssid Nov 15 15:55:42 localhost 01990256 ==> acx_l_sta_list_init Nov 15 15:55:42 localhost 01990256 <== acx_l_sta_list_init Nov 15 15:55:42 localhost 01990256 ==> acx_set_status Nov 15 15:55:42 localhost acx_set_status(1):SCANNING Nov 15 15:55:42 localhost 01990256 ==> acx_set_timer Nov 15 15:55:42 localhost acx_set_timer(1000 ms) Nov 15 15:55:42 localhost 01990256 <== acx_set_timer Nov 15 15:55:42 localhost 01990256 <== acx_set_status We only ask for a scan once - so we can find what AP's are available. If the driver does more than one scan, then that is the drivers fault, error or design. fex, the rt2x00 driver scans around 5 times whereas the prism54 driver only scans the once. This is a driver issue and should be reported upstream by yourself |