Forum Topic - Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3):
   
Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Hi All,

Does anyone know when/if the Ralink RT2800U chipset is on the roadmap in terms of driver availability for QNX?

The reason I ask is because originally I evaluated the use of thee Linksys WUSB54GC USB adapter for development purposes
 (version 1 with the Ralink RT2501USB chipset) which worked well, however unfortunately this part is now obsolete and no
 longer made.  As a result the new version of the Linksys WUSB54GC USB adapters (version 3 with the RT2800U chipsets) is
 as yet not supported within QNX.

Cheers,
Radek.
RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
The io-pkt ral driver is a BSD source driver - 
we didn't write it.  I will check the BSD source
to see if there is an update coming.

--
aboyd
Re: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Hi Andrew,

That's excellent news.  I just check the Open BSD archives and the RT2800U has been supported since 4.3. 


One mirror I found that holds the file that contains the appropriate source is:
ftp://mirror.pacific.net.au/OpenBSD/4.5/sys.tar.gz

For the correct source for RT2800U look under the path (within the archive):
\sys\dev\usb\if_run.c
\sys\dev\usb\ifrunvar.h


Is it possible to have it built?

Cheers,
Radek.
RE: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Stand by ...

--
aboyd
RE: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Slight complication.  This is not a simple re-compile. 

That is an OPEN bsd driver, not a NET bsd driver.  

I couldn't find a NET bsd if_run.c driver source, 
so I am attempting to port the OPEN bsd driver to 
our modified NET bsd infrastructure.

At first glance, there are differences in how system
timeouts are implemented, and in the 802.11 stack.

Stay tuned.

--
aboyd
Re: RE: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Thanks alot for the update Andrew - I'll stay tuned and keep my fingers crossed.

Radek.
RE: RE: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Update: I haven't forgotten about this (though I 
sure can get distracted, but not often by alien
green women :)
 
I ported the OpenBSD driver, got a clean compile,
and it initializes - oddly, I had to add a new
device type for the cisco/linksys WUSB54GC, which
I got two of from shoprbc.com (thx bert) - and it 
initializes, reads the eeprom correctly, downloads 
the 8051 microcode, etc.

When I do a 

  # ifconfig run0 up

I get an inscrutable USB error, which I need to
track down.

I think it's important for us to have support 
for some common and current USB/wifi adapters,
so I will try my best to make this work.  I don't
think I'm all that far off - it's mostly a matter
of tracking down annoying differences between
NetBSD and OpenBSD.

--
aboyd
Re: RE: RE: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Hehe, I'm a little lost as to where the alien green women came from, but thanks for not giving up on me yet! :)  I'll 
continue to keep my fingers crossed and hope it all starts to work soon.

Cheers,
Radek.
 
Re: RE: RE: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Hi Andrew,

I'm just writing to see if you've had had any time to progress further with the RT2800 chipset? :)

Cheers,
Radek.

RE: RE: RE: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
I'm working on something else right now, but I 
hope to get back on this soon.  I actually checked
the code in, which is always a good sign  :-)

--
aboyd
Re: RE: RE: RE: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Hi Andrew,

I know this thread is now quite old, however we'd still love the ability to use the RT2800U wireless chipsets within QNX
 and I see that sufficient time has passed for NETBsd to now have versions of if_run.c that contain support for the 
RT2800U. Any chance the driiver will be ported to QNX some time soon?

Cheers,
Radek.
RE: RE: RE: RE: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Hi Radek - I think Yao was making commits
to if_run.c for the ral 2800/2900/3000.

--
aboyd

-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com] 
Sent: Tuesday, April 13, 2010 8:06 PM
To: drivers-networking
Subject: Re: RE: RE: RE: RE: Support for Ralink RT2800U Chipset(Linksys
WUSB54GCV3)

Hi Andrew,

