Robert,
I'm having no luck getting your requested output.  My target PC does not
have PS/2 keyboard and mouse ports, so I lose my keyboard as soon as I
slay io-usb.  I've tried writing a script to perform the steps you
outline but it seems to either hang or the USB Wi-Fi adapter is not
detected.  I've also tried unsuccessfully to get phindows to run over
the serial port, but it simply states that it is waiting for phrelay on
com1 and I have been unable to figure out what needs to be configured on
the target.

Any suggestions?

Thanks,

Gordon 

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

And nothing obvious sticks out there either.  You're plugged into the
high speed EHCI controller (which is good), there aren't any interrupts
being shared between USB and networking (good).  It looks like the
enumerator found and started a network driver for a card in the system
since networking does have a real IRQ assigned to it.

Let's try something a bit more drastic... As root

slay io-pkt
slay io-usb 

sloginfo -c

io-usb -dehci -dohci -duhci

usb -vvv

(Make sure that the device shows up)

io-pkt-v4-hc -drum

And send the output from sloginfo


	Robert.


-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Friday, January 09, 2009 9:05 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Robert,
OK, here we go, lot's of answers.

Here's the output of "usb -vvv" with the Linksys inserted:

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

USB 1 (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   : 1
Upstream Device Address    : 0
Upstream Port              : 0
Upstream Port Speed        : Low
Vendor                     : 0x413c (Dell)
Product                    : 0x2003 (Dell USB Keyboard)
Device Release             : r3.06
USB Spec Release           : v1.10
Serial Number              : N/A
Class                      : 0x00 (Independent per interface)
Max PacketSize0            : 8
Languages                  : 0x0409 (English)
Current Frame              : 505 (1024 bytes)
Configurations             : 1
  Configuration            : 1
    Attributes             : 0xa0 (Bus-powered, Remote-wakeup)
    Max Power              : 70 mA
    Interfaces             : 1
      Interface            : 0 / 0
        Class              : 0x03 (HID)
        Subclass           : 0x01 (Boot interface)
        Protocol           : 0x01 (Keyboard)
        Endpoints          : Control + 1
          Endpoint         : 0
            Attributes     : Control
            Max Packet Size: 8
          Endpoint         : 1
            Attributes     : Interrupt/IN
            Max Packet Size: 8
            Interval       : 24 ms

Device Address             : 2
Upstream Host Controller   : 1
Upstream Device Address    : 0
Upstream Port              : 1
Upstream Port Speed        : Low
Vendor                     : 0x413c (Dell)
Product                    : 0x3012 (Dell USB Optical Mouse)
Device Release             : r43.01
USB Spec Release           : v2.00
Serial Number              : N/A
Class                      : 0x00 (Independent per interface)
Max PacketSize0            : 8
Languages                  : 0x0409 (English)
Current Frame              : 541 (1024 bytes)
Configurations             : 1
  Configuration            : 1
    Attributes             : 0xa0 (Bus-powered, Remote-wakeup)
    Max Power              : 100 mA
    Interfaces             : 1
      Interface            : 0 / 0
        Class  ...

Hmmm...  Hadn't thought about that one.  I can think of a convoluted way
involving running two stacks (one with the wired adapter) and using
telnet....

Let's start off with just
slay io-pkt
sloginfo -c
usb -vvv
(Make sure that the device shows up)

io-pkt-v4-hc -drum
 

	Robert.

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

Robert,
I'm having no luck getting your requested output.  My target PC does not
have PS/2 keyboard and mouse ports, so I lose my keyboard as soon as I
slay io-usb.  I've tried writing a script to perform the steps you
outline but it seems to either hang or the USB Wi-Fi adapter is not
detected.  I've also tried unsuccessfully to get phindows to run over
the serial port, but it simply states that it is waiting for phrelay on
com1 and I have been unable to figure out what needs to be configured on
the target.

Any suggestions?

Thanks,

Gordon 

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

And nothing obvious sticks out there either.  You're plugged into the
high speed EHCI controller (which is good), there aren't any interrupts
being shared between USB and networking (good).  It looks like the
enumerator found and started a network driver for a card in the system
since networking does have a real IRQ assigned to it.

Let's try something a bit more drastic... As root

slay io-pkt
slay io-usb 

sloginfo -c

io-usb -dehci -dohci -duhci

usb -vvv

(Make sure that the device shows up)

io-pkt-v4-hc -drum

And send the output from sloginfo


	Robert.


-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Friday, January 09, 2009 9:05 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Robert,
OK, here we go, lot's of answers.

Here's the output of "usb -vvv" with the Linksys inserted:

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

USB 1 (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   : 1
Upstream Device Address    : 0
Upstream Port              : 0
Upstream Port Speed        : Low
Vendor                     : 0x413c (Dell)
Product                    : 0x2003 (Dell USB Keyboard)
Device Release             : r3.06
USB Spec Release           : v1.10
Serial Number              : N/A
Class                      : 0x00 (Independent per interface)
Max PacketSize0            : 8
Languages                  : 0x0409 (English)
Current Frame              : 505 (1024 bytes)
Configurations             : 1
  Configuration            : 1
    Attributes             : 0xa0 (Bus-powered, Remote-wakeup)
    Max Power              : 70 mA
    Interfaces             : 1
      Interface            : 0 / 0
        Class              : 0x03 (HID)
        Subclass           : 0x01 (Boot interface)
        Protocol           : 0x01 (Keyboard)
        Endpoints          : Control + 1
          Endpoint         : 0
            Attributes     : Control
            Max Packet Size: 8
          Endpoint         : 1
            Attributes     : Interrupt/IN
            Max Packet Size: 8
            Interval       : 24 ms

Device Address             : 2
Upstream Host Controller   : 1
Upstream Device Address    : 0
Upstream Port              : 1
Upstream Port Speed        : Low
Vendor                     : 0x413c (Dell)
Product                    : 0x3012 (Dell USB Optical Mouse)
Device...

Robert,
It's very inconsistent whether or not the USB Wi-Fi adapter is detected
on boot-up, or when I remove and re-insert it, but for what it is worth,
here's the sloginfo:

Time             Sev Major Minor Args
Jan 12 10:48:22    5    14     0 tcpip starting
Jan 12 10:48:22    3    14     0 Using pseudo random generator.  See
"random" option
Jan 12 10:48:22    5    14     0 if_attach: lo0 null if_stop
Jan 12 10:48:22    5    14     0 if_attach: lo0 null if_init
Jan 12 10:48:22    5    14     0 initializing IPsec... done
Jan 12 10:48:22    5    14     0 IPsec: Initialized Security Association
Processing.
Jan 12 10:48:22    2    14     0 Unable to init devnp-rum.so: No such
device or address


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

Hmmm...  Hadn't thought about that one.  I can think of a convoluted way
involving running two stacks (one with the wired adapter) and using
telnet....

Let's start off with just
slay io-pkt
sloginfo -c
usb -vvv
(Make sure that the device shows up)

io-pkt-v4-hc -drum
 

	Robert.

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

Robert,
I'm having no luck getting your requested output.  My target PC does not
have PS/2 keyboard and mouse ports, so I lose my keyboard as soon as I
slay io-usb.  I've tried writing a script to perform the steps you
outline but it seems to either hang or the USB Wi-Fi adapter is not
detected.  I've also tried unsuccessfully to get phindows to run over
the serial port, but it simply states that it is waiting for phrelay on
com1 and I have been unable to figure out what needs to be configured on
the target.

Any suggestions?

Thanks,

Gordon 

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

And nothing obvious sticks out there either.  You're plugged into the
high speed EHCI controller (which is good), there aren't any interrupts
being shared between USB and networking (good).  It looks like the
enumerator found and started a network driver for a card in the system
since networking does have a real IRQ assigned to it.

Let's try something a bit more drastic... As root

slay io-pkt
slay io-usb 

sloginfo -c

io-usb -dehci -dohci -duhci

usb -vvv

(Make sure that the device shows up)

io-pkt-v4-hc -drum

And send the output from sloginfo


	Robert.


-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Friday, January 09, 2009 9:05 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Robert,
OK, here we go, lot's of answers.

Here's the output of "usb -vvv" with the Linksys inserted:

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

USB 1 (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   : 1
Upstream Device Address    : 0
Upstream Port              : 0
Upstream Port Speed        : Low
Vendor                     : 0x413c (Dell)
Product                    : 0x2003 (Dell USB Keyboard)
Device Release             : r3.06
USB Spec Release           : v1.10
Serial Number              : N/A
Class                      : 0x00 (Independent per interface)
Max PacketSize0            : 8
Languages                  : 0x0409 (English)
Current Frame              : 505...

All of this is pointing to "something" going wrong with USB on that
platform.  The fact that it worked with 6.3.2 and doesn't work on 6.4.0
is concerning me.  Is there anyway that you can try out a different
platform and see if that works?   Do you happen to have some sort of
USB-Ethernet dongle (e.g. SMC-2209) that one of our drivers might work
with to try out?  What are the specs on the hardware?

This is another one of those "weird ones".
	Robert.

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

Robert,
It's very inconsistent whether or not the USB Wi-Fi adapter is detected
on boot-up, or when I remove and re-insert it, but for what it is worth,
here's the sloginfo:

Time             Sev Major Minor Args
Jan 12 10:48:22    5    14     0 tcpip starting
Jan 12 10:48:22    3    14     0 Using pseudo random generator.  See
"random" option
Jan 12 10:48:22    5    14     0 if_attach: lo0 null if_stop
Jan 12 10:48:22    5    14     0 if_attach: lo0 null if_init
Jan 12 10:48:22    5    14     0 initializing IPsec... done
Jan 12 10:48:22    5    14     0 IPsec: Initialized Security Association
Processing.
Jan 12 10:48:22    2    14     0 Unable to init devnp-rum.so: No such
device or address


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

Hmmm...  Hadn't thought about that one.  I can think of a convoluted way
involving running two stacks (one with the wired adapter) and using
telnet....

Let's start off with just
slay io-pkt
sloginfo -c
usb -vvv
(Make sure that the device shows up)

io-pkt-v4-hc -drum
 

	Robert.

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

Robert,
I'm having no luck getting your requested output.  My target PC does not
have PS/2 keyboard and mouse ports, so I lose my keyboard as soon as I
slay io-usb.  I've tried writing a script to perform the steps you
outline but it seems to either hang or the USB Wi-Fi adapter is not
detected.  I've also tried unsuccessfully to get phindows to run over
the serial port, but it simply states that it is waiting for phrelay on
com1 and I have been unable to figure out what needs to be configured on
the target.

Any suggestions?

Thanks,

Gordon 

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

And nothing obvious sticks out there either.  You're plugged into the
high speed EHCI controller (which is good), there aren't any interrupts
being shared between USB and networking (good).  It looks like the
enumerator found and started a network driver for a card in the system
since networking does have a real IRQ assigned to it.

Let's try something a bit more drastic... As root

slay io-pkt
slay io-usb 

sloginfo -c

io-usb -dehci -dohci -duhci

usb -vvv

(Make sure that the device shows up)

io-pkt-v4-hc -drum

And send the output from sloginfo


	Robert.


-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Friday, January 09, 2009 9:05 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Robert,
OK, here we go, lot's of answers.

Here's the output of "usb -vvv" with the Linksys inserted:

USB 0 (UHCI) v1.10, v1.01 DDK, v1.01 HCD
    Control, Interrupt, Bulk(SG),...

Robert,
OK, it seems to be pointing to the USB Wi-Fi adapter itself.  I used a
different LinkSys dongle on my Dell Optiplex GX620 target and the
problem appears to have gone away.  I moved the original LinkSys dongle
to another target (Dell Optiplex 745) and the problem moved with the
dongle.

Thanks,

Gordon 

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

All of this is pointing to "something" going wrong with USB on that
platform.  The fact that it worked with 6.3.2 and doesn't work on 6.4.0
is concerning me.  Is there anyway that you can try out a different
platform and see if that works?   Do you happen to have some sort of
USB-Ethernet dongle (e.g. SMC-2209) that one of our drivers might work
with to try out?  What are the specs on the hardware?

This is another one of those "weird ones".
	Robert.

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

Robert,
It's very inconsistent whether or not the USB Wi-Fi adapter is detected
on boot-up, or when I remove and re-insert it, but for what it is worth,
here's the sloginfo:

Time             Sev Major Minor Args
Jan 12 10:48:22    5    14     0 tcpip starting
Jan 12 10:48:22    3    14     0 Using pseudo random generator.  See
"random" option
Jan 12 10:48:22    5    14     0 if_attach: lo0 null if_stop
Jan 12 10:48:22    5    14     0 if_attach: lo0 null if_init
Jan 12 10:48:22    5    14     0 initializing IPsec... done
Jan 12 10:48:22    5    14     0 IPsec: Initialized Security Association
Processing.
Jan 12 10:48:22    2    14     0 Unable to init devnp-rum.so: No such
device or address


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

Hmmm...  Hadn't thought about that one.  I can think of a convoluted way
involving running two stacks (one with the wired adapter) and using
telnet....

Let's start off with just
slay io-pkt
sloginfo -c
usb -vvv
(Make sure that the device shows up)

io-pkt-v4-hc -drum
 

	Robert.

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

Robert,
I'm having no luck getting your requested output.  My target PC does not
have PS/2 keyboard and mouse ports, so I lose my keyboard as soon as I
slay io-usb.  I've tried writing a script to perform the steps you
outline but it seems to either hang or the USB Wi-Fi adapter is not
detected.  I've also tried unsuccessfully to get phindows to run over
the serial port, but it simply states that it is waiting for phrelay on
com1 and I have been unable to figure out what needs to be configured on
the target.

Any suggestions?

Thanks,

Gordon 

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

And nothing obvious sticks out there either.  You're plugged into the
high speed EHCI controller (which is good), there aren't any interrupts
being shared between USB and networking (good).  It looks like the
enumerator found and started a network driver for a card in the system
since networking does have a real IRQ assigned to it.

Let's try something a bit more drastic... As root

slay io-pkt
slay io-usb 

sloginfo -c

io-usb -dehci...

Whew!  (I think).  Sounds very strange, but I'm glad to hear that things
are working again.  Funny how I never even thought to question the
dongle, but I guess that I should have.  USB on x86 is usually solid, so
to have it fail would be unusual.

    Robert.

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

Robert,
OK, it seems to be pointing to the USB Wi-Fi adapter itself.  I used a
different LinkSys dongle on my Dell Optiplex GX620 target and the
problem appears to have gone away.  I moved the original LinkSys dongle
to another target (Dell Optiplex 745) and the problem moved with the
dongle.

Thanks,

Gordon 

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

All of this is pointing to "something" going wrong with USB on that
platform.  The fact that it worked with 6.3.2 and doesn't work on 6.4.0
is concerning me.  Is there anyway that you can try out a different
platform and see if that works?   Do you happen to have some sort of
USB-Ethernet dongle (e.g. SMC-2209) that one of our drivers might work
with to try out?  What are the specs on the hardware?

This is another one of those "weird ones".
	Robert.

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

Robert,
It's very inconsistent whether or not the USB Wi-Fi adapter is detected
on boot-up, or when I remove and re-insert it, but for what it is worth,
here's the sloginfo:

Time             Sev Major Minor Args
Jan 12 10:48:22    5    14     0 tcpip starting
Jan 12 10:48:22    3    14     0 Using pseudo random generator.  See
"random" option
Jan 12 10:48:22    5    14     0 if_attach: lo0 null if_stop
Jan 12 10:48:22    5    14     0 if_attach: lo0 null if_init
Jan 12 10:48:22    5    14     0 initializing IPsec... done
Jan 12 10:48:22    5    14     0 IPsec: Initialized Security Association
Processing.
Jan 12 10:48:22    2    14     0 Unable to init devnp-rum.so: No such
device or address


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

Hmmm...  Hadn't thought about that one.  I can think of a convoluted way
involving running two stacks (one with the wired adapter) and using
telnet....

Let's start off with just
slay io-pkt
sloginfo -c
usb -vvv
(Make sure that the device shows up)

io-pkt-v4-hc -drum
 

	Robert.

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

Robert,
I'm having no luck getting your requested output.  My target PC does not
have PS/2 keyboard and mouse ports, so I lose my keyboard as soon as I
slay io-usb.  I've tried writing a script to perform the steps you
outline but it seems to either hang or the USB Wi-Fi adapter is not
detected.  I've also tried unsuccessfully to get phindows to run over
the serial port, but it simply states that it is waiting for phrelay on
com1 and I have been unable to figure out what needs to be configured on
the target.

Any suggestions?

Thanks,

Gordon 

-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: Friday, January 09, 2009 2:16 PM
To: general-networking
Subject: RE: RE: Problems getting USB...

Robert,
OK, now that we've got THAT out of the way, on to the issue that first
started this investigation.  :-)

Sometimes when we boot up our target with the USB WiFi adapter inserted
the system hangs during startup.  I modified /etc/system/sysinit to
automatically set VERBOSE.
The output that shows up on the console during boot up is:

  QNX v1.2a Boot Loader: qnxbasesmp.ifs .....

  Press the space bar to input boot options or D to disable DMA...
  Trying SATA ahci. Scanning for devices...
  xpt_configure:  ahci SIM attach failure
  Trying EIDE. Scanning for devices...
  ...found 2 devices
  Detected USB. Scanning for devices...
  Trying SATA mvSata. Scanning for devices...
  xpt_configure:  No mvSata interfaces found
  BOOTSRC=disk
  SAFEMODE=
  VERBOSE=1
  ROOTDEV=/dev/hd0t179
  NO_ETC=
 
Typically, the next output would be:

  Starting extra run commands

Which indicates that /etc/rc.d/rc.local is being executed, but we don't
see that during a hang.
Is there any other debugging/tracing we could enable to further isolate
what is going wrong?

Secondly, we have seen several instances where the system does not
shutdown and reboot properly (we invoke system("shutdown -q") to bring
the system down).
Photon exits (we get back to the console output screen) but the system
doesn't reboot, and the power button doesn't shut the PC off until it's
been held for more than 5 seconds.

Thanks,

Gordon

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

Whew!  (I think).  Sounds very strange, but I'm glad to hear that things
are working again.  Funny how I never even thought to question the
dongle, but I guess that I should have.  USB on x86 is usually solid, so
to have it fail would be unusual.

    Robert.

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

Robert,
OK, it seems to be pointing to the USB Wi-Fi adapter itself.  I used a
different LinkSys dongle on my Dell Optiplex GX620 target and the
problem appears to have gone away.  I moved the original LinkSys dongle
to another target (Dell Optiplex 745) and the problem moved with the
dongle.

Thanks,

Gordon 

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

All of this is pointing to "something" going wrong with USB on that
platform.  The fact that it worked with 6.3.2 and doesn't work on 6.4.0
is concerning me.  Is there anyway that you can try out a different
platform and see if that works?   Do you happen to have some sort of
USB-Ethernet dongle (e.g. SMC-2209) that one of our drivers might work
with to try out?  What are the specs on the hardware?

This is another one of those "weird ones".
	Robert.

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

Robert,
It's very inconsistent whether or not the USB Wi-Fi adapter is detected
on boot-up, or when I remove and re-insert it, but for what it is worth,
here's the sloginfo:

Time             Sev Major Minor Args
Jan 12 10:48:22    5    14     0 tcpip starting
Jan 12 10:48:22    3    14     0 Using pseudo random generator.  See
"random" option
Jan 12 10:48:22    5    14     0 if_attach: lo0 null if_stop
Jan 12 10:48:22    5    14     0 if_attach: lo0 null if_init
Jan 12 10:48:22    5    14     0 initializing IPsec... done
Jan 12...

OK, I turned on verbose in enum-devices and got the following debug
output:

  Starting: io-display
  Starting: mount -Tio-display vid=0x1002,did=0x5b62,deviceindex=0
  Starting: io-pkt-v4-hc -ptcpip
  Starting: mount -Tio-pkt -opci=0,vid=0x14e4,did=0x1677
/lib/dll/devn-tigon3.so
  Starting: netmanager
  Starting: io-pkt-v4-hc -ptcpip  (skipped: already running)
  Starting: mount -Tio-pkt devnp-rum.so
  Starting: netmanager
  Starting enumerator: legacy'
(neednet,,chkser,ioport=3f8+7,irq=4,nopar,nokb,nonet) => 155672
  Starting: devb-fdc cam quiet blk auto=partition,cache=100k
  Starting: io-pkt-v4-hc -ptcpip  (skipped: already running)

Gordon
 
- 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.

So it LOOKS like you're about to mount another network device and it
never gets to it...  You've got a BCM57xx, the Linksys dongle and some
other NIC in there (?)  Wouldn't happen to be an Intel 10/100 card would
it?

	Robert. 

-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com] 
Sent: Thursday, January 15, 2009 10:03 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

OK, I turned on verbose in enum-devices and got the following debug
output:

  Starting: io-display
  Starting: mount -Tio-display vid=0x1002,did=0x5b62,deviceindex=0
  Starting: io-pkt-v4-hc -ptcpip
  Starting: mount -Tio-pkt -opci=0,vid=0x14e4,did=0x1677
/lib/dll/devn-tigon3.so
  Starting: netmanager
  Starting: io-pkt-v4-hc -ptcpip  (skipped: already running)
  Starting: mount -Tio-pkt devnp-rum.so
  Starting: netmanager
  Starting enumerator: legacy'
(neednet,,chkser,ioport=3f8+7,irq=4,nopar,nokb,nonet) => 155672
  Starting: devb-fdc cam quiet blk auto=partition,cache=100k
  Starting: io-pkt-v4-hc -ptcpip  (skipped: already running)

Gordon
 
- 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/post20120

There's only the on-board NIC and the Linksys dongle.  No separate Intel
10/100 card.
Perhaps something is being mis-identified? 

-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com] 
Sent: Thursday, January 15, 2009 9:39 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

