From: vcjones@networkingunlimited.com (Vincent C Jones)
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: mpm@selenic.com
Subject: Re: Radeon FB troubles with recent kernels
Date: Mon, 14 Feb 2005 22:14:41 -0500 (EST) [thread overview]
Message-ID: <20050215031441.EFABE1DDFE@X31.nui.nul> (raw)
In-Reply-To: <3xVku-kH-15@gated-at.bofh.it>
In article <3xVku-kH-15@gated-at.bofh.it> you write:
>On my Thinkpad T30 with a Radeon Mobility M7 LW, I get interesting
>console video corruption if I start GDM, switch back to text mode,
>then stop it again. X is Xfree86 from Debian/unstable or X.org 6.8.2.
>
>The corruption shows up whenever the console scrolls after X has been
>shut down and manifests as horizontal lines spaced about 4 pixel rows
>apart containing contents recognizable as the X display. Switch from
>vt1 to vt2 and back or visual bell clears things back to normal, but
>corruption will reappear on the next scroll.
>
>This has appeared in at least 2.6.11-rc3-mm2 and rc4.
On my Thinkpad X31 with a Radeon Mobility M6 LY I see a major
regression going from 2.6.11-rc3 to rc4. With rc-4, the frame
buffer console (using "video=radeonfb:1024x768-24@60") comes up as
640x480 expanded to 1024x768. The inability of ACPI suspend to turn
off the backlight also returns. Using rc-3, frame buffer console
works fine and suspend/resume appears to work reliably without
needing radeontool to turn off the backlight (as long as I do it
from X.org X).
--
Dr. Vincent C. Jones, PE Expert advice and a helping hand
Computer Network Consultant for those who want to manage and
Networking Unlimited, Inc. control their networking destiny
Phone: +1 201 568-7810
14 Dogwood Lane, Tenafly, NJ 07670
VCJones@NetworkingUnlimited.com http://www.networkingunlimited.com
next parent reply other threads:[~2005-02-15 3:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3xVku-kH-15@gated-at.bofh.it>
2005-02-15 3:14 ` Vincent C Jones [this message]
2005-02-15 12:46 ` Benjamin Herrenschmidt
2005-02-15 12:50 ` Benjamin Herrenschmidt
2005-02-15 12:58 ` sigwait() and 2.6 Yves Crespin
2005-02-15 23:59 ` Ulrich Drepper
2005-02-16 10:08 Radeon FB troubles with recent kernels tvrtko.ursulin
[not found] <3y1SR-5K6-1@gated-at.bofh.it>
[not found] ` <3yatk-4mE-29@gated-at.bofh.it>
2005-02-15 15:07 ` Vincent C Jones
2005-02-15 22:02 ` Benjamin Herrenschmidt
2005-02-16 1:53 ` Vincent C Jones
2005-02-16 2:41 ` Benjamin Herrenschmidt
2005-02-16 14:39 ` Vincent C Jones
-- strict thread matches above, loose matches on Subject: below --
2005-02-14 20:39 Matt Mackall
2005-02-14 22:38 ` Benjamin Herrenschmidt
2005-02-14 23:08 ` Benjamin Herrenschmidt
2005-02-15 0:02 ` Antonino A. Daplas
2005-02-15 0:20 ` Matt Mackall
2005-02-15 1:07 ` Benjamin Herrenschmidt
2005-02-15 6:06 ` Matt Mackall
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=20050215031441.EFABE1DDFE@X31.nui.nul \
--to=vcjones@networkingunlimited.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/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®