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]

Message-ID: <47635888.6040401@earthlink.net>
Date:	Fri, 14 Dec 2007 23:31:04 -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

My apologies for the delay. I thought this was posted on the twelfth but
there was an email client problem.

Success!
I downloaded kernel-2.6.24-0.81.rc4.git7.fc9.src.rpm from the Fedora
development tree. Went through "rpm dependecy hell" and solved all
dependencies by installing other fc9 rpms. I used
config-2.6.23.1-42.fc8 as my starting point. My
config-2.6.24-0.81.rc4.git7.local.fc8 is attached.

After compilation and installation of the kernel rpm, upon boot I could
see a device sdc4 being created, but boot failed with
mount: missing mount point, some errors in mounting from setuproot and
switchroot.

I believe the problem was with the Red Hat/Fedora annaconda installer
and/or grub, and my multiboot machine setup. I had not been able to boot
updated fc8 kernel packages, only the originally installed kernel.
Note that my Fedora 7 and Fedora 8 distributions share no directories
(one exception) and all this work is taking place in the Fedora 8
distribution. The /boot partition IS shared among my distributions.
I found my /etc/fstab file had two "/" mount point entries. The last line
contained LABEL=/ and is a reference to my Fedora 7 root partition.
I deleted this line from fstab as I did not want to change the mount
point for this line to mount my Fedora 7 distribution on Fedora 8.
The kernel installation process was appending LABEL=/ to my kernel line
in grub.conf:
kernel /vmlinuz-2.6.24-0.81.rc4.git7.local.fc8 ro root=/dev/VGf800/LogVol00 rhgb quiet LABEL=/

LABEL=/ was removed from the line.

I then needed to recreate my initrd image:
mkinitrd /boot/initrd-2.6.24-0.81.rc4.git7.local.fc8.img \
  2.6.24-0.81.rc4.git7.local.fc8

Finally I was able to boot (Zip disk inserted) to the local kernel and the
Zip drive works.

# blkid
/dev/sdc4: SEC_TYPE="msdos" LABEL="ZIP-100" UUID="4910-1305" TYPE="vfat"

dmesg:
ata9.00: ATAPI: LITE-ON DVDRW SOHW-1693S, KS0B, max UDMA/66
ata9.01: ATAPI: IOMEGA  ZIP 100       ATAPI, 05.H, max MWDMA1, CDB intr
ata9.00: limited to UDMA/33 due to 40-wire cable
ata9.00: configured for UDMA/33
ata9.01: configured for MWDMA1
scsi 8:0:0:0: CD-ROM            LITE-ON  DVDRW SOHW-1693S KS0B PQ: 0 ANSI: 5
scsi 8:0:1:0: Direct-Access     IOMEGA   ZIP 100          05.H PQ: 0 ANSI: 5
sd 8:0:1:0: [sdc] 196608 512-byte hardware sectors (101 MB)
sd 8:0:1:0: [sdc] Write Protect is off
sd 8:0:1:0: [sdc] Mode Sense: 00 40 00 00
sd 8:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 8:0:1:0: [sdc] 196608 512-byte hardware sectors (101 MB)
sd 8:0:1:0: [sdc] Write Protect is off
sd 8:0:1:0: [sdc] Mode Sense: 00 40 00 00
sd 8:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdc: sdc4

My thanks to all the great people who solved this problem and those who patiently
responded to my queries.

- -RoyBoy626
Mark Lord wrote:
> 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.
> ..
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHY1h6z1/aqdDsM3URAqyGAKC5D17UMMxkp8AO8D5OnyZaDbtEWQCdHQuD
NqN3+HX8DVhICS8rGmgDXe8=
=gUUP
-----END PGP SIGNATURE-----

View attachment "config-2.6.24-0.81.rc4.git7.local.fc8" of type "text/plain" (82372 bytes)