So it LOOKS like you're about to mount another network device and it
never gets to it...  You've got a BCM57xx, the Linksys dongle and some
other NIC in there (?)  Wouldn't happen to be an Intel 10/100 card would
it?

	Robert. 

-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Thursday, January 15, 2009 10:03 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

OK, I turned on verbose in enum-devices and got the following debug
output:

  Starting: io-display
  Starting: mount -Tio-display vid=0x1002,did=0x5b62,deviceindex=0
  Starting: io-pkt-v4-hc -ptcpip
  Starting: mount -Tio-pkt -opci=0,vid=0x14e4,did=0x1677
/lib/dll/devn-tigon3.so
  Starting: netmanager
  Starting: io-pkt-v4-hc -ptcpip  (skipped: already running)
  Starting: mount -Tio-pkt devnp-rum.so
  Starting: netmanager
  Starting enumerator: legacy'
(neednet,,chkser,ioport=3f8+7,irq=4,nopar,nokb,nonet) => 155672
  Starting: devb-fdc cam quiet blk auto=partition,cache=100k
  Starting: io-pkt-v4-hc -ptcpip  (skipped: already running)

Gordon
 
- 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/post20120


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

Hmmm... I wonder why it looks like it's trying to bring up another
io-pkt session.  You'd really only expect it to do so if there were
another interface recognized.  Where did you add in the info for the rum
driver? Can you post your net configuration file for me to take a look
at?  

	I guess the other thing to make sure of is that this is
