> confirmed it a second time ...
> hang after mounting qnet?

Remember that qnet will call the _init routine for
any devices that it discovers.  

Depending upon how  you intend to use qnet, you can 
either use the "bind=" option to tell it to only use 
specific interfaces, or perhaps just:

  # rm /etc/system/config/useqnet

file during your initialization debugging, to simplify
things as much as possible.

--
aboyd

OK, binding qnet to en0 only seems like it resolved the issue.  Although
we're not planning on shipping a product with qnet enabled, it would be
good to know what's going on when qnet is enabled for the Linksys
dongle. 

-----Original Message-----
From: Andrew Boyd [mailto:community-noreply@qnx.com] 
Sent: Monday, January 19, 2009 8:18 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)


> confirmed it a second time ...
> hang after mounting qnet?

Remember that qnet will call the _init routine for any devices that it
discovers.  

Depending upon how  you intend to use qnet, you can either use the
"bind=" option to tell it to only use specific interfaces, or perhaps
just:

  # rm /etc/system/config/useqnet

file during your initialization debugging, to simplify things as much as
possible.

--
aboyd


_______________________________________________
General
http://community.qnx.com/sf/go/post20298
 
- CONFIDENTIAL-
This email and any files transmitted with it are confidential, and may also be legally privileged.  If you are not the 
intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, 
please notify the sender immediately by reply email and then delete this email.

> binding qnet to en0 only seems like it resolved the issue. 

:-)

> it would be good to know what's going on when qnet is 
> enabled for the Linksys dongle.

As I said before, when qnet is discovering interfaces,
it makes a call to the driver "init" function to bring
the interface up.  This is because you don't need to 
configure TCP/IP on the interface, to make it work.

When you have more than one network interface, it is
a good idea to use the "bind=" command line option to
qnet, so that it only transmits and recieves qnet
packets on the interface(s) that you want.

What I suspect is happening in your case, is some
timing problem, related to the initialization of
the USB wifi dongle.  I suspect that if you delayed
the mounting of qnet a few seconds, that would also 
fix the (timing related hardware) problem.

But six of one, half a dozen of the other.

--
aboyd  www.PoweredByQNX.com

Hi Gordon:

	My current guess is that when you do the soft re-boot, either
the USB hardware or the dongle is left in a state which is... ummmm...
less than optimal. QNET comes up, tries to initialize the dongle and
things end up getting stuck for whatever reason.  We can continue on
with debugging if you'd like.  At this stage we might want to look at
getting a shell out of the serial port.  The problem is getting
visibility of what's happening under during the boot sequence...

	Robert.

-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com] 
Sent: Monday, January 19, 2009 1:11 PM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

OK, binding qnet to en0 only seems like it resolved the issue.  Although
we're not planning on shipping a product with qnet enabled, it would be
good to know what's going on when qnet is enabled for the Linksys
dongle. 

-----Original Message-----
From: Andrew Boyd [mailto:community-noreply@qnx.com]
Sent: Monday, January 19, 2009 8:18 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)


> confirmed it a second time ...
> hang after mounting qnet?

Remember that qnet will call the _init routine for any devices that it
discovers.  

Depending upon how  you intend to use qnet, you can either use the
"bind=" option to tell it to only use specific interfaces, or perhaps
just:

  # rm /etc/system/config/useqnet

file during your initialization debugging, to simplify things as much as
possible.

--
aboyd


_______________________________________________
General
http://community.qnx.com/sf/go/post20298
 
- CONFIDENTIAL-
This email and any files transmitted with it are confidential, and may
also be legally privileged.  If you are not the intended recipient, you
may not review, use, copy, or distribute this message. If you receive
this email in error, please notify the sender immediately by reply email
and then delete this email.

_______________________________________________
General
http://community.qnx.com/sf/go/post20329

We'll let this sleeping dog lie for now, and revisit it (if necessary)
if in the future we decide to ship a product with qnet enabled.

Thanks for all the help. 

-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com] 
Sent: Monday, January 19, 2009 12:29 PM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Hi Gordon:

	My current guess is that when you do the soft re-boot, either
the USB hardware or the dongle is left in a state which is... ummmm...
less than optimal. QNET comes up, tries to initialize the dongle and
things end up getting stuck for whatever reason.  We can continue on
with debugging if you'd like.  At this stage we might want to look at
getting a shell out of the serial port.  The problem is getting
visibility of what's happening under during the boot sequence...

	Robert.

-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Monday, January 19, 2009 1:11 PM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

OK, binding qnet to en0 only seems like it resolved the issue.  Although
we're not planning on shipping a product with qnet enabled, it would be
good to know what's going on when qnet is enabled for the Linksys
dongle. 

-----Original Message-----
From: Andrew Boyd [mailto:community-noreply@qnx.com]
Sent: Monday, January 19, 2009 8:18 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)


> confirmed it a second time ...
> hang after mounting qnet?

Remember that qnet will call the _init routine for any devices that it
discovers.  

Depending upon how  you intend to use qnet, you can either use the
"bind=" option to tell it to only use specific interfaces, or perhaps
just:

  # rm /etc/system/config/useqnet

file during your initialization debugging, to simplify things as much as
possible.

--
aboyd


_______________________________________________
General
http://community.qnx.com/sf/go/post20298
 
- CONFIDENTIAL-
This email and any files transmitted with it are confidential, and may
also be legally privileged.  If you are not the intended recipient, you
may not review, use, copy, or distribute this message. If you receive
this email in error, please notify the sender immediately by reply email
and then delete this email.

_______________________________________________
General
http://community.qnx.com/sf/go/post20329


_______________________________________________
General
http://community.qnx.com/sf/go/post20333