On Wednesday 05 March 2014 06:36:50 Thierry Moreau wrote:
> I am using a kind-of "linux from scratch" (i.e. Crux 3.0, 64 bits
> Intel, kernel 3.10.32) and I am stuck with a EBUSY error return from
> the wireless driver I suspect it comes from the driver behavior since
> it is consistent either from the command
>
> iw dev wlan1 set channel 2
>
> or the comand
>
> iwconfig wlan1 set channel 2
>
> (it occurred also with "iw" with a kernel where the iwconfig support
> emulation is off -- CONFIG_CFG82011_WEXT). The EBUSY error return
> occurs as early as immediately after the initial module install, and
> consistently thereafter. The wireless scanning works (reporting a
> nearby beacon on channel 1).
It was not entirely clear for me, but have you enabled the interface
before changing the channel? I.e.
ip link set wlan0 up
iw dev wlan0 set channel 2
I suggest to try 3.13 or even 3.14(-rcish). Earlier kernels (3.10 being
the worst) had an issue[1] that impacted wireless stability.
> The system is a Shuttle XS36VL box
> (http://us.shuttle.com/barebone/Models/XS36VL.html). It does not have
> a physical wireless switch (a dmesg line above reports the switch
> position as "on").
The same box is operating in my neighbourhood (networking was not
required for its purpose). Good luck with getting multi-head working.
This box is running 3.14-rc2-something now with patches to get monitor
mode to function properly.
Kind regards,
Peter
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=60713
--
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