something to do with networking and not another subsystem.  If you don't
have the dongle plugged in, does it still fail to come up?

	Robert.

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

There's only the on-board NIC and the Linksys dongle.  No separate Intel
10/100 card.
Perhaps something is being mis-identified? 

-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: Thursday, January 15, 2009 9:39 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

So it LOOKS like you're about to mount another network device and it
never gets to it...  You've got a BCM57xx, the Linksys dongle and some
other NIC in there (?)  Wouldn't happen to be an Intel 10/100 card would
it?

	Robert. 

-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Thursday, January 15, 2009 10:03 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

OK, I turned on verbose in enum-devices and got the following debug
output:

  Starting: io-display
  Starting: mount -Tio-display vid=0x1002,did=0x5b62,deviceindex=0
  Starting: io-pkt-v4-hc -ptcpip
  Starting: mount -Tio-pkt -opci=0,vid=0x14e4,did=0x1677
/lib/dll/devn-tigon3.so
  Starting: netmanager
  Starting: io-pkt-v4-hc -ptcpip  (skipped: already running)
  Starting: mount -Tio-pkt devnp-rum.so
  Starting: netmanager
  Starting enumerator: legacy'
(neednet,,chkser,ioport=3f8+7,irq=4,nopar,nokb,nonet) => 155672
  Starting: devb-fdc cam quiet blk auto=partition,cache=100k
  Starting: io-pkt-v4-hc -ptcpip  (skipped: already running)

