el900 driver for 3C905 Fast Etherlink

Hi.

How can I tell if the el900 is working with the 3C905 Fast Etherlink card?
This network card works great on a QNX 4 system, but not on NTO.

I start the driver using…

io-net -d el900 verbose -p tcpip

I get no error messages when I start the driver.

Here is the output of ‘nicinfo’

3COM (90xB) COMBO Ethernet Controller
Physical Node ID … 000102 2ED7D7
Current Physical Node ID … 000102 2ED7D7
Media Rate … 10.00 Mb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0xD400 → 0xD47F
Hardware Interrupt … 0x5

Total Packets Txd OK … 0
Total Packets Txd Bad … 0
Total Packets Rxd OK … 0
Total Rx Errors … 0

Tx Collision Errors … 0
Tx Collisions Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 0
Tx defered … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 0
CRC errors … 0

There never seems to be any data transmitted or received. Why?
Why is the media rate 10 instead of 100 (see above and below info)?

I can’t get TCP/IP to work. I want to make sure the card is working.

Here is the ‘netinfo’ from the QNX 4 node for this card.

Total Number Of Net Driver Slots: 2

Driver Slot 0: Driver Pid 52 Logical Net 1 Network Card: Ethernet/
3Com905 Ethernet Controller
Vendor ID … 0x10b7
Device ID … 0x9058
Revision … 0x0
Physical Node ID … 000102 2ED7D7
Media Rate … 100Mb/s
Mtu … 1514
I/O Port Range … 0xD400 → 0xD47F
Hardware Interrupt … 5

Total Packets Txd OK … 1500
Total Packets Txd Bad … 0
Tx Collision Errors … 0
Tx Collision Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 0
Tx deferred … 0
Out of Window Collisions … 0

Total Packets Rxd OK … 1200
Total Rx Errors … 0
FIFO Overruns During Rx … 0
Alignment errors … 0
CRC errors … 0


Driver Slot 1: Unused

Any ideas? Please help -:slight_smile:

Thanks

Augie

Augie <augieh@scieng.com> wrote:

Hi.

How can I tell if the el900 is working with the 3C905 Fast Etherlink card?
This network card works great on a QNX 4 system, but not on NTO.

I start the driver using…

io-net -d el900 verbose -p tcpip

I get no error messages when I start the driver.

Here is the output of ‘nicinfo’

3COM (90xB) COMBO Ethernet Controller
Physical Node ID … 000102 2ED7D7
Current Physical Node ID … 000102 2ED7D7
Media Rate … 10.00 Mb/s half-duplex UTP

Is this supposed to be 10Mb? If not, try this…

io-net -d el900 speed=100,duplex=1,verbose -p tcpip

That is for 100Mb/s full duplex. Are you configuring the interface
after you run io-net? ifconfig and route and such?

chris

\

cdm@qnx.com > “The faster I go, the behinder I get.”

Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Chris McKillop <cdm@qnx.com> wrote in message
news:8rbifs$hpq$1@nntp.qnx.com

Augie <> augieh@scieng.com> > wrote:
Hi.

How can I tell if the el900 is working with the 3C905 Fast Etherlink
card?
This network card works great on a QNX 4 system, but not on NTO.

I start the driver using…

io-net -d el900 verbose -p tcpip

I get no error messages when I start the driver.

Here is the output of ‘nicinfo’

3COM (90xB) COMBO Ethernet Controller
Physical Node ID … 000102 2ED7D7
Current Physical Node ID … 000102 2ED7D7
Media Rate … 10.00 Mb/s half-duplex UTP


Is this supposed to be 10Mb? If not, try this…

io-net -d el900 speed=100,duplex=1,verbose -p tcpip

I did this. The driver still list the same info with ‘nicinfo’ :frowning:. It
looks like it is not setting any of the parameters. The speed is wrong, the
media type is wrong and it can’t go to full duplex. The card is setup for
auto speed and auto media type. I have the 3C905B-Combo, which does work
with QNX 4.

Augie

That is for 100Mb/s full duplex. Are you configuring the interface
after you run io-net? ifconfig and route and such?

chris

\

cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL

Augie <augieh@scieng.com> wrote in message news:8rcij6$gvr$1@inn.qnx.com

Chris McKillop <> cdm@qnx.com> > wrote in message
news:8rbifs$hpq$> 1@nntp.qnx.com> …
Augie <> augieh@scieng.com> > wrote:
Hi.

How can I tell if the el900 is working with the 3C905 Fast Etherlink
card?
This network card works great on a QNX 4 system, but not on NTO.

I start the driver using…

io-net -d el900 verbose -p tcpip

I get no error messages when I start the driver.

Here is the output of ‘nicinfo’

3COM (90xB) COMBO Ethernet Controller
Physical Node ID … 000102 2ED7D7
Current Physical Node ID … 000102 2ED7D7
Media Rate … 10.00 Mb/s half-duplex UTP


