The tulip driver doesn’t seem to work as documented on QNX 6.2 PE. If I look
at the use message (use /lib/dll/devn-tulip.so) the verbose option is listed
like this:
Options (to override autodetected defaults):
verbose Be verbose.
Options:
verbose=0|1|2|3
The higher the number, the more verbose the messages. The default is 0 (no
messages).
The bad thing is that I can seem to get EITHER of them to work. Neither
“io-net -dtulip verbose=3 -pqnet” or “io-net -dtulip verbose -pqnet” print
out any information to stdout or stderr, although I know in previous
versions of 6.X they did.
Am I doing something wrong, or do others have this same problem? If it is a
problem with the driver, how do I submit a bug fix request?
The verbose output from the network drivers now goes to slogger, so you
will have to do a ‘sloginfo’ to see the output.
Previously, Matthew Herberg wrote in qdn.public.qnxrtp.os:
The tulip driver doesn’t seem to work as documented on QNX 6.2 PE. If I look
at the use message (use /lib/dll/devn-tulip.so) the verbose option is listed
like this:
Options (to override autodetected defaults):
verbose Be verbose.
Options:
verbose=0|1|2|3
The higher the number, the more verbose the messages. The default is 0 (no
messages).
The bad thing is that I can seem to get EITHER of them to work. Neither
“io-net -dtulip verbose=3 -pqnet” or “io-net -dtulip verbose -pqnet” print
out any information to stdout or stderr, although I know in previous
versions of 6.X they did.
Am I doing something wrong, or do others have this same problem? If it is a
problem with the driver, how do I submit a bug fix request?
The verbose output from the network drivers now goes to slogger, so you
will have to do a ‘sloginfo’ to see the output.
That is the case with most network drivers, but not with the tulip. The
tulip driver still prints its verbose output to stderr – this is a known
issue PR9735.
Previously, Matthew Herberg wrote in qdn.public.qnxrtp.os:
The tulip driver doesn’t seem to work as documented on QNX 6.2 PE. If I look
at the use message (use /lib/dll/devn-tulip.so) the verbose option is listed
like this:
Options (to override autodetected defaults):
verbose Be verbose.
There appears to be a bug in how the tulip driver parses the command line
arguments. Don’t know if this is a known issue or not. Try this instead:
“io-net -dtulip verbose=3,verbose=3 -pqnet”
or
“io-net -dtulip verbose,verbose -pqnet”
This works for me:
amdk6iii-1# slay -f io-net
amdk6iii-1# io-net -d tulip verbose,verbose
amdk6iii-1# Tulip: LiteOn PNIC
Vendor … 0x11ad
Device … 0x2
Revision … 0x0
I/O port base … 0xd400
Interrupt … 0xc
MAC address … 00a0cc 111111