Anyone else just getting a black screen on their steam deck after updating?
Anyone else just getting a black screen on their steam deck after updating?
Ai like immutability tbh
Vi also like it when it works
Vgive it a while, it might be doing some extra set up. i've had that happen a few times after an update and i just have to be really patient
Ait should be working???
DWhen I press the B button ^[ appears on screen, A makes a line break. It looks broken to me, not like it's loading sth
DIt also killed my clover install
D(That I need because I dual-boot and Steam Deck BIOS doesn't let you change boot priority and just boots windows by default)
Ahw decode works with mpv inside a container, idk if its just encode thats not working??
Vmaybe encoding is actually broken on bazzite? i honestly don't know
Vi don't know of anyone atm who is using bazzite on an amd card who has sunshine perfectly set up
Ano clue
Tsame here...
Tnot sure what to do tbh.
RYeah, same reason for sticking with Arch on my desktop.
RIt's fine for fixed or standard hardware, but if you have a weird configuration the immutability is far more a pain in the butt than a feature if you ask me.
REspecially around virtualization.
RI know that there are helper script for that, but they will never replace the arch wiki /s
RThis was the main issue I had when I tried Debian distro in the past.
REspecially for changing compile time flags in software.
Tthat heavily depends on if you need that software directly on the host image, and not in a distrobox, to be fair.
RYeah, but at the time distrobox didn't exists.
RNor a lot of other virtualization helpers.
RTherefore you either recompile or good luck.
Tyou sure man?
virt-manager exists for quite some time, aswell as docker and Podman.
virt-manager exists for quite some time, aswell as docker and Podman.
RYeah, I'm sure.
RStuff changed over the years.
RBesides, I'm still not a fan of virt layers over virt layer anyway.
RIt might have existed already in 2010, but good luck finding guides/help on them.
RAnd even the tooling itself wasn't quite there.
RJust far easier to recompile and enabling flags if you ask me.
Thonestly, if you can recompile stuff and enable flags across a variety of packages, you dont really need any particular guide for virtualisation.
RFair, but I'm not running a full stack VM for a single change.
Tpodman/docket isnt a full stack vm.
RAt that point I just use a different distro.
Tit shares the kernel of the host.
Tits like you are chrooting into another install
Twould you call that virtualisation too?
RDocker has been created in 2013
RSo after I had experiences with Debian.
Tand thats why i compare it to chroot.
RSo that was out of the picture anyway.
Tbecause that definitely existed way before docker
RTBH, I never tried that at the time, blame that at guides/help/knowledge found around at the time.
Tarchwiki mentioned it way back to verify if your installation was sucessful.
TLFS aswell
TGentoo aswell
RI used Arch from 2016(?) circa.
Twith way back, i seriously mean when arch was introduced.
RYeah, just need to call Intel to stop rereleasing quad cores for that /s
RYeah, I found arch far later to be honest.
