Specifying a devn* in the bootup config files.

QNX Newsgroups (Archives) qdn.public.qnxrtp.installation
1

Hello.

I was wondering if anyone has had any experience in passing devn* stuff
to the io-net command on bootup.
I have been playing with the /etc/system/enum/include/net file, trying
to modify the line that says:

set( IONET_CMD, io-net …)

Currently, I have it simply set to: set( IONET_CMD, io-net -ptcpip )

The network driver that nettrap detects (when I do: nettrap query) is
the devn-el900.so. I would like to
pass in the arguments to set the card to full duplex and 100Mbit, as
opposed to allowing it to autodetect.

I have tried from the command line to find a io-net sequence that will
work but I have been very unsuccessful. As well, I would
like whatever stuff I do to work with the phlip utility. I tried
something like:

io-net -ptcpip -del900 duplex=1 speed=100

Any help would be much appreciated. Thanks.

Rodney Lott

2

Hi Rodney,

Try comma separating your options.

ex: io-net -del9000 duplex=1,speed=100 -ptcpip

Note: Make sure there are no spaces between comma and options.

Regards,

Joe

Rodney Lott <rod@fuelcelltechnologies.ca> wrote:

Hello.

I was wondering if anyone has had any experience in passing devn* stuff
to the io-net command on bootup.
I have been playing with the /etc/system/enum/include/net file, trying
to modify the line that says:

set( IONET_CMD, io-net …)

Currently, I have it simply set to: set( IONET_CMD, io-net -ptcpip )

The network driver that nettrap detects (when I do: nettrap query) is
the devn-el900.so. I would like to
pass in the arguments to set the card to full duplex and 100Mbit, as
opposed to allowing it to autodetect.

I have tried from the command line to find a io-net sequence that will
work but I have been very unsuccessful. As well, I would
like whatever stuff I do to work with the phlip utility. I tried
something like:

io-net -ptcpip -del900 duplex=1 speed=100

Any help would be much appreciated. Thanks.

Rodney Lott

3

Hi, Joe.

I tried it out, first by putting it in the /etc/system/enum/includes/net
file and
the network stuff didn’t start up. I see messages about the io-net
mount not
occurring and all kinds of network related errors.

I then slayed io-net and started it up on the cmd line. It sort-of
started okay - I could
do a netstat -rn and see a minimal table. I started up phlip and it
started okay, except
all the previous IP info was gone (which I suppose is reasonable since I
am messing
around with the lower interface).

I guess my question is: can I add the same command line stuff to the
set
command that is in /etc/system/enum/includes/net? Or do I have to just
accept that
it can’t take the arguments at that stage?

Thanks.

Rodney

Hardware Support Account wrote:

Hi Rodney,

Try comma separating your options.

ex: io-net -del9000 duplex=1,speed=100 -ptcpip

Note: Make sure there are no spaces between comma and options.

Regards,

Joe

Rodney Lott <> rod@fuelcelltechnologies.ca> > wrote:
Hello.

I was wondering if anyone has had any experience in passing devn* stuff
to the io-net command on bootup.
I have been playing with the /etc/system/enum/include/net file, trying
to modify the line that says:

set( IONET_CMD, io-net …)

Currently, I have it simply set to: set( IONET_CMD, io-net -ptcpip )

The network driver that nettrap detects (when I do: nettrap query) is
the devn-el900.so. I would like to
pass in the arguments to set the card to full duplex and 100Mbit, as
opposed to allowing it to autodetect.

I have tried from the command line to find a io-net sequence that will
work but I have been very unsuccessful. As well, I would
like whatever stuff I do to work with the phlip utility. I tried
something like:

io-net -ptcpip -del900 duplex=1 speed=100

Any help would be much appreciated. Thanks.

Rodney Lott

4

Hi Rodney,

You will want to make your changes in the /etc/system/enum/devices/net file.

Search the file for where io-net is being mounted with the driver for your device.
Do a ‘pci -vvv’ to find out the device id for your network card (will display info for pci devices only)

example:

90x devices

device(pci, ven=$(PCI_VEND_3COM), dev=9000) # 900
device(pci, ven=$(PCI_VEND_3COM), dev=9050) # 905
device(pci, ven=$(PCI_VEND_3COM), dev=9055) # 905B
device(pci, ven=$(PCI_VEND_3COM), dev=9058) # COMBO
device(pci, ven=$(PCI_VEND_3COM), dev=9200)
device(pci, ven=$(PCI_VEND_3COM), dev=9001)
device(pci, ven=$(PCI_VEND_3COM), dev=9051)
device(pci, ven=$(PCI_VEND_3COM), dev=9056)
device(pci, ven=$(PCI_VEND_3COM), dev=9004)
device(pci, ven=$(PCI_VEND_3COM), dev=9005)
device(pci, ven=$(PCI_VEND_3COM), dev=9006)
device(pci, ven=$(PCI_VEND_3COM), dev=900a)
device(pci, ven=$(PCI_VEND_3COM), dev=905a)
device(pci, ven=$(PCI_VEND_3COM), dev=9800)
tag(devn)
append(legacy, “,nonet”)
requires($(IONET_CMD),)
uniq(netnum, devn-en, 0)
mount(-Tio-net “-opci=$(index)” /lib/dll/devn-el900.so, “/dev/io-net/en$(netnum)”)
use(symbolic=netmgr)

