linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Arendsen Hein <thomas@intevation.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: cyblafb in kernel 2.6.16: corrupted display in Xfree86
Date: Thu, 23 Mar 2006 00:48:12 +0100	[thread overview]
Message-ID: <20060322234812.GB2361@intevation.de> (raw)

Hi!

The cyblafb driver workes fine for me up to Linux kernel 2.6.15.6,
but with 2.6.16 I get the following problem:

After booting the system, the framebuffer console comes up fine, but
when xdm starts up the X server, I get this diplay:
http://ftp.intevation.de/users/thomas/cyblafb/cyblafb-1.jpg

After switching to the console with Ctrl-Alt-F1 and back to X:
http://ftp.intevation.de/users/thomas/cyblafb/cyblafb-2.jpg

When I use Ctrl-Alt-Backspace to restart xdm everything looks fine:
http://ftp.intevation.de/users/thomas/cyblafb/cyblafb-3.jpg

I use Debian sarge on a Lex Light (CV860A board):
0000:01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a) (prog-if 00 [VGA])
        Subsystem: Trident Microsystems CyberBlade/i1
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 5
        Memory at e4000000 (32-bit, non-prefetchable) [size=8M]
        Memory at e5000000 (32-bit, non-prefetchable) [size=128K]
        Memory at e4800000 (32-bit, non-prefetchable) [size=8M]
        Expansion ROM at 10000000 [disabled] [size=64K]
        Capabilities: <available only to root>


Resolution 1152x864 pixels (16 bpp) with fbdev driver in XF86Config-4.

/etc/fb.modes:
mode "1152x864-70"
    # D: 100.0 MHz, H: 66.138 kHz, V: 69.99 Hz
    geometry 1152 864 1152 864 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
(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

-- 
Email: thomas@intevation.de
http://intevation.de/~thomas/


-------------------------------------------------------
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-22 23:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22 23:48 Thomas Arendsen Hein [this message]
2006-03-23  8:34 ` cyblafb in kernel 2.6.16: corrupted display in Xfree86 Knut Petersen
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=20060322234812.GB2361@intevation.de \
    --to=thomas@intevation.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).