From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Lord Subject: Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip? Date: Tue, 11 Dec 2007 14:30:40 -0500 Message-ID: <475EE560.6040601@rtr.ca> References: <475DD7FF.4030906@shaw.ca> <475EAEDD.9090905@earthlink.net> <475EC0D1.8010200@rtr.ca> <475EC163.8070305@rtr.ca> <475EDF76.4000703@earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from rtr.ca ([76.10.145.34]:2506 "EHLO mail.rtr.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751007AbXLKTal (ORCPT ); Tue, 11 Dec 2007 14:30:41 -0500 In-Reply-To: <475EDF76.4000703@earthlink.net> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: trash can Cc: Robert Hancock , linux-kernel@vger.kernel.org, ide trash can wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Thanks for the note. Zip drive as only device on the bus did not work > for me. kernel is correctly identifying the Jmicron chip. .. So have you tried 2.6.24-rc* on that system yet, using only libata ? > Mark Lord wrote: >> Mark Lord wrote: >>> I missed the early part of this thread, >>> but here is a data point that may or may not be useful. >>> >>> I have an ASUS mobo here with an onboard JM363 SATA/PATA controller >>> (verified by looking at the actual chip). >>> >>> It works fine when in AHCI mode with a PATA ATAPI ZIP100 drive >>> all by itself. No other configurations tested. >>> This is with kernel 2.6.24-rc4-git?. >> .. >> >> Oh yeah.. that's with libata controlling all drives in the system. ..