“Operating Systems Group” <os@qnx.com> wrote in message
news:9vnkvp$g7u$1@nntp.qnx.com…
“Sean Boudreau” <> seanb@qnx.com> > wrote in message
news:9vnir0$e70$> 1@nntp.qnx.com> …
Jim Lambert <> jlambert@futurex.com> > wrote:
: I was using the driver for Intel’s 82557 but I switched the card out
today
: to an Intel 82559 with the same results. I don’t know what driver it
is
: using other than that it is the default driver for the above card. It
finds
: it without me having to change anything.
Both of these use devn-speedo.so. You can see what is mounted into
io-net
by looking at the output from ‘pidin me’.
I would try a different chipset based NIC card (like 3com etc), but also
try
using the new speedo driver available on developers.qnx.com/Fixes . See
if
that helps at all.
I’ll try the new speedo first. It might take me a while to find a different
nic card (we have a lot of these Intels floating around 
)
Keep us posted on your library linking status as well.
Will do.
Thanks,
Jim
“Operating Systems Group” <os@qnx.com> wrote in message
news:9vnkvp$g7u$1@nntp.qnx.com…
“Sean Boudreau” <> seanb@qnx.com> > wrote in message
news:9vnir0$e70$> 1@nntp.qnx.com> …
Jim Lambert <> jlambert@futurex.com> > wrote:
: I was using the driver for Intel’s 82557 but I switched the card out
today
: to an Intel 82559 with the same results. I don’t know what driver it
is
: using other than that it is the default driver for the above card. It
finds
: it without me having to change anything.
Both of these use devn-speedo.so. You can see what is mounted into
io-net
by looking at the output from ‘pidin me’.
I would try a different chipset based NIC card (like 3com etc), but also
try
using the new speedo driver available on developers.qnx.com/Fixes . See
if
that helps at all.
I have downloaded it but do not know exactly where it needs to go in my
system (devn-speedo fix). Is there a set way to install these or do I just
tar out the one I need and copy it to lib/dll?
TIA,
Jim
“Jim Lambert” <jlambert@futurex.com> wrote in message
news:9vnv6i$5r8$1@inn.qnx.com…
I put the devn-speedo.so file in /lib/dll. I then rebooted and ran my
program. It exhibited the same behavior except the first error shown was
error code 6 and then the rest of the daemons failed with error code 3.
The best way to avoid config file problems when experimenting, is to slay
off io-net, then restart it with just the protocol (eg. io-net -ptcpip).
Then mount the driver from your current dir onto io-net (eg. mount -T io-net
…/devn-speedo.so)
That way you know you’re using the new speedo driver and don’t have extra
“stuff” loaded.
-Adam
“Operating Systems Group” <os@qnx.com> wrote in message
news:9vnkvp$g7u$1@nntp.qnx.com…
“Sean Boudreau” <> seanb@qnx.com> > wrote in message
news:9vnir0$e70$> 1@nntp.qnx.com> …
Jim Lambert <> jlambert@futurex.com> > wrote:
: I was using the driver for Intel’s 82557 but I switched the card out
today
: to an Intel 82559 with the same results. I don’t know what driver it
is
: using other than that it is the default driver for the above card. It
finds
: it without me having to change anything.
Both of these use devn-speedo.so. You can see what is mounted into
io-net
by looking at the output from ‘pidin me’.
I would try a different chipset based NIC card (like 3com etc), but also
try
using the new speedo driver available on developers.qnx.com/Fixes . See
if
that helps at all.
I put the devn-speedo.so file in /lib/dll. I then rebooted and ran my
program. It exhibited the same behavior except the first error shown was
error code 6 and then the rest of the daemons failed with error code 3.
YOUCH! Just popped back over to QNX box to restart io-net and my box is
locked hard. Mouse doesn’t move and am going to have to hard boot it. 
Jim
“Operating Systems Group” <os@qnx.com> wrote in message
news:9vnkvp$g7u$1@nntp.qnx.com…
“Sean Boudreau” <> seanb@qnx.com> > wrote in message
news:9vnir0$e70$> 1@nntp.qnx.com> …
Jim Lambert <> jlambert@futurex.com> > wrote:
: I was using the driver for Intel’s 82557 but I switched the card out
today
: to an Intel 82559 with the same results. I don’t know what driver it
is
: using other than that it is the default driver for the above card. It
finds
: it without me having to change anything.
Both of these use devn-speedo.so. You can see what is mounted into
io-net
by looking at the output from ‘pidin me’.
I would try a different chipset based NIC card (like 3com etc), but also
try
using the new speedo driver available on developers.qnx.com/Fixes . See
if
that helps at all.
Went out and purchased a 3c905C TX-M card today. It loaded up the correct
el900 driver in io-net. Ran my tests and the same thing happened (ie.
io-net crashed).
The weird thing is that it looked like it was working fine until I moved my
mouse over to the right and opened up the taskbar. As soon as it opened the
taskbar, it failed.
I think I’m going to go ahead and build a test program that I hope will
exhibit the same issues.
Jim
(io-net failure)
I’ve got some code that demonstrates this problem (on my machine at least).
Who do I need to send it to to have a look at it?
Thanks,
Jim
Please email it to me.
-seanb
Jim Lambert <jlambert@futurex.com> wrote:
: (io-net failure)
: I’ve got some code that demonstrates this problem (on my machine at least).
: Who do I need to send it to to have a look at it?
: Thanks,
: Jim