From: "Kristofer T. Karas" <ktk@enterprise.bidmc.harvard.edu>
To: kronos@kronoz.cjb.net
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Javier Villavicencio <jvillavicencio@arnet.com.ar>
Subject: Re: RadeonFB [Re: 2.4.23pre8 - ACPI Kernel Panic on boot]
Date: 30 Oct 2003 00:20:34 -0500 [thread overview]
Message-ID: <1067491238.1735.4.camel@ktkhome> (raw)
In-Reply-To: <20031029210321.GA11437@dreamland.darkstar.lan>
On Wed, 2003-10-29 at 16:03, Kronos wrote:
> > have been using ATI's private DRI/DRM kernel module driver (fglrx) in
> > concert with XFree 4.2.0 for quite some time.
>
> Ah! ATI's driver touches registers behind our back. Can you reproduce
> without this binary module?
Hi Luca, et al,
Yes, I can reproduce without the tainting kernel module (fglrx.o).
Debugging a bit, the corruption shows up when using ATI's "fglr" device
driver in XF86Config. If I switch to using the unaccelerated "Radeon"
driver provided by XFree, then the screen remains readable upon return
from X. Thus, the kernel module is OK, the ATI proprietary glx and dri
modules are OK, it's just the driver.
However, I still think this belongs as a kernel issue, because it
appears to be a failing of the radeonfb.o module to properly set the
radeon registers. Remember that version 0.1.4 of the driver does not
have this issue; it works just fine with the ATI fglr X driver.
Kris
next prev parent reply other threads:[~2003-10-30 5:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 13:32 2.4.23pre8 - ACPI Kernel Panic on boot Joachim Bremer
2003-10-28 15:49 ` Marcelo Tosatti
2003-10-28 22:42 ` RadeonFB [Re: 2.4.23pre8 - ACPI Kernel Panic on boot] Kristofer T. Karas
2003-10-28 23:05 ` Javier Villavicencio
2003-10-29 16:51 ` Marcelo Tosatti
2003-10-29 20:06 ` Kristofer T. Karas
2003-10-29 21:03 ` Kronos
2003-10-30 5:20 ` Kristofer T. Karas [this message]
2003-10-31 7:59 ` Benjamin Herrenschmidt
2003-10-31 19:16 ` Kristofer T. Karas
2003-10-31 22:55 ` Benjamin Herrenschmidt
2003-11-01 6:22 ` Kristofer T. Karas
2003-10-28 17:40 ` 2.4.23pre8 - ACPI Kernel Panic on boot Marcos D. Marado Torres
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=1067491238.1735.4.camel@ktkhome \
--to=ktk@enterprise.bidmc.harvard.edu \
--cc=jvillavicencio@arnet.com.ar \
--cc=kronos@kronoz.cjb.net \
--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;
as well as URLs for NNTP newsgroup(s).