#asahi-alt · 2023-04-07 12:17
chadmedhmm. if the kernel was halted the WDT _should_ reboot the machine after a couple of minutes#asahi-alt · 2023-04-07 12:13
chadmedif it doesnt then the kernel isnt actually halted and the issue is simpledrm#asahi-alt · 2023-04-07 12:13
chadmedid be curious to see if the WDT kills the machine after 2 minutes#asahi-alt · 2023-04-07 12:12
chadmedfor context zerdox's issue is the kernel halting with no debug info on first boot#asahi-alt · 2023-04-07 12:10
chadmedyeah i had to do some surgery to /boot on my x86 mac in macos today, it was an ordeal :P#asahi-alt · 2023-04-07 12:07
chadmedi run ESP as boot on my own machine though and will switch it over to do that once/if asahi does the same#asahi-alt · 2023-04-07 12:07
chadmedseparate by default because people are used to it, hence mounting the ESP at /boot/efi#asahi-alt · 2023-04-07 12:06
chadmedand that should at least give us an idea of whats causing the problem #asahi-alt · 2023-04-07 12:06
chadmedif you have access to /boot somehow (virtualbox can be passed through a pointer to raw block devices on macos hint hint) you can add earlycon and debug to your kernel command line #asahi-alt · 2023-04-07 12:05
chadmedits hard to really understand WHAT is causing the error because you have no kernel debug output#asahi-alt · 2023-04-07 12:04
chadmedonly different thing i do is instead of rm -rf / on the asahi partition, i clobber it and make a new one#asahi-alt · 2023-04-07 12:04
chadmedno that should all be fine, theres nothing specific you need to do in that regard#asahi-alt · 2023-04-07 11:54
chadmedvery odd indeed...#asahi-alt · 2023-04-07 11:54
chadmedand the only fix i encountered was kernel config related#asahi-alt · 2023-04-07 11:54
chadmedbecause i do remember running into similar issues when first developing all that stuff but ive done multiple installs since and havent hit it#asahi-alt · 2023-04-07 11:53
chadmedinteresting#asahi-alt · 2023-04-07 11:53
chadmedhm okay#asahi-alt · 2023-04-06 22:14
chadmedtheres only a couple of ways you can hit this particular failure mode#asahi-alt · 2023-04-06 22:10
chadmedi know this because just last night i detonated my gentoo root fs and re-ran the entire process from scratch and it worked without a hitch#asahi-alt · 2023-04-06 22:10
chadmedwhich means, again, youve messed up keywording (mismatched kernel version to the one that was running in asahi) or youve clobbered something in the kernel config file #asahi-alt · 2023-04-06 22:09
chadmedyou should not have gotten any additional kconfig options to say y/n to #asahi-alt · 2023-04-06 05:17
chadmedbut yeah things are moving so fast that its basically impossible to keep on top of them #asahi-alt · 2023-04-06 05:17
chadmedi have scripts to automate most of it... except the dangerous part ;) #asahi-alt · 2023-04-06 04:17
chadmeddont do installs at 11pm after a day at work folks#asahi-alt · 2023-04-06 04:15
chadmedwhich i might need to do again because i accidentally turned the system wide recovery partition into a swap :P #asahi-alt · 2023-04-06 04:14
chadmedive had my own share of graphics issues over the last week or so, i gave up trying to debug and just detonated my root fs#asahi-alt · 2023-04-06 04:14
chadmedasahi mesa, that is#asahi-alt · 2023-04-06 04:14
chadmedmashrafi: there might have been a regression on sway. mesa has no package with stable keywords so youll have to build and install from one of the tagged commits on FDO#asahi-alt · 2023-04-04 10:20
chadmedwhatever ill just nuke it and start from scratch again over the long weekend, gives me a chance to clean up any bugs in the installer scripts#asahi-alt · 2023-04-04 10:20
chadmedso idk#asahi-alt · 2023-04-04 10:20
chadmedit might be portage not liking that i installed mesa from git at one point to debug? but i cleaned it out...#asahi-alt · 2023-04-04 10:19
chadmedjannau: nah none#asahi-alt · 2023-04-04 09:07
chadmedi completely nuked my kde config, tried the previous tagged mesa and tried asahi-6.2-11#asahi-alt · 2023-04-04 09:07
chadmedlucky these machines are fast and bootstrapping a rootfs only takes a couple of hours#asahi-alt · 2023-04-04 09:06
chadmedwell it wasnt plasma, its not mesa and its not the kernel#asahi-alt · 2023-04-04 08:24
chadmedgiven that firefox, glxgears, libreoffice and other stuff still works im pretty confident its a plasma issue#asahi-alt · 2023-04-04 08:24
chadmedim downgrading to stable (5.26.5) now to see if that fixes it#asahi-alt · 2023-04-04 08:23
chadmedjannau: 5.27.3, and yeah i disabled night colour when we were debugging the issue with the screen not coming back on#asahi-alt · 2023-04-04 07:57
chadmedthe error was related to gamma blobs so i think theyve broken the colour correction stuff #asahi-alt · 2023-04-04 07:57
chadmedjannau: ack. latest plasma seems borked. ill try downgrade to stable keyworded plasma and see if that helps#asahi-alt · 2023-04-04 07:52
chadmedso it probably is :P#asahi-alt · 2023-04-04 07:52
chadmednot sure, but no one else has reported anything strange#asahi-alt · 2023-04-04 07:52
chadmeduntil the latest kde update but that might be something weird in my environment #asahi-alt · 2023-04-04 07:52
chadmedive been running it for a while now with no dramas #asahi-alt · 2023-04-04 07:52
chadmedmashrafi: ~arm64 is the latest and should be fine #asahi-alt · 2023-04-02 00:56
chadmedkwin still "runs" but no plasma workspace, no screen locker, no kde apps#asahi-alt · 2023-04-02 00:55
chadmedmost applications still work fine though so im going out on a limb and assuming its a plasma issue #asahi-alt · 2023-04-02 00:55
chadmedbroken with latest kernel with mesa at HEAD and the last tagged release#asahi-alt · 2023-04-02 00:54
chadmedjust want to see if its something i screwed up or if its reproducible#asahi-alt · 2023-04-02 00:54
chadmedsome error about gamma blobs and an invalid argument to libGLX