public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Weird Xorg stretching (setfont)
Date: Fri, 16 May 2008 16:53:08 +0100	[thread overview]
Message-ID: <g0kal5$f5v$1@ger.gmane.org> (raw)
In-Reply-To: 21d7e9970805151618i71ccc581j7e07082bd0b7a8e@mail.gmail.com

Dave Airlie wrote:

> wierd got any fglrx or anything installed on you're system.. the
> radeon drm hasn't seen any changes that should affect this sorta
> thing, do you run radeonfb or vesafb?

Just in case you didn't see my reply I'm not an fglrx user and I don't run
radeonfb or vesafb.

After testing far too many kernels it turns out that this is not a
conventional regression. During startup openSUSE runs the following
command:

/bin/setfont -C /dev/tty1 lat9w-16.psfu -m trivial

in /etc/init.d/kbd

Now on the openSUSE provided 2.6.22.17-0.1-default #1 SMP kernel if X has
started and your run that command (e.g.
chvt 7; sleep 5s && /bin/setfont -C /dev/tty1 lat9w-16.psfu -m trivial
) the command will fail with error output similar to the following:
setfont: putfont: 256,8x16: failed: -1
putfont: KDFONTOP: Invalid Argument

If you are using a stock kernel (e.g. 2.6.24/2.6.25 etc) the command will
not fail and will instead corrupt X causing the lower part of the screen to
be drawn using the same line (creating a stretch/mirror effect).

There seems to be a bit of mention of this over in
https://bugzilla.novell.com/show_bug.cgi?id=335267 but that talks about it
failing (which I consider to be better behaviour than corrupting X).

The whole thing is racy on boot (e.g. if setfont happens before X is shown
then there is no corruption) fooling me into thinking it was a regression.

-- 
Sitsofe


  parent reply	other threads:[~2008-05-16 15:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 14:00 Weird Xorg radeon mirroring with linux-next-20080515 Sitsofe Wheeler
2008-05-15 17:35 ` Chris Snook
2008-05-15 21:36   ` Weird Xorg radeon mirroring with linux-next-20080515 [paritial bisect] Sitsofe Wheeler
2008-05-15 23:18     ` Dave Airlie
2008-05-16  7:39       ` Sitsofe Wheeler
2008-05-16 15:53       ` Sitsofe Wheeler [this message]
     [not found] <atMjN-4Qh-19@gated-at.bofh.it>
     [not found] ` <atPB7-2Ai-23@gated-at.bofh.it>
     [not found]   ` <atTlj-1SF-3@gated-at.bofh.it>
     [not found]     ` <atUU6-4Xh-15@gated-at.bofh.it>
     [not found]       ` <auaw7-1tZ-9@gated-at.bofh.it>
2008-05-19 22:03         ` Weird Xorg stretching (setfont) Bodo Eggert

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='g0kal5$f5v$1@ger.gmane.org' \
    --to=sitsofe@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox