linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: trash can <thetrashcan@earthlink.net>
To: Mark Lord <liml@rtr.ca>
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 14:05:26 -0500	[thread overview]
Message-ID: <475EDF76.4000703@earthlink.net> (raw)
In-Reply-To: <475EC163.8070305@rtr.ca>

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

Removed the DVD drive and jumpered the Zip drive to Master. BIOS
set to IDE. Fedora 8 with nash on boot:
Buffer I/O error on dev/sdc locaical block 0

dmesg:
Buffer I/O error on device sdc, logical block 0
sd 4:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sd 4:0:0:0: [sdc] Sense Key : Hardware Error [current]
sd 4:0:0:0: [sdc] Add. Sense: Scsi parity error
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
sd 4:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sd 4:0:0:0: [sdc] Sense Key : Hardware Error [current]
sd 4:0:0:0: [sdc] Add. Sense: Scsi parity error
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
Dev sdc: unable to read RDB block 0

udev creates a /dev/sdc only.

With DVD removed and BIOS set to AHCI device changes to sda
Fedora 8: nash:
Buffer I/O error on device sda, logical block 0

dmesg:
Buffer I/O error on device sda, logical block 0
sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sd 0:0:0:0: [sda] Sense Key : Hardware Error [current]
sd 0:0:0:0: [sda] Add. Sense: Scsi parity error
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
Dev sda: unable to read RDB block 0


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.
> 
> This exact same mobo was used for a while with a PATA DVD-RW (no ZIP drive)
> under older kernels using drivers/IDE, but was unreliable in that
> configuration
> (Ubuntu Edgy).   Ditto when the PATA DVD-RW was replaced with a SATA
> DVD-RW.
> 
> -ml
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHXt92z1/aqdDsM3URAvoNAKD4jBHDbhppOx6Fa8URPjbgN+jc9gCdEc6s
HomNnFPdQEDa6m8aJKB+vLM=
=PkYa
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-12-11 19:07 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
2007-12-11 16:57       ` Mark Lord
2007-12-11 19:05         ` trash can [this message]
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=475EDF76.4000703@earthlink.net \
    --to=thetrashcan@earthlink.net \
    --cc=hancockr@shaw.ca \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).