Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263999AbTIIKTj (ORCPT ); Tue, 9 Sep 2003 06:19:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263997AbTIIKTj (ORCPT ); Tue, 9 Sep 2003 06:19:39 -0400 Received: from mailgw.cvut.cz ([147.32.3.235]:15762 "EHLO mailgw.cvut.cz") by vger.kernel.org with ESMTP id S263999AbTIIKTi (ORCPT ); Tue, 9 Sep 2003 06:19:38 -0400 From: "Petr Vandrovec" Organization: CC CTU Prague To: Zoup Date: Tue, 9 Sep 2003 12:19:05 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Frame Buffer Problem . Cc: linux-kernel@vger.kernel.org X-mailer: Pegasus Mail v3.50 Message-ID: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1148 Lines: 25 On 9 Sep 03 at 13:37, Zoup wrote: > got blank screen when enable Frame Buffer console on 2.6.0-test5 :) > Config file attached . Do not enable vga16, vesafb and riva together. Decided for only one of them, and use just that one. Although your configuration should give you /dev/fb0 on riva, /dev/fb1 on vesafb and /dev/fb2 on vga16, it looks like that you got reordered framebuffers somehow. Did not you pass 'video=vga16fb:XXXX' option to the kernel? What kernel cmdline you used? Other possibility is that vga16 setup confused your hardware enough for picture to disappear... Doing 'cat /proc/fb > /non-working-fbs; dmesg >> /non-working-fbs' after you boot your system with non-working display could give us clue what's going on. But in any case, do not use more than one fbdev... Petr Vandrovec - 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/