From: Jim Hague <jim.hague@acm.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [2.6.11 Permedia-2 Framebuffer] driver broken (?).
Date: Mon, 07 Mar 2005 19:44:24 -0000 (GMT) [thread overview]
Message-ID: <XFMail.20050307194424.jim.hague@acm.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0503052355320.12643@poirot.grange>
On 05-Mar-2005 Guennadi Liakhovetski wrote:
> Worked on 2.6.10-rc2. With 2.6.11 during boot upon switching to fb, text
> becomes orange, penguins look sick (not sharp). X starts and runs normal
> (doesn't use fb), switching to vt not possible any more. Disabling
> fb-console in kernel config fixes VTs. Reverting pm2fb.c fixes the
> problem.
I've just tried a stock 2.6.11 fresh from the tarball, and I see some of what
you are seeing.
I don't see any problems with text colour or images. Text is white, Tux is 100%
normal. This on a single processor K6/2-450 with a Creative Graphics Blaster
Exxtreme, BTW.
However, I do see the problem switching back to a vt from X. In fact it does
work, except that the video is blanked. This is a bug in pm2fb.c exposed by
recent changes to fbcon. Please try this fix (works for me) and let me know if
it restores normal service for you too.
--- drivers/video/pm2fb.c.orig 2005-03-07 15:35:28.000000000 +0000
+++ drivers/video/pm2fb.c 2005-03-07 18:34:13.000000000 +0000
@@ -747,7 +747,7 @@
}
if ((info->var.vmode & FB_VMODE_MASK)==FB_VMODE_DOUBLE)
video |= PM2F_LINE_DOUBLE;
- if (info->var.activate==FB_ACTIVATE_NOW)
+ if ((info->var.activate & FB_ACTIVATE_MASK)==FB_ACTIVATE_NOW)
video |= PM2F_VIDEO_ENABLE;
par->video = video;
Returning to your problems with text colour and images, can you try
with CONFIG_FB_PM2_FIFO_DISCONNECT=n and see if that makes a difference.
Thanks.
--
Jim Hague - jim.hague@acm.org Never trust a computer you can't lift.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-07 19:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 23:53 [2.6.11 Permedia-2 Framebuffer] driver broken (?) Guennadi Liakhovetski
2005-03-06 9:52 ` Guennadi Liakhovetski
2005-03-06 13:30 ` Guennadi Liakhovetski
2005-03-07 19:44 ` Jim Hague [this message]
2005-03-07 20:24 ` Guennadi Liakhovetski
2005-03-07 22:08 ` Jim Hague
2005-03-08 23:08 ` Jim Hague
2005-03-09 23:48 ` Guennadi Liakhovetski
2005-03-21 22:59 ` Andrew Morton
2005-03-21 23:37 ` Antonino A. Daplas
2005-03-21 23:40 ` Guennadi Liakhovetski
2005-03-22 9:41 ` Jim Hague
2005-05-25 23:53 ` Andrew Morton
2005-05-26 22:38 ` Guennadi Liakhovetski
2005-05-27 23:31 ` Guennadi Liakhovetski
2005-05-28 10:46 ` Jim Hague
2005-06-09 14:35 ` Jim Hague
2005-06-10 5:30 ` Guennadi Liakhovetski
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=XFMail.20050307194424.jim.hague@acm.org \
--to=jim.hague@acm.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).