Device isn<|pad|>,检测失败，原因不明
Device isn<|pad|>,检测失败，原因不明
I'm updating the water cooling system in my main machine and have moved all tasks to my secondary computer. I'm exploring the possibility of switching to Linux entirely, mainly to test it out. Everything seems to be working smoothly—games launch through Proton with minimal problems, except for a clock issue. The system clock was set to UTC time and then adjusted to be 4 hours behind real time, but this caused issues. When playing a controller-based game like Arkham Asylum, my Xbox One S didn't detect the controller at all. I tried using a wired Xbox 360 controller, but it kept flashing and wasn't recognized. I attempted to install the recommended drivers from Arch-Wiki, but it didn’t resolve the problem. I changed the USB port to rule out a faulty controller, yet the issue persisted. Currently, I’m unsure what to do next; controllers should just work plug-and-play. I'm open to any suggestions, especially solutions for the clock problem. Just a heads-up—I’m weighing this against troubleshooting options.
Can't help with the controller issue as I'm not a gamer so no controllers here. But here's the solution to your clock: As root do: ln -sf /usr/share/zoneinfo/<zone/location> /etc/localtime #<zone/location> is in the form Canada/Pacific for Vancouver Look at the contents of /usr/share/zoneinfo/ and adjust your time zone according to what's available in the directories below that.
You haven't fully understood the page. It suggests you might need the xboxdrv package for a wireless Xbox 360 controller.
I reviewed those pages multiple times, and the advice is to use the default drivers. If you run into problems, try switching to xboxdrv. I’ve tested both options already, but neither works. For troubleshooting, I used an old steelseries controller that only shows up as an input device. It seems the issue might be with the Xbox controllers not being recognized by the OS.
UTC is configured as GMT by default. You likely need to adjust your hardware clock if you haven't done so already. Using an NTP client can automatically keep your clock in sync with UTC/EDT.
The systemd-timedated already includes an NTP client. It seems to be reporting as active, but you might want to try: sudo timedatectl set-ntp true (https://wiki.archlinux.org/title/Install...stem_clock). If that doesn’t help, adjust your clock directly in the BIOS. It’s possible the BIOS blocks OS changes there. You’re not dual booting with Windows, are you? This requires further steps: https://wiki.archlinux.org/title/System_...e_standard
In general, I didn't use a controller on Linux, but I can explain what happens if I try to connect my USB Microsoft XBOX 360 controller. I run Arch and don't have drivers installed manually. This gives a useful reference: connecting now – step 1. The light on the controller – top left of the ring – flashes then stays on. Kernel logs show the device is detected: $ sudo dmesg ... [314419.758093] usb 1-1: new full-speed USB device number 7 using xhci_hcd [314419.906794] usb 1-1: New USB device found, idVendor=045e, idProduct=028e, bcdDevice= 1.14 [314419.906797] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [314419.906798] usb 1-1: Product: Controller [314419.906799] usb 1-1: Manufacturer: ©Microsoft Corporation [314419.906800] usb 1-1: SerialNumber: 17EC39B [314419.918384] Input: Microsoft X-Box 360 pad as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/input/input21 [314419.918674] usbcore: registered new interface driver xpad ... 2. Entries show up in /dev/input $ ls -l /dev/input total 0 drwxr-xr-x 2 root root 240 Aug 26 09:41 by-id drwxr-xr-x 2 root root 240 Aug 26 09:41 by-path crw-rw---- 1 root input 13, 64 Aug 22 18:20 event0 crw-rw---- 1 root input 13, 65 Aug 22 18:20 event1 crw-rw---- 1 root input 13, 74 Aug 22 18:20 event10 crw-rw---- 1 root input 13, 75 Aug 22 18:20 event11 crw-rw---- 1 root input 13, 76 Aug 22 18:20 event12 crw-rw---- 1 root input 13, 77 Aug 22 18:20 event13 crw-rw---- 1 root input 13, 78 Aug 22 18:20 event14 crw-rw---- 1 root input 13, 79 Aug 22 18:20 event15 crw-rw---- 1 root input 13, 80 Aug 22 18:20 event16 crw-rw---- 1 root input 13, 81 Aug 22 18:20 event17 crw-rw---- 1 root input 13, 82 Aug 22 18:20 event18 crw-rw---- 1 root input 13, 83 Aug 22 18:20 event19 crw-rw---- 1 root input 13, 84 Aug 22 18:20 event20 crw-rw----+ 1 root input 13, 85 Aug 22 18:20 event21 crw-rw---- 1 root input 13, 86 Aug 22 18:20 event3 crw-rw---- 1 root input 13, 87 Aug 22 18:20 event4 crw-rw---- 1 root input 13, 88 Aug 22 18:20 event5 crw-rw---- 1 root input 13, 89 Aug 22 18:20 event6 crw-rw---- 1 root input 13, 90 Aug 22 18:20 event7 crw-rw---- 1 root input 13, 91 Aug 22 18:20 event8 crw-rw---- 1 root input 13, 92 Aug 22 18:20 event9 crw-rw---- 1 root input 13, 93 Aug 26 09:41 js0 crw-rw---- 1 root input 13, 94 Aug 22 18:20 mice crw-rw---- 1 root input 13, 95 Aug 22 18:20 mouse0 Take note of the timestamps for event21 and js0. 3. This requires evtest installed: sudo pacman -S evtest After installation and running it, selecting the device (event21) shows: $ sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: ... [rest of output] $ Now pushing buttons or hitting the axis on the controller will display events. That’s my experience, but essentially this means: - If you can’t get it, the issue is likely a driver or kernel module problem - Once you’re connected and every button/axle triggers an event in evtest, drivers are probably fine - Configuration in your desktop or games/apps may need fixing.
After several attempts and following your directions, it looks like the controller was finally identified and the player 1 light is now active. The Xbox 360 controller is functioning properly, but I'm satisfied with that. Thanks!
Provide extra guidance for the other installer: Always verify the module is properly loaded into the kernel before testing. Some setup scripts might delay loading or fail after reboot. Refer to the short wiki page on kernel modules for details: https://wiki.archlinux.org/title/Kernel_module. It’s also useful to review the driver’s GitHub or official documentation for specific installation steps. Updated August 27, 2021 by grg994 Additional info