Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
On Mon, 10 Dec 2007 15:09:43 -0500 trash can <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I have tolerated this problem for a year and do not post to this list in > haste. I have posted on forums and searched the community over the past > year. Your report is welcome - thanks. Let's cc the IDE/sata development list. > I have looked at the list archive on gossamer-threads.com for > solutions. With Fedora Core 6 unsupported (the last kernel for which my > zip drive worked), it is time for my last attempt at a solution. Please > CC: any response as I have not joined the list. I have compiled a > kernel-debug RPM and can run this if its output would help. Thank you > for any time you might devote to this problem. > > motherboard: MSI P965 Platinum/Intel P965 Express Chipset Based (MS-7238 > series) > Fedora 8 : kernel 2.6.23.1-42.fc8 > Iomega Zip drive internal Model Z100ATAPI > > lspci > 03:00.0 SATA controller: JMicron Technologies, Inc. JMB361 AHCI/IDE (rev 02) > 03:00.1 IDE interface: JMicron Technologies, Inc. JMB361 AHCI/IDE (rev 02) > > # lsmod | grep ata > pata_jmicron8257 0 > ata_generic 8901 0 > ata_piix 16709 0 > libata 99633 4 ahci,pata_jmicron,ata_generic,ata_piix > scsi_mod 119757 4 sr_mod,sg,libata,sd_mod > > I have recently changed the BIOS setting for the SATA#1 Controller from > [IDE] to [AHCI] with no effect. I assume AHCI is correct? > > Text below attached as text.txt for readability. > from dmesg: > libata version 2.21 loaded. > device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] > PCI: Enabling device :03:00.1 ( -> 0001) > ACPI: PCI Interrupt :03:00.1[B] -> GSI 17 (level, low) -> IRQ 17 > PCI: Setting latency timer of device :03:00.1 to 64 > scsi0 : pata_jmicron > scsi1 : pata_jmicron > ata1: PATA max UDMA/100 cmd 0x0001cc00 ctl 0x0001c882 bmdma 0x0001c400 irq 17 > ata2: PATA max UDMA/100 cmd 0x0001c800 ctl 0x0001c482 bmdma 0x0001c408 irq 17 > ata1.00: ATAPI: LITE-ON DVDRW SOHW-1693S, KS0B, max UDMA/66 > ata1.01: ATAPI: IOMEGA ZIP 100 ATAPI, 05.H, max MWDMA1, CDB intr > ata1.00: configured for UDMA/66 > ata1.01: configured for MWDMA1 > scsi 0:0:0:0: CD-ROMLITE-ON DVDRW SOHW-1693S KS0B PQ: 0 ANSI: 5 > scsi 0:0:1:0: Direct-Access IOMEGA ZIP 100 05.H PQ: 0 ANSI: 5 > sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) > sd 0:0:1:0: [sda] Write Protect is off > sd 0:0:1:0: [sda] Mode Sense: 00 40 00 00 > sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support > DPO or FUA > sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) > sd 0:0:1:0: [sda] Write Protect is off > sd 0:0:1:0: [sda] Mode Sense: 00 40 00 00 > sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support > DPO or FUA > sda:<6>sd 0:0:1:0: [sda] Result: hostbyte=DID_OK > driverbyte=DRIVER_SENSE,SUGGEST_OK > sd 0:0:1:0: [sda] Sense Key : Hardware Error [current] > sd 0:0:1: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 > > If a disk is inserted into the drive (/var/log/messages) > Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Spinning up > disk.<5>sd 0:0:1:0: [sda] Spinning up diskready > Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] 196608 512-byte hardware > sectors (101 MB) > Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write Protect is off > Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write cache: enabled, > read cache: enabled, doesn't support DPO or FUA > Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] 196608 512-byte hardware > sectors (101 MB) > Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write Protect is off > Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write cache: enabled, > read cache: enabled, doesn't support DPO or FUA > Dec 10 14:22:53 localhost kernel: sda:<6>sd 0:0:1:0: [sda] Result: > hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK > Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Sense Key : Hardware > Error [current] > Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Add. Sense: Scsi parity > error > Dec 10 14:22:53 localhost kernel: end_request: I/O error, dev sda, sector 0 > Dec 10 14:22:53 localhost kernel: printk: 42 messages suppressed. > Dec 10 14:22:53 localhost kernel: Buffer I/O error on device sda, logical > block 0 > So which is the most recent kernel version which worked OK? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
On Mon, 10 Dec 2007 15:09:43 -0500 trash can [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have tolerated this problem for a year and do not post to this list in haste. I have posted on forums and searched the community over the past year. Your report is welcome - thanks. Let's cc the IDE/sata development list. I have looked at the list archive on gossamer-threads.com for solutions. With Fedora Core 6 unsupported (the last kernel for which my zip drive worked), it is time for my last attempt at a solution. Please CC: any response as I have not joined the list. I have compiled a kernel-debug RPM and can run this if its output would help. Thank you for any time you might devote to this problem. motherboard: MSI P965 Platinum/Intel P965 Express Chipset Based (MS-7238 series) Fedora 8 : kernel 2.6.23.1-42.fc8 Iomega Zip drive internal Model Z100ATAPI lspci 03:00.0 SATA controller: JMicron Technologies, Inc. JMB361 AHCI/IDE (rev 02) 03:00.1 IDE interface: JMicron Technologies, Inc. JMB361 AHCI/IDE (rev 02) # lsmod | grep ata pata_jmicron8257 0 ata_generic 8901 0 ata_piix 16709 0 libata 99633 4 ahci,pata_jmicron,ata_generic,ata_piix scsi_mod 119757 4 sr_mod,sg,libata,sd_mod I have recently changed the BIOS setting for the SATA#1 Controller from [IDE] to [AHCI] with no effect. I assume AHCI is correct? Text below attached as text.txt for readability. from dmesg: libata version 2.21 loaded. device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] PCI: Enabling device :03:00.1 ( - 0001) ACPI: PCI Interrupt :03:00.1[B] - GSI 17 (level, low) - IRQ 17 PCI: Setting latency timer of device :03:00.1 to 64 scsi0 : pata_jmicron scsi1 : pata_jmicron ata1: PATA max UDMA/100 cmd 0x0001cc00 ctl 0x0001c882 bmdma 0x0001c400 irq 17 ata2: PATA max UDMA/100 cmd 0x0001c800 ctl 0x0001c482 bmdma 0x0001c408 irq 17 ata1.00: ATAPI: LITE-ON DVDRW SOHW-1693S, KS0B, max UDMA/66 ata1.01: ATAPI: IOMEGA ZIP 100 ATAPI, 05.H, max MWDMA1, CDB intr ata1.00: configured for UDMA/66 ata1.01: configured for MWDMA1 scsi 0:0:0:0: CD-ROMLITE-ON DVDRW SOHW-1693S KS0B PQ: 0 ANSI: 5 scsi 0:0:1:0: Direct-Access IOMEGA ZIP 100 05.H PQ: 0 ANSI: 5 sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) sd 0:0:1:0: [sda] Write Protect is off sd 0:0:1:0: [sda] Mode Sense: 00 40 00 00 sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) sd 0:0:1:0: [sda] Write Protect is off sd 0:0:1:0: [sda] Mode Sense: 00 40 00 00 sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda:6sd 0:0:1:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK sd 0:0:1:0: [sda] Sense Key : Hardware Error [current] sd 0:0:1: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 If a disk is inserted into the drive (/var/log/messages) Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Spinning up disk.5sd 0:0:1:0: [sda] Spinning up diskready Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write Protect is off Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write Protect is off Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 10 14:22:53 localhost kernel: sda:6sd 0:0:1:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Sense Key : Hardware Error [current] Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Add. Sense: Scsi parity error Dec 10 14:22:53 localhost kernel: end_request: I/O error, dev sda, sector 0 Dec 10 14:22:53 localhost kernel: printk: 42 messages suppressed. Dec 10 14:22:53 localhost kernel: Buffer I/O error on device sda, logical block 0 So which is the most recent kernel version which worked OK? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
trash can wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 anaconda 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. This 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 as expected. # 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-ROMLITE-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 I've been behing reading this list, I was going to say that I have always had best luck with those drives using the old idescsi driver, although I haven't used a kernel newer than... 2.6.18 or so on the old machines. Since you have a solution I won't suggest you try that with an old kernel ;-) -- Bill Davidsen <[EMAIL PROTECTED]> "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
trash can wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 anaconda 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. This 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 as expected. # 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-ROMLITE-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 I've been behing reading this list, I was going to say that I have always had best luck with those drives using the old idescsi driver, although I haven't used a kernel newer than... 2.6.18 or so on the old machines. Since you have a solution I won't suggest you try that with an old kernel ;-) -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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.
- --RoyBoy626
Fedora Core 6 information (computer booted December 11th with Zip
disk inserted):
# uname -r
2.6.22.5-49.fc6
# blkid
/dev/hdb4: SEC_TYPE="msdos" LABEL="ZIP-100" UUID="-" TYPE="vfat"
from dmesg:
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
JMB361: IDE controller at PCI slot :03:00.1
PCI: Enabling device :03:00.1 ( -> 0001)
ACPI: PCI Interrupt :03:00.1[B] -> GSI 17 (level, low) -> IRQ 17
JMB361: chipset revision 2
JMB361: 100% native mode on irq 17
PCI: Setting latency timer of device :03:00.1 to 64
ide0: BM-DMA at 0xc400-0xc407, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xc408-0xc40f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: LITE-ON DVDRW SOHW-1693S, ATAPI CD/DVD-ROM drive
hdb: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
hda: host side 80-wire cable detection failed, limiting max speed to UDMA33
hda: selected mode 0x42
hdb: selected mode 0x21
ide0 at 0xcc00-0xcc07,0xc882 on irq 17
Probing IDE interface ide1...
Probing IDE interface ide1...
ide-floppy driver 0.99.newide
hdb: 98304kB, 196608 blocks, 512 sector size
hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
hdb: hdb4
Manual mount: mount -t vfat /dev/hdb4 /mnt/zip
/var/log/messages response: Dec 11 10:12:43 kernel: hdb: hdb4
]# df /mnt/zip
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hdb498078 11782 86296 13% /mnt/zip
All is well in Fedora Core 6.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHXq7dz1/aqdDsM3URAvV0AKDzd4PnK9/Bt7jao0OIsPrIAHxMVACfbzkY
feZlOXUDXZ9bmiArwsp+O78=
=1jws
-END PGP SIGNATURE-
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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.
- --RoyBoy626
Fedora Core 6 information (computer booted December 11th with Zip
disk inserted):
# uname -r
2.6.22.5-49.fc6
# blkid
/dev/hdb4: SEC_TYPE=msdos LABEL=ZIP-100 UUID=- TYPE=vfat
from dmesg:
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
JMB361: IDE controller at PCI slot :03:00.1
PCI: Enabling device :03:00.1 ( - 0001)
ACPI: PCI Interrupt :03:00.1[B] - GSI 17 (level, low) - IRQ 17
JMB361: chipset revision 2
JMB361: 100% native mode on irq 17
PCI: Setting latency timer of device :03:00.1 to 64
ide0: BM-DMA at 0xc400-0xc407, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xc408-0xc40f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: LITE-ON DVDRW SOHW-1693S, ATAPI CD/DVD-ROM drive
hdb: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
hda: host side 80-wire cable detection failed, limiting max speed to UDMA33
hda: selected mode 0x42
hdb: selected mode 0x21
ide0 at 0xcc00-0xcc07,0xc882 on irq 17
Probing IDE interface ide1...
Probing IDE interface ide1...
ide-floppy driver 0.99.newide
hdb: 98304kB, 196608 blocks, 512 sector size
hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
hdb: hdb4
Manual mount: mount -t vfat /dev/hdb4 /mnt/zip
/var/log/messages response: Dec 11 10:12:43 kernel: hdb: hdb4
]# df /mnt/zip
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hdb498078 11782 86296 13% /mnt/zip
All is well in Fedora Core 6.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHXq7dz1/aqdDsM3URAvV0AKDzd4PnK9/Bt7jao0OIsPrIAHxMVACfbzkY
feZlOXUDXZ9bmiArwsp+O78=
=1jws
-END PGP SIGNATURE-
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
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
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
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 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
(linux-ide cc'ed) trash can wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have tolerated this problem for a year and do not post to this list in haste. I have posted on forums and searched the community over the past year. I have looked at the list archive on gossamer-threads.com for solutions. With Fedora Core 6 unsupported (the last kernel for which my zip drive worked), it is time for my last attempt at a solution. Please CC: any response as I have not joined the list. I have compiled a kernel-debug RPM and can run this if its output would help. Thank you for any time you might devote to this problem. motherboard: MSI P965 Platinum/Intel P965 Express Chipset Based (MS-7238 series) Fedora 8 : kernel 2.6.23.1-42.fc8 Iomega Zip drive internal Model Z100ATAPI lspci 03:00.0 SATA controller: JMicron Technologies, Inc. JMB361 AHCI/IDE (rev 02) 03:00.1 IDE interface: JMicron Technologies, Inc. JMB361 AHCI/IDE (rev 02) # lsmod | grep ata pata_jmicron8257 0 ata_generic 8901 0 ata_piix 16709 0 libata 99633 4 ahci,pata_jmicron,ata_generic,ata_piix scsi_mod 119757 4 sr_mod,sg,libata,sd_mod I have recently changed the BIOS setting for the SATA#1 Controller from [IDE] to [AHCI] with no effect. I assume AHCI is correct? AHCI is better, yes. It shouldn't be relevant this this problem though. Text below attached as text.txt for readability. from dmesg: libata version 2.21 loaded. device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] PCI: Enabling device :03:00.1 ( -> 0001) ACPI: PCI Interrupt :03:00.1[B] -> GSI 17 (level, low) -> IRQ 17 PCI: Setting latency timer of device :03:00.1 to 64 scsi0 : pata_jmicron scsi1 : pata_jmicron ata1: PATA max UDMA/100 cmd 0x0001cc00 ctl 0x0001c882 bmdma 0x0001c400 irq 17 ata2: PATA max UDMA/100 cmd 0x0001c800 ctl 0x0001c482 bmdma 0x0001c408 irq 17 ata1.00: ATAPI: LITE-ON DVDRW SOHW-1693S, KS0B, max UDMA/66 ata1.01: ATAPI: IOMEGA ZIP 100 ATAPI, 05.H, max MWDMA1, CDB intr ata1.00: configured for UDMA/66 ata1.01: configured for MWDMA1 scsi 0:0:0:0: CD-ROMLITE-ON DVDRW SOHW-1693S KS0B PQ: 0 ANSI: 5 scsi 0:0:1:0: Direct-Access IOMEGA ZIP 100 05.H PQ: 0 ANSI: 5 sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) sd 0:0:1:0: [sda] Write Protect is off sd 0:0:1:0: [sda] Mode Sense: 00 40 00 00 sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) sd 0:0:1:0: [sda] Write Protect is off sd 0:0:1:0: [sda] Mode Sense: 00 40 00 00 sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda:<6>sd 0:0:1:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK sd 0:0:1:0: [sda] Sense Key : Hardware Error [current] sd 0:0:1: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 If a disk is inserted into the drive (/var/log/messages) Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Spinning up disk.<5>sd 0:0:1:0: [sda] Spinning up diskready Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write Protect is off Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write Protect is off Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 10 14:22:53 localhost kernel: sda:<6>sd 0:0:1:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Sense Key : Hardware Error [current] Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Add. Sense: Scsi parity error Dec 10 14:22:53 localhost kernel: end_request: I/O error, dev sda, sector 0 Dec 10 14:22:53 localhost kernel: printk: 42 messages suppressed. Dec 10 14:22:53 localhost kernel: Buffer I/O error on device sda, logical block 0 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? -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at
Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
(linux-ide cc'ed) trash can wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have tolerated this problem for a year and do not post to this list in haste. I have posted on forums and searched the community over the past year. I have looked at the list archive on gossamer-threads.com for solutions. With Fedora Core 6 unsupported (the last kernel for which my zip drive worked), it is time for my last attempt at a solution. Please CC: any response as I have not joined the list. I have compiled a kernel-debug RPM and can run this if its output would help. Thank you for any time you might devote to this problem. motherboard: MSI P965 Platinum/Intel P965 Express Chipset Based (MS-7238 series) Fedora 8 : kernel 2.6.23.1-42.fc8 Iomega Zip drive internal Model Z100ATAPI lspci 03:00.0 SATA controller: JMicron Technologies, Inc. JMB361 AHCI/IDE (rev 02) 03:00.1 IDE interface: JMicron Technologies, Inc. JMB361 AHCI/IDE (rev 02) # lsmod | grep ata pata_jmicron8257 0 ata_generic 8901 0 ata_piix 16709 0 libata 99633 4 ahci,pata_jmicron,ata_generic,ata_piix scsi_mod 119757 4 sr_mod,sg,libata,sd_mod I have recently changed the BIOS setting for the SATA#1 Controller from [IDE] to [AHCI] with no effect. I assume AHCI is correct? AHCI is better, yes. It shouldn't be relevant this this problem though. Text below attached as text.txt for readability. from dmesg: libata version 2.21 loaded. device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] PCI: Enabling device :03:00.1 ( - 0001) ACPI: PCI Interrupt :03:00.1[B] - GSI 17 (level, low) - IRQ 17 PCI: Setting latency timer of device :03:00.1 to 64 scsi0 : pata_jmicron scsi1 : pata_jmicron ata1: PATA max UDMA/100 cmd 0x0001cc00 ctl 0x0001c882 bmdma 0x0001c400 irq 17 ata2: PATA max UDMA/100 cmd 0x0001c800 ctl 0x0001c482 bmdma 0x0001c408 irq 17 ata1.00: ATAPI: LITE-ON DVDRW SOHW-1693S, KS0B, max UDMA/66 ata1.01: ATAPI: IOMEGA ZIP 100 ATAPI, 05.H, max MWDMA1, CDB intr ata1.00: configured for UDMA/66 ata1.01: configured for MWDMA1 scsi 0:0:0:0: CD-ROMLITE-ON DVDRW SOHW-1693S KS0B PQ: 0 ANSI: 5 scsi 0:0:1:0: Direct-Access IOMEGA ZIP 100 05.H PQ: 0 ANSI: 5 sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) sd 0:0:1:0: [sda] Write Protect is off sd 0:0:1:0: [sda] Mode Sense: 00 40 00 00 sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) sd 0:0:1:0: [sda] Write Protect is off sd 0:0:1:0: [sda] Mode Sense: 00 40 00 00 sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda:6sd 0:0:1:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK sd 0:0:1:0: [sda] Sense Key : Hardware Error [current] sd 0:0:1: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 If a disk is inserted into the drive (/var/log/messages) Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Spinning up disk.5sd 0:0:1:0: [sda] Spinning up diskready Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write Protect is off Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] 196608 512-byte hardware sectors (101 MB) Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write Protect is off Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 10 14:22:53 localhost kernel: sda:6sd 0:0:1:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Sense Key : Hardware Error [current] Dec 10 14:22:53 localhost kernel: sd 0:0:1:0: [sda] Add. Sense: Scsi parity error Dec 10 14:22:53 localhost kernel: end_request: I/O error, dev sda, sector 0 Dec 10 14:22:53 localhost kernel: printk: 42 messages suppressed. Dec 10 14:22:53 localhost kernel: Buffer I/O error on device sda, logical block 0 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? -- Robert Hancock Saskatoon, SK, Canada To email, remove nospam from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
