search

ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.23k stars 174 forks source link

No controller is detected #5479

Closed Leeo97one closed 6 years ago

Leeo97one commented 6 years ago

System information

Issue:

None of my controllers (Xbox 360 and Switch Pro) are detected with the Steam Client Beta. Here are logs when I plug the Switch Pro Controller:

mai 04 04:22:51 leeo-arch-msi steam.desktop[9635]: Local Device Found
mai 04 04:22:51 leeo-arch-msi steam.desktop[9635]:   type: 057e 2009
mai 04 04:22:51 leeo-arch-msi steam.desktop[9635]:   path: 0001:000c:00
mai 04 04:22:51 leeo-arch-msi steam.desktop[9635]:   serial_number:  - 0
mai 04 04:22:51 leeo-arch-msi steam.desktop[9635]:   Manufacturer:
mai 04 04:22:51 leeo-arch-msi steam.desktop[9635]:   Product:
mai 04 04:22:51 leeo-arch-msi steam.desktop[9635]:   Release:      200
mai 04 04:22:51 leeo-arch-msi steam.desktop[9635]:   Interface:    0
mai 04 04:22:51 leeo-arch-msi steam.desktop[9635]: Unable to open local device: 0001:000c:00

And there is just nothing when I plug the Xbox 360 controller.

The detection works fine when I opt-out the beta. (Both of the controller are detected and I can use the Xbox 360.)

Also on the Steam Beta Client group discussions: https://steamcommunity.com/groups/SteamClientBeta/discussions/0/1696046342857494604/

Steps for reproducing this issue:

  1. Opt-in the Steam Client Beta
  2. Plug a Xbox 360 or Switch Pro Controller
  3. Find that no controller is detected in the Controller Settings of Big Picture mode
kisak-valve commented 6 years ago

Possible duplicate of #5477.

YangtseSu commented 6 years ago

Same problem here. But the steam client can detect my Steam controller. While xbox one controller and ns pro controller not.

trinitronx commented 6 years ago

Also duplicate of #5353

This bug was pushed out in today's steam update & now affects stable channel!

Please see issue #5353 for my test results & affected steam versions.

trinitronx commented 6 years ago

Issue summary:

Your system information

Steam client version (build number or date): 1526499729, May 16 2018, at 12:02:10 Distribution (e.g. Ubuntu): Ubuntu 17.10 Opted into Steam client beta?: [Yes/No] Yes Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

Any controller is not recognized in steam-client (Big Picture mode & using joystick as desktop mouse), but it is functional in games.

Steps for reproducing this issue:

  1. Load affected steam client version
  2. Go to Steam => Settings => Controller => Desktop Configuration (or any of: "Big Picture Configuration", "Guide Button Chord Configuration")
  3. Window opens saying "No Controller Attached Please attach a controller in order to configure it" (See screenshot)

If you had the controller / joystick previously configured to act as Desktop mouse, it does not work any more!

screenshot from 2018-05-17 09-54-21

Expected Behavior:

Controller should be detected in controller settings, can be used as a Desktop Mouse or to navigate the Big Picture UI.

Current Behavior:

Controller is not detected or functional in steam-client. Controller does function inside games.

Additional Information

Controller is fully-functional using jstest. Was previously working without issue, before many recent beta steam application updates (see #5353 for affected version details).

Opting out of the beta fixed the issue, until the stable channel pushed out the buggy version May 17th 2018.

Leeo97one commented 6 years ago

Really, this problem in the stable client? Valve, are you kidding me x)

PJBrs commented 6 years ago

Is there any way to roll back? I only use big picture mode, so this bug is a very major annoyance...

jason-oliveira commented 6 years ago

I'm having this same problem with every XInput gamepad I try on two separate computers running two separate distros. Only a handful of games detect controllers (Enter the Gungeon and PAC-MAN 256 work, Rocket League, Bastion, Owlboy do not). Gamepad works with GoG/Pirated versions of the games I own. Gamepad works in KDE (uses evdev), RetroArch, Wine (with x360ce), and Dolphin. Just not many (most) games within Steam.

Machine 1: Gentoo Linux Kernel 4.16.8 KDE Plasma Desktop 5 AMDGPU kernel driver and radeonsi Non-beta Steam client.

