From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 07:20:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED4D016A469 for ; Wed, 31 Oct 2007 07:20:39 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp1.yandex.ru (smtp1.yandex.ru [213.180.223.87]) by mx1.freebsd.org (Postfix) with ESMTP id 39A8013C4A3 for ; Wed, 31 Oct 2007 07:20:38 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:47809 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S8373911AbXJaHPy (ORCPT ); Wed, 31 Oct 2007 10:15:54 +0300 X-Comment: RFC 2476 MSA function at smtp1.yandex.ru logged sender identity as: bu7cher Message-ID: <47282B93.3010801@yandex.ru> Date: Wed, 31 Oct 2007 10:15:31 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: =?KOI8-R?Q?=3F=3F=3F_Bill_Hacker?= References: <4725558F.6040702@fusiongol.com> <4726BEEE.3070704@yandex.ru> <472778F7.9030405@conducive.net> In-Reply-To: <472778F7.9030405@conducive.net> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Nathan Butcher , freebsd-current@freebsd.org, blacknova@tut.by, Mark Powell Subject: Re: Problem with ATAPI device on JMicron JMB363 on 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 07:20:40 -0000 Bill Hacker wrote: > There seem to also be certain 'proprietary' (I hope...) issues with that > MB BIOS. We had tested combinations of BIOS settings extensively, using > PATA CDR, PATA HDD, PATA <==> SATA converters, and SATA HDD - even an > aged IDE Zip. Yes. Several people reported that theirs issues with jmb363 was fixed after BIOS update. And seem that the "last" BIOS is not mean "stable". -- WBR, Andrey V. Elsukov