#asahi · 2023-11-02 08:45
amwI have uploaded : grep -C3 --color -E 'framebuffer|Linux version|apple-dcp' /var/log/kern.log - as https://paste.debian.net/1296933/#asahi · 2023-11-02 08:42
jannegamw: do have you apple-dcp messages in the failing kernel?#asahi · 2023-11-02 08:41
jannegthat's asahi-6.4-3 and rules the issue out I had in mind. the kernel tree has tags of the form asahi-$KERNEL_VERSION-$N#asahi · 2023-11-02 08:39
amwjanneg: Not sure which particular number you mean - my kernel is vmlinuz-6.4.0-asahi-00514-gbb1ea272fd94#asahi · 2023-11-02 08:37
amwHmm - I see on the failing kernel: simple-framebuffer bd58dc000.framebuffer: [drm] *ERROR* could not acquire memory range [??? 0xffff07880629d480-0x2a5000001a7 flags 0x0]: -16#asahi · 2023-11-02 08:30
jannegdo you have the asahi tag of the working driver?#asahi · 2023-11-02 08:29
amwPaulFertser: I need to boot up in my not working kernel - do it later#asahi · 2023-11-02 08:28
amwjanneg: In my working kernel only /dev/dri/card0 and by-path#asahi · 2023-11-02 08:26
jannegamw: what files are in /dev/dri/?#asahi · 2023-11-02 08:26
PaulFertseramw: it should be possible to start X on fbdev without any acceleration, is that the same error when you run Xorg as root?#asahi · 2023-11-02 08:23
amwPaulFertser: Thanks - I guess the card0 device is something else - not sure what but it gives me a way in#asahi · 2023-11-02 08:22
amwI'm not bothered with HW acceleration - so perhaps that is why#asahi · 2023-11-02 08:20
PaulFertserWas it really your aim to just use fbdev for everything, without any hw acceleration at all, fully software, when there is a stable kernel driver and Mesa support?#asahi · 2023-11-02 08:20
amwHmm only see CONFIG_DRM_ASAHI=y in my 6.3 kernel???#asahi · 2023-11-02 08:19
PaulFertseramw: backtrace is not show because you do not have the package with debug symbols installed I guess.#asahi · 2023-11-02 08:17
PaulFertseramw: https://github.com/AsahiLinux/linux/blob/asahi/drivers/gpu/drm/asahi/Kconfig#L16#asahi · 2023-11-02 08:16
amwIt's a good idea - I made a diff of the configs here : https://paste.debian.net/1296932/#asahi · 2023-11-02 08:13
amwThe following are present in both kernel configs : CONFIG_DRM_SIMPLEDRM CONFIG_DRM_PANFROST CONFIG_DRM_APPLE#asahi · 2023-11-02 08:10
amwgrep ASAHI shows nothing on both working and non-working kernels#asahi · 2023-11-02 08:08
PaulFertseramw: CONFIG_DRM_ASAHI probably#asahi · 2023-11-02 08:02
amwPaulFertser: Do you know the kernel CONFIG I should be looking for?#asahi · 2023-11-02 07:54
PaulFertseramw: "open /dev/dri/card0: No such file or directory" it's like you built a kernel without the gpu driver?#asahi · 2023-11-02 07:50
amwMy Aug 3rd kernel - 6.4.0-asahi-00514 ok - but the 6.5-asahi ones are not#asahi · 2023-11-02 07:49
amwX11 crashing with recent kernels - SIGABRT no stack trace - https://paste.debian.net/1296930/ - any suggestions how to debug this further?#asahi · 2023-11-02 02:56
jmr2Anyway, I cleaned it up, deleted the last old m1n1 stub, and it's back, with a newer stage1 m1n1 and based on a 13.5. stub. I'll check after the next MacOS update if it helped.#asahi · 2023-11-02 02:56
jmr2Even considering that deleting partitions changed the GPT indexes, I don't see how that could work.#asahi · 2023-11-02 02:56
jmr2So it was really booting using m1n1 from the new EFI partition, but grub data from the old one.#asahi · 2023-11-02 02:06
balrogis it possible to switch between ProMotion and 60Hz from within Linux?#asahi · 2023-11-02 00:36
jmr2OK, there's really some mixup, because there's no EFI folder on the new EFI partition.#asahi · 2023-11-02 00:29
jmr2Here's the current partition list, to make it more visual https://pastebin.com/qaAN8YEc Thanks!#asahi · 2023-11-02 00:29
jmr2Is it really that simple, or do I have some mixups in my stub + ESP associations? Can I safely delete the old m1n1 stub & EFI?#asahi · 2023-11-02 00:29
jmr2Except that I don't have to do it - regardless if I use the old or the new bootpicker entry, I get the grub menu, with my usual entries and configs, and everything boots as it used to.#asahi · 2023-11-02 00:29
jmr2I ran the current ALARM installer, non-expert, in m1n1/UBoot/ESP mode. The plan was to keep the same rootfs, move the content of my (custom) ESP to the new one, and then delete the last old m1n1 install.#asahi · 2023-11-02 00:29
jmr2I used to have three installation of m1n1 - with 12.01, 12.1 and 12.3, with only the 3rd one paired with an ESP. Deleted the two oldest.#asahi · 2023-11-02 00:29
jmr2Hey folks... a little help please. Following the discovery that my SystemRecovery is still 12.2.1, I decided to do come cleanup.#asahi · 2023-11-01 23:28
eldondevAlso, this machine doesn't have direct access to the internet, so I'm not sure about the best procedure for an offline update of recent macOS versions.#asahi · 2023-11-01 23:27
eldondevjanneg yeah, that's fair, but I've updated linux a bazillion times, macOS only a few times.#asahi · 2023-11-01 22:07
j`eytmbrwn: I think markan has said that he plans on updating the packages.. but other than that, not much support#asahi · 2023-11-01 21:40
tmbrwnLike, will I have to switch to Fedora Asahi Remix for support?#asahi · 2023-11-01 21:39
tmbrwnRandom Q. Will the Asahi Linux team continue to support the packages necessary to run ALARM on Apple Silicon? #asahi · 2023-11-01 21:34
jannegsounds much more complicated than updating macOS#asahi · 2023-11-01 20:47
eldondev_janneg: Yeah, I think I could find a way to manage that.#asahi · 2023-11-01 18:28
MichaelLongwhat, please have a look here: https://github.com/AsahiLinux/docs/wiki/macOS-Sonoma-Boot-Failures#asahi · 2023-11-01 18:16
whatOh it only affects the MacBook pros?#asahi · 2023-11-01 18:15
MichaelLongI also was, until a week ago....#asahi · 2023-11-01 18:15
whatBut the air shouldn't be affected right #asahi · 2023-11-01 18:14
whatI'm pretty sure I'm on a older version of ventura#asahi · 2023-11-01 18:11
leio13.6*#asahi · 2023-11-01 18:11
leiowhat: the Ventura 14.6 update is affected as well, as it updates to Sonoma firmware