You remember that file I had that can consistently lockup my device?
Turns out it has something to do with the cable length and capacitance between the chip and the drive!
My enclosure is a ViPower smart cable. The chip resides inside the head of a small centronics connector. This then plugs into a PCB at the back of the drive enclosure that has an IDC termination block soldered to it, that the 80 pin cable terminates to. That 80 pin cable then plugs into an IDE connector on the back of the enclosure inside the main enclosure. That IDE connector is soldered to a PCB that has a 50 pin centronics connector on it. That 50 pin centronics connector plugs into the caddy that has another PCB inside it with another IDC termination block that holds another 80 pin cable which then plugs into the drive.
GL-811 -> Mini-Centronics-Male -> Mini-Centronics-Female -> PCB -> 80 Pin Cable -> IDE Connector -> PCB -> 50 Pin Centronics Male -> 50 Pin Centronics Female -> PCB -> 80 Pin Cable -> Hard disk
!!!!?!
So I grabbed a dongly thing that plugs the GL-811 directly into the back of the Caddy
GL-811 -> Mini-Centronics-Male -> Mini-Centronics-Female -> PCB -> Centronics Male -> Centronics Female -> PCB -> 80 Pin Cable -> HD
And what do you know! It works with the latest kernel changes.
So it is the stuipd convoluted ViPower connection system that is corrupting the data under some condition that causes the GL-811 to lock up.
Regards, Brad
------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
