Albert Lee wrote: > Tejun Heo wrote: > > Hmmm... weird. Your drive bears the same model name as Stanislav's. I > > don't think the low level driver is causing the difference. They both > > use the standard libata HSM implementation. Any ideas? Stanislav, can > > you try to connect that zip drive to another IDE controller? > Maybe it's also worth a try to replace the medium, cable or even the > drive itself to rule out the possibility of hardware problem. I'll try it. I cannot replace the drive, I don't have any spare one, but my colleague has. He will try it on his machine. So let's wait for result. Looking at the syslog in Novell bug 232086 in detail, following line may indicate hardware failure: usb 5-1: string descriptor 0 read error: -22 My drive is a slave on bus, where master is a modern Seagate ST3160812A. On my system I see two regressions: - One between year 2002 kernels and SuSE Linux 10.0: Delay with "packet command initiated yet DRQ isn't asserted" before first read access, then the read will succeed. I did not yet reproduce this regression just now on my hardware. - Second between SuSE 10.1 and 10.2: Delay with "packet command initiated yet DRQ isn't asserted" before any attempt to access, then it will fail. This regression is reproducible just now on my hardware, but still may be caused by hardware problems raised by a slightly different initialization order. Tejun Heo wrote: > [libata] > And, as the device requires custom high level driver, libata fails > miserably. Would it be worth to try support these devices? Or are > they just too outdated to put the effort in? As far as I remember, it was working without any special driver with ide-scsi. -- Best Regards, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@xxxxxxx Lihovarska 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
