#
…

2025-04-01

02:07tobhe has joined #ubuntu-asahi
02:14tobhe_ has quit [Ping timeout: 480 seconds]
09:59number0ne_ has joined #ubuntu-asahi
10:05number0ne_ has quit [Quit: Konversation terminated!]
15:06Paul[m] has joined #ubuntu-asahi
15:06Paul[m]The goal for all of that is to resize my Ubuntu partition to make it bigger after I resized down my macOS partition
15:07Paul[m]* macOS partition and I want to boot a liveusb in order to run gparted
15:07Paul[m]Not sure if relevant but I'm on a Mac Mini M1 and the debian live is on a USB key connected to a USB-A port of my Mac Mini
15:08tobhe[m]so you could potentially live resize it
15:08tobhe[m]there was a change in u-boot at some point
15:08tobhe[m]that changed all the boot commands
15:09Paul[m]tobhe[m]: Only if the free space is right after the Linux partition no?
15:09Paul[m]Which I guess isn't since I resized macOS to make some free space
15:09tobhe[m]oh yeah right, that is true
15:12Paul[m]tobhe[m]: How/where can I find the updated commands?
15:16tobhe[m]let me see
15:24Paul[m]After looking a bit around I couldn't figure out how to use it to boot :(
15:32tobhe[m]let me try on mine actually
15:32tobhe[m]i somehow thought that usb boot should even be the default
15:33tobhe[m]i think bootdev is the command you need actually
15:34tobhe[m]bootdev select, try to select the usb drive and then boot
15:34tobhe[m]if it doesn't show up maybe rescan with usb start or usb reset
15:34Paul[m]bootdev select runs without an output or error
15:34tobhe[m]does usb show up in bootdev list?
15:35Paul[m]Tried to run usb start and usb reset but same issue
15:35tobhe[m]it might also be a bit picky with usb drives
15:36tobhe[m]usb reset should show sth like 1 Storage Device found
15:36tobhe[m]and then bootdev list should have an usb_mass entry at the end
15:41Paul[m]Sorry for the ugly screen shot, OCR wasn't working well
15:43Paul[m]s/usb_mass/usb_mass_/, s/usb_mass/usb_mass_/
15:44tobhe[m]ok and now I think you can use the bootflow command to scan and boot it
15:44Paul[m]s/usb_mass/usb_mass_/, s/usb_mass/usb_mass_/
15:44tobhe[m]bootdev select 3
15:44tobhe[m]bootflow scan -b
15:44tobhe[m]or sth like that
15:44Paul[m]s/usb_mass/usb_mass_/, s/usb_mass/usb_mass_/
15:46tobhe[m]actually I wonder if we should tune our config. uboot supports a tui boot menu too
15:49tobhe[m]that looks wrong. I'd expect booting ... usb_mass
15:49tobhe[m]i guess that just boots regular ubuntu? ok
15:54tobhe[m]I guess try bootflow scan without -b and then try to use bootflow to select the correct entry and boot that directly
15:54tobhe[m]with bootflow boot
15:54tobhe[m]this seems all too complicated tbh
15:55tobhe[m]let me see if this works better with a newer uboot...
16:12Paul[m]Ah we don't see it in that screen shot but I ran bootdev list and then bootdev select 4 before bootflow scan, bootflow list, bootflow select 0andbootflow boot`
16:12tobhe[m]bootflow select 0
16:12tobhe[m]and then bootflow boot
16:14Paul[m]Ah yes that's what I did at the end
16:14Paul[m]That's after that point that it showed a GRUB shell, dunno which one is it (from the USB key or not). Not sure how to open a GRUB menu from there
16:25Paul[m]It just restarted so I guess something is wrong
16:28tobhe[m]still building a new u-boot
16:31Saviq[m] has joined #ubuntu-asahi
16:32tobhe[m]i guess we could make it smaller
16:32tobhe[m]probably just copied that from desktop
16:39tobhe[m]so I have a config with bootmenu now
16:39tobhe[m]let me update it...
16:40tobhe[m]I still wonder if the problem might just be that u-boot doesn't like that particular drive
16:40Paul[m]Could be...
16:41Paul[m]But then I wonder why it manages to boot GRUB after doing the manual commands?
16:42tobhe[m]oh right i missed that
16:42tobhe[m]ok and grub is misconfigured
16:42tobhe[m]I thought it was your local installation's grub
16:43Paul[m]tobhe[m]: Hmmmmm now I'm not even sure anymore
16:43Paul[m]I have no idea
16:58tobhe[m]so with this new u-boot you can just type bootmenu and select the usb option
16:58tobhe[m]uploading to ubuntu-asahi-next right now...
16:59Paul[m]Is ubuntu-asahi-next some kind of bleeding edge ppa?
17:31tobhe[m]to make sure things can easily be tested fore rolling them out for everyone
17:32tobhe[m]we usually build there and then copy to the regular ppa once we are confident nothing breaks
17:35Paul[m]How would I go to update my installed u-boot with the new version?
17:42tobhe[m]you could just download the deb via the web interface and install it via apt install or dpkg -i
17:43tobhe[m]or add the ppa raise the priority to 1001 in /etc/apt/preferences.d/ubuntu-asahi.pref and the update
17:49Saviq[m]Huh! This actually worked!
17:49Saviq[m]I have a luks-crypted Ubuntu Asahi now 🎉
17:50tobhe[m]Saviq: I wonder if we could actually just write the ISO to disk and then have it install over itself
17:51tobhe[m]I built an openbsd installer at one point that works like that
18:02Saviq[m]You probably have enough space in `/boot` to keep a network installer
18:05tobhe[m]you could also pack it all into a UKI with ramdisk + kernel and dump it on the ESP
18:17Paul[m]Do you have a recommendation for a live image I could try alternatively?
18:21Paul[m]Interestingly I also see two usb_mass_ devices now
18:22Paul[m]Oh wait nvm the second one is just an SSD I plugged in the meantime
18:28Paul[m]This appears a split second before that the GRUB shell shows up
18:29Paul[m]I think it appears for around 1/30 of a second lol
18:29Paul[m]s/30/30th/
18:31Paul[m]Ok I got a better screenshot
18:31Paul[m]I'm not sure why it tries to load kernel from hd0,msdos1...
18:39Paul[m]When you can see from the GRUB shell that then opens that that is clearly no (hd0,msdos1) but (hd3,msdos1)
18:40Paul[m]When you can see from the GRUB shell that shows up immediately afterwards that there is clearly no (hd0,msdos1) but (hd3,msdos1)
18:40Paul[m]When you can see from the GRUB shell that shows up immediately afterwards that there is clearly no (hd0,msdos1) but there is a (hd3,msdos1)
18:51checkfoc_us9 has quit []
18:54checkfoc_us9 has joined #ubuntu-asahi
19:03checkfoc_us9 has quit []
19:03checkfoc_us9 has joined #ubuntu-asahi
19:23Paul[m]But either way if I manually write `linux (hd3,msdos1)/vmlinuz` as I did before it doesn't work
20:15tobhe[m]I suppose you could try to find the disc by uuid
20:16tobhe[m]but at least this seems to be a bug in the image rather than u-boot now
20:18tobhe[m]hope it works 🙂 I could try to build a new one if it doesn't
20:18Paul[m]sudo dd if=Downloads/ubuntu-24.04-preinstalled-desktop-arm64+asahi.img of=/dev/rdisk12 bs=1m is the right way to go, right? Running this from a macOS computer
20:19tobhe[m]assuming rdisk12 is actually the usb drive that looks correct
20:24Paul[m]I ran `bootmenu` from U-Boot and chose the USB device. It then showed `Booting: usb 0` and then promisingly showed some Ubuntu splash/loading screen with animation that looked different from the one I'm used to with Ubuntu server. After a while it just rebooted unfortunately
20:24tobhe[m]that would mean it got a little further and actually booted the kernel
20:24tobhe[m]or at least started
20:25tobhe[m]let me try to fix the debian one before I fix that though
20:25tobhe[m]that seems easier
20:31Paul[m]Maybe it's just a faulty USB stick?
20:31Paul[m](For the live Ubuntu thingie)
20:31Paul[m]I looked around but the biggest USB key I could find is 8 GB, which I guess won't be enough (at least for the Ubuntu live image)
20:31tobhe[m]so I think you could just run lsblk --fs to find the fs-uuid of the file system on your usb drive
20:32tobhe[m]where UUID is whatever you found
20:32tobhe[m]* where $UUID is
20:34tobhe[m]on macos I think diskutil can do that too
20:39tobhe[m]yes that worked for me
20:40tobhe[m]fat UUID has the format XXXX-XXXX
20:41Paul[m]<tobhe[m]> "and then:..." <- Replace `efi/debian/grub.cfg` on my Debian USB key with this right?
20:43Paul[m]Weird error: no such device: root
20:43Paul[m]After Loading Kernel...
20:43Paul[m]:facepalm:
20:43tobhe[m]that sounds like wrong uuid
20:43Paul[m]Forgot to replace the UUID
20:50Paul[m]Man I got that XHCI timeout on event type 0... error again
20:51Paul[m]It randomly happens after some time while in GRUB/U-Boot
20:51Paul[m]Was happening with the other USB key too
20:51Paul[m]Will try to force reboot and try my luck again
20:52tobhe[m]that is definitely a usb problem
20:57Paul[m]Could be a bug in whatever handles USB?
20:59Paul[m]Is it still necessary to run update-m1n1 at all or is this already done in the triggers of the U-Boot DEB you sent me?
21:06tobhe[m]it should be done automatically on installation
21:28Paul[m]My 3rd USB key does the same thing
21:37Paul[m]Now I have some abort_td: Expected a TRB_TRANSFER TRB first as well (whichever comes first)
21:51tobhe[m]that doesn't sound right
21:51tobhe[m]I had to try 2. One didn't show up at all
21:52tobhe[m]adding or removing bridges might help
21:54tobhe[m]I guess at least we know u-boot works as well as the previous version, so I'll publish that
22:03Paul[m]Ah interesting, mine all show up reliably
…