devmapal / nvidia-shield-controller-driver Goto Github PK

Hello all,

I understand the P2P connection itself might not really be within the scope of the project (as it's not part of the driver presented in this repository), however, I have been unsuccessful when trying to connect my 2015 Shield Controller wirelessly to my Linux PC and I was hoping I could get some support here, to eventually be able to use the Ozwpan driver as well.

My system:

Ubuntu 20.04.2
Linux 5.10.18-051018-generic
Intel AX200 WiFi (it supports P2P-GO)
wpa_supplicant v2.9

I can add the P2P group no problem:

5: p2p-wlp4s0-0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 68:54:5a:18:2d:76 brd ff:ff:ff:ff:ff:ff

However, when attempting to run wpa_cli commands on it I get:

Could not connect to wpa_supplicant: p2p-wlp4s0-0 - re-trying

Thus, I can't pair my controller. I've been trying with different wpa_supplicant versions and at one point I could connect to the P2P interface. However, upon issuing "wps_pbc", it would stay at "WPS-PBC-ACTIVE" until timing out, with the controller still flashing. In this case, I could see connection attempts in the wpa_supplicant log (referencing the correct MAC from the controller), but they were apparently ignored with a "no valid beacon" message.

Stucked in this situation I would like to ask: has anyone managed to use the controller in a similar system? Any more pointers?

Thank you very much and kind regards!

I had this working pretty well until recently. After the last couple updates on Fedora 26, the controllers have stopped working. The connection procedure works fine, devices enumerate correctly, but no input actually gets through. Not mouse, not gamepad, nothing. I was able to boot a previous 4.11 kernel and it worked fine. Any ideas what might have changed?

I know a little about computer science but where should I start? And does this work for windows 10? Thanks and sorry for the dumb question

Are you able to give more details on the pairing process? I've tried to monitor the WiFi signals between the Sheild and Controller although I don't see how the pairing takes place. I would have expected to see a AP show up that gets connected to during the pairing process. If I create a WiFi Direct Advertisement as a Group Owner on a PC how do I get the to connect?

I am trying to apply your patch to a ubuntu 16.04 kernel tree and it is failing:

I have installed the kernel source package as per (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel)
When trying to apply your patch, i get the following:

poine@adam /usr/src/linux-source-4.4.0/linux-4.4.0 $ sudo patch --dry-run -p1 < ../../nvidia-shield-controller-driver/driver/0001-Revert-staging-ozwpan-Remove-from-tree.patch
checking file MAINTAINERS
Hunk #1 succeeded at 10288 with fuzz 2 (offset -848 lines).
checking file drivers/staging/Kconfig
Hunk #1 succeeded at 78 with fuzz 2 (offset 8 lines).
checking file drivers/staging/Makefile
Hunk #1 FAILED at 25.
1 out of 1 hunk FAILED
checking file drivers/staging/ozwpan/Kconfig
checking file drivers/staging/ozwpan/Makefile
checking file drivers/staging/ozwpan/README
checking file drivers/staging/ozwpan/TODO
checking file drivers/staging/ozwpan/ozappif.h
[...]

any suggestion on what i am doing wrong ?

Best Regards

Can I get some more info on how you got this to work? I'm trying to replicate it on Fedora 24 with no luck. I can create the ago interface and start the pairing, but the light continues blinking and wpa_cli loops the following messages:

<3>CTRL-EVENT-EAP-STARTED ${macaddr}
<3>CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1

System Info:
OS: Fedora 24 x86_64
WiFi card: Think Penguin TPE-N150USB (Atheros AR9271)
wpa_supplicant: wpa_supplicant-2.5-5.fc24.x86_64

I'm trying to get this working manually, then I'll be poking at a userspace program to handle the pairing and ozwpan configuration (via the ioctl interface) automatically. There's also a lot that could be done with the blake interface to get battery info and such. The SHIELD stock Android roms contain two cli programs (blake and lota) that handle controller status and firmware updates respectively. Should be possible to sniff those and fold them into a userspace driver.