安裝 Steam
登入
|
語言
簡體中文
日本語（日文）
한국어（韓文）
ไทย（泰文）
Български（保加利亞文）
Čeština（捷克文）
Dansk（丹麥文）
Deutsch（德文）
English（英文）
Español - España（西班牙文 - 西班牙）
Español - Latinoamérica（西班牙文 - 拉丁美洲）
Ελληνικά（希臘文）
Français（法文）
Italiano（義大利文）
Bahasa Indonesia（印尼語）
Magyar（匈牙利文）
Nederlands（荷蘭文）
Norsk（挪威文）
Polski（波蘭文）
Português（葡萄牙文 - 葡萄牙）
Português - Brasil（葡萄牙文 - 巴西）
Română（羅馬尼亞文）
Русский（俄文）
Suomi（芬蘭文）
Svenska（瑞典文）
Türkçe（土耳其文）
tiếng Việt（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
2 
檢舉此篇文章
Not sure if you can help, or anyone, but I'll ask. I am trying to get this to work.
I've enabled steamos dev mode
I've installed wpa_supplicant ( and wpa_gui, is it needed?)
Questions:
I am not sure how to setup wpa_supplicant.conf
I am not sure how to apply the patch to the rtw88 driver
Thank you!
Disclaimer: doing stuff like this can soft brick your hardware and you might be required to reinitialize your Steam Deck and/or format your internal drive. Take backups before it's too late to do. I'm not responsible for bricked hardware, just to be clear ;)
Before starting, you should need to install all the build tools necessary for compiling software. SteamOS is extremely barebone, so I'm not sure if it's probably easier to use Distrobox and install this docker container https://github.com/SteamDeckHomebrew/holo-docker/pkgs/container/holo-base which is already ready for compiling stuff. If you want to use the stock system, you might have to google around for errors before being able to start. ArchLinux (the base for SteamOS) requires at least base-devel, so at least run sudo pacman -S base-devel before following along (reference https://wiki.archlinux.org/title/Makepkg ).
This is generally the process:
1) Download this folder from the evlav repo, that contains the build scripts for the kernel itself: https://gitlab.com/evlaV/jupiter-PKGBUILD/-/tree/master/linux-neptune-61?ref_type=heads
2) copy the patch file mentioned in the mailing list above inside a text file with a name of your choice, like p2p.patch, inside of the folder previously downloaded. The extension .patch name is important to be there.
3) Open the file called PKGBUILD with a text editor and add the filename above after row 23 and before the closing parenthesis. This will include the patch file as a source to the build process and it will be automatically included in when we compile the kernel.
4) Open a terminal like Konsole and move inside the folder with cd 'pathname'.
5) Run updpkgsums when inside the folder with to add the checksum for the patch file that we have previously added. It might take a while to do this.
6) Now just run makepkg inside that folder. This will kick off the build process for compiling the kernel with the patch compiled in. This will take a while, so just wait.
7) When the terminal return control to you, if the compilation process ended successfully you should have inside that folder a couple of archives with the name of linux-neptune-61-<version_number>.tar.zst and linux-neptune-61-headers-<same as above>. This are the packages with the patched kernel. To install and replace the current running kernel you just do sudo pacman -U <two filenames above>. This should ask if you want to install and replace the current ones. Press yes.
Reboot and you should load the patched kernel.
Then check for p2p support and do further tests.
Also wondering since there is /lib/modules/6.1.../kernal/drivers/net/wireless/realtek/rtw88/rtw88* files if that means the driver can be compiled by itself and swapped in...
You can definitely compile single modules and just replace them, but creating a package is safer in order to avoid to have binaries incompatibility between the built module and the kernel installed in. If they are the exact same it should not matter and work fine nonetheless.
Wifi works but p2p doesn't seem to be enabled. Was a learning experience at least. All I can think to try next is use the rtw88/main.c from an updated repo that includes the missing parts of the patch.
Using Chrome to cast the screen in desktop mode as suggested earlier works ok, altho no audio and requires chromecast device. Tried vlc too, which has huge delay, and no audio there over chromecast either.
From my still limited experience with it the latency won't be that bad, but the image quality will drop with rapid screen changes as the compression can't keep up the high quality, though that may not be the universal experience, and absolutely should expect some latency increase.
For a serious twitch reaction type game wireless is rarely if ever going to be a good idea - even if the latency and bandwidth are usually good for superb image quality that RF interference will mess with it once in a while - a cable is reliable. But for the most part it should be good enough for sharing your game with others and most types of game, and would be a very useful thing to have when using the deck like the portable computer it is.
Google made high quality chromecast for game streaming. Chromecast ultra which supports stadia should be quick.
I am more worried about the TV itself. TV manufacturers do not care about latency......
https://superuser.com/questions/419070/transatlantic-ping-faster-than-sending-a-pixel-to-the-screen
I've made the necessary modifications and now the device exposes correctly P2P GO and P2P Device successfully (i'll post the patch shortly here if someone else want to test this on their own pace with a short guide on how to apply it). From the core code at a quick glance P2P seem to be handled in some way, so it might just work with that. If so, I'll submit this on the kernel mailinglist in the hope that they'll integrate in mainline Linux.
If someone can suggest an easy case to test maybe I could take another look at it. I've tried miraclecast as a test but I couldn't see any receiver from an AOSP android phone, not sure what's broken tho (if it is miraclecast or the driver, but from the raw logs from wpa_supplicant + no error messages from kernel this looks quite possibly working fine already).
Patch to apply to main.c here: https://pastebin.com/9JYb5hXQ
DISCLAIMER: This is given 'as-is' with no warranties, and is intended for people who know how to work with computers. I'm not responsible for exploding Decks or similar issues (although I doubt that this will happen).
To apply this I'll assume that you are using ArchLinux as a base:
Edit: the patch seems to give a couple of messages about ending in the middle of file but it applied succesfully anyway, so just ignore it. It should still work.
I don’t have the fortitude to go through patching rtw88 again only to run into issues. At least for now. It does seem like we’re close to having this built-in….