Riva TNT only works in VGA and VESA mode

I have been trying to get a TNT card to work with RTP patch A (and also
before patch A). When I run crttrap trap I get:

/usr/bin/photon/bin/devgt-iographics -dldevg-tnt.so -I0 -d0x10de,0x0020
mode switcher init: Bad file descriptor
/usr/bin/photon/bin/devgt-iographics -dldevg-vesabios.so -I0 -d0x10de,0x0020
crttrap: wrote config file as /etc/system/config/graphics-modes

When I look at the graphics-modes files I of course have only vesa modes
because the TNT driver is failing.

I tried running devgt-iographics in verbose mode to see what was happening
with the TNT driver, here is what I get:

VGA primary: bus 0x1 dev/func 0x0
Found 1 PCI/AGP display devices
PCI attatch device failed!
Primary active: 1 0 807
mode switcher init: Bad file descriptor

First of all the TNT is a AGP card, maybe the RTP doesn’t support AGP? I
tried moving all my PCI cards around, sometimes that fixes things in
Windoze, but I still get the same problems. I can’t think of anything else
to try I guess I’m stuck using the SLOW VESA modes (ugh the terminal is
really slow in photon, when I compile stuff I have to minimize it just to
speed up the compile). Anyone seen this problem before, and if so is there
any way to fix it?

Shane Warren

I also have a Riva TNT AGP card and I’m having the exact same problem.

If only someone could help, please, please, pretty please. :slight_smile:


Bye,
Jurgen

Gyro,

I got my TNT to work, but this is a really strange way to do it…

I downloaded the RTP Patch A and had it installed. Of course I was still
having the same problem, the TNT would not work except in VGA/Vesa modes. I
tried about a billion different things, from moving cards around to yelling
at my computer (none very productive), then I stared trying really bizarre
things…

I started the package manager in photon and viewed my current packages. Then
I looked at my User Repository, from there I went to the QNX Realtime
Platform/Applications/X Photon Patch A. For some reason X Photon Patch A was
disabled, so I enabled it and then went back out of photon
(CTL-ALT-SHIFT-DEL). Now I ran crttrap trap and WHOAH it talked to my TNT
and gave me modes. Then I typed ph and I was then allowed to choose the TNT
in accelerated mode!!

Ok now here’s the REALLY strange part. The next time I droppped out of
photon and tried to type ph to get back in, it said the same error as before
DOH! But alas, the little trick of (this time) deactivating the X Photon
Patch A, and then redoing crttrap trap worked again.
This is very puzzling what does enabling X Photon Patch A have to do with my
TNT card? If any of you QNX guys are reading this, what is going on here? I
guesss I’m just happy to have the TNT in accelerated mode (the VESA mode
sucks bad, I mean really bad) for now anyway.

Shane


“Gyro” <jurgen.blok@iae.nl> wrote in message
news:95pou7$gf8$1@inn.qnx.com

I also have a Riva TNT AGP card and I’m having the exact same problem.

If only someone could help, please, please, pretty please. > :slight_smile:


Bye,
Jurgen
\

Hello Shane,

I’m glad you got your TNT to work with this strange solution, but it didn’t
work for me :frowning:

My Patch A was enabled and I can enable/disable what I want and run crttrap
a million times, but I still get “Bad file descriptor”

Shouting at the computer does help by the way …


It releives.


Let’s hope the guys QNX will come up with a solution that will work…SOON!
:wink:


Bye,
Jurgen

Gyro <jurgen.blok@iae.nl> wrote:

Hello Shane,

I’m glad you got your TNT to work with this strange solution, but it didn’t
work for me > :frowning:

My Patch A was enabled and I can enable/disable what I want and run crttrap
a million times, but I still get “Bad file descriptor”

Alrighty then, lets get to the bottom of this…

First of all, try this:
run “crttrap trap”
Edit /etc/system/config/graphics-modes, and grab one of the mode lines
that has “vesabios” in it. Place this line at the top of the file, then
replace “vesabios” with “tnt”.

Try starting “ph”. If this doesn’t work, then at least we’ve eliminated
the trapping process, in which case I can send you a debug tnt driver to try.

