From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261365AbTEAPVT (ORCPT ); Thu, 1 May 2003 11:21:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261369AbTEAPVT (ORCPT ); Thu, 1 May 2003 11:21:19 -0400 Received: from deviant.impure.org.uk ([195.82.120.238]:6303 "EHLO deviant.impure.org.uk") by vger.kernel.org with ESMTP id S261365AbTEAPVS (ORCPT ); Thu, 1 May 2003 11:21:18 -0400 Date: Thu, 1 May 2003 16:32:49 +0100 From: Dave Jones To: Daniel Taylor Cc: linux-kernel@vger.kernel.org Subject: Re: Boot failure, VIA chipset. Message-ID: <20030501153249.GA19001@suse.de> Mail-Followup-To: Dave Jones , Daniel Taylor , linux-kernel@vger.kernel.org References: <20030430214848.GB24111@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 01, 2003 at 05:53:53AM -0400, Daniel Taylor wrote: > > CONFIG_INPUT=y > > CONFIG_VT=y > > CONFIG_VT_CONSOLE=y > > > All enabled, and I tried last night with a stripped down 386 only kernel. > > No dice, dies hard even before printing the Kernel ID. > > It is probably a BIOS compatability issue, but it works OK with 2.4. Since > the system actually works as it sits I've been taking my time debugging > the 2.5 issues. The only other outstanding hang that I've seen was caused by ACPI. Does it boot with acpi=off ? Dave