Carl Rosenberger wrote:
After getting the device ID with ‘pci -vvv’, I use the following
command:
io-net -dspeedo vid=0x8086,did=0x1043,pci=0x0 -ptcpip
Sheesh, the above mistake cost me half a day experimenting
with just about everything.
0x1043 is the WLAN card, the 82562 EZ has a device ID of
0x103D
Accordingly the correct call for my notebook would be:
io-net -dspeedo vid=0x8086,did=0x103D,pci=0x0 -ptcpip
Trying to track the problem down, I did learn a lot about
QNX, so I might as well try to answer my own questions:
(1) Now I want to configure QNX to use the Internet Connection
Sharing of my W2K box.
W2K works as a Gateway at:
192.168.0.1 subnet 255.255.255.0
A manual setup of the QNX box to be in the same range
as the W2K box could look like this:
ifconfig en0 192.168.0.7 netmask 255.255.255.0
To use the W2K server as a gateway:
route add default 192.168.0.1
I also want to use the DNS-Server of my Internet provider:
194.25.2.129
I don’t think this is necessary, since the W2K box resolves
the addresses.
I also have a DHCP Server running on my router at
192.168.0.3 subnet 255.255.255.0
This is even easier than ifconfig.
A simple “dhcp.client” after calling “io-net” does the trick.
(2) If I run io-net in a script, it appears to take some time, until
en0 is available and ipconfig fails, if I execute it immediately
in the same script. How would I specify to wait for the first command
to complete?
From what I have read in GoogleGroups
waitfor /dev/socket/
is intended to solve this issue.
However, it didn’t work for me, I wonder why.
I have been successful by issuing the “io-net” call in
/etc/rc.d/rc.local and the following two lines in
/usr/bin/ph:
waitfor /dev/socket
/usr/sbin/dhcp.client &
(3) npm-ttcpip.so would allow me to specify router and gateway
right away in the io-net call, but it doesn’t seem to be available
in my 6.2.1 NC distribution, although it is listed in the help
files. Is this on purpose?
I still don’t understand why this file does not come with the
NC distribution, although it is documented.
(4) I would like to configure TCP-IP on startup of my machine.
What would be the recommended place?
/etc/rc.d/rc.local is intended for custom startup code.
It just needs to be created to be run automatically from
/etc/rc.d/rc.sysinit
I would prefer all the documented configuration files to be
present on a newly installed system (lot’s of others are
missing also) but that’s a matter of taste.
As written above, I moved part of my own initialisation
routine to /usr/bin/ph.
Maybe someone can point me to a better place for late
initialisations.
I also didn’t like that all changes that I make to the $PATH
environment variable in /etc/rc.d/rc.local get lost when
Photon starts up.
I suppose, I could also get my network card to work with some
changes in /etc/system/enum/devices/net.
Maybe the QNX team wants to add the device ID of 0x103D to the
Intel list there.
It would also make sense to pass the device- and PCI-IDs as
parameters to “mount”.
Did you try devn-prism.so?
I can’t find devn-prism.so in my NC distribution.
Again, I don’t understand why a couple of files are documented
in the NC version but not distributed.
Further to all of the above, I got Eclipse 2.1.2 to work on Neutrino
with IBMs J9 today. It’s a bit of a pain to collect the necessary
jclMax files and the QNX runtime from within the update perspective
of WSDD but now that the system is running it looks great:
fast, smooth, good-looking
Good job QNX and IBM!
I really hope that QNX and J9 will be the favourite platform for all
sorts of embedded systems.
Thanks for letting me try the evaluation version!
Kind regards,
Carl
Carl Rosenberger
db4o - database for objects - http://www.db4o.com
