Administered by:
@grunge_foxHmmm, I tried the new postmarketOS os-installer image (specifically google-x64cros, as I'm using an x86 Chromebook with MrChromebox firmware, and postmarketOS seems to be the only Linux distro that I know of to come with the audio fixes), and it's just so slow and buggy. I've already tried various other distros that use GNOME's OS Installer, but never had this bad of an experience with it, as on postmarketOS's live session. It just keeps showing me "This app isn't responding dialogue" every time I click anything 
Also, the first time I booted into it, the OS Installer kept showing me "The installation was unsuccessful" after every step, but pressing the back arrow button, put me onto the next step of the installer, and once I went through all the steps, and it said it started installing, the console was blank, for about half an hour, until I decided to stop the installation 
But, I've booted into it for the 2nd time, and this time, the only issue I've encountered was that it kept not responding, but no other error showed up. It did start the installation almost right away this time, but I'm now stuck at 100% of package install, for the past 40 minutes, and I honestly don't know if I should wait, try the whole process again, or just give up... 
Unfortunately, the postmarketOS's repos are kind of a mess, so I don't even know where to report an issue for this 
@grunge_foxOkay, it did install about 5 minutes after I posted this, but... The audio is definitely not working, so the Wiki is definitely wrong about AMD Picasso Chromebooks working "perfectly fine". Also, my Bluetooth doesn't work either, even tho the WiFi does? I'm confused, because I haven't had an issue with Bluetooth on any distro so far 
Man, I was so excited about finally being able to test this distro, as I couldn't figure out how to install it before... Like, the installation instructions are also really counterintuitive, because they're for all Chromebooks, both x86 and ARM, which probably assumes you're using modified Google firmware (which allows you to dual boot ChromeOS and Linux), but I'm using the MrChromebox's custom firmware which is completely different (supports Linux and Windows, but not ChromeOS), so I have no idea how to install it on my machine. I thought the os-installer image will finally fix that problem for me, but it feels like it's just not working as intended? Maybe the audio and Bluetooth are broken because it assumes I'm using the modified firmware, and not the custom one? I wish it was explained better
@grunge_foxI'm now convinced that the os-installer, despite being only available in postmarketOS Edge images, still installs the stable version of the system. For whatever reason, the live session was running Linux kernel 6.15, but after the install, it says it's using 6.12 LTS?? This might also explain why my audio doesn't work, because I think I had an issue with ALSA on 6.12 previously, but it was fixed once I updated to 6.13
@grunge_fox@wetdry.worldNo, I am using postmarketOS Edge, because I have systemd running. The LTS is still using OpenRC. How the fuck did I get LTS kernel then? This is such a mess WTF
@grunge_foxI think the postmarketOS Wiki page for ChromeOS devices is either a massive lie, weirdly phrased, or I somehow fucked up the install. The audio on AMD Picasso is simply not working, and I can't even fix it with the script that usually works, and also keyd is not installed, nor there's any keyd config that I can find anywhere. Why does the Wiki even mention the audio working and keyd being pre-installed with a special config? Does it only not apply to the generic x64 Chromebooks or something? What the fuck...
@grunge_foxIs there anyone in #postmarketOS or #Chrultrabook that could help me with this? I'm so lost and confused
@grunge_foxI tried the generic-x86_64 os-installer image today, and not only the boot screen was extremely different from the google-x64cros image (different logo size, the text at the bottom was also smaller on the generic image, and actually stated it's running Linux kernel 6.12 LTS, instead of 6.15), and I also had no "This app isn't responding", not even once. However, while most steps went fine, and the installation started immediately, it did still fail, while trying to download the system packages, and stated no error messages about it. Tried it the second time, same result. I really don't know if I'm just doing it wrong, or if it hates my USB stick (I have only one, and to be fair, most distros install with it fine, maybe besides Calamares-based ISOs, which have 99% chance of failure, for whatever reason), or if this distro just hates me in particular... 
I think I'm going to flash the GNOME-only google-x64cros image, and try figuring out how to install it manually, if I manage to figure it out, because so far, the instructions are just too confusing, and my brain can't comprehend any of it... If this also fails, I'm going to go back to stupid Fedora, which might be the most annoying distro I've ever used, but somehow also the most reliable, very predictable, and trivial to install... <- trying to distrohop away from Fedora for the past 3 years or so, always goes back to using it, because every other distro fails in one way or another
@grunge_foxOh, the reason why it failed at downloading the system packages today wasn't due to the installer's fault. Apparently FFmpeg AV1 requires some kind of dependency that just... doesn't exist in the repos, apparently?
Which is really annoying, because I don't even care about AV1, my system doesn't even support decoding it. I think I might just give up on postmarkerOS entirely. I had high hopes about this distro before I tried it, but my experience has been nothing but suffering so far...