#
…

2024-01-06

00:33eiln has joined #asahi-alt
01:13eiln has quit [Quit: WeeChat 4.1.2]
01:19lactosealright so im now past grub but now i'm stuck in initramfs it looks like
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:45chadmedwhat are you using to generate it
01:50lactoseI used the one that was included with the kernel in Slackware ARM, I don't know how to generate one
01:58chadmedplease use dracut
02:24lactosedracut isn't packaged, I'm not sure if that's a problem
02:34kidplayer666 has quit [Quit: Connection closed for inactivity]
03:01jeisom has joined #asahi-alt
03:06chadmedif slackware has some other initramfs generating infrastructure _probably_ not
03:06chadmedso long as you cna specify things to add to it
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:06chadmedit just makes this so much eaiser
03:35VeeBop has quit [Ping timeout: 480 seconds]
03:49VeeBop has joined #asahi-alt
04:00jeisom has quit [Ping timeout: 480 seconds]
04:08lactosechadmed: Where are these drivers located? do I compile them myself?
04:17JayBeeFOSS has quit [Remote host closed the connection]
04:18JayBeeFOSS has joined #asahi-alt
04:43chadmedlactose: theyre part of the kernel..
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:45chadmedyoure supposed to run dracut to build the initramfs _before_ you zip up the root image
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:39lactoseWait so even if it's baked into the kernel it's still called a module?
07:50mpslactose: I guess chadmed talking about kernel package (not vmlinuz - kernel) where are modules
07:50chadmedits not baked into the kernel. all of those drivers are/should be modules
07:51lactoseWhere can I find them? Because I certainly didn't put them in my image
07:51mpsbut nowadays some call drivers as module even when they compiled in kernel
07:52chadmedif you installed your kernel properly they will be in /lib/modules/
07:53lactoseWell I probably didn't
07:53chadmedplease just use dracut though it takes care of all of this automatically
07:53chadmedyou dont need to/should not be trying to build initramfses manually
07:53lactoseI understand that but what's the proper way to install a kernel?
07:54lactoseI just took the source tree, checkout the latest tag, and compiled it
07:54chadmedmake install && make modules_install assuming youre building from source
07:54chadmedthen all the grub updating etc
07:54mpslactose: proper way should be how your distro does this
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:55mpsah, maybe asahi kernel isn't packaged for slackware
07:55chadmedyeah so make the package
07:55lactosemake install from within a chroot?
07:56mpsbest way would be to make slackware pkg of asahi kernel
07:56lactoseIn order to make a package I'd need to know where all the files need to go
07:56lactoseSlackware packages are just tarballs with a post install script
07:57mpsI guess you look at current slackware kernel pkg
07:57sventhere should be some normal Slackware kernel package, shouldn’t there?
07:57chadmedjust take whatever slackware does for a normal kernel and point it at the asahi sources and a valid config
07:57lactoseWhat? Slackware isn't source based
07:58chadmedthe package manager will have some sort of instruction or infrastructure for building your binary packages though
07:58chadmedslackbuilds or whatever
07:58mpsI didn't used slackware for more than 25 years but I bet it is still binary distro
07:59chadmedr0ni's repo has slackbuilds for m1n1 and an old version of libunwind
07:59chadmedupstream slackware will have something similar from which they build the kernel binary package
07:59lactoseIf I make a slackbuild that will take ages to build
08:00chadmedyeah but at least it will be correct lmfao
08:00chadmedi dont think theres any point doing this if youre not going to do it properly
08:00chadmedyoull just end up with an unmaintainable mess of bs
08:00svenright, and there should be some slack build or something that generates that kernel package
08:00chadmedyeah but do you understand that gets built by slackware maintainers on the backend
08:00chadmedand automatically packaged up
08:01chadmedlike folks arent sitting there manually building package tarballs
08:01svenand building a kernel shouldn’t really take hours :/
08:01chadmeddistro specced kernel might on a base m1
08:02svenhours??
08:02mpslactose: does slackware have developers IRC channel? if yes then you can ask there how to build package.
08:02chadmedbut my gentoo kernel takes like 15 mins on a 15" m2 air
08:02sveneven a bloated kernel config took maybe 20 minutes on my m1 air
08:03mpslooks like here aren't any of slackware devs (or they still sleep)
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:04chadmedyoud have to set up a cross toolchain
08:04lactoseI do have that, but I was moreso asking if it's possible to chroot into an ARM root
08:04Guest12859of course it is
08:04sam_not sure "of course" is really right there
08:05sam_it's not obvious
08:05sam_with qemu-user it is possible, yes
08:05sam_just slow :)
08:05chadmedthis isnt really something you can do "properly" in a chroot
08:05chadmedour drivers will not get loaded for instance
08:05chadmedyou need to be doing this on hardware to make sure it actually works
08:06sam_yes, sorry, to be clear, answering the specific question about chrooting, and not the rest of it
08:06chadmedyou could get away with building the images in a cross environment
08:06chadmedbut you still need to be using your mac to make sure it works
08:06lactoseOkay then, how should I go about building the packages?
08:06Guest12859 is now known as tdr
08:06chadmedwe dont know we're not slackware devs
08:06lactoseSince you need Slackware to build a slackbuild
08:07sam_i generally recommend using a distro where you're comfortable with its packaging and how to use it
08:07sam_especially if trying to port to new hw...
08:07mpsmy first builds of asahi kernels were on arm64 LXC
08:07chadmedyou can just chroot into a slackware root from fedora asahi and do it there
08:07lactoseI understand how slackbuilds work
08:07sam_so surely there's a slackbuild for the kernel you can use to start with?
08:07chadmedbut the images you build therein need to be tested on bare metal
08:08lactoseI'm asking about the logistics of actually building a slackbuild
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:10chadmedugh... so apparently slackware packages _are_ just built manually
08:11chadmedand the tarball is just a tarball of DESTDIR...
08:11lactoseslackbuilds are yes
08:13sam_amazing
08:14lactoseslackbuilds are unofficial but afaik most slackware users use it because it beats having to compile and install stuff manually
08:14lactoseThey are essentially build scripts
08:14mpssometimes I built tar.gz kernels with this simple script https://tpaste.us/a1gN and run mkinitfs manually, on alpine
08:15chadmedlactose: yeah so is the output of a slackbuild a package?
08:17lactoseI'm pretty sure it is?
08:18lactoseI'll have to do some more reading
08:18chadmedyeah so surely somewhere in the official docs/repos will be a slackbuild for the kernel
08:18chadmedyou just take that and rework it to build the asahi sources
08:20lactoseAlright then, I'll do that then
08:21lactoseBut first I probably should delete the Linux partitions since they aren't useful to me right now
08:21lactoseHow do I do that?
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:27lactosehmm? I've never run straight QEMU, let alone on MacOS
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
08:29mpslactose: this could give you some hints https://arvanta.net/alpine/qemu-access-linux-m1/
09:10j`eylactose: you can use UTM instead of qemu, for a GUI
09:11lactoseI see, can I pass a drive with UTM as well?
09:11j`eyI couldn't get that working, you can with qemu though
09:12j`ey(well an interntal partition I tried to get working, not sure about a USB drive)
09:13mpsj`ey: safest method is to use CLI, IME OFC
09:15mpsbtw, is there some tool to control bass/treble on speakers, like equalizer
09:18chadmedyou can use easyeffets
09:22mpschadmed: thanks
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:09r0nii'll look around for a asahi kernel config and add slackbuilds to my repo
12:09j`eybut I dunno if it needs updating
12:10r0ni... and packages for that matter
12:14chadmedj`ey: its still current if youre swivelling from ALARM which still works
12:15j`eychadmed: make a useless edit so the page date looks recent :P
12:16mpsslackware is still popular? (I'm surprised)
12:18u154ssThanks j'ey. Will have a look.
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:24j`eywhy is it totally diffeerent?
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:27chadmedwe dont ship a kernel config
12:27chadmedi can dump mine somewhere if you want
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:29r0nichadmed that would be cool, would make a package much easier to make
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:29chadmedwe only ship asahi-sources atm
12:30mpsand I was easy for me to switch to alpine 'rebasing' my knowledge about slackware
12:30j`eyu154ss: good luck!
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:31mpsr0ni: and I was positively surprised that slackware is still popular
12:31r0nii think theres a group of hardcore enthusiasts keeping it alive
12:31r0nichadmed: thank you sir!
12:32chadmedno worries :)
12:32chadmedits probably a bit barebones to ship as a distro package though
12:32mpsif the slackware switch to musl I will again test it
12:32chadmedi build only the stuff i actually use
12:32r0niwell for being asahi specific, i assume it'd be ok
12:32u154ss has quit [Remote host closed the connection]
12:33chadmedprobably not tbh
12:33chadmedi dont build any drivers for things that can be attached externally
12:33chadmedusb devices etc
12:33r0nislackwarearm ships a generalized kernel and machine specific ones cuz arm
12:33chadmedexcept the like 3 things i actually plug into these machines
12:34r0nihrm well I'll look at the config and add some things in that they ship
12:35r0nii know the basics it needs, i just havne't build one in quite some time
12:36chadmedthe only things you need to keep from mine are the apple related ones
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:36chadmedeverything else can be however slack does it
12:41r0niya i see a lot of "is not set" in there ;)
12:42chadmedtold ya
12:42mpshm, so alpine is the best distro for asahi, everything (or nearly everything) is in official repo
12:43chadmedsam_, leio: that sounds like a direct challenge to me
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:58mpsyes, it is fast and lean thanks to musl
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
12:59r0nigentoo boot disk is a magic key to installing anything in vmware
13:00r0nithat and any rootfs and you're golden
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:03r0niadd mesa and thats basically how i roll, but i do a fresh installation usually
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:08r0niabout all i copy is my sway config... really all i need
13:09r0niif i'm using gnome, the default stuff is fine for me, but sway is my norm
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:11leiochadmed: you know I think that should have been all in main tree long ago besides mesa! :)
13:11john-cabaj has quit [Quit: john-cabaj]
13:12kidplayer666 has quit [Quit: Connection closed for inactivity]
13:13chadmedit's been finding the time and energy thats the challenge
13:13chadmedwork is... getting unpleasant
13:15j`eywhat about uboot?
13:16chadmedu-boot is a whole discussion that needs to happen
13:16chadmedbecause of the approximately eleventy bagrillion boards that all have slightly different versions
13:17leiook, maybe besides u-boot initially too
13:17leiobut that's something that might be possible to package under an asahi name, unlike mesa
13:17leioas nothing else depends on it
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:19chadmedwhich iirc was something we really, really wanted to avoid
13:22leioI think practicality trumps it, especially if we figure out a way to deal with mesa as well without needing an overlay.
13:22leioor once the uapi is made stable
13:23chadmedthe mechanism i thought of could be used for both
13:23chadmedbut i think with mesa the smart play is to just wait
13:23j`eywhat about the kernel sources?
13:24leiothere are numerious sys-kernel/*-sources
13:24leionumerous*
13:25leiois asahi u-boot built from upstream?
13:25chadmedno its our fork
13:25leiothen it can be a separate package for the time being
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:33mpsI would like to make something similar for alpine and have few questions for debian people who made this
13:34mpsGlanzmann is rarely here and I don't know if someone else works in this
13:34mpscy8aer maybe?
13:35j`eyothers can probably answer
13:36mpsj`ey: my bets are on you ;-)
13:36cy8aermps: I just switched in and need to read first
13:36j`eyand others!
13:37mpscy8aer: ah sorry than, I misunderstood some of your previous messages about subject
13:37mpsj`ey: ofc, I'm just kidding a little
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:40j`eyyup, since that script is what alarm/fedora uses too
13:40j`eyjust modified to point to the debian stuff
13:41mpsand also put these scripts somewhere on the web
13:41mpsso I don't need to build installer and put it on the web
13:42mpsnice, looks easier than I thought
13:42mpsj`ey: cy8aer: thanks for explanation
13:42chadmednah you can swing the asahi installer and just feed it the json pointing to your images
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:43mpsalpine installer could be excepted next weekend if something doesn't need more work
13:44cy8aerboth - asahi installer and alpine installer for efi would be the best solution.
13:45mpsyes, but first step first, later we will see
13:46cy8aeron the debian side: It is quite difficult to build the installer - that takes time too.
13:47mpsit took me little time last night on alpine after j`ey explained me what is needed
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:25leiomps: it's not like gentoo hasn't had asahi u-boot for 1.5 years already ;)
14:26mpsleio: I know, but I wanted to say about cursor and bigger fonts
14:27leioaha, ok
14:27mpsalpine u-boot-asahi had cursor and terminus fonts from the start
14:28mpsand about month or two ago Simon Glass added cursor to u-boot
14:29mpsu-boot mainline*
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?
15:52j`eyu154ss: ah right. you need to export EXPERT=1
15:52j`eythen run the installer
15:54u154ss@j'ey fairenough. Like so - EXPERT=1 curl -L https://alx.sh/ |sh ??
15:55u154ssfair enough
16:00u154ss has quit [Remote host closed the connection]
16:50ameliabadelia has joined #asahi-alt
16:56possiblemeatball has joined #asahi-alt
18:23tpw_rulesdoes it still have the uefi only option without expert mode?
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
…