Hi Kernel Wireless developers, I write here since I have an issue with this module.
We bought 2 of them since they are both 2.4 and 5Ghz capable, and they seem to be powerful enough for our pourposes
http://www.edimax.com/au/produce_detail.php?pd_id=399&pl1_id=1&pl2_id=44
Anyway there is a problem, that the linux kernel seems to be not supporting them
I tried following this guide
http://wikidevi.com/wiki/Edimax_EW-7733UnD
rt3573sta, possibly rt5572sta, and future support in rt2800usb "uhosg's patchset adding support, may be in by k3.12"
but at this moment it is showing an interface with one of them (I cannot connect to anything, the interface shown seems to be incorrect), with another I get a kernel anic and with the third one doesn't work at all.
lsusb |grep Edimax
Bus 002 Device 002: ID 7392:7733 Edimax Technology Co., Ltd
Are you guys working on it? How can I make it work? I'm open to patches, suggestions or whatever can help me in using them
thanks
(please cc me, I'm not yet subscribed to this list)
Gianfranco
>Aren't you trying to get a RT3573 card to work? You should activate
>CONFIG_RT2800USB_RT3573.
I'm rebuilding the kernel with this module, but I don't think this is my chip
http://www.edimax.com/au/produce_detail.php?pd_id=399&pl1_id=1&pl2_id=44
is it?
Thanks
Gianfranco
> Il Gioved? 31 Ottobre 2013 15:11, Hauke Mehrtens <[email protected]> ha scritto:
> > On 10/31/2013 02:56 PM, Gianfranco Costamagna wrote:
>>
>>
>>> Il Gioved? 24 Ottobre 2013 13:41, Stanislaw Gruszka
> <[email protected]> ha scritto:
>>>> On Thu, Oct 24, 2013 at 12:32:16PM +0100, Gianfranco Costamagna
> wrote:
>>>>
>>>>
>>>> ? Il Gioved? 24 Ottobre 2013 13:25, Stanislaw Gruszka
>>> <[email protected]> ha scritto:
>>>>
>>>> ? On Wed, Oct 23, 2013 at 03:27:49PM +0100, Gianfranco Costamagna
> wrote:
>>>> ? >
>>>> ? >> Hi Kernel Wireless developers, I write here since I have
> an issue
>>> with this module.
>>>> ? >>
>>>> ? >>
>>>> ? >> We bought 2 of them since they are both 2.4 and 5Ghz
> capable, and
>>> they seem to be powerful enough for our pourposes
>>>> ? >>
>>>
> http://www.edimax.com/au/produce_detail.php?pd_id=399&pl1_id=1&pl2_id=44
>>>> ? >>
>>>> ? >>
>>>> ? >> Anyway there is a problem, that the linux kernel seems to
> be not
>>> supporting them
>>>> ? >>
>>>> ? >> I tried following this guide
>>>> ? >> http://wikidevi.com/wiki/Edimax_EW-7733UnD
>>>> ? >> rt3573sta, possibly rt5572sta, and future support in
> rt2800usb
>>> "uhosg's patchset adding support, may be in by k3.12"
>>>> ? >> but at this moment it is showing an interface with one of
> them (I
>>> cannot connect to anything, the interface shown seems to be incorrect),
> with
>>> another I get a kernel anic and with the third one doesn't work at
> all.
>>>> ? >>
>>>> ? >> lsusb |grep Edimax
>>>> ? >>
>>>> ? >> Bus 002 Device 002: ID 7392:7733 Edimax Technology Co.,
> Ltd
>>>> ? >
>>>> ? >I have that exect device and it works ok here, but I'm
> using
>>>> ? >wireless-testing tree. So perhaps you should try install that
>>>> ? >tree or use backports .
>>>>
>>>>
>>>> ? Wonderful! I don't really understand what do you mean with
> backports,
>>> are you referring to "linux kernel backports" right?
>>>
>>> Yes.
>>>
>>>> ? So I can choose the backport source or to checkout and build the
>>> wireless-testing tree.
>>>>
>>>> ? Just as information, how long will it take to have it into the
> stable
>>> mainline?
>>>
>>> Current wireless-testing content will be available on 3.13 ,
>>> though I think that device should also work on 3.12 .
>>>
>>
>> Ok I built a custom kernel but I still have some issues
>> Ubuntu 13.10 x64
>> git clone
> http://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git
>> cd wireless-testing
>> copied my config from this kernel
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc7-saucy/
>>
>> make oldconfig
>> (a tail of my .config file after the make)
>> CONFIG_RT2800PCI=m
>> CONFIG_RT2800PCI_RT33XX=y
>> CONFIG_RT2800PCI_RT35XX=y
>> CONFIG_RT2800PCI_RT53XX=y
>> CONFIG_RT2800PCI_RT3290=y
>> CONFIG_RT2500USB=m
>> CONFIG_RT73USB=m
>> CONFIG_RT2800USB=m
>> CONFIG_RT2800USB_RT33XX=y
>> CONFIG_RT2800USB_RT35XX=y
>> # CONFIG_RT2800USB_RT3573 is not set
>
> Aren't you trying to get a RT3573 card to work? You should activate
>
> CONFIG_RT2800USB_RT3573.
>
>> CONFIG_RT2800USB_RT53XX=y
>> CONFIG_RT2800USB_RT55XX=y
>> CONFIG_RT2800USB_UNKNOWN=y
>> CONFIG_RT2800_LIB=m
>> CONFIG_RT2800_LIB_MMIO=m
>> CONFIG_RT2X00_LIB_MMIO=m
>> CONFIG_RT2X00_LIB_PCI=m
>> CONFIG_RT2X00_LIB_USB=m
>> CONFIG_RT2X00_LIB=m
>> CONFIG_RT2X00_LIB_FIRMWARE=y
>> CONFIG_RT2X00_LIB_CRYPTO=y
>> CONFIG_RT2X00_LIB_LEDS=y
>> # CONFIG_RT2X00_LIB_DEBUGFS is not set
>> # CONFIG_RT2X00_DEBUG is not set
>>
>> (apt-get build-dep linux)
>> make
>> make all
>> sudo make modules_install
>> sudo make install
>>
>> I was surprised that everything was automatically copied in /boot and grub
> automatically found the new kernel without manual mkinitrd anymore (so long time
> from my last kernel build)
>>
>> Reboot
>>
>> locutus@gianfranco-Latitude-E5520:~/wireless-testing$ uname -a
>> Linux gianfranco-Latitude-E5520 3.12.0-rc5-wl #2 SMP Thu Oct 31 14:04:43
> CET 2013 x86_64 x86_64 x86_64 GNU/Linux
>>
>>
>> put key in my pc
>> [? 471.585065] usb 2-1.2: new high-speed USB device number 11 using
> ehci-pci
>> [? 471.693762] usb 2-1.2: New USB device found, idVendor=7392,
> idProduct=7733
>> [? 471.693766] usb 2-1.2: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
>> [? 471.693768] usb 2-1.2: Product: 802.11 n WLAN
>> [? 471.693770] usb 2-1.2: Manufacturer: Ralink
>> [? 471.693771] usb 2-1.2: SerialNumber: 1.0
>>
>> sudo modprobe rt2800usb
>>
>> [? 540.170899] usbcore: registered new interface driver rt2800usb
>>
>> nothing works...
>>
>> Can you please help me again?
>>
>
On 10/31/2013 02:56 PM, Gianfranco Costamagna wrote:
>
>
>> Il Gioved? 24 Ottobre 2013 13:41, Stanislaw Gruszka <[email protected]> ha scritto:
>>> On Thu, Oct 24, 2013 at 12:32:16PM +0100, Gianfranco Costamagna wrote:
>>>
>>>
>>> Il Gioved? 24 Ottobre 2013 13:25, Stanislaw Gruszka
>> <[email protected]> ha scritto:
>>>
>>> On Wed, Oct 23, 2013 at 03:27:49PM +0100, Gianfranco Costamagna wrote:
>>> >
>>> >> Hi Kernel Wireless developers, I write here since I have an issue
>> with this module.
>>> >>
>>> >>
>>> >> We bought 2 of them since they are both 2.4 and 5Ghz capable, and
>> they seem to be powerful enough for our pourposes
>>> >>
>> http://www.edimax.com/au/produce_detail.php?pd_id=399&pl1_id=1&pl2_id=44
>>> >>
>>> >>
>>> >> Anyway there is a problem, that the linux kernel seems to be not
>> supporting them
>>> >>
>>> >> I tried following this guide
>>> >> http://wikidevi.com/wiki/Edimax_EW-7733UnD
>>> >> rt3573sta, possibly rt5572sta, and future support in rt2800usb
>> "uhosg's patchset adding support, may be in by k3.12"
>>> >> but at this moment it is showing an interface with one of them (I
>> cannot connect to anything, the interface shown seems to be incorrect), with
>> another I get a kernel anic and with the third one doesn't work at all.
>>> >>
>>> >> lsusb |grep Edimax
>>> >>
>>> >> Bus 002 Device 002: ID 7392:7733 Edimax Technology Co., Ltd
>>> >
>>> >I have that exect device and it works ok here, but I'm using
>>> >wireless-testing tree. So perhaps you should try install that
>>> >tree or use backports .
>>>
>>>
>>> Wonderful! I don't really understand what do you mean with backports,
>> are you referring to "linux kernel backports" right?
>>
>> Yes.
>>
>>> So I can choose the backport source or to checkout and build the
>> wireless-testing tree.
>>>
>>> Just as information, how long will it take to have it into the stable
>> mainline?
>>
>> Current wireless-testing content will be available on 3.13 ,
>> though I think that device should also work on 3.12 .
>>
>
> Ok I built a custom kernel but I still have some issues
> Ubuntu 13.10 x64
> git clone http://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git
> cd wireless-testing
> copied my config from this kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc7-saucy/
>
> make oldconfig
> (a tail of my .config file after the make)
> CONFIG_RT2800PCI=m
> CONFIG_RT2800PCI_RT33XX=y
> CONFIG_RT2800PCI_RT35XX=y
> CONFIG_RT2800PCI_RT53XX=y
> CONFIG_RT2800PCI_RT3290=y
> CONFIG_RT2500USB=m
> CONFIG_RT73USB=m
> CONFIG_RT2800USB=m
> CONFIG_RT2800USB_RT33XX=y
> CONFIG_RT2800USB_RT35XX=y
> # CONFIG_RT2800USB_RT3573 is not set
Aren't you trying to get a RT3573 card to work? You should activate
CONFIG_RT2800USB_RT3573.
> CONFIG_RT2800USB_RT53XX=y
> CONFIG_RT2800USB_RT55XX=y
> CONFIG_RT2800USB_UNKNOWN=y
> CONFIG_RT2800_LIB=m
> CONFIG_RT2800_LIB_MMIO=m
> CONFIG_RT2X00_LIB_MMIO=m
> CONFIG_RT2X00_LIB_PCI=m
> CONFIG_RT2X00_LIB_USB=m
> CONFIG_RT2X00_LIB=m
> CONFIG_RT2X00_LIB_FIRMWARE=y
> CONFIG_RT2X00_LIB_CRYPTO=y
> CONFIG_RT2X00_LIB_LEDS=y
> # CONFIG_RT2X00_LIB_DEBUGFS is not set
> # CONFIG_RT2X00_DEBUG is not set
>
> (apt-get build-dep linux)
> make
> make all
> sudo make modules_install
> sudo make install
>
> I was surprised that everything was automatically copied in /boot and grub automatically found the new kernel without manual mkinitrd anymore (so long time from my last kernel build)
>
> Reboot
>
> locutus@gianfranco-Latitude-E5520:~/wireless-testing$ uname -a
> Linux gianfranco-Latitude-E5520 3.12.0-rc5-wl #2 SMP Thu Oct 31 14:04:43 CET 2013 x86_64 x86_64 x86_64 GNU/Linux
>
>
> put key in my pc
> [ 471.585065] usb 2-1.2: new high-speed USB device number 11 using ehci-pci
> [ 471.693762] usb 2-1.2: New USB device found, idVendor=7392, idProduct=7733
> [ 471.693766] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [ 471.693768] usb 2-1.2: Product: 802.11 n WLAN
> [ 471.693770] usb 2-1.2: Manufacturer: Ralink
> [ 471.693771] usb 2-1.2: SerialNumber: 1.0
>
> sudo modprobe rt2800usb
>
> [ 540.170899] usbcore: registered new interface driver rt2800usb
>
> nothing works...
>
> Can you please help me again?
>
On Thu, Oct 31, 2013 at 4:37 PM, Gianfranco Costamagna
<[email protected]> wrote:
>
>>Aren't you trying to get a RT3573 card to work? You should activate
>>CONFIG_RT2800USB_RT3573.
>
>
> I'm rebuilding the kernel with this module, but I don't think this is my chip
> http://www.edimax.com/au/produce_detail.php?pd_id=399&pl1_id=1&pl2_id=44
>
> is it?
>
It should be, as it is the only Ralink chipset that supports 3x3
operation (i.e. 450 Mbps).
Also, the USB id of the device is listed in the driver under that
configuration option, so I'm pretty sure you
have to enable that configuration option ;-)
--
---
Gertjan
On Thu, Oct 31, 2013 at 2:56 PM, Gianfranco Costamagna
<[email protected]> wrote:
>
>
>> Il Gioved? 24 Ottobre 2013 13:41, Stanislaw Gruszka <[email protected]> ha scritto:
>> > On Thu, Oct 24, 2013 at 12:32:16PM +0100, Gianfranco Costamagna wrote:
>>>
>>>
>>> Il Gioved? 24 Ottobre 2013 13:25, Stanislaw Gruszka
>> <[email protected]> ha scritto:
>>>
>>> On Wed, Oct 23, 2013 at 03:27:49PM +0100, Gianfranco Costamagna wrote:
>>> >
>>> >> Hi Kernel Wireless developers, I write here since I have an issue
>> with this module.
>>> >>
>>> >>
>>> >> We bought 2 of them since they are both 2.4 and 5Ghz capable, and
>> they seem to be powerful enough for our pourposes
>>> >>
>> http://www.edimax.com/au/produce_detail.php?pd_id=399&pl1_id=1&pl2_id=44
>>> >>
>>> >>
>>> >> Anyway there is a problem, that the linux kernel seems to be not
>> supporting them
>>> >>
>>> >> I tried following this guide
>>> >> http://wikidevi.com/wiki/Edimax_EW-7733UnD
>>> >> rt3573sta, possibly rt5572sta, and future support in rt2800usb
>> "uhosg's patchset adding support, may be in by k3.12"
>>> >> but at this moment it is showing an interface with one of them (I
>> cannot connect to anything, the interface shown seems to be incorrect), with
>> another I get a kernel anic and with the third one doesn't work at all.
>>> >>
>>> >> lsusb |grep Edimax
>>> >>
>>> >> Bus 002 Device 002: ID 7392:7733 Edimax Technology Co., Ltd
>>> >
>>> >I have that exect device and it works ok here, but I'm using
>>> >wireless-testing tree. So perhaps you should try install that
>>> >tree or use backports .
>>>
>>>
>>> Wonderful! I don't really understand what do you mean with backports,
>> are you referring to "linux kernel backports" right?
>>
>> Yes.
>>
>>> So I can choose the backport source or to checkout and build the
>> wireless-testing tree.
>>>
>>> Just as information, how long will it take to have it into the stable
>> mainline?
>>
>> Current wireless-testing content will be available on 3.13 ,
>> though I think that device should also work on 3.12 .
>>
>
> Ok I built a custom kernel but I still have some issues
> Ubuntu 13.10 x64
> git clone http://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git
> cd wireless-testing
> copied my config from this kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc7-saucy/
>
> make oldconfig
> (a tail of my .config file after the make)
> CONFIG_RT2800PCI=m
> CONFIG_RT2800PCI_RT33XX=y
> CONFIG_RT2800PCI_RT35XX=y
> CONFIG_RT2800PCI_RT53XX=y
> CONFIG_RT2800PCI_RT3290=y
> CONFIG_RT2500USB=m
> CONFIG_RT73USB=m
> CONFIG_RT2800USB=m
> CONFIG_RT2800USB_RT33XX=y
> CONFIG_RT2800USB_RT35XX=y
> # CONFIG_RT2800USB_RT3573 is not set
You will have to enable this configuration item to make this device work.
> CONFIG_RT2800USB_RT53XX=y
> CONFIG_RT2800USB_RT55XX=y
> CONFIG_RT2800USB_UNKNOWN=y
> CONFIG_RT2800_LIB=m
> CONFIG_RT2800_LIB_MMIO=m
> CONFIG_RT2X00_LIB_MMIO=m
> CONFIG_RT2X00_LIB_PCI=m
> CONFIG_RT2X00_LIB_USB=m
> CONFIG_RT2X00_LIB=m
> CONFIG_RT2X00_LIB_FIRMWARE=y
> CONFIG_RT2X00_LIB_CRYPTO=y
> CONFIG_RT2X00_LIB_LEDS=y
> # CONFIG_RT2X00_LIB_DEBUGFS is not set
> # CONFIG_RT2X00_DEBUG is not set
>
> (apt-get build-dep linux)
> make
> make all
> sudo make modules_install
> sudo make install
>
> I was surprised that everything was automatically copied in /boot and grub automatically found the new kernel without manual mkinitrd anymore (so long time from my last kernel build)
>
> Reboot
>
> locutus@gianfranco-Latitude-E5520:~/wireless-testing$ uname -a
> Linux gianfranco-Latitude-E5520 3.12.0-rc5-wl #2 SMP Thu Oct 31 14:04:43 CET 2013 x86_64 x86_64 x86_64 GNU/Linux
>
>
> put key in my pc
> [ 471.585065] usb 2-1.2: new high-speed USB device number 11 using ehci-pci
> [ 471.693762] usb 2-1.2: New USB device found, idVendor=7392, idProduct=7733
> [ 471.693766] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [ 471.693768] usb 2-1.2: Product: 802.11 n WLAN
> [ 471.693770] usb 2-1.2: Manufacturer: Ralink
> [ 471.693771] usb 2-1.2: SerialNumber: 1.0
>
> sudo modprobe rt2800usb
>
> [ 540.170899] usbcore: registered new interface driver rt2800usb
>
> nothing works...
>
> Can you please help me again?
>
--
---
Gertjan
On Thu, Oct 24, 2013 at 12:32:16PM +0100, Gianfranco Costamagna wrote:
>
>
> Il Gioved? 24 Ottobre 2013 13:25, Stanislaw Gruszka <[email protected]> ha scritto:
>
> On Wed, Oct 23, 2013 at 03:27:49PM +0100, Gianfranco Costamagna wrote:
> >
> >> Hi Kernel Wireless developers, I write here since I have an issue with this module.
> >>
> >>
> >> We bought 2 of them since they are both 2.4 and 5Ghz capable, and they seem to be powerful enough for our pourposes
> >> http://www.edimax.com/au/produce_detail.php?pd_id=399&pl1_id=1&pl2_id=44
> >>
> >>
> >> Anyway there is a problem, that the linux kernel seems to be not supporting them
> >>
> >> I tried following this guide
> >> http://wikidevi.com/wiki/Edimax_EW-7733UnD
> >> rt3573sta, possibly rt5572sta, and future support in rt2800usb "uhosg's patchset adding support, may be in by k3.12"
> >> but at this moment it is showing an interface with one of them (I cannot connect to anything, the interface shown seems to be incorrect), with another I get a kernel anic and with the third one doesn't work at all.
> >>
> >> lsusb |grep Edimax
> >>
> >> Bus 002 Device 002: ID 7392:7733 Edimax Technology Co., Ltd
> >
> >I have that exect device and it works ok here, but I'm using
> >wireless-testing tree. So perhaps you should try install that
> >tree or use backports .
>
>
> Wonderful! I don't really understand what do you mean with backports, are you referring to "linux kernel backports" right?
Yes.
> So I can choose the backport source or to checkout and build the wireless-testing tree.
>
> Just as information, how long will it take to have it into the stable mainline?
Current wireless-testing content will be available on 3.13 ,
though I think that device should also work on 3.12 .
Stanislaw
On 10/23/2013 09:27 AM, Gianfranco Costamagna wrote:
> Hi Kernel Wireless developers, I write here since I have an issue with this module.
>
>
> We bought 2 of them since they are both 2.4 and 5Ghz capable, and they seem to be powerful enough for our pourposes
> http://www.edimax.com/au/produce_detail.php?pd_id=399&pl1_id=1&pl2_id=44
>
>
> Anyway there is a problem, that the linux kernel seems to be not supporting them
>
> I tried following this guide
> http://wikidevi.com/wiki/Edimax_EW-7733UnD
> rt3573sta, possibly rt5572sta, and future support in rt2800usb "uhosg's patchset adding support, may be in by k3.12"
> but at this moment it is showing an interface with one of them (I cannot connect to anything, the interface shown seems to be incorrect), with another I get a kernel anic and with the third one doesn't work at all.
>
> lsusb |grep Edimax
>
> Bus 002 Device 002: ID 7392:7733 Edimax Technology Co., Ltd
>
> Are you guys working on it? How can I make it work? I'm open to patches, suggestions or whatever can help me in using them
That device was added to the kernel version of rt2800usb in July of 2013, and it
is in version 3.12-rc6. You can either generate that kernel for your system, or
you could get the latest backports source and build it.
I am not an expert on the rt2x00 drivers, and I have no idea if it works.
Larry
> Il Gioved? 24 Ottobre 2013 13:41, Stanislaw Gruszka <[email protected]> ha scritto:
> > On Thu, Oct 24, 2013 at 12:32:16PM +0100, Gianfranco Costamagna wrote:
>>
>>
>> Il Gioved? 24 Ottobre 2013 13:25, Stanislaw Gruszka
> <[email protected]> ha scritto:
>>
>> On Wed, Oct 23, 2013 at 03:27:49PM +0100, Gianfranco Costamagna wrote:
>> >
>> >> Hi Kernel Wireless developers, I write here since I have an issue
> with this module.
>> >>
>> >>
>> >> We bought 2 of them since they are both 2.4 and 5Ghz capable, and
> they seem to be powerful enough for our pourposes
>> >>
> http://www.edimax.com/au/produce_detail.php?pd_id=399&pl1_id=1&pl2_id=44
>> >>
>> >>
>> >> Anyway there is a problem, that the linux kernel seems to be not
> supporting them
>> >>
>> >> I tried following this guide
>> >> http://wikidevi.com/wiki/Edimax_EW-7733UnD
>> >> rt3573sta, possibly rt5572sta, and future support in rt2800usb
> "uhosg's patchset adding support, may be in by k3.12"
>> >> but at this moment it is showing an interface with one of them (I
> cannot connect to anything, the interface shown seems to be incorrect), with
> another I get a kernel anic and with the third one doesn't work at all.
>> >>
>> >> lsusb |grep Edimax
>> >>
>> >> Bus 002 Device 002: ID 7392:7733 Edimax Technology Co., Ltd
>> >
>> >I have that exect device and it works ok here, but I'm using
>> >wireless-testing tree. So perhaps you should try install that
>> >tree or use backports .
>>
>>
>> Wonderful! I don't really understand what do you mean with backports,
> are you referring to "linux kernel backports" right?
>
> Yes.
>
>> So I can choose the backport source or to checkout and build the
> wireless-testing tree.
>>
>> Just as information, how long will it take to have it into the stable
> mainline?
>
> Current wireless-testing content will be available on 3.13 ,
> though I think that device should also work on 3.12 .
>
Ok I built a custom kernel but I still have some issues
Ubuntu 13.10 x64
git clone http://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git
cd wireless-testing
copied my config from this kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc7-saucy/
make oldconfig
(a tail of my .config file after the make)
CONFIG_RT2800PCI=m
CONFIG_RT2800PCI_RT33XX=y
CONFIG_RT2800PCI_RT35XX=y
CONFIG_RT2800PCI_RT53XX=y
CONFIG_RT2800PCI_RT3290=y
CONFIG_RT2500USB=m
CONFIG_RT73USB=m
CONFIG_RT2800USB=m
CONFIG_RT2800USB_RT33XX=y
CONFIG_RT2800USB_RT35XX=y
# CONFIG_RT2800USB_RT3573 is not set
CONFIG_RT2800USB_RT53XX=y
CONFIG_RT2800USB_RT55XX=y
CONFIG_RT2800USB_UNKNOWN=y
CONFIG_RT2800_LIB=m
CONFIG_RT2800_LIB_MMIO=m
CONFIG_RT2X00_LIB_MMIO=m
CONFIG_RT2X00_LIB_PCI=m
CONFIG_RT2X00_LIB_USB=m
CONFIG_RT2X00_LIB=m
CONFIG_RT2X00_LIB_FIRMWARE=y
CONFIG_RT2X00_LIB_CRYPTO=y
CONFIG_RT2X00_LIB_LEDS=y
# CONFIG_RT2X00_LIB_DEBUGFS is not set
# CONFIG_RT2X00_DEBUG is not set
(apt-get build-dep linux)
make
make all
sudo make modules_install
sudo make install
I was surprised that everything was automatically copied in /boot and grub automatically found the new kernel without manual mkinitrd anymore (so long time from my last kernel build)
Reboot
locutus@gianfranco-Latitude-E5520:~/wireless-testing$ uname -a
Linux gianfranco-Latitude-E5520 3.12.0-rc5-wl #2 SMP Thu Oct 31 14:04:43 CET 2013 x86_64 x86_64 x86_64 GNU/Linux
put key in my pc
[? 471.585065] usb 2-1.2: new high-speed USB device number 11 using ehci-pci
[? 471.693762] usb 2-1.2: New USB device found, idVendor=7392, idProduct=7733
[? 471.693766] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[? 471.693768] usb 2-1.2: Product: 802.11 n WLAN
[? 471.693770] usb 2-1.2: Manufacturer: Ralink
[? 471.693771] usb 2-1.2: SerialNumber: 1.0
sudo modprobe rt2800usb
[? 540.170899] usbcore: registered new interface driver rt2800usb
nothing works...
Can you please help me again?
Many thanks
have a nice day,
Gianfranco
>
> Stanislaw?
>
Il Gioved? 24 Ottobre 2013 13:25, Stanislaw Gruszka <[email protected]> ha scritto:
On Wed, Oct 23, 2013 at 03:27:49PM +0100, Gianfranco Costamagna wrote:
>
>> Hi Kernel Wireless developers, I write here since I have an issue with this module.
>>
>>
>> We bought 2 of them since they are both 2.4 and 5Ghz capable, and they seem to be powerful enough for our pourposes
>> http://www.edimax.com/au/produce_detail.php?pd_id=399&pl1_id=1&pl2_id=44
>>
>>
>> Anyway there is a problem, that the linux kernel seems to be not supporting them
>>
>> I tried following this guide
>> http://wikidevi.com/wiki/Edimax_EW-7733UnD
>> rt3573sta, possibly rt5572sta, and future support in rt2800usb "uhosg's patchset adding support, may be in by k3.12"
>> but at this moment it is showing an interface with one of them (I cannot connect to anything, the interface shown seems to be incorrect), with another I get a kernel anic and with the third one doesn't work at all.
>>
>> lsusb |grep Edimax
>>
>> Bus 002 Device 002: ID 7392:7733 Edimax Technology Co., Ltd
>
>I have that exect device and it works ok here, but I'm using
>wireless-testing tree. So perhaps you should try install that
>tree or use backports .
Wonderful! I don't really understand what do you mean with backports, are you referring to "linux kernel backports" right?
So I can choose the backport source or to checkout and build the wireless-testing tree.
Just as information, how long will it take to have it into the stable mainline?
How does the merge works?
(just because I don't want to build a custom kernel if not really needed I use the rc kernels packaged by ubuntu team
http://kernel.ubuntu.com/~kernel-ppa/mainline/ )
many thanks
Gianfranco
>
>Stanislaw
>
>
>
>
On Wed, Oct 23, 2013 at 03:27:49PM +0100, Gianfranco Costamagna wrote:
> Hi Kernel Wireless developers, I write here since I have an issue with this module.
>
>
> We bought 2 of them since they are both 2.4 and 5Ghz capable, and they seem to be powerful enough for our pourposes
> http://www.edimax.com/au/produce_detail.php?pd_id=399&pl1_id=1&pl2_id=44
>
>
> Anyway there is a problem, that the linux kernel seems to be not supporting them
>
> I tried following this guide
> http://wikidevi.com/wiki/Edimax_EW-7733UnD
> rt3573sta, possibly rt5572sta, and future support in rt2800usb "uhosg's patchset adding support, may be in by k3.12"
> but at this moment it is showing an interface with one of them (I cannot connect to anything, the interface shown seems to be incorrect), with another I get a kernel anic and with the third one doesn't work at all.
>
> lsusb |grep Edimax
>
> Bus 002 Device 002: ID 7392:7733 Edimax Technology Co., Ltd
I have that exect device and it works ok here, but I'm using
wireless-testing tree. So perhaps you should try install that
tree or use backports .
Stanislaw
On Thu, Oct 31, 2013 at 01:56:54PM +0000, Gianfranco Costamagna wrote:
> put key in my pc
> [? 471.585065] usb 2-1.2: new high-speed USB device number 11 using ehci-pci
> [? 471.693762] usb 2-1.2: New USB device found, idVendor=7392, idProduct=7733
> [? 471.693766] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [? 471.693768] usb 2-1.2: Product: 802.11 n WLAN
> [? 471.693770] usb 2-1.2: Manufacturer: Ralink
> [? 471.693771] usb 2-1.2: SerialNumber: 1.0
>
> sudo modprobe rt2800usb
>
> [? 540.170899] usbcore: registered new interface driver rt2800usb
>
> nothing works...
>
> Can you please help me again?
Lack of firmware ? Also check if device support is really compiled in
the module - "modinfo rt2800usb | grep 7733" should show device id.
Stanislaw
> Il Gioved? 31 Ottobre 2013 16:49, Gertjan van Wingerde <[email protected]> ha scritto:
> > On Thu, Oct 31, 2013 at 4:37 PM, Gianfranco Costamagna
>
> <[email protected]> wrote:
>>
>>> Aren't you trying to get a RT3573 card to work? You should activate
>>> CONFIG_RT2800USB_RT3573.
>>
>>
>> I'm rebuilding the kernel with this module, but I don't think this
> is my chip
>>
> http://www.edimax.com/au/produce_detail.php?pd_id=399&pl1_id=1&pl2_id=44
>>
>> is it?
>>
>
> It should be, as it is the only Ralink chipset that supports 3x3
> operation (i.e. 450 Mbps).
> Also, the USB id of the device is listed in the driver under that
> configuration option, so I'm pretty sure you
> have to enable that configuration option ;-)
>
Yep indeed, after enabling it everything was fine :)
So maybe ubuntu kernel developers disable the module by default? In this case I'll ask them to enable it...
Last question, is it normal than disabling the wifi switch (hardware) on my laptop also the usb key gets disabled?
I think I also had to modprobe rt2800usb for enabling it... don't know
Linux gianfranco-Latitude-E5520 3.12.0-rc5-wl #3 SMP Thu Oct 31 16:17:50 CET 2013 x86_64 x86_64 x86_64 GNU/Linux
[? 741.973598] usb 2-1.4: new high-speed USB device number 14 using ehci-pci
[? 742.082098] usb 2-1.4: New USB device found, idVendor=7392, idProduct=7733
[? 742.082103] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[? 742.082105] usb 2-1.4: Product: 802.11 n WLAN
[? 742.082107] usb 2-1.4: Manufacturer: Ralink
[? 742.082109] usb 2-1.4: SerialNumber: 1.0
[? 742.157836] usb 2-1.4: reset high-speed USB device number 14 using ehci-pci
[? 742.259161] ieee80211 phy6: rt2x00_set_rt: Info - RT chipset 3593, rev 0402 detected
[? 742.287567] ieee80211 phy6: rt2x00_set_rf: Info - RF chipset 000d detected
[? 742.287949] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht'
[? 742.305198] ieee80211 phy6: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[? 742.305226] ieee80211 phy6: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.29
[? 742.558830] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[? 749.516755] wlan1: authenticate with 90:f6:52:3b:2c:88
[? 749.601351] wlan1: send auth to 90:f6:52:3b:2c:88 (try 1/3)
[? 749.706159] wlan1: send auth to 90:f6:52:3b:2c:88 (try 2/3)
[? 749.709059] wlan1: authenticated
[? 749.710172] wlan1: associate with 90:f6:52:3b:2c:88 (try 1/3)
[? 749.714112] wlan1: RX AssocResp from 90:f6:52:3b:2c:88 (capab=0x431 status=0 aid=4)
[? 749.721140] wlan1: associated
[? 749.721172] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[? 749.721258] cfg80211: Calling CRDA for country: IT
[? 749.724127] cfg80211: Regulatory domain changed to country: IT
[? 749.724131] cfg80211:?? (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[? 749.724132] cfg80211:?? (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[? 749.724134] cfg80211:?? (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[? 749.724135] cfg80211:?? (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[? 749.724136] cfg80211:?? (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
[? 749.724137] cfg80211:?? (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
Thanks for your help!
I really appreciated it ;)
Cheers!
Gianfranco
> --
> ---
> Gertjan
>