Shouting at the computer does help by the way …



It releives.



Let’s hope the guys QNX will come up with a solution that will work…SOON!
:wink:


Bye,
Jurgen

David Donohoe <ddonohoe@qnx.com> wrote:

Gyro <> jurgen.blok@iae.nl> > wrote:
Hello Shane,

I’m glad you got your TNT to work with this strange solution, but it didn’t
work for me > :frowning:

My Patch A was enabled and I can enable/disable what I want and run crttrap
a million times, but I still get “Bad file descriptor”

Alrighty then, lets get to the bottom of this…

First of all, try this:
run “crttrap trap”
Edit /etc/system/config/graphics-modes, and grab one of the mode lines
that has “vesabios” in it. Place this line at the top of the file, then
replace “vesabios” with “tnt”.

Try starting “ph”. If this doesn’t work, then at least we’ve eliminated
the trapping process, in which case I can send you a debug tnt driver to try.

Oh, and by the way, do you see a message along the lines of
“Reserve RMEM failed” when the system boots?

Hello David,

Alrighty then, lets get to the bottom of this…

That would be great!

First of all, try this:
run “crttrap trap”
Edit /etc/system/config/graphics-modes, and grab one of the mode lines
that has “vesabios” in it. Place this line at the top of the file, then
replace “vesabios” with “tnt”.

Try starting “ph”. If this doesn’t work, then at least we’ve eliminated
the trapping process, in which case I can send you a debug tnt driver to
try.

If tried tried it and when I start “ph” it says:

Mode_init: Bad file descriptor
devi-hirun kbd fd -d/dev/kbd ps kb -2

and won’t load any further and basically, errr, hangs :wink:

Oh, and by the way, do you see a message along the lines of
“Reserve RMEM failed” when the system boots?

Yes, it’s the second line I see when I boot.

Thanks,

Bye,
Jurgen

Gyro <jurgen.blok@iae.nl> wrote:

Oh, and by the way, do you see a message along the lines of
“Reserve RMEM failed” when the system boots?

Yes, it’s the second line I see when I boot.

Ahh… it sounds like a bug in pci-bios which we fixed, but it
didn’t make the last patch.

You might be able to work around it by playing with BIOS settings,
inserting/removing PCI cards, moving cards around in their slots
etc.

“David Donohoe” <ddonohoe@qnx.com> wrote in message
news:95uovb$o8t$1@nntp.qnx.com

David Donohoe <> ddonohoe@qnx.com> > wrote:
Gyro <> jurgen.blok@iae.nl> > wrote:
Hello Shane,

I’m glad you got your TNT to work with this strange solution, but it
didn’t
work for me > :frowning:

My Patch A was enabled and I can enable/disable what I want and run
crttrap
a million times, but I still get “Bad file descriptor”

Alrighty then, lets get to the bottom of this…

First of all, try this:
run “crttrap trap”
Edit /etc/system/config/graphics-modes, and grab one of the mode lines
that has “vesabios” in it. Place this line at the top of the file, then
replace “vesabios” with “tnt”.

Try starting “ph”. If this doesn’t work, then at least we’ve eliminated
the trapping process, in which case I can send you a debug tnt driver to
try.

Oh, and by the way, do you see a message along the lines of
“Reserve RMEM failed” when the system boots?

First:

Yes, I started getting that exact message after I installed patch A.

Also:

I tried replacing the vesabios driver with the tnt driver while in photon,
and I get a lockup, until I hit ctl-atl-shift-del to kill photon. If you
need me to try anything else just tell me.

Thanks

Shane

Hello David,

Oh, and by the way, do you see a message along the lines of
“Reserve RMEM failed” when the system boots?

Yes, it’s the second line I see when I boot.

Ahh… it sounds like a bug in pci-bios which we fixed, but it
didn’t make the last patch.

You might be able to work around it by playing with BIOS settings,
inserting/removing PCI cards, moving cards around in their slots
etc.

Nah, I played around long enough as it is and I have absolutly no intention
to spend more time finding a workaround. I think I just save my sanity and
wait for the next patch and try it again then.

Thanks for your time anyway!

Bye,
Jurgen