Re: [update] Vesafb problem since 2.5.51

[S Ait-Kassi]

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@xxxxxxxxxxxxxxx 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. 

Hope you can shed more light on the situation.

Thanks,

S Ait-Kassi

On Friday 02 January 2004 14:22, S Ait-Kassi wrote:
> Hello,
>
> I figured out in which kernel the problem I was having appeared. It seems
> to work with 2.5.50 and the problems starts with 2.5.51.
>
> I've looked at the changelog and showed these changes that might have
> contibuted to my problem;
>
> -There are some changes in fbcon. Made modular along with some fixes and
> some vesafb fixes.
>
> -Accel wrapper is now intergarted into fbcon.c. VESA fb fixes
>
> -Made fbcon modular.
>
> -New NVIDIA and Radeon cards pci ids. Soon I will add support for these :-)
> Also a needed fix for fbcon.c.
>
> -Moved AGP and DRM code back to drivers/char until a proper solution is
> done for handling AGP/DMA based framebuffer devices.
>
> Almost all changes by the same developer <jsimmons>. I've been looking
> at the source differences but the introduction of the fbcon module really
> complicates the matter.
>
> I was wondering where to go about reporting the
> problem or where this issue might stem from. (i.e. the includes shown in
> vesafb.h, vesafb.h itself, fb.h or the fbcon module related code.
>
> Or would it be best to just mail the developer? :)
> Any help is appreciated.
>
> Regards,
>
> P.S.: Here is the part of my original mail describing the problem. It has
> been confirmed by two other submits to this mailinglist regarding the
> 2.6.0-test4 kernel. I'm using the 2.6.0.-bk3 kernel myself.
>
> >The most apparent occurrence of the problem for me is when
> >running mc (Midnight Commander). The blue blackground isn't drawn in the
> >parts where there is no text. When using mcedit this comes all the more
> > clear and  particularly when scrolling is done. The space which hasn't
> > got any text is replaced with RGB pixels (looks grey from a distance). If
> > you jump back from one console and back again the screen is redrawn
> > correctly.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Attachment: blue.png
Description: PNG image

Attachment: bottom.png
Description: PNG image

Attachment: red.png
Description: PNG image