Am Donnerstag, 5. November 2015 17:48:20 UTC+1 schrieb Ingo Ruhnke: > > On Wed, Nov 4, 2015 at 10:55 PM, jonny kotzur <[email protected] > <javascript:>> wrote: > > here it is: > > sudo lsusb -v -d 045e:028f > > > > Bus 003 Device 002: ID 045e:028f Microsoft Corp. Xbox360 Wireless > Controller > > Device Descriptor: > > bLength 18 > > bDescriptorType 1 > > bcdUSB 2.00 > > bDeviceClass 255 Vendor Specific Class > > bDeviceSubClass 255 Vendor Specific Subclass > > bDeviceProtocol 255 Vendor Specific Protocol > > bMaxPacketSize0 8 > > idVendor 0x045e Microsoft Corp. > > idProduct 0x028f Xbox360 Wireless Controller > > bcdDevice 2.04 > > ... > > That just looks like the regular old Play&Charge cable, as expected > there are no endpoints to transmit input data. > > Are you sure that you don't have a Wireless Receiver plugged in? And > when was the last time you actually tried to use your wireless Xbox360 > controller in Windows? Meaning have you actually verified that it > works and aren't just operating on faulty memory or assumptions? > > -- > Blog: http://grumbel.blogspot.com/ > JabberID: xmpp:[email protected] <javascript:> > ICQ: 59461927 >
Yeah, silly me. If you connect a new controller, Windows installs the the corresponding driver and adds a new controller to its configuration, but it actually does not work until you connect a wireless receiver... -- You received this message because you are subscribed to the Google Groups "xboxdrv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/xboxdrv. For more options, visit https://groups.google.com/d/optout.
