search

eniva / MisSTer_Guides

A collection of known tips and tricks to get stuff working or take advantage of advanced settings
26 stars 0 forks source link

dmesg show nothing even at debug level 9 #3

Open vinz2k opened 4 years ago

vinz2k commented 4 years ago

Hello

When using dmesg command after plug in my controller, i thought i will see the polling rate applied but that’s not the case, is it normal ?

Regards

vinz2k commented 4 years ago

E36BE6F6-1696-4D7D-B5A9-AF4D2C00E33F

eniva commented 4 years ago

Hello, let's see if jspoll setting is being applied properly first.

Try typing "systool -m usbhid -A jspoll" into the terminal and see what comes up. Also, what controller are you using?

vinz2k commented 4 years ago

Hello

Here is the result :

Module = "usbhid"

     jspoll                     = "1"

Doest it mean it’s ok ?

I use a raphnet adapter with 8bit do 2.4G snes classic adapter.

vinz2k commented 4 years ago

Hi

Any news ?

eniva commented 4 years ago

Hi, yes. Sorry, I'm on and off currently between breaks, spending time with families and friends. I'll return soon. By the looks of it, forced 1ms polling is at least set properly in the Linux kernel. Your screenshot doesn't seem to contain the complete log so I can't really tell, but unless it's a rare Bluetooth controller it should be at least being applied properly.

I'm working on a separate setting menu to manage custom polling rate on OSD so you don't ever have to deal with the boot parameters anymore. New values can be applied without rebooting the kernel (or MiSTer). The page is likely to report how many controllers are set to 1ms, so if you could wait on that you can check if your controller is working or not. It will take time as I'm working on bringing a blacklist feature all at the same time.

In the meantime, feel free to share the complete log and I will be more than happy to look into your case further! 😄

tekn0x commented 4 years ago

Also adding the "-v" can sometimes help if you can't see the information:: "systool -m usbhid -A jspoll -v"

What you are looking for in the dmesg output is the "applied interval" I have used =2 in my u-boot.txt: There is what that file looks like: v=loglevel=7 usbhid.jspoll=2 xpad.cpoll=2 btusb.bpoll=2 Here is the dmesg output: [ 2.885026] usb 1-1.3: new low-speed USB device number 5 using dwc2 [ 2.984923] usb 1-1.3: New USB device found, idVendor=0583, idProduct=2060, bcdDevice= 1.00 [ 2.993297] usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 3.000594] usb 1-1.3: Product: USB,2-axis 8-button gamepad
[ 3.010795] HID usage: 0x00010004, original interval: 10 [ 3.016162] JS: endpoint->bInterval=10, interval=2 [ 3.020962] HID usage: 0x00010004, applied interval: 2 [ 3.026372] input: USB,2-axis 8-button gamepad as /devices/platform/soc/ffb40000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:0583:2060.0003/input/input3

I hope this helps! Also, I am so excited about btusb.bpoll getting implemented. Thank you again so much @eniva for doing this project! :)