From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29384] Slow switch between TTY1-TTY6 with /dev/fb0 or X11 involved
Date: Tue, 10 Aug 2010 04:20:44 -0700 (PDT) [thread overview]
Message-ID: <20100810112044.B2DDF13012F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-29384-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=29384
--- Comment #24 from peterle@hottemptation.org 2010-08-10 04:20:44 PDT ---
I'am sorry, the patch doesn't fix 29384 and 27744.
The system reacts like before, dmesg output is also exactly the same.
To new hints/quesitions:
With 2.6.34 I had no delay while loading the ATOMBIOS, if feels "smooth". I see
some kernel-messages at bootup in standard vga-resolution and the kernel
switches immidiatley to 1380x768 (my native display resolution).
Instead with 2.6.35 is see the bootup-message from kernel
"Linux agpgart interface v0.103
[drm] Initialized drm 1.1.0 20060810
[drm] radeon defaulting to kernel modesetting.
[drm] radeon kernel modesetting enabled." in resolution 640x480 standard vga,
than I got a blank screen with a delay and some seconds after this I see the
next bootup-messages.
Is it correct the the Radeon-Driver in the kernel creat all this
frequencq-scaling stuff under /sys with a Evergreen GPU. I tought this is only
supported till R700 GPUs?
Of course this could be just some generic stuff.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-08-10 11:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:04 [Bug 29384] New: Slow switch between TTY1-TTY6 with /dev/fb0 or X11 involved bugzilla-daemon
2010-08-03 15:05 ` [Bug 29384] " bugzilla-daemon
2010-08-03 15:05 ` bugzilla-daemon
2010-08-03 15:06 ` bugzilla-daemon
2010-08-03 15:43 ` bugzilla-daemon
2010-08-03 15:45 ` bugzilla-daemon
2010-08-03 15:46 ` bugzilla-daemon
2010-08-03 15:50 ` bugzilla-daemon
2010-08-03 18:08 ` bugzilla-daemon
2010-08-03 18:13 ` bugzilla-daemon
2010-08-03 18:16 ` bugzilla-daemon
2010-08-03 18:30 ` bugzilla-daemon
2010-08-03 18:41 ` bugzilla-daemon
2010-08-03 18:56 ` bugzilla-daemon
2010-08-03 19:41 ` bugzilla-daemon
2010-08-07 15:32 ` bugzilla-daemon
2010-08-07 15:33 ` bugzilla-daemon
2010-08-07 15:36 ` bugzilla-daemon
2010-08-07 15:39 ` bugzilla-daemon
2010-08-07 15:53 ` bugzilla-daemon
2010-08-07 16:43 ` bugzilla-daemon
2010-08-07 16:47 ` bugzilla-daemon
2010-08-07 17:20 ` bugzilla-daemon
2010-08-07 17:23 ` bugzilla-daemon
2010-08-07 17:23 ` bugzilla-daemon
2010-08-08 12:53 ` bugzilla-daemon
2010-08-09 16:40 ` bugzilla-daemon
2010-08-09 18:12 ` bugzilla-daemon
2010-08-10 11:20 ` bugzilla-daemon [this message]
2010-08-10 11:22 ` bugzilla-daemon
2010-08-16 9:18 ` bugzilla-daemon
2010-08-16 9:20 ` bugzilla-daemon
2010-08-16 11:11 ` bugzilla-daemon
2010-08-16 14:10 ` bugzilla-daemon
2010-08-16 15:06 ` bugzilla-daemon
2010-08-16 15:57 ` bugzilla-daemon
2010-08-23 12:22 ` bugzilla-daemon
2010-08-23 14:08 ` bugzilla-daemon
2010-08-23 16:12 ` bugzilla-daemon
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=20100810112044.B2DDF13012F@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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