Gordon
 
- 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/post20120


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


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

Robert,
I was unable to reproduce this boot-up hang without the Linksys dongle
inserted.  The power-down hang occurs regardless of whether or not the
Linksys dongle is inserted or not.

The contents of my /etc/netconfig file is:

udp6       tpi_clts      v     inet6    udp     -       -
tcp6       tpi_cots_ord  v     inet6    tcp     -       -
udp        tpi_clts      v     inet     udp     -       -
tcp        tpi_cots_ord  v     inet     tcp     -       -
rawip      tpi_raw       -     inet      -      -       -
local      tpi_cots_ord  -     loopback  -      -       -

The contents of my /etc/system/enum/devices/net file is (see the
"gemhack" comments below to see what I added):

#
# Definitions for net devices
#

# Make sure ionet starts even if there is no network card (for 127.1)
device(none, .type=$(ISA_TYPE_NETWORK))
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	
# ne1000/ne2000 devices
device(isa, .type=$(ISA_TYPE_NETWORK), .subtype=$(ISA_NETWORK_ETHER),
.progif=00)
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
	mount(-Tio-pkt "-oioport=0x$(ioport)" /lib/dll/devn-ne2000.so,
"/dev/io-net/en$(netnum)")
	use(symbolic=netmgr)
	
device(pci, ven=$(PCI_VEND_REALTEK), dev=8029)
device(pci, ven=$(PCI_VEND_WINBOND), dev=0940)		#89C940
device(pci, ven=$(PCI_VEND_POWERMATIC), dev=1401)	#Compex RL2000
device(pci, ven=$(PCI_VEND_KTI), dev=3000)			#ET32P2
device(pci, ven=$(PCI_VEND_NETVIN), dev=5000)		#NV5000SC
device(pci, ven=$(PCI_VEND_VIA), dev=0926)			#82C926
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
	mount(-Tio-pkt "-opci=$(index),vid=0x$(ven),did=0x$(dev)"
/lib/dll/devn-ne2000.so, "/dev/io-net/en$(netnum)")
	use(symbolic=netmgr)

