[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cb7bb73a0702221108r161441ebt61886ce67746f389@mail.gmail.com>
Date: Thu, 22 Feb 2007 20:08:43 +0100
From: "Giuseppe Bilotta" <giuseppe.bilotta@...il.com>
To: "Antonino A. Daplas" <adaplas@...il.com>
Cc: "James Simmons" <jsimmons@...radead.org>,
"Luca Tettamanti" <kronos@...ple.it>,
linux-fbdev-devel@...ts.sourceforge.net,
"Andrew Morton" <akpm@...l.org>, "Dave Airlie" <airlied@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH] nvidiafb: allow ignoring EDID info
On 2/22/07, Antonino A. Daplas <adaplas@...il.com> wrote:
> On Thu, 2007-02-22 at 16:55 +0100, Giuseppe Bilotta wrote:
> >
> > However, I'm still getting the same snowy effects, which doesn't come
> > as a surprise since the actual mode timings used are just the same ...
>
> Yes, because the EDID has only 1 mode entry. But now you can use 'fbset
> 1024x768-60' (or any mode smaller than 1600x1200-60) for example and it
> should work.
No, it doesn't. I've tried all the methods from 640x480 to 1600x1200,
and they /all/ come up snowy. This is starting to look queerer and
queerer. I've also tried changing vf min and max as you suggested:
> You might want to change vfmin and vfmax to 59 and 61
and even the M and MR methods which you suggested in the other email.
Since nvidiafb is being loaded from the command line because it's a
blacklisted module otherwise, I've been using the mode_option option.
However, neither the mode_option nor fbset seem to give me anything
not snowy.
Damn.
--
Giuseppe "Oblomov" Bilotta
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists