I recently installed an old version of QNX on my system and I had no
problems with the video. When it started up, it gave me the option of VGA
or VESA in the driver list and the VESA worked fine. But I couldn’t get my
ethernet card to work so I downloaded and installed a clean copy of QNX
6.1.0 and now the only option I can get is VGA at 640x480.
I have an STB Velocity 128 and I’m including the graphics-traplist and
graphics-modes files just in case.
I noticed other people were having problems with their Riva 128 cards and I
tried some of those solutions but they just don’t work for me. Any help?
Matt
begin 666 graphics-traplist.dat
M9&5V9W0M:6]G<F%P:&EC<R M9&QD979G+71N=“YS;R M23 @+60P>#$R9#(L
M,’@P,#$X"F1E=F=T+6EO9W)A<&AI8W,@+61L9&5V9RUV97-A8FEO<RYS;R M
323 @+60P>#$R9#(L,’@P,#$X”@``
`
end
begin 666 graphics-modes.dat
M:6\M9W)A<&AI8W,@+6V-#!X-#@P#@@+61L9&5V9RUV9V$N<V@+5!V9V$T
M+G!A;#LC-C0P+#0X,"PT+#$P,“PP+‘9G82 M(’-A9F4@;6]D90II;RUG<F%P
M:&EC<R M9&QD979G+79G82YS;R M9S8T,’@T.#!X.” M4’9G830N<&%L.R,V
M-# L-#@P+#0L,3 P+# L=F=A(“T@<V%F92!M;V1E"B,@8VAE8VMS=6T@,3(Y
'(#0S(#4V”@``
`
end
It is obvious that many NVIDIA based cards do not get recognised by QNX 6.0
and 6.1. The devgt-iographics command crashes when trying to recognise the
NVIDIA card (I have a TNT). Problem is, it then also crashes trying to
verify the VESA mode. Exit Photon to the console mode and run crttrap to see
what I mean. The solution is to remove the first line from the traplist
file. The vesa mode will then become available after a re-boot. I wish this
problem could get solved though… 6.1 is worse than 6.0.
Dirk
Matthew Isaacs wrote in message <9jau2f$3v8$2@inn.qnx.com>…
I recently installed an old version of QNX on my system and I had no
problems with the video. When it started up, it gave me the option of VGA
or VESA in the driver list and the VESA worked fine. But I couldn’t get my
ethernet card to work so I downloaded and installed a clean copy of QNX
6.1.0 and now the only option I can get is VGA at 640x480.
I have an STB Velocity 128 and I’m including the graphics-traplist and
graphics-modes files just in case.
I noticed other people were having problems with their Riva 128 cards and I
tried some of those solutions but they just don’t work for me. Any help?
Matt
I have the same problem. I ended up changing my traplist to:
devgt-iographics -dldevg-tnt.so -I0
devgt-iographics -dldevg-vesabios.so -I0
(removed -d option, from my ‘enum-pci’ it appeared that the -d option values
were correct) which allowed my to use ‘crttrap trap’ to get the
graphics-modes file filled with valid modes for the tnt, vesa, and vga.
Unfortunately the tnt modes do not work but the vesa one do. So that’s what
I’ve been using.
However, I need to do this every time I boot up. It doesn’t appear to stick
when I do this. I tried to substitute the ‘-d0x12d2,0x0018’ in the
graphics-modes file. but this didn’t help.
Carey Duran
Thanks for the suggestions! They worked…although I had to alter the
method a little bit…first, I ran the crttrap clear to get rid of the
graphics-modes file, then edited the graphics-traplist file to remove the
tnt entry and remove the -d option from the vesa line. After saving the
graphics-traplist file, I chmod the permissions to 444 and then rebooted.
The OS went right into the VESA driver. I’ve rebooted three times and
booted into Win2k and then back into QNX and the driver stays the same every
time. I don’t have to keep editing the file.
Again, thanks for the suggestion…the desktop looks freakin’ great with
millions of colors instead of those damn EGA crap graphics…
“Carey Duran” <cduran@harscotrack.com> wrote in message
news:9jh700$nr2$1@inn.qnx.com…
I have the same problem. I ended up changing my traplist to:
devgt-iographics -dldevg-tnt.so -I0
devgt-iographics -dldevg-vesabios.so -I0
(removed -d option, from my ‘enum-pci’ it appeared that the -d option
values
were correct) which allowed my to use ‘crttrap trap’ to get the
graphics-modes file filled with valid modes for the tnt, vesa, and vga.
Unfortunately the tnt modes do not work but the vesa one do. So that’s
what
I’ve been using.
However, I need to do this every time I boot up. It doesn’t appear to
stick
when I do this. I tried to substitute the ‘-d0x12d2,0x0018’ in the
graphics-modes file. but this didn’t help.
Carey Duran