#
…

2024-06-29

00:25zerdox has joined #asahi-alt
01:00KxCORP5894 has quit [Quit: Bye!]
01:00KxCORP5894 has joined #asahi-alt
01:50zerdox has quit [Ping timeout: 480 seconds]
02:16JayBeeFOSS has quit [Remote host closed the connection]
02:17JayBeeFOSS has joined #asahi-alt
02:37JayBeeFOSS has quit [Remote host closed the connection]
02:39JayBeeFOSS has joined #asahi-alt
04:29VeeBop has quit [Quit: buh bye]
04:30chadmedurgh bindgen depends on libclang, which means every livecd has to have clang and llvm...
04:31chadmedno wonder its so big
04:31chadmedactually no we can unmerge them once the kernel is built
04:32VeeBop has joined #asahi-alt
04:44kode54 has quit [Quit: The Lounge - https://thelounge.chat]
04:44KDDLB has quit [Quit: The Lounge - https://thelounge.chat]
04:47kode54 has joined #asahi-alt
04:48cylm has joined #asahi-alt
04:52cylm_ has quit [Ping timeout: 480 seconds]
04:56cylm has quit [Ping timeout: 480 seconds]
05:10zerdox has joined #asahi-alt
05:26scari has joined #asahi-alt
06:04u154ss has joined #asahi-alt
06:10u154ss@chadmed et all as stated the other day, the Gentoo installer ISO when burnt to a USB stick works perfectly on my M1 Mini. Command sequence: setenv boot_targets "usb"; setenv bootmeths "efi"; boot. On the M2 Mini, repeating the same command sequence, again "XHCI timeout on event type 0..." appears endlessly. no way to interuppt etc. Any ideas?
06:13chadmedu154ss: i told you to ignore them, its just u-boot
06:13chadmedif you get to the livecd and are able to select a boot option in its grub then you can ignore those messages entirely
06:13chadmedthe initramfs will be loaded (it's big, it takes a while) and youll get into the livecd
06:16u154ss@chadmed, no luck, do not get that far, just the endless "XHCI timeout on event type 0..." messages. No command line.
06:19chadmedwhen do they start showing up
06:19u154ss@chadmed changed to a port on my USB-C hub, now it is working...
06:19zerdox has quit [Ping timeout: 480 seconds]
06:20chadmedyes, because as i said a few times, u-boot's usb stack is awful
06:21chadmedwhich is why i havent made bootable media a massive priority until now
06:29u154ss@chadmed as per your documentation, I am not at step 4 in your documentation - https://github.com/AsahiLinux/docs/wiki/Installing-Gentoo-with-LiveCD??
06:29u154ssnot = now
06:30chadmedyou can skip that since youve booted the livecd off a usb stick
06:30chadmedthat guide is for using fedora as a slingshot
06:30chadmedyoure basically already at step 5
06:31u154ss@chadmed stupid question, what tools do I have to download stuff for a basic Gentoo install at this stage? openssh-server Gentoo Stage 3 etc.
06:32chadmedyou can basically just follow the handbook exactly
06:33u154ss@chadmed the Gentoo x86 handbook?
06:34mpsyes, usb-c ports are quirky, I often have to try different ones even with different devices not only for u-boot
06:34chadmedu154ss: yeah
06:34zerdox has joined #asahi-alt
06:35u154ssI am in the LiveCD already, how do I proceed fro here. The last time I installed a Gentoo system on an Intel box was about twenty years ago.
06:38u154ssI have no emerge or utilities etc.
06:46chadmedu154ss: the handbook will show you everything you need to do, step by step
06:46chadmedsome steps can be skipped by following the guide on the asahi wiki, since install.sh from asahi-gentoosupport will do those for you
06:51zerdox has quit [Ping timeout: 480 seconds]
06:52u154ssIn the state I am in at the moment (virginal LiveCD), I have no git/clone commands etc.
06:58chadmedfollow the handbook
06:59chadmedyou dont do any of that stuff until you have prepared your rootfs
07:26u154ss@chadmed, I still need to run genstrap.sh?
07:27chadmedlike i said when youre booted into the livecd youre already at step 5 in the guide
07:27chadmedso from there just follow the handbook
07:28u154ssThe x86 handbook?
07:28u154ssMaybe I need more coffee...
07:29chadmedyes, the x86 handbook
07:33zerdox has joined #asahi-alt
08:03zerdox has quit [Ping timeout: 480 seconds]
08:35zerdox has joined #asahi-alt
08:53leioI'd go with amd64 handbook over x86
08:58leiochadmed: I think the handbook is a collection of templates where each arch then includes the parts it wants, we should be able to make an asahi one out of it really too. I just don't understand how it's done, like e.g. IA64 has custom bootloader text, but the "Edit source" of it doesn't reveal me anything special, but we can ask gentoo wiki people.
08:58chadmedleio: that would probably make sense given we have "real" install media now
09:00leioso we can make the install media official through the upstreaming efforts of that, get that into a cron job and all, and make a asahi handbook and just avoid any of this "which guide you use" business and cross-referencing by just having a full on handbook
09:02chadmedhow do the stage/livecd builders work in that regard (if you knoiw)
09:03chadmedbecause i have specfiles and a builder script that pulls in ::gentoo and ::asahi and builds the media so if we can call that on the builders then we dont have to rush to upstream fast-moving stuff
09:06leiowe need stuff from ::asahi for the livecd still?
09:07leioand I don't really know
09:18chadmedyeah we need a few things from ::asahi
09:18chadmedmostly the kernel and the dracut modules to build the initramfs properly
09:36zerdox has quit [Ping timeout: 480 seconds]
09:46scari has quit [Remote host closed the connection]
09:46scari has joined #asahi-alt
09:48zerdox has joined #asahi-alt
10:08leiosounds like a good thing to upstream, overlay can have newer versions faster, while ::gentoo has what we end up with in livecd build
10:09leioand the handbook could document adding asahi overlay as a step via eselect repository or similar, if it doesn't get added out of the box somehow
10:10chadmedif the user runs install.sh then it gets added via eselect repo so that's all good
10:11chadmedbut yeah i agree. im flying to melbourne tomorrow morning and have the whole week off so ill get some of those upstreaming PRs done
10:11chadmed has quit [Quit: Konversation terminated!]
10:11chadmed has joined #asahi-alt
10:13leioHope sam_ can help, I'm completely backtracked and swamped and will need to handle backlog for weeks after I can get some gentoo time in
10:17zerdox has quit [Ping timeout: 480 seconds]
10:25scari has quit [Ping timeout: 480 seconds]
10:27u154ss@chadmed what do have have in your /etc/portage/ to make this all work... See screenshot https://paste.debian.net/1321819/
10:35chadmedmy /etc/portage is.... unconventional
10:35chadmedit's best to just do as portage says. make a file like /etc/portage/package.use/asahi and put "dev-lang/rust-bin rustfmt rust-src" in it
10:37u154ssI have these entries in my /etc/portage/package.use/asahi - GNU nano 8.0 /etc/portage/package.use/asahi # Remove '-audio' before emerging a DE metapackage or WM # Remove 'kernel' and '-sources' if you plan to replace the # dist-kernel with sys-kernel/asahi-sources sys-apps/asahi-meta kernel -sources -audio
10:39u154ssI have not touched this file at all.
10:46chaos_princessjust put the thing it wants into package.use, it will work fine
10:50u154ss@chaos_princess /etc/portage/package.use is a directory. Does all of this stuff need to go here . /etc/portage/package.use/asahi?
10:51chaos_princessyes, the specific file name inside there does not matter, personally i organize it by package name, (i.e dev-lang-rust), but you can do whatever you prefer
10:54chadmedu154ss: it doesnt matter what you call the file inside package.use, as long as it has the package name (dev-lang/rust-bin) and the use flags portage asked for (rustfmt rust-src)
10:55u154ssJust a sec...
10:59u154ss@all this is my /etc/portage/package.use/asahi before running install.sh again.. https://paste.debian.net/1321830/
11:00chaos_princessi do not think lines 5 and following do what you want them to do, delete them
11:01u154ssRunning install install.sh gives me this - nvalid atom in /etc/portage/package.use/asahi-copy: sys-kernel/asahi-kernel-6.8.10_p2::asahi --- Invalid atom in /etc/portage/package.use/asahi-copy: sys-apps/asahi-meta-2-r8::asahi --- Invalid atom in /etc/portage/package.use/asahi-copy: sys-boot/m1n1-1.4.14::asahi
11:01u154ssSyntax methinks.
11:04chadmeddont put the version in the package name
11:04chadmedliterally just sys-kernel/asahi-kernel etc
11:07u154ss@chadmed it would seem the install is progressing - https://paste.debian.net/1321831/
12:31u154ss_ has joined #asahi-alt
12:33u154ss_@all thanks for the assistance. I will have to abort the Gentoo installation at this time. I will come back later and report.
12:48leioif you for some reason need a specific version, then = in front would make it valid, or ~ for any revision of that version, but for package.use that's usually not what you'd want
12:53zerdox has joined #asahi-alt
13:18u154ss_ has quit [Remote host closed the connection]
13:18u154ss has quit [Remote host closed the connection]
13:29zerdox has quit [Ping timeout: 480 seconds]
13:34zerdox has joined #asahi-alt
13:43zerdox has quit [Remote host closed the connection]
14:17SalimTer- has joined #asahi-alt
14:20SalimTerryLi has quit [Ping timeout: 480 seconds]
15:04u154ss has joined #asahi-alt
15:04u154ss@all Could someone please tell me I am doing WRONG here - https://paste.debian.net/1321845/
15:20u154ss has quit [Quit: Page closed]
15:28chaos_princess`echo 'dev-lang/rust-bin rust-src rustfmt' >/etc/portage/package.use/dev-lang-rust-bin`
16:13leiosam_: would be neat to have profile mixins easier, and we could just add some asahi one on top
16:14leioof the standard choice, without having to make some combinatorial explosion
17:38sam_starting to feel increasingly like this is importanr
18:19cylm has joined #asahi-alt
20:20zerdox has joined #asahi-alt
20:53cylm has quit [Ping timeout: 480 seconds]
20:58cylm has joined #asahi-alt
21:01cylm_ has joined #asahi-alt
21:08cylm has quit [Ping timeout: 480 seconds]
21:08chadmed has quit [Quit: Konversation terminated!]
21:57ipatch has quit [Quit: WeeChat 4.3.2]
22:14ipatch has joined #asahi-alt
22:22KDDLB has joined #asahi-alt
…