Machine 2: Calculate Linux Kernel 4.14.19 KDE Plasma Desktop 5 Proprietary nvidia driver Non-beta Steam client.

Controllers: Zhidong V Xinput gamepad Matricom XYBA G-pad (in both bluetooth and XInput mode) 8Bitdo SN30 Pro (in both Switch and XInput mode)

pierrep commented 6 years ago

I'm also getting this bug, happened immediately upon installing the May 16th stable steam update on both my SteamOS and Ubuntu machines. My Logitech F710 controllers can no longer navigate Big Picture Mode.

I 100% confirmed it by testing the controller on my Ubuntu machine, applying the update, then watching the controllers stop working. They appear to still work in game however.

One thing of note - my Steam controller is still fully functional.

siebz0r commented 6 years ago

I have also fallen victim to this bug since last update. Can confirm that this is quite annoying. It's a bit of a shocker to me that this was reported in beta and is now in stable as well. I see numerous bugs being reported on this with various controllers, except for the steam controller. What happened?

jakepearse commented 6 years ago

Arggh I spent hours messing with my configs...and its a regression in the stable branch. Sad thing is I hadn't played with steam for like 9 mths fired it up and it worked great for a day now this...time to find my steam controller -- edit steam controller works fine

PJBrs commented 6 years ago

I'll add my info - controllers don´t work anymore in the steam client, regardless of whether in BPM or regular mode. I tried with both Logitech F710 and F310 controllers (XInput mode; didn´t try directinput). Controller does work in The Talos Principle. This is on Slackware64 14.2.

Another report for this bug: https://github.com/ValveSoftware/steam-for-linux/issues/5394

Again, if anybody knows how to roll back or how to work around thisI'd really appreciate it! Would also like to have some dev reaction. It´s slightly worrying to see a known beta bug make its way into the stable client...

dragonfly-lover commented 6 years ago

This bug is probably tightly related with the one i filed on february when the problem started to appear with logic3 pads: https://github.com/ValveSoftware/steam-for-linux/issues/5394

evilnick commented 6 years ago

Also having this issue with a Logitech F710 on ubuntu 18.04 LTS

Has been working fine for over a year, stopped working when the latest update went out. This also seems to prevent it working within several games

jkumara commented 6 years ago

Same thing happening for me on SteamOS (2.0 update 1:2.148) after the client's stable May 16th update. XBox 360 controller (wired) works in games, but not in Big Picture. No problems before this update.

kotajacob commented 6 years ago

Same thing with me and an emulated xbox 360 controller (via xboxdrv)... spent the last 2 days trying to figure out what was going wrong...

kisak-valve commented 6 years ago

Per "Fixed a library compatibility issue that resulted in gamepad support not working" in the 2018-05-18 Steam beta client update, please opt into Steam's beta client and check if the behavior has improved.

kotajacob commented 6 years ago

Haven't had time to fully test it yet, but so far so good. It did detect my emulated xbox 360 controller and seems to be working as normal as of the current beta. Thanks a ton!

EDIT: Just tested on a pretty much stock Ubuntu 18.04 install with a generic Logitech controller and everything worked fine with that too! 🎉

siebz0r commented 6 years ago

I just tested the current beta with a wireless Xbox 360 controller and navigation in big picture mode seems to work fine. :smiley: This is on Gentoo.

jkumara commented 6 years ago

Current Beta fixed my issue on SteamOS with wired XBox controller too. Good job 👍🏻

brain-anti-freeze commented 6 years ago

Has anyone tried with a NS Pro controller since the latest beta ? XBone controller works for me now but still no NS Pro. I'm also seeing no controllers detected in some games (Rise of the Tomb Raider)

dragonfly-lover commented 6 years ago

didn't solve my bug https://github.com/ValveSoftware/steam-for-linux/issues/5394

Leeo97one commented 6 years ago

OK it now works with standard controller again but not with the Switch Pro. I think we have to create another issue for that...

avdean commented 6 years ago

On solus OS, up-to-date and I'm experiencing the same issue with both a generic gamepad and an Xbox wired gamepad, both unrecognised in both beta and stable. One thing I did notice is that the generic controller is recognised before assigning there button profiles, Though haven't tried with the Xbox controller yet.

trinitronx commented 6 years ago

