Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Unable to mount io-net: (12 Items)
   
Unable to mount io-net  
In qnx6.3.2, i tried to use qnet with another qnx6.2.1:
$mount -T io-net /lib/dll/npm-qnet-compat.so

But has the following err:
mount: Can't mount / (type io-net)
mount: Possible reason: Resource temporarily unavailable.

I tried to slay io-net and then tried again, but still failed. Look forward to ur solutions. thank u
RE: Unable to mount io-net  
Are you only running one version of qnet?  You can't run both qnet-compat
and qnet-l4-lite at the same time.  If you are, only running one version of
qnet, what's the output from

pidin -pio-net mem 

?

	Robert.



-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Monday, May 19, 2008 12:15 PM
To: drivers-networking
Subject: Unable to mount io-net

In qnx6.3.2, i tried to use qnet with another qnx6.2.1:
$mount -T io-net /lib/dll/npm-qnet-compat.so

But has the following err:
mount: Can't mount / (type io-net)
mount: Possible reason: Resource temporarily unavailable.

I tried to slay io-net and then tried again, but still failed. Look forward
to ur solutions. thank u

_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post8242
Re: RE: Unable to mount io-net  
> Are you only running one version of qnet?  You can't run both qnet-compat
> and qnet-l4-lite at the same time.  If you are, only running one version of
> qnet, what's the output from
> 
> pidin -pio-net mem 
> 
> ?
> 
> 	Robert.
> 
> 
> 
> -----Original Message-----
> From: Eric Dong [mailto:eric.dongxx@gmail.com] 
> Sent: Monday, May 19, 2008 12:15 PM
> To: drivers-networking
> Subject: Unable to mount io-net
> 
> In qnx6.3.2, i tried to use qnet with another qnx6.2.1:
> $mount -T io-net /lib/dll/npm-qnet-compat.so
> 
> But has the following err:
> mount: Can't mount / (type io-net)
> mount: Possible reason: Resource temporarily unavailable.
> 
> I tried to slay io-net and then tried again, but still failed. Look forward
> to ur solutions. thank u
> 
> _______________________________________________
> Networking Drivers
> http://community.qnx.com/sf/go/post8242


You are right. Under mem column, there was a "npm-qnet.so", which should be a sign that the elder version of qnet is 
running. 
But how can i stop using it? i tried "slay io-net", but no effects.  thank u.
RE: RE: Unable to mount io-net  
Hi Eric:
	If you slay io-net and then do a pidin, is io-net no longer running?
Perhaps the best thing to do is to provide the following information

pidin -p io-net mem

slay io-net

pidin -p io-net mem

/sbin/io-net

mount -T io-net /lib/dll/npm-qnet-compat.so

pidin -pio-net mem


	Robert.

-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Tuesday, May 20, 2008 8:33 AM
To: drivers-networking
Subject: Re: RE: Unable to mount io-net

> Are you only running one version of qnet?  You can't run both qnet-compat
> and qnet-l4-lite at the same time.  If you are, only running one version
of
> qnet, what's the output from
> 
> pidin -pio-net mem 
> 
> ?
> 
> 	Robert.
> 
> 
> 
> -----Original Message-----
> From: Eric Dong [mailto:eric.dongxx@gmail.com] 
> Sent: Monday, May 19, 2008 12:15 PM
> To: drivers-networking
> Subject: Unable to mount io-net
> 
> In qnx6.3.2, i tried to use qnet with another qnx6.2.1:
> $mount -T io-net /lib/dll/npm-qnet-compat.so
> 
> But has the following err:
> mount: Can't mount / (type io-net)
> mount: Possible reason: Resource temporarily unavailable.
> 
> I tried to slay io-net and then tried again, but still failed. Look
forward
> to ur solutions. thank u
> 
> _______________________________________________
> Networking Drivers
> http://community.qnx.com/sf/go/post8242


You are right. Under mem column, there was a "npm-qnet.so", which should be
a sign that the elder version of qnet is running. 
But how can i stop using it? i tried "slay io-net", but no effects.  thank
u.

_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post8252
RE: RE: Unable to mount io-net  
Sometimes io-net will get wedged (usually
due to a malfunctioning driver) and slay
will not terminate it.  In this situation
you can either:

