problem with networking on Dell Optiplex GX260 with intel 82

Well,

We just got a new batch of Dells in, and I was installing Qnx on them, and
noticed… They don’t recognize the network adapter…#@!!

I looked at the adapter with pci -v:

Vendor=8086=intel
Device=100e=unknown,unknown

I went to the enum files in /etc/system/enum/devices/net, and …

It shows up in the list, and calls for the driver:

/lib/dll/devn-i82544.so

but…

I can’t seem to find that driver on the system after the install.

Is the file missing???
Is the name wrong???

Windows recognises the card and does fine with it.

Any ideas??

Thanks,

John

John Eddy <john.h.eddy@lmco.com> wrote:

Well,

We just got a new batch of Dells in, and I was installing Qnx on them, and
noticed… They don’t recognize the network adapter…#@!!

I looked at the adapter with pci -v:

Vendor=8086=intel
Device=100e=unknown,unknown

I went to the enum files in /etc/system/enum/devices/net, and …

It shows up in the list, and calls for the driver:

/lib/dll/devn-i82544.so

but…

I can’t seem to find that driver on the system after the install.

Is the file missing???
Is the name wrong???

If the file /lib/dll/devn-i82544.so is not present, then there must
be some kind of packaging/installation problem.

Note that there was a problem with the driver whereby an error
message would be printed even though the driver was running
correctly. This error message can be ignored. Run ‘nicinfo’
or ifconfig -a to see if the driver is actually running.

What version of the OS are you running, BTW?

Cheers,
Dave

David,

I don’t see it. I will try to look over the install disk again (when I can
find it… I know it was around here somewhere…). There was only one disk
in release 6.21 SE, right?? At least thats all I remember seeing.

This machine has several versions on it, from 6.1 non-commercial to 6.2 SE.
I had installed them as root.qfs files in the fat32 partition that windows
sees, and either select which to boot from config.sys/autoexec.bat menu
(using loadqnx.sys from config.sys, or loadsys loadqnx.sys from
autoexec.bat) or modify altboot and directory names manually.

Since this is a new machine (they took my old one away, and upgraded me), I
figured I had the best chance with the newest version, so I was lookint at
6.21 SE.

Should I download a copy of what is on the website instead of using the ver
6.21 SE that QNX sent us?

Thanks,

John


“David Donohoe” <ddonohoe@qnx.com> wrote in message
news:b8759v$q97$1@nntp.qnx.com

John Eddy <> john.h.eddy@lmco.com> > wrote:
Well,

We just got a new batch of Dells in, and I was installing Qnx on them,
and
noticed… They don’t recognize the network adapter…#@!!

I looked at the adapter with pci -v:

Vendor=8086=intel
Device=100e=unknown,unknown

I went to the enum files in /etc/system/enum/devices/net, and …

It shows up in the list, and calls for the driver:

/lib/dll/devn-i82544.so

but…

I can’t seem to find that driver on the system after the install.

Is the file missing???
Is the name wrong???

If the file /lib/dll/devn-i82544.so is not present, then there must
be some kind of packaging/installation problem.

Note that there was a problem with the driver whereby an error
message would be printed even though the driver was running
correctly. This error message can be ignored. Run ‘nicinfo’
or ifconfig -a to see if the driver is actually running.

What version of the OS are you running, BTW?

Cheers,
Dave

Dave,

Ok, I found the official disks we got from QNX and it turns out we have
6.2.1 SE and PE. I looked throught the respositories for SE, and found
drivers in

os-drivers-2-1-3-x86-qnx.qpk
the SE disk also had
os-se-drivers-2-1-3-x86-qnx.qpk
but no devn drivers in that section
the PE disk also had
os-pe-drivers-2.1.4-x86-qnx.qpk
THIS file contained devn-i82544.so!!!

WHY IS AN EXECUTABLE FOR A NETWORK DRIVER ONLY AVAIABLE ON THE PROFESSIONAL
VERSION OF THE OPERATING SYSTEM???

I don’t have such an exotic system. It is an off the shelf dell optiplex
gx-260. And the built in ethernet uses this chipset.

I can see why the driver development kit (source) might not be in the low
cost versions of the operating system, but why would the driver executables
be left out??? I would expect the latest batch of driver executables to be
available for even the non-commercial version.

Thanks,

John



“John Eddy” <john.h.eddy@lmco.com> wrote in message
news:b8lmgt$gou$1@inn.qnx.com

David,

I don’t see it. I will try to look over the install disk again (when I can
find it… I know it was around here somewhere…). There was only one
disk
in release 6.21 SE, right?? At least thats all I remember seeing.

This machine has several versions on it, from 6.1 non-commercial to 6.2
SE.
I had installed them as root.qfs files in the fat32 partition that windows
sees, and either select which to boot from config.sys/autoexec.bat menu
(using loadqnx.sys from config.sys, or loadsys loadqnx.sys from
autoexec.bat) or modify altboot and directory names manually.

Since this is a new machine (they took my old one away, and upgraded me),
I
figured I had the best chance with the newest version, so I was lookint at
6.21 SE.

Should I download a copy of what is on the website instead of using the
ver
6.21 SE that QNX sent us?

Thanks,

John


“David Donohoe” <> ddonohoe@qnx.com> > wrote in message
news:b8759v$q97$> 1@nntp.qnx.com> …
John Eddy <> john.h.eddy@lmco.com> > wrote:
Well,

We just got a new batch of Dells in, and I was installing Qnx on them,
and
noticed… They don’t recognize the network adapter…#@!!

I looked at the adapter with pci -v:

Vendor=8086=intel
Device=100e=unknown,unknown

I went to the enum files in /etc/system/enum/devices/net, and …

It shows up in the list, and calls for the driver:

/lib/dll/devn-i82544.so

but…

I can’t seem to find that driver on the system after the install.

Is the file missing???
Is the name wrong???

If the file /lib/dll/devn-i82544.so is not present, then there must
be some kind of packaging/installation problem.

Note that there was a problem with the driver whereby an error
message would be printed even though the driver was running
correctly. This error message can be ignored. Run ‘nicinfo’
or ifconfig -a to see if the driver is actually running.

What version of the OS are you running, BTW?

Cheers,
Dave