I know this thread is now quite old, however we'd still love the ability
to use the RT2800U wireless chipsets within QNX and I see that
sufficient time has passed for NETBsd to now have versions of if_run.c
that contain support for the RT2800U. Any chance the driiver will be
ported to QNX some time soon?

Cheers,
Radek.



_______________________________________________

Networking Drivers
http://community.qnx.com/sf/go/post51613
RE: RE: RE: RE: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Excellent.

I tried an SVN checkout of the networking project however receive an unauthorized access error:

svn checkout --username radek-pesina@swsa.com.au http://community.qnx.com/svn/repos/core_networking/trunk/lib
svn: Not authorized to open root of edit operation

Is there a way I can get access to the driver?

Cheers,
Radek.



-----Original Message-----
From: Andrew Boyd [mailto:community-noreply@qnx.com] 
Sent: Tuesday, April 20, 2010 3:40 AM
To: drivers-networking
Subject: RE: RE: RE: RE: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)


Hi Radek - I think Yao was making commits
to if_run.c for the ral 2800/2900/3000.

--
aboyd
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
This is probably due to:
http://community.qnx.com/sf/wiki/do/viewPage/projects.community/wiki/Up
/P

On 19/04/10 06:28 PM, Radek Pesina wrote:
> Excellent.
>
> I tried an SVN checkout of the networking project however receive an unauthorized access error:
>
> svn checkout --username radek-pesina@swsa.com.au http://community.qnx.com/svn/repos/core_networking/trunk/lib
> svn: Not authorized to open root of edit operation
>
> Is there a way I can get access to the driver?
>
> Cheers,
> Radek.
>
>
>
> -----Original Message-----
> From: Andrew Boyd [mailto:community-noreply@qnx.com]
> Sent: Tuesday, April 20, 2010 3:40 AM
> To: drivers-networking
> Subject: RE: RE: RE: RE: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)
>
>
> Hi Radek - I think Yao was making commits
> to if_run.c for the ral 2800/2900/3000.
>
> --
> aboyd
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post52079
>
>    
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Sorry?  I get "The page you requested cannot be found."

Cheers,
Radek.
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
the usb rt28xx support is in devnp-run.so and code is in if_run.c but it is not committed yet:( You may ask Andrew to 
review. It works now.

I also ported the pci/pcie rt28xx support to devnp-ral.so in my spare time(on weekend), I can post it here but I don't 
have card to test so ral driver I didn't test all.

when I have time I will port more drivers.
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Hi Yao,

That's great news!  I'm sending off the application for restricted access, however any chance of getting a prebuilt 
binary before then?  If it has to go through a formal process and be reviewed first etc then I understand.

Thanks and best regards,
Radek.
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
> Hi Yao,
> 
> That's great news!  I'm sending off the application for restricted access, 
> however any chance of getting a prebuilt binary before then?  If it has to go 
> through a formal process and be reviewed first etc then I understand.
> 
> Thanks and best regards,
> Radek.


bad news!
I got a WUSB54GCV3 from Andrew and just tried today, it didn't work. It is a Mac3070, RF2020 so I didn't test before, 
totally different register setting with Mac2860.
but I tried Linux trunk staging driver and it works so I have Linux driver to reference the register setting.

will let you know.
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Thanks for the update Yao, is it much work to port over the register settings from the Linux driver?

Cheers,
Radek.
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
I did check the register setting with Linux driver and I didn't find anything different in rt3070.
So I installed a vmware machine on my Linux host as I don't have a QNX machine at home and tried this WUSB54GCV3 with my
 vmware machine, it works:)
so probably I did something wrong with the real machiine and I didn't change any code.

after you got the code, try it:)
it is strange Linux driver didn't include  this vid,did:(
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Well (I guess) that's good news!  I have restricted access now so I'll give it a try and let you know.  What is the SVN 
path for the code?  It seems the svn networking directory structure has changed in the last few months since I last 
looked at it.

