Date: Thu, 23 Oct 2008 10:04:59 +0200
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Robert Moss <robert.von.moss@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Framebuffer issues in 2.6.26 with uvesafb and vesafb. Linux is about choice!
Message-ID: <20081023080459.GC5073@const.bordeaux.inria.fr>
Mail-Followup-To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Robert Moss <robert.von.moss@gmail.com>,
	linux-kernel@vger.kernel.org
References: <6ffd69180810230054s3b6aff5y880a898c3fc66a37@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <6ffd69180810230054s3b6aff5y880a898c3fc66a37@mail.gmail.com>
User-Agent: Mutt/1.5.12-2006-07-14
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 756
Lines: 18

Robert Moss, le Thu 23 Oct 2008 00:54:56 -0700, a ?crit :
> Anyhow, I noticed that vesafb is no longer a part of the kernel.

That's not true. It works nicely on my laptop (though I don't get
the native 1280x800 resolution).

> vga=791 still gave a mode not found.

Then that's a bug, which is a completely different thing. Could you
check that the output of vga=ask and typing scan at the boot prompt is
the same between 2.6.24 and 2.6.25/26??

Samuel, who may want to try 2.6.24 to get his native resolution.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/