Hi,
I just baught a Sitecom WL-608 USB WIFI dongle and it seems it isn't supported out of the box yet. Here is some info on the device:
http://www.sitecom.com/product.php?productname=Wireless+USB+Adapter+54g&productcode=WL-608&productid=709&inactive=1
Bus 001 Device 024: ID 0df6:003f Sitecom Europe B.V.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0df6 Sitecom Europe B.V.
idProduct 0x003f
bcdDevice 1.01
iManufacturer 1 Ralink
iProduct 2 802.11 g WLAN
iSerial 3 1.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 450mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 7
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 5 1.0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
It look like this device uses a RaLink chip. How do I go about to find out which one?
Thanks,
--
Christoph .J Thompson <[email protected]>
Hi,
On Thu, Feb 12, 2009 at 08:43, Christoph .J Thompson
<[email protected]> wrote:
> On Thu, 12 Feb 2009 08:05:48 +0000
> Luis Correia <[email protected]> wrote:
>> can any brave soul have the guts to pry open this USB stick and look
>> at the chip?
>>
>> That was, we all would be sure of it's origins :)
>>
>> Luis Correia
>
> I did it, it was quite easy without damaging it. This was written on the chip inside:
>
> Ralink
> RT2070L
> PB49460ED
> 0841ST
>
> Did they do a typo?
Probably, it should probably be RT2870L :)
But yes, looks like rt2800usb.
Luis Correia
On Thu, 12 Feb 2009 09:00:27 +0100
Ivo Van Doorn <[email protected]> wrote:
> On Thu, Feb 12, 2009 at 4:22 AM, Christoph .J Thompson
> Hmm thats weird, I couldn't find the reference that it is a 11n device. :S
> Anyway, I'll add the USB ID to rt2800usb.
>
> Ivo
What tiped me was that the string 2870 could be found in the MacOS X dmg driver file name available for download for this WL-608 card on Sitecom's website. So I guess my dreams of Access Point are over now :s By any chance, could you recommend a small form factor USB WiFi dongle that works for that purpose?
--
Christoph .J Thompson <[email protected]>
Hi,
On Thu, Feb 12, 2009 at 08:00, Ivo Van Doorn <[email protected]> wrote:
> On Thu, Feb 12, 2009 at 4:22 AM, Christoph .J Thompson
> <[email protected]> wrote:
>> Further research suggest this WiFi dongle has the RT2870 chipset, it works with the RaLink driver once the id has been added to it.
>
> Hmm thats weird, I couldn't find the reference that it is a 11n device. :S
> Anyway, I'll add the USB ID to rt2800usb.
>
> Ivo
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
can any brave soul have the guts to pry open this USB stick and look
at the chip?
That was, we all would be sure of it's origins :)
Luis Correia
On Thu, 12 Feb 2009 09:40:22 +0100
Ivo Van Doorn <[email protected]> wrote:
> As far as I know the rt2870 driver provided by Ralink contains support
> for Master mode, and it should even cooperate with hostapd. Not sure
> if anybody has tested that yet. But you could give it a try.
I've looked at the RaLink 1.4.0.0 driver for the rt2870usb available on RaLink's
website and there is only station mode support. Maybe I'm missing something and
there is a fork or older driver with AP support?
> Otherwise
> you can check rt2x00.git to see if the rt2800usb driver can send out
> beacons correctly. So far I have only tested managed mode and that
> worked reasonable (if you ignore the lack of 11n AP scan results, and
> some startup kickups). Note that you should use the module parameter
> nohwcrypt for rt2800usb to disable HW crypto.
I think I'll have to resort to that. Sorry if the question is stupid, but
what version of the kernel is in rt2x00.git? Can I backport the changes
to 2.6.28.4 by making a diff between rt2x00.git's drivers/net/wireless
and 2.6.28.4's drivers/net/wireless directory?
--
Christoph .J Thompson <[email protected]>
On Wed, 11 Feb 2009 23:32:53 +0100
Ivo van Doorn <[email protected]> wrote:
> Hi,
>
> Looks like a new USB id. Since it isn't an 11n device it can only be a rt73usb or rt2500usb device.
> Could you try below patch? My current bet is that the device contains the rt73 chipset,
> so this will enable rt73usb to use the device.
I have tried to add the id of the Sitecom WL-608 to the rt73usb, rt2500usb and zd1211rw drivers but so far no luck. I turned debugging on for the aforementioned drivers and here is what I got:
phy4 -> rt73usb_validate_eeprom: EEPROM recovery - Antenna: 0x09aa
phy4 -> rt73usb_validate_eeprom: EEPROM recovery - NIC: 0xffef
phy4 -> rt73usb_validate_eeprom: EEPROM recovery - RSSI OFFSET BG: 0x0000
phy4 -> rt73usb_validate_eeprom: EEPROM recovery - RSSI OFFSET A: 0x0000
phy4 -> rt2x00_set_chip: Info - Chipset detected - rt: 1300, rf: 0001, rev: d5af900a.
phy4 -> rt73usb_init_eeprom: Error - Invalid RT chipset detected.
phy4 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
usbcore: registered new interface driver rt73usb
phy5 -> rt2500usb_validate_eeprom: EEPROM recovery - Antenna: 0x0002
phy5 -> rt2500usb_validate_eeprom: EEPROM recovery - NIC: 0xfff0
phy5 -> rt2x00_set_chip: Info - Chipset detected - rt: 1201, rf: 0000, rev: 00002080.
phy5 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected.
phy5 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
usbcore: registered new interface driver rt2500usb
zd1211rw usb_init()
usb 1-1.1: print_id() 0df6:003f v0101 high
usb 1-1.1: reset high speed USB device using ehci_hcd and address 6
zd1211rw 1-1.1:1.0: zd_chip_read_mac_addr_fw()
usb 1-1.1: read over firmware interface failed: -32
zd1211rw 1-1.1:1.0: probe() couldn't initialize mac. Error number -32
usb 1-1.1: reset high speed USB device using ehci_hcd and address 6
zd1211rw: probe of 1-1.1:1.0 failed with error -32
usbcore: registered new interface driver zd1211rw
zd1211rw initialized
--
Christoph .J Thompson <[email protected]>
Further research suggest this WiFi dongle has the RT2870 chipset, it works with the RaLink driver once the id has been added to it.
--
Christoph .J Thompson <[email protected]>
I added the WL-603 to the zd1211rw driver in wireless-testing a couple
of weeks. ago.
zd1211rw: adding Sitecom WL-603 (0df6:0036) to the USB id list
Here was the entry - could you try adding a similiar line (using
0x003f for your device, instead of 0x0036 shown here) and report back
if the WL608 is similiar to the WL 603 except by the ID?
diff --git a/drivers/net/wireless/zd1211rw/zd_usb.c
b/drivers/net/wireless/zd1211rw/zd_usb.c
index b5db57d..17527f7 100644
--- a/drivers/net/wireless/zd1211rw/zd_usb.c
+++ b/drivers/net/wireless/zd1211rw/zd_usb.c
@@ -84,6 +84,7 @@ static struct usb_device_id usb_ids[] = {
{ USB_DEVICE(0x0586, 0x340a), .driver_info = DEVICE_ZD1211B },
{ USB_DEVICE(0x0471, 0x1237), .driver_info = DEVICE_ZD1211B },
{ USB_DEVICE(0x07fa, 0x1196), .driver_info = DEVICE_ZD1211B },
+ { USB_DEVICE(0x0df6, 0x0036), .driver_info = DEVICE_ZD1211B },
/* "Driverless" devices that need ejecting */
{ USB_DEVICE(0x0ace, 0x2011), .driver_info = DEVICE_INSTALLER },
{ USB_DEVICE(0x0ace, 0x20ff), .driver_info = DEVICE_INSTALLER },
On Wed, Feb 11, 2009 at 10:32 PM, Ivo van Doorn <[email protected]> wrote:
> Hi,
>
>> I just baught a Sitecom WL-608 USB WIFI dongle and it seems it isn't supported out of the box yet. Here is some info on the device:
>
> Looks like a new USB id. Since it isn't an 11n device it can only be a rt73usb or rt2500usb device.
> Could you try below patch? My current bet is that the device contains the rt73 chipset,
> so this will enable rt73usb to use the device.
>
> Ivo
>
> ---
>
> diff --git a/drivers/net/wireless/rt2x00/rt73usb.c b/drivers/net/wireless/rt2x00/rt73usb.c
> index 846996c..84f2ee8 100644
> --- a/drivers/net/wireless/rt2x00/rt73usb.c
> +++ b/drivers/net/wireless/rt2x00/rt73usb.c
> @@ -2398,6 +2398,7 @@ static struct usb_device_id rt73usb_device_table[] = {
> /* Senao */
> { USB_DEVICE(0x1740, 0x7100), USB_DEVICE_DATA(&rt73usb_ops) },
> /* Sitecom */
> + { USB_DEVICE(0x0df6, 0x003f), USB_DEVICE_DATA(&rt73usb_ops) },
> { USB_DEVICE(0x0df6, 0x9712), USB_DEVICE_DATA(&rt73usb_ops) },
> { USB_DEVICE(0x0df6, 0x90ac), USB_DEVICE_DATA(&rt73usb_ops) },
> /* Surecom */
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
On Thu, 12 Feb 2009 08:05:48 +0000
Luis Correia <[email protected]> wrote:
> can any brave soul have the guts to pry open this USB stick and look
> at the chip?
>
> That was, we all would be sure of it's origins :)
>
> Luis Correia
I did it, it was quite easy without damaging it. This was written on the chip inside:
Ralink
RT2070L
PB49460ED
0841ST
Did they do a typo?
--
Christoph .J Thompson <[email protected]>
On Thursday 12 February 2009, Christoph .J Thompson wrote:
> On Thu, 12 Feb 2009 09:40:22 +0100
> Ivo Van Doorn <[email protected]> wrote:
> > As far as I know the rt2870 driver provided by Ralink contains support
> > for Master mode, and it should even cooperate with hostapd. Not sure
> > if anybody has tested that yet. But you could give it a try.
>
> I've looked at the RaLink 1.4.0.0 driver for the rt2870usb available on RaLink's
> website and there is only station mode support. Maybe I'm missing something and
> there is a fork or older driver with AP support?
Hmm, the driver does contain comments and some code for master mode,
so perhaps the implementation isn't complete or indeed restricted to an
internal or private version of the driver.
> > Otherwise
> > you can check rt2x00.git to see if the rt2800usb driver can send out
> > beacons correctly. So far I have only tested managed mode and that
> > worked reasonable (if you ignore the lack of 11n AP scan results, and
> > some startup kickups). Note that you should use the module parameter
> > nohwcrypt for rt2800usb to disable HW crypto.
>
> I think I'll have to resort to that. Sorry if the question is stupid, but
> what version of the kernel is in rt2x00.git? Can I backport the changes
> to 2.6.28.4 by making a diff between rt2x00.git's drivers/net/wireless
> and 2.6.28.4's drivers/net/wireless directory?
rt2x00.git = wireless-testing + rt2800usb
So that makes it 2.6.29-rcx.
It won't be possible to copy the drivers only, you need to copy mac80211
as well, and even then you might run into problems for other API changes.
You might want to grab the compat-wireless testing package, copy the drivers/net/wireless/rt2x00
sourcecode into the compat-wireless folder (just override the existing rt2x00 code). After that it
might be needed to update some Makefiles and config options, but that shouldn't be too hard.
Ivo
On Thu, Feb 12, 2009 at 4:22 AM, Christoph .J Thompson
<[email protected]> wrote:
> Further research suggest this WiFi dongle has the RT2870 chipset, it works with the RaLink driver once the id has been added to it.
Hmm thats weird, I couldn't find the reference that it is a 11n device. :S
Anyway, I'll add the USB ID to rt2800usb.
Ivo
On Thu, Feb 12, 2009 at 9:26 AM, Christoph .J Thompson
<[email protected]> wrote:
> On Thu, 12 Feb 2009 09:00:27 +0100
> Ivo Van Doorn <[email protected]> wrote:
>
>> On Thu, Feb 12, 2009 at 4:22 AM, Christoph .J Thompson
>> Hmm thats weird, I couldn't find the reference that it is a 11n device. :S
>> Anyway, I'll add the USB ID to rt2800usb.
>>
>> Ivo
>
> What tiped me was that the string 2870 could be found in the MacOS X dmg driver file name available for download for this WL-608 card on Sitecom's website. So I guess my dreams of Access Point are over now :s By any chance, could you recommend a small form factor USB WiFi dongle that works for that purpose?
As far as I know the rt2870 driver provided by Ralink contains support
for Master mode, and it should even cooperate with hostapd. Not sure
if anybody has tested that yet. But you could give it a try. Otherwise
you can check rt2x00.git to see if the rt2800usb driver can send out
beacons correctly. So far I have only tested managed mode and that
worked reasonable (if you ignore the lack of 11n AP scan results, and
some startup kickups). Note that you should use the module parameter
nohwcrypt for rt2800usb to disable HW crypto.
Ivo
On Wed, 11 Feb 2009 22:51:29 +0000
Hin-Tak Leung <[email protected]> wrote:
> I added the WL-603 to the zd1211rw driver in wireless-testing a couple
> of weeks. ago.
> zd1211rw: adding Sitecom WL-603 (0df6:0036) to the USB id list
>
> Here was the entry - could you try adding a similiar line (using
> 0x003f for your device, instead of 0x0036 shown here) and report back
> if the WL608 is similiar to the WL 603 except by the ID?
No problem, I will try it and report back.
--
Christoph .J Thompson <[email protected]>
Hi,
> I just baught a Sitecom WL-608 USB WIFI dongle and it seems it isn't supported out of the box yet. Here is some info on the device:
Looks like a new USB id. Since it isn't an 11n device it can only be a rt73usb or rt2500usb device.
Could you try below patch? My current bet is that the device contains the rt73 chipset,
so this will enable rt73usb to use the device.
Ivo
---
diff --git a/drivers/net/wireless/rt2x00/rt73usb.c b/drivers/net/wireless/rt2x00/rt73usb.c
index 846996c..84f2ee8 100644
--- a/drivers/net/wireless/rt2x00/rt73usb.c
+++ b/drivers/net/wireless/rt2x00/rt73usb.c
@@ -2398,6 +2398,7 @@ static struct usb_device_id rt73usb_device_table[] = {
/* Senao */
{ USB_DEVICE(0x1740, 0x7100), USB_DEVICE_DATA(&rt73usb_ops) },
/* Sitecom */
+ { USB_DEVICE(0x0df6, 0x003f), USB_DEVICE_DATA(&rt73usb_ops) },
{ USB_DEVICE(0x0df6, 0x9712), USB_DEVICE_DATA(&rt73usb_ops) },
{ USB_DEVICE(0x0df6, 0x90ac), USB_DEVICE_DATA(&rt73usb_ops) },
/* Surecom */
Or maybe someone has the fcc id. FCC website provide internal pictures
of wireless adapters (if they have such id of course).
Thomas
On Thu, Feb 12, 2009 at 2:05 AM, Luis Correia <[email protected]=
> wrote:
> Hi,
>
> On Thu, Feb 12, 2009 at 08:00, Ivo Van Doorn <[email protected]> wrot=
e:
>> On Thu, Feb 12, 2009 at 4:22 AM, Christoph .J Thompson
>> <[email protected]> wrote:
>>> Further research suggest this WiFi dongle has the RT2870 chipset, i=
t works with the RaLink driver once the id has been added to it.
>>
>> Hmm thats weird, I couldn't find the reference that it is a 11n devi=
ce. :S
>> Anyway, I'll add the USB ID to rt2800usb.
>>
>> Ivo
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wire=
less" in
>> the body of a message to [email protected]
>> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html
>>
>
> can any brave soul have the guts to pry open this USB stick and look
> at the chip?
>
> That was, we all would be sure of it's origins :)
>
> Luis Correia
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wirel=
ess" in
> the body of a message to [email protected]
> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html
>