Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753517AbYBQSUH (ORCPT ); Sun, 17 Feb 2008 13:20:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751072AbYBQST4 (ORCPT ); Sun, 17 Feb 2008 13:19:56 -0500 Received: from iabervon.org ([66.92.72.58]:46310 "EHLO iabervon.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751011AbYBQST4 (ORCPT ); Sun, 17 Feb 2008 13:19:56 -0500 Date: Sun, 17 Feb 2008 13:19:55 -0500 (EST) From: Daniel Barkalow To: Frans Pop cc: linux-kernel@vger.kernel.org Subject: Re: [REGRESSION 2.6.23] no vga console and no messages In-Reply-To: Message-ID: References: <200802171848.16969.elendil@planet.nl> User-Agent: Alpine 1.00 (LNX 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 817 Lines: 17 As far as I can tell, the only differences in either dmesg or lspci between the broken one and the working one are the phrasing of messages, not what's happening. Out of curiousity, what do you see for the "Console: " line when you boot? It's possible that the VGA console code somehow got broken for both of us in 2.6.23, and this means that (a) my console doesn't work, since I'm trying to use it, and (b) if your framebuffer console tries to match your VGA console, it'll break, because your VGA console is broken. -Daniel *This .sig left intentionally blank* -- 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/