Date: 01 Nov 2002 14:39:29 +1030 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Forrest Aldrich <forrie@forrie.com> Cc: freebsd-stable@freebsd.org Subject: Re: Unrecognized CPU Class (and a disc error) Message-ID: <1036123769.1736.151.camel@chowder.localdomain> In-Reply-To: <5.1.1.6.2.20021031230137.01ff0440@192.168.1.1> References: <5.1.1.6.2.20021031225359.01fd6ea0@192.168.1.1> <5.1.1.6.2.20021031223636.01fdb7c0@192.168.1.1> <5.1.1.6.2.20021031225359.01fd6ea0@192.168.1.1> <5.1.1.6.2.20021031230137.01ff0440@192.168.1.1>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2002-11-01 at 14:32, Forrest Aldrich wrote: > I'll go in to the data center tomorrow and check the cables and BIOS -- I'm > sure they were okay. > > If this is a FreeBSD error (and I'm not certain yet) - what was your fix > for this - will this cause problems with the system? I ran atacontrol and forced it down to UDMA33.. Or rather, I ran atacontrol and forced it UP to UDMA33 - the first access failed so it went to PIO4 - those accesses are fine, but it could do UDMA33 safely. I'm not sure if this is a bug with the code which does cable detection, or whether it is a properly of the IDE chip. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1036123769.1736.151.camel>