#asahi-alt · 2025-09-15 17:44
jannauyou need an snapshot of idevicerestore though#asahi-alt · 2025-09-15 17:43
jannauno, https://docs.fedoraproject.org/en-US/fedora-asahi-remix/troubleshooting/#dfu-fedora and ignore that the instructions are written for fedora#asahi-alt · 2025-09-15 16:14
jannauwe can't mask packages from the overlay?#asahi-alt · 2025-09-15 16:06
jannautime to purge it with fire?#asahi-alt · 2025-09-13 21:38
jannaunot via usb-c#asahi-alt · 2025-09-13 21:36
jannauDP tunneling might drag thunderbolt into dcp#asahi-alt · 2025-09-13 21:33
jannaudcp will be annoying#asahi-alt · 2025-09-13 20:55
jannauhttps://www.kernel.org/doc/html/latest/arch/arm64/arm-acpi.html#asahi-alt · 2025-09-13 20:42
jannausee snapdragon X devices which are in a much better position than we as qualcomm has at least designed with it in mind#asahi-alt · 2025-09-13 20:39
jannauI think some people equate ACPI with x86 PC style install support which wouldn't be true for several reason#asahi-alt · 2025-09-13 15:59
jannaucraftyguy: yeah, I figured. we're in the process of sorting this out to not ship an ancient version#asahi-alt · 2025-09-13 07:59
jannauthat was one reason for the theme-able m1n1 logos#asahi-alt · 2025-09-13 07:59
jannauI was planning to build it in the fedora installer image creation. At least there we have easy access to the dtbs#asahi-alt · 2025-09-13 07:40
jannaurealized that it is ancient (October 2023)#asahi-alt · 2025-09-13 07:39
jannauany idea where m1n1 1.4.1 comes from? I fear it might be the version we ship in the uefi-only install option#asahi-alt · 2025-09-13 07:08
jannauthere is no mechanism which restores boot.bin. Did you replace the one on the partiotion with the part uuid in /chosen/asahi,efi-system-partition ?#asahi-alt · 2025-09-13 06:42
jannau/chosen/asahi,m1n1-stage2-version is interesting as well#asahi-alt · 2025-09-13 06:39
jannauthe uat-ttbs node in reserved-memory#asahi-alt · 2025-09-13 06:37
jannaubut even without it `dtc -I fs -O dts -o - /proc/device-tree` displays the boot DT. I would expect that #asahi-alt · 2025-09-13 06:35
jannauif you built the kernel with CONFIG_MTD_PHRAM we have access to the m1n1 log#asahi-alt · 2025-09-13 06:34
jannaucraftyguy: please boot with `modprobe.blacklist=asahi` in the kernel command line. that should boot without gpu and make it easier to diagnose#asahi-alt · 2025-09-12 16:42
jannauyou probably want CONFIG_DRM_SIMPLEDRM=y as well#asahi-alt · 2025-09-12 16:41
jannauhttps://github.com/chadmed/asahi-overlay/blob/main/sys-kernel/asahi-kernel/files/linux-6.16.4_apple_silicon_base.config should have all relevant CONFIGs #asahi-alt · 2025-09-06 11:47
jannauthe mesa driver overlay for app-emulation/fex-rootfs-gentoo-20250425 are not compatible with upstream mesa or virglrenderer. that's probably the explanation for the render errors#asahi-alt · 2025-09-06 11:44
jannautry mesa-25.2* then#asahi-alt · 2025-09-06 11:39
jannau"asahi: enable virtgpu support" was backported in 25.1.8 I haen't test it though#asahi-alt · 2025-09-06 11:37
jannaumesa-25.1.8 and later should be ok#asahi-alt · 2025-09-05 14:57
jannaucan we remove the sub-slotting from asahi-kernel and instead use "asahi-${PVR}"?#asahi-alt · 2025-09-05 14:56
jannauthis is all under the assumption that asahi-kernel is in the gentoo repo? Otherwise I don't see how conflicts arise.#asahi-alt · 2025-09-05 13:33
jannaucouldn't asahi-kernel just depend on virtual/dist-kernel:asahi (or conflict with dist-kernel:0)#asahi-alt · 2025-09-05 13:32
jannaubut that's just an issue with upgrading dist-kernel to an ebuild from the gentoo repo#asahi-alt · 2025-09-05 08:32
jannauI also don't understand the the commit message. as long as there is no asahi-kernel in gentoo we're free to use the kernel package version as slot#asahi-alt · 2025-09-05 08:29
jannauit broke with https://github.com/chadmed/asahi-overlay/commit/e1c619b6b7642753eb90833feefcd919c910b2ce as multiple subslots can not be installed in parallel#asahi-alt · 2025-09-05 08:04
jannaulooks like it is the RDEPEND "~sys-kernel/asahi-kernel-${PV}:asahi=" in the dist-kernel ebuild#asahi-alt · 2025-09-05 07:54
jannauso it seems that something broke#asahi-alt · 2025-09-05 07:54
jannauI have emerge --depclean calls with multiple asahi-kernel slots in my emerge.log#asahi-alt · 2025-09-05 07:49
jannauhence my question whether I broke the slotting or if asahi-kernel always behaved this way#asahi-alt · 2025-09-05 07:48
jannauthere is just a single installed slot after `emerge -u @world`#asahi-alt · 2025-09-05 07:16
jannaunot a practical issue since the old version left its /lib/modules/${VERSION}/ behind#asahi-alt · 2025-09-05 07:15
jannauis it expected that only one asahi-kernel slot is installed or did I break something or something else changed?#asahi-alt · 2025-09-04 18:46
jannauthat wouldn't explain why wayland is slow as well#asahi-alt · 2025-09-04 18:45
jannauI think the xorg server config snipped should be backported with a security fix release last year#asahi-alt · 2025-09-04 15:16
jannaugentoouser: output of `eglinfo | grep -e renderer -e platform:` when logged in either x11, wayland or terminal`#asahi-alt · 2025-09-04 15:11
jannauthat's unrelated to your issue#asahi-alt · 2025-09-04 14:50
jannaugentoo's mesa-25.2 mask was removed, is the x86 root fs still blocked?#asahi-alt · 2025-09-04 14:42
jannaugentoouser: is the GPU driver loaded, check with `dmesg | grep gpu`#asahi-alt · 2025-09-04 13:26
jannaugentoouser: not the emerge output but `emerge --info mesa`. a pastebin like https://paste.debian.net/#asahi-alt · 2025-09-04 12:58
jannaugentoouser: which kernel package / version and which mesa version is installed? please provide the output of `emerge --info mesa`. does `journalctl -k -g gpu` contain "kernel: [drm] Initialized asahi 0.0.0 for 406400000.gpu on minor 1" or similar#asahi-alt · 2025-09-04 12:54
jannauxorg/X11 "works" but is not recommend#asahi-alt · 2025-09-01 07:29
jannauthanks