DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=JJzX+l25QezRVz8WFDGMtbH95gilmJ02MpUhWwtwsrLDT6ydnktv3MpGKOZWYrDsZR6DxwctRAXohIoh2xGIqLQrX+raIrfxKwBvdUBoh054EpJKCpCMrN9p2uN83TR7OYXgwlbp7XDbk9Zd0h9EbxfP8D6HosLwMKh9WMI2iMA=
Message-ID: <60f2b0dc0605021251i1c883617vf132e8bdeffd6c7f@mail.gmail.com>
Date: Tue, 2 May 2006 21:51:13 +0200
From: "Olivier Fourdan" <fourdan@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: framebuffer broken in 2.6.16.x and 2.6.17-rc3 ?
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 862
Lines: 22

hi all,

Sorry if this has been already covered recently, but it seems that the
framebuffer doesn't work anymore in 2.6.16.9 and 2.6.17-rc3, while it
worked in 2.6.16 at least.

I'm surprised noone has raised that issue yet, so I'm wondering if I'm
missing something obvious :) When using the fb in 2.6.16.x and
2.6.17-rc3, the screen stays just black, nothing is displayed... I'm
using the regular unaccelerated vesa framebuffer.

I'm wondering if this could related to the fb changes that occured
after 2.6.16 initial release and if other people are experiencing
issues with frame buffer recently.

Cheers,
Olivier.
-
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/