From: Andrew Morton <akpm@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: pluto@pld-linux.org
Subject: Fw: [framebuffer] broken again :/
Date: Wed, 21 Jul 2004 22:45:15 -0700 [thread overview]
Message-ID: <20040721224515.1b76193e.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Wed, 21 Jul 2004 16:00:44 +0200
From: Pawe³ Sikora <pluto@pld-linux.org>
To: Andrew Morton <akpm@osdl.org>
Subject: [framebuffer] broken again :/
Hi,
# vanilla 2.8.8rc2...
I switch *all* consoles to 1024x768(75Hz,32bpp) (rivafb) mode.
(http://149.156.124.14/~pluto/tmp/kernel/step1.png)
Even without launching a bootsplash while switching
to another console I observe below effect:
(strange resolution and horrible aspect ratio)
http://149.156.124.14/~pluto/tmp/kernel/step2.png
I switch consoles again to 1024x768(75Hz,32bpp) mode
and get an oops:
http://149.156.124.14/~pluto/tmp/kernel/step3.png
# vanilla 2.6.7...
I switch *all* consoles to 1024x768(75Hz,32bpp) (rivafb) mode.
While switching to another console everything is all right.
(no resolution/aspect changes, no oops).
# summary
Framebuffer in 2.6.8-xx is broken (again) :/
Writing to lkml == Writing to /dev/null :/
Please, forward this email to fb-related developers.
At now, PLD-Linux rolls back to 2.6.7(+security fixes).
2.6.8 is unusable :(
--
/* Copyright (C) 2003, SCO, Inc. This is valuable Intellectual Property. */
#define say(x) lie(x)
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id\x10040&op=click
next reply other threads:[~2004-07-22 2:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 5:45 Andrew Morton [this message]
2004-07-22 6:51 ` Fw: [framebuffer] broken again :/ Antonino A. Daplas
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=20040721224515.1b76193e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=pluto@pld-linux.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;
as well as URLs for NNTP newsgroup(s).