# kill -9 <pid>

Or

# slay -s SIGKILL io-net

--
aboyd

-----Original Message-----
From: Robert Craig 
Sent: Tuesday, May 20, 2008 10:51 AM
To: drivers-networking
Subject: RE: RE: Unable to mount io-net

Hi Eric:
	If you slay io-net and then do a pidin, is io-net no longer running?
Perhaps the best thing to do is to provide the following information

pidin -p io-net mem

slay io-net

pidin -p io-net mem

/sbin/io-net

mount -T io-net /lib/dll/npm-qnet-compat.so

pidin -pio-net mem


	Robert.

-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Tuesday, May 20, 2008 8:33 AM
To: drivers-networking
Subject: Re: RE: Unable to mount io-net

> Are you only running one version of qnet?  You can't run both qnet-compat
> and qnet-l4-lite at the same time.  If you are, only running one version
of
> qnet, what's the output from
> 
> pidin -pio-net mem 
> 
> ?
> 
> 	Robert.
> 
> 
> 
> -----Original Message-----
> From: Eric Dong [mailto:eric.dongxx@gmail.com] 
> Sent: Monday, May 19, 2008 12:15 PM
> To: drivers-networking
> Subject: Unable to mount io-net
> 
> In qnx6.3.2, i tried to use qnet with another qnx6.2.1:
> $mount -T io-net /lib/dll/npm-qnet-compat.so
> 
> But has the following err:
> mount: Can't mount / (type io-net)
> mount: Possible reason: Resource temporarily unavailable.
> 
> I tried to slay io-net and then tried again, but still failed. Look
forward
> to ur solutions. thank u
> 
> _______________________________________________
> Networking Drivers
> http://community.qnx.com/sf/go/post8242


You are right. Under mem column, there was a "npm-qnet.so", which should be
a sign that the elder version of qnet is running. 
But how can i stop using it? i tried "slay io-net", but no effects.  thank
u.

_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post8252

_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post8270
Re: RE: RE: Unable to mount io-net  
Thanks very much.

