Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 28 Oct 2001 17:01:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 28 Oct 2001 17:01:09 -0500 Received: from nydalah028.sn.umu.se ([130.239.118.227]:58753 "EHLO x-files.giron.wox.org") by vger.kernel.org with ESMTP id ; Sun, 28 Oct 2001 17:00:57 -0500 Message-ID: <033901c15ffc$53100280$0201a8c0@HOMER> From: "Martin Eriksson" To: "David Grant" , "linux kernel mailinglist" In-Reply-To: <045301c15fa7$c2809b70$1901a8c0@node0.idium.eu.org> Subject: Re: Via KT133 and 2.4.8 and a hard disk problem ? Date: Sun, 28 Oct 2001 23:03:06 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org ----- Original Message ----- From: "David Grant" To: "David Flynn" ; "linux kernel mailinglist" Sent: Sunday, October 28, 2001 9:46 PM Subject: Re: Via KT133 and 2.4.8 and a hard disk problem ? > I've had these problems before. Can you provide a listings of the kernel > errors you are getting? I'm curious myself, and I'm sure this would help > any developers as well. Also, is it an old KT133 (with vt82c686a chip) or > KT133A (with vt82c686b chip). Actually, the KT133 revision has nothing (substantial) to do with the 686 chip. There were some motherboards with both KT133 and 686B, such as my MSI K7TPRO 2-A. There are also AMD chipsets that use the 686A/B as an IO chipset, and other VIA chipsets, such as Apollo Pro. _____________________________________________________ | Martin Eriksson | MSc CSE student, department of Computing Science | Ume? University, Sweden - 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/