ChanServ changed the topic of #asahi-alt to: Asahi Linux: porting Linux to Apple Silicon macs | User-contributed/unofficial distribution ports | Logs: https://alx.sh/l/asahi-alt
zerdox has joined #asahi-alt
KxCORP5894 has quit [Quit: Bye!]
KxCORP5894 has joined #asahi-alt
zerdox has quit [Ping timeout: 480 seconds]
JayBeeFOSS has quit [Remote host closed the connection]
JayBeeFOSS has joined #asahi-alt
JayBeeFOSS has quit [Remote host closed the connection]
JayBeeFOSS has joined #asahi-alt
VeeBop has quit [Quit: buh bye]
<chadmed>
urgh bindgen depends on libclang, which means every livecd has to have clang and llvm...
<chadmed>
no wonder its so big
<chadmed>
actually no we can unmerge them once the kernel is built
<u154ss>
@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?
<chadmed>
u154ss: i told you to ignore them, its just u-boot
<chadmed>
if you get to the livecd and are able to select a boot option in its grub then you can ignore those messages entirely
<chadmed>
the initramfs will be loaded (it's big, it takes a while) and youll get into the livecd
<u154ss>
@chadmed, no luck, do not get that far, just the endless "XHCI timeout on event type 0..." messages. No command line.
<chadmed>
when do they start showing up
<u154ss>
@chadmed changed to a port on my USB-C hub, now it is working...
zerdox has quit [Ping timeout: 480 seconds]
<chadmed>
yes, because as i said a few times, u-boot's usb stack is awful
<chadmed>
which is why i havent made bootable media a massive priority until now
<chadmed>
you can skip that since youve booted the livecd off a usb stick
<chadmed>
that guide is for using fedora as a slingshot
<chadmed>
youre basically already at step 5
<u154ss>
@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.
<chadmed>
you can basically just follow the handbook exactly
<u154ss>
@chadmed the Gentoo x86 handbook?
<mps>
yes, usb-c ports are quirky, I often have to try different ones even with different devices not only for u-boot
<chadmed>
u154ss: yeah
zerdox has joined #asahi-alt
<u154ss>
I 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.
<u154ss>
I have no emerge or utilities etc.
<chadmed>
u154ss: the handbook will show you everything you need to do, step by step
<chadmed>
some steps can be skipped by following the guide on the asahi wiki, since install.sh from asahi-gentoosupport will do those for you
zerdox has quit [Ping timeout: 480 seconds]
<u154ss>
In the state I am in at the moment (virginal LiveCD), I have no git/clone commands etc.
<chadmed>
follow the handbook
<chadmed>
you dont do any of that stuff until you have prepared your rootfs
<u154ss>
@chadmed, I still need to run genstrap.sh?
<chadmed>
no
<chadmed>
like i said when youre booted into the livecd youre already at step 5 in the guide
<chadmed>
so from there just follow the handbook
<u154ss>
The x86 handbook?
<u154ss>
Maybe I need more coffee...
<chadmed>
yes, the x86 handbook
zerdox has joined #asahi-alt
zerdox has quit [Ping timeout: 480 seconds]
zerdox has joined #asahi-alt
<leio>
I'd go with amd64 handbook over x86
<leio>
chadmed: 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.
<chadmed>
leio: that would probably make sense given we have "real" install media now
<leio>
so 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
<chadmed>
how do the stage/livecd builders work in that regard (if you knoiw)
<chadmed>
because 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
<leio>
we need stuff from ::asahi for the livecd still?
<leio>
and I don't really know
<chadmed>
yeah we need a few things from ::asahi
<chadmed>
mostly the kernel and the dracut modules to build the initramfs properly
zerdox has quit [Ping timeout: 480 seconds]
scari has quit [Remote host closed the connection]
scari has joined #asahi-alt
zerdox has joined #asahi-alt
<leio>
sounds like a good thing to upstream, overlay can have newer versions faster, while ::gentoo has what we end up with in livecd build
<leio>
and 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
<chadmed>
if the user runs install.sh then it gets added via eselect repo so that's all good
<chadmed>
but yeah i agree. im flying to melbourne tomorrow morning and have the whole week off so ill get some of those upstreaming PRs done
chadmed has quit [Quit: Konversation terminated!]
chadmed has joined #asahi-alt
<leio>
Hope 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
<chadmed>
it'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
<u154ss>
I 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
<chaos_princess>
just put the thing it wants into package.use, it will work fine
<u154ss>
@chaos_princess /etc/portage/package.use is a directory. Does all of this stuff need to go here . /etc/portage/package.use/asahi?
<chaos_princess>
yes, 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
<chadmed>
u154ss: 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)
<chaos_princess>
i do not think lines 5 and following do what you want them to do, delete them
<u154ss>
Running 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
<u154ss>
Syntax methinks.
<chadmed>
dont put the version in the package name
<chadmed>
literally just sys-kernel/asahi-kernel etc
<u154ss_>
@all thanks for the assistance. I will have to abort the Gentoo installation at this time. I will come back later and report.
<leio>
if 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
zerdox has joined #asahi-alt
u154ss_ has quit [Remote host closed the connection]
u154ss has quit [Remote host closed the connection]
zerdox has quit [Ping timeout: 480 seconds]
zerdox has joined #asahi-alt
zerdox has quit [Remote host closed the connection]