From: Andrew Morton <akpm@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Fw: Re: disabling VESAFB no longer locks up VT (was Re: 2.4.10-r1 MTRR bug)
Date: Fri, 14 Jan 2005 17:04:45 -0800 [thread overview]
Message-ID: <20050114170445.0d02ae91.akpm@osdl.org> (raw)
Are you folks aware of this lkml thread??
Thanks.
Begin forwarded message:
Date: Fri, 14 Jan 2005 16:50:42 -0800
From: Steve <s.egbert@sbcglobal.net>
To: Daniel Drake <dsd@gentoo.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: disabling VESAFB no longer locks up VT (was Re: 2.4.10-r1 MTRR bug)
Daniel Drake wrote:
> Hi Andrew,
>
> Andrew Morton wrote:
>
>> Steve <s.egbert@sbcglobal.net> wrote:
>>
>>> For the Athlon 2100, I get the following outputs and then the VGA
>>> console is frozen from further output (but it doesn't prevent the
>>> full bootup into X windows session of which I am able to resume
>>> normal Linux/X session, but not able to regain any virtual console
>>> session.)
>>
>>
>>
>> hm. Not sure what could have caused that.
>
>
> This may be a problem in Gentoo's kernels, we offer an experimental
> version of vesafb...
Disabling the VESAFB resulted in regaining control of the VTs (virtual
terminals).
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next reply other threads:[~2005-01-15 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 1:04 Andrew Morton [this message]
2005-01-15 12:33 ` Fw: Re: disabling VESAFB no longer locks up VT (was Re: 2.4.10-r1 MTRR bug) Antonino A. Daplas
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=20050114170445.0d02ae91.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).