On Mittwoch 16 September 2009, Alan Stern wrote:
> On Wed, 16 Sep 2009, Volker Armin Hemmann wrote:
> > emm, the mouse is attached through a powered 4port usb 2.0 hub. That is
> > the only way to get it working. If I attach it directly (without loading
> > ohci) it does not work (well, only tried with both Transaction Translator
> > options off), and if I load ohci before I connect it, it is very very
> > jerky. So jerky in fact, that I considered douzends of lockups a day a
> > better alternative.
> 
> That is a separate issue and it is a serious bug.  If anything, the
> behavior with OHCI should be better than with EHCI.  This is worth
> pursuing farther.  A usbmon log combined with the dmesg log would help.
> There's no need to include all the boot-up messages in the dmesg log;
> you can clear the log buffer before plugging in the mouse.
> 
> In fact, we can probably forget about the EHCI issue.  If it works okay
> with the newer TT scheduler, that should be good enough.
> 
> Alan Stern
> 

ok, I was in the kitchen, I am back and the mouse is extremely jerky.

I cat usbmon/5u into a file for a short while, I hope it is the right file?

Glück Auf
Volker