ChanServ changed the topic of #asahi-dev to: Asahi Linux: porting Linux to Apple Silicon macs | Non-development talk: #asahi | General development | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-dev
<MikeWyxtt>
Hi! I am interested in contributing to the project in some way. I have some (hobbyist) low-level systems programming experience but nothing ARM related. Just writing a small kernel in Rust, not really applicable to this but i do know how to read/write C as well. Wouldn't consider myself a pro by any means however. I have a 2024 MacBook Air with the M3 chip, after seeing Hectors post im not sure how much help i can really be
<MikeWyxtt>
but if someone would be interested in onboarding me i would be happy to help, even if its just cleaning up a wiki or something
chadmed has quit [Quit: Konversation terminated!]
chadmed has joined #asahi-dev
flom84 has joined #asahi-dev
<chadmed>
theres not really a lot of front-ended onboarding to do
<chadmed>
just find something you think would be interesting to work on and start asking questions :)
flom84 has quit [Remote host closed the connection]
<chadmed>
the yaks page is a good place to start though it hasnt been updated in a while
<j`ey>
M3 is currently in a state of having to bash stuff together yourself
chrisl has quit [Ping timeout: 480 seconds]
<MikeWyxtt>
okay fair enough. I'll hang out in here for a few days to learn how things go in here. I'm willing to bash stuff together myself, just curious if any attention/work on the M3 chip would be welcome or considered a distraction?
nela has quit [Quit: bye!]
nela has joined #asahi-dev
MikeWyxtt has quit [Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…]
MikeWyxtt has joined #asahi-dev
<chadmed>
itd be welcome
<MikeWyxtt>
sounds good. I'll start browsing the commit logs and reading up on the wiki
psykose has quit [Remote host closed the connection]
chrisl has joined #asahi-dev
chrisl has quit [Ping timeout: 480 seconds]
kokoschmoko has quit [Ping timeout: 480 seconds]
___nick___ has quit [Ping timeout: 480 seconds]
kaazoo has quit [Quit: Leaving.]
<MikeWyxtt>
Hopefully not a stupid question, but when it was stated that ill have to hack together a system that boots on an m3 chip did that mean i need to modify the install script or manually partition and insatll everything? Because from reviewing the asahi-installer code it appears i can modify a few things to get it to run on my macbook air?
<chaos_princess>
if you patch the installer, it will work, and install a copy of linux that will crash in early boot
<MikeWyxtt>
thats what im looking forward to tinkering with :) sounds good.
Halian has joined #asahi-dev
Halian has quit [Read error: Connection reset by peer]
<yuka>
^ what tooling was used to create these dumps?
aptzero has quit [Remote host closed the connection]
<yuka>
Both m1n1 and darwin
<MikeWyxtt>
im going to submit a PR to have the asahi-installer verify the 'certifi' python package is installed and if not install it, or would it be more appropriate to just have it throw an error and give an intsruction on how to fix eg 'pip3 install certifi'?
<MikeWyxtt>
i was unable to successfully complete the build until i installed that package.
pb17 has quit [Ping timeout: 480 seconds]
<chaos_princess>
the installer as comes from the website has it's own copy of python and vendors all required packages
<MikeWyxtt>
yeah im seeing that in the code now that im looking closer. I dpm
<MikeWyxtt>
dont see where its pulling certifi, i had to install it manually? perhaps i did something wrong
<j`ey>
MikeWyxtt: you mean to build it. not run it?
pb17 has joined #asahi-dev
<MikeWyxtt>
yes. i ran 'USE_CLANG=1 ./build.sh'
<MikeWyxtt>
i pulled the build script from 'main' branch of asahi-linux repo on github, and pulled the git submods. then executed that command
<fl0_id>
MikeWyxtt you can also just start m1n1 for now, which prob also doesn't work I assume
<MikeWyxtt>
fl0_id: Yeah i was trying to patch the build script first to have it setup things in a known way (partitions and whatever else, still wrapping my head around this). Then i was going to move on to the tethered setup so i can test kernels
<MikeWyxtt>
Unless that's backwards of what you all did to get the other chips going. not sure. whatever makes the most sense to start building kernels and attempting to get it going is fine by me