From: Kronos <kronos@kronoz.cjb.net>
To: linux-kernel@vger.kernel.org
Cc: "Kristofer T. Karas" <ktk@enterprise.bidmc.harvard.edu>,
"Javier Villavicencio" <jvillavicencio@arnet.com.ar>
Subject: Re: RadeonFB [Re: 2.4.23pre8 - ACPI Kernel Panic on boot]
Date: Wed, 29 Oct 2003 22:03:21 +0100 [thread overview]
Message-ID: <20031029210321.GA11437@dreamland.darkstar.lan> (raw)
In-Reply-To: <3FA01DB6.6080106@enterprise.bidmc.harvard.edu>
> I guess the newer 0.1.8 is needed to support Radeon 9600's. I'm curious
> as to whether other people have the same massive screen corruption
> problems returning from X as I do. If not, probably best to keep the
> new driver. (Maybe I should go out and buy myself a new Radeon. :-) I
> 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?
Luca
--
Reply-To: kronos@kronoz.cjb.net
Home: http://kronoz.cjb.net
Al termine di un pranzo di nozze mi hanno dato un
amaro alle erbe cosi' schifoso che perfino sull'etichetta
c'era un frate che vomitava.
next prev parent reply other threads:[~2003-10-29 21:03 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 [this message]
2003-10-30 5:20 ` Kristofer T. Karas
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=20031029210321.GA11437@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=jvillavicencio@arnet.com.ar \
--cc=ktk@enterprise.bidmc.harvard.edu \
--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
all inboxes | Powered by JetHome®