Re: Re: cyblafb in kernel 2.6.16: corrupted display in Xfree86

[Knut Petersen <Knut_Petersen@t-online.de>]

Thomas Arendsen Hein schrieb:

>>/sbin/modprobe cyblafb && /usr/sbin/fbset -a 1280x1024-85 -depth 16
>>    
>>
>
>works
>
>  
>
>>/sbin/modprobe cyblafb && /usr/sbin/fbset -g 1152 864 1152 864 8 -t 10000 
>>168 40 57 13 152 11
>>    
>>
>
>doesn't work
>
>  
>
>>/sbin/modprobe cyblafb && /usr/sbin/fbset -g 1152 864 1152 864 16 -t 10000 
>>168 40 57 13 152 11
>>    
>>
>
>works
>
>  
>
>>/sbin/modprobe cyblafb && /usr/sbin/fbset -g 1152 864 2048 4096 8 -t 10000 
>>168 40 57 13 152 11
>>    
>>
>
>doesn't work
>
>  
>
>>/sbin/modprobe cyblafb && /usr/sbin/fbset -g 1152 864 2048 2048 16 -t 10000 
>>168 40 57 13 152 11
>>    
>>
>
>works
>
>With /sbin/modprobe cyblafb && /usr/sbin/fbset -a 1152x864-70 -depth 16
>(changing fb.modes would probably help, too) everything is back to
>normal for me.
>
>I think the extra colors on console won't hurt, now that I know
>about the 2048/4096 setting.
>
>  
>
So the problem is that the 8bpp modes do not work with the
X framebuffer driver. Please report that bug, I think X is responsible.

>>Is there a special reason not to use the X* trident driver?
>>    
>>
>
>Yes, I had crashes when using more than one X display (e.g. one
>local xdm and one "X -query other :1"), 
>
Try it again, the recent cyblafb works around X and xdm bugs
that could have caused that crashes.

>and switching between X and
>console is _much_ faster this way.
>
>  
>
I doubt that ... switching between X trident and cyblafb and back again
takes only a few miliseconds here.

cu,
 knut


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642