Installation Success, Connecting Fails, no /sys/module/hid_xpadneo #76
Comments
|
Hi There, have you read the section about secure boot / kernel lockdown? And is It maybe active? Sounds like! |
|
As you can see from my output, secure boot is disabled. |
|
Sorry, I must have overread that somehow... It's clear that Let me try to help you anyway, please give me the output of:
|
|
Did another fresh install of Ubuntu 18.10 and xpadneo as well to make sure
|
|
xpadneo gets loaded when the gamepad was sucessfully connected, therefore I wouldn't expect xpadneo in
|
|
Furthermore, can you please do what is described here? https://stackoverflow.com/questions/37003147/i-want-to-enable-debug-messages-on-bluez |
|
I just received this controller earlier this week. I synced it up with my Windows 10 PC and played around with it for a bit, with a USB cable, the Windows Wireless Adapter, as well as Bluetooth with the same 4.1 adapter as I am using in Linux. I am trying to build a project using xinput in python for something else down the road. Xbox Accessories in Windows 10 reports that it is up-to-date, and no updates are available. I power the controller on with the xbox button, which then causes the controller's light to slow pulse. I then press the sync button at the top of the controller until the light starts to fast pulse. I then go through the pair, trust, connect commands. I am the first to admit, I am no guru in Linux, especially when it comes to the hardware side of it. |
|
So is it by any chance the same PC (native Windows and Linux in VM?).
Please hit the upgrade/update button anyways if possible (the gamepad should then "shutdown" for a moment - sometimes the gamepad has a little problem to connect to another OS after connecting it to another, especially if it is the same PC. By "updating" it - even if it was already the latest fw - you reset the internals. |
|
Moreover, please remove the already paired gamepad by
As we all where once/are ;) |
|
I have hit the upgrade button, the controller reboots, receive a message about it already being up-to-date, and it reboots again. No version number change. Still unable to connect with Bluetooth in Linux. Yes, Native Windows, Workstation Pro 15 Trial, using hardware level pass-through. They had to be added independently between OS's, as one would expect. I did a remove, I see a DEL message, did a pair, says it still exists, did a trust, says succeeded, did a connect, now its looping, until the controller goes to slow blinking, and eventually power off, then it goes quiet. Also, just played ~2hr with it in Bluetooth mode using that 4.1 adapter in Windows and it worked great. Having to get used to a gamepad again :). I just added as a bluetooth device, pushed the sync button for the fast pulsing light, it see's it, I click connect, and done. Working towards figuring out how to read it from Bluetooth in both OS's. |
|
Ah! looping is at least a bit more common problem - that's mostly because of the ERTM thingy which should gets disabled while installing xpadneo. Can you give me again the output of:
What do you mean by "says it still exists"? |
|
Sorry I don't see a |
|
hum, that's a hard one,... have you ensured that the gamepad is disconnected - I mean really removed - from the native OS? And have you rebooted the system after the |
|
Yes, there is no way for it to be talking to the native OS right now, as the Bluetooth adapter is passed through to the VM, I don't have it connected with USB, and I have the Windows Wireless Adapter pulled out sitting on my desk :). Having said that, I detatched the Bluetooth adapter again (probably the 100th time), did a couple reboots, ran the delete command again, this time getting the I have to assume it "auto-pairs" because the controller is actively looking for that adapters MAC on power on, presenting the Ultimately, who knows what was going on, I'll report back if there are any further issues. Thanks for the help. |
|
perfect, this device is definitely naughty sometimes... anyhow I am happy it works now - I will add the given advices to the README later on. |
|
I think a lot of it also has to do with the fact this is the first time on discovery that it picked up the UUIDs. I think its pretty hard for it to determine what profile/module to select/load when it doesn't have those. Specifically, these 3 lines, this was the first time I saw them when scanning/auto-pairing. |
|
This seems a lot like the problem I've been having with my controller. I have not been able to get it to reliably connect. Usually, I have to go to the terminal and manually connect it in bluetoothctl. As a workaround, I've made an easy script (replace the MAC address with your own): And running that a couple times usually gets it to connect. The only time I can connect 100% of the time, is at boot. If I power on the XBox controller before I start my PC. When the desktop loads up, it will connect every time. But if I wait until after the desktop loads up, I have to use the above script, once or sometimes a couple of times to connect. I'm thinking it has something to do with some USB Bluetooth dongles don't play as well with Linux and the Xbox controller. If I use the dongle on Windows, it seems to work fine, on the same PC and on other PCs I've tested. If I use the same Xbox controller using a Linux PC with an internal bluetooth adapter, it connects perfectly. I have a generic bluetooth gamepad that works perfectly with this dongle on Mint and in Windows. But using the USB dongle with the Xbox controller with Linux Mint on two different PCs have the same issue. It seems to work fine once it's connected, but it's a real chore to actually connect. I've tried removing the controller, and pairing again. I've tried unplugging and replugging in the dongle. I've tried this tip: https://unix.stackexchange.com/questions/255509/bluetooth-pairing-on-dual-boot-of-windows-linux-mint-ubuntu-stop-having-to-p. Nothing works reliably, other than immediately connecting at boot. |
|
Yeah, I am having issues getting it to connect without running the same. The other main issue I am experiencing right now, is js0 just seems to stop streaming data, and I am forced to go through reconnecting again. When plugging in with USB, js0 streams like a charm. :) |
|
I am really sorry guys to hear that, but it is definitely not a problem with xpadneo itself, believe me. Xpadneo does nothing as long as the gamepad is not connected, it is not even loaded. I cannot help you therefore by fixing a bug or sth like that, I fear. But feel free to discuss here and exchange experiences :) And feel free to open new issues if something else doesn't work. Cheers! |
|
Heh, I’m giving up I think. Something about this setup is entirely unreliable, and I just don’t know enough to know what piece is the issue. Still having issues with input from the controller just stopping in the middle after a successful connection, randomly, while on Bluetooth. As well as auto connecting issues. My PS3 controller seems to work just fine over Bluetooth. Had an input streaming test running for about 30m with no hiccups. Auto connecting seems to work with it as well, no issues. Even after reboot. And in Windows, both work perfectly on Bluetooth. So, I think I’ll be using a PS3 controller for my project instead, even though it’s not nearly as comfortable as the Xbox controller. |
|
I know that it can be a pain in the ..., but believe me - the gamepad is worth it - once it runs. |
|
It is a Broadcom BCM20702A0. I just find it strange, that if it was the adapter, then why does the PS3 controller not have its input hang after a successful connection as the Xbox one does? |
|
We still don't know what exactly is causing the connection problems, and I don't say that it is the adapter, it is most probably the adapter in combination with the GP under linux. Therefore changing the adapter is probably the easiest solution, but if you want to dig a bit deeper: go on, I would appreciate it to know the underlying problem in linux. Do you still have enabled the debug output? And if, what is the output right before the connection hangs - if there is any. Furthermore: the js interface is a bit deprecated, I would always use event if possible (has nothing to do with the connection, just btw) |
|
Yeah, js0 is just easy to read right off the bat for basic this button, this value @ 8 byte values. I do have everything still setup, I am just out of time for now. I will likely have to revisit this with you later in the week. I am not even against setting up an SSH account/Teamviewer for you and working with you directly over slack or similar. I'd love to see/learn this side of linux. |
|
I would be happy to help you, but before we can examine the problem any further, we should localize the problem a bit more by trying another bt-dongle first ;) |
|
If it helps anybody, here are the Bluetooth USB dongles I have. Panda Bluetooth 4.0 USB Nano Adapter (Amazon link) Using: I have a second one: Using: So, both dongles I have result in the same unreliable behaviour, and it looks like they use the same Cambridge Silicon Radio chipset (probably should have done some research before buying two dongles with the same chipset). On my miniPC that has an internal Bluetooth chip, and the controller connects immediately, I don't know how to find the exact model, but |
|
Unfortunately both are not available in Germany, I will see If I can get one somewhere else cheaply |
|
Btw, great article to localize the Problem: https://wiki.ubuntu.com/DebuggingBluetooth |
|
I decided to buy a different USB adapter. I found one that advertises a different chipset. Plugable USB Bluetooth 4.0 Low Energy Micro Adapter From the link provided by @atar-axis it seems one command is And This appears to be the same chipset mentioned by @jslay88. With this new Broadcom chipset adapter, the Xbox One S controller connects perfectly. Usually by the 2nd or third time the connection light on the controller blinks it connects. I have no issues reconnecting. It works exactly the way I would expect it to. For completeness, here is what I get with The Cambridge Silicon chipset provides a link policty of 'HOLD' and 'PARK', but I have no idea if that has anything to do with anything. So, for me at least, the issue seems to be the dongle. I have a feeling there might be something more to the issue. On a quick look at Amazon, it seems that most of the cheap dongles list CSR (for Cambridge Silicon Radio) as the chipset. So if the chipset was the only issue, I'd expect more people to be running into this issue. As an unrelated side note, I find the Pluggable USB dongle is shitty for audio (tends to be laggy and doesn't connect as well to my headphones). I really like the Panda dongle since it has a discreet green light instead of the bright blue LED that most dongles have. For now I'm actually using both. The Pluggable dongle only for the controller, and the Panda dongle for everything else. @atar-axis if you want to test out one of my Cambridge Silicon Radio chipsets, I'll send you one. I have a spare one. |
|
I am super happy that it works now, at least for you @ugly95 . It's strange that the same chipset does works on your machine, but not on @jslay88 's... just another riddle, looks like it is not the chipset itself but the way it is driven. hum I would appreciate it if you would send me one of your spare ones, where are you from? |
|
Just a follow-up on this after testing for a week or two. With the Broadcom-based adapter, the controller still works fine. But it is quite sensitive. For example, if I plug the adapter into a cheap 4-to-1 USB hub, the adapter does not work at all. If I plug the adapter in one of my monitor USB ports (which essentially is a USB hub that connects to one of the rear panel USB ports on my PC), the controller connects fine and generally works, but has issues. For example, it's a bit laggy at times, especially if I don't press a button for a minute or two. And sometimes the rumble will get stuck on until I power cycle the gamepad. For best results I have a USB extension cable running from a USB port on the rear panel (I think it's a USB 2.0 port), and up to my desk. Even though this is physically farther away from me than the monitor USB port, this works best. No lag, no rumble issues and connects well. I did try testing the adapters in a different distro (Manjaro). I didn't see any different results, and when I went back to my normal distro (Mint), none of the adapters would connect. To fix I purged bluez and reinstalled: @atar-axis |
|
I just followed #76 (comment):
I removed the controllers in bluetoothctl, rebooted, than run |
|
Yeah, maybe we should add that to the docs: Currently, the controller can only be added with scan mode on I believe. I'm not sure if this is due to updated firmware in the controller, or due to changes in the Linux Bluetooth stack, tho. |
Describe the bug
Ubuntu 18.10 Desktop
Disabled Secure Boot
I have installed prereqs, can scan, pair, and trust the controller. Connecting Fails.
Cannot enable debug as
/sys/module/hid_xpadneodoes not exist.To Reproduce
Steps to reproduce the behavior:
Fresh install of Ubuntu 18.10, EFI, Disabled Secure Boot
git clonerepoapt installprereqscdintoxpadneosudo ./install.sh-- reports successsudo bluetoothctlscan onpair EC:83:50:C3:D6:BCtrust EC:83:50:C3:D6:BCconnect EC:83:50:C3:D6:BCExpected behavior
A connected controller
System information
I cannot enable Debugging.
uname -a--Linux ubuntu 4.18.0-15-generic #16-Ubuntu SMP Thu Feb 7 10:56:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linuxsudo mokutil --sb-state--SecureBoot disableddmesg--sudo find "/sys/kernel/debug/hid/" -name "0005:045E:*" -exec sh -c 'echo "{}" && head -1 "{}/rdesc" | tee /dev/tty | cksum && echo' \;-- Returns nothingThe text was updated successfully, but these errors were encountered: