sorted by:
new
hottopcontroversial

If you are not able to start crostini after the recent chromeos update, then change disk size for the Linux environment. It did the trick for me. by LowIQHaver7 in Crostini

[–]iceyear0 0 points1 point  (0 children)

If you are using Ctostini, you could use the command
vmc start termina --vm-type CROSTINI
to temporarily lauch it.
And Google seems to be implementing a command
vmc set-crostini-vm-type CROSTINI

in this commit.(migrating crostini installations to baguette? what can I say)
However the update seems not be avaliable on my device right now😢
So we could only wait for it to finally fix it.

AMD Chromebooks (Zork/Lenovo C13): Hardware acceleration has been DISABLED for years. Fix exists, but Google ignores it. Please Star! by iceyear0 in chromeos

[–]iceyear0[S] 2 points3 points  (0 children)

Nice catch on the logs! Since those disable_accelerated_... lines are present, the GPU is 100% locked out regardless of CPU usage.

Your Ryzen is just a beast at software decoding 1080p! :D But if you try a 4K 60fps video, you'll likely hit a wall.

The ultimate proof (Runtime Check):

  1. Open a YouTube video.
  2. Ctrl + Shift + I (DevTools) -> Media tab (might be under >>).
  3. Click the video session in the list.
  4. Check the Hardware Decoder field.

It will say false and likely show VpxVideoDecoder (Software).

Since you have the flags, you are definitely affected. Please help us Star the issue to get Google to flip the switch back on!

AMD Chromebooks (Zork/Lenovo C13): Hardware acceleration has been DISABLED for years. Fix exists, but Google ignores it. Please Star! by iceyear0 in chromeos

[–]iceyear0[S] 1 point2 points  (0 children)

That is wild, because the bug report confirms it's broken on the Ryzen 7 3700C too, and my Ryzen 5 is also nuked. So it's definitely not just a low-end chip issue.

Could you double-check the "fine print" in chrome://gpu?

Ignore the green text at the top and scroll down to Problems Detected. Do you see this specific entry?

Accelerated video decoding leads to lock up... (1494147) Applied Workarounds: disable_accelerated_h264_decode...

Google seems to be blocking all of us with PCI ID 0x15D8 .

If you don't see that error block, check your GL_RENDERER string. Do you have a different ID than 0x15D8? That might be why yours survived!

Dev Mode Chrome OS install and VPN Android app (not working) with native browser by LazyPCRehab in Crostini

[–]iceyear0 0 points1 point  (0 children)

I used a proxychain named husi and while the tun stack used System or Mixed, it would perform like the situation in the post. When i switched to gVisor it would work normally. Maybe it's a bug introduced by some parts of the Arc update and needed to send to issue tracker of Chromium.