Cheers,
Radek.
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
> Well (I guess) that's good news!  I have restricted access now so I'll give it
>  a try and let you know.  What is the SVN path for the code?  It seems the svn
>  networking directory structure has changed in the last few months since I 
> last looked at it.
> 
> Cheers,
> Radek.


I even don't know what the restricted access is now, is it the svn on foundry27? Or the source Legal department gave to 
you?

I checked into internal svn not svn on foundry27, not sure they are synced.

it is under io-pkt/sys/dev/run(make under this dir) and io-pkt/sys/dev/usb/if_run.c
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Ohh, I'm referring to the Networking SVN repository which was publicly accessible up until the 1st of April - http://
community.qnx.com/svn/repos/core_networking/trunk

Since then all are required to apply for restricted access to gain access to the source for certain Foundry 27 projects.
  It's just that since I last browsed the networking SVN repository the directory structure has changed.  

Thanks for that, the path you provided me with is all I needed to find it!

Cheers,
Radek.



RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Hi Yao,

After finally checking it all out (phew takes a while for the svn checkout!) I've managed to successfully build the 
library and give
it a try.  Unfortunately I has the same level of success as yourself - it didn't seem to work :(  Please see some output
 below.
Please let me know if there is anything you would like me to try or anything I can do.

Thanks again for all your help so far.

Radek.


# sloginfo -c
Time             Sev Major Minor Args
Jan 01 00:01:55    5    14     0 initializing IPsec... done
Jan 01 00:01:55    5    14     0 IPsec: Initialized Security Association Processing.
Jan 01 00:01:55    5    14     0 USB device vendor 0x1737, device 0x77 matched.
Jan 01 00:01:55    2    14     0 run_attach(): starting

Jan 01 00:01:56    5    14     0 run0 at pci0 dev 0 function 0run0: MAC/BBP RT3070 (rev 0x0200), RF RT3020 (MIMO 1T1R), 
address
00:23:69
:df:67:3f
Jan 01 00:01:56    5    14     0 ether_ifattach: run0 null if_stop
Jan 01 00:01:56    2    14     0 run_attach(): ending

# ifconfig -vvvvvv run0 up
# 
# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
        inet 127.0.0.1 netmask 0xff000000
run0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ssid ""
        powersave off
        address: 00:23:69:df:67:3f
        media: IEEE802.11 autoselect (DS1)
        status: no network
# 
# sloginfo -c
Time             Sev Major Minor Args
Jan 01 00:06:11    5    14     0 run0: device timeout
Jan 01 00:06:16    5    14     0 USB error 0x06000000 encountered  in io-pkt.
# dhcp.client -irun0 -d 
# sloginfo -c            
Time             Sev Major Minor Args
Jan 01 00:07:27    5    14     0 run0: device timeout
# dhcp.client -irun0 -d                  
# sloginfo
Time             Sev Major Minor Args
Jan 01 00:09:46    5    14     0 USB error 0x06000000 encountered  in io-pkt. 
# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
        inet 127.0.0.1 netmask 0xff000000
run0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ssid ""
        powersave off
        address: 00:23:69:df:67:3f
        media: IEEE802.11 autoselect (DS1)
        status: no network
        inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
# usb -vvvvvvvvvvvvvvvvvvvv
USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
    Control, Interrupt, Bulk(SG), Isoch(Stream), Low speed, High speed

