From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Giuseppe Bilotta <bilotta78@hotpop.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Blanky rivafb vs snowy nvidiafb with 2.6.12
Date: Thu, 29 Sep 2005 20:40:49 +0800 [thread overview]
Message-ID: <433BE0D1.1070501@gmail.com> (raw)
In-Reply-To: <1gie1vr78iijd$.qcvoypipyouu.dlg@40tude.net>
Giuseppe Bilotta wrote:
> On Thu, 29 Sep 2005 05:01:15 +0800, Antonino A. Daplas wrote:
>
>> Giuseppe Bilotta wrote:
>
> So as you can see the problem is that the timings are NOT set by
> fbset. No error messages or anything.
>
Sorry about the blank reply, hit send accidentally.
Probably, the EDID block is incomplete, so nvidiafb is refusing
custom modes. You can change the #undef DEBUG to #define DEBUG
in drivers/video/fbmon.c to see verbose output of the EDID block in
dmesg.
Then, can you recompile without the DDC/I2C support, and boot with:
video=nvidiafb:1600x1200-60, then play with fbset later on.
If possible, you can also get the latest git snapshot then boot with:
video=nvidiafb:1600x1200MR
Note the appended MR - it's CVT with reduced blanking - which is
for LCD displays especially those manufactured by Dell since they
are the proponents of CVT.
Tony
next prev parent reply other threads:[~2005-09-29 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 14:12 Blanky rivafb vs snowy nvidiafb with 2.6.12 Giuseppe Bilotta
2005-09-28 21:01 ` Antonino A. Daplas
2005-09-29 11:41 ` Giuseppe Bilotta
2005-09-29 12:39 ` Antonino A. Daplas
2005-09-29 12:40 ` Antonino A. Daplas [this message]
2005-09-29 15:43 ` Giuseppe Bilotta
2005-09-29 20:47 ` Antonino A. Daplas
2005-09-30 8:53 ` Giuseppe Bilotta
2005-10-01 5:49 ` Antonino A. Daplas
2005-10-01 7:07 ` Giuseppe Bilotta
2005-10-01 10:49 ` Antonino A. Daplas
2005-10-02 15:13 ` Giuseppe Bilotta
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=433BE0D1.1070501@gmail.com \
--to=adaplas@gmail.com \
--cc=bilotta78@hotpop.com \
--cc=linux-kernel@vger.kernel.org \
/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).