|
|
Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/14/2008 1:10 AM
post16549
|
Problems getting USB wireless working (Ralink RT2501USB chipset)
Hi,
I am trying to get a Linksys WUSB54GC-AS USB Wireless adapter working which I believe should have a Ralink RT2501USB
chipset.
I can start the devnp-rum.so driver successfully using the command:
#io-pkt-v6-hc -v -d rum
The resulting slog is as follows:
----------------------------------------------------
Time Sev Major Minor Args
Jan 01 00:21:57 5 14 0 tcpip starting
Jan 01 00:21:57 3 14 0 Unable to attach to pci server: No such file or directory
Jan 01 00:21:57 3 14 0 Using pseudo random generator. See "random" option
Jan 01 00:21:57 5 14 0 initializing IPsec... done
Jan 01 00:21:57 5 14 0 IPsec: Initialized Security Association Processing.
Jan 01 00:21:57 5 14 0 USB device vendor 0x13b1, device 0x20 matched.
Jan 01 00:21:57 5 14 0 rum0 at pci0 dev 0 function 0rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:
2
1:29:de:ff:9e
Jan 01 00:21:57 5 14 0 ether_ifattach: rum0 null if_stop
Jan 01 00:21:57 5 14 0 rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
Jan 01 00:21:57 5 14 0 rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps
48Mb
ps 54Mbps
----------------------------------------------------
However once I set the interface status to up (using the command: ifconfig rum0 up), I get the following errors in slog:
----------------------------------------------------
Time Sev Major Minor Args
Nov 08 23:08:25 6 816493 1862 ite MAC register: NOMEM
Mar 22 22:57:57 2 204858 1782 544501614 1953265005 1920409705 543519849 541278541 1768383858 1919251571 1330520122
5
064013 799325 14 1448 812479858 1868767290 543452277 544501614 1953265005 1701978217 1293968481 1914716993 1936287589
980
575604 1297042976 19781 799357 14 1448 812479858 1868767290 543452277 544501614 1953265005 1920409705 543519849
541278541
1768383858 1919251571 1330520122 5064013 799421 14 1448 812479858 1868767290 543452277 544501614 1953265005 1701978217
1
293968481 1914716993 1936287589 980575604 1297042976 19781 799453 14 1448 812479858 1868767290 543452277 544501614
195326
5005 1920409705 543519849 541278541 1768383858 1919251571 1330520122 5064013 799517 14 1448 812479858 1868767290
54345227
7 544501614 1953265005 1701978217 1293968481 1914716993 1936287589 980575604 1297042976 19781 799549 14 1448 812479858
18
68767290 543452277 544501614 1953265005 1920409705 543519849 541278541 1768383858 1919251571 1330520122 5064013 799613
14
1448 812479858 1868767290 543452277 544501614 1953265005 1701978217 1293968481
Jan 27 06:06:44 1 616293 1846 1297042976 19781 799645 14 1448 812479858 1868767290 543452277 544501614 1953265005
19
20409705 543519849 541278541 1768383858 1919251571 1330520122 5064013 799709 14 1448 812479858 1868767290 543452277
54450
1614 1953265005 1701978217 1293968481 1914716993 1936287589 980575604 1297042976 19781
Jan 01 00:24:08 5 14 0 rum0: could not multi write MAC register: NOMEM
Jan 01 00:24:08 5 14 0 rum0: could not multi read MAC register: NOMEM
Jan 01 00:24:10 5 14 0 rum0: timeout waiting for BBP/RF to wakeup
Jan 01 00:24:10 5 14 0 rum0: could not multi read MAC register: NOMEM
Jan 01 00:24:10 5 14 0 rum0: could not multi write MAC register: NOMEM
----------------------------------------------------
Running USB, the device is detected as follows:
----------------------------------------------------
Device Address : 2
Upstream Host Controller : 0
Upstream Device Address : 1
Upstream Port : 4
Upstream Port Speed : Full
Vendor : 0x13b1 (Cisco-Linksys)
Product : 0x0020 (Compact Wireless-G USB Adapter)
Device Release : r0.01
USB Spec Release : v2.00
Serial Number : N/A
Class : 0x00 (Independent per...
View Full Message
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/14/2008 11:40 AM
post16585
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Although the device designation (WUSB-54GC-AS) is different from mine
(WUSB-54GC), the USB vendor and device appear to be the same, so it
should be working (I've tested it here and it works fine).
Is this on x86? Have you already stopped io-pkt-v4-hc which was
launched on boot?
The driver code is here
http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/dev/u
sb/if_rum.c?root=core_networking&rev=562&system=exsy1001&view=markup
Here's where the failure appears to be occuring (in usb_do_request):
http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib/l
ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=411&system=exsy1001
&view=markup
So it looks like usbd_alloc is failing to allocate memory.
Are you operating in a very low memory situation ("pidin in" should
help)?
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Friday, November 14, 2008 1:10 AM
To: general-networking
Subject: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Hi,
I am trying to get a Linksys WUSB54GC-AS USB Wireless adapter working
which I believe should have a Ralink RT2501USB chipset.
I can start the devnp-rum.so driver successfully using the command:
#io-pkt-v6-hc -v -d rum
The resulting slog is as follows:
----------------------------------------------------
Time Sev Major Minor Args
Jan 01 00:21:57 5 14 0 tcpip starting
Jan 01 00:21:57 3 14 0 Unable to attach to pci server: No such
file or directory
Jan 01 00:21:57 3 14 0 Using pseudo random generator. See
"random" option
Jan 01 00:21:57 5 14 0 initializing IPsec... done
Jan 01 00:21:57 5 14 0 IPsec: Initialized Security Association
Processing.
Jan 01 00:21:57 5 14 0 USB device vendor 0x13b1, device 0x20
matched.
Jan 01 00:21:57 5 14 0 rum0 at pci0 dev 0 function 0rum0:
MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:2
1:29:de:ff:9e
Jan 01 00:21:57 5 14 0 ether_ifattach: rum0 null if_stop
Jan 01 00:21:57 5 14 0 rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps
11Mbps
Jan 01 00:21:57 5 14 0 rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps
11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mb
ps 54Mbps
----------------------------------------------------
However once I set the interface status to up (using the command:
ifconfig rum0 up), I get the following errors in slog:
----------------------------------------------------
Time Sev Major Minor Args
Nov 08 23:08:25 6 816493 1862 ite MAC register: NOMEM
Mar 22 22:57:57 2 204858 1782 544501614 1953265005 1920409705
543519849 541278541 1768383858 1919251571 1330520122 5
064013 799325 14 1448 812479858 1868767290 543452277 544501614
1953265005 1701978217 1293968481 1914716993 1936287589 980
575604 1297042976 19781 799357 14 1448 812479858 1868767290 543452277
544501614 1953265005 1920409705 543519849 541278541
1768383858 1919251571 1330520122 5064013 799421 14 1448 812479858
1868767290 543452277 544501614 1953265005 1701978217 1
293968481 1914716993 1936287589 980575604 1297042976 19781 799453 14
1448 812479858 1868767290 543452277 544501614 195326
5005 1920409705 543519849 541278541 1768383858 1919251571 1330520122
5064013 799517 14 1448 812479858 1868767290 54345227
7 544501614 1953265005 1701978217 1293968481 1914716993 1936287589
980575604 1297042976 19781 799549 14 1448 812479858 18 68767290
543452277 544501614 1953265005 1920409705 543519849 541278541 1768383858
1919251571 1330520122 5064013 799613 14
1448 812479858 1868767290 543452277 544501614 1953265005 1701978217
1293968481
Jan 27 06:06:44 1 616293 1846 1297042976 19781 799645 14 1448
812479858 1868767290 543452277 544501614 1953265005 19
20409705 543519849 541278541 1768383858 1919251571 1330520122 5064013
799709 14 1448 812479858 1868767290 543452277 54450
1614 1953265005...
View Full Message
|
|
|
|
|
|
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/16/2008 6:48 PM
post16626
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hi Robert,
Thanks for the quick reply!
The system it is running on is an ARM-le device (Freescale i.MX31 ADS board).
Yes I stopped the instance of io-pkt-v4-hc loaded during bootup first.
In terms of memory, pidin in gives the following output:
CPU:ARM Release:6.4.0 FreeMem:106Mb/128Mb BootTime:Jan 01 00:00:00 UTC 1970
Processor1: 1091023716 arm1136 532MHz FPU
I would assume this is enough memory for the device?
> Although the device designation (WUSB-54GC-AS) is different from mine
> (WUSB-54GC), the USB vendor and device appear to be the same, so it
> should be working (I've tested it here and it works fine).
>
> Is this on x86? Have you already stopped io-pkt-v4-hc which was
> launched on boot?
>
> The driver code is here
> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/dev/u
> sb/if_rum.c?root=core_networking&rev=562&system=exsy1001&view=markup
>
> Here's where the failure appears to be occuring (in usb_do_request):
>
> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib/l
> ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=411&system=exsy1001
> &view=markup
>
>
> So it looks like usbd_alloc is failing to allocate memory.
>
> Are you operating in a very low memory situation ("pidin in" should
> help)?
>
> Robert.
>
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/17/2008 4:56 PM
post16701
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
That should be plenty.... Hmmmm.... I seem to remember that ARM is
somewhat strange when it comes to how much memory a process can use at
one time, but I seem to remember that we have had people using the
Linksys dongle on an ARM platform...
What does "pidin -p io-pkt-v4-hc mem" report with the rum driver
running?
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Sunday, November 16, 2008 6:48 PM
To: general-networking
Subject: Re: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Hi Robert,
Thanks for the quick reply!
The system it is running on is an ARM-le device (Freescale i.MX31 ADS
board).
Yes I stopped the instance of io-pkt-v4-hc loaded during bootup first.
In terms of memory, pidin in gives the following output:
CPU:ARM Release:6.4.0 FreeMem:106Mb/128Mb BootTime:Jan 01 00:00:00 UTC
1970
Processor1: 1091023716 arm1136 532MHz FPU
I would assume this is enough memory for the device?
> Although the device designation (WUSB-54GC-AS) is different from mine
> (WUSB-54GC), the USB vendor and device appear to be the same, so it
> should be working (I've tested it here and it works fine).
>
> Is this on x86? Have you already stopped io-pkt-v4-hc which was
> launched on boot?
>
> The driver code is here
> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/dev
> /u
> sb/if_rum.c?root=core_networking&rev=562&system=exsy1001&view=markup
>
> Here's where the failure appears to be occuring (in usb_do_request):
>
> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib
> /l
> ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=411&system=exsy10
> 01
> &view=markup
>
>
> So it looks like usbd_alloc is failing to allocate memory.
>
> Are you operating in a very low memory situation ("pidin in" should
> help)?
>
> Robert.
>
_______________________________________________
General
http://community.qnx.com/sf/go/post16626
|
|
|
|
|
|
|
Re: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/17/2008 4:58 PM
post16702
|
Re: Problems getting USB wireless working (Ralink RT2501USB chipset)
Which procnto are you running? I think the imx31 can run procnto-v6 which would eliminate the 32Mb problem..
Robert Craig wrote:
> That should be plenty.... Hmmmm.... I seem to remember that ARM is
> somewhat strange when it comes to how much memory a process can use at
> one time, but I seem to remember that we have had people using the
> Linksys dongle on an ARM platform...
>
> What does "pidin -p io-pkt-v4-hc mem" report with the rum driver
> running?
>
>
> Robert.
>
> -----Original Message-----
> From: Radek Pesina [mailto:community-noreply@qnx.com]
> Sent: Sunday, November 16, 2008 6:48 PM
> To: general-networking
> Subject: Re: RE: Problems getting USB wireless working (Ralink RT2501USB
> chipset)
>
> Hi Robert,
>
> Thanks for the quick reply!
>
> The system it is running on is an ARM-le device (Freescale i.MX31 ADS
> board).
>
> Yes I stopped the instance of io-pkt-v4-hc loaded during bootup first.
>
> In terms of memory, pidin in gives the following output:
>
> CPU:ARM Release:6.4.0 FreeMem:106Mb/128Mb BootTime:Jan 01 00:00:00 UTC
> 1970
> Processor1: 1091023716 arm1136 532MHz FPU
>
>
> I would assume this is enough memory for the device?
>
>
>
>
>> Although the device designation (WUSB-54GC-AS) is different from mine
>> (WUSB-54GC), the USB vendor and device appear to be the same, so it
>> should be working (I've tested it here and it works fine).
>>
>> Is this on x86? Have you already stopped io-pkt-v4-hc which was
>> launched on boot?
>>
>> The driver code is here
>> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/dev
>> /u
>> sb/if_rum.c?root=core_networking&rev=562&system=exsy1001&view=markup
>>
>> Here's where the failure appears to be occuring (in usb_do_request):
>>
>> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib
>> /l
>> ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=411&system=exsy10
>> 01
>> &view=markup
>>
>>
>> So it looks like usbd_alloc is failing to allocate memory.
>>
>> Are you operating in a very low memory situation ("pidin in" should
>> help)?
>>
>> Robert.
>>
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post16626
>
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post16701
>
--
cburgess@qnx.com
|
|
|
|
|
|
|
Re: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/17/2008 5:11 PM
post16705
|
Re: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hi Robert and Colin,
In terms of procnto, currently I am running procnto-v6.
Pidin reports the following with the rum driver running:
# pidin -p io-pkt-v4-hc mem
pid tid name prio STATE code data stack
12303 1 /boot/io-pkt-v4-hc 21r SIGWAITINFO 944K 500K 4096(132K)*
12303 2 /boot/io-pkt-v4-hc 21r RECEIVE 944K 500K 8192(132K)
12303 3 /boot/io-pkt-v4-hc 21r REPLY 944K 500K 4096(20K)
libc.so.3 @ 1000000 448K 12K
devnp-rum.so @78000000 64K 8192
> Which procnto are you running? I think the imx31 can run procnto-v6 which
> would eliminate the 32Mb problem..
>
>
> Robert Craig wrote:
> > That should be plenty.... Hmmmm.... I seem to remember that ARM is
> > somewhat strange when it comes to how much memory a process can use at
> > one time, but I seem to remember that we have had people using the
> > Linksys dongle on an ARM platform...
> >
> > What does "pidin -p io-pkt-v4-hc mem" report with the rum driver
> > running?
> >
> >
> > Robert.
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/17/2008 5:13 PM
post16706
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
So that all looks fine (I would have been worried if networking were
taking 32 MB!)
Do other USB devices work on the platform (e.g. mass storage devices)?
Can you post the output from
pidin ar
?
R.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Monday, November 17, 2008 5:11 PM
To: general-networking
Subject: Re: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Hi Robert and Colin,
In terms of procnto, currently I am running procnto-v6.
Pidin reports the following with the rum driver running:
# pidin -p io-pkt-v4-hc mem
pid tid name prio STATE code data
stack
12303 1 /boot/io-pkt-v4-hc 21r SIGWAITINFO 944K 500K
4096(132K)*
12303 2 /boot/io-pkt-v4-hc 21r RECEIVE 944K 500K
8192(132K)
12303 3 /boot/io-pkt-v4-hc 21r REPLY 944K 500K
4096(20K)
libc.so.3 @ 1000000 448K 12K
devnp-rum.so @78000000 64K 8192
> Which procnto are you running? I think the imx31 can run procnto-v6
> which would eliminate the 32Mb problem..
>
>
> Robert Craig wrote:
> > That should be plenty.... Hmmmm.... I seem to remember that ARM is
> > somewhat strange when it comes to how much memory a process can use
> > at one time, but I seem to remember that we have had people using
> > the Linksys dongle on an ARM platform...
> >
> > What does "pidin -p io-pkt-v4-hc mem" report with the rum driver
> > running?
> >
> >
> > Robert.
_______________________________________________
General
http://community.qnx.com/sf/go/post16705
|
|
|
|
|
|
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/17/2008 5:21 PM
post16707
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Yes other USB devices work fine on the platform, so far USB hubs, memory card readers and USB flash drives work without
a problem.
Pidin output is as follows:
# pidin ar
pid Arguments
1 proc/boot/procnto-v6
2 devc-sermx1 -e -F -c66500000 0x43F90000,45 0x43F94000,32 -u5 0x43fb4000,47
3 slogger
4 pipe
5 fs-etfs-imx31ads_512 -r 1024
6 devf-mx31ads
7 io-usb -d ehci-mx31 ioport=0x43f88300,irq=35
8 spi-master -d mx31 base=0x50010000,irq=13,waitstate=2
4105 io-audio -v -d imx31ads
4106 io-display -v -dvid=0,did=0 -c/etc/system/config/display.conf
4107 i2c-imx31ads
4108 devb-umass cam pnp blk cache=2m,auto=partition,automount=hd0t14:/fs/usb0 dos exe=all
4109 qconn port=8000
4110 ksh
12303 io-pkt-v4-hc -v -d rum
49168 pidin ar
> So that all looks fine (I would have been worried if networking were
> taking 32 MB!)
>
> Do other USB devices work on the platform (e.g. mass storage devices)?
>
>
> Can you post the output from
>
> pidin ar
>
> ?
>
> R.
>
>
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/18/2008 11:21 AM
post16801
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
I'm really not sure what's happening with this one. I've confirmed that
the driver has been used extensively with an i.MX35 platform without any
problems.
Is devb-umass always running? How about slaying that and trying again?
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Monday, November 17, 2008 5:22 PM
To: general-networking
Subject: Re: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Yes other USB devices work fine on the platform, so far USB hubs, memory
card readers and USB flash drives work without a problem.
Pidin output is as follows:
# pidin ar
pid Arguments
1 proc/boot/procnto-v6
2 devc-sermx1 -e -F -c66500000 0x43F90000,45 0x43F94000,32 -u5
0x43fb4000,47
3 slogger
4 pipe
5 fs-etfs-imx31ads_512 -r 1024
6 devf-mx31ads
7 io-usb -d ehci-mx31 ioport=0x43f88300,irq=35
8 spi-master -d mx31 base=0x50010000,irq=13,waitstate=2
4105 io-audio -v -d imx31ads
4106 io-display -v -dvid=0,did=0 -c/etc/system/config/display.conf
4107 i2c-imx31ads
4108 devb-umass cam pnp blk
cache=2m,auto=partition,automount=hd0t14:/fs/usb0 dos exe=all
4109 qconn port=8000
4110 ksh
12303 io-pkt-v4-hc -v -d rum
49168 pidin ar
> So that all looks fine (I would have been worried if networking were
> taking 32 MB!)
>
> Do other USB devices work on the platform (e.g. mass storage devices)?
>
>
> Can you post the output from
>
> pidin ar
>
> ?
>
> R.
>
>
_______________________________________________
General
http://community.qnx.com/sf/go/post16707
|
|
|
|
|
|
|
Re: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/18/2008 6:17 PM
post16842
|
Re: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Okay I tried changing startup so devb-umass is not started and now after running "ifconfig rum0 up", slog reads a little
differently (and I can see the LED on the adapter flash a couple times during):
Time Sev Major Minor Args
Jan 01 00:01:14 5 14 0 tcpip starting
Jan 01 00:01:14 3 14 0 Unable to attach to pci server: No such file or directory
Jan 01 00:01:14 3 14 0 Using pseudo random generator. See "random" option
Jan 01 00:01:14 5 14 0 initializing IPsec... done
Jan 01 00:01:14 5 14 0 IPsec: Initialized Security Association Processing.
Jan 01 00:01:14 5 14 0 USB device vendor 0x13b1, device 0x20 matched.
Jan 01 00:01:15 5 14 0 rum0 at pci0 dev 0 function 0rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:
2
1:29:de:ff:9e
Jan 01 00:01:15 5 14 0 ether_ifattach: rum0 null if_stop
Jan 01 00:01:15 5 14 0 rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
Jan 01 00:01:15 5 14 0 rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps
48Mb
ps 54Mbps
Jan 01 00:05:50 5 14 0 rum0: could not multi read MAC register: NOMEM
Jan 01 00:05:50 5 14 0 USB error 0x02000005 encountered in io-pkt.
Jan 01 00:05:50 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:05:55 5 14 0 rum0: device timeout
Jan 01 00:05:57 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:06:01 5 14 0 USB error 0x02000005 encountered in io-pkt.
Jan 01 00:06:01 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:06:06 5 14 0 rum0: device timeout
Jan 01 00:06:08 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:06:12 5 14 0 USB error 0x02000005 encountered in io-pkt.
Jan 01 00:06:12 5 14 0 rum0: could not transmit buffer: 24
Jan 01 00:06:14 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:06:17 5 14 0 rum0: device timeout
Jan 01 00:06:19 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Strange considering there is not that much difference between the i.MX31 and i.MX35.
> I'm really not sure what's happening with this one. I've confirmed that
> the driver has been used extensively with an i.MX35 platform without any
> problems.
>
> Is devb-umass always running? How about slaying that and trying again?
>
>
|
|
|
|
|
|
|
RE: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/19/2008 1:51 PM
post16914
|
RE: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hmmm... As soon as I see a single NOMEM then that's an error condition
that's problematic. All the errors are indicative of something being
wrong at the USB layer.
02000005 = URB status 0200 => CMP_ERR and USB Status 0005 = CRC_ERR +
STALL
0a000000 = URB status 0a00 = CMP_ERR + ABORTED (aborted because of the
initial CMP_ERR).
You can see where this message is generated in usb_handle_error in
usb_conv_qnx.c in
http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib/l
ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=583&system=exsy1001
&view=markup
How about a "pidin -p io-usb mem" to see what io-usb is doing with
memory?
R.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Tuesday, November 18, 2008 6:17 PM
To: general-networking
Subject: Re: RE: RE: Problems getting USB wireless working (Ralink
RT2501USB chipset)
Okay I tried changing startup so devb-umass is not started and now after
running "ifconfig rum0 up", slog reads a little differently (and I can
see the LED on the adapter flash a couple times during):
Time Sev Major Minor Args
Jan 01 00:01:14 5 14 0 tcpip starting
Jan 01 00:01:14 3 14 0 Unable to attach to pci server: No such
file or directory
Jan 01 00:01:14 3 14 0 Using pseudo random generator. See
"random" option
Jan 01 00:01:14 5 14 0 initializing IPsec... done
Jan 01 00:01:14 5 14 0 IPsec: Initialized Security Association
Processing.
Jan 01 00:01:14 5 14 0 USB device vendor 0x13b1, device 0x20
matched.
Jan 01 00:01:15 5 14 0 rum0 at pci0 dev 0 function 0rum0:
MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:2
1:29:de:ff:9e
Jan 01 00:01:15 5 14 0 ether_ifattach: rum0 null if_stop
Jan 01 00:01:15 5 14 0 rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps
11Mbps
Jan 01 00:01:15 5 14 0 rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps
11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mb
ps 54Mbps
Jan 01 00:05:50 5 14 0 rum0: could not multi read MAC
register: NOMEM
Jan 01 00:05:50 5 14 0 USB error 0x02000005 encountered in
io-pkt.
Jan 01 00:05:50 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:05:55 5 14 0 rum0: device timeout
Jan 01 00:05:57 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:01 5 14 0 USB error 0x02000005 encountered in
io-pkt.
Jan 01 00:06:01 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:06 5 14 0 rum0: device timeout
Jan 01 00:06:08 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:12 5 14 0 USB error 0x02000005 encountered in
io-pkt.
Jan 01 00:06:12 5 14 0 rum0: could not transmit buffer: 24
Jan 01 00:06:14 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:17 5 14 0 rum0: device timeout
Jan 01 00:06:19 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Strange considering there is not that much difference between the i.MX31
and i.MX35.
> I'm really not sure what's happening with this one. I've confirmed
> that the driver has been used extensively with an i.MX35 platform
> without any problems.
>
> Is devb-umass always running? How about slaying that and trying
again?
>
>
_______________________________________________
General
http://community.qnx.com/sf/go/post16842
|
|
|
|
|
|
|
RE: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/19/2008 1:51 PM
post16915
|
RE: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hmmm... As soon as I see a single NOMEM then that's an error condition
that's problematic. All the errors are indicative of something being
wrong at the USB layer.
02000005 = URB status 0200 => CMP_ERR and USB Status 0005 = CRC_ERR +
STALL
0a000000 = URB status 0a00 = CMP_ERR + ABORTED (aborted because of the
initial CMP_ERR).
You can see where this message is generated in usb_handle_error in
usb_conv_qnx.c in
http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib/l
ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=583&system=exsy1001
&view=markup
How about a "pidin -p io-usb mem" to see what io-usb is doing with
memory?
R.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Tuesday, November 18, 2008 6:17 PM
To: general-networking
Subject: Re: RE: RE: Problems getting USB wireless working (Ralink
RT2501USB chipset)
Okay I tried changing startup so devb-umass is not started and now after
running "ifconfig rum0 up", slog reads a little differently (and I can
see the LED on the adapter flash a couple times during):
Time Sev Major Minor Args
Jan 01 00:01:14 5 14 0 tcpip starting
Jan 01 00:01:14 3 14 0 Unable to attach to pci server: No such
file or directory
Jan 01 00:01:14 3 14 0 Using pseudo random generator. See
"random" option
Jan 01 00:01:14 5 14 0 initializing IPsec... done
Jan 01 00:01:14 5 14 0 IPsec: Initialized Security Association
Processing.
Jan 01 00:01:14 5 14 0 USB device vendor 0x13b1, device 0x20
matched.
Jan 01 00:01:15 5 14 0 rum0 at pci0 dev 0 function 0rum0:
MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:2
1:29:de:ff:9e
Jan 01 00:01:15 5 14 0 ether_ifattach: rum0 null if_stop
Jan 01 00:01:15 5 14 0 rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps
11Mbps
Jan 01 00:01:15 5 14 0 rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps
11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mb
ps 54Mbps
Jan 01 00:05:50 5 14 0 rum0: could not multi read MAC
register: NOMEM
Jan 01 00:05:50 5 14 0 USB error 0x02000005 encountered in
io-pkt.
Jan 01 00:05:50 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:05:55 5 14 0 rum0: device timeout
Jan 01 00:05:57 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:01 5 14 0 USB error 0x02000005 encountered in
io-pkt.
Jan 01 00:06:01 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:06 5 14 0 rum0: device timeout
Jan 01 00:06:08 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:12 5 14 0 USB error 0x02000005 encountered in
io-pkt.
Jan 01 00:06:12 5 14 0 rum0: could not transmit buffer: 24
Jan 01 00:06:14 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Jan 01 00:06:17 5 14 0 rum0: device timeout
Jan 01 00:06:19 5 14 0 USB error 0x0a000000 encountered in
io-pkt.
Strange considering there is not that much difference between the i.MX31
and i.MX35.
> I'm really not sure what's happening with this one. I've confirmed
> that the driver has been used extensively with an i.MX35 platform
> without any problems.
>
> Is devb-umass always running? How about slaying that and trying
again?
>
>
_______________________________________________
General
http://community.qnx.com/sf/go/post16842
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/19/2008 5:58 PM
post16939
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Thanks for not giving up on the problem yet!
Below is the output after I ran "ifconfig rum0 up" on the device (it seemed to increase in memory usage a little after
doing so).
# pidin -p io-usb mem
pid tid name prio STATE code data stack
7 1 proc/boot/io-usb 10r SIGWAITINFO 92K 364K 8192(132K)*
7 2 proc/boot/io-usb 21r RECEIVE 92K 364K 4096(20K)
7 3 proc/boot/io-usb 21r RECEIVE 92K 364K 4096(20K)
7 4 proc/boot/io-usb 21r RECEIVE 92K 364K 4096(20K)
7 5 proc/boot/io-usb 10r NANOSLEEP 92K 364K 4096(20K)
7 6 proc/boot/io-usb 21r RECEIVE 92K 364K 4096(20K)
7 7 proc/boot/io-usb 21r RECEIVE 92K 364K 4096(20K)
libc.so.3 @ 1000000 448K 12K
devu-ehci-mx31.so @78000000 28K 4096
/dev/mem @28000000 ( 0) 8192
Regards,
Radek.
> Hmmm... As soon as I see a single NOMEM then that's an error condition
> that's problematic. All the errors are indicative of something being
> wrong at the USB layer.
>
> 02000005 = URB status 0200 => CMP_ERR and USB Status 0005 = CRC_ERR +
> STALL
> 0a000000 = URB status 0a00 = CMP_ERR + ABORTED (aborted because of the
> initial CMP_ERR).
>
> You can see where this message is generated in usb_handle_error in
> usb_conv_qnx.c in
> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib/l
> ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=583&system=exsy1001
> &view=markup
>
> How about a "pidin -p io-usb mem" to see what io-usb is doing with
> memory?
>
> R.
>
>
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/20/2008 4:53 PM
post17013
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Nothin obvious there either.
Someone mentioned that there may be a conflict with audio and USB on
that platform. I'm not sure of the details and I would have thought
that it would have shown up with devb-umass, but it's worthwhile not
starting audio (and, just to make sure, anything else that you don't
really need...) and see if that changes the behaviour at all.
I'll have to try and dig up a platform somewhere and try for myself...
R.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 19, 2008 5:59 PM
To: general-networking
Subject: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Thanks for not giving up on the problem yet!
Below is the output after I ran "ifconfig rum0 up" on the device (it
seemed to increase in memory usage a little after doing so).
# pidin -p io-usb mem
pid tid name prio STATE code data
stack
7 1 proc/boot/io-usb 10r SIGWAITINFO 92K 364K
8192(132K)*
7 2 proc/boot/io-usb 21r RECEIVE 92K 364K
4096(20K)
7 3 proc/boot/io-usb 21r RECEIVE 92K 364K
4096(20K)
7 4 proc/boot/io-usb 21r RECEIVE 92K 364K
4096(20K)
7 5 proc/boot/io-usb 10r NANOSLEEP 92K 364K
4096(20K)
7 6 proc/boot/io-usb 21r RECEIVE 92K 364K
4096(20K)
7 7 proc/boot/io-usb 21r RECEIVE 92K 364K
4096(20K)
libc.so.3 @ 1000000 448K 12K
devu-ehci-mx31.so @78000000 28K 4096
/dev/mem @28000000 ( 0) 8192
Regards,
Radek.
> Hmmm... As soon as I see a single NOMEM then that's an error
> condition that's problematic. All the errors are indicative of
> something being wrong at the USB layer.
>
> 02000005 = URB status 0200 => CMP_ERR and USB Status 0005 = CRC_ERR +
> STALL 0a000000 = URB status 0a00 = CMP_ERR + ABORTED (aborted because
> of the initial CMP_ERR).
>
> You can see where this message is generated in usb_handle_error in
> usb_conv_qnx.c in
> http://community.qnx.com/integration/viewcvs/viewcvs.cgi/trunk/sys/lib
> /l
> ibnbdrvr/usb/usb_conv_qnx.c?root=core_networking&rev=583&system=exsy10
> 01
> &view=markup
>
> How about a "pidin -p io-usb mem" to see what io-usb is doing with
> memory?
>
> R.
>
>
_______________________________________________
General
http://community.qnx.com/sf/go/post16939
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/20/2008 5:44 PM
post17018
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Okay I changed the startup script so only the bare minimum is started.
pid Arguments:
---------------------
1 proc/boot/procnto-v6
2 devc-sermx1 -e -F -c66500000 0x43F90000,45 0x43F94000,32 -u5 0x43fb4000,47
3 slogger
4 pipe
5 io-usb -d ehci-mx31 ioport=0x43f88300,irq=35
6 ksh
7 io-pkt-v4-hc -v -d rum
Unfortunately I'm still getting the same USB error.
Radek.
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/20/2008 5:50 PM
post17019
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
That's the initial NOMEM plus subsequent USB errors?
Looks like it's time to go hunting for hardware... I'm running out of
ideas.
R.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Thursday, November 20, 2008 5:44 PM
To: general-networking
Subject: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Okay I changed the startup script so only the bare minimum is started.
pid Arguments:
---------------------
1 proc/boot/procnto-v6
2 devc-sermx1 -e -F -c66500000 0x43F90000,45 0x43F94000,32 -u5
0x43fb4000,47
3 slogger
4 pipe
5 io-usb -d ehci-mx31 ioport=0x43f88300,irq=35
6 ksh
7 io-pkt-v4-hc -v -d rum
Unfortunately I'm still getting the same USB error.
Radek.
_______________________________________________
General
http://community.qnx.com/sf/go/post17018
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/20/2008 5:55 PM
post17020
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Yes that's correct (I should have clarified that...), here's the slog:
Jan 01 00:00:02 5 14 0 initializing IPsec... done
Jan 01 00:00:02 5 14 0 IPsec: Initialized Security Association Processing.javascript:if%
20(validateCreatePost(document.createPost))%20{%20submitForm(document.createPost,%20'submit');%20}%20else%20{%20void(0)%
20}
Jan 01 00:00:02 5 14 0 USB device vendor 0x13b1, device 0x20 matched.
Jan 01 00:00:02 5 14 0 rum0 at pci0 dev 0 function 0rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:
2
1:29:de:ff:9e
Jan 01 00:00:02 5 14 0 ether_ifattach: rum0 null if_stop
Jan 01 00:00:02 5 14 0 rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
Jan 01 00:00:02 5 14 0 rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps
48Mb
ps 54Mbps
Jan 01 00:00:12 5 14 0 rum0: could not multi read MAC register: NOMEM
Jan 01 00:00:12 5 14 0 USB error 0x02000005 encountered in io-pkt.
Jan 01 00:00:12 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:00:16 5 14 0 rum0: device timeout
Jan 01 00:00:19 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:00:26 5 14 0 USB error 0x0a000000 encountered in io-pkt.
Jan 01 00:00:27 5 14 0 rum0: device timeout
|
|
|
|
|
|
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/25/2008 10:10 PM
post17324
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hi Robert,
Just giving you a quick update. Since the i.MX31 PDK BSP is now available, I have downloaded the BSP and tried using
the wireless adapter on the PDK board. To my surprise the wireless adapter works fine on the PDK. I thought that maybe
libstartup or the USB driver itself may be different between the two, however they are identical.
Still no luck on the ADS board however.
Cheers,
Radek.
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/26/2008 11:00 AM
post17387
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hi Radek:
Well THAT'S good news. I still don't have any idea why it won't
work on the ADS board... It'll probably have a bit of a lower priority
on my front now that you've shown it to be working on a similar
platform.
Oh... I just had a thought. One thing about some of these platforms is
that the USB ports don't provide enough power to drive the WiFi chips.
Can you plug the dongle into a powered USB hub and see if that changes
things at all?
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Tuesday, November 25, 2008 10:11 PM
To: general-networking
Subject: Re: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Hi Robert,
Just giving you a quick update. Since the i.MX31 PDK BSP is now
available, I have downloaded the BSP and tried using the wireless
adapter on the PDK board. To my surprise the wireless adapter works
fine on the PDK. I thought that maybe libstartup or the USB driver
itself may be different between the two, however they are identical.
Still no luck on the ADS board however.
Cheers,
Radek.
_______________________________________________
General
http://community.qnx.com/sf/go/post17324
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/26/2008 4:38 PM
post17426
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hi Robert,
And we have success! - you were spot on the money there, the ADS board doesn't seem to have enough power on the USB port
to run the Wifi adapter.
Thanks alot for your help.
> Hi Radek:
> Well THAT'S good news. I still don't have any idea why it won't
> work on the ADS board... It'll probably have a bit of a lower priority
> on my front now that you've shown it to be working on a similar
> platform.
>
> Oh... I just had a thought. One thing about some of these platforms is
> that the USB ports don't provide enough power to drive the WiFi chips.
> Can you plug the dongle into a powered USB hub and see if that changes
> things at all?
>
> Robert.
>
|
|
|
|
|
|
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/26/2008 4:40 PM
post17427
|
RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
I should have thought of that one earlier. We hit it once before. At
least now it's indelibly etched in my mind :->>
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 26, 2008 4:39 PM
To: general-networking
Subject: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Hi Robert,
And we have success! - you were spot on the money there, the ADS board
doesn't seem to have enough power on the USB port to run the Wifi
adapter.
Thanks alot for your help.
> Hi Radek:
> Well THAT'S good news. I still don't have any idea why it won't
work
> on the ADS board... It'll probably have a bit of a lower priority on
> my front now that you've shown it to be working on a similar platform.
>
> Oh... I just had a thought. One thing about some of these platforms
> is that the USB ports don't provide enough power to drive the WiFi
chips.
> Can you plug the dongle into a powered USB hub and see if that changes
> things at all?
>
> Robert.
>
_______________________________________________
General
http://community.qnx.com/sf/go/post17426
|
|
|
|
|
|
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/26/2008 4:47 PM
post17429
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
... and that's a lesson learnt for me too. It didn't cross my mind that it would not have sufficient power for a
wireless adapter - a portable harddrive or multiple devices yes, but not for a single adapter so thanks.
Now before I go chasing a wild goose with one of my intended uses for the wireless adapter, is it possible to do
ethernet-based debugging over wireless (i.e. qconn)? Reason being once we have our target hardware we will no longer
have the luxury of an ethernet connection.
Cheers,
Radek.
> I should have thought of that one earlier. We hit it once before. At
> least now it's indelibly etched in my mind :->>
>
> Robert.
>
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/26/2008 4:52 PM
post17430
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
That one had us scratching our heads for a while too. I'm actually
surprised that a hard drive works for you (as opposed to a flash based
drive...).
In any case, you should have no problems at all debugging over wireless.
From an app point of view, it's all Ethernet / IP at the end of the day
so once you get connected, the rest is good. Our QNET protocol works
over WiFi links as well.
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 26, 2008 4:47 PM
To: general-networking
Subject: Re: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
... and that's a lesson learnt for me too. It didn't cross my mind that
it would not have sufficient power for a wireless adapter - a portable
harddrive or multiple devices yes, but not for a single adapter so
thanks.
Now before I go chasing a wild goose with one of my intended uses for
the wireless adapter, is it possible to do ethernet-based debugging over
wireless (i.e. qconn)? Reason being once we have our target hardware we
will no longer have the luxury of an ethernet connection.
Cheers,
Radek.
> I should have thought of that one earlier. We hit it once before. At
> least now it's indelibly etched in my mind :->>
>
> Robert.
>
_______________________________________________
General
http://community.qnx.com/sf/go/post17429
|
|
|
|
|
|
|
Re: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
11/26/2008 5:01 PM
post17432
|
Re: RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
That's the answer I was hoping to hear, at least we will have an affordable debugging solution on our target hardware.
As for the hard drive, I haven't tried it yet, it was more a comment that I would expect a portable hdd to require a
powered hub and hence I would click to try powering it to fix the problem, but not a wireless adapter. It is on the
list of things to try though so if it does work I will let you know.
> That one had us scratching our heads for a while too. I'm actually
> surprised that a hard drive works for you (as opposed to a flash based
> drive...).
>
> In any case, you should have no problems at all debugging over wireless.
> From an app point of view, it's all Ethernet / IP at the end of the day
> so once you get connected, the rest is good. Our QNET protocol works
> over WiFi links as well.
>
> Robert.
>
|
|
|
|
|
|
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/08/2009 4:20 PM
post19690
|
Re: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
I'm having similar problems get rum0 to work on an x86 PC. I've followed this thread as best as I could (even so far as
trying the wireless dongle in a powered USB hub).
When I power up the target, I get one of the following behaviors:
1 The USB device doesn't seem to be detected at all.
2 The USB device is detected but I get a boat load of the "" messages displayed by slogger.
3 The rum0 interface appears to come up (ifconfig shows it with a DHCP address) but I can't connect to the target via
the wireless interface.
Sometimes if the device isn't detected during power up, if I remove it and insert it in a different USB port it will be
detected (at least to the point where ifconfig shows the rum0 interface).
Thanks,
Gordon Molek
Zebra Technologies Corporation
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/08/2009 4:22 PM
post19691
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Hi Gordon:
This is really sounding like a problem with the USB side of
things. What type of interface is it (EHCI, UHCI, OHCI)? Does the
dongle work OK on a different x86 platform?
When you say "" messages displayed, does it mean exactly that (empty
messages or "" messages)?
Robert.
-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Thursday, January 08, 2009 4:20 PM
To: general-networking
Subject: Re: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
I'm having similar problems get rum0 to work on an x86 PC. I've
followed this thread as best as I could (even so far as trying the
wireless dongle in a powered USB hub).
When I power up the target, I get one of the following behaviors:
1 The USB device doesn't seem to be detected at all.
2 The USB device is detected but I get a boat load of the "" messages
displayed by slogger.
3 The rum0 interface appears to come up (ifconfig shows it with a DHCP
address) but I can't connect to the target via the wireless interface.
Sometimes if the device isn't detected during power up, if I remove it
and insert it in a different USB port it will be detected (at least to
the point where ifconfig shows the rum0 interface).
Thanks,
Gordon Molek
Zebra Technologies Corporation
_______________________________________________
General
http://community.qnx.com/sf/go/post19690
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/08/2009 4:43 PM
post19693
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Robert,
Sorry, that was a placeholder and then I forgot to go dig up the error
message and fill it in before hitting "Submit."
The error I usually get is the "rum0: could not multi read MAC register:
NOMEM".
The dongle was working on this particular target with io-net as the base
networking with a separate start-up of io-pkt. It seems we started
getting into trouble when Mike Cranston created an image to run io-pkt
"natively."
How do I determine EHCI/UHCI/OHCI? I'm not particularly knowledgeable
of USB.
Thanks,
Gordon
-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: Thursday, January 08, 2009 3:23 PM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Hi Gordon:
This is really sounding like a problem with the USB side of
things. What type of interface is it (EHCI, UHCI, OHCI)? Does the
dongle work OK on a different x86 platform?
When you say "" messages displayed, does it mean exactly that (empty
messages or "" messages)?
Robert.
-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Thursday, January 08, 2009 4:20 PM
To: general-networking
Subject: Re: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
I'm having similar problems get rum0 to work on an x86 PC. I've
followed this thread as best as I could (even so far as trying the
wireless dongle in a powered USB hub).
When I power up the target, I get one of the following behaviors:
1 The USB device doesn't seem to be detected at all.
2 The USB device is detected but I get a boat load of the "" messages
displayed by slogger.
3 The rum0 interface appears to come up (ifconfig shows it with a DHCP
address) but I can't connect to the target via the wireless interface.
Sometimes if the device isn't detected during power up, if I remove it
and insert it in a different USB port it will be detected (at least to
the point where ifconfig shows the rum0 interface).
Thanks,
Gordon Molek
Zebra Technologies Corporation
_______________________________________________
General
http://community.qnx.com/sf/go/post19690
_______________________________________________
General
http://community.qnx.com/sf/go/post19691
- 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.
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/08/2009 4:50 PM
post19695
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
Weirder and weirder. So with io-net up and running and (presumably)
connected to a PCI NIC, you could start up io-pkt separately and
everything ran OK. But take io-net out of the picture and things no
longer work? That's very odd.
What does "created an image" mean? Did it include everything from
before but just no longer starts io-net or were major alterations made
to the contents of the image?
Can you try other USB devices (e.g. a USB flash drive) and see if they
work?
Have you also removed the NIC that io-net was using from the machine?
How has the interrupt allocation been changed by the removal of io-net?
(pidin irq will tell you which sub-systems are using which interrupts).
Were any BIOS changes made after the new image was used?
If the same hardware worked with io-net in the picture, then I won't
worry about which flavour of usb is being used (although the USB utility
should let you know what type of bus a device is plugged into if the
device is detected).
Lots of questions... :>
Robert.
-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Thursday, January 08, 2009 4:43 PM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Robert,
Sorry, that was a placeholder and then I forgot to go dig up the error
message and fill it in before hitting "Submit."
The error I usually get is the "rum0: could not multi read MAC register:
NOMEM".
The dongle was working on this particular target with io-net as the base
networking with a separate start-up of io-pkt. It seems we started
getting into trouble when Mike Cranston created an image to run io-pkt
"natively."
How do I determine EHCI/UHCI/OHCI? I'm not particularly knowledgeable
of USB.
Thanks,
Gordon
-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: Thursday, January 08, 2009 3:23 PM
To: general-networking
Subject: RE: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
Hi Gordon:
This is really sounding like a problem with the USB side of
things. What type of interface is it (EHCI, UHCI, OHCI)? Does the
dongle work OK on a different x86 platform?
When you say "" messages displayed, does it mean exactly that (empty
messages or "" messages)?
Robert.
-----Original Message-----
From: Gordon Molek [mailto:community-noreply@qnx.com]
Sent: Thursday, January 08, 2009 4:20 PM
To: general-networking
Subject: Re: RE: Problems getting USB wireless working (Ralink RT2501USB
chipset)
I'm having similar problems get rum0 to work on an x86 PC. I've
followed this thread as best as I could (even so far as trying the
wireless dongle in a powered USB hub).
When I power up the target, I get one of the following behaviors:
1 The USB device doesn't seem to be detected at all.
2 The USB device is detected but I get a boat load of the "" messages
displayed by slogger.
3 The rum0 interface appears to come up (ifconfig shows it with a DHCP
address) but I can't connect to the target via the wireless interface.
Sometimes if the device isn't detected during power up, if I remove it
and insert it in a different USB port it will be detected (at least to
the point where ifconfig shows the rum0 interface).
Thanks,
Gordon Molek
Zebra Technologies Corporation
_______________________________________________
General
http://community.qnx.com/sf/go/post19690
_______________________________________________
General
http://community.qnx.com/sf/go/post19691
- 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...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/09/2009 9:04 AM
post19724
|
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 : 0x03 (HID)
Subclass : 0x01 (Boot interface)
Protocol : 0x02 (Mouse)
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 8
Endpoint : 1
Attributes : Interrupt/IN
Max Packet Size: 5
Interval : 10 ms
USB 2 (UHCI) v1.10, v1.01 DDK, v1.01 HCD
Control, Interrupt, Bulk(SG), Isoch(Stream), Low speed, Full speed
USB 3 (UHCI) v1.10, v1.01 DDK, v1.01 HCD
Control, Interrupt, Bulk(SG), Isoch(Stream), Low speed, Full speed
USB 4 (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 : 4
Upstream Device Address : 0
Upstream Port : 7
Upstream Port Speed : High
Vendor : 0x13b1 (Cisco-Linksys)
Product : 0x0020 (Compact Wireless-G USB Adapter)
Device Release : r0.01
USB Spec Release : v2.00
Serial Number : N/A
Class : 0x00 (Independent per interface)
Max PacketSize0 : 64
Languages : 0x0409 (English)
Current Frame : 5313 (1024 bytes)
Configurations : 1
Configuration : 1
Attributes : 0x80 (Bus-powered)
Max Power : 300 mA
Interfaces : 1
Interface : 0 / 0
Class : 0xff (Vendor-specific)
Subclass ...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/09/2009 3:16 PM
post19788
|
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 : 0x03 (HID)
Subclass : 0x01 (Boot interface)
Protocol : 0x02 (Mouse)
Endpoints : Control + 1
Endpoint : 0
Attributes : Control
Max Packet Size: 8
Endpoint : 1
Attributes : Interrupt/IN
Max Packet Size: 5
Interval : 10 ms
USB 2 (UHCI) v1.10, v1.01 DDK, v1.01 HCD
Control, Interrupt, Bulk(SG), Isoch(Stream), Low speed, Full speed
USB 3 (UHCI) v1.10, v1.01 DDK, v1.01 HCD
Control, Interrupt, Bulk(SG), Isoch(Stream), Low speed, Full speed
USB 4 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
Control, Interrupt, Bulk(SG), Isoch(Stream), Full speed, High speed
Device Address : 1
Upstream...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/12/2009 10:59 AM
post19853
|
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 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 ...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/12/2009 11:04 AM
post19856
|
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 (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...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/12/2009 11:56 AM
post19879
|
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), 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...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/12/2009 12:01 PM
post19880
|
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 -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),...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/12/2009 3:10 PM
post19902
|
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 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...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/12/2009 3:12 PM
post19903
|
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 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...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/15/2009 8:55 AM
post20107
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
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...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/15/2009 10:02 AM
post20120
|
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.
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/15/2009 10:39 AM
post20129
|
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
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/15/2009 1:27 PM
post20155
|
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
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/15/2009 1:39 PM
post20156
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
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
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/15/2009 1:47 PM
post20159
|
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, "/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...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/15/2009 2:03 PM
post20160
|
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, 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,...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/16/2009 7:31 AM
post20193
|
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, "/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,...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/16/2009 12:36 PM
post20230
|
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, 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,...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/16/2009 1:41 PM
post20242
|
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 (/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,...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/16/2009 1:49 PM
post20245
|
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 - -
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...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/16/2009 3:04 PM
post20252
|
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 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 - ...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/16/2009 4:07 PM
post20267
|
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 [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...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/19/2009 8:36 AM
post20295
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
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...
View Full Message
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/19/2009 9:17 AM
post20298
|
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
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/19/2009 1:10 PM
post20329
|
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.
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/19/2009 1:22 PM
post20331
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
> 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
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/19/2009 1:29 PM
post20333
|
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
|
|
|
|
|
|
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
|
|
01/19/2009 1:54 PM
post20341
|
RE: RE: Problems getting USB wireless working (Ralink RT2501USB chipset)
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
|
|
|
|
|
|