Yes, unfortunately the controller is the VT-6202 on a PCI card. Is there a problem in the silicon or is there a chance that this controller will eventually work? It seems like it is very close, if it didn't freeze my system it would be ideal for me. ...
Just a driver problem, I expect, so someone has to spend time on it. It could be the same root problem as another problem someone's having with different ehci hardware (I hope it is!).
Any further attempt to access the disk simply hangs and does not respond to signals. Is there anything I can do to diagnose the problem or am I just SOL with this controller?If you can reproduce this on a 2.5 sytem, you'd be able to provide
some useful diagnostics through the new "sysfs" facility. (2.5.45
is a 2+ MByte patch, so be careful, and might call it "driverfs".)
Basically, if the PCI slot name of your VT-6202 controller is "00:08.4"
then /sys/root/pci0/00:08.4/ is a directory with a bunch of files. If
you configure with "USB verbose debug messages" you'll see "ehci-hcd"
put three files there, "async", "periodic", and "registers". When it
hangs, send the contents of those three files ... in your case "async"
should have the most useful info.
- Dave
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
