2024-01-06
00:33eiln has joined #asahi-alt
01:13eiln has quit [Quit: WeeChat 4.1.2]
01:23lactose"mount: can't find /mnt in /etc/fstab" and "ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead."
01:36lactoseMaybe I'm missing something in my initrd, I'm not sure what though, I've never generated one myself
01:50lactoseI used the one that was included with the kernel in Slackware ARM, I don't know how to generate one
02:34kidplayer666 has quit [Quit: Connection closed for inactivity]
03:01jeisom has joined #asahi-alt
03:06chadmedlook at the dracut config files in asahi-scripts for what the initramfs needs to be able to do
03:06chadmedi think the easiest solution would be to get dracut packaged in slackware first and take it from there
03:35VeeBop has quit [Ping timeout: 480 seconds]
03:49VeeBop has joined #asahi-alt
04:00jeisom has quit [Ping timeout: 480 seconds]
04:17JayBeeFOSS has quit [Remote host closed the connection]
04:18JayBeeFOSS has joined #asahi-alt
05:14Catyre has joined #asahi-alt
05:14Catyre has quit [Remote host closed the connection]
05:42lactosechadmed: then what exactly is being included here? https://github.com/AsahiLinux/asahi-scripts/blob/main/dracut/dracut.conf.d/10-asahi.conf also how am i supposed to run dracut on a system i can't boot into yet?
06:27possiblemeatball has quit [Quit: Quit]
06:43chadmedthat file is telling dracut to explicitly add those kernel modules to the initramfs so that they can be loaded and the machine can boot successfully
06:43chadmedif youre trying to bootstrap a rootfs then you need to do that from a distro which works first
06:52Carvajal has joined #asahi-alt
07:22kidplayer666 has joined #asahi-alt
07:24lactose has quit [Ping timeout: 480 seconds]
07:37lactose has joined #asahi-alt
07:50mpslactose: I guess chadmed talking about kernel package (not vmlinuz - kernel) where are modules
07:55chadmedbut yeah thats a good point the correct way to do this is to use slackware's packaging infrastructure to do all this
07:57chadmedjust take whatever slackware does for a normal kernel and point it at the asahi sources and a valid config
07:58chadmedthe package manager will have some sort of instruction or infrastructure for building your binary packages though
07:59chadmedupstream slackware will have something similar from which they build the kernel binary package
08:00lactoseAlso kernel package is this http://ftp.arm.slackware.com/slackwarearm/slackwareaarch64-current/slackware/a/kernel_armv8-6.1.69-aarch64-1.txz
08:00svenright, and there should be some slack build or something that generates that kernel package
08:02mpslactose: does slackware have developers IRC channel? if yes then you can ask there how to build package.
08:03lactoseIs it possible to do this on my AMD64 desktop? I'm not sure if I wanna work on this with my M1 MBP
08:04Guest12859of course it is
08:06sam_yes, sorry, to be clear, answering the specific question about chrooting, and not the rest of it
08:06Guest12859 is now known as tdr
08:07sam_i generally recommend using a distro where you're comfortable with its packaging and how to use it
08:09chadmedyou can just do that in a chroot then exfil the packages or whatever needs to happen to get them installed in your prospective root image
08:09lactoseI'm not sure if slackbuilds allow me to create a binary package, that I'll have to look into
08:14lactoseslackbuilds are unofficial but afaik most slackware users use it because it beats having to compile and install stuff manually
08:14mpssometimes I built tar.gz kernels with this simple script https://tpaste.us/a1gN and run mkinitfs manually, on alpine
08:21lactoseBut first I probably should delete the Linux partitions since they aren't useful to me right now
08:25mpslactose: btw, you can run qemu on macos probably with slackware current arm64 image and build kernel in it. it is quite fast
08:28lactoseAlso while I couldn't find an "official" kernel slackbuild I found something that's good enough to work with https://github.com/perrin4869/linux-kernel-slackbuild/blob/master/linux.SlackBuild
09:37jeisom has joined #asahi-alt
09:45jeisom has quit [Quit: Leaving]
09:51lactose has quit [Quit: Quit]
11:31qyliss has quit [Quit: bye]
11:34qyliss has joined #asahi-alt
12:00john-cabaj has joined #asahi-alt
12:04u154ss has joined #asahi-alt
12:08r0nithis guy does not really know slackware if compiling the kernel isn't something they have figured out yet
12:08u154ssRevisiting this theme again.. is there a definitive and current Gentoo/Asahi install guide? My goal would be to install Gentoo alongside (dual boot) my existing Debian setup. I have seen Jared's version, bit I am note sure as to it's currency. Chadmed?
12:20r0nislackware is not flashy nor full of bullshit packaging ideas and is not corporately sponsored... it's rock solid and for linux pros, stays out of the way. You can't get that with fedora or these other systems. Its for boomers who dont want their hand held and want to do what they want to do with their system. it's not for everyone, and many dont want that level of control
12:21r0nifor someone who needs to "read up" on a slackbuild trying to get asahi to run.... isn't likely
12:23r0nia build script is a build script, a slackware one is simpler as the system doens't do anything, it's all done in the slackbuild.... except for the ARM port, that's almost totally different than the x86 base
12:25r0nithe arm port author has crafted a system to do things... but one could still use a plain slackbuild on it... he's just coming at it from defining things each package does and make a devkit for it. scripts can be much simpler
12:27r0niwhere is the kernel config for asahi-gentoo?, im not finding it in the repo, is it in main gentoo somewhere?
12:28r0nireally? huh wow i always steal kernel configs from gentoo bootdisk but it's on 6.1 right now on arm64
12:28chadmedyeah thats just because the kernel install script puts it there when the images are built
12:28mpsr0ni: I didn't want to say anything bad about slackware, it was my first distro on which I started to use linux seriously for work
12:29chadmedgentoo has two approaches to kernels: sources and distkernels. distkernels are your traditional distro-supported canned configs (still built locally but automated from a known-good config) where as -sources packages leave everything to the user
12:30u154ss@Chadmed/j'ey will try this https://github.com/AsahiLinux/docs/wiki/Installing-Gentoo-with-LiveCD and report back..
12:30r0nimps: no hard feelings, it's def not for everyone. Its just where i'm comfortable. I use plenty diff distros, but slackware is the one i use the most
12:32u154ss has quit [Remote host closed the connection]
12:36r0nithey are about to switch to 6.6 i might be able to even get it into the base config for booting support in kernel at least
12:42mpshm, so alpine is the best distro for asahi, everything (or nearly everything) is in official repo
12:54mpsr0ni: btw, alpine also doesn't have any commercial entity behind it, only build/CI machines are sponsored but we don't accept any influences from the sponsors. And we don't package any closed or non-free software
12:56r0nireally huh? i've tried it out a few times, and it seems decent. i have a vm on my intel mac running gnome but i still have very little idea how it works as a system
12:57r0nii was going to do a vm on my arm mac just lazy and haven't gotten to it.. i like how speedy it is, even in a vm on decade old hardware
12:58mpsif you ever want to try alpine on 'strange' hardware here are some my short guides https://arvanta.net/alpine/
12:59r0nione reason why i haven't bothered with asahi-slackware was I found how well it ran on vmware... and i couldnt find a reason for all the trouble to run natively
13:01r0nionly qemu i use is with nbd to mount disks but i've not had so much fun with utm and such. never get any networking to work
13:02mpsI'm probably boring now, but when I started to use M1 I simply copied rootFS and home dir from one of my arm64 chromebooks, build m1n1 and kernel and installed on M1. nothing more
13:05mpsinstalling and configuring everything from start is boring for me, easier is simply copy what I already have and tweaked for my workflow
13:10r0nii maintain repos and package sets for slackware tho, so ensuring sane defaults is what i'm after and i do a lot of clean installs etc
13:11john-cabaj has quit [Quit: john-cabaj]
13:12kidplayer666 has quit [Quit: Connection closed for inactivity]
13:16chadmedbecause of the approximately eleventy bagrillion boards that all have slightly different versions
13:17chadmedinitially i was going to try and make the version in ::asahi easily generalisable for different flavours but i think that discussion needs to happen further upstream because i dont want to make assumptions about the Correct Way to do things
13:19chadmedi think upstreaming it as uboot-asahi or something similar would open the floodgates for 99999 different uboot-* packages in the tree
13:22leioI think practicality trumps it, especially if we figure out a way to deal with mesa as well without needing an overlay.
13:29mpsif you want u-boot with (clunky) cursor and bigger fonts look at https://git.alpinelinux.org/aports/tree/community/u-boot-asahi
13:33mpslast night I looked at https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/ and especially https://tg.st/u/asahi-installer-bootstrap.sh
13:33mpsI would like to make something similar for alpine and have few questions for debian people who made this
13:39mpsI see that script https://tg.st/u/asahi-installer-bootstrap.sh use installer from https://cdn.asahilinux.org/installer/ and have tailored installer_data.json for debian and zipped rootFS somewhere
13:40cy8aerAnd - as I understand asahi-installer-bootstrap.sh: There is a complete debian distribution in a zipped file and downloadable. Then there is a json https://tg.st/u/installer_data.json which describes the partitioning and al the downloadable files defined.
13:40mpsmy question is: is it enough to put installer_data.json somewhere and zipped alpine rootFS and use same scripts as debian uses
13:43cy8aerThough it has disadvantages (why I actually try to create a debian network installer iso for mac): No self configuration stuff, likle disk encryption and changeing file system...
13:51xcpy0 has quit [Quit: The Lounge - https://thelounge.chat]
13:52cy8aeryeah, but in debian they have another packaging format inside the installer and I need to repack my kernel to this format. I will ask the bananas people if they have experience with the installer.
13:58kidplayer666 has joined #asahi-alt
13:58r0niok, kernel building, updated m1n1, need to upload packages, mesa, and figure out what is needed for dracut and thats bout all outside of an installer I reckon is needed
14:09r0niwelp it failed at modules, and it's past my bedtime, so i'll have to look after work tomorrow... no slackware pkgs going up as of yet
14:31mpsAndre Prziwara (if I wrote last name correct) made fist versions of cursor patch and terminus fonts for u-boot which I took later and refactored
15:01jeisom has joined #asahi-alt
15:17lactose has joined #asahi-alt
15:32kraem is now known as Guest13066
15:32kraem has joined #asahi-alt
15:36Guest13066 has quit [Ping timeout: 480 seconds]
15:44zzywysm has joined #asahi-alt
15:46zzywysm_ has quit [Ping timeout: 480 seconds]
15:49u154ss has joined #asahi-alt
15:52u154ss@j'ey/chadmed the Asahi installer's OS choice is now exclusively Fedora. This guide - https://github.com/AsahiLinux/docs/wiki/Installing-Gentoo-with-LiveCD is Arch-oriented. Are there any gotcha's here?
16:00u154ss has quit [Remote host closed the connection]
16:50ameliabadelia has joined #asahi-alt
16:56possiblemeatball has joined #asahi-alt
19:09amelia has joined #asahi-alt
19:09amelia is now known as Guest13092
19:13ameliabadelia has quit [Ping timeout: 480 seconds]
19:22Guest13092 has quit [Ping timeout: 480 seconds]
19:38amelia_ has joined #asahi-alt
21:27john-cabaj has joined #asahi-alt
21:50john-cabaj has quit [Ping timeout: 480 seconds]
22:11v9c6or has joined #asahi-alt
22:18amelia_ has quit [Ping timeout: 480 seconds]
22:24v9c6or has quit []
22:41xcpy0 has joined #asahi-alt
23:22seb91nihel has joined #asahi-alt
23:22seb4nihel has quit [Ping timeout: 480 seconds]
23:26lactose has quit [Ping timeout: 480 seconds]
23:26lactose has joined #asahi-alt
23:52lawrence has joined #asahi-alt