All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Dänzer <daenzerm@student.ethz.ch>
To: Josh Huber <huber@mclx.com>
Cc: Linux/PowerPC Devel List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: dual head r128
Date: Wed, 11 Oct 2000 20:43:28 +0200	[thread overview]
Message-ID: <39E4B4D0.FA62D929@student.ethz.ch> (raw)
In-Reply-To: 20001011141722.A1437@missioncriticallinux.com


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/

  reply	other threads:[~2000-10-11 18:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-11 18:17 dual head r128 Josh Huber
2000-10-11 18:43 ` Michel Dänzer [this message]
2000-10-11 18:52   ` Josh Huber
2000-10-11 19:04     ` Tom Rini
2000-10-11 19:09     ` Michel Dänzer
2000-10-11 19:26       ` Josh Huber
2000-10-11 22:48         ` Michel Dänzer
2000-10-13 17:16           ` Josh Huber
2000-10-12 13:09     ` Kostas Gewrgiou
2000-10-12 15:13       ` Benjamin Herrenschmidt
2000-10-12 15:49         ` Gabriel Paubert
2000-10-12 16:40           ` David Edelsohn
2000-10-17  0:12           ` Paul Mackerras
2000-10-17  5:56             ` Michel Lanners
2000-10-17 10:41             ` Benjamin Herrenschmidt
2000-10-17 13:45               ` Geert Uytterhoeven
2000-10-17 17:17                 ` Benjamin Herrenschmidt
2000-10-12 16:44         ` Kostas Gewrgiou
2000-10-11 21:01 ` Gabriel Paubert
  -- strict thread matches above, loose matches on Subject: below --
2000-10-12 13:41 Hendricks, Kevin
2000-10-12 14:10 ` Kostas Gewrgiou
2000-10-12 14:30 Hendricks, Kevin
2000-10-12 16:11 ` Kostas Gewrgiou
2000-10-12 17:22   ` Michel Dänzer
2000-10-12 17:44     ` Kostas Gewrgiou
2000-10-12 21:25       ` Michel Dänzer
2000-10-13 15:26         ` Kostas Gewrgiou
2000-10-13 16:21       ` Geert Uytterhoeven
2000-10-12 16:25 Hendricks, Kevin
     [not found] <200010121619.TAA27476@ns0.imbc.gr>
2000-10-12 17:08 ` Kostas Gewrgiou
     [not found] <19340906102959.14429@192.168.1.2>
2000-10-12 17:57 ` Gabriel Paubert
     [not found] <Pine.LNX.4.10.10010132302530.381-100000@cassiopeia.home>
2000-10-13 21:36 ` Benjamin Herrenschmidt
2000-10-13 21:47   ` Michel Lanners
2000-10-14 10:13     ` Benjamin Herrenschmidt
2000-10-14 10:21   ` Geert Uytterhoeven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39E4B4D0.FA62D929@student.ethz.ch \
    --to=daenzerm@student.ethz.ch \
    --cc=huber@mclx.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.