All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: X display shift with disabled console blanking
Date: Tue, 01 May 2007 16:58:48 +0100	[thread overview]
Message-ID: <463763B8.7060606@moving-picture.com> (raw)
In-Reply-To: <1178032840.5331.2.camel@daplas>

Antonino A. Daplas wrote:
> On Tue, 2007-05-01 at 13:17 +0100, James Pearson wrote:
> 
>>Antonino A. Daplas wrote:
>>
>>>On Mon, 2007-04-30 at 13:58 +0100, James Pearson wrote:
>>>
>>>
>>>>Antonino A. Daplas wrote:
>>>>
>>>>
>>>>>On Fri, 2007-04-27 at 18:08 +0100, James Pearson wrote:
> 
> 
>>It does indeed seem that the switching back and forth between text and 
>>graphics does appear to be part of the issue - in my previous testing I 
>>probably did do this (but didn't include this in my recipe above) - so 
>>here is a new 'recipe' that shows the problem (for me)
>>
>>boot to run level 3
>>
>>if not root, then make sure /dev/console is writeable
>>
>>login and type:
>>
>>setterm -blank 0
>>
>>start X
>>
>>type into an xterm:
>>
>>while true; do echo "" > /dev/console; usleep 100000; done
>>
>>while the above loop is running switch to the text console and back 
>>again (Ctrl-Alt-F1 then Ctrl-Alt-F7)
>>
>>... and the screen will be shifting (and wrapping) to the left.
>>
> 
> 
> Okay, this makes me see the problem more clearly.  It looks like that
> vt/console layer is unreliable in terms of checking for the
> text/graphics mode of the current console.  Instead of auditing the
> console code, I'll just have vgacon check for the mode.  Try the
> attached patch and let me know if it helps. 

That seems to fix it!

Thanks

James Pearson

      reply	other threads:[~2007-05-01 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 17:08 X display shift with disabled console blanking James Pearson
2007-04-28  2:24 ` Antonino A. Daplas
2007-04-30 12:58   ` James Pearson
2007-04-30 21:51     ` Antonino A. Daplas
2007-05-01 12:17       ` James Pearson
2007-05-01 15:20         ` Antonino A. Daplas
2007-05-01 15:58           ` James Pearson [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=463763B8.7060606@moving-picture.com \
    --to=james-p@moving-picture.com \
    --cc=adaplas@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.