Using 6.3 PE on an X86
I have npm-qnet.so linked to npm-qnet-compat.co. I have also edited my
startup files so that I am loading io-net as follows:
io-net -ptcpip -pqnet -di82544
When I do this TCP/Ip works fine but QNET does not.
If I don’t load the -pqnet and subsequently mount -Tio-net npm-qnet.so
then all is fine.
Is there a reason I can’t load everything on the one command line?
Does the problem goes away if you do this ?
io-net -d i82544 -p tcpip -p qnet
-xtang
Bill Caroselli <qtps@earthlink.net> wrote in message
news:ce39f9$lfi$1@inn.qnx.com…
Using 6.3 PE on an X86
I have npm-qnet.so linked to npm-qnet-compat.co. I have also edited my
startup files so that I am loading io-net as follows:
io-net -ptcpip -pqnet -di82544When I do this TCP/Ip works fine but QNET does not.
If I don’t load the -pqnet and subsequently mount -Tio-net npm-qnet.so
then all is fine.Is there a reason I can’t load everything on the one command line?
Xiaodan Tang <xtang@qnx.com> wrote:
XT > Does the problem goes away if you do this ?
XT > io-net -d i82544 -p tcpip -p qnet
XT > -xtang
No, it didn’t help.
Do I need some kind of waitfor before this line?
The hardware device and TCP do work fine.
It’s just QNET that isn’t working.
Bill Caroselli <qtps@earthlink.net> wrote in message
news:ce5hfu$efb$1@inn.qnx.com…
Xiaodan Tang <> xtang@qnx.com> > wrote:
XT > Does the problem goes away if you do this ?XT > io-net -d i82544 -p tcpip -p qnet
XT > -xtang
No, it didn’t help.
Do I need some kind of waitfor before this line?
The hardware device and TCP do work fine.
It’s just QNET that isn’t working.
Hm, and this is 6.3 you are saying.
When it is not working, what happened?
If it’s 3), does it works if you force a “ls /net/someoneremote” ?
-xtang
Xiaodan Tang <xtang@qnx.com> wrote:
XT > Bill Caroselli <qtps@earthlink.net> wrote in message
XT > news:ce5hfu$efb$1@inn.qnx.com…
Xiaodan Tang <> xtang@qnx.com> > wrote:
XT > Does the problem goes away if you do this ?XT > io-net -d i82544 -p tcpip -p qnet
XT > -xtang
No, it didn’t help.
Do I need some kind of waitfor before this line?
The hardware device and TCP do work fine.
It’s just QNET that isn’t working.
XT > Hm, and this is 6.3 you are saying.
XT > When it is not working, what happened?
XT > 1) Is there no /net?
XT > 2) Is there a /net but nothing in it (not even yourself)?
XT > 3) Is there a /net, and a /net/myself but no one else in it?
XT > If it’s 3), does it works if you force a “ls /net/someoneremote” ?
XT > -xtang
OK, this is weird. First your answer is #3. “ls /net” shows just me.
This system is called “dell.ts”. The other two hosts are called “lil.ts”
and “test1.ts”. Lil.ts is running 6.2.1 PE, the others are running 6.3.
Typing “ls /net/lil” or “ls /net/test1” finds nothing. I get No Route
To Host. But typing “ls /net/lil.ts” or “ls /net/test1.ts” puts them
into the /net directory.
All three systems have the domain .ts. Isn’t this a bug?
Bill Caroselli <qtps@earthlink.net> wrote in message
news:ce86sh$fuj$2@inn.qnx.com…
Xiaodan Tang <> xtang@qnx.com> > wrote:
XT > 1) Is there no /net?
XT > 2) Is there a /net but nothing in it (not even yourself)?
XT > 3) Is there a /net, and a /net/myself but no one else in it?XT > If it’s 3), does it works if you force a “ls /net/someoneremote” ?
XT > -xtang
OK, this is weird. First your answer is #3. “ls /net” shows just me.
Cool. I think this problem is because the driver isn’t ready when QNET
try to advertise itself (and finding other nodes). You can try this.
io-net -d i82544 -p tcpip -p qnet trydelay=5
This tells QNET to delay 5 seconds before advertise itself.
This system is called “dell.ts”. The other two hosts are called “lil.ts”
and “test1.ts”. Lil.ts is running 6.2.1 PE, the others are running 6.3.
Typing “ls /net/lil” or “ls /net/test1” finds nothing. I get No Route
To Host. But typing “ls /net/lil.ts” or “ls /net/test1.ts” puts them
into the /net directory.All three systems have the domain .ts. Isn’t this a bug?
Sounds like the domain of yourself is not “ts”, You can try a
getconf _CS_DOMAIN to check out. (may be an extra dot
or something)
-xtang
Xiaodan Tang <xtang@qnx.com> wrote:
XT > Cool. I think this problem is because the driver isn’t ready when QNET
XT > try to advertise itself (and finding other nodes). You can try this.
XT > io-net -d i82544 -p tcpip -p qnet trydelay=5
XT > This tells QNET to delay 5 seconds before advertise itself.
This did not help. Do I need quotes anywhere?
XT > Sounds like the domain of yourself is not “ts”, You can try a
XT > getconf _CS_DOMAIN to check out. (may be an extra dot
XT > or something)
Good call here. This host was set to
getconf -s _CS_DOMAIN .ts
so there was an extra dot.
Bill Caroselli <qtps@earthlink.net> wrote:
BC > Xiaodan Tang <xtang@qnx.com> wrote:
BC > XT > Cool. I think this problem is because the driver isn’t ready when QNET
BC > XT > try to advertise itself (and finding other nodes). You can try this.
BC > XT > io-net -d i82544 -p tcpip -p qnet trydelay=5
BC > XT > This tells QNET to delay 5 seconds before advertise itself.
BC > This did not help. Do I need quotes anywhere?
BTW, adding the trydelay argument caused qnet not to work at all.
I.E. I couldn’t even access the other hosts as /net/test1.
Bill Caroselli <qtps@earthlink.net> wrote in message
news:ce8fus$n6q$1@inn.qnx.com…
Bill Caroselli <> qtps@earthlink.net> > wrote:
BC > Xiaodan Tang <> xtang@qnx.com> > wrote:BC > XT > Cool. I think this problem is because the driver isn’t ready
when QNET
BC > XT > try to advertise itself (and finding other nodes). You can try
this.BC > XT > io-net -d i82544 -p tcpip -p qnet trydelay=5
BC > XT > This tells QNET to delay 5 seconds before advertise itself.
BC > This did not help. Do I need quotes anywhere?
BTW, adding the trydelay argument caused qnet not to work at all.
I.E. I couldn’t even access the other hosts as /net/test1.
No you don’t need quotes anywhere, does sloginfo said anything?
I will try this option later sometime…
-xtang
Xiaodan Tang <xtang@qnx.com> wrote:
XT > Bill Caroselli <qtps@earthlink.net> wrote in message
XT > news:ce8fus$n6q$1@inn.qnx.com…
Bill Caroselli <> qtps@earthlink.net> > wrote:
BC > Xiaodan Tang <> xtang@qnx.com> > wrote:BC > XT > Cool. I think this problem is because the driver isn’t ready
XT > when QNET
BC > XT > try to advertise itself (and finding other nodes). You can try
XT > this.BC > XT > io-net -d i82544 -p tcpip -p qnet trydelay=5
BC > XT > This tells QNET to delay 5 seconds before advertise itself.
BC > This did not help. Do I need quotes anywhere?
BTW, adding the trydelay argument caused qnet not to work at all.
I.E. I couldn’t even access the other hosts as /net/test1.
XT > No you don’t need quotes anywhere, does sloginfo said anything?
XT > I will try this option later sometime…
XT > -xtang
Time Sev Major Minor Args
Jul 29 04:46:25 3 17 0 Range check failed (IO) - Dev 244b - Vend 8086 - Class 10180 - Addr ffa0 - Size 10
Jul 29 04:46:25 2 19 0 eide_identify_devices: Intel 82801BA vid 8086, did 244b, class 10180 rev 4, busno 0, dfunc f9
Jul 29 04:46:25 2 19 0 eide_identify_devices: cmd_addr 1f0, cntl_addr 3f4, irq e, chnl 0, udma 5, mdma 2, sdma 0, pio 4
Jul 29 04:46:25 2 19 0 eide_display_devices: IC35L080AVVA07-0 tid 0, cable 80, max udma 5, cur udma 5, max mdma 0, cur mdma 2, max sdma -1, cur sdma -1, pio 4, mblk 16
Jul 29 04:46:25 2 19 0 eide_parse_identify: IDENTIFY DRIVE CMD cksum failure
Jul 29 04:46:25 2 19 0 eide_display_devices: WDC WD2500JB-00E tid 1, cable 80, max udma 5, cur udma 5, max mdma 0, cur mdma 2, max sdma -1, cur sdma -1, pio 4, mblk 16
Jul 29 04:46:25 2 19 0 eide_init_devices: IC35L080AVVA07-0 path 0, tid 0, udma 5, mdma 2, sdma -1, pio 4, mblk 16
Jul 29 04:46:25 2 19 0 eide_init_devices: WDC WD2500JB-00E path 0, tid 1, udma 5, mdma 2, sdma -1, pio 4, mblk 16
Jul 29 04:46:25 2 19 0 eide_identify_devices: Intel 82801BA vid 8086, did 244b, class 10180 rev 4, busno 0, dfunc f9
Jul 29 04:46:25 2 19 0 eide_identify_devices: cmd_addr 170, cntl_addr 374, irq f, chnl 1, udma 5, mdma 2, sdma 0, pio 4
Jul 29 04:46:25 2 19 0 eide_display_devices: HL-DT-ST GCE-848 tid 0, cable 40, max udma 2, cur udma 2, max mdma 0, cur mdma 2, max sdma -1, cur sdma -1, pio 4, mblk 0
Jul 29 04:46:25 2 19 0 eide_init_devices: HL-DT-ST GCE-848 path 0, tid 0, udma 2, mdma 2, sdma -1, pio 4, mblk 0
Jul 29 04:46:30 5 6 200 Installing /dev/par port 378
Jul 29 04:46:30 5 14 0 tcpip starting
Jul 29 04:46:30 3 14 0 Using pseudo random generator. See “random” option