#
…

2024-01-03

00:05zumi_ has joined #asahi-alt
00:05zumi has quit [Remote host closed the connection]
00:10zumi_ is now known as zumi
00:22demon_in_a_jar has quit [Remote host closed the connection]
00:54lactose has joined #asahi-alt
01:52possiblemeatball has joined #asahi-alt
02:05kidplayer666 has quit [Quit: Connection closed for inactivity]
02:15lactoseI want to try to craft a Slackware rootfs image to use with the official installer, but I'm confused as to how to do that.
02:17lactoseI'm looking at the Debian repo and I'm not sure how m1n1 and u-boot fit into the picture, also the official installer has no documentation that I could find
02:29pthariensflame has joined #asahi-alt
02:45john-cabaj has quit [Ping timeout: 480 seconds]
02:59pthariensflame has quit [Quit: Textual IRC Client: www.textualapp.com]
03:01KxCORP has quit [Quit: Bye!]
03:02KxCORP has joined #asahi-alt
03:11jeisom has quit [Ping timeout: 480 seconds]
04:25wookey has joined #asahi-alt
05:01possiblemeatball has quit [Quit: Quit]
05:46john-cabaj has joined #asahi-alt
05:58lactose has quit [Quit: Leaving]
06:04zumi_ has joined #asahi-alt
06:04zumi has quit [Remote host closed the connection]
06:09zumi_ is now known as zumi
06:31kidplayer666 has joined #asahi-alt
07:16tobhe_ has joined #asahi-alt
07:21tobhe has quit [Ping timeout: 480 seconds]
07:21tobhe has joined #asahi-alt
07:24tobhe_ has quit [Ping timeout: 480 seconds]
07:42cy8aerm1n1 and u-boot together with the dps from the kernel create a file /boot/efi/m1n1/boot.bin which is the second stage of m1n1. In the @Glanzmann-Repo m1n1 has not only the m1n1 binary but also the combined boot.bin which is copied to /boot/efi/m1n1 at install time (together with creating a backup). So there is a dependency of m1n1 with the kernel because different kernels have different dps
07:45cy8aerThe main problem is that it is difficult to find the dps at install time from the kernel packages so it is precompiled at packaging time. Other dists do it at install time. As long as the kernel dpc is not stable this must be done.
07:48cy8aerAnd the pre compilation of boot.bin is only possible because the kernel source is lying around in the build dir at the same time with the m1n1_uboot_kernel.sh script
08:03dylanchapell has quit [Read error: Connection reset by peer]
08:12cy8aerhas not -> there is
08:19dylanchapell has joined #asahi-alt
08:20john-cabaj has quit [Remote host closed the connection]
08:20john-cabaj has joined #asahi-alt
08:29cy8aerdp -> dtb (sorry)
08:31cy8aeraka device tree binary
08:42eiln has quit [Quit: WeeChat 4.1.2]
09:15billak has joined #asahi-alt
10:25billak has quit [Ping timeout: 480 seconds]
10:27chadmed_ has joined #asahi-alt
10:35chadmed_hm cargo-ebuild doesnt seem to tolerate workspaces properlyt
10:39leiochadmed_: pycargoebuild is the current thing that's mostly used, not cargo-ebuild.
10:40chadmed_leio: that doesnt either :p
10:40chadmed_but at least it tells you it expects each member of the workspace to be its own package
10:52sam_are you sure it doesn't handle it properly? (pycargoebuild)
10:52sam_anyway file a bug if it's doing something wrong or speak to mgorny
10:52billak has joined #asahi-alt
10:54chadmed_i think its expected behaviour because if you run it in a workspace it explicitly says to only do it at the path of an actual binary package
10:54chadmed_so not necessarily a bug
11:01jeisom has joined #asahi-alt
11:01sam_i'm not really sure what else you want it to do
11:02chadmed_a couple of things ive tried to package up in the last week or so have depended on cargo's workspace feature, where multiple interdependent modules get developed, built and installed from a single root
11:02jeisom has quit []
11:02chadmed_libkrun is egregious because it makes use of this _and_ vendors multiple other crates that it really really shouldnt
11:03chadmed_and because cargo-ebuild and pycargoebuild cant tolerate workspaces, i had to do some weird stuff to get cargo.eclass to behave nicely with those vendored crates and the different components that the actual package expects to build
11:04chadmed_whereas cargo proper, you just run cargo build/install from the root and it iterates over the workspace members and it resolves all the dependencies and interdependencies, builds them in the correct order, then installs them
11:06sam_but isn't it quite unusual for multiple binaries to be needed?
11:06sam_this doesn't sound related to that part
11:06sam_it sounds more related to stupid shenanigans like git crates
11:07sam_but maybe i'm missing something, i'm no rust expert
11:07sam_but you should file a bug if you think it should handle it better and it doesn't
11:07sam_not clear to me what else it should do differently (every time I've hit a workspace, just picking the things I actually want worked fine for me) but if you have an idea in mind, go nuts
11:38jeisom has joined #asahi-alt
11:59billak has quit [Ping timeout: 480 seconds]
12:05zumi_ has joined #asahi-alt
12:06zumi has quit [Remote host closed the connection]
12:10zumi_ is now known as zumi
12:24billak has joined #asahi-alt
12:31kidplayer666 has quit [Quit: Connection closed for inactivity]
13:29tobhe_ has joined #asahi-alt
13:34tobhe has quit [Ping timeout: 480 seconds]
13:52kidplayer666 has joined #asahi-alt
13:52jacksonchen666 is now known as Guest12720
13:52jacksonchen666 has joined #asahi-alt
13:52jacksonchen666 has quit []
13:56Guest12720 has quit [Ping timeout: 480 seconds]
14:37tobhe has joined #asahi-alt
14:40tobhe_ has quit [Ping timeout: 480 seconds]
14:43jeisom has quit [Ping timeout: 480 seconds]
14:55tobhe_ has joined #asahi-alt
15:00tobhe has quit [Ping timeout: 480 seconds]
15:00tobhe has joined #asahi-alt
15:03tobhe_ has quit [Ping timeout: 480 seconds]
15:25possiblemeatball has joined #asahi-alt
15:40lactose has joined #asahi-alt
15:44lactoseI've done a little more research about m1n1 and U-Boot, so I think I understand them a bit better now. If I wanted to craft an image to be used with the installer, I need to set up stage 2 m1n1 + U-Boot and an EFI compatible bootloader (i.e. GRUB)?
15:46j`eyalong with the rootfs, yeah
15:53lactoseWell I figured that was a given haha. From what I could gather the installer handles stage 1 m1n1 so I wouldn't have to worry about that, is that right?
15:58lactoseAlright cool, thanks a lot
15:59matteo has joined #asahi-alt
16:02lactoseOh wow I never knew that existed, thanks
16:02lactoseI have plans to make a Slackware image so this will be incredibly useful
16:03j`eyI dont know where/if there are any slackbuilds
16:14lactoseThat first repo doesn't build an install image, it instead creates a squashfs and uses a different distro to handle the bootloader stuff
16:16lactoseAt least that's what I could make out of it. I don't really understand how it works. I know it's based on chadmed's asahi-gentoosupport though
16:19lactoseI've never worked with squashfs and I've certainly never seen one used as root
16:20j`eyit's just a way of getting a live-ish environment
16:31lactose has quit [Read error: Connection reset by peer]
16:56flokli has quit [Quit: WeeChat 4.1.1]
17:08billak has quit [Remote host closed the connection]
17:09flokli has joined #asahi-alt
17:17lactose has joined #asahi-alt
17:23lactose has quit [Read error: Connection reset by peer]
17:28possiblemeatball has quit [Read error: Connection reset by peer]
17:28possiblemeatball1 has joined #asahi-alt
17:47lactose has joined #asahi-alt
17:49lactose has quit [Read error: Connection reset by peer]
17:50lactose has joined #asahi-alt
17:50lactose has quit [Remote host closed the connection]
17:51lactose has joined #asahi-alt
17:55matteo_ has joined #asahi-alt
17:55matteo has quit [Read error: Connection reset by peer]
18:05zumi_ has joined #asahi-alt
18:05zumi has quit [Remote host closed the connection]
18:09lactose has quit [Quit: Quit]
18:10zumi_ is now known as zumi
18:16nela has quit [Ping timeout: 480 seconds]
18:26lawrence has quit [Quit: The Lounge - https://thelounge.chat]
18:26nela has joined #asahi-alt
18:30lawrence has joined #asahi-alt
18:57matteo_ has quit [Quit: Leaving...]
19:12possiblemeatball1 has quit [Quit: Quit]
19:15possiblemeatball has joined #asahi-alt
21:06psanford_ has quit [Quit: leaving]
21:06psanford has joined #asahi-alt
21:56jeisom has joined #asahi-alt
22:23jacksonchen666 has joined #asahi-alt
23:19jeisom has quit [Remote host closed the connection]
23:30pthariensflame has joined #asahi-alt
23:30pthariensflame has quit []
…