linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Knut Petersen <Knut_Petersen@t-online.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: cyblafb in kernel 2.6.16: corrupted display in Xfree86
Date: Thu, 23 Mar 2006 09:34:53 +0100	[thread overview]
Message-ID: <44225DAD.8080004@t-online.de> (raw)
In-Reply-To: <20060322234812.GB2361@intevation.de>

Hi Thomas!

>/etc/fb.modes:
>mode "1152x864-70"
>    # D: 100.0 MHz, H: 66.138 kHz, V: 69.99 Hz
>    geometry 1152 864 1152 864 8
>  
>
That is very slow. Use geometry 1152 864 2048 4096 8

>    timings 10000 168 40 57 13 152 11
>    hsync high
>    vsync high
>endmode
>
>To enable this resolution I use:
>
>/etc/rcS.d/S42cyblafb:
>/sbin/modprobe cyblafb bpp=16 mode=1024x768 ref=85 && /usr/sbin/fbset -a 1152x864-70
>  
>

/sbin/modprobe cyblafb && /usr/sbin/fbset -a 1152x864-70 should be 
sufficient.

>(because the cyblafb driver doesn't understand mode=1152x864 as parameter)
>
>XFree86 is standard Debian sarge: 4.3.0.dfsg.1-14sarge1
>
>One further thing to note is that I compiled 2.6.15.6 with gcc
>2.95.4 and 2.6.16 with gcc 3.4.3, can this make a difference?
>
>Any idea what's happening here?
>
>Regards,
>Thomas
>
>  
>

I cannot test 1152x864 on my system because my monitor does not understand
that resolution. But if it worked previously it should work now ;-)

Are there any problems on the framebuffer console? You wrote that the fb 
console
comes up fine, but please confirm that scrolling is ok.

Are there any problems left after you reach the state of your third 
picture? Switching
between the fb console and X works flawlessly then?

Are there any problems if you use the standard resolutions, eg 1024x768 
or 1280x1024?

Try a fbset -vxres 2048 -vyres 4096  after your first fbset. Does that 
change anything?

Please send dmesg logs of kernel 2.6.15.6 and 2.6.16 after adding 
verbosity=2
to the modprobe of cyblafb - everything from the point of loading 
cyblafb to your third
picture. Also include the X server logs. Maybe it´s a good idea to send 
those logs to my
private address Knut_Petersen@t-online.de.

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

  reply	other threads:[~2006-03-23  8:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22 23:48 cyblafb in kernel 2.6.16: corrupted display in Xfree86 Thomas Arendsen Hein
2006-03-23  8:34 ` Knut Petersen [this message]
2006-03-23 12:52   ` Thomas Arendsen Hein
2006-03-23 14:57     ` Knut Petersen
2006-03-23 16:03       ` Thomas Arendsen Hein
2006-03-23 16:57         ` Knut Petersen
2006-03-23 18:39           ` Thomas Arendsen Hein
2006-03-23 18:50             ` Thomas Arendsen Hein
2006-03-23 23:37               ` Antonino A. Daplas
2006-03-23 22:46             ` Knut Petersen

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=44225DAD.8080004@t-online.de \
    --to=knut_petersen@t-online.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).