However at times the during bootup the following error message is reported:
ifconfig: socket: no such file or directory. On one particular board the
error is reproducible (4 out of 5 times of booting), on others the problem
is intermittend (every couple of days) on others again the error never
occured. Does anyone have suggestions?
Drop the & on io-net, it will detach itself once it has done the loading
of the DLLs. The if_up actually ensures that the socket layer is aware
of the interface while the waitfor only ensures that the driver is loaded.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll – http://qnx.wox.org/
Chris,
do you by any chance know why the different mothervoards behave so
different. Apparently does the network driver on some machines load faster
than on others; and can it really take a minute or more to load the speedo
driver.
Drop the & on io-net, it will detach itself once it has done the loading
of the DLLs. The if_up actually ensures that the socket layer is aware
of the interface while the waitfor only ensures that the driver is loaded.
chris
–
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll – http://qnx.wox.org/
Chris,
do you by any chance know why the different mothervoards behave so
different. Apparently does the network driver on some machines load faster
than on others; and can it really take a minute or more to load the speedo
driver.
It will likly depend on the phy (phyiscal layer) and how it does the
negotiation with the other side of the connection. If you know the speed
and duplex of the connection ahead of time you can try to force it on the
command line to the driver, that can speed things up.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll – http://qnx.wox.org/
Chris,
something is not working there, I modified my build and tried your solution,
but I get only the two error messages:
if_up : socket : No such file or directory
ifconfig : socket : No such file or directory
When I start if_up on the command line after the boot is completed is get
the same error. However I can start ifconfig successfully. I will revert
back to my initial solution using waitfor and just remove the timeout.
Drop the & on io-net, it will detach itself once it has done the loading
of the DLLs. The if_up actually ensures that the socket layer is aware
of the interface while the waitfor only ensures that the driver is loaded.
chris
–
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll – http://qnx.wox.org/
Chris,
something is not working there, I modified my build and tried your solution,
but I get only the two error messages:
if_up : socket : No such file or directory
ifconfig : socket : No such file or directory
When I start if_up on the command line after the boot is completed is get
the same error. However I can start ifconfig successfully. I will revert
back to my initial solution using waitfor and just remove the timeout.
Drop the & on io-net, it will detach itself once it has done the loading
of the DLLs. The if_up actually ensures that the socket layer is aware
of the interface while the waitfor only ensures that the driver is loaded.
chris
–
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll – http://qnx.wox.org/
Marcus Daiber <> mdaiber@ziimaging.com> > wrote:
Chris,
something is not working there, I modified my build and tried your
solution,
but I get only the two error messages:
if_up : socket : No such file or directory
You did take the & away from the end of io-net command line right?
chris
\
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll – http://qnx.wox.org/
In article <bp3i4g$bvp$> 1@inn.qnx.com> >, > mdaiber@ziimaging.com > says…
Chris,
something is not working there, I modified my build and tried your
solution,
but I get only the two error messages:
if_up : socket : No such file or directory
ifconfig : socket : No such file or directory
When I start if_up on the command line after the boot is completed is
get
the same error. However I can start ifconfig successfully. I will revert
back to my initial solution using waitfor and just remove the timeout.
Drop the & on io-net, it will detach itself once it has done the
loading
of the DLLs. The if_up actually ensures that the socket layer is
aware
of the interface while the waitfor only ensures that the driver is
loaded.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I
get.”
Software Engineer, QSSL – Lewis Carroll – http://qnx.wox.org/
In article <bp3i4g$bvp$> 1@inn.qnx.com> >, > mdaiber@ziimaging.com > says…
Chris,
something is not working there, I modified my build and tried your
solution,
but I get only the two error messages:
if_up : socket : No such file or directory
ifconfig : socket : No such file or directory
When I start if_up on the command line after the boot is completed is
get
the same error. However I can start ifconfig successfully. I will revert
back to my initial solution using waitfor and just remove the timeout.
Drop the & on io-net, it will detach itself once it has done the
loading
of the DLLs. The if_up actually ensures that the socket layer is
aware
of the interface while the waitfor only ensures that the driver is
loaded.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I
get.”
Software Engineer, QSSL – Lewis Carroll – http://qnx.wox.org/
