tobhe changed the topic of #ubuntu-asahi to: Ubuntu-Asahi development | Github: https://github.com/UbuntuAsahi | Logs: https://oftc.irclog.whitequark.org/ubuntu-asahi
marcan has quit [Quit: Now where's my screwdriver...]
marcan has joined #ubuntu-asahi
sckova has joined #ubuntu-asahi
sckova has quit [Quit: sckova]
sckova has joined #ubuntu-asahi
sckova has quit [Ping timeout: 480 seconds]
autumn has joined #ubuntu-asahi
<autumn> Hi all. I'm having problems upgrading from 23.10 to 24.04. I thought it would be possible because of https://github.com/UbuntuAsahi/ubuntu-asahi/issues/112.
<autumn> I updated from macOS 12.x to 14.5 yesterday to start the asahi installation process on my M1 Max Mac Studio. I hadn't seen the warnings about m1n1, but it seems I started the process after the m1n1 patches were released as the installer supplied m1n1 v1.4.14.
<autumn> I am able to install and use Ubuntu 23.10, but the upgrade to 24.04 always causes the system to kernel panic after GRUB boots the upgraded system
<autumn> I have wiped away my asahi container + partitions and retried about 3 times now, always with the same results.
<autumn> Here's a screenshot of the kernel panic: https://i.postimg.cc/Bn237MHW/panic.png
<tobhe[m]> interesting, thanks for letting us know. That is something I haven't seen before
<tobhe[m]> do you think you could open a bug on github so we can track this?
<autumn> yeah, absolutely. i'll be able to submit it today. Is there any additional information you'd like me to include in the bug report?
<tobhe[m]> I think you actually included the most important things already. m1n1 version could be relevant, kernel version is shown in the screenshot
<autumn> oh wow it actually booted. I had left it to loop for over an hour and at some point in the last ~20 minutes it actually made it through to the greeter. I've verified from the now-booted system that (m1n1/noble,now 1.4.14-1ubuntu0.1~asahi1 arm64)
<autumn> would `sudo journalctl --no-hostname -b 0` be sufficient for logs or would you like me to run anything else?
<autumn> output of journacltl --no-hostname -b 0: https://pastebin.com/LdXXCKb0
<tobhe[m]> I think that is sufficient for now, maybe john-cabaj has an idea on what else would help
<autumn> here's the logs for the previous, failed boot as well, in two parts: https://pastebin.com/Ywxh6hb9 https://pastebin.com/wiPet75D
<john-cabaj[m]> Will try to look later. Traveling atm
<autumn> Okay, I've opened an issue: https://github.com/UbuntuAsahi/ubuntu-asahi/issues/119 Thanks for the assistance! I'm happy to provide any other info from the now-running system. Hope you all have a great day!
kaazoo has joined #ubuntu-asahi
<autumn> I ran `sudo journalctl --no-hostname -b -1` to obtain the "previous failed boot logs" but it looks like I misunderstood which boot was captured by that command, and that it was from a boot that happened under 23.10.
<kaazoo> Hi, I just updated to kernel 6.8.0-1005-apple-arm and it's working fine so far.
<kaazoo> However, https://github.com/AsahiLinux/linux/releases/tag/asahi-6.8.9-6 has been released to address that dm-crypt data corruption bug.
autumn_ has joined #ubuntu-asahi
autumn has quit [Quit: Page closed]
<autumn_> :q
autumn_ has quit []
kaazoo has quit [Remote host closed the connection]
<john-cabaj[m]> <kaazoo> "However, https://github.com/..."; <- I can look into the bug reports and see what the impact is. There’s been 1-2 release tags a week lately, and it takes 2 days for our builder to publish. I’ve been trying to update the kernels on Fridays.