<br><br><div class="gmail_quote">On Thu, Jul 9, 2009 at 9:32 AM, Greg KH <span dir="ltr"><<a href="mailto:greg@kroah.com">greg@kroah.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div><div></div><div class="h5">On Thu, Jul 09, 2009 at 09:20:56AM -0600, jasonlife wrote:<br> > ><br> > > Could you explain little bit more about this problem? I noticed my Samsung<br> > > monitor provides a HID interface as you expected. Does a DisplayLink USB<br> > > device have a problem if it also provides other device types like<br> > > keyboard/mouse (HID) and sound?<br> > ><br> ><br> > I think my question was not clear. Based on lsusb -vv result, DisplayLink<br> > device provides two configurations in my Samsung monitor. Does this cause<br> > the problem? Is there a way to fix or go around this problem?<br> <br> </div></div>Yes, the solution is to always set the first configuration as active.<br> This can be done with a single line of code, perhaps it needs to be<br> added to the driver?</blockquote><div><br>The first configuration is HID in my samsung monitor case. if it is a single line of code, then could you show me how to do it? I want to try that..<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br> <br> thanks,<br> <br> greg k-h<br> </blockquote></div><br>