From owner-freebsd-hackers Sat Dec 1 4: 6:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 0958837B416 for ; Sat, 1 Dec 2001 04:06:16 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.6) id fB1C5r243828; Sat, 1 Dec 2001 13:05:53 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200112011205.fB1C5r243828@freebsd.dk> Subject: Re: UDMA33 and SiS5591 on FreeBSD 4.4-RELEASE In-Reply-To: To: Zwane Mwaikambo Date: Sat, 1 Dec 2001 13:05:53 +0100 (CET) Cc: freebsd-hackers@freebsd.org Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Zwane Mwaikambo wrote: > Hi, > I've got a box which boots up with UDMA33 but during the boot > sequence gets write problems and ends up disabling it and i presume > falling back to PIO4. I've tested the same box on Linux 2.4.2+ and have > had no problems running it at UDMA33. > > Host: SiS 5591 (revision?) > Disk: Seagate 3.2G ATA2 Ohhh, I need alot more info before I can tell whats going on.. I need at least the dmesg from a verbosely booted system and also a pciconf -l to tell what chips you have. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message