Now i really slayed io-net, since the output of "pidin -pio-net mem" had nothing (no elder version of qnet is running). 
Then i tried to mount qnet-compat, still the same error. What r the possible reasons??
RE: RE: RE: Unable to mount io-net  
Hm.  Sometimes the command line arrangement
of mount can be a little user-unfriendly  :-(

After making sure that there are really no
other io-net instances running, have you
simply tried:

   #  io-net -d i82544 -p qnet-compat

--
aboyd

-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Wednesday, May 21, 2008 1:38 AM
To: drivers-networking
Subject: Re: RE: RE: Unable to mount io-net

Thanks very much.

Now i really slayed io-net, since the output of "pidin -pio-net mem" had
nothing (no elder version of qnet is running). Then i tried to mount
qnet-compat, still the same error. What r the possible reasons??

_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post8291
RE: RE: RE: Unable to mount io-net  
Hi Eric:
	What happens if you try

io-net -p/lib/dll/npm-qnet-compat.so

Can you also post the output from sloginfo and pidin so that we can see what
else is running?

	Thanks

		Robert.

-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Wednesday, May 21, 2008 1:38 AM
To: drivers-networking
Subject: Re: RE: RE: Unable to mount io-net

Thanks very much.

Now i really slayed io-net, since the output of "pidin -pio-net mem" had
nothing (no elder version of qnet is running). Then i tried to mount
qnet-compat, still the same error. What r the possible reasons??

_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post8291
Re: RE: RE: RE: Unable to mount io-net  
Thanks.
Output of pidin:
     pid tid name               prio STATE       Blocked         
       1   1 procnto              0f READY                       
       1   2 procnto             10r RECEIVE     1               
       1   3 procnto             10r RUNNING                     
       1   4 procnto             10r RECEIVE     1               
       1   5 procnto             10r RECEIVE     1               
       1   6 procnto             10r RECEIVE     1               
       1   7 procnto             10r RECEIVE     1               
       1   8 procnto             10r RECEIVE     1               
       1   9 procnto             10r RECEIVE     1               
       1  10 procnto             10r RECEIVE     1               
       1  11 procnto             10r RECEIVE     1               
       2   1 sbin/tinit          10o REPLY       1               
    4099   1 proc/boot/pci-bios  12o RECEIVE     1               
    4100   1 proc/boot/slogger   10o RECEIVE     1               
    4101   1 proc/boot/io-usb    10o SIGWAITINFO                 
    4101   2 proc/boot/io-usb    21r RECEIVE     4               
    4101   3 proc/boot/io-usb    21r RECEIVE     7               
    4101   4 proc/boot/io-usb    21r RECEIVE     10              
    4101   5 proc/boot/io-usb    21r RECEIVE     13              
    4101   6 proc/boot/io-usb    21r RECEIVE     1               
    4101   7 proc/boot/io-usb    10o RECEIVE     16              
    4101   8 proc/boot/io-usb    10r NANOSLEEP                   
    4101   9 proc/boot/io-usb    10o RECEIVE     16              
    4102   1 proc/boot/io-hid    10o SIGWAITINFO                 
    4102   2 proc/boot/io-hid    10o RECEIVE     4               
    4102   3 proc/boot/io-hid    10o RECEIVE     4               
    4102   4 proc/boot/io-hid    10r REPLY       4101            
    4102   5 proc/boot/io-hid    15r RECEIVE     12              
    4102   6 proc/boot/io-hid    15r RECEIVE     16              
    4103   1 /boot/devc-con-hid  10o RECEIVE     1               
    4103   2 /boot/devc-con-hid  10o REPLY       4102            
    8200   1 roc/boot/devb-eide  10o SIGWAITINFO                 
    8200   2 roc/boot/devb-eide  21r RECEIVE     1               
    8200   3 roc/boot/devb-eide  21r RECEIVE     4               
    8200   4 roc/boot/devb-eide  10o RECEIVE     10              
    8200   6 roc/boot/devb-eide  10o RECEIVE     7               
    8200   7 roc/boot/devb-eide  10o RECEIVE     7               
    8200   8 roc/boot/devb-eide  10o RECEIVE     7               
    8200  10 roc/boot/devb-eide  10o RECEIVE     7               
    8200  12 roc/boot/devb-eide  10o RECEIVE     7               
    8201   1 oc/boot/umass-enum  10o SIGWAITINFO                 
    8201   2 oc/boot/umass-enum  10r REPLY       4101            
   16394   1 sbin/pipe           10o SIGWAITINFO                 
   16394   2 sbin/pipe           10o RECEIVE     1               
   16394   3 sbin/pipe           10o RECEIVE     1               
   16394   4 sbin/pipe           10o RECEIVE     1               
   20491   1 sbin/mqueue         10o RECEIVE     1               
   49164   1 sbin/enum-devices   10o REPLY       16394           
   77838   1 sbin/devp-pccard    21o RECEIVE     1               
   77839   1 sbin/enum-pccard    29f RECEIVE     1               
   77840   1 sbin/io-audio       10o SIGWAITINFO                 
   77840   2 sbin/io-audio       10o RECEIVE     1               
   77840   3 sbin/io-audio       10o RECEIVE     1               
   77840   4 sbin/io-audio       10o RECEIVE     1               
   77840   5 sbin/io-audio       50r INTR                        
   94225   1 sbin/devc-par       10o RECEIVE     1               
   94225   2 sbin/devc-par        9r CONDVAR     8053e00         
   94227   1 sbin/io-net         10o SIGWAITINFO                 
   94227   2...
View Full Message
RE: RE: RE: RE: Unable to mount io-net  
I'm guessing that this is right after booting?  If you don't want qnet to
start up on booting you have to remove the /etc/system/config/useqnet
(See Creating useqnet here:
http://www.qnx.com/developers/docs/6.3.2/neutrino/user_guide/qnet.html
)

To kill io-net after it's running, you have to become root and do a "slay -s
SIGKILL io-net"

	Robert.

-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Thursday, May 22, 2008 5:10 AM
To: drivers-networking
Subject: Re: RE: RE: RE: Unable to mount io-net

Thanks.
Output of pidin:
     pid tid name               prio STATE       Blocked         
       1   1 procnto              0f READY                       
       1   2 procnto             10r RECEIVE     1               
       1   3 procnto             10r RUNNING                     
       1   4 procnto             10r RECEIVE     1               
       1   5 procnto             10r RECEIVE     1               
       1   6 procnto             10r RECEIVE     1               
       1   7 procnto             10r RECEIVE     1               
       1   8 procnto             10r RECEIVE     1               
       1   9 procnto             10r RECEIVE     1               
       1  10 procnto             10r RECEIVE     1               
       1  11 procnto             10r RECEIVE     1               
       2   1 sbin/tinit          10o REPLY       1               
    4099   1 proc/boot/pci-bios  12o RECEIVE     1               
    4100   1 proc/boot/slogger   10o RECEIVE     1               
    4101   1 proc/boot/io-usb    10o SIGWAITINFO                 
    4101   2 proc/boot/io-usb    21r RECEIVE     4               
    4101   3 proc/boot/io-usb    21r RECEIVE     7               
    4101   4 proc/boot/io-usb    21r RECEIVE     10              
    4101   5 proc/boot/io-usb    21r RECEIVE     13              
    4101   6 proc/boot/io-usb    21r RECEIVE     1               
    4101   7 proc/boot/io-usb    10o RECEIVE     16              
    4101   8 proc/boot/io-usb    10r NANOSLEEP                   
    4101   9 proc/boot/io-usb    10o RECEIVE     16              
    4102   1 proc/boot/io-hid    10o SIGWAITINFO                 
    4102   2 proc/boot/io-hid    10o RECEIVE     4               
    4102   3 proc/boot/io-hid    10o RECEIVE     4               
    4102   4 proc/boot/io-hid    10r REPLY       4101            
    4102   5 proc/boot/io-hid    15r RECEIVE     12              
    4102   6 proc/boot/io-hid    15r RECEIVE     16              
    4103   1 /boot/devc-con-hid  10o RECEIVE     1               
    4103   2 /boot/devc-con-hid  10o REPLY       4102            
    8200   1 roc/boot/devb-eide  10o SIGWAITINFO                 
    8200   2 roc/boot/devb-eide  21r RECEIVE     1               
    8200   3 roc/boot/devb-eide  21r RECEIVE     4               
    8200   4 roc/boot/devb-eide  10o RECEIVE     10              
    8200   6 roc/boot/devb-eide  10o RECEIVE     7               
    8200   7 roc/boot/devb-eide  10o RECEIVE     7               
    8200   8 roc/boot/devb-eide  10o RECEIVE     7               
    8200  10 roc/boot/devb-eide  10o RECEIVE     7               
    8200  12 roc/boot/devb-eide  10o RECEIVE     7               
    8201   1 oc/boot/umass-enum  10o SIGWAITINFO                 
    8201   2 oc/boot/umass-enum  10r REPLY       4101            
   16394   1 sbin/pipe           10o SIGWAITINFO                 
   16394   2 sbin/pipe           10o RECEIVE     1               
   16394   3 sbin/pipe           10o RECEIVE     1               
   16394   4 sbin/pipe           10o RECEIVE     1               
   20491   1 sbin/mqueue         10o RECEIVE     1               
   49164   1 sbin/enum-devices   10o REPLY       16394           
   77838   1 sbin/devp-pccard    21o RECEIVE     1               
   77839   1 sbin/enum-pccard    29f RECEIVE     1               
  ...
View Full Message
Re: RE: RE: RE: RE: Unable to mount io-net  
Thx so much.
I deleted the file you specified, and i mount the qnet-compat again, now it worked. A little strange abt that is the 
useqnet is a total empty file without any scripts, then the system will still start the qnet service everytime it boots?


Eric
RE: RE: RE: RE: RE: Unable to mount io-net  
Hi Eric:
	What happens is that the startup script (/etc/system/sysinit) just
looks for the existence of that file and acts accordingly.  That's covered
in the section of the docs that I sent the link for.

	Glad that things are working for you now.
	Robert.



-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Thursday, May 22, 2008 10:19 AM
To: drivers-networking
Subject: Re: RE: RE: RE: RE: Unable to mount io-net

Thx so much.
I deleted the file you specified, and i mount the qnet-compat again, now it
worked. A little strange abt that is the useqnet is a total empty file
without any scripts, then the system will still start the qnet service
everytime it boots?

Eric

_______________________________________________
Networking Drivers
http://community.qnx.com/sf/go/post8378