device(pcmcia, ven=$(PCCARD_VEND_DLINK), dev=021b)
device(pcmcia, ven=$(PCCARD_VEND_SOCKET), dev=000d)	#PCMCIA LPE
device(pcmcia, ven=$(PCCARD_VEND_SOCKET), dev=0075)	#CF+ LPE
device(pcmcia, .type=$(PCCARD_TYPE_NETWORK)
.subtype=$(PCCARD_NETWORK_ETHER),
.progif=$(PCCARD_NETWORK_ETHER_NE2000))
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
# assume pcmcia only have one ethernet card for now so en0 is always
used
#	mount(-Tio-pkt "-oioport=0x$(ioport),irq=$(irq)"
/lib/dll/devn-ne2000.so, "/dev/io-net/en$(netnum)")
	mount(-Tio-pkt "-oioport=0x$(ioport),irq=$(irq)"
/lib/dll/devn-ne2000.so, "/dev/io-net/en0")
	use(symbolic=netmgr)

device(cardbus, ven=10b7, dev=5157)
device(cardbus, ven=10b7, dev=5257)
device(cardbus, ven=10b7, dev=6560)
device(cardbus, ven=10b7, dev=6562)
device(cardbus, ven=10b7, dev=6564)
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
# assume cardbus only have one ethernet card for now so en0 is always
used
	mount(-Tio-pkt "-opci=$(index),vid=0x$(ven),did=0x$(dev)"
/lib/dll/devn-el900.so, "/dev/io-net/en$(netnum)")
	use(symbolic=netmgr)

device(cardbus, ven=8086, dev=1229)
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
# assume cardbus only have one ethernet card for now so en0 is always
used
	mount(-Tio-pkt "-opci=$(index),vid=0x$(ven),did=0x$(dev)"
/lib/dll/devn-speedo.so, "/dev/io-net/en$(netnum)")
	use(symbolic=netmgr)

device(cardbus, ven=1011, dev=0019)
device(cardbus, ven=$(PCI_VEND_ABOCOM), dev=ab02)	# Abocom FE2500
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
# assume cardbus only have one ethernet card for now so en0 is always
used
	mount(-Tio-pkt "-opci=$(index),vid=0x$(ven),did=0x$(dev)"
/lib/dll/devn-tulip.so, "/dev/io-net/en$(netnum)")
	use(symbolic=netmgr)

device(cardbus, ven=10b8, dev=0006)
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor...

OK...  Tried that out and everything worked for me on my system.   Can
you try commenting out the "start(netmanager)" line and see what
happens? Do you have a /etc/net.cfg file present?

In terms of ths power-down hang, you might have to ask in another forum.
What happens if you try a "shutdown -f" from the commmand line?

	Robert.

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

Robert,
I was unable to reproduce this boot-up hang without the Linksys dongle
inserted.  The power-down hang occurs regardless of whether or not the
Linksys dongle is inserted or not.

The contents of my /etc/netconfig file is:

udp6       tpi_clts      v     inet6    udp     -       -
tcp6       tpi_cots_ord  v     inet6    tcp     -       -
udp        tpi_clts      v     inet     udp     -       -
tcp        tpi_cots_ord  v     inet     tcp     -       -
rawip      tpi_raw       -     inet      -      -       -
local      tpi_cots_ord  -     loopback  -      -       -

The contents of my /etc/system/enum/devices/net file is (see the
"gemhack" comments below to see what I added):

#
# Definitions for net devices
#

# Make sure ionet starts even if there is no network card (for 127.1)
device(none, .type=$(ISA_TYPE_NETWORK))
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	
# ne1000/ne2000 devices
device(isa, .type=$(ISA_TYPE_NETWORK), .subtype=$(ISA_NETWORK_ETHER),
.progif=00)
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
	mount(-Tio-pkt "-oioport=0x$(ioport)" /lib/dll/devn-ne2000.so,
"/dev/io-net/en$(netnum)")
	use(symbolic=netmgr)
	
device(pci, ven=$(PCI_VEND_REALTEK), dev=8029)
device(pci, ven=$(PCI_VEND_WINBOND), dev=0940)		#89C940
device(pci, ven=$(PCI_VEND_POWERMATIC), dev=1401)	#Compex RL2000
device(pci, ven=$(PCI_VEND_KTI), dev=3000)			#ET32P2
device(pci, ven=$(PCI_VEND_NETVIN), dev=5000)		#NV5000SC
device(pci, ven=$(PCI_VEND_VIA), dev=0926)			#82C926
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
	mount(-Tio-pkt "-opci=$(index),vid=0x$(ven),did=0x$(dev)"
/lib/dll/devn-ne2000.so, "/dev/io-net/en$(netnum)")
	use(symbolic=netmgr)

device(pcmcia, ven=$(PCCARD_VEND_DLINK), dev=021b)
device(pcmcia, ven=$(PCCARD_VEND_SOCKET), dev=000d)	#PCMCIA LPE
device(pcmcia, ven=$(PCCARD_VEND_SOCKET), dev=0075)	#CF+ LPE
device(pcmcia, .type=$(PCCARD_TYPE_NETWORK)
.subtype=$(PCCARD_NETWORK_ETHER),
.progif=$(PCCARD_NETWORK_ETHER_NE2000))
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
# assume pcmcia only have one ethernet card for now so en0 is always
used
#	mount(-Tio-pkt "-oioport=0x$(ioport),irq=$(irq)"
/lib/dll/devn-ne2000.so, "/dev/io-net/en$(netnum)")
	mount(-Tio-pkt "-oioport=0x$(ioport),irq=$(irq)"
/lib/dll/devn-ne2000.so, "/dev/io-net/en0")
	use(symbolic=netmgr)

device(cardbus, ven=10b7, dev=5157)
device(cardbus, ven=10b7, dev=5257)
device(cardbus, ven=10b7, dev=6560)
device(cardbus, ven=10b7, dev=6562)
device(cardbus, ven=10b7, dev=6564)
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
# assume cardbus only have one ethernet card for now so en0 is always
used
	mount(-Tio-pkt "-opci=$(index),vid=0x$(ven),did=0x$(dev)"
/lib/dll/devn-el900.so, "/dev/io-net/en$(netnum)")
	use(symbolic=netmgr)

