> On Sunday 17 August 2008, Lars Ericsson wrote: > > > > > > > > Have tried using the wpa_supplicant and got the -EBUSY from > > > > ieee80211_ioctl_siwmode(). > > > > > > As usual: The interface must be down when changing working mode. > > > > > > > The initial mode is 2. I do not know the source of that > mode, might be a > > default. > > <7>[ 85.713782] LaE: ieee80211_ioctl_siwmode: type=2, > sdata->vif.type=2 > > that is managed mode. > > > Between 85.713698 and 85.821832 device is opened > (1=netif_running(dev)) > > <7>[ 85.713698] LaE: ieee80211_ioctl_siwmode: 0=netif_running(dev) > > <7>[ 85.713752] LaE: ieee80211_ioctl_siwmode: mode=2 > > <7>[ 85.713782] LaE: ieee80211_ioctl_siwmode: type=2, > sdata->vif.type=2 > > <6>[ 85.713938] phy0 -> rt2x00lib_request_firmware: Info - Loading > > firmware file 'rt2561s.bin'. > > <6>[ 85.724265] firmware: requesting rt2561s.bin > > <6>[ 85.779042] phy0 -> rt2x00lib_request_firmware: Info > - Firmware > > detected - version: 0.8. > > <7>[ 85.821654] LaE: ieee80211_ioctl_giwrange: enter; > > <7>[ 85.821832] LaE: ieee80211_ioctl_giwrange: > 1=netif_running(dev) > > > > When wpa supplicant set the adhoc mode=1/type=3 the device > is running and > > fails > > to quota myself: "The interface must be down when changing > working mode." OK, I got that ;) > > > <7>[ 85.947991] LaE: ieee80211_ioctl_siwmode: mode=1 > > <7>[ 85.948134] LaE: ieee80211_ioctl_siwmode: type=3, > sdata->vif.type=2 > > <7>[ 85.948433] LaE: ieee80211_ioctl_siwmode: type=3 > > > > My work around was to ignore this situation and continue > the mode change. > > that is not correct, as I've stated already: The interface > must be down when changing working mode. > I have to check if it is the mac80211 or the wpa_supplicant that is doing wrong. > > > > Two tests cases, but same behaviour: > > > > 1) Linx.git: 2.6.26 and wpa_supplicant 0.5.9 > > > > 2) rt2x00.git: Version 2.2.0 and wpa_supplicant 0.5.9 > > > > > > Are any beacons going out? Is there anything in the logs which > > > indicates what is happening? > > > > > > > As you can se in the trace below, the configuration > proceeds and the adhoc > > is created. > > The warnon might give some clues. > > So how about those beacons? are they getting out? > I will check that and come back as soon as the first issue is sorted out. I might broke some logic when I was trying to change mode for an open interface. /Lars -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
