linux-kernel - Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <475EDF76.4000703@earthlink.net>
Date:	Tue, 11 Dec 2007 14:05:26 -0500
From:	trash can <thetrashcan@...thlink.net>
To:	Mark Lord <liml@....ca>
CC:	Robert Hancock <hancockr@...w.ca>, linux-kernel@...r.kernel.org,
	ide <linux-ide@...r.kernel.org>
Subject: Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?

-----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-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/