Device Address             : 1
Upstream Host Controller   : 0
Upstream Device Address    : 0
Upstream Port              : 0
Upstream Port Speed        : Full
Vendor                     : 0x1737 (Ralink)
Product                    : 0x0077 (802.11 g WLAN)
Device Release             : r1.01
USB Spec Release           : v2.00
Serial Number              : 1.0
Class                      : 0x00 (Independent per interface)
Max PacketSize0            : 64
Languages                  : 0x0409 (English)
Current Frame              : 5600 (1024 bytes)
Configurations             : 1
  Configuration            : 1
    Attributes             : 0x80 (Bus-powered)
    Max Power              : 450 mA
    Interfaces             : 1
      Interface            : 0 / 0 (1.0)
        Class              : 0xff (Vendor-specific)
        Subclass           : 0xff
        Protocol           : 0xff
        Endpoints          : Control + 7
          Endpoint         : 0
            Attributes     : Control
            Max Packet Size: 64
          Endpoint         : 1
            Attributes     : Bulk/IN
            Max Packet Size: 64
          Endpoint         : 1
            Attributes     : Bulk/OUT
            Max Packet Size: 64
          Endpoint         : 2
            Attributes     : Bulk/OUT
            Max Packet Size: 64
          Endpoint         : 3
            Attributes     : Bulk/OUT
            Max Packet Size: 64
          Endpoint         : 4
            Attributes     :...
View Full Message
Re: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Success!  I've been checking out the SVN repository over a fair few days (after a while I always get a "svn: REPORT of '
/svn/repos/multimedia/!svn/vcc/default': Compressed response was truncated (http://community.qnx.com)" error and need to
 kick it off again) and noticed that you've checked in some changes over the weekend.  Quick SVN update and rebuild and 
the driver works perfectly!

Thanks alot for your efforts Yao, great work!

Best regards,
Radek.
Re: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
> 
> Success!  I've been checking out the SVN repository over a fair few days (
> after a while I always get a "svn: REPORT of '/svn/repos/multimedia/!svn/vcc/
> default': Compressed response was truncated (http://community.qnx.com)" error 
> and need to kick it off again) and noticed that you've checked in some changes
>  over the weekend.  Quick SVN update and rebuild and the driver works 
> perfectly!
> 
> Thanks alot for your efforts Yao, great work!
> 
> Best regards,
> Radek.


If there are some packets lost, please try to modify here in ieee80211_input, I copy the code from netbsd:(see the #
ifndef __QNXNTO__ below)
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/net80211/ieee80211_input.c?only_with_tag=MAIN

		if (HAS_SEQ(type)) {
			u_int8_t tid;
			if (IEEE80211_QOS_HAS_SEQ(wh)) {
				tid = ((struct ieee80211_qosframe *)wh)->
					i_qos[0] & IEEE80211_QOS_TID;
				if (TID_TO_WME_AC(tid) >= WME_AC_VI)
					ic->ic_wme.wme_hipri_traffic++;
				tid++;
			} else
				tid = 0;
			rxseq = le16toh(*(u_int16_t *)wh->i_seq);
			if ((wh->i_fc[1] & IEEE80211_FC1_RETRY) &&
#ifndef __QNXNTO__
			    SEQ_LEQ(rxseq, ni->ni_rxseqs[tid])) {
#else
				(rxseq == ni->ni_rxseqs[tid])) {
#endif
				/* duplicate, discard */
				IEEE80211_DISCARD_MAC(ic, IEEE80211_MSG_INPUT,
				    bssid, "duplicate",
				    "seqno <%u,%u> fragno <%u,%u> tid %u",
				    rxseq >> IEEE80211_SEQ_SEQ_SHIFT,
				    ni->ni_rxseqs[tid] >>
					IEEE80211_SEQ_SEQ_SHIFT,
				    rxseq & IEEE80211_SEQ_FRAG_MASK,
				    ni->ni_rxseqs[tid] &
					IEEE80211_SEQ_FRAG_MASK,
				    tid);
				ic->ic_stats.is_rx_dup++;
				IEEE80211_NODE_STAT(ni, rx_dup);
				goto out;
			}
			ni->ni_rxseqs[tid] = rxseq;
		}
	}

that is in 802.11 spec, stack should only store the most recent seq and some APs have bugs.

yao
RE: RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
I am actually loosing some packets therefore I'll give it a try.  Thanks Yao.
RE: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Please check in your fixes to if_run.c!  :)

