public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Dave Airlie <airlied@gmail.com>,
	linux-kernel@vger.kernel.org, keenanpepper@gmail.com
Subject: Re: i830 DRM problems
Date: Tue, 22 Mar 2005 00:34:34 +0100	[thread overview]
Message-ID: <423F5A0A.7060307@ens-lyon.org> (raw)
In-Reply-To: <20050321151453.695c73e2.akpm@osdl.org>

Andrew Morton a écrit :
> Dave Airlie <airlied@gmail.com> wrote:
> 
>>>I am experiencing problems with DRM on my Dell Optiplex GX260.
>>>I am running a Debian Sarge with Vanilla Linux 2.6.11 and XFree 4.3.0.
>>>This one appeared while playing crack-attack and lead to a crash
>>>of the X server.
>>>
>>
>>a) does it work with 2.6.10?
>>b) does it work if you turn off intelfb?
>>
> 
> afacit we're still waiting for an answer from Brice on this one?

Sorry about that, we start to talk about it in private with Dave.
But, I did not really it since Keenan Pepper told me it was due
to a bug in the XFree 4.3 driver.
I am now using Xorg and didn't see any DRM problem since.
However, I can't confirm that my bug was surely due to the XFree driver 
and not to the kernel driver since Xorg uses i915 instead of i830.
Keenan, do you have details ?

I was also talking about a problem in intelfb on this box (i845G).
Basically, it works great during startup. But from what I remember, it
always crashes when switching from X to a text console.
I'll try to debug this one soon.

Brice

  reply	other threads:[~2005-03-21 23:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 13:41 i830 DRM problems Brice Goglin
2005-03-11 23:07 ` Dave Airlie
2005-03-21 23:14   ` Andrew Morton
2005-03-21 23:34     ` Brice Goglin [this message]
2005-03-22  0:13       ` Andrew Morton
2005-03-22 12:01         ` Brice Goglin
2005-03-22  1:07       ` Keenan Pepper

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=423F5A0A.7060307@ens-lyon.org \
    --to=brice.goglin@ens-lyon.org \
    --cc=airlied@gmail.com \
    --cc=akpm@osdl.org \
    --cc=keenanpepper@gmail.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox