Problem S3 Trio V+

QNX Newsgroups (Archives) qdn.public.qnxrtp.newuser
1

Hi,

I have installed the QNXRTP on two computers, both of them have S3 Trio V+
video card.
One of them seemed to work fine till the first reboot, the other
had the same problem but it occured during the installation.
The computer i mentioned first, after the first reboot (it wasn’t shut down
with the power button :slight_smile:, didn’t display a correct screen, but a mess. Only
portions of the login window could be seen, and after the login i didn’t get
a usable screen either.
On the other computer i experienced the same phenomenon when i tried to
choose an appropriate colordepth/resolution during the installation. Only the
640*480/4c worked with the svga driver.

Any suggestion ?


Thanx

Ferenc

2

Could you post the output of pci -v so we can see
what your chip device ID is?

Ferenc Sarkozy <sarkozyf@freemail.c3.hu> wrote:

Hi,

I have installed the QNXRTP on two computers, both of them have S3 Trio V+
video card.
One of them seemed to work fine till the first reboot, the other
had the same problem but it occured during the installation.
The computer i mentioned first, after the first reboot (it wasn’t shut down
with the power button > :slight_smile:> , didn’t display a correct screen, but a mess. Only
portions of the login window could be seen, and after the login i didn’t get
a usable screen either.
On the other computer i experienced the same phenomenon when i tried to
choose an appropriate colordepth/resolution during the installation. Only the
640*480/4c worked with the svga driver.

Any suggestion ?



Thanx

Ferenc

3

Look at the thread “photon starts looking “weird” after a while” in
qdn.public.qnxrtp.photon . (From the end of September)

/ Jonathan

Ferenc Sarkozy wrote:

Hi,

I have installed the QNXRTP on two computers, both of them have S3 Trio V+
video card.
One of them seemed to work fine till the first reboot, the other
had the same problem but it occured during the installation.
The computer i mentioned first, after the first reboot (it wasn’t shut down
with the power button > :slight_smile:> , didn’t display a correct screen, but a mess. Only
portions of the login window could be seen, and after the login i didn’t get
a usable screen either.
On the other computer i experienced the same phenomenon when i tried to
choose an appropriate colordepth/resolution during the installation. Only the
640*480/4c worked with the svga driver.

Any suggestion ?

Thanx

Ferenc

4

Here is the output of the pci-v command:


PCI version = 2.10



Class = Bridge (Host/PCI)

Vendor ID = 8086h, Intel Corporation

Device ID = 1250h, 82439HX System Controller (TXC)

PCI index = 0h

Class Codes = 060000h

Revision ID = 3h

Bus number = 0

Device number = 0

Function num = 0

Status Reg = 2200h

Command Reg = 6h

Header type = 0h Single-function

BIST = 0h Build-in-self-test not supported

Latency Timer = 20h

Cache Line Size= 0h

Max Lat = 0ns

Min Gnt = 0ns

PCI Int Pin = NC

Interrupt line = 0



Class = Bridge (PCI/ISA)

Vendor ID = 8086h, Intel Corporation

Device ID = 7000h, 82371SB PIIX3 PCI-to-ISA Bridge (Triton II)

PCI index = 0h

Class Codes = 060100h

Revision ID = 1h

Bus number = 0

Device number = 7

Function num = 0

Status Reg = 280h

Command Reg = fh

Header type = 0h Multi-function

BIST = 0h Build-in-self-test not supported

Latency Timer = 0h

Cache Line Size= 0h

Max Lat = 0ns

Min Gnt = 0ns

PCI Int Pin = NC

Interrupt line = 0



Class = Mass Storage (IDE)

Vendor ID = 8086h, Intel Corporation

Device ID = 7010h, 82371SB PIIX3 IDE Interface (Triton II)

PCI index = 0h

Class Codes = 010180h

Revision ID = 0h

Bus number = 0

Device number = 7

Function num = 1

Status Reg = 280h

Command Reg = 5h

Header type = 0h Single-function

BIST = 0h Build-in-self-test not supported

Latency Timer = 20h

Cache Line Size= 0h

IO Address = ffa0h length 16 enabled

Max Lat = 0ns

Min Gnt = 0ns

PCI Int Pin = NC

Interrupt line = 0



Class = Display (VGA)

Vendor ID = 5333h, S3 Incorporated

Device ID = 8811h, 86C764/765 Trio 64/64V+ GUI Accelerator

PCI index = 0h

Class Codes = 030000h

Revision ID = 44h

Bus number = 0

Device number = 16

Function num = 0

Status Reg = 200h

Command Reg = 3h

Header type = 0h Single-function

BIST = 0h Build-in-self-test not supported

Latency Timer = 0h

Cache Line Size= 0h

Mem Address = f8000000h 32bit length 67108864 enabled

Max Lat = 0ns

Min Gnt = 0ns

PCI Int Pin = INT A

Interrupt line = 9



Class = Network (Ethernet)

Vendor ID = 10b7h, 3Com Corporation

Device ID = 9050h, 3C905-TX Fast Etherlink XL PCI 10/100

PCI index = 0h

Class Codes = 020000h

Revision ID = 0h

Bus number = 0

Device number = 17

Function num = 0

Status Reg = 200h

Command Reg = 107h

Header type = 0h Single-function

BIST = 0h Build-in-self-test not supported

Latency Timer = 20h

Cache Line Size= 0h

IO Address = dcc0h length 64 enabled

Expansion ROM = fc000000h length 65536 disabled

Max Lat = 8ns

Min Gnt = 3ns

PCI Int Pin = INT A

Interrupt line = 11

5

jonathanjohnsson@hotmail.com (Jonathan Johnsson) wrote in
<3A0FE966.7CD649C4@hotmail.com>:

Hello,

Have your problem fixed ?

Ferenc

6

Ferenc Sarkozy <sarkozyf@freemail.c3.hu> wrote:

jonathanjohnsson@hotmail.com > (Jonathan Johnsson) wrote in
3A0FE966.7CD649C4@hotmail.com> >:

Hello,

Have your problem fixed ?

You will have to wait for the patch to try out the latest driver, should be
available soon and when the patch is available it will be posted…

Chris

Ferenc

7

ctravis@qnx.com (Chris Travis) wrote in <8uou6a$1p9$7@nntp.qnx.com>:

You will have to wait for the patch to try out the latest driver, should be
available soon and when the patch is available it will be posted…

Chris

Thank you Chris, i’m looking forward to it.