All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Matrox G400 DRI doesn't work w/ Linux/ia64 2.4.5
Date: Mon, 30 Jul 2001 21:25:09 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005952@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005951@msgid-missing>

Just an additional data point: DRI works fine on 2.4.5 with the 3dfx
card.  The card doesn't use AGP though.

	--david

>>>>> On Mon, 30 Jul 2001 15:13:48 -0600, Bjorn Helgaas <bjorn_helgaas@hp.com> said:

  Bjorn> I'm running RedHat 7.1 on an HP i2000 ia64 box with a Matrox
  Bjorn> G400.  This has kernel 2.4.3 (with RedHat's patches) and
  Bjorn> XFree86 4.0.3.

  Bjorn> DRI seems to work fine as far as I can tell (glxinfo says
  Bjorn> "Mesa DRI G400", gears reports ~36 fps with "dri" and "glx"
  Bjorn> loaded, ~28 fps without).

  Bjorn> However, DRI doesn't work with a 2.4.5 kernel.  The kernel
  Bjorn> boots fine, and X starts up fine, and glxinfo again says
  Bjorn> "Mesa DRI G400", but gears opens a window with nothing in it.
  Bjorn> After starting gears, I can move the mouse pointer, but X
  Bjorn> seems dead.  The screen looks fine (with the empty gears
  Bjorn> window), but no mouse events work and I can't kill the
  Bjorn> server.

  Bjorn> I've applied RedHat's agp kernel patches to my 2.4.5 kernel,
  Bjorn> so drivers/char/agp and drivers/char/drm are identical
  Bjorn> between the working 2.4.3 and the broken 2.4.5 trees.

  Bjorn> Bjorn

  Bjorn> _______________________________________________ Linux-IA64
  Bjorn> mailing list Linux-IA64@linuxia64.org
  Bjorn> http://lists.linuxia64.org/lists/listinfo/linux-ia64


      reply	other threads:[~2001-07-30 21:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 21:13 [Linux-ia64] Matrox G400 DRI doesn't work w/ Linux/ia64 2.4.5 Bjorn Helgaas
2001-07-30 21:25 ` David Mosberger [this message]

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=marc-linux-ia64-105590693005952@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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.