device(cardbus, ven=8086, dev=1229)
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
# assume cardbus only have one ethernet card for now so en0 is always
used
	mount(-Tio-pkt "-opci=$(index),vid=0x$(ven),did=0x$(dev)"
/lib/dll/devn-speedo.so,...

Robert,
Well, it doesn't fail to boot every time.  It's probably hanging 1 in
every 30 attempts.
I tried commenting out the line you suggested and the failure still
occurred.  I do not have an "/etc/net.cfg" file.

When I'm not running one of these reset tests, I usually use "shutdown
-f" to reboot the system and have never noticed the hang, but then
again, during my testing it happens approximatetly 1 in 100 cycles. 

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

OK...  Tried that out and everything worked for me on my system.   Can
you try commenting out the "start(netmanager)" line and see what
happens? Do you have a /etc/net.cfg file present?

In terms of ths power-down hang, you might have to ask in another forum.
What happens if you try a "shutdown -f" from the commmand line?

	Robert.

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

Robert,
I was unable to reproduce this boot-up hang without the Linksys dongle
inserted.  The power-down hang occurs regardless of whether or not the
Linksys dongle is inserted or not.

The contents of my /etc/netconfig file is:

udp6       tpi_clts      v     inet6    udp     -       -
tcp6       tpi_cots_ord  v     inet6    tcp     -       -
udp        tpi_clts      v     inet     udp     -       -
tcp        tpi_cots_ord  v     inet     tcp     -       -
rawip      tpi_raw       -     inet      -      -       -
local      tpi_cots_ord  -     loopback  -      -       -

The contents of my /etc/system/enum/devices/net file is (see the
"gemhack" comments below to see what I added):

#
# Definitions for net devices
#

# Make sure ionet starts even if there is no network card (for 127.1)
device(none, .type=$(ISA_TYPE_NETWORK))
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	
# ne1000/ne2000 devices
device(isa, .type=$(ISA_TYPE_NETWORK), .subtype=$(ISA_NETWORK_ETHER),
.progif=00)
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
	mount(-Tio-pkt "-oioport=0x$(ioport)" /lib/dll/devn-ne2000.so,
"/dev/io-net/en$(netnum)")
	use(symbolic=netmgr)
	
device(pci, ven=$(PCI_VEND_REALTEK), dev=8029)
device(pci, ven=$(PCI_VEND_WINBOND), dev=0940)		#89C940
device(pci, ven=$(PCI_VEND_POWERMATIC), dev=1401)	#Compex RL2000
device(pci, ven=$(PCI_VEND_KTI), dev=3000)			#ET32P2
device(pci, ven=$(PCI_VEND_NETVIN), dev=5000)		#NV5000SC
device(pci, ven=$(PCI_VEND_VIA), dev=0926)			#82C926
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
	mount(-Tio-pkt "-opci=$(index),vid=0x$(ven),did=0x$(dev)"
/lib/dll/devn-ne2000.so, "/dev/io-net/en$(netnum)")
	use(symbolic=netmgr)

device(pcmcia, ven=$(PCCARD_VEND_DLINK), dev=021b)
device(pcmcia, ven=$(PCCARD_VEND_SOCKET), dev=000d)	#PCMCIA LPE
device(pcmcia, ven=$(PCCARD_VEND_SOCKET), dev=0075)	#CF+ LPE
device(pcmcia, .type=$(PCCARD_TYPE_NETWORK)
.subtype=$(PCCARD_NETWORK_ETHER),
.progif=$(PCCARD_NETWORK_ETHER_NE2000))
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
# assume pcmcia only have one ethernet card for now so en0 is always
used
#	mount(-Tio-pkt "-oioport=0x$(ioport),irq=$(irq)"
/lib/dll/devn-ne2000.so, "/dev/io-net/en$(netnum)")
	mount(-Tio-pkt "-oioport=0x$(ioport),irq=$(irq)"
/lib/dll/devn-ne2000.so, "/dev/io-net/en0")
	use(symbolic=netmgr)

device(cardbus, ven=10b7, dev=5157)
device(cardbus, ven=10b7, dev=5257)
device(cardbus, ven=10b7, dev=6560)
device(cardbus, ven=10b7, dev=6562)
device(cardbus, ven=10b7,...

Well THAT certainly makes things harder to track down.  No netmanager or
net.cfg file means that the interface isn't getting brought up so it's
something to do with the attach.  The problem with tracking down any of
these boot problems is that, without a shell, you really can't figure
out what the system is doing while it's "not booting" so it's divide and
conquer.


Can you try increasing the verbosity on enum-devices to get more output
and post the log when it fails?  I'll try to see if by machine survives
multiple re-boots.

Come to think of it, by re-boot, do you mean a re-start after "shutdown
-f" or a full power cycle?

	Robert.
 

-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com] 
Sent: Friday, January 16, 2009 7:31 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Robert,
Well, it doesn't fail to boot every time.  It's probably hanging 1 in
every 30 attempts.
I tried commenting out the line you suggested and the failure still
occurred.  I do not have an "/etc/net.cfg" file.

When I'm not running one of these reset tests, I usually use "shutdown
-f" to reboot the system and have never noticed the hang, but then
again, during my testing it happens approximatetly 1 in 100 cycles. 

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

OK...  Tried that out and everything worked for me on my system.   Can
you try commenting out the "start(netmanager)" line and see what
happens? Do you have a /etc/net.cfg file present?

In terms of ths power-down hang, you might have to ask in another forum.
What happens if you try a "shutdown -f" from the commmand line?

	Robert.

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

Robert,
I was unable to reproduce this boot-up hang without the Linksys dongle
inserted.  The power-down hang occurs regardless of whether or not the
Linksys dongle is inserted or not.

The contents of my /etc/netconfig file is:

udp6       tpi_clts      v     inet6    udp     -       -
tcp6       tpi_cots_ord  v     inet6    tcp     -       -
udp        tpi_clts      v     inet     udp     -       -
tcp        tpi_cots_ord  v     inet     tcp     -       -
rawip      tpi_raw       -     inet      -      -       -
local      tpi_cots_ord  -     loopback  -      -       -

The contents of my /etc/system/enum/devices/net file is (see the
"gemhack" comments below to see what I added):

#
# Definitions for net devices
#

# Make sure ionet starts even if there is no network card (for 127.1)
device(none, .type=$(ISA_TYPE_NETWORK))
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	
# ne1000/ne2000 devices
device(isa, .type=$(ISA_TYPE_NETWORK), .subtype=$(ISA_NETWORK_ETHER),
.progif=00)
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
	mount(-Tio-pkt "-oioport=0x$(ioport)" /lib/dll/devn-ne2000.so,
"/dev/io-net/en$(netnum)")
	use(symbolic=netmgr)
	
