marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | Not ready for end users / self contained install yet. Soon. | General project discussion | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
bpye has joined #asahi
skipwich has quit [Quit: DISCONNECT]
skipwich has joined #asahi
bpye4 has joined #asahi
skipwich has quit []
rwhitby has joined #asahi
bpye has quit [Ping timeout: 480 seconds]
bpye has joined #asahi
rwhitby has quit []
bpye4 has quit [Ping timeout: 480 seconds]
Dcow_ has joined #asahi
<tpw_rules>
hmm, linux seems to only be starting one cpu
<Glanzmann>
mps: No, just the instructions Alyssa told me how to set up a rootfs. Maybe I should do a video with for the junior kernel devs. https://ab34.de/u/asahi.txt
VinDuv has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
<NightRaven[m]>
I have went to options and then clicked Macintosh HD
<NightRaven[m]>
And then restarts
m42uko has joined #asahi
<j`ey>
I feel like linkerscript for the raw m1n1 needs to ensure that _start is first, or at least at offset 2048..
<NightRaven[m]>
Hmmm
<NightRaven[m]>
It loads just running proxy it is not the drive
<NightRaven[m]>
Then it is m1n1
<NightRaven[m]>
Or kmutil
Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<j`ey>
NightRaven[m]: wait, you should be using build/m1n1.bin, not build/m1n1.macho
<NightRaven[m]>
Ohh so I should use m1n1.bin
<NightRaven[m]>
Not macho
<j`ey>
that should work with --entry-point 2048 --lowest-virtual-address 0
<NightRaven[m]>
j`ey: That breaks my computer
<j`ey>
?
<NightRaven[m]>
just restarts
<NightRaven[m]>
or freezes
<NightRaven[m]>
but should i use the .bin instead of the .macho
<NightRaven[m]>
?
<j`ey>
yes
<NightRaven[m]>
and do the same payload with the .macho to .bin
<NightRaven[m]>
?
<j`ey>
yes
<NightRaven[m]>
oh ok i will try
<NightRaven[m]>
again
<j`ey>
and then use --entry-point 2048 --lowest-virtual-address 0
<NightRaven[m]>
oh ok
<mps>
Glanzmann: ah ok
Dcow has joined #asahi
amarioguy has joined #asahi
<roxfan>
magic incantations
<sven>
:/
<j`ey>
would probably be better to make _start the first symbol and use --entry-point 0
<roxfan>
then you can't use macho container
<j`ey>
seems like the plan is to not do that anyway
<sven>
which will probably be deprecated anyway soonish
<roxfan>
apple loader will be raw binary too?
<j`ey>
yep
<roxfan>
cool
n1c has quit []
wCPO has joined #asahi
<wCPO>
Would it be possible to run x86-64 VMs on Asahi Linux with hardware acceleration? I know the hardware supports x86-64 memory ordering, but can that be used with qemu/KVM?
<roxfan>
not directly, but it could improve binary traslated code performance/correctness
<roxfan>
but qemu would need to be modified to make use of it
Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<wCPO>
Has anyone looked into it?
<tpw_rules>
landscape15[m]: does the keyboard work?
<mps>
reading https://github.com/AsahiLinux/docs/wiki/SW:Linux#running-linux-via-usb-cable I'm not sure do I need first to install m1n1.macho to target machine with kmutil and then run proxyclient/tools/linux.py -b 'earlycon console=ttySAC0,1500000 console=tty0 debug' Image.gz t8103-j293.dtb to debug audio problem and send report
<j`ey>
mps: you just use your normal booting method
<mps>
j`ey: so I don't even need to reboot from current linux on target machine?
<j`ey>
mps: what are you actually trying to do?
<mps>
j`ey: marcan told me yesterday to dump something about audio driver
<j`ey>
that was from m1n1
<mps>
and I think I could try this now
<j`ey>
so you need to do it from the proxy
<j`ey>
you want to get to m1n1, not linux
<mps>
my question is do have to install m1n1.macho on target and run it to test this
<mps>
j`ey: iirc when I installed just m1n1 it boots and stays there waiting
<j`ey>
thats what you want, I guess you currently have m1n1+uboot kmutil'd?
<mps>
currently I have m1n1 kernel and dtb
<j`ey>
oh ok, then yeah, just kmutil m1n1 by itself
<mps>
only m1n1 in macho iiuc
<Glanzmann>
mps: Yes, you have to. Because currently you have a m1n1 that does not wait for the proxy but instead boots linux immedately.
<Glanzmann>
So you boot in 1tr by turning it off and turning it back on again and pressing the power button until you end up with the options menu.
<Glanzmann>
Than you choose options and run a terminal.
<Glanzmann>
Than you can use curl to download a new m1n1. And run kmutil configure-boot -c m1n1.macho -C -v /Volumes/Linux
<Glanzmann>
or whatever you Linux stub partition is called.
<mps>
Glanzmann: yes, I know these things, else I wouldn't have typing from it right now
<mps>
anyway thanks
<Glanzmann>
I see. And than you can run the audio experiment from a second system using m1n1.
Dcow has joined #asahi
<Glanzmann>
I thought that was your question.
<mps>
Glanzmann: no, I just wanted confirmation that I have to install m1n1.macho on target machine and not full payload with m1n1+kernel+dtb (which seems logical)
<Glanzmann>
I see. Yes, you have to. And when you're done with your experiemnt you have to install your old payload.
<Glanzmann>
And soon we have wifi. Hopefully marcan implements it in m1n1, too. So that we can also boot over wifi. :-)
<dottedmag>
wat
<Glanzmann>
just kidding around.
<dottedmag>
wdew
<dottedmag>
*whew
<Glanzmann>
But I assume one day we're able to boot over network on this machines.
<sven>
should already work with a supported usb ethernet dongle and u-boot
<Glanzmann>
sven: I see. Have soemone tried? But then we have no nvme, right because of the nvme shutdown problem? I read the discussion fromt the last 24 hours on -dev. I could not imagine how hard it is to get this NVMe up and running.
<sven>
i'm pretty sure someone has already been booting using that setup, yes
aleasto has quit [Ping timeout: 480 seconds]
the_lanetly_052 has quit [Ping timeout: 480 seconds]
<Glanzmann>
NightRaven[m]: Means your kernel does not have framebuffer compiled in.
<NightRaven[m]>
But like I have done everything thing
<NightRaven[m]>
With the boot args
<Glanzmann>
NightRaven[m]: I had good results with using jannau .config if you want I can also build you a kernel with the asahi branch and jannaus config.
<NightRaven[m]>
Do you think apple made a good move for the kmutil )
<NightRaven[m]>
s/)/?/
<SamAdams[m]>
Ok, so I got to the Debian installer. Which partition should I install Debian to, so Asahi can boot to the debian partition?
<j`ey>
NightRaven[m]: well yes, means we can install!
<Glanzmann>
SamAdams[m]: You need to make space first, once you have done that, you should create a new partition.
<NightRaven[m]>
j`ey: Oh ok
<Glanzmann>
SamAdams[m]: Do be honest, I would skip the whole debian installer thing, and just run debootstrap or extract the testing rootfs it is much faster. The Debian installer might give you trouble, at least it always gives me trouble even if I try to do supported things on supported architectures.
MajorBiscuit has joined #asahi
MajorBiscuit has quit []
<Glanzmann>
marcan / j'ey: I saw that the marcan wifi stream has finished, is there some alpha version we can test?
<NightRaven[m]>
Question do you work for Alpine Linux
<mps>
NightRaven[m]: I'm alpine developer
<NightRaven[m]>
Oooh
<NightRaven[m]>
That's interesting what's it like ?
<mps>
small and simpple distro (though not so small nowadays)
<mps>
most important difference from other famous distro is that is based on musl libc and not glibc
Glanzmann has joined #asahi
<mps>
and no systemd
MajorBiscuit has joined #asahi
<mps>
smells somewhat as bsd on linux
jmr2 has joined #asahi
<jmr2>
marcan: one thing I didn’t catch in the wifi streams: where do you plan to pull the FW files from ?
<jmr2>
I see three options (the “full” MacOS partition, the 1TR partition, and the IPSW used for the stub partition installation - which could be from three different MacOS versions.
<jmr2>
I see some pros & cons for each. Which one are you planning to use?
<j`ey>
IPSW
<j`ey>
since thats what the stub is being built from
<Glanzmann>
jmr2: I think he said he is pulling it from the apple cdn in the beginning.
<Glanzmann>
jmr2: What is IPSW?
<Glanzmann>
jmr2: ^--
<mps>
it is some of brcm drivers, maybe firmware could be downloaded from internet. I did this for old intel macbook
<j`ey>
IPSW is the file format used to hold the macOS update / firmware etc
<jmr2>
Thanks j`ey. That was what I thought made the most sense, but I didn't hear any reference to the IPSW in the parts of the stream that I listened too. Listened too fast...
<j`ey>
jmr2: well there's 10hs to get through.. :P
<jmr2>
lol... There's 24 hours in a day, but still...
<Glanzmann>
j`ey: I see.
<mps>
hmm, maybe I could upload complete kernel tar.gz file to my dev account on alpine. I contains all dtbs, config, modules and vmlinux
<Glanzmann>
j`ey: I see, bummer. Is the reason identified or currently unknown?
<j`ey>
unknown
<Glanzmann>
I see. :-(
<Glanzmann>
Has someone managed to get the corellium wifi driver running with recent kernel? Because I think a few tried (me, alyssa, maybe someone else) and were unable to get it to work. Or is that one broken as well?
<Glanzmann>
Hopefully a good night sleep and few more eyeballs will find the issue.
<tpw_rules>
is the plan on how to install the firmware written anywhere?
<j`ey>
tpw_rules: nope
<j`ey>
tpw_rules: but the installer will handle it
<j`ey>
and if you dont want to use the installer, the script he wrote today makes a tarball with all the firmware, so you can just extract it into the right spot
<tpw_rules>
it's not redistributable though, right
<tpw_rules>
(has he published the script?)
<j`ey>
the firmware isn't, but the script is
<j`ey>
but the script isn't published yet
<tpw_rules>
how will this work for other distro installers?
<sven>
They’ll need to cp -a /boot/firmware /whatever/firmware/
<tpw_rules>
how was it decided that these files aren't redistributable? what about the .ipsw?
<sven>
Why would they be redistributable?
<sven>
They aren’t by default and apple isn’t going to give us a license for them
MajorBiscuit has quit [Quit: WeeChat 3.3]
<tpw_rules>
i guess i haven't really heard of providing firmware being a problem for other wifi cards
<sven>
quite a few vendors specifically grant a redistribution license, see linux-firmware.git
<tpw_rules>
ah ok
Dcow has joined #asahi
<j`ey>
and for the IPSW, that's not being redistributed either, it's downloaded/installed on/by the m1 itself
MajorBiscuit has joined #asahi
<tpw_rules>
landscape15[m]: did you ever get the keyboard working