Mach64 WinTurbo

Is this card supported ?

Works on QNX4.25/Photon 1.14.

I can’t figure it out from the supported hardware list.

thanks in advance


Per Åkesson
Carmenta AB
SWEDEN

Per Akesson <Per.Akesson@carmenta.se> wrote:
: Is this card supported ?

: Works on QNX4.25/Photon 1.14.

I believe this is a Mach64 GX. If if worked under QNX4, it will more
than likely work. If it doesn’t, we’ll fix it.

: I can’t figure it out from the supported hardware list.

: thanks in advance

: –
: Per ?kesson
: Carmenta AB
: SWEDEN

David Donohoe wrote:

Per Akesson <> Per.Akesson@carmenta.se> > wrote:
: Is this card supported ?

: Works on QNX4.25/Photon 1.14.

I believe this is a Mach64 GX. If if worked under QNX4, it will more
than likely work. If it doesn’t, we’ll fix it.

Well, the only mode available is svga.

When I do a

crttrap -VV trap

it hangs at devg-cyrix.so.

Below is output from the pci command:

PCI version = 2.10

Class = Mass Storage (IDE)
Vendor ID = 1042h, PC Technology
Device ID = 1000h, RZ1000 IDE Ctrlr
PCI index = 0h
IO Address = 1f0h enabled
IO Address = 3f4h enabled
PCI Int Pin = NC
Interrupt line = 0

Class = Display (VGA)
Vendor ID = 1002h, ATI Technologies
Device ID = 4758h, 210888GX Mach 64 (WinTurbo)
PCI index = 0h
Mem Address = a0000000h enabled
Expansion ROM = fe000000h disabled
PCI Int Pin = NC
Interrupt line = 162


Any clues ?

thanks in advance

\

Per Åkesson
Carmenta AB
SWEDEN

Per Akesson <Per.Akesson@carmenta.se> wrote:
: David Donohoe wrote:

:> Per Akesson <Per.Akesson@carmenta.se> wrote:
:> : Is this card supported ?
:>
:> : Works on QNX4.25/Photon 1.14.
:>
:> I believe this is a Mach64 GX. If if worked under QNX4, it will more
:> than likely work. If it doesn’t, we’ll fix it.

It should be detected. Can you edit /etc/system/config/graphics-traplist.
Remove all lines, and add this one:

devgt-iographics -dldevg-mach64.so -d0x1002,0x4758 -I0

Then re-run crttrap -VV trap, and see what it prints.

: Well, the only mode available is svga.

: When I do a

: crttrap -VV trap

: it hangs at devg-cyrix.so.

: Below is output from the pci command:

: PCI version = 2.10

: Class = Mass Storage (IDE)
: Vendor ID = 1042h, PC Technology
: Device ID = 1000h, RZ1000 IDE Ctrlr
: PCI index = 0h
: IO Address = 1f0h enabled
: IO Address = 3f4h enabled
: PCI Int Pin = NC
: Interrupt line = 0

: Class = Display (VGA)
: Vendor ID = 1002h, ATI Technologies
: Device ID = 4758h, 210888GX Mach 64 (WinTurbo)
: PCI index = 0h
: Mem Address = a0000000h enabled
: Expansion ROM = fe000000h disabled
: PCI Int Pin = NC
: Interrupt line = 162


: Any clues ?

: thanks in advance


: –
: Per ?kesson
: Carmenta AB
: SWEDEN

David Donohoe wrote:

It should be detected. Can you edit /etc/system/config/graphics-traplist.
Remove all lines, and add this one:

devgt-iographics -dldevg-mach64.so -d0x1002,0x4758 -I0

Then re-run crttrap -VV trap, and see what it prints.

Work great, thanks.

But how do I keep these settings ?

It seems when I reboot, the settings are removed.

I get the following startup messages

/etc/system/config/graphics-modes removed
Running crttrap, please wait

and then hangs in devg-cyrix.so and defaults to vga

regards

\

Per Åkesson
Carmenta AB
SWEDEN

Per Akesson <Per.Akesson@carmenta.se> wrote:
: David Donohoe wrote:

:>
:>
:> It should be detected. Can you edit /etc/system/config/graphics-traplist.
:> Remove all lines, and add this one:
:>
:> devgt-iographics -dldevg-mach64.so -d0x1002,0x4758 -I0
:>
:> Then re-run crttrap -VV trap, and see what it prints.
:>

: Work great, thanks.

: But how do I keep these settings ?

Well, you could hack /etc/system/enum/devices/graphics, and replace
the cyrix line with the devgt-… line above.

In the meantime, we gotta figure out why the enumerator doesn’t “see”
the mach64 card.

: It seems when I reboot, the settings are removed.

: I get the following startup messages
: …
: /etc/system/config/graphics-modes removed
: Running crttrap, please wait
: …

: and then hangs in devg-cyrix.so and defaults to vga

: regards


: –
: Per ?kesson
: Carmenta AB
: SWEDEN

David Donohoe wrote:

Per Akesson <> Per.Akesson@carmenta.se> > wrote:
: David Donohoe wrote:

:
:
:> It should be detected. Can you edit /etc/system/config/graphics-traplist.
:> Remove all lines, and add this one:
:
:> devgt-iographics -dldevg-mach64.so -d0x1002,0x4758 -I0
:
:> Then re-run crttrap -VV trap, and see what it prints.
:

: Work great, thanks.

: But how do I keep these settings ?

Well, you could hack /etc/system/enum/devices/graphics, and replace
the cyrix line with the devgt-… line above.

In the meantime, we gotta figure out why the enumerator doesn’t “see”
the mach64 card.

I tried to run system without starting pci-bios at all and my matrox
G200 was succesfully detected… as cyrix.
Might be problem with then…

  • igor

Igor Kovalenko <Igor.Kovalenko@motorola.com> wrote:
: David Donohoe wrote:
:>
:> Per Akesson <Per.Akesson@carmenta.se> wrote:
:> : David Donohoe wrote:
:>
:> :>
:> :>
:> :> It should be detected. Can you edit /etc/system/config/graphics-traplist.
:> :> Remove all lines, and add this one:
:> :>
:> :> devgt-iographics -dldevg-mach64.so -d0x1002,0x4758 -I0
:> :>
:> :> Then re-run crttrap -VV trap, and see what it prints.
:> :>
:>
:> : Work great, thanks.
:>
:> : But how do I keep these settings ?
:>
:> Well, you could hack /etc/system/enum/devices/graphics, and replace
:> the cyrix line with the devgt-… line above.
:>
:> In the meantime, we gotta figure out why the enumerator doesn’t “see”
:> the mach64 card.
:>

: I tried to run system without starting pci-bios at all and my matrox
: G200 was succesfully detected… as cyrix.
: Might be problem with then…

It wasn’t detected as a cyrix. The idea is that if no hardware is
detected by searching PCI configuration space, then run the trappers
which could potentially find non-pci hardware. (It is possible
to have a Cyrix that does not show up in PCI space).

(But if you got a bunch of modes in the graphics-modelist file,
referencing devg-cyrix.so, then it was detected as a cyrix, and
that would be bad…)

There’s also a bug wherby the cyrix trapper leaves the console
locked (which we’ve fixed) but that’s a separate issue.