Validated that latest stable update fixed the Xbox 360 Controller issue!

Working version:

Steam client application
Built: May 18 2018, at 14:50:44
Steam API: v018
Steam package versions: 1526683293

Only minor issue was with joystick dead zone settings being reverted to default, which caused mouse to drift up when joystick was still centered. After fixing this setting, it works fine again!

Dead Zone config steps:

  1. Go to Steam => Settings => Controller => Desktop Configuration
  2. Select "Joystick Mouse" for corresponding joystick that is controlling the mouse
  3. Select "Additional Settings"
  4. Ensure "Dead Zone Shape" is Cross (or your preferred shape)
  5. Select "Dead Zone Inner", and adjust the slider to fit your joystick's minimum neutral X & Y values

Note that due to hysteresis, your min & max values for neutral X & Y joystick coordinates will vary depending on how you move the stick & release back to neutral. This setting and dead zone shape should be adjusted to fit your particular controller's quirks. Check your values with one of the following tools:

kisak-valve commented 6 years ago

Closing as fixed in the 2018-05-18 Steam stable client update.

See https://github.com/ValveSoftware/steam-for-linux/issues/4920#issuecomment-386188223 or https://github.com/ValveSoftware/steam-devices/blob/master/steam_input.rules for a udev rule that allows Steam to work with the Nintendo Switch Pro controller.

pierrep commented 6 years ago

Thanks for the prompt response :)

brain-anti-freeze commented 6 years ago

Thanks Kisak, with the udev rule installed Steam can see the Switch Pro contoller. I will open a SteamOS bug to have that file added. The issue with Rise of The Tombraider and Rocket League are still present (no controllers detected when NS Pro plugged in for Rocket League and behaves as if up+left are being held down in RotT) - I'll log new issues for them.

ekianjo commented 6 years ago

This issue should not be closed @kisak-valve . I still have the issue with Xbox360 controller for both the stable and beta branch. No controller is recognized.

kisak-valve commented 6 years ago

Hello @ekianjo, if you are using the distro-provided steam package on Debian or Ubuntu, then you'll also need the steam-devices package installed for controllers to work.

The specific issue that was tracked in this issue report was identified and triaged, so if the just mentioned scenario or #5353 does not apply to you, then please open a new issue report.

dragonfly-lover commented 6 years ago

@ekianjo your bug could possibly be this one: https://github.com/ValveSoftware/steam-for-linux/issues/5394

ekianjo commented 6 years ago

@kisak-valve I confirm that installing steam-devices fixes the problem on Ubuntu and derivatives - however I also have another computer running SOLUS, and how do you fix the same issue there?

Wykks commented 6 years ago

@ekianjo Had the same issue. After reading stuff in https://github.com/ValveSoftware/steam-for-linux/issues/1894, I decided to turn off "Linux steam integration" completly; aaand it's finally working!

You'll probably need to adjust /dev/input/event* permission through udev: I added this (no very secure, but it's a home computer soo I guess it's ok) SUBSYSTEM=="input", MODE="666"

ekianjo commented 6 years ago

oh wow that sucks if that is the case...

On Monday, June 18, 2018, Guillaume de Jabrun notifications@github.com wrote:

@ekianjo https://github.com/ekianjo Had the same issue. After reading stuff in #1894 https://github.com/ValveSoftware/steam-for-linux/issues/1894, I decided to turn off "Linux steam integration" completly; aaand it's finally working!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/steam-for-linux/issues/5479#issuecomment-397892284, or mute the thread https://github.com/notifications/unsubscribe-auth/ACWMmKzcweqmmFdbXR_Xd8KrPqv7LRjtks5t9ox4gaJpZM4T4U9B .

-- Raphael

ronlaws86 commented 6 years ago

screenshot from 2018-09-23 14-33-45 September 2018 and this is still an ongoing issue? Screenshot proves controller is picked up and working by the OS but steam is oblivious to it. a Generic Logitech F310 works fine though.

YangtseSu commented 6 years ago

It works now.

Yangtse Su

