All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: trash can <thetrashcan@earthlink.net>
Cc: Robert Hancock <hancockr@shaw.ca>,
	linux-kernel@vger.kernel.org, ide <linux-ide@vger.kernel.org>
Subject: Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
Date: Tue, 11 Dec 2007 11:54:41 -0500	[thread overview]
Message-ID: <475EC0D1.8010200@rtr.ca> (raw)
In-Reply-To: <475EAEDD.9090905@earthlink.net>

trash can wrote:
..
> Robert Hancock wrote:
>> That is rather curious. There's no sign of any libata error handling
>> going on.. Maybe the drive is actually returning that error code in the
>> ATAPI CDB, or at least we think it is?
>>
>> You are sure that this drive still works with older kernels using
>> drivers/ide, and that the hardware didn't break at some point, I assume?
>>
> Thanks for your time. I get a kernel panic with the controller mode in BIOS
> set to AHCI with Fedora Core 6. Once returned to IDE (setting used since
> computer was built) I booted up. Added information: In Fedora 7 I can not
> burn DVDs or CDROM using K3b with the Zip drive connected. Some
> preformatting (I assume) is done rendering the CD/DVD useless then got an
> I/O error. In Fedora 8 I am able to burn a CDROM using K3b but DVDs behave
> as with Fedora 7. All is well when the Zip is totaly removed. This Zip
> drive also worked under Microsoft 2000 { which was removed over a year
> ago ;-) }. Fedora Core 6, Fedora 7, and Fedora 8 are all installed on
> this machine. This drive did not work with a Ubuntu 7.10 Live CD on this
> machine. I intend to try this Zip drive on another motherboard with the
> above live CD.
...

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?.

Cheers

  reply	other threads:[~2007-12-11 16:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.yONLBG7CMuz80f4dUP5r/5k7emw@ifi.uio.no>
2007-12-11  0:21 ` Iomega ZIP-100 drive unsupported with jmicron JMB361 chip? Robert Hancock
2007-12-11 15:38   ` trash can
2007-12-11 16:54     ` Mark Lord [this message]
2007-12-11 16:57       ` Mark Lord
2007-12-11 19:05         ` trash can
2007-12-11 19:30           ` Mark Lord
2007-12-12 19:23             ` trash can
2007-12-17  0:50               ` Bill Davidsen
2007-12-15  4:31             ` trash can
2007-12-10 20:09 trash can
2007-12-17  9:00 ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=475EC0D1.8010200@rtr.ca \
    --to=liml@rtr.ca \
    --cc=hancockr@shaw.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thetrashcan@earthlink.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.