Anyone got dual head r128 up and running on ppc? I've got a dual G4
system here (running a UP kernel for now), with the shipped AGP r128
card, and another PCI (pc, no fcode) r128 card.
The relevant information is attached, lspci -vv, XF86Config, and the
log of the failed X startup. X works with just the AGP card, as
expected.
Of note is the:
c000:00b9: 63 ILLEGAL X86 OPCODE!
line in x.log, when trying to run int10 on the secondary card.
Thanks,
--
Josh
| huber@mclx.com |
1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A
Josh Huber wrote:
Anyone got dual head r128 up and running on ppc? I've got a dual G4
system here (running a UP kernel for now), with the shipped AGP r128
card, and another PCI (pc, no fcode) r128 card.
The relevant information is attached, lspci -vv, XF86Config, and the
log of the failed X startup. X works with just the AGP card, as
expected.
Of note is the:
c000:00b9: 63 ILLEGAL X86 OPCODE!
line in x.log, when trying to run int10 on the secondary card.
I don't think that's the cause, it fails much later.
Have you built X yourself? If yes, you need patches from Ani Joshi. The memory
and clock values it probes are obviously bogus.
Wait a minute, I see you are using debs, which should contain Ani's stuff.
Does aty128fb work on the second card? If yes, try Option "UseFBDev".
Michel
--
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
On Wed, 11 Oct 2000, Josh Huber wrote:
Of note is the:
c000:00b9: 63 ILLEGAL X86 OPCODE!
line in x.log, when trying to run int10 on the secondary card.
Hmmm, 0x63 is the opcode for arpl, a protected mode only instruction which
is related to (shudder) segments and their protection model. If you reach
this code, it might be an emulator bug (but I gave up trying to understand
Xfree's emulator), but I can't remember (and I got rid of my XFree sources
because I needed the disk space for something else) if there is a way to
put a breakpoint in the emulated ROM and step (emulated) instruction by
instruction.
Gabriel.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/