From: Boszormenyi Zoltan <zboszor@pr.hu>
To: linux-kernel@vger.kernel.org
Subject: VESA and VGA16 framebuffer drivers clash sometimes
Date: Fri, 20 Apr 2012 09:51:04 +0200 [thread overview]
Message-ID: <4F911568.7050601@pr.hu> (raw)
Hi,
on an embedded x86 board with Intel Atom, text on vesafb
gets distorted if both vesafb and vga16fb are compiled in.
The strange thing is that it doesn't happen all the time but
about once out of 15 boots.
The distortion looks like this:
http://www.postgresql-support.de/private/IMG_7221.jpg
The relevant kernel messages:
Apr 13 11:14:30 term002 kernel: vesafb: mode is 800x600x16, linelength=1600, pages=7
Apr 13 11:14:30 term002 kernel: vesafb: scrolling: redraw
Apr 13 11:14:30 term002 kernel: vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Apr 13 11:14:30 term002 kernel: vesafb: framebuffer at 0xa0000000, mapped to 0xdf580000,
using 1875k, total 8128k
Apr 13 11:14:30 term002 kernel: Console: switching to colour frame buffer device 100x37
Apr 13 11:14:30 term002 kernel: fb0: VESA VGA frame buffer device
Apr 13 11:14:30 term002 BOOTLOG: Terminal startup
Apr 13 11:14:30 term002 kernel: vga16fb: mapped to 0xc00a0000
Apr 13 11:14:30 term002 kernel: fbcon: VGA16 VGA (fb1) is primary device
Apr 13 11:14:30 term002 kernel: fbcon: Remapping primary device, fb1, to tty 1-63
Apr 13 11:14:30 term002 kernel: fb1: VGA16 VGA frame buffer device
It's strange that vga16fb is always detected as primary
and vesafb gets remapped to fb1 even when there is no
screen distortion. The kernel is compiled for SMP.
Best regards,
Zoltán Böszörményi
next reply other threads:[~2012-04-20 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 7:51 Boszormenyi Zoltan [this message]
2012-04-20 11:12 ` VESA and VGA16 framebuffer drivers clash sometimes Geert Uytterhoeven
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=4F911568.7050601@pr.hu \
--to=zboszor@pr.hu \
--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