Is this supposed to be 10Mb? If not, try this…

io-net -d el900 speed=100,duplex=1,verbose -p tcpip

I did this. The driver still list the same info with ‘nicinfo’ > :frowning:> . It
looks like it is not setting any of the parameters. The speed is wrong,
the
media type is wrong and it can’t go to full duplex. The card is setup for
auto speed and auto media type. I have the 3C905B-Combo, which does work
with QNX 4.

Augie

The driver doesn’t work with the 3C905B-Combo card. I tried a 3C905C and
the driver did work with this card. Any chance the driver can be fixed and
posted?

Now I have a different question. It seems I can ftp other machines from the
Neutrino machine. When I try to ftp the Neutrino machine tough, I get
connection refused. What am I missing? Do you have a sample .netrc file?
Does ftp use the .netrc or .rhosts file?

I can I change from using ttcpip to tcpip? Which file should I change?

Where in the docs is this described?

Thanks

Augie

That is for 100Mb/s full duplex. Are you configuring the interface
after you run io-net? ifconfig and route and such?

chris

\



cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
\

Augie <augieh@scieng.com> wrote:

Augie <> augieh@scieng.com> > wrote in message news:8rcij6$gvr$> 1@inn.qnx.com> …

Chris McKillop <> cdm@qnx.com> > wrote in message
news:8rbifs$hpq$> 1@nntp.qnx.com> …
Augie <> augieh@scieng.com> > wrote:
Hi.

How can I tell if the el900 is working with the 3C905 Fast Etherlink
card?
This network card works great on a QNX 4 system, but not on NTO.

I start the driver using…

io-net -d el900 verbose -p tcpip

I get no error messages when I start the driver.

Here is the output of ‘nicinfo’

3COM (90xB) COMBO Ethernet Controller
Physical Node ID … 000102 2ED7D7
Current Physical Node ID … 000102 2ED7D7
Media Rate … 10.00 Mb/s half-duplex UTP


Is this supposed to be 10Mb? If not, try this…

io-net -d el900 speed=100,duplex=1,verbose -p tcpip

I did this. The driver still list the same info with ‘nicinfo’ > :frowning:> . It
looks like it is not setting any of the parameters. The speed is wrong,
the
media type is wrong and it can’t go to full duplex. The card is setup for
auto speed and auto media type. I have the 3C905B-Combo, which does work
with QNX 4.

Augie

The driver doesn’t work with the 3C905B-Combo card. I tried a 3C905C and
the driver did work with this card. Any chance the driver can be fixed and
posted?

If it’s a “combo”, the “connector=xxx” driver option may also important.
“use /lib/dll/devn-el900.so” to make sure you submit the right option.

Now I have a different question. It seems I can ftp other machines from the
Neutrino machine. When I try to ftp the Neutrino machine tough, I get
connection refused. What am I missing? Do you have a sample .netrc file?
Does ftp use the .netrc or .rhosts file?

Start “/sbin/inetd”.

I can I change from using ttcpip to tcpip? Which file should I change?

“slay io-net; io-net -d el900 -p tcpip”.
If this works, put these commands in /etc/rc/rc.local, do a chmod a+x
on it if you just create it.

-xtang

Where in the docs is this described?

Thanks

Augie



That is for 100Mb/s full duplex. Are you configuring the interface
after you run io-net? ifconfig and route and such?

chris

\



cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
\

Xiaodan Tang <xtang@ottawa.com> wrote in message
news:8rcoik$9dn$1@nntp.qnx.com

Augie <> augieh@scieng.com> > wrote:

Augie <> augieh@scieng.com> > wrote in message
news:8rcij6$gvr$> 1@inn.qnx.com> …

Chris McKillop <> cdm@qnx.com> > wrote in message
news:8rbifs$hpq$> 1@nntp.qnx.com> …
Augie <> augieh@scieng.com> > wrote:
Hi.

How can I tell if the el900 is working with the 3C905 Fast
Etherlink
card?
This network card works great on a QNX 4 system, but not on NTO.

I start the driver using…

io-net -d el900 verbose -p tcpip

I get no error messages when I start the driver.

Here is the output of ‘nicinfo’

3COM (90xB) COMBO Ethernet Controller
Physical Node ID … 000102 2ED7D7
Current Physical Node ID … 000102 2ED7D7
Media Rate … 10.00 Mb/s half-duplex UTP


Is this supposed to be 10Mb? If not, try this…

io-net -d el900 speed=100,duplex=1,verbose -p tcpip

I did this. The driver still list the same info with ‘nicinfo’ > :frowning:> .
It
looks like it is not setting any of the parameters. The speed is
wrong,
the
media type is wrong and it can’t go to full duplex. The card is setup
for
auto speed and auto media type. I have the 3C905B-Combo, which does
work
with QNX 4.

