From: Andreas Theofilu <abfall@TheosSoft.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [update] Vesafb problem since 2.5.51
Date: Sun, 4 Jan 2004 10:50:28 +0100 [thread overview]
Message-ID: <20040104105028.3449aa9e.abfall@TheosSoft.net> (raw)
In-Reply-To: <1a49X-1o2-7@gated-at.bofh.it>
On Sun, 04 Jan 2004 01:20:09 +0100
S Ait-Kassi <sait-kassi@zonnet.nl> wrote:
> Hi,
>
> I'm mailing to inform you of a possible bug in the vesa framebuffer
> module which has been appearing in the kernel since 2.5.51. I posted at
> the linux-kernel@vger.kernel.org mailinglist but wasn't able to get
> feedback so I'm directing it directly to the developers of the
> framebuffer layer and to you specifically since you were involved with
> most of the changes in 2.5.51.
>
> I have attached grabbed framebuffer distortion pics (png) since I think
> those speak clearer than my previous attempts to put the problem into
> words through the mailing list.
After starting tuxcard or the program "fracplanet" (creates a 3d model of
a planet) and possibly others, my screen looks exactly the same as you can
see on the screen shots of S Ait-Kassi. Beside this, random pixels still
appearing.
My Hardware:
CPU: AMD 2800+
Graphic card: Radeon 7000 (with 64 Mb RAM)
Motherboard: MSI KT4V
Chipset: KT400
PS: I got several tips already and they made it a little bit better, but
it's still not ok.
--
Andreas Theofilu
http://www.TheosSoft.net/
--==| Enjoy the science of Linux! |==--
next parent reply other threads:[~2004-01-04 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1a49X-1o2-7@gated-at.bofh.it>
2004-01-04 9:50 ` Andreas Theofilu [this message]
2004-01-13 14:47 S Ait-Kassi
-- strict thread matches above, loose matches on Subject: below --
2004-01-06 13:40 S Ait-Kassi
2004-01-06 23:06 ` James Simmons
2004-01-07 23:40 ` S Ait-Kassi
2004-01-09 20:57 ` James Simmons
2004-01-08 9:29 ` Pavel Machek
2004-01-04 0:11 S Ait-Kassi
2004-01-05 22:13 ` James Simmons
2004-01-02 13:22 S Ait-Kassi
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=20040104105028.3449aa9e.abfall@TheosSoft.net \
--to=abfall@theossoft.net \
--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
Powered by JetHome