From: "Nathanael D. Noblet" <nathanael@gnat.ca>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: linux-fbdev-devel@lists.sourceforge.net, directfb-users@directfb.org
Subject: Re: Re: [directfb-users] Framebuffer woes...
Date: Wed, 19 Oct 2005 12:11:41 -0700 [thread overview]
Message-ID: <1129749102.25223.7.camel@localhost.localdomain> (raw)
In-Reply-To: <4355E708.1000702@t-online.de>
On Wed, 2005-10-19 at 08:26 +0200, Knut Petersen wrote:
> Hi Nathanael,
>
> >>I have a VIA EPIA board. It has a built in Trident graphics adapter. The
> >>problem I'm having is that when I try to get it to run, the lcd OSD
> >>throws up an error message about 'Out Of Range', sometimes blanking the
> >>screen, sometimes not.
> >>
> >>
> >>
>
> What kind of Epia? I suppose Epia 800 or Epia 5000. If that´s the case,
> disable
> tridentfb and enable the cyblafb driver included in the 2.6.14-rc kernels.
>
> >>mode "1024x768-76"
> >> # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz
> >> geometry 1024 768 1024 768 16
> >> timings 12714 128 32 16 4 128 4
> >> rgba 5/11,6/5,5/0,0/0
> >>endmode
> >>
> >>
> >>
> Add
> video=cyblafb:1024x768,bpp=16,ref=76
> to the kernel command line. If that does not help immediately, use
> video=cyblafb:1024x768,bpp=16,ref=76,verbosity=2 vga=0x317
> and send complete dmesg output after booting as well as lspci -vv output.
>
> There will be a lot of debugging output, be sure to use a big enough
> buffer size for kernel messages.
>
> >>All of those (regardless of depth (8,16,24) all produce 'out of range'
> >>problems.
> >>
> >>
> >>
> tridentfb timing calcualtion was broken in 2.4 kernels and is broken for
> 2.6 kernels,
> at least for the cyberblade/i1.
Well thank you SOO much. I'm not done yet, but those messages are gone.
I will continue testing & working on this, if I run into more problems
or bugs I'll post any feedback/information I have.
--
Nathanael D. Noblet
Gnat Solutions, Inc
http://www.gnat.ca/
T 250.385.4613
C 250.383.4613
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
prev parent reply other threads:[~2005-10-19 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1129687824.25556.32.camel@localhost.localdomain>
2005-10-19 5:01 ` [directfb-users] Framebuffer woes Antonino A. Daplas
2005-10-19 6:26 ` Knut Petersen
2005-10-19 19:11 ` Nathanael D. Noblet [this message]
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=1129749102.25223.7.camel@localhost.localdomain \
--to=nathanael@gnat.ca \
--cc=Knut_Petersen@t-online.de \
--cc=directfb-users@directfb.org \
--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