Augie

The driver doesn’t work with the 3C905B-Combo card. I tried a 3C905C
and
the driver did work with this card. Any chance the driver can be fixed
and
posted?

If it’s a “combo”, the “connector=xxx” driver option may also important.
“use /lib/dll/devn-el900.so” to make sure you submit the right option.

Yes sir. I did this. The driver doesn’t seem to be affected by any of the
parameters passed. It finds the card, but it does not change any of the
default parameters.

Now I have a different question. It seems I can ftp other machines from
the
Neutrino machine. When I try to ftp the Neutrino machine tough, I get
connection refused. What am I missing? Do you have a sample .netrc
file?
Does ftp use the .netrc or .rhosts file?

Start “/sbin/inetd”.

I can I change from using ttcpip to tcpip? Which file should I change?

“slay io-net; io-net -d el900 -p tcpip”.
If this works, put these commands in /etc/rc/rc.local, do a chmod a+x
on it if you just create it.

Wow! You mean I have to slay io-net and then restart it again? Can’t I
just start it with the correct options the first time?

I would like to understand how QNX RTP performs the boot sequence? In QNX 4
we were able to add/remove drivers nicelly from the sysinit file. Is this
been taken away? Are there no file(s) were we can put these?

Thanks

Augie


-xtang

Where in the docs is this described?

Thanks

Augie



That is for 100Mb/s full duplex. Are you configuring the interface
after you run io-net? ifconfig and route and such?

chris

\




cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL



\

Augie <augieh@scieng.com> wrote:

Xiaodan Tang <> xtang@ottawa.com> > wrote in message
news:8rcoik$9dn$> 1@nntp.qnx.com> …
Augie <> augieh@scieng.com> > wrote:

Augie <> augieh@scieng.com> > wrote in message
news:8rcij6$gvr$> 1@inn.qnx.com> …

Chris McKillop <> cdm@qnx.com> > wrote in message
news:8rbifs$hpq$> 1@nntp.qnx.com> …
Augie <> augieh@scieng.com> > wrote:
Hi.

How can I tell if the el900 is working with the 3C905 Fast
Etherlink
card?
This network card works great on a QNX 4 system, but not on NTO.

I start the driver using…

io-net -d el900 verbose -p tcpip

I get no error messages when I start the driver.

Here is the output of ‘nicinfo’

3COM (90xB) COMBO Ethernet Controller
Physical Node ID … 000102 2ED7D7
Current Physical Node ID … 000102 2ED7D7
Media Rate … 10.00 Mb/s half-duplex UTP


Is this supposed to be 10Mb? If not, try this…

io-net -d el900 speed=100,duplex=1,verbose -p tcpip

I did this. The driver still list the same info with ‘nicinfo’ > :frowning:> .
It
looks like it is not setting any of the parameters. The speed is
wrong,
the
media type is wrong and it can’t go to full duplex. The card is setup
for
auto speed and auto media type. I have the 3C905B-Combo, which does
work
with QNX 4.

Augie

The driver doesn’t work with the 3C905B-Combo card. I tried a 3C905C
and
the driver did work with this card. Any chance the driver can be fixed
and
posted?

If it’s a “combo”, the “connector=xxx” driver option may also important.
“use /lib/dll/devn-el900.so” to make sure you submit the right option.

Yes sir. I did this. The driver doesn’t seem to be affected by any of the
parameters passed. It finds the card, but it does not change any of the
default parameters.

OK. Then I have no idea :slight_smile: I assume you sure there is no space, only “,”
between each option right.

Now I have a different question. It seems I can ftp other machines from
the
Neutrino machine. When I try to ftp the Neutrino machine tough, I get
connection refused. What am I missing? Do you have a sample .netrc
file?
Does ftp use the .netrc or .rhosts file?

Start “/sbin/inetd”.

I can I change from using ttcpip to tcpip? Which file should I change?

“slay io-net; io-net -d el900 -p tcpip”.
If this works, put these commands in /etc/rc/rc.local, do a chmod a+x
on it if you just create it.

Wow! You mean I have to slay io-net and then restart it again? Can’t I
just start it with the correct options the first time?

I would like to understand how QNX RTP performs the boot sequence? In QNX 4
we were able to add/remove drivers nicelly from the sysinit file. Is this
been taken away? Are there no file(s) were we can put these?

You can change “/etc/system/enum/include/net”, to start the “-ptcpip”
for you.

The reason I don’t recommanded this, is because this file in in
system package, and next time, if you install a new one/update a
patch, this could be getting tricky.

-xtang

Thanks

Augie



-xtang

Where in the docs is this described?

Thanks

Augie



That is for 100Mb/s full duplex. Are you configuring the interface
after you run io-net? ifconfig and route and such?

chris

\




cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL



\