Bug#645055: realtek 8188CE ad-hoc mode not supported
Package: linux-2.6
Version: 2.6.39-3~bpo60+1
Severity: normal
Tags: upstream
Hi,
The documentation for the rtl8192ce driver explicitely mentions that
it supports ad-hoc mode, yet, on the rtl8188CE card I have here (which
is advertised as supported both by the upstream driver and the driver
in the linux source), the ad-hoc mode yields this error:
root@angela:/home/anarcat# iwconfig wlan0 mode Ad-hoc essid foo
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Device or resource busy.
I have tried changing the case of the "ad-hoc" word and various
spellings, nothing works there. I have also tried the upstream driver
available here:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PFid=48&Level=5&Conn=4 &ProdID=278&DownTypeID=3&GetDown=false&Downloads=t rue
without any more luck, which means this is a problem with upstream (or
with the card not supporting ad-hoc mode at all, although that would
be very surprising).
-- Package-specific info:
** Version:
Linux version 2.6.39-bpo.2-686-pae (Debian 2.6.39-3~bpo60+1) (norbert@tretkowski.de) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Thu Aug 4 11:02:22 UTC 2011
** USB devices:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 5986:01a6 Acer, Inc Lenovo Integrated Webcam
Bus 002 Device 002: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Kernel: Linux 2.6.39-bpo.2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6.39-bpo.2-686-pae depends on:
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
ii initramfs-tools [linux-init 0.99~bpo60+1 tools for generating an initramfs
ii linux-base 3.2 Linux image base package
ii module-init-tools 3.12-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.39-bpo.2-686-pae recommends:
ii firmware-linux-free 2.6.32-35squeeze2 Binary firmware for various driver
ii libc6-i686 2.11.2-10 Embedded GNU C Library: Shared lib
Versions of packages linux-image-2.6.39-bpo.2-686-pae suggests:
ii grub-pc 1.98+20100804-14 GRand Unified Bootloader, version
pn linux-doc-2.6.39 <none> (no description available)
Versions of packages linux-image-2.6.39-bpo.2-686-pae is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
ii firmware-linux 0.32~bpo60+1 Binary firmware for various driver
ii firmware-linux-nonfree 0.32~bpo60+1 Binary firmware for various driver
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
pn xen-hypervisor <none> (no description available)
-- debconf information excluded
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111012052940.17383.59248.reportbug@localhost">ht tp://lists.debian.org/20111012052940.17383.59248.reportbug@localhost
10-12-2011, 01:08 PM
Ben Hutchings
Bug#645055: realtek 8188CE ad-hoc mode not supported
On Wed, 2011-10-12 at 01:29 -0400, Antoine Beaupré wrote:
> Package: linux-2.6
> Version: 2.6.39-3~bpo60+1
> Severity: normal
> Tags: upstream
>
> Hi,
>
> The documentation for the rtl8192ce driver explicitely mentions that
> it supports ad-hoc mode, yet, on the rtl8188CE card I have here (which
> is advertised as supported both by the upstream driver and the driver
> in the linux source), the ad-hoc mode yields this error:
>
> root@angela:/home/anarcat# iwconfig wlan0 mode Ad-hoc essid foo
> Error for wireless request "Set Mode" (8B06) :
> SET failed on device wlan0 ; Device or resource busy.
[...]
Can you create an ad-hoc interface like this:
iw dev wlan0 interface add wlan1 type adhoc
(you'll need the iw package).
Ben.
--
Ben Hutchings
If at first you don't succeed, you're doing about average.
10-12-2011, 03:20 PM
Antoine Beaupré
Bug#645055: realtek 8188CE ad-hoc mode not supported
On Wed, 12 Oct 2011 14:08:32 +0100, Ben Hutchings <ben@decadent.org.uk> wrote:
> Can you create an ad-hoc interface like this:
>
> iw dev wlan0 interface add wlan1 type adhoc
>
> (you'll need the iw package).
Interesting - this works. Didn't know of the iw tool. But this creates a
separate interface, kind of odd!
The adhoc mode works like that. I am not sure I understand why it
doesn't work with iwconfig, can you enlighten me?
Thanks!
--
L'art n'est pas un bureau d'anthropométrie.
- Léo Ferré, "Préface"
10-12-2011, 04:01 PM
Ben Hutchings
Bug#645055: realtek 8188CE ad-hoc mode not supported
On Wed, Oct 12, 2011 at 11:20:31AM -0400, Antoine Beaupré wrote:
> On Wed, 12 Oct 2011 14:08:32 +0100, Ben Hutchings <ben@decadent.org.uk> wrote:
> > Can you create an ad-hoc interface like this:
> >
> > iw dev wlan0 interface add wlan1 type adhoc
> >
> > (you'll need the iw package).
>
> Interesting - this works. Didn't know of the iw tool. But this creates a
> separate interface, kind of odd!
>
> The adhoc mode works like that. I am not sure I understand why it
> doesn't work with iwconfig, can you enlighten me?
iwconfig uses the original WEXT (wireless extensions) configuration
interface. This interface was never very well specified and was
implemented in inconsistent ways by different drivers.
The newer configuration interface used by iw, Network Manager and
other tools is nl80211 (netlink for IEEE 802.11).
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111012160135.GK3366@decadent.org.uk">http://lists.debian.org/20111012160135.GK3366@decadent.org.uk
10-12-2011, 11:24 PM
Ben Hutchings
Bug#645055: realtek 8188CE ad-hoc mode not supported
On Wed, 2011-10-12 at 17:01 +0100, Ben Hutchings wrote:
> On Wed, Oct 12, 2011 at 11:20:31AM -0400, Antoine Beaupré wrote:
> > On Wed, 12 Oct 2011 14:08:32 +0100, Ben Hutchings <ben@decadent.org.uk> wrote:
> > > Can you create an ad-hoc interface like this:
> > >
> > > iw dev wlan0 interface add wlan1 type adhoc
> > >
> > > (you'll need the iw package).
> >
> > Interesting - this works. Didn't know of the iw tool. But this creates a
> > separate interface, kind of odd!
> >
> > The adhoc mode works like that. I am not sure I understand why it
> > doesn't work with iwconfig, can you enlighten me?
>
> iwconfig uses the original WEXT (wireless extensions) configuration
> interface. This interface was never very well specified and was
> implemented in inconsistent ways by different drivers.
>
> The newer configuration interface used by iw, Network Manager and
> other tools is nl80211 (netlink for IEEE 802.11).
[...]
I looked a little further and saw that nl80211 does support changing
interface type (mode). But this driver (rtl8192ce) only supports
creating new interfaces, not changing their type.
Should mac80211 drivers generally support changing interface type
(change_interface operation)?
Ben.
--
Ben Hutchings
Quantity is no substitute for quality, but it's the only one we've got.
10-13-2011, 01:46 AM
Antoine Beaupré
Bug#645055: realtek 8188CE ad-hoc mode not supported
On Thu, 13 Oct 2011 00:24:12 +0100, Ben Hutchings <ben@decadent.org.uk> wrote:
> I looked a little further and saw that nl80211 does support changing
> interface type (mode). But this driver (rtl8192ce) only supports
> creating new interfaces, not changing their type.
>
> Should mac80211 drivers generally support changing interface type
> (change_interface operation)?
Seems to me really counter-intuitive that it didn't work. It was the
first time I ever see such a problem.
I have seen numerous drivers not support "Master" or "Monitor" mode,
because of limitations of the implementation or the hardware, but if
this is purely a API problem, it seems like a problem that should be
fixed...
Is this the right place though?
A.
--
The idea that Bill Gates has appeared like a knight in shining armour to
lead all customers out of a mire of technological chaos neatly ignores
the fact that it was he who, by peddling second-rate technology, led
them into it in the first place. - Douglas Adams (1952-2001)
10-13-2011, 02:10 AM
Larry Finger
Bug#645055: realtek 8188CE ad-hoc mode not supported
On 10/12/2011 06:24 PM, Ben Hutchings wrote:
I looked a little further and saw that nl80211 does support changing
interface type (mode). But this driver (rtl8192ce) only supports
creating new interfaces, not changing their type.
Should mac80211 drivers generally support changing interface type
(change_interface operation)?
I don't think that implementation of the WEXT interface is necessary. As to
using iw, the following sequence worked:
iw dev wlan14 interface add wlan15 type adhoc
iw dev set rename5 type managed
iw dev set rename5 type adhoc
Why it was called "rename5" when I asked for "wlan15" is not understood, but the
iw interface changes the mode for an existing interface when using rtl8192ce.
BTW, I added a new iface because I did not want to interrupt my internat connection.
Larry
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E964896.5050004@lwfinger.net">http://lists.debian.org/4E964896.5050004@lwfinger.net
10-13-2011, 02:25 AM
Ben Hutchings
Bug#645055: realtek 8188CE ad-hoc mode not supported
On Wed, 2011-10-12 at 21:10 -0500, Larry Finger wrote:
> On 10/12/2011 06:24 PM, Ben Hutchings wrote:
> > I looked a little further and saw that nl80211 does support changing
> > interface type (mode). But this driver (rtl8192ce) only supports
> > creating new interfaces, not changing their type.
> >
> > Should mac80211 drivers generally support changing interface type
> > (change_interface operation)?
>
> I don't think that implementation of the WEXT interface is necessary.
The change_interface operation appears to be used in implementation of
nl80211 too.
> As to using iw, the following sequence worked:
>
> iw dev wlan14 interface add wlan15 type adhoc
> iw dev set rename5 type managed
> iw dev set rename5 type adhoc
>
> Why it was called "rename5" when I asked for "wlan15" is not understood,
udev's persistent name generator isn't able to distinguish the two
interfaces by MAC address, so it decides the new interface should also
be named 'wlan14'. udev does renaming in two steps for some reason, and
the second step obviously fails.
> but the
> iw interface changes the mode for an existing interface when using rtl8192ce.
>
> BTW, I added a new iface because I did not want to interrupt my
> internat connection.
Hmm. Maybe the change_interface operation is only needed to change
type/mode while the interface is up.
Antoine, did you bring the interface down before setting its mode?
Ben.
--
Ben Hutchings
Quantity is no substitute for quality, but it's the only one we've got.
10-13-2011, 02:31 AM
Antoine Beaupré
Bug#645055: realtek 8188CE ad-hoc mode not supported
On Thu, 13 Oct 2011 03:25:17 +0100, Ben Hutchings <ben@decadent.org.uk> wrote:
> > but the
> > iw interface changes the mode for an existing interface when using rtl8192ce.
> >
> > BTW, I added a new iface because I did not want to interrupt my
> > internat connection.
>
> Hmm. Maybe the change_interface operation is only needed to change
> type/mode while the interface is up.
>
> Antoine, did you bring the interface down before setting its mode?
Crap. No, I didn't. And now it works if I bring it down first. Oh well,
I guess I just made a lot of noise for nothing, this bug can be closed,
thank you!
A.
--
Travail, du latin Tri Palium trois pieux, instrument de torture.