lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1177727097.7568.6.camel@daplas>
Date:	Sat, 28 Apr 2007 10:24:57 +0800
From:	"Antonino A. Daplas" <adaplas@...il.com>
To:	James Pearson <james-p@...ing-picture.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: X display shift with disabled console blanking

On Fri, 2007-04-27 at 18:08 +0100, James Pearson wrote:
> I have a problem whereby the X display 'shifts' to left when anything 
> writes to /dev/console - where console screen blanking has been disabled 
> i.e. doing something like:
> 
> 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:
> 
> echo "some random text" > /dev/console
> (may have to repeat the echo above a few times)
> 
> ... and the whole X display jumps (and wraps) to the left
> 
> I'm using a RHEL4 based distro with a vanilla 2.6.21 x86_64 kernel 
> (although I've seen the problem with various x86_64 and i686 2.6.X kernels).
> 
> I've seen this problem on a number of different nVidia cards - using 
> the vesa driver (same problem occurs with nVidia's binary driver). I 
> haven't tried using other makes of graphics cards.
> 
> 
> OK, this may be a strange combination of disabling the text console 
> blanking and running X, but something isn't right somewhere ...

Yep, it's strange because I can't reproduce this. And the console write
should not succeed if the current console is in KD_GRAPHICS mode, which
is done by X (unless your version is different).

> 
> Any ideas?

I don't.  But, what is your current console?  Is it VGA, or framebuffer?
Can you try doing this again in both VGA and vesafb?

And this does not happen if there is no previous setterm -blank 0
command?

Tony


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