From: Ronnie notifications@github.com Sent: Sunday, September 23, 2018 9:35:46 PM To: ValveSoftware/steam-for-linux Cc: Yangtse Su; Comment Subject: Re: [ValveSoftware/steam-for-linux] No controller is detected (#5479)

[screenshot from 2018-09-23 14-33-45]https://user-images.githubusercontent.com/11991709/45928579-d0b17080-bf3d-11e8-943f-6e6bf138fe7c.png September 2018 and this is still an ongoing issue? Screenshot proves controller is picked up and working by the OS but steam is oblivious to it. a Generic Logitech F310 works fine though.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/ValveSoftware/steam-for-linux/issues/5479#issuecomment-423816989, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAnsWB8Qsdn7dZYouidxi_iDs6QQfN-Pks5ud44ygaJpZM4T4U9B.

Leeo97one commented 6 years ago

@ronlaws86 Verify your udev rules (https://github.com/ValveSoftware/steam-devices/blob/master/steam_input.rules). You should install the steam-devices package if you are on a Debian/Ubuntu-based distro.

tomgar commented 6 years ago

I'm in the same situation as @ronlaws86 , @Leeo97one .

Using archlinux updated to today's latest packages. Steam can't recognize my Thrustmaster GPX controller (a Xbox 360 controller clone).

Steam is installed from the official package of the repos, so the official udev rules are installed too, although they're patched. Look here: https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/steam

Upon running Steam from a terminal I see this: Local Device Found type: 24c6 5b02 path: sdl://0 serial_number: - 0 Manufacturer: Product: Thrustmaster, Inc. GPX Controller Release: 202 Interface: -1

Local Device Found type: 24c6 5b02 path: sdl://0 serial_number: - 0 Manufacturer: Product: Thrustmaster, Inc. GPX Controller Release: 202 Interface: -1

Tried Steam beta too but still no dice.

trinitronx commented 6 years ago

@tomgar : Although this issue was originally posted as a generic "No controller is detected" issue... The issue's details & fixes appear to have been focused on the following controllers:

If you found that this issue is still affecting your Thrustmaster, Inc. GPX Controller, please check that this device ID is compatible with known Xbox 360 drivers on Linux. How to do this?... you might ask:

  1. Find your USB device ID in output of lsusb command. For example:

    $ lsusb
Bus 001 Device 006: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter

  2. Assuming you are using the xpad driver: Check in source code for xpad.c for this Device ID.

You'll need to find out what controller input device driver and version of this driver you are using. It could be that the device ID exists in latest source code, but you have an older version which does not support your device ID.

If you find that it's supported in your driver and feel like this is still an problem, it's probably best to open your own issue on this project or the ValveSoftware/steamos_kernel project to address your particular device support.

tomgar commented 6 years ago

@trinitronx my controller appears in the xpad.c of the kernel version I'm using ( https://github.com/torvalds/linux/blob/94710cac0ef4ee177a63b5227664b38c95bbf703/drivers/input/joystick/xpad.c#L328 ). I think that with the issue #5621 should be enough to address this problem. My controller was detected in Steam months ago, but nowadays it's not...

trinitronx commented 6 years ago

@tomgar : Ok, good to know it's supported in the SteamOS version of xpad! I've had some issues on Ubuntu with this driver not being up to date from time to time. Could it be that a package update on your distro has inadvertently overwritten this driver with an older version? Always good to check your version is up to date with the source.

tomgar commented 6 years ago

@trinitronx my issue got finally fixed. Check #5621 for the solution I applied.

Nayr438 commented 4 years ago

Your system information

Steam client version (build number or date): June 4 2020
Distribution (e.g. Ubuntu): Arch Linux
Opted into Steam client beta?: No
Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible: Steam is unable to detect my PowerA xbox one Controller, games seem to be unable to see it as well.

lsusb -> Bus 001 Device 014: ID 24c6:543a BDA Xbox ONE Pro Ex controller Is detected by KDE Input and appears fully functional

I have tried using steam-native-runtime and installing steamos-xpad-dkms

Steps for reproducing this issue: Connect PowerA xbox one controller and check steam controllers or start a game through steam.

kisak-valve commented 4 years ago

Hello @Nayr438, please open a new issue report.

Also, please test if adding a udev rule with something like KERNEL=="hidraw*", ATTRS{idVendor}=="24c6", ATTRS{idProduct}=="543a", MODE="0660", TAG+="uaccess" has an effect.