14:48 <r0ni> ok after i update the kernel pkg locally, do i run update-grub and then update-m1n1 or the other way around?

14:56 <_jannau_> order doesn't matter, update-grub and update-m1n1 update independent parts at runtime

14:57 <r0ni> ok, i was thinking that. thx Outside of the kernel and headers and those scripts, is there anything else need to be ran to successfully update the kernel and have the system boot?

14:58 <r0ni> i've previously updated kernel pkgs and grub but get non-boot after... hadn't thought about m1n1

15:03 <jannau> m1ni itself needs to be updated soon for display and gpu driver to work

15:04 <r0ni> ive already made a pkg for m1n1 so i can update it whenever releases happen, i'm just trying to work on getting the system updatable overall

15:04 <j`ey> r0ni: is your stuff public?

15:06 <r0ni> j`ey, not yet. I plan on putting a git up later today, it's not anything special, just a few slackbuilds for slackware asahi packages

15:06 <j`ey> r0ni: still will be nice to look at, and show my slackusingcoworker

15:07 <r0ni> i'll post a link to it in here

15:09 <r0ni> this is why i'm trying to work out the kernel updating

15:16 <j`ey> r0ni: so do you currently have a broken setup?

15:45 <r0ni> nah, i just boot into macos when i break it and copy a backup of the /boot/grub folder and it all good

15:46 <r0ni> also sry, was on a important call... the lady wasn't lying, it was about 30 mins lol

15:46 <j`ey> well broken in that linux doesnt boot I mean

15:46 <r0ni> oh no, i'm booted to it right now

15:47 <r0ni> Client: HexChat 2.16.1 • OS: Slackware 15.0+ • Memory: 15.0 GiB Total (13.4 GiB Free) • Storage: 24.8 GB / 40.8 GB (16.1 GB Free) • Uptime: 1h 16m 52s

15:47 <j`ey> well its broken in that it was broken before you fixed it with the backup :P

15:48 <r0ni> well whats broken is updating the kernel or at least how i've tried to update it

15:48 <j`ey> can you try the kernel update procedure, but with the same kernel?

15:49 <j`ey> then you can tell if it's just a broken kernel (which seems likely..)

15:50 <r0ni> i'm just using the arch kernels as of now. I've built the kernel but I haven't tried installing mine yet. I want to ensure I have a working upgrade path first before I tamper with my builds

15:50 <r0ni> just re-packaged them as slackware pkgs

15:50 <j`ey> aha

15:50 <r0ni> so they *should* work

15:51 <r0ni> but i seem to be missing a key element of updating the kernel

15:58 <r0ni> on slackware, we don't use scripts to do things during a kernel update... you update your kernel pkg, run grub/lilo/elilo, make an initrd, etc. Most other distros hide all that from the user, but on slackware, you're on your own. So I want to make sure I have a reproducible path of updating the kernel. requiring the user to run update-grub, update-m1n1 is fine, as long as I package and maintain them as well

16:00 <j`ey> r0ni: so you get to grub etc right, it's just that afterwards, the kernel gives a black screen?

16:02 <r0ni> if i update the kernel and then run grub-mkconfig my grub screen has all jumbled graphics upon reboot and then starts to load, and fails... I'll have to take a pic, I'd assume a module failed but since i'm using the arch pkgs, everything needed should be there

16:06 <r0ni> i've re-built grub to include all the patches in the arch build, but my /etc/default/grub is slackware's default... not sure if it's a custom file for asahi

16:07 <r0ni> the only logical solution is I need more M1 machines to compare lol

16:16 <r0ni> ok i'm going to run both these update-* scripts after cleaning up my mess and reboot and see what happens

17:15 <r0ni> i broke it pretty good now lol

17:29 <r0ni> so it seems the /boot/efi/EFI/BOOT/BOOTAA64.EFI my system created don't work. I'll need to look into that

17:32 <j`ey> you should be able to replace that with the older/backup right? thats just the grub build

17:32 <r0ni> so it seems the /boot/efi/m1n1/boot.bin is also much larger than the OEM asahi file

17:33 <j`ey> well thats weird, isnt it built from the same sources / same script?

17:33 <r0ni> j`ey ya i'm fixing the files right now, but running both those update- scripts broke everything including grub

17:34 <r0ni> i realize also my boot issue is likely the initramfs

17:37 <j`ey> you'd at least get some kernel output I think

17:39 <r0ni> before i broke grub as well, it was complaining about modules which are there... but i realized the initramfs is out of date and it must not be mounting the nvme even during boot of new kernel

17:40 <r0ni> i think m1n1 size difference is cuz one is 1.1.5 other is 1.1.6

17:42 <r0ni> these issues are why no one but me has slackware on m1 lol

17:42 <j`ey> I have a m1n1.bin that's only 800K, built from main branch

17:42 <j`ey> how big are yours?

17:42 <r0ni> i'm not the guy for booting aarch64 machines... i just make pkgs lol

17:44 <r0ni> it's like 1.8mb

17:46 <r0ni> i've got to run in a min but i'm going to try booting this again before i go... it should work now

17:46 <mps> r0ni: my m1n1.bin is 816K