--
aboyd
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Hi, from the responses here, applying for SVN general access and building the source code for the driver discussed above
 should support Linksys WUSB54GCV3? 

I ask becuse when I contacted Linksys about the particular dongle (Version 3), they told me the chipset was RT2501, not 
RT2800U as indicated here. However, using 

#io-plt-v4-hc -v -d rum  
Unable to init devnp-rum.so: No such device or address"

even though #usb shows a Ralink WLAN device plugged in.
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
> Hi, from the responses here, applying for SVN general access and building the 
> source code for the driver discussed above should support Linksys WUSB54GCV3? 
> 
> 
> I ask becuse when I contacted Linksys about the particular dongle (Version 3),
>  they told me the chipset was RT2501, not RT2800U as indicated here. However, 
> using 
> 
> #io-plt-v4-hc -v -d rum  
> Unable to init devnp-rum.so: No such device or address"
> 
> even though #usb shows a Ralink WLAN device plugged in.


If it is RT2501 then rum driver should support it.
If it is rt2800 then run driver should support it.

what is the output of "usb -v" or sloginfo?
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
> If it is RT2501 then rum driver should support it.
> If it is rt2800 then run driver should support it.
> 
> what is the output of "usb -v" or sloginfo?

# usb -v
USB 0 (UHCI) v1.10, v1.01 DDK, v1.01 HCD
    Control, Interrupt, Bulk(SG), Isoch(Stream), Low speed, Full speed

Device Address             : 1
Upstream Host Controller   : 0
Upstream Device Address    : 0
Upstream Port              : 1
Upstream Port Speed        : Low
Vendor                     : 0x046d (Logitech)
Product                    : 0xc045 (USB-PS/2 Optical Mouse)
Device Release             : r27.20
Class                      : 0x00 (Independent per interface)
Max PacketSize0            : 8
Configurations             : 1
  Configuration            : 1
    Attributes             : 0xa0 (Bus-powered, Remote-wakeup)
    Max Power              : 98 mA

USB 1 (UHCI) v1.10, v1.01 DDK, v1.01 HCD
    Control, Interrupt, Bulk(SG), Isoch(Stream), Low speed, Full speed

USB 2 (UHCI) v1.10, v1.01 DDK, v1.01 HCD
    Control, Interrupt, Bulk(SG), Isoch(Stream), Low speed, Full speed

USB 3 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
    Control, Interrupt, Bulk(SG), Isoch(Stream), Full speed, High speed

Device Address             : 1
Upstream Host Controller   : 3
Upstream Device Address    : 0
Upstream Port              : 0
Upstream Port Speed        : High
Vendor                     : 0x1737 (Ralink)
Product                    : 0x0077 (802.11 g WLAN)
Device Release             : r1.01
Class                      : 0x00 (Independent per interface)
Max PacketSize0            : 64
Configurations             : 1
  Configuration            : 1
    Attributes             : 0x80 (Bus-powered)
    Max Power              : 450 mA

# io-pkt-v4-hc -d rum
# sloginfo -c
Time             Sev Major Minor Args
Jun 24 13:39:28    7    15     0 qnet(L4): lr_add_ndb(): adding L4 0 addr to ndb for nd 3  bike.ad.itk.ntnu.no

Jun 24 13:39:28    7    15     0 qnet(QOS): nd_change_notify(): Node Up:   nd 3 bike.ad.itk.ntnu.no

Jun 24 13:44:29    5    14     0 tcpip starting
Jun 24 13:44:29    3    14     0 Using pseudo random generator.  See "random" option
Jun 24 13:44:29    5    14     0 initializing IPsec... done
Jun 24 13:44:29    5    14     0 IPsec: Initialized Security Association Processing.
Jun 24 13:44:29    2    14     0 Unable to init devnp-rum.so: No such device or address


