Of course there is an implementation for the multi-interrupt workaround in version 1.1.4. But if you get NO symlink at all, there might be annother problem which is unrelated. Are you saying that you don't get any per-interface logs with the test script? And if you are not willing to help finding the problem, can we agree to close this bug?
Josua Dietze "Nils Radtke" <nils.rad...@think-future.de> schrieb: > Hi, > > There is specific information and even a patch showing how it should work. > > Not working is precise enough, as it is: Not Working. Also, there's the > indication > that there's no symlink. What else do you need? Yeah, except for the log, > there's nothing > new to see. > > It was tested using latest packages. > > I'm tired of trying stuff that's bound to fail because the real issue never > got > investigated nor implemented. > > We finally stick to the patched versions. > > Cheers > > >On Tue 2010-09-14 @ 09-28-16AM -0400, Josua Dietze wrote: ># "Not working" is a bit unspecific. Please post the per-interface logs that >the custom dispatcher script puts out. And check if you are using the latest >data package. ># ># Josua Dietze ># ># ># ># "Nils Radtke" <l...@think-future.de> schrieb: ># ># >Using 1.1.4-1 w/ the dispatcher packaged and the one w/ md5sum ># > ># >4dbee5f67f0fc15c8a949cabd8df4bfe usb_modeswitch_dispatcher ># > ># >does NOT work. ># > ># >Reliably working: 1.1.2-3 + patch above. ># >Working 1.1.3-1, w/ symlink but errors in log, occasionally missing link, >time to appearance of symlink is very long. ># > ># > ># > ># > ># ># =-- ># Gesendet von meinem Dell Streak. > > >-- > > > =-- Gesendet von meinem Dell Streak.
