On 23/07/14(Wed) 03:07, Mike Burns wrote: > On 2014-07-23 07.40.00 +0200, Martin Pieuchot wrote: > > On 22/07/14(Tue) 19:37, Mike Burns wrote: > > > On 2014-07-22 10.10.02 +0200, Martin Pieuchot wrote: > > > > > umass0 at uhub2 port 2 configuration 1 interface 0 "SanDisk Cruzer" > > > > > rev > > > > > 2.00/2.00 addr 6 > > > > > umass0: using SCSI over Bulk-Only > > > > > scsibus4 at umass0: 2 targets, initiator 0 > > > > > sd2 at scsibus4 targ 1 lun 0: <SanDisk, Cruzer, 8.02> SCSI0 0/direct > > > > > removable serial.0781553001117562C886 > > > > > sd2: 30547MB, 512 bytes/sector, 62562239 sectors > > > > > > > > In your previous dmesg your touchscreen attaches itself to uhub3, when > > > > you plug a device like this one, does it always attaches to uhub2? In > > > > other words, does something, somehow, sometimes attach to uhub3? > > > > > > I have two USB ports (at least, ones I can plug into): one is labeled > > > with a USB symbol and a battery symbol; that one works and shows up as > > > uhub2. The other is labeled with a SS followed by a USB symbol; this one > > > does not work and adds nothing to the dmesg. > > > > Did you try the BIOS option USB 3.0? > > Sorry for forgetting that earlier. With the USB 3.0 option turned off, > when I plug a USB stick into the other port:
But more importantly... > uhidev0 at uhub3 port 3 configuration 1 interface 0 "eGalax Inc. eGalaxTouch > EXC7903-66v03_T1" rev 2.00/66.03 addr 3 > uhidev0: iclass 3/1, 7 report ids > uhid0 at uhidev0 reportid 1: input=5, output=0, feature=0 > uhid1 at uhidev0 reportid 3: input=63, output=63, feature=0 > uhid2 at uhidev0 reportid 5: input=0, output=0, feature=2 > ums0 at uhidev0 reportid 6: 1 button, tip > wsmouse1 at ums0 mux 0 > ums1 at uhidev0 reportid 7 > ums1: mouse has no X report ...your touchpad is back! I'll try to dig into the wsmoused issue, please let me know if you have any other problem.
