From: Jason Wessel <jason.wessel@windriver.com>
To: Uwe Bonnes <bon@elektron.ikp.physik.tu-darmstadt.de>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Any SYSRQ key to force mode switch to console mode when using KMS?
Date: Wed, 06 Oct 2010 13:44:48 -0500 [thread overview]
Message-ID: <4CACC3A0.4090300@windriver.com> (raw)
In-Reply-To: <20100924080707.ba98fa1e.rdunlap@xenotime.net>
On 09/24/2010 10:07 AM, Randy Dunlap wrote:
> On Thu, 23 Sep 2010 18:31:32 +0200 Uwe Bonnes wrote:
>
> [just adding cc's]
>
>
>>>>>>> "Randy" == Randy Dunlap <rdunlap@xenotime.net> writes:
>>>>>>>
>> Randy> Is CONFIG_DRM_KMS_HELPER enabled in your kernel .config file? If
>> Randy> not, we need to find out how to enable it (there is no kconfig
>> Randy> prompt for it).
>>
>> Yes, it is enabled
>>
>> Randy> Can you check if Alt-Sysrq-H (help) lists V for "force-fb(V)"?
>> Yes, it is listed.
>>
>> And yes, my last experiments where with ALT-CTL-sysreq, so doomed for non
>> function due to operator error.
>>
>> However:
>> When running X, X.Org X Server 1.9.0 on Thinkpad R50 RV250, Alt-Sysrq-v
>> switches to an all-black display. By console switching with ALT-CLT-F1 I
>> get back to the booting console and ALT-CLT-F7 brings me back to X. Running
>> on the console and calling Alt-Sysrq-v prints
>> SysRq : Restore framebuffer console
>>
>> Is there some omission by the distribution or my setup that Alt-Sysrq-v when
>> running X results in an all-black screen?
>>
>> And when I hit the hibernate problem, the screen stays black even with a
>> console switch after Alt-Sysrq-v
>>
>>
I am not exactly sure what you are looking for but alt-sysrq-v might not
tell you a whole lot because an escape back to the text console that was
not actively receiving printk's or crash data is going to in general
provide you with a black screen.
If you were interested in something a bit more invasive such as a
collecting a process listing or examining the dmesg output you might
consider jumping into kdb.
echo kbd > /sys/module/kgdboc/parameters/kgdboc
Then you would do the "alt-sysrq v" followed by "alt-sysrq g". From
there you could then run dmesg, and your screen would no longer be blank
in theory. :-)
We do have some patches for the RV250 for atomic kernel mode setting
plus kdb support but they are not merged to the mainline kernels as of yet.
Jason.
prev parent reply other threads:[~2010-10-06 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 17:40 Any SYSRQ key to force mode switch to console mode when using KMS? Uwe Bonnes
2010-09-21 22:10 ` Randy Dunlap
2010-09-22 9:44 ` Uwe Bonnes
2010-09-22 15:24 ` Randy Dunlap
2010-09-23 9:51 ` Uwe Bonnes
2010-09-23 13:01 ` Uwe Bonnes
2010-09-23 15:02 ` Randy Dunlap
2010-09-23 16:31 ` Uwe Bonnes
2010-09-24 15:07 ` Randy Dunlap
2010-10-06 18:44 ` Jason Wessel [this message]
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=4CACC3A0.4090300@windriver.com \
--to=jason.wessel@windriver.com \
--cc=airlied@linux.ie \
--cc=bon@elektron.ikp.physik.tu-darmstadt.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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