How To Apply Raphnet Kernel Patch To Fix "Northwest" Drift

[j.e.f.f]

@edmaul69 I wonder if there is something wrong with my setup... I can't see the other models behaving all that different.

I was pretty sure I followed the setup properly. Other than the scrolling problem, the controllers work great after hitting the D-pad once to stop the scrolling. I'm even considering picking up two more to have all four controllers wireless.

[edmaul69]

@j.e.f.f oh i know what you are saying. I have one. I have two of the pros as well. An fc30 pro and an nes30 pro. I dont have the issue with them but i do with my nes30.

[hansolo77]

Sorry to post in an old thread, but ti seemed redundant to create a new one... The latest "underlying kernel" update I did when I "updated all installed packages" broke the raphnet patch. So I need to reinstall it. Is it possible to patch without rebuilding the entire kernel again? If not, will going through this process still give me the latest updates to the kernel?

Suggestion - In future builds of the Setup Script, I think it should have this patch automatically applied when it does the kernel updates. Does this patch do anything to a system that doesn't have a raphnet adapter? If not, why not just include it?

[BuZz]

@hansolo77 said in How To Apply Raphnet Kernel Patch To Fix "Northwest" Drift:

Suggestion - In future builds of the Setup Script, I think it should have this patch automatically applied when it does the kernel updates. Does this patch do anything to a system that doesn't have a raphnet adapter? If not, why not just include it?

We don't provide custom kernels - RetroPie sits on top of existing OS. If you want the patches included, they need to be fed to upstream kernel development. https://bugzilla.kernel.org/ - They will then filter down eventually to the Raspbian kernel, but they might be willing to backport it if it's accepted upstream.

[Dhrystone]

Trying this and getting the following errors:

pi@retropie:~ $ cd linux
pi@retropie:~/linux $ patch -p1 < ../usbhid_iostart.diff
patching file drivers/hid/hid-core.c
Hunk #1 succeeded at 2508 (offset 335 lines).

pi@retropie:~/linux $ patch -p1 < ../usbhid_start_before_connect.diff
patching file include/linux/hid.h
Hunk #1 FAILED at 936.
1 out of 1 hunk FAILED -- saving rejects to file include/linux/hid.h.rej

pi@retropie:~/linux $ patch -p1 < ../jsdev_initial_value.diff
patching file drivers/input/joydev.c
Hunk #1 succeeded at 155 (offset -1 lines).
Hunk #2 FAILED at 234.
Hunk #3 succeeded at 916 (offset 68 lines).
Hunk #4 FAILED at 901.
2 out of 4 hunks FAILED -- saving rejects to file drivers/input/joydev.c.rej

[jthomas5150]

@edmaul69 Hi, sorry to reply to an old post but I have found no progress on the northwest movement when the SN30 (firmware v4.10) is turned on and connects. (This 8bitdo controller seems to be popular so I am surprised this issue is not more documented.) This problem appears on fresh Retropie 4.3 and 4.4 installs. Once I tap the d-pad the scrolling stops. I tried the above kernel patch and same issue. My other bluetooth controller, the wiiupro, does not scroll northwest when turned on. Any ideas? Makes connecting my second player 2 SN30 kinda a pain...

I would not mind buying two SN30 Pro controllers (as I hear this issue does not exist with this model), but I like the more simple SN30 controllers better for my NES/SNES games.

I am willing to help to troubleshoot in any way I can!

[edmaul69]

@jthomas5150 the problem is actually in linux and linux needs to be updated to stop it. Some controllers are affected and some arent. Most newer controllers have the problem fixed in them. But linux needs to actually fix the problem. If you use any usb controllers with the issue try putting them on a usb hub. Some people have luck that way.

[jthomas5150]

@edmaul69 Thanks for the reply. My USB controllers work just fine and so does my WiiUPro bluetooth controller. I wonder if anyone has any kind of bluetooth workaround like the Raphnet Kernel Patch but instead of fixing USB controller issues, addresses the bluetooth northwest issue for effected bluetooth controllers?

Would an aftermarket bluetooth adapter solve the issue i wonder...? Or maybe that is a dumb idea since there is an issue with the kernel.

[edmaul69]

@jthomas5150 if you have a northwest issue on bt, did you try the raphnet northwest fix?

[jthomas5150]

@edmaul69 I sure did. Did not help. Ran it on a fresh 4.4 install.

I think @j-e-f-f posted somewhere he also tried the above fix with no help using his bluetooth N30 controller...

[edmaul69]

@jthomas5150 ok. Wasnt sure if it would.

[jthomas5150]

Thanks for trying @edmaul69 !

Anyone else have a suggestion or is this issue not "fixable" with the SN30 controllers?

[Dopy25]

I know the last comment on this was over a year ago, but I am having issues applying these patches. Has there been any update to this process?

I am having the exact same issue as @Dhrystone from above. Second patch fails at 1 out of 1 hunk, 3rd patch at 2 out of 4 hunks. I tried repeating the whole process, and even proceeding anyway, but the patch still does not apply, and without the second (and third?) the only difference is that now emulation station is constantly scrolling.

[Asmodeus04]

@Dopy25 said in How To Apply Raphnet Kernel Patch To Fix "Northwest" Drift:

I know the last comment on this was over a year ago, but I am having issues applying these patches. Has there been any update to this process?

I am having the exact same issue as @Dhrystone from above. Second patch fails at 1 out of 1 hunk, 3rd patch at 2 out of 4 hunks. I tried repeating the whole process, and even proceeding anyway, but the patch still does not apply, and without the second (and third?) the only difference is that now emulation station is constantly scrolling.

I know this is a serious Necro, but I'd rather not lose all the progress on the thread.

I'm seeing the same issue here as @Dhrystone and @Dopy25.

Is anyone with a bit more kernel compilation experience able to offer some advice here?