I encountered the following problem:
When I boot my QNX and start any kind of tcp operations, self written as
well as the included ftp-server, the net data transfer rate yields somewhere
in a 3-15kBit/s transfer rate for up/download.
However, if I turn the hub/switch, the QNX computer is connected to, on and
off again after the GUI has started, or simply turn the hub/switch on after
the GUI is started the network perfomance is as expected on a 100MBit
Ethernet.
Besides starting the hub/switch delayed, is there any solution to solve this
issue and does anyone the source of the problem.
Suggestions appreciated,
Marcus Daiber
Which ethernet driver are you using? The 6.1 ethernet drivers are
notoriously poor at guessing the hub/switch media rate and duplex. When
the driver guesses wrong, one of the symptoms could be a low transfer
rate. When you power cycle the hub/switch, the driver gets a chance
to guess again – this time it may guess correctly. I think this
could be the source of this problem.
The work-a-round would be to hard code the media rate and duplex you
want the ethernet driver to use, using driver command line args – but
most of the 6.1 ethernet drivers don’t correctly implement this
functionality.
I would contact your QSSL sales representative and ask when a new
release of ethernet drivers can be expected.
Marcus Daiber <mdaiber@ziimaging.com> wrote:
I encountered the following problem:
When I boot my QNX and start any kind of tcp operations, self written as
well as the included ftp-server, the net data transfer rate yields somewhere
in a 3-15kBit/s transfer rate for up/download.
However, if I turn the hub/switch, the QNX computer is connected to, on and
off again after the GUI has started, or simply turn the hub/switch on after
the GUI is started the network perfomance is as expected on a 100MBit
Ethernet.
Besides starting the hub/switch delayed, is there any solution to solve this
issue and does anyone the source of the problem.
Suggestions appreciated,
Marcus Daiber
–
Kirk Russell Bridlewood Software Testers Guild
Well,
I tried to work with the driver myself since I needed the MTU changed, which
is a different issue, however, I use the speedo driver and hardcoded the
100MBIT through slaying during runtime as well as putting it in the config
files, the data rate remains slow, until I physically turn off the hub or
switch whichever it is connected to.
Thank you,
Marcus
“kirk” <kirussel@NOSPAMrogers.com> wrote in message
news:a8qkgj$hob$1@inn.qnx.com…
Which ethernet driver are you using? The 6.1 ethernet drivers are
notoriously poor at guessing the hub/switch media rate and duplex. When
the driver guesses wrong, one of the symptoms could be a low transfer
rate. When you power cycle the hub/switch, the driver gets a chance
to guess again – this time it may guess correctly. I think this
could be the source of this problem.The work-a-round would be to hard code the media rate and duplex you
want the ethernet driver to use, using driver command line args – but
most of the 6.1 ethernet drivers don’t correctly implement this
functionality.I would contact your QSSL sales representative and ask when a new
release of ethernet drivers can be expected.Marcus Daiber <> mdaiber@ziimaging.com> > wrote:
I encountered the following problem:
When I boot my QNX and start any kind of tcp operations, self written as
well as the included ftp-server, the net data transfer rate yields
somewhere
in a 3-15kBit/s transfer rate for up/download.
However, if I turn the hub/switch, the QNX computer is connected to, on
and
off again after the GUI has started, or simply turn the hub/switch on
after
the GUI is started the network perfomance is as expected on a 100MBit
Ethernet.
Besides starting the hub/switch delayed, is there any solution to solve
this
issue and does anyone the source of the problem.
Suggestions appreciated,
Marcus Daiber–
Kirk Russell Bridlewood Software Testers Guild
Speedo is notorious for the auto-detection stuff. Download the fixed speedo
driver off of the developer site and your problems will likely disappear.
http://developers.qnx.com
-Warren “Speedo = Bad (in almost ever case!)” Peece
“Marcus Daiber” <mdaiber@gmx.net> wrote in message
news:a8qp67$kgd$1@inn.qnx.com…
Well,
I tried to work with the driver myself since I needed the MTU changed,
which
is a different issue, however, I use the speedo driver and hardcoded the
100MBIT through slaying during runtime as well as putting it in the config
files, the data rate remains slow, until I physically turn off the hub or
switch whichever it is connected to.Thank you,
Marcus
“kirk” <> kirussel@NOSPAMrogers.com> > wrote in message
news:a8qkgj$hob$> 1@inn.qnx.com> …
Which ethernet driver are you using? The 6.1 ethernet drivers are
notoriously poor at guessing the hub/switch media rate and duplex. When
the driver guesses wrong, one of the symptoms could be a low transfer
rate. When you power cycle the hub/switch, the driver gets a chance
to guess again – this time it may guess correctly. I think this
could be the source of this problem.The work-a-round would be to hard code the media rate and duplex you
want the ethernet driver to use, using driver command line args – but
most of the 6.1 ethernet drivers don’t correctly implement this
functionality.I would contact your QSSL sales representative and ask when a new
release of ethernet drivers can be expected.Marcus Daiber <> mdaiber@ziimaging.com> > wrote:
I encountered the following problem:
When I boot my QNX and start any kind of tcp operations, self written
as
well as the included ftp-server, the net data transfer rate yields
somewhere
in a 3-15kBit/s transfer rate for up/download.
However, if I turn the hub/switch, the QNX computer is connected to,
on
and
off again after the GUI has started, or simply turn the hub/switch on
after
the GUI is started the network perfomance is as expected on a 100MBit
Ethernet.
Besides starting the hub/switch delayed, is there any solution to
solve
this
issue and does anyone the source of the problem.
Suggestions appreciated,
Marcus Daiber–
Kirk Russell Bridlewood Software Testers Guild
Hi,
Do you know the exact link of the driver?.Or if you have already
downloaded it ,i would like to have a copy of that. The closest i see in
developers.qnx.com is that they are in the process of fixing the driver(It
is dated June 28 2001).I am sure that there should be a tested driver by
now.
Thanks,
Sreekanth
“Warren Peece” <Warren@NoSpam.com> wrote in message
news:a8vi9k$6q2$1@inn.qnx.com…
Speedo is notorious for the auto-detection stuff. Download the fixed
speedo
driver off of the developer site and your problems will likely disappear.
http://developers.qnx.com-Warren “Speedo = Bad (in almost ever case!)” Peece
“Marcus Daiber” <> mdaiber@gmx.net> > wrote in message
news:a8qp67$kgd$> 1@inn.qnx.com> …
Well,
I tried to work with the driver myself since I needed the MTU changed,
which
is a different issue, however, I use the speedo driver and hardcoded the
100MBIT through slaying during runtime as well as putting it in the
config
files, the data rate remains slow, until I physically turn off the hub
or
switch whichever it is connected to.Thank you,
Marcus
“kirk” <> kirussel@NOSPAMrogers.com> > wrote in message
news:a8qkgj$hob$> 1@inn.qnx.com> …Which ethernet driver are you using? The 6.1 ethernet drivers are
notoriously poor at guessing the hub/switch media rate and duplex.
When
the driver guesses wrong, one of the symptoms could be a low transfer
rate. When you power cycle the hub/switch, the driver gets a chance
to guess again – this time it may guess correctly. I think this
could be the source of this problem.The work-a-round would be to hard code the media rate and duplex you
want the ethernet driver to use, using driver command line args – but
most of the 6.1 ethernet drivers don’t correctly implement this
functionality.I would contact your QSSL sales representative and ask when a new
release of ethernet drivers can be expected.Marcus Daiber <> mdaiber@ziimaging.com> > wrote:
I encountered the following problem:
When I boot my QNX and start any kind of tcp operations, self
written
as
well as the included ftp-server, the net data transfer rate yields
somewhere
in a 3-15kBit/s transfer rate for up/download.
However, if I turn the hub/switch, the QNX computer is connected to,
on
and
off again after the GUI has started, or simply turn the hub/switch
on
after
the GUI is started the network perfomance is as expected on a
100MBit
Ethernet.
Besides starting the hub/switch delayed, is there any solution to
solve
this
issue and does anyone the source of the problem.
Suggestions appreciated,
Marcus Daiber–
Kirk Russell Bridlewood Software Testers Guild
\
Ok…I found the fix. it is at http://developers.qnx.com/Fixes/Software . But
here is my problem.When i read the devn-speedo.readme.It says Due to a bug
in multicast enabling so multicast has been disabled.I need multicast
support in my driver so…this driver is practically unusable for me.Also the
date on the driver says it was built on Aug 9 2001.Does anybody know if
there is a later version of the driver available?
Thanks
Sreekanth
“Sreekanth” <sreekanth@cambira.com> wrote in message
news:a9066u$jha$1@inn.qnx.com…
Hi,
Do you know the exact link of the driver?.Or if you have already
downloaded it ,i would like to have a copy of that. The closest i see in
developers.qnx.com is that they are in the process of fixing the driver(It
is dated June 28 2001).I am sure that there should be a tested driver by
now.Thanks,
Sreekanth
“Warren Peece” <> Warren@NoSpam.com> > wrote in message
news:a8vi9k$6q2$> 1@inn.qnx.com> …
Speedo is notorious for the auto-detection stuff. Download the fixed
speedo
driver off of the developer site and your problems will likely
disappear.
http://developers.qnx.com-Warren “Speedo = Bad (in almost ever case!)” Peece
“Marcus Daiber” <> mdaiber@gmx.net> > wrote in message
news:a8qp67$kgd$> 1@inn.qnx.com> …
Well,
I tried to work with the driver myself since I needed the MTU changed,
which
is a different issue, however, I use the speedo driver and hardcoded
the
100MBIT through slaying during runtime as well as putting it in the
config
files, the data rate remains slow, until I physically turn off the hub
or
switch whichever it is connected to.Thank you,
Marcus
“kirk” <> kirussel@NOSPAMrogers.com> > wrote in message
news:a8qkgj$hob$> 1@inn.qnx.com> …Which ethernet driver are you using? The 6.1 ethernet drivers are
notoriously poor at guessing the hub/switch media rate and duplex.
When
the driver guesses wrong, one of the symptoms could be a low
transfer
rate. When you power cycle the hub/switch, the driver gets a chance
to guess again – this time it may guess correctly. I think this
could be the source of this problem.The work-a-round would be to hard code the media rate and duplex you
want the ethernet driver to use, using driver command line args –
but
most of the 6.1 ethernet drivers don’t correctly implement this
functionality.I would contact your QSSL sales representative and ask when a new
release of ethernet drivers can be expected.Marcus Daiber <> mdaiber@ziimaging.com> > wrote:
I encountered the following problem:
When I boot my QNX and start any kind of tcp operations, self
written
as
well as the included ftp-server, the net data transfer rate yields
somewhere
in a 3-15kBit/s transfer rate for up/download.
However, if I turn the hub/switch, the QNX computer is connected
to,
on
and
off again after the GUI has started, or simply turn the hub/switch
on
after
the GUI is started the network perfomance is as expected on a
100MBit
Ethernet.
Besides starting the hub/switch delayed, is there any solution to
solve
this
issue and does anyone the source of the problem.
Suggestions appreciated,
Marcus Daiber–
Kirk Russell Bridlewood Software Testers Guild
\