#
…

2026-10-27

00:58f_ has quit [Remote host closed the connection]
01:32fatcullen has joined #asahi-alt
03:26fatcullen has quit [Quit: This computer has gone to sleep]
03:32bgb has quit [Remote host closed the connection]
03:38bgb has joined #asahi-alt
03:40fatcullen has joined #asahi-alt
04:34fatcullen has quit [Quit: This computer has gone to sleep]
04:37bgb has quit [Remote host closed the connection]
04:42bgb has joined #asahi-alt
04:48bgb has quit [Remote host closed the connection]
05:04fatcullen has joined #asahi-alt
05:08ohxorud_ has joined #asahi-alt
05:11ohxorud has quit [Ping timeout: 480 seconds]
05:12ohxorud_ is now known as ohxorud
05:24fatcullen has quit [Quit: This computer has gone to sleep]
05:25fatcullen has joined #asahi-alt
05:26fatcullen has quit []
05:43bgb has joined #asahi-alt
06:27bgb has quit [Remote host closed the connection]
06:33bgb has joined #asahi-alt
07:15f_ has joined #asahi-alt
07:20mattia013 has quit [Quit: mattia013]
07:20mattia013 has joined #asahi-alt
07:23mpsjannau: sorry for false alarm. actually reboot is triggered by elogin-daemon which should be started on my machine but something start it and i didn't noticed this
07:24mpskilled it and suspend/resume works fine
07:24bgb has quit [Remote host closed the connection]
07:30bgb has joined #asahi-alt
07:31x1z53[m]About distrubition building
07:31x1z53[m]Is boot.img and root.img required? Or can we just leave root.img with two partitions in it?
07:32chadmedwhat distro are you trying to put together?
07:34chadmedyou declare in installer_data which partitions each install option will want to write to disk and what the image for them is. you can declare only one partition but dding an image with two partitions into that space probably wont work
07:34x1z53[m]chadmed: I'm trying to write installer_data.json and artifacts for it to install ALT Linux with asahi-installer script
07:35mpsi don't have boot.img in installer for alpine linux, root.img
07:36mpskernel and initramfs are in ESP
07:38x1z53[m]It's just that so far we have a problem — our images can be assembled either in .tar (without the generated GRUB, only extlinux), or .img with two partitions (with GRUB, which relies on the UUIDs of the partitions).
07:38x1z53[m]That's why I'm trying to come up with a plan for what to do — IMG from TAR or convert an IMG with two sections into an IMG with one section.
07:38x1z53[m]Then we won't have multi-kernel load
07:39x1z53[m]mps: About this
07:40x1z53[m]ALT Linux allows you to have multiple kernels in the system and switch between them
07:40x1z53[m]When installing a new kernel, extlinux/GRUB is updated and new items are added.
07:40x1z53[m]And if you put the kernel and initramfs separately, then it won't work (if I understand correctly, this is just a guess)
07:41chadmedcan you assemble a bootable image with custom kernel
07:41chadmedmight be easier to just direct users to flash an asahi-flavoured iso on to a usb and boot from that
07:42mpsx1z53[m]: I use limine boot loader with only one kernel but it is easy to add more if it is wanted/needed
07:42x1z53[m]chadmed: We already have USB-load variant, but chaos princess says, that it's not recommended way (if I remember correctly)
07:45x1z53[m]Can we just chainload extlinux to other partition somehow maybe?
07:48mpsboot with extlinux worked at beginning fine but nowadays most uses grub
07:48x1z53[m]Or maybe I don't understand how U-Boot detects boot partitions and we can just directly load from system partition?
07:48x1z53[m]I also have seen that USB drive is marked as `extlinux`, but ESP partition as `efi`. Can we maybe say to U-Boot to load directly from system if mark it as `extlinux`?
07:49x1z53[m]x1z53[m]: (I do not know how it works, so I do not know if this is even possible)
07:50mpsiirc is enough to create 'extlinux/extlinux.conf' in boot partition
07:59JamesCalligeros[m]It’s not that usb boot is “not recommended” (its personal taste really) you just need to make sure your users are guided through partitioning so they dont break any apfs containers
08:14x1z53[m]<JamesCalligeros[m]> "It’s not that usb boot is “not..." <- But it's installer's script work, no?
08:14x1z53[m]Just choose UEFI-only installation, write system on USB drive, connect it, reboot and it will boot
08:20bit_runner80 has joined #asahi-alt
08:29JamesCalligeros[m]Yes, but the user then has to partition/install the OS
08:30JamesCalligeros[m]So it is incumbent on tje distro’s asahi guide to warn users very explicitly about the dangers of partitioning
08:30JamesCalligeros[m]See the gentoo asahi guide for an example of this flow
08:36bit_runner80 has quit [Remote host closed the connection]
09:01x1z53[m]<JamesCalligeros[m]> "Yes, but the user then has to..." <- In our case it work delegated to `alt-rootfs-installer` script, that do rootfs installation things
09:01chadmedis it smart enough to avoid destroying apfs containers etc on the disk?
09:01bgb has quit [Remote host closed the connection]
09:02x1z53[m]chadmed: It's for installing to USB drive
09:02x1z53[m]But... Hm
09:02x1z53[m]Maybe it can install to one partition, idk
09:05x1z53[m]I'm too afraid to try it on my machine 🙂
09:05x1z53[m]I don't no how to recover it in case of troubles
09:07chadmedthen your flow should look like this:
09:07bgb has joined #asahi-alt
09:07chadmed1. user flashes asahi-flavoured bootable alt linux iso to a usb stick
09:08chadmed2. user runs the upstream asahi installer and installs the uefi-only boot option, reserving as much space as they want for linux when prompted
09:08chadmed3. user completes the install proces, and then plugs in the bootable usb stick and boots from it using u-boot
09:08chadmed4. user manually installs alt-linux via whatever mechanism, preferably being guided through manual partitioning to ensure that no automated tools try to destroy apfs containers
10:10mattia013_ has joined #asahi-alt
10:13waltmck has quit [Remote host closed the connection]
10:14mattia013 has quit [Ping timeout: 480 seconds]
10:14mattia013_ is now known as mattia013
10:25waltmck has joined #asahi-alt
10:48mattia013 has quit [Ping timeout: 480 seconds]
11:46fatcullen has joined #asahi-alt
12:03fatcullen has quit [Quit: This computer has gone to sleep]
12:27fatcullen has joined #asahi-alt
12:57fatcullen has quit [Quit: This computer has gone to sleep]
13:35bgb has quit [Remote host closed the connection]
13:41bgb has joined #asahi-alt
14:25picnoir has joined #asahi-alt
15:39bgb has quit [Remote host closed the connection]
15:44bgb has joined #asahi-alt
16:02scoopy[m]jw do you (that is, other gentoo users) use the asahi efi partition as your os efi partition
16:03chaos_princessdo you mean efi as /boot? yes, it works pretty well.
16:04scoopy[m]i recall when i first tried to install gentoo i didnt go that route, and tried making a distinct efi partition, and for some reason i couldnt get that partition to be writable no matter what
16:05scoopy[m]perhaps i did something wrong (very likely), but i figured out to use the asahi efi because the install script linked on the wiki page does that, in fact, it errors if you dont
16:06scoopy[m]it was a huge headache, and i only resolved it by looking at bash scripts, so im just wondering why its not mentioned on the wiki page itself to use the asahi efi as /boot ?
16:37denice68 has joined #asahi-alt
16:38denice68 has quit [Read error: Connection reset by peer]
16:53ipatch has quit [Quit: WeeChat 4.10.1]
16:54denice68 has joined #asahi-alt
16:54denice68 has quit [Read error: Connection reset by peer]
16:54ipatch has joined #asahi-alt
17:08mattia013 has joined #asahi-alt
18:06bgb has quit [Remote host closed the connection]
18:11bgb has joined #asahi-alt
18:38x1z53[m]We'll simplify situation a bit
18:38x1z53[m]And because of that, U-Boot will boot system partition directly with extlinux
18:39x1z53[m]And now system can be installed with asahi-installer correctly (after some more changes in boot.bin)
18:39chaos_princesswhat would happen if i install two copies
18:41x1z53[m]Guess first will boot
18:41x1z53[m]But with `bootflow` in U-Boot you can choose the other
18:41x1z53[m]Or maybe I misunderstand your question
18:42chaos_princessfedora is capable of booting the correct install in that case
18:56VasiliyDoylov[m] has joined #asahi-alt
19:57bgb has quit [Remote host closed the connection]
20:00kraem is now known as Guest4083
20:00kraem has joined #asahi-alt
20:02Guest4083 has quit [Ping timeout: 480 seconds]
20:03bgb has joined #asahi-alt
21:02fatcullen has joined #asahi-alt
21:17mattia013 has quit [Quit: mattia013]
21:26JamesCalligeros[m]scoopy: the asahi installer burns the uuid of the esp it creates into m1n1. It is not supported (as in, we wont help you) to create additional ESPs
21:27JamesCalligeros[m]Use the ESP created by the installer, and as already mentioned optionally also use it as /boot which is totally valid and works well
21:29fatcullen has quit [Quit: This computer has gone to sleep]
21:33x1z53[m]BTW, how to inject own logo in m1n1/U-Boot?
21:34JamesCalligeros[m]The logo is part of the m1n1 binary
21:34JamesCalligeros[m]You can build your own m1n1 and provide a logo for it
21:36x1z53[m]Okay, found it. Thanks for the tip
22:28tobhe has joined #asahi-alt
22:48fatcullen has joined #asahi-alt
23:35fatcullen has quit [Quit: This computer has gone to sleep]
…