Now, there is another io-pkt already running for the ethernet interface, but still, shouldn't the device be recognized?
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
> 
> > If it is RT2501 then rum driver should support it.
> > If it is rt2800 then run driver should support it.
> > 
> > what is the output of "usb -v" or sloginfo?
> 
> # usb -v
> USB 0 (UHCI) v1.10, v1.01 DDK, v1.01 HCD
>     Control, Interrupt, Bulk(SG), Isoch(Stream), Low speed, Full speed
> 
> Device Address             : 1
> Upstream Host Controller   : 0
> Upstream Device Address    : 0
> Upstream Port              : 1
> Upstream Port Speed        : Low
> Vendor                     : 0x046d (Logitech)
> Product                    : 0xc045 (USB-PS/2 Optical Mouse)
> Device Release             : r27.20
> Class                      : 0x00 (Independent per interface)
> Max PacketSize0            : 8
> Configurations             : 1
>   Configuration            : 1
>     Attributes             : 0xa0 (Bus-powered, Remote-wakeup)
>     Max Power              : 98 mA
> 
> USB 1 (UHCI) v1.10, v1.01 DDK, v1.01 HCD
>     Control, Interrupt, Bulk(SG), Isoch(Stream), Low speed, Full speed
> 
> USB 2 (UHCI) v1.10, v1.01 DDK, v1.01 HCD
>     Control, Interrupt, Bulk(SG), Isoch(Stream), Low speed, Full speed
> 
> USB 3 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
>     Control, Interrupt, Bulk(SG), Isoch(Stream), Full speed, High speed
> 
> Device Address             : 1
> Upstream Host Controller   : 3
> Upstream Device Address    : 0
> Upstream Port              : 0
> Upstream Port Speed        : High
> Vendor                     : 0x1737 (Ralink)
> Product                    : 0x0077 (802.11 g WLAN)
> Device Release             : r1.01
> Class                      : 0x00 (Independent per interface)
> Max PacketSize0            : 64
> Configurations             : 1
>   Configuration            : 1
>     Attributes             : 0x80 (Bus-powered)
>     Max Power              : 450 mA
> 
> # io-pkt-v4-hc -d rum
> # sloginfo -c
> Time             Sev Major Minor Args
> Jun 24 13:39:28    7    15     0 qnet(L4): lr_add_ndb(): adding L4 0 addr to 
> ndb for nd 3  bike.ad.itk.ntnu.no
> 
> Jun 24 13:39:28    7    15     0 qnet(QOS): nd_change_notify(): Node Up:   nd 
> 3 bike.ad.itk.ntnu.no
> 
> Jun 24 13:44:29    5    14     0 tcpip starting
> Jun 24 13:44:29    3    14     0 Using pseudo random generator.  See "random" 
> option
> Jun 24 13:44:29    5    14     0 initializing IPsec... done
> Jun 24 13:44:29    5    14     0 IPsec: Initialized Security Association 
> Processing.
> Jun 24 13:44:29    2    14     0 Unable to init devnp-rum.so: No such device 
> or address
> 
> 
> Now, there is another io-pkt already running for the ethernet interface, but 
> still, shouldn't the device be recognized?


This is the RT3070 chip(V3) so please use "devnp-run.so".
Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Heh, so techsupport where clueless in otherwods. Figures.

This might sound stupid, but where do I get the run driver? It is not listed in the hardware database.

Re: Support for Ralink RT2800U Chipset(Linksys WUSB54GCV3)  
Cannot edit, so double post:
I'm assuming I can get it from the project downloads page http://community.qnx.com/sf/frs/do/viewSummary/projects.
networking/frs . However, I dont have permission. I know there was a policy change recently, and that I can access some 
parts if I agree to a "click through Foundery27 agreement". MyQNX lists me with License Type: Non-commercial End User 
License Agreement, but I cant for the love of me find this "click through" agreement. 

Or do I need the restricted access, by filling out the form and crossing my fingers?