Anyone had any luck with QNX4 and the GX or GZ variants of the INTEL 82562
10/100 LAN chipset. I tried Net.ether82557 (as indicated on ther website
for the 82562(no GX, no GZ)) but it comes up with:
rInit: Unable to locate adapter.
I tried setting the -D with the PCI device ID but it didn’t help. The PCI
info for the device is 8086h (INTEL), device=27DCh.
Thanks.
–
Allan Williams
Got it working if I added the -V 8086 parameter as well. Apparently if you
specify -D you must also specify -V (it doesn’t use the default?).
–
Allan Williams
“Al Williams” <sysadm@harding.ca> wrote in message
news:eqg1mh$8ka$1@inn.qnx.com…
Anyone had any luck with QNX4 and the GX or GZ variants of the INTEL 82562
10/100 LAN chipset. I tried Net.ether82557 (as indicated on ther website
for the 82562(no GX, no GZ)) but it comes up with:rInit: Unable to locate adapter.
I tried setting the -D with the PCI device ID but it didn’t help. The PCI
info for the device is 8086h (INTEL), device=27DCh.Thanks.
–
Allan Williams
\
One strange thing I’ve noticed with this driver. I ran it with the -v
option for tetsing and have it plugged in to a Ethernet switch. The funny
thing is the link keeps going up and down. I get Speedo: Link Down /
Speedo: Link up messages fairly often. I’ve changed the cable/switch and
don’t see any problems on the switch LED’s - the link just seems to go up
and down on it’s own. I used the -s 100 option to set the speed, so it
should not be negotiating.
Anyone seen this?
The Net.ether82557 driver I’m using is from 2005, not sure if there is a
newer one.
–
Allan Williams
“Al Williams” <sysadm@harding.ca> wrote in message
news:eqg61j$b5c$1@inn.qnx.com…
Got it working if I added the -V 8086 parameter as well. Apparently if
you specify -D you must also specify -V (it doesn’t use the default?).–
Allan Williams
“Al Williams” <> sysadm@harding.ca> > wrote in message
news:eqg1mh$8ka$> 1@inn.qnx.com> …
Anyone had any luck with QNX4 and the GX or GZ variants of the INTEL
82562 10/100 LAN chipset. I tried Net.ether82557 (as indicated on ther
website for the 82562(no GX, no GZ)) but it comes up with:rInit: Unable to locate adapter.
I tried setting the -D with the PCI device ID but it didn’t help. The
PCI info for the device is 8086h (INTEL), device=27DCh.Thanks.
–
Allan Williams
\
FYI: It only does this if you use the -s option. It seems to work fine
without -s though (unlike some drivers like the RTL one which seem to
need -s to hanlde startupo without cables plugged in).
–
Allan Williams
“Al Williams” <sysadm@harding.ca> wrote in message
news:eqi5st$nkc$1@inn.qnx.com…
One strange thing I’ve noticed with this driver. I ran it with the -v
option for tetsing and have it plugged in to a Ethernet switch. The funny
thing is the link keeps going up and down. I get Speedo: Link Down /
Speedo: Link up messages fairly often. I’ve changed the cable/switch and
don’t see any problems on the switch LED’s - the link just seems to go up
and down on it’s own. I used the -s 100 option to set the speed, so it
should not be negotiating.Anyone seen this?
The Net.ether82557 driver I’m using is from 2005, not sure if there is a
newer one.–
Allan Williams
“Al Williams” <> sysadm@harding.ca> > wrote in message
news:eqg61j$b5c$> 1@inn.qnx.com> …
Got it working if I added the -V 8086 parameter as well. Apparently if
you specify -D you must also specify -V (it doesn’t use the default?).–
Allan Williams
“Al Williams” <> sysadm@harding.ca> > wrote in message
news:eqg1mh$8ka$> 1@inn.qnx.com> …
Anyone had any luck with QNX4 and the GX or GZ variants of the INTEL
82562 10/100 LAN chipset. I tried Net.ether82557 (as indicated on ther
website for the 82562(no GX, no GZ)) but it comes up with:rInit: Unable to locate adapter.
I tried setting the -D with the PCI device ID but it didn’t help. The
PCI info for the device is 8086h (INTEL), device=27DCh.Thanks.
–
Allan Williams
\