#asahi · 2022-12-11 14:01
marcanit will see the empty space, I just hope it doesn't think it isn't enough or ends up with rounding issues#asahi · 2022-12-11 14:01
marcanyes, it requires a full stub reinstall and the installer does not have a way of doing that without also doing a full install#asahi · 2022-12-11 14:00
marcan(I hope this actually works, I'm not sure I ever tried an in-place "tight" reinstall like that... there could be issues with sizing, I should test it)#asahi · 2022-12-11 13:58
marcanand you'll have to fix the UUID for the EFI partition in your /etc/fstab most likely#asahi · 2022-12-11 13:57
marcanthen yeah, you'll have to reinstall the stub. probably back up the EFI partition, delete it and the stub partition, reinstall the stub, and restore the relevant contents (EFI subdirectory and maybe m1n1/boot.bin if you updated m1n1 more recently than the latest images)#asahi · 2022-12-11 13:56
marcanthe actual distro images always required 12.3#asahi · 2022-12-11 13:56
marcanthe installer always checked, but had a 12.1 option available with the UEFI boot option I think?#asahi · 2022-12-10 12:14
marcanyou'll have to wait until either FEX implements 4K page emulation or we get 4K kernels usable#asahi · 2022-12-10 12:13
marcanqemu is going to be too slow to be usable for games#asahi · 2022-12-10 10:15
marcanjmshrv: as expected, but good to hear that :)#asahi · 2022-12-09 17:19
marcanthat's why the speakers have never been enabled and won't be until it's safe#asahi · 2022-12-09 17:19
marcanLaddda: Asahi has never been dangerous to install, we make sure of that#asahi · 2022-12-09 17:18
marcanif that reason weren't there I probably wouldn't bother, but that's a damn good reason#asahi · 2022-12-09 17:18
marcanaxboe: there's a good reason to put it in the kernel: it'll work in s2idle#asahi · 2022-12-09 17:18
marcanaxboe: lol :D#asahi · 2022-12-08 16:10
marcanbcrumb: that's something else (I think, sven?)#asahi · 2022-12-08 16:10
marcanunless I missed something#asahi · 2022-12-08 16:10
marcanfwiw the modules should be in the initramfs as of recent asahi-scripts#asahi · 2022-12-08 16:05
marcanforcing DPI is likely to cause other issues with apps and is not really supported on wayland#asahi · 2022-12-08 16:05
marcanthis is being fixed in wayland, see the above bug#asahi · 2022-12-08 15:59
marcanbut it's barely noticeable, and macOS does the same thing. KDE at 150% looks pretty similar to macOS tbh, as far as font rendering.#asahi · 2022-12-08 15:59
marcanunless you're talking about stuff looking *slightly* softer with non-integer scaling: https://bugs.kde.org/show_bug.cgi?id=446674#asahi · 2022-12-08 15:57
marcanit's normal for stuff to look blurry when first applying until you restart#asahi · 2022-12-08 15:57
marcanfonts look fine for me, did you log out and back in after changing the settings?#asahi · 2022-12-08 15:50
marcanuse output scale instead#asahi · 2022-12-08 15:50
marcanthat setting should be off in wayland#asahi · 2022-12-08 15:50
marcanit's mentioned in the article#asahi · 2022-12-08 15:50
marcandon't set font DPI#asahi · 2022-12-08 14:34
marcansee https://asahilinux.org/2022/11/november-2022-report/#asahi · 2022-12-08 14:32
marcan(this is similar to how the installer internally encodes beta version numbers)#asahi · 2022-12-08 14:31
marcanfor example, 12.3 beta1 would probably end up as 12, 2, 99, 1#asahi · 2022-12-08 14:30
marcanso ideally don't hardcode that#asahi · 2022-12-08 14:30
marcanalso the version number length can change in principle#asahi · 2022-12-08 14:30
marcanyou can just report it numerically as %d.%d.%d :)#asahi · 2022-12-08 14:28
marcanin this case I think we want to reject missing props, since this is critical information#asahi · 2022-12-08 14:28
marcanfor DCP right now, I think it should just drop the unknown version check for the version field#asahi · 2022-12-08 14:27
marcancompat can be checked for exactly since we define the "blessed" versions and those are all that should go in compat#asahi · 2022-12-08 14:27
marcanthe only piece that should care about exact actual firmware versions is m1n1#asahi · 2022-12-08 14:26
marcanand for the latter, the check ideally needs to be done with an actual vercmp style greater-than check, not a hard match#asahi · 2022-12-08 14:24
marcanthe idea is we check compat only unless a new version adds optional but backwards compatible features, in which case we use version to check for that#asahi · 2022-12-08 14:24
marcanyou're supposed to check the compat version lol#asahi · 2022-12-08 14:23
marcanoh wait, you check the firmware version, not the compat version?#asahi · 2022-12-08 14:23
marcanjannau: m1n1 sets compat as 12.3.0#asahi · 2022-12-08 14:20
marcanbut I'll properly tag a build and push it to the production installer so we can tell people who run into it what to do#asahi · 2022-12-08 14:20
marcanI'm going to leave this as expert-only for now since it's such a weird edge case, so we don't proliferate 12.3.1 just in case#asahi · 2022-12-08 14:17
marcancool, let me push m1n1 then, thanks for finding this :)#asahi · 2022-12-08 14:15
marcanI know the keyboard/trackpad is a problem#asahi · 2022-12-08 14:15
marcanand just generally debug suspend, I barely had a chance to look into it beyond the stuff that completely broke it#asahi · 2022-12-08 14:14
marcanI need to add a current log thing to the battery driver, so we can debug this stuff#asahi · 2022-12-08 14:13
marcanokay yeah, lots of reports for that one