public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Reid Hekman <hekman@ideaone.net>
To: linux-kernel@vger.kernel.org
Cc: jsimmons@infradead.org
Subject: 2.5 neofb screen corruption leaving X
Date: 05 May 2003 23:06:13 -0500	[thread overview]
Message-ID: <1052193973.31970.3.camel@artemis> (raw)

Description: The console is "blown up" upon leaving X with neofb
compiled in on an IBM TP600E. Characters are 2-3 times normal size, dots
are not in consecutive pixels but spaced several screen elements apart.
Lines are still spaced normally but the larger text overwrites the
previous line when they wrap. The system is still usable, but the
console is unreadable ;-) I can still go back into X just fine.

Environment: IBM Thinkpad 600E, NeoMagic 256AV, RedHat 8.0.94 (Phoebe)

lspci -v
01:00.0 VGA compatible controller: Neomagic Corporation NM2200
[MagicGraph 256AV] (rev 20) (prog-if 00 [VGA])
        Subsystem: IBM ThinkPad 570
        Flags: bus master, medium devsel, latency 128, IRQ 11
        Memory at e0000000 (32-bit, prefetchable) [size=16M]
        Memory at 70000000 (32-bit, non-prefetchable) [size=4M]
        Memory at 70400000 (32-bit, non-prefetchable) [size=1M]
        Capabilities: [dc] Power Management version 1

cat /proc/cmdline 
ro root=/dev/hda2 video=neofb:1024x768-16

Kernels: Tested 2.5.67-2.5.69 and are affected, haven't gone back
further yet but I can test. RedHat 2.4.18 works correctly. 

Config is here: http://dslstatic-236-77.ideaone.net/2.5.69-config

dmesg output here: http://dslstatic-236-77.ideaone.net/kernmsg.txt

Thanks in advance,
Reid



             reply	other threads:[~2003-05-06  3:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06  4:06 Reid Hekman [this message]
2003-05-06 18:25 ` 2.5 neofb screen corruption leaving X James Simmons
2003-05-07  2:12   ` Reid Hekman

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=1052193973.31970.3.camel@artemis \
    --to=hekman@ideaone.net \
    --cc=jsimmons@infradead.org \
    --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