You will want to modify the mount command to include the wanted driver options.

example:
mount(-Tio-net “-opci=$(index),connector=1,speed=100” /lib/dll/devn-el900.so, “/dev/io-net/en$(netnum)”)

The next time you boot your computer and the enumerator runs the changes will take affect.
Do a ‘nicinfo’ to confirm the changes.

Regards,

Joe



Rodney Lott <rod@fuelcelltechnologies.ca> wrote:

Hi, Joe.

I tried it out, first by putting it in the /etc/system/enum/includes/net
file and
the network stuff didn’t start up. I see messages about the io-net
mount not
occurring and all kinds of network related errors.

I then slayed io-net and started it up on the cmd line. It sort-of
started okay - I could
do a netstat -rn and see a minimal table. I started up phlip and it
started okay, except
all the previous IP info was gone (which I suppose is reasonable since I
am messing
around with the lower interface).

I guess my question is: can I add the same command line stuff to the
set
command that is in /etc/system/enum/includes/net? Or do I have to just
accept that
it can’t take the arguments at that stage?

Thanks.

Rodney

Hardware Support Account wrote:

Hi Rodney,

Try comma separating your options.

ex: io-net -del9000 duplex=1,speed=100 -ptcpip

Note: Make sure there are no spaces between comma and options.

Regards,

Joe

Rodney Lott <> rod@fuelcelltechnologies.ca> > wrote:
Hello.

I was wondering if anyone has had any experience in passing devn* stuff
to the io-net command on bootup.
I have been playing with the /etc/system/enum/include/net file, trying
to modify the line that says:

set( IONET_CMD, io-net …)

Currently, I have it simply set to: set( IONET_CMD, io-net -ptcpip )

The network driver that nettrap detects (when I do: nettrap query) is
the devn-el900.so. I would like to
pass in the arguments to set the card to full duplex and 100Mbit, as
opposed to allowing it to autodetect.

I have tried from the command line to find a io-net sequence that will
work but I have been very unsuccessful. As well, I would
like whatever stuff I do to work with the phlip utility. I tried
something like:

io-net -ptcpip -del900 duplex=1 speed=100

Any help would be much appreciated. Thanks.

Rodney Lott

5

Rodney Lott <rod@fuelcelltechnologies.ca> wrote:

Hi, Joe.

I tried it out, first by putting it in the /etc/system/enum/includes/net
file and
the network stuff didn’t start up. I see messages about the io-net
mount not
occurring and all kinds of network related errors.

I then slayed io-net and started it up on the cmd line. It sort-of
started okay - I could
do a netstat -rn and see a minimal table. I started up phlip and it
started okay, except
all the previous IP info was gone (which I suppose is reasonable since I
am messing
around with the lower interface).

I guess my question is: can I add the same command line stuff to the
set
command that is in /etc/system/enum/includes/net? Or do I have to just
accept that
it can’t take the arguments at that stage?

You can edit /etc/system/enum/device/net, devn-* mount commands are in
there. But this is NOT a recommanded way to do it.

The recommanded way is create/edit your own /etc/rc.d/rc.local, and
kill, restart io-net (with your own options) there.

-xtang

6

Hi!

Is it possible to open text mode (console) without quiting the Photon
session?
It’s because I like big letters in text mode (VIM) and html help in Photon
:slight_smile:

Darek Borkowski

7

Thanks, Joe and Xiaodan.

I will try a couple of those things.

Rodney

Xiaodan Tang wrote:

Rodney Lott <> rod@fuelcelltechnologies.ca> > wrote:
Hi, Joe.

I tried it out, first by putting it in the /etc/system/enum/includes/net
file and
the network stuff didn’t start up. I see messages about the io-net
mount not
occurring and all kinds of network related errors.

I then slayed io-net and started it up on the cmd line. It sort-of
started okay - I could
do a netstat -rn and see a minimal table. I started up phlip and it
started okay, except
all the previous IP info was gone (which I suppose is reasonable since I
am messing
around with the lower interface).

I guess my question is: can I add the same command line stuff to the
set
command that is in /etc/system/enum/includes/net? Or do I have to just
accept that
it can’t take the arguments at that stage?

You can edit /etc/system/enum/device/net, devn-* mount commands are in
there. But this is NOT a recommanded way to do it.

The recommanded way is create/edit your own /etc/rc.d/rc.local, and
kill, restart io-net (with your own options) there.

-xtang

8

Hi,

If all you want to do is increase the font size for the terminal you can just
right click on the terminal and choose properties, then enlarge the font to
your liking.

Regards,

Barry

Dariusz Borkowski <borkows@uci.agh.edu.pl> wrote:

Hi!

Is it possible to open text mode (console) without quiting the Photon
session?
It’s because I like big letters in text mode (VIM) and html help in Photon
:slight_smile:

Darek Borkowski