Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - How to integrate io-pkt into the enumeration process during boot up?: (6 Items)
   
How to integrate io-pkt into the enumeration process during boot up?  
I have a target system with 2 network adapters, one is a Intel chip, the other is a Marvell chip VendorID: 11abh, 
DeviceID: 4362h, 88E8053. Because there is only a io-pkt driver for the Marvell availiable ( which is working when 
started manually) I tried to change the device enumeration and include the starting of io-pkt there.

-> I added to /etc/system/enum/include/pci-vendors a line:
set(PCI_VEND_MARVELL,4362)

-> I added a new entry for the Marvel chip in /etc/system/enum/devices/net

#Marvell
device( pci, ven=$(PCI_VEND_MARVELL),dev=11ab
tag(devn)
append(legacy, ",nonet")
uniq(netnum,devn-en, 0)
requires($IONET_CMD),)
mount(-Tio-pkt /lib/dll/devnp-msk.so,)
use(symbolic=netmgr)

-> in /etc/system/enum/overrides I set the following

all
set(IONET_CMD, io-pkt-v6-hc -ptcpip)

Result: did not work.

->Errors occuring during boot up: 
mount: Can't mount / (type io-pkt-v6-hc)
mount: Possible reason: Invalid argument
mount: Can't mount / (type io-pkt)
mount: Possible reason: Invalid argument

How to change IONET_CMD and mount lines to use io-pkt for all network devices in the system?
RE: How to integrate io-pkt into the enumeration process during boot up?  
Can you post the output from "pidin", "pidin mem" and "sloginfo" from
your system after it's booted?  I'll try and reproduce your problem
here.


I'd recommend modifying /etc/system/enum/include/net instead of
/etc/system/enum/overrides to change the IONET_CMD line. I'm not 100%
sure that the "overrides" overrides the include side of things.  It will
definitely override a device clause, but I'm not sure if it overrides a
macro definition.

Once you've modified the "IONET_CMD" option, then everything should work
OK as long as you've got the proper libraries / binaries in place on the
target.

	Robert.


-----Original Message-----
From: stefan thiel [mailto:s.thiel@multitest.com] 
Sent: Tuesday, June 17, 2008 7:59 AM
To: ionetmig-networking
Subject: How to integrate io-pkt into the enumeration process during
boot up?

I have a target system with 2 network adapters, one is a Intel chip, the
other is a Marvell chip VendorID: 11abh, DeviceID: 4362h, 88E8053.
Because there is only a io-pkt driver for the Marvell availiable ( which
is working when started manually) I tried to change the device
enumeration and include the starting of io-pkt there.

-> I added to /etc/system/enum/include/pci-vendors a line:
set(PCI_VEND_MARVELL,4362)

-> I added a new entry for the Marvel chip in
/etc/system/enum/devices/net

#Marvell
device( pci, ven=$(PCI_VEND_MARVELL),dev=11ab
tag(devn)
append(legacy, ",nonet")
uniq(netnum,devn-en, 0)
requires($IONET_CMD),)
mount(-Tio-pkt /lib/dll/devnp-msk.so,)
use(symbolic=netmgr)

-> in /etc/system/enum/overrides I set the following

all
set(IONET_CMD, io-pkt-v6-hc -ptcpip)

Result: did not work.

->Errors occuring during boot up: 
mount: Can't mount / (type io-pkt-v6-hc)
mount: Possible reason: Invalid argument
mount: Can't mount / (type io-pkt)
mount: Possible reason: Invalid argument

How to change IONET_CMD and mount lines to use io-pkt for all network
devices in the system?


_______________________________________________
io-net migration
http://community.qnx.com/sf/go/post9278
Re: RE: How to integrate io-pkt into the enumeration process during boot up?  
See the attached files
Attachment: Compressed file pidin.zip 8.76 KB
RE: RE: How to integrate io-pkt into the enumeration process during boot up?  
I've changed the block that you have in the net file (added the
"waitfor" line).
Can you double check that the file /lib/dll/devnp-msk.so exists?


device(pci, ven=$(PCI_VEND_MARVELL), dev=11ab)
	requires($(IONET_CMD),)
	waitfor /dev/socket
	mount(-Tio-pkt /lib/dll/devnp-msk.so, )
	use(symbolic=netmgr)




-----Original Message-----
From: stefan thiel [mailto:s.thiel@multitest.com] 
Sent: Tuesday, June 17, 2008 12:25 PM
To: ionetmig-networking
Subject: Re: RE: How to integrate io-pkt into the enumeration process
during boot up?

See the attached files


_______________________________________________
io-net migration
http://community.qnx.com/sf/go/post9338
Re: RE: RE: How to integrate io-pkt into the enumeration process during boot up?  
sorry, doesn't work.

I found the the line 
waitfor /dev/socket 
has to be 
waitfor( /dev/socket)
in the enumeration file, but end up with only the loopback device.
I think the mount command is not doing the correct thing, because
io-pkt-v6-hc is running after enumeration has finished.

I stop my investigation at this point and wait for an official release which will have this autostart I guess.

In the meantime I put all the stuff in a script which I run from rc.local.

This does the job.
Thanks for the moment
Re: RE: RE: How to integrate io-pkt into the enumeration process during boot up?  
Yup.  Quite right about the missing brackets around the waitfor statement.  That's what I get for not cut/pasting...

There's definitely a /lib/dll/devnp-msk.so is there (just to double check)?.  The other thing to do is to provide the 
output from sloginfo.  That'll give us some idea about what the stack thinks happened.  

You can actually get some verbose output from the enumerator to see what's going on if you like.

You have to log in as root (to make sure that your paths are properly set up...don't "su") and then run

enum-devices -vvvvv 2>&1 | more 

you can page through the output and see what the enumerator thinks it's doing.

(This will re-attempt to start up existing drivers, so you might have to ^C it at some point if it stops).