When it fails to start, there is no daemon.socket file. daemon fails to start and the daemon log is created but remains at 0 bytes. ![]() Telepresence proxy: ON (networking to the cluster is enabled) Kubernetes context: arn:aws:eks:us-west-2:xxxxxx:cluster/xxxx-eks > sudo telepresence statusĮxclude suffixes: > pgrep -lf daemon-foregroundħ5804 /usr/local/bin/telepresence daemon-foreground /Users/sean.sabour/Library/Logs/telepresence /Users/sean.sabour/Library/Application Support/telepresence TERM=xterm-256colorĬurl: (7) Failed to connect to fault port 443: Operation timed out Srwxrwxrwx 1 root daemon 0 Jul 26 13:06 telepresence-daemon.socket > sudo telepresence connectĬonnected to context arn:aws:eks:us-west-2:xxxxx:cluster/xxxx-eks () Telepresence: error: daemon service did not start (see "/Users/sean.sabour/Library/Logs/telepresence/daemon.log" for more info) Need root privileges to run: /usr/local/bin/telepresence daemon-foreground /Users/sean.sabour/Library/Logs/telepresence '/Users/sean.sabour/Library/Application Support/telepresence' '' ![]() rw-r-r- 1 root wheel 0 Jul 19 13:00 wifi Srw- 1 root daemon 0 Jul 19 12:59 vpncontrol.sock Srwxrwxrwx 1 root daemon 0 Jul 19 12:59 1 root daemon 6280 Jul 26 13:00 utmpx Srw-rw-rw- 1 root daemon 0 Jul 19 12:59 systemkeychaincheck.socket r-r-r- 1 root daemon 0 Jul 19 12:59 systemkeychaincheck.done Srw-rw-rw- 1 root daemon 0 Jul 19 12:59 1 root daemon 3 Jul 19 12:59 syslog.pid r- 1 root daemon 0 Jul 19 12:59 socketfilterfw.launchd Srwxrwxrwx 1 root daemon 0 Jul 19 12:59 pppconfd Srwxrwxrwx 1 root daemon 0 Jul 19 12:59 portmap.socket Srw-rw-rw- 1 root daemon 0 Jul 19 12:59 mDNSResponderĭrwx- 3 root daemon 96 Jul 19 13:00 mds rw-r-r- 1 root daemon 6 Jul 20 11:13 hdiejectd.pidĭrwx- 2 root admin 64 Jul 22 16:27 jamf rw-r-r- 1 root wheel 16 Jul 19 13:00 fudinit Lrwxr-xr-x 1 root daemon 72 Jul 19 13:04 docker.sock -> /Users/sean.sabour/Library/Containers//Data/docker.sock Lrwxr-xr-x 1 root daemon 76 Jul 19 13:04 docker-cli.sock -> /Users/sean.sabour/Library/Containers//Data/docker-cli.sock rw-r-r- 1 root daemon 3 Jul 19 12:59 diskarbitrationd.pidĭrwxr-xr-x 3 _displaypolicyd _displaypolicyd 96 Jul 19 12:59 displaypolicyd Srwxrwxrwx 1 root daemon 0 Jul 19 12:59 cupsd r- 1 root daemon 0 Jul 19 12:59 .didRunThisBoot rw- 1 root daemon 0 Jul 19 13:00 automount.initializedĭrwxr-xr-x 3 _assetcache _assetcache 96 Jul 19 13:01 rw-r-r- 1 root daemon 6 Jul 26 12:59 auditd.pid ![]() rw-r-r- 1 root daemon 4 Jul 19 12:59 appfwd.pid are fine.-rw-r-r- 1 root daemon 6 Jul 20 11:12 PanGPS.pid FFmpeg is more CPU-intensive and much more laggy than AMD decode on 22.11.2, so ffmpeg is not ideal on a laptop utilizing an iGPU. I've rolled back to 22.11.2 on my AMD laptop (Ryzen 7 4700U w/Vega iGPU) as I use the Parsec client frequently from that laptop. The other workaround is to roll back to AMD Radeon driver 22.11.2, as that driver has zero problems from the Parsec client side. The workaround using ffmpeg (as the decode method within the Parsec client, requires some files to be installed) continues to be the only choice while this issue is being sorted out with the newest drivers, 23.x.x. ![]() The AMD overlay now pops up when connecting to a host in fullscreen mode, but no frames are returned/decoded. The driver seems to be getting further than it did before. What you'll see is the image below instead of an error being thrown. The error -14 is gone but what happens is a complete frame is never returned when attempting to connect to a Parsec host. Parsec Client decoding is still broken under 23.3.1 when AMD is chosen as the decoder method, whether h.264 or HEVC h.265 is used. As of this post, the AMD Link client app is broken in Windows 11. Today I launched the app and it says an update is available, but I can't for the life of me figure out how to get the app to update as it will not update within the Microsoft app store. As of yesterday AMD Link refused to connect to any of my AMD systems running the latest 23.2.1 driver. The AMD Link app for Windows is also broken. OBS Studio is also impacted and does not run properly under 23.2.1. I rely on Parsec for streaming, remote desktop access, and remote gaming, so it's a big inconvenience in my case having decode broken in AMD's latest drivers. Steam Remote Play, which utilizes some form of hardware GPU decoding, is also working fine. From the testing I've done with the new 23.2.1 drivers, games and other 3D graphics apps involving the GPU seem to run fine. I'm not sure how many other applications will be affected by decode being broken in 23.2.1. Adrenalin 23.2.1 included a number of rolled-up changes that were implemented for the 7000 series AMD Radeon GPU's, including a broken decode.
0 Comments
Leave a Reply. |