Drivers for newer hardware

I am trying to move my QNX development over to a newer PC. There are two
pieces of hardware that do not seem to have hardware support. The
motherboard has the new nVidia nForce2 chipset.

FIrst, this means the on-board ethernet MAC is actually in the nVidia south
bridge chip. QNX doesn’t seem to talk to this ethernet port – any plans to
support it?

The second device that is a problem is the video. It is an integrated
graphics processor (part of hte nForce2 chipset) that looks like an nVidia
GeForce4 MX. Is there any way to take the current QNX video drivers for the
GeForce3 and fool it into supporting the newer chip? Currently I am limited
to 800x600 resolution using the VESA driver.

Thanx for any help.
Dave G.

The second device that is a problem is the video. It is an integrated
graphics processor (part of hte nForce2 chipset) that looks like an nVidia
GeForce4 MX. Is there any way to take the current QNX video drivers for the
GeForce3 and fool it into supporting the newer chip? Currently I am limited
to 800x600 resolution using the VESA driver.

Unfortunatly, Nvidia doesn’t provide documentation for thier chipsets. So
unless that policy changes/has changed, you won’t see support.

chris


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

Dave G. <~~~dkg@ormec.com> wrote:

The second device that is a problem is the video. It is an integrated
graphics processor (part of hte nForce2 chipset) that looks like an nVidia
GeForce4 MX. Is there any way to take the current QNX video drivers for the
GeForce3 and fool it into supporting the newer chip? Currently I am limited
to 800x600 resolution using the VESA driver.

If you want to run X, I believe XFree86 4.3 supports it.
Check out sf.net/projects/openqnx for qnx binaries.

And yet, somehow the QSSL website shows support for nVidia graphics
processors up to GeForce2 and it shows the devg-tnt.so driver is the one to
use. So, how do I try that with my GeForce4 chipset just to see if I can
get beyond 800x600?

Dave G.

“Chris McKillop” <cdm@qnx.com> wrote in message
news:b9q5c8$6cp$1@nntp.qnx.com

The second device that is a problem is the video. It is an integrated
graphics processor (part of hte nForce2 chipset) that looks like an
nVidia
GeForce4 MX. Is there any way to take the current QNX video drivers for
the
GeForce3 and fool it into supporting the newer chip? Currently I am
limited
to 800x600 resolution using the VESA driver.


Unfortunatly, Nvidia doesn’t provide documentation for thier chipsets. So
unless that policy changes/has changed, you won’t see support.

chris


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

Unfortunately, I need to run the self-hosted IDE under Photon.
Dave G.

<fliu@mail.vipstage.com> wrote in message news:b9rcdu$ito$1@inn.qnx.com

Dave G. <~~~> dkg@ormec.com> > wrote:
The second device that is a problem is the video. It is an integrated
graphics processor (part of hte nForce2 chipset) that looks like an
nVidia
GeForce4 MX. Is there any way to take the current QNX video drivers for
the
GeForce3 and fool it into supporting the newer chip? Currently I am
limited
to 800x600 resolution using the VESA driver.

If you want to run X, I believe XFree86 4.3 supports it.
Check out sf.net/projects/openqnx for qnx binaries.

Dave G. <~~~dkg@ormec.com> wrote:

And yet, somehow the QSSL website shows support for nVidia graphics
processors up to GeForce2 and it shows the devg-tnt.so driver is the one to
use. So, how do I try that with my GeForce4 chipset just to see if I can
get beyond 800x600?

Which is correct. But devg-tnt will not work with cards past the GeForce2.
But unfortunatly without docs that situation will not change. Is this in
a laptop? If not, could you possibly get a card from a better supported
chipset maker (like ATi)?

chris


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

This is a compact box made by Shuttle which has everything on an ITX
motherboard. They did provide an AGP slot so I could find another graphics
card at least for development. For putting this into a production
environment, we really do not want the extra cost of a video card so we
might have to chose another model.

More of an immediate issue is the fact the onboard Ethernet port is not
supported. This box has one PCI slot and I need it for other purposes
during development. Right now I have an Ethernet NIC in that slot because
QNX doesn’t recognize the onboard Ethernet. I’m pretty sure the onboard
Ethernet looks like a Realtek chip but it is being enumerated as part of the
nVidia chipset. Is there a way to force QNX into trying an ethernet driver
even though the startup scan didn’t recognize the hardware?

On a related question: the Ethernet NIC I have in the PCI slot right now is
a 10/100Mbps 3COM board. The ifconfig report shows under media that it is
an Ethernet 10baseT half-duplex device. I am suspicious that QNX is not
configuring the hardware to run at 100Mb (slow breakpoint processing in
remote debugging) and was wondering if ifconfig is reporting accurately and
if there is a way to change that.

Thanx,
Dave G.

“Chris McKillop” <cdm@qnx.com> wrote in message
news:b9sccv$o6s$1@nntp.qnx.com

Dave G. <~~~> dkg@ormec.com> > wrote:
And yet, somehow the QSSL website shows support for nVidia graphics
processors up to GeForce2 and it shows the devg-tnt.so driver is the one
to
use. So, how do I try that with my GeForce4 chipset just to see if I
can
get beyond 800x600?


Which is correct. But devg-tnt will not work with cards past the
GeForce2.
But unfortunatly without docs that situation will not change. Is this in
a laptop? If not, could you possibly get a card from a better supported
chipset maker (like ATi)?

chris


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

More of an immediate issue is the fact the onboard Ethernet port is not
supported. This box has one PCI slot and I need it for other purposes
during development. Right now I have an Ethernet NIC in that slot because
QNX doesn’t recognize the onboard Ethernet. I’m pretty sure the onboard
Ethernet looks like a Realtek chip but it is being enumerated as part of the
nVidia chipset. Is there a way to force QNX into trying an ethernet driver
even though the startup scan didn’t recognize the hardware?

slay io-net
io-net -d rtl vid=0x…,did=0x…,verbose=10

Where vid and did are the pci vendor and device ids. You can get them from
the output of the “pci” utility.

chris


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

FYI: didn’t work. Oh well.

Dave G.

“Chris McKillop” <cdm@qnx.com> wrote in message
news:b9u2p8$rch$1@nntp.qnx.com

More of an immediate issue is the fact the onboard Ethernet port is not
supported. This box has one PCI slot and I need it for other purposes
during development. Right now I have an Ethernet NIC in that slot
because
QNX doesn’t recognize the onboard Ethernet. I’m pretty sure the onboard
Ethernet looks like a Realtek chip but it is being enumerated as part of
the
nVidia chipset. Is there a way to force QNX into trying an ethernet
driver
even though the startup scan didn’t recognize the hardware?


slay io-net
io-net -d rtl vid=0x…,did=0x…,verbose=10

Where vid and did are the pci vendor and device ids. You can get them
from
the output of the “pci” utility.

chris


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