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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 11 Dec 2007 14:30:40 -0500
From:	Mark Lord <liml@....ca>
To:	trash can <thetrashcan@...thlink.net>
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?

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