device(pci, ven=$(PCI_VEND_REALTEK), dev=8029)
device(pci, ven=$(PCI_VEND_WINBOND), dev=0940)		#89C940
device(pci, ven=$(PCI_VEND_POWERMATIC), dev=1401)	#Compex RL2000
device(pci, ven=$(PCI_VEND_KTI), dev=3000)			#ET32P2
device(pci, ven=$(PCI_VEND_NETVIN), dev=5000)		#NV5000SC
device(pci, ven=$(PCI_VEND_VIA), dev=0926)			#82C926
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
	mount(-Tio-pkt "-opci=$(index),vid=0x$(ven),did=0x$(dev)"
/lib/dll/devn-ne2000.so,...

My tests perform a "soft" reset, not a power-cycle. 

-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com] 
Sent: Friday, January 16, 2009 11:37 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Well THAT certainly makes things harder to track down.  No netmanager or
net.cfg file means that the interface isn't getting brought up so it's
something to do with the attach.  The problem with tracking down any of
these boot problems is that, without a shell, you really can't figure
out what the system is doing while it's "not booting" so it's divide and
conquer.


Can you try increasing the verbosity on enum-devices to get more output
and post the log when it fails?  I'll try to see if by machine survives
multiple re-boots.

Come to think of it, by re-boot, do you mean a re-start after "shutdown
-f" or a full power cycle?

	Robert.
 

-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Friday, January 16, 2009 7:31 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Robert,
Well, it doesn't fail to boot every time.  It's probably hanging 1 in
every 30 attempts.
I tried commenting out the line you suggested and the failure still
occurred.  I do not have an "/etc/net.cfg" file.

When I'm not running one of these reset tests, I usually use "shutdown
-f" to reboot the system and have never noticed the hang, but then
again, during my testing it happens approximatetly 1 in 100 cycles. 

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

OK...  Tried that out and everything worked for me on my system.   Can
you try commenting out the "start(netmanager)" line and see what
happens? Do you have a /etc/net.cfg file present?

In terms of ths power-down hang, you might have to ask in another forum.
What happens if you try a "shutdown -f" from the commmand line?

	Robert.

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

Robert,
I was unable to reproduce this boot-up hang without the Linksys dongle
inserted.  The power-down hang occurs regardless of whether or not the
Linksys dongle is inserted or not.

The contents of my /etc/netconfig file is:

udp6       tpi_clts      v     inet6    udp     -       -
tcp6       tpi_cots_ord  v     inet6    tcp     -       -
udp        tpi_clts      v     inet     udp     -       -
tcp        tpi_cots_ord  v     inet     tcp     -       -
rawip      tpi_raw       -     inet      -      -       -
local      tpi_cots_ord  -     loopback  -      -       -

The contents of my /etc/system/enum/devices/net file is (see the
"gemhack" comments below to see what I added):

#
# Definitions for net devices
#

# Make sure ionet starts even if there is no network card (for 127.1)
device(none, .type=$(ISA_TYPE_NETWORK))
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	
# ne1000/ne2000 devices
device(isa, .type=$(ISA_TYPE_NETWORK), .subtype=$(ISA_NETWORK_ETHER),
.progif=00)
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	uniq(netnum, devn-en, 0)
	mount(-Tio-pkt "-oioport=0x$(ioport)" /lib/dll/devn-ne2000.so,
"/dev/io-net/en$(netnum)")
	use(symbolic=netmgr)
	
