Your message dated Fri, 18 Oct 2013 19:39:05 +0100
with message-id
<CAPQ4b8=YDd0df96B4N=ystsgbtb99hirref41y6u33waham...@mail.gmail.com>
and subject line Re: libsdl can fail to enumerate XBox 360 wireless controllers
has caused the Debian Bug report #585655,
regarding libsdl can fail to enumerate XBox 360 wireless controllers
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
585655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585655
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-2.6-686
Version: 2.6.32+25
Severity: important
Hello,
Visibly you put in your website that the new kernels were updated and working
better for microsoft wireless 360, and that one could use them.
Well one gamepad, yes it works ,but 2 identical gamepads arent working at all.
I tried under hatari, zsnes, and genesis.
Please make sure that 2 identical gamepad are working under linux.
It is crazy linux, there is never a single piece of hardware that works without
any troubles, for most of the time. If you have an old PC, the kernel is not
supposed to work either. Too new, it sure not working, and too old neither.
Well kernels arent intended to be huge. I mean in 20 years, those kernel will
eat the ram of old PC.
I mean think a bit. Debian cannot share within the years the kernels having all
hardware in there. If their drivers works, please make sure that they really
work, and good.
So here the lusb output.
~$ lsusb
Bus 002 Device 007: ID 045e:00b0 Microsoft Corp. Digital Media Pro Keyboard
Bus 002 Device 006: ID 046d:0928 Logitech, Inc. QuickCam Express
Bus 002 Device 005: ID 05fe:2001 Chic Technology Corp.
Bus 002 Device 004: ID 067b:2305 Prolific Technology, Inc. PL2305 Parallel Port
Bus 002 Device 003: ID 04f3:0216 Elan Microelectronics Corp.
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 009: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter
Bus 001 Device 007: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter
Bus 001 Device 004: ID 066f:4200 SigmaTel, Inc. STIr4200 IrDA Bridge
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
those 2 xbox 360 are the cauchemar.
I want to play with my friend please. it could be great. But well tongiht is
the only chance :( :(
Best regards
Y.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6-686 depends on:
ii linux-image-2.6.32-3-686 2.6.32-9 Linux 2.6.32 for modern PCs
linux-image-2.6-686 recommends no packages.
linux-image-2.6-686 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
2012/3/4 Manuel A. Fernandez Montecelo <[email protected]>:
> tags 585655 +moreinfo
> stop
>
> Hello,
>
> Thank you for your interest in improving Debian, and sorry to keep the
> bug unattended for so long. There's now an effort to review the open
> bugs related with SDL packages.
>
> Several new versions have entered the archive after this report was
> submitted, can somebody please confirm if this is still happening?
>
> I don't have that hardware myself so I cannot test it.
Nobody provided more information for 3 years.
Still, upstream reviewed this and suggested the possibility that it
was not tested above, AFAICT (so I am posting here in the case that
somebody still sees this and can follow up):
-------
FYI, some people have reported that SDL can't detect their joysticks
because they don't have permission to access /dev/input/event*
Maybe that's the problem here?
-------
Now the focus is on SDL2 (in which many internals of the code changed
significantly, after 10 years of development) and this branch is
discontinued.
So I think that it's better to close this bug report, please somebody
reopen if you can provide meaningful information or test.
Cheers.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