device(pci, ven=$(PCI_VEND_REALTEK), dev=8029)
device(pci, ven=$(PCI_VEND_WINBOND), dev=0940)		#89C940
device(pci, ven=$(PCI_VEND_POWERMATIC), dev=1401)	#Compex RL2000
device(pci, ven=$(PCI_VEND_KTI), dev=3000)			#ET32P2
device(pci, ven=$(PCI_VEND_NETVIN), dev=5000)		#NV5000SC
device(pci,...

Ahhh... That means that the hardware is in a potentially "indeterminate"
state...  Nothing like making a problem a little more challenging :>.  

Increasing the verbosity of enum-devices would still be useful... 

   Robert. 

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

My tests perform a "soft" reset, not a power-cycle. 

-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: Friday, January 16, 2009 11:37 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Well THAT certainly makes things harder to track down.  No netmanager or
net.cfg file means that the interface isn't getting brought up so it's
something to do with the attach.  The problem with tracking down any of
these boot problems is that, without a shell, you really can't figure
out what the system is doing while it's "not booting" so it's divide and
conquer.


Can you try increasing the verbosity on enum-devices to get more output
and post the log when it fails?  I'll try to see if by machine survives
multiple re-boots.

Come to think of it, by re-boot, do you mean a re-start after "shutdown
-f" or a full power cycle?

	Robert.
 

-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Friday, January 16, 2009 7:31 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Robert,
Well, it doesn't fail to boot every time.  It's probably hanging 1 in
every 30 attempts.
I tried commenting out the line you suggested and the failure still
occurred.  I do not have an "/etc/net.cfg" file.

When I'm not running one of these reset tests, I usually use "shutdown
-f" to reboot the system and have never noticed the hang, but then
again, during my testing it happens approximatetly 1 in 100 cycles. 

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

OK...  Tried that out and everything worked for me on my system.   Can
you try commenting out the "start(netmanager)" line and see what
happens? Do you have a /etc/net.cfg file present?

In terms of ths power-down hang, you might have to ask in another forum.
What happens if you try a "shutdown -f" from the commmand line?

	Robert.

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

Robert,
I was unable to reproduce this boot-up hang without the Linksys dongle
inserted.  The power-down hang occurs regardless of whether or not the
Linksys dongle is inserted or not.

The contents of my /etc/netconfig file is:

udp6       tpi_clts      v     inet6    udp     -       -
tcp6       tpi_cots_ord  v     inet6    tcp     -       -
udp        tpi_clts      v     inet     udp     -       -
tcp        tpi_cots_ord  v     inet     tcp     -       -
rawip      tpi_raw       -     inet      -      -       -
local      tpi_cots_ord  -     loopback  -      -       -

The contents of my /etc/system/enum/devices/net file is (see the
"gemhack" comments below to see what I added):

#
# Definitions for net devices
#

# Make sure ionet starts even if there is no network card (for 127.1)
device(none, .type=$(ISA_TYPE_NETWORK))
	requires($(IOPKT_CMD),)
	waitfor (/dev/socket)
	
# ne1000/ne2000 devices
device(isa, .type=$(ISA_TYPE_NETWORK), .subtype=$(ISA_NETWORK_ETHER),
.progif=00)
	tag(devn)
	append(legacy, ",nonet")
	requires($(IOPKT_CMD),)
	waitfor...

Robert,
OK, setting VERRBOSE to 9 yielded the following:

  .
  .
  .
  Starting: devb-fdc cam quiet blk auto=partition,cache=100k
  Starting: io-pkt-v4-hc -ptcpip  (skipped: already running)
- this is the point where it would normally hang, but we got the
following 3 lines.
  uset verbose
  test -r /etc/system/config/useqnet -a -d /dev/socket
  mount -Tio-pkt lsm-qnet.so
 

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

Ahhh... That means that the hardware is in a potentially "indeterminate"
state...  Nothing like making a problem a little more challenging :>.  

Increasing the verbosity of enum-devices would still be useful... 

   Robert. 

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

My tests perform a "soft" reset, not a power-cycle. 

-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: Friday, January 16, 2009 11:37 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Well THAT certainly makes things harder to track down.  No netmanager or
net.cfg file means that the interface isn't getting brought up so it's
something to do with the attach.  The problem with tracking down any of
these boot problems is that, without a shell, you really can't figure
out what the system is doing while it's "not booting" so it's divide and
conquer.


Can you try increasing the verbosity on enum-devices to get more output
and post the log when it fails?  I'll try to see if by machine survives
multiple re-boots.

Come to think of it, by re-boot, do you mean a re-start after "shutdown
-f" or a full power cycle?

	Robert.
 

-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Friday, January 16, 2009 7:31 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Robert,
Well, it doesn't fail to boot every time.  It's probably hanging 1 in
every 30 attempts.
I tried commenting out the line you suggested and the failure still
occurred.  I do not have an "/etc/net.cfg" file.

When I'm not running one of these reset tests, I usually use "shutdown
-f" to reboot the system and have never noticed the hang, but then
again, during my testing it happens approximatetly 1 in 100 cycles. 

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

OK...  Tried that out and everything worked for me on my system.   Can
you try commenting out the "start(netmanager)" line and see what
happens? Do you have a /etc/net.cfg file present?

In terms of ths power-down hang, you might have to ask in another forum.
What happens if you try a "shutdown -f" from the commmand line?

	Robert.

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

Robert,
I was unable to reproduce this boot-up hang without the Linksys dongle
inserted.  The power-down hang occurs regardless of whether or not the
Linksys dongle is inserted or not.

The contents of my /etc/netconfig file is:

udp6       tpi_clts      v     inet6    udp     -       -
tcp6       tpi_cots_ord  v     inet6    tcp     -       -
udp        tpi_clts      v     inet     udp     -       -
tcp        tpi_cots_ord  v     inet     tcp     -     ...

Do I read that right and it appears to hang after mounting qnet?

	Robert. 

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

Robert,
OK, setting VERRBOSE to 9 yielded the following:

  .
  .
  .
  Starting: devb-fdc cam quiet blk auto=partition,cache=100k
  Starting: io-pkt-v4-hc -ptcpip  (skipped: already running)
- this is the point where it would normally hang, but we got the
following 3 lines.
  uset verbose
  test -r /etc/system/config/useqnet -a -d /dev/socket
  mount -Tio-pkt lsm-qnet.so
 

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

Ahhh... That means that the hardware is in a potentially "indeterminate"
state...  Nothing like making a problem a little more challenging :>.  

Increasing the verbosity of enum-devices would still be useful... 

   Robert. 

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

My tests perform a "soft" reset, not a power-cycle. 

-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: Friday, January 16, 2009 11:37 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Well THAT certainly makes things harder to track down.  No netmanager or
net.cfg file means that the interface isn't getting brought up so it's
something to do with the attach.  The problem with tracking down any of
these boot problems is that, without a shell, you really can't figure
out what the system is doing while it's "not booting" so it's divide and
conquer.


Can you try increasing the verbosity on enum-devices to get more output
and post the log when it fails?  I'll try to see if by machine survives
multiple re-boots.

Come to think of it, by re-boot, do you mean a re-start after "shutdown
-f" or a full power cycle?

	Robert.
 

-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Friday, January 16, 2009 7:31 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Robert,
Well, it doesn't fail to boot every time.  It's probably hanging 1 in
every 30 attempts.
I tried commenting out the line you suggested and the failure still
occurred.  I do not have an "/etc/net.cfg" file.

When I'm not running one of these reset tests, I usually use "shutdown
-f" to reboot the system and have never noticed the hang, but then
again, during my testing it happens approximatetly 1 in 100 cycles. 

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

OK...  Tried that out and everything worked for me on my system.   Can
you try commenting out the "start(netmanager)" line and see what
happens? Do you have a /etc/net.cfg file present?

In terms of ths power-down hang, you might have to ask in another forum.
What happens if you try a "shutdown -f" from the commmand line?

	Robert.

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

Robert,
I was unable to reproduce this boot-up hang without the Linksys dongle
inserted.  The power-down hang occurs regardless of whether or not...

Yes, I have confirmed it a second time.  That is the last output shown
on the console. 

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

Do I read that right and it appears to hang after mounting qnet?

	Robert. 

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

Robert,
OK, setting VERRBOSE to 9 yielded the following:

  .
  .
  .
  Starting: devb-fdc cam quiet blk auto=partition,cache=100k
  Starting: io-pkt-v4-hc -ptcpip  (skipped: already running)
- this is the point where it would normally hang, but we got the
following 3 lines.
  uset verbose
  test -r /etc/system/config/useqnet -a -d /dev/socket
  mount -Tio-pkt lsm-qnet.so
 

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

Ahhh... That means that the hardware is in a potentially "indeterminate"
state...  Nothing like making a problem a little more challenging :>.  

Increasing the verbosity of enum-devices would still be useful... 

   Robert. 

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

My tests perform a "soft" reset, not a power-cycle. 

-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: Friday, January 16, 2009 11:37 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Well THAT certainly makes things harder to track down.  No netmanager or
net.cfg file means that the interface isn't getting brought up so it's
something to do with the attach.  The problem with tracking down any of
these boot problems is that, without a shell, you really can't figure
out what the system is doing while it's "not booting" so it's divide and
conquer.


Can you try increasing the verbosity on enum-devices to get more output
and post the log when it fails?  I'll try to see if by machine survives
multiple re-boots.

Come to think of it, by re-boot, do you mean a re-start after "shutdown
-f" or a full power cycle?

	Robert.
 

-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Friday, January 16, 2009 7:31 AM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)

Robert,
Well, it doesn't fail to boot every time.  It's probably hanging 1 in
every 30 attempts.
I tried commenting out the line you suggested and the failure still
occurred.  I do not have an "/etc/net.cfg" file.

When I'm not running one of these reset tests, I usually use "shutdown
-f" to reboot the system and have never noticed the hang, but then
again, during my testing it happens approximatetly 1 in 100 cycles. 

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

OK...  Tried that out and everything worked for me on my system.   Can
you try commenting out the "start(netmanager)" line and see what
happens? Do you have a /etc/net.cfg file present?

In terms of ths power-down hang, you might have to ask in another forum.
What happens if you try a "shutdown -f" from the commmand line?

	Robert.

-----Original Message-----
From: Gordon Molek...