marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | 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
<marcan>
kettenis_: made the asahi logo stick when booting a kernel (still restores for chainload/HV)
nskl has joined #asahi
nsklaus_ has quit [Ping timeout: 480 seconds]
<amw>
marcan: Is there any place on the Wiki about the new installer? I can't see it
<amw>
I presume it is or will be prefered over a direct kmutil configure-boot
<marcan>
I haven't written docs on it yet, partially because it's not properly deployed yet and I want a few more people in here to try it before we start publicizing it more :)
<marcan>
there are a few things missing like resizing partitions and doing reinstalls properly
<amw>
ok - Do I need a seperate partition already or will it do that
<citizen1[m]>
please add an option for 1 time donations
<marcan>
it will create a partition for you but it won't make space for it
<marcan>
so you need to use diskutil to resize your existing partition to make free space first
<marcan>
(this is a missing feature)
<klange>
<@marcan> jthom[m]: ToaruOS when? (cc klange) <- Can I at least target a raspberry pi or something first...
<marcan>
you think *broadcom* is easier than M1?!
<marcan>
I mean, if you're that much of a masochist...
<klange>
It _is_ better documented, somehow!
<marcan>
also insane :D
<klange>
Yes, if you told me that you've found M1 to be less insane I would believe you without question.
<marcan>
citizen1[m]: I have PayPal, but I try not to advertise it too much because having lots of little one-time donations can make managing taxes/etc a bit of a nightmare
<marcan>
klange: if we ignore DCP, it is one of the saner SoCs I've seen
<marcan>
AIC is stupid simple, the clock stuff is stupid simple, CPU startup is stupid simple, ...
<citizen1[m]>
how about your create a Ko-Fi account?! $1 from a million users is $1Million !
<klange>
(Though really it'll be one of QEMU's virt targets first... and it'll be a long road... and I have so many other things on my plate at the moment...)
<marcan>
citizen1[m]: A million users aren't going to donate :) but I'll consider ko-fi if more people ask for it
<klange>
The one system I found that wasn't a royal pain to set up here was Github Sponsors, which pays out through Stripe and didn't require me to provide a business registration like PayPal wants.
<marcan>
PayPal didn't ask me for a business registration
<marcan>
Patreon pays through Payoneer which also didn't ask for anything weird other than the usual identity verification stuff
<klange>
Patreon was problematic for other reasons... they do not correctly provide or accept documents for US citizens living abroad.
<klange>
Though really I blame the IRS more for that than Patreon themselves.
<marcan>
ah, right, the US is out to screw its foreign residents problem
<marcan>
still can't believe that's a thing
<klange>
Non-resident citizens. Foreign residents would be us in Japan.
<marcan>
yeah, that
<klange>
Though they do also enjoy screwing their foreign residents, but that's a different matter.
<marcan>
I love all the "I swear I'm not a US Person for tax purposes" boxes I have to tick everywhere
<klange>
I can say I do get a couple hundred yen every other month from Github, from a grand total of *checks* one sponsor at the moment.
<klange>
Turns out people only want to sponsor useful OSes!
<citizen1[m]>
i had issues transferring $100 to a guy internationally, they make it so hard thus why now I am starting to believe in Crypto... although i am not a crypto person and do not know how to use it
<amw>
I have a 6 partitions (using the whole disk) iSC, APFS (MacOS), APFS (Asahi), MS basic data LB, ... LR, Recovery : Should I blow away the LR + LB or just make a 3GB space?
<marcan>
amw: assuming LB/LR are not in use yet, just blow them away, you can always recreate them from linux once you do a filesystem install
<marcan>
The APFS asahi partition has a full macos I assume?
<amw>
ok - thanks - Yep
<marcan>
if you don't need to use the hypervisor, you can blow that one away too if you want, and use the installer fresh
<marcan>
I mean HV for macos (HV for linux always works, of course)
<amw>
I'm not sure I'm using the Asahi partition, I think I might be using a APFS volume in the MacOS APFS Container - very confusing
chadmed has joined #asahi
<marcan>
amw: for m1n1?
<marcan>
you might be if you installed macOS onto the same container twice, yeah
<amw>
marcan: Yep - I probably did - just learning about fdisk and gpt commands on the MacOS
<marcan>
you want to use diskutil for everything on macos
<marcan>
(the commandline tool, not the terrible GUI)
<amw>
Still trying to work out how to delete a partition with diskutil :-)
<marcan>
if it's apfs, `apfs deleteContainer`
<amw>
No - the LR/LB FAT ones
<marcan>
I think the manpages suck but the built-in help should tell you
<marcan>
let me check...
<marcan>
amw: diskutil eraseVolume free space disk0sX
<amw>
Yep eraseVolume - thanks - man page is pretty sucky on this !
<kettenis_>
marcan: any particular reason you're not yet trying to push the "syscon" clocks approach yet?
<marcan>
kettenis_: you mean upstream?
<marcan>
amw: what version of macos are you on? and is this macOS or recovery mode?
<marcan>
I set some environment variables to make it find that python lib, which is part of the installer, but maybe whatever OS you're on ignores those?
<kettenis_>
yeah, discussion about DT bindings tends to take a while, so getting things out there early makes some sense
aleasto has quit [Quit: Konversation terminated!]
aleasto has joined #asahi
<marcan>
kettenis_: somewhat busy week is all :)
<amw>
marcan: This is recovery OS - should I be running this from MacOS?
<marcan>
amw: it should work from both, but old recovery OSes were locked down
<marcan>
if you have an ancient version of macOS/recoveryOS it won't work anyway
<marcan>
I've only tested 11.5.2 and 12.0 betas, and I only claim to support 11.4 or newer (we'll eventually require 12.x firmwares anyway)
<amw>
ok - I tried it from MacOS (11.4) and it failed with the same "image not found" error
<marcan>
interesting
<marcan>
look at /tmp/asahi-install/install.sh (which you can just run to try again)
<marcan>
it's supposed to be setting the framework path so python works
<marcan>
I wonder if this is a security thing too..
<marcan>
I always forget that script doesn't put into clipboard, only selection
<pipcet[m]>
oh, reading is hard :-)
<amw>
Nope - nothing like that - I think that mode disappeared a while back for me
<marcan>
amw: I'm confused, what screen are you on?
<marcan>
is this the Boot Recovery Assistant?
<amw>
Options goes straight into macOS Recovery
<marcan>
what's "macOS Recover"?
<marcan>
after you pick options, it's supposed to spin for a bit on a screen that says "macOS Recovery" at the top, then go into the menu I screenshotted
<marcan>
are you getting something else?
<marcan>
amw: can you take a photo/screenshot?
<amw>
Got it but trying to upload it
<pipcet[m]>
marcan: just retried, that instruction never appeared...
<marcan>
I would not be surprised if `shutdown -h now` kills the system before the terminal has a chance to flush its state
<marcan>
did you see a "Press enter to shut down the system." message?
<pipcet[m]>
no
<pipcet[m]>
press enter to continue, then it shut down
<pipcet[m]>
thought that was a bit rude :P
<marcan>
after picking the boot volume?
<pipcet[m]>
yes
<marcan>
print( "Press enter to shut down the system.")
<marcan>
input()
<marcan>
os.system("shutdown -h now")
<marcan>
it's literally that
<marcan>
preceded by the explanation I'm talking about
<marcan>
if you didn't see that message and your system shut down anyway, then you weren't paying attention, because it's literally impossible for the script to call down shutdown -h now *without* printing that message and waiting for a keypress first
<alyssa>
klange: don't forget the famous "I'm revoking my dual US citizenship because it's too much of a tax liability, and they want to charge $5000 for that"
<klange>
Now, now! I'll have none of this hyperbole! It's _only_ $2350!
<amw>
marcan: I believe the system boots to a macOS recovery and you get to choose which one of the recoveries - I think it can run the kmutils from that one you select?
<marcan>
amw: interesting. I haven't seen that before. can you quit it from the top left menu?
<pipcet[m]>
marcan: I see the message in the source code, but I did not see it on the screen
<marcan>
pipcet[m]: and your system shut down (not rebooted)?
aleasto has quit [Quit: Konversation terminated!]
aleasto has joined #asahi
<amw>
Under the apple I gt "startup disk...", Restart or Shut Down
<pipcet[m]>
correct. looks like input() returned right away and i never saw the message?
<marcan>
no offense, but every time the two options have been "something crazy that doesn't make any sense" and "pipcet wasn't following instructions", it's always been the latter
<marcan>
you're going to have to show me a video or something if you want to convince me it's the former
<pipcet[m]>
none taken, I'm sure others will run into this problem :-)
<marcan>
you were also sure the macOS kernel wasn't ARM64 code
<amw>
Choosing "Startup Disk" takes me to another picker
<marcan>
amw: yeah, that won't work
<marcan>
interesting, what happens if you pick the asahi volume?
<marcan>
actually any of them
<marcan>
I guess those are only real macOS installs
<amw>
I can select the Asahi Linux (stub) one
<marcan>
I mean under recovery
<marcan>
not from the boot picker
<marcan>
the startup disk thing won't help you
<kettenis_>
I successfuly switched from "Macintosh HD" to "OpenBSD" using the recovery "Startup Disk" menu option yesterday
<marcan>
kettenis_: that's only once kmutil is done
<kettenis_>
true
<marcan>
I mean it works, it just won't do what you want because at this stage in the install the state is "a macOS kernel with no root filesystem"
<marcan>
which gets you into a bootloop and eventual crash to recovery
<amw>
I can "Quit Startup Disk" to get out of this picker
<marcan>
amw: yeah, go back to the recovery screen and pick a volume
<marcan>
it might not matter which one?
<amw>
Ok - I picked my macOS one and took me to the 1TR (I think) it has the Utilities menu and Terminal....
<marcan>
interesting
<marcan>
wonder what's up with that picker, I've never seen it before, even on the machine with multiple installs
<marcan>
I'll have to update the instructions to account for that
<marcan>
anyway, run Terminal and do the step2.sh thing
<j_ey>
kettenis_: you need an icon next :-)
<amw>
Hmm there is /Volumes/Linux/step2.sh - But there is also a /Volumes/Linux 1 (which doesn't have that!)
<marcan>
hey, I know I called it "Asahi Linux" but I'm not against "Asahi OpenBSD" ;)
<marcan>
amw: yeah, it's random which one's which
<marcan>
since you have two with the same name :)
<marcan>
so you got lucky and it's in the right place
<amw>
ok - bit worried - but hey what could go wrong ....
<marcan>
it'll work, the script itself addresses the OS by UUID, not path
<marcan>
it's just where it gets mounted is random
<maz>
marcan: as long as it isn't 'Asahi MacOS', anything goes.
<marcan>
technically, running macOS under the hypervisor might count...
<j_ey>
marcan: ah, so the Volumes are both Linux, and it's mac OS adding the '1' when it mounts it
<marcan>
yeah
<kettenis_>
heh
<marcan>
kettenis_: seriously though, if you want we can offer openbsd as one of the options in the installer, if you tell me how to set it up FS-wise (for linux I was just thinking of shipping raw FS images and have it auto-expand on first boot)
<kettenis_>
I think what makes most sense is to just have an option to install m1n1 with an U-Boot payload
<kettenis_>
and leave free space on the disk
<marcan>
yeah, we'll have that either way
<marcan>
I'm just going to offer pre baked options for installing a distro/kernel too in one go
<kettenis_>
That is good enough to boot the OpenBSD installer from USB (and maybe network in the future)
<kettenis_>
The OpenBSD installer already knows that it needs to preserve certain Apple partitions
<marcan>
cool
<amw>
ok - I have finished it - see https://paste.debian.net/1209781/ - and it boots into a m1n1 - can't tell the version but it says m1n1 vdb52119
<marcan>
oh, that's the old m1n1, heh
<marcan>
wonder how that happened
<marcan>
ah, but it isn't
<j_ey>
hm, I dont have that in my m1n1 repo..
<j_ey>
that = db52119 sha
<marcan>
it's bd52119
<marcan>
but it's actually version a18033e, it's just our Makefile is a bit dumb here, I should fix that
<marcan>
and update the m1n1 in the installer which is old anyway
<amw>
Hmm on entering MacOS I got "panic... rootvp not authenticated after mounting \n"
<amw>
So is disk3, disk4, disk5 seperate partitions, each a container ?
yuyichao has joined #asahi
<amw>
The 2.5G disk3 (synthesized) is the newly added one I guess, my extra Linux is actually a Volume in disk5 APFS Container - very confusing...
yuyichao has quit [Quit: Konversation terminated!]
<marcan>
amw: you mean you got a crash reporter message?
yuyichao has joined #asahi
<marcan>
that means you tried to boot into m1n1 at least once *before* the step2 thing was complete
<marcan>
which means you tried to boot the stub macOS which doesn't have a root filesystem and so panics :)
<marcan>
that's why I have the installer shutdown instead of reboot, so you can go into recovery and never end up in that messy bootloop
<marcan>
there's a hideous hack in the installer to race the boot picker and kill it before it can reboot the system for that...
<marcan>
updated the m1n1 version tag generation thing
<marcan>
and the installer too, slightly newer version of m1n1 now
<amw>
alls well that ends well ? - I think things are ok now...
<marcan>
yeah :)
<marcan>
and yes the diskN numbering is also random
<marcan>
this is why the installer tries hard to show you an OS list with detailed information about what everything is
<marcan>
because trying to make sense of diskutil output is hell
<amw>
it sure is!
<marcan>
a lot of effort went into that silly little OS list :)
<marcan>
gathering info on all volumes/etc
<marcan>
though I need to add support for multiple OS volumes per container
<marcan>
that isn't really supported now
<marcan>
but it's a thing people can do
<marcan>
thanks for testing!
<maz>
I remember asking this before, but obviously cannot remember the answer: what's the plan for kicking the firestorm CPUs into decent frequencies? I guess this would involve mailbox communication with another core somewhere?
<marcan>
maz: nah, the cpufreq stuff is just a few registers, it's stupid easy
<sven>
iirc it's some magic pokes to magic registers
<marcan>
see the corellium PoC, it's really simple
<maz>
gimegimegime!!!!!
<j_ey>
:3
<marcan>
mostly just need to define sane bindings for this
<marcan>
(since the pstate info comes from the adt)
<marcan>
obviously that driver is silly for multiple reasons (e.g. assuming there is only one pcore cluster, pretty sure that assumption will be void in a couple months)
<marcan>
but the logic is simple enough
<maz>
sven: marcan: awesome, thanks. I'll have a couple of weeks to write something (the joy of a rainy holiday in the UK).
<j_ey>
the only thing that seemed new to me was that the recovery OS can only change the security settings of its paired main OS
<marcan>
correct
<marcan>
you can install asahi without any reboots on 11.x from 1TR, but that stopped working with 12.0, it requires at least one reboot into the new paired rOS
<marcan>
which is a shame, but not worth trying to keep people on 11.x; I'd rather rip off that bandaid and go straight to 12.0 anyway, since we need to pick specific firmware versions and we don't want to get stuck in the past
<marcan>
but the installer does support all those flows right now
<marcan>
this is why the installer does the boot picker *first*, and *then* asks you to go into 1TR and do step2, if you install from macos
<marcan>
since that is required on 12.x (on 11.x you could e.g. just shut down, do the step2 thing and select the next boot volume from there)
<j_ey>
makes more sense now
<marcan>
one thing that text does not mention is that the system recoveryOS *is* going to be the latest version you've ever had installed, since it's part of SFR
<marcan>
so if you've ever had 12.0, it'll be 12.0
<marcan>
but it's still the blessed recovery to downgrade security for 11.x installs
<j_ey>
last sentence of 2nd paragraph mentions that a bit
<j_ey>
just not which version it is
<marcan>
yeah, I mean it isn't mentioned that system rOS is going to be 12.0 on any system with 12.0 installed
<marcan>
you might think it'd be 11.x to pair with 11.x installs, but that's not how it works
chadmed has quit [Quit: Konversation terminated!]
jbowen has quit [Ping timeout: 480 seconds]
<kettenis_>
maz: the MSI controller DT schema in my series makes you the maintainer of the binding since according to MAINTAINERS you're in charge of the generic MSI stuff
<kettenis_>
hope that's ok
jbowen has joined #asahi
<maz>
kettenis_: huh, I sort of missed that. I guess that comes with the territory... :-/
dsrt^ has joined #asahi
jmcneill has joined #asahi
dsrt^ has quit [Ping timeout: 480 seconds]
<jmcneill>
hi folks
<marcan>
welcome :)
<jmcneill>
thanks!
marvin24_ has joined #asahi
marvin24 has quit [Ping timeout: 480 seconds]
jbowen has quit [Ping timeout: 480 seconds]
jbowen has joined #asahi
bps has quit [Ping timeout: 480 seconds]
jbowen has quit [Ping timeout: 480 seconds]
marvin24 has joined #asahi
marvin24_ has quit [Ping timeout: 480 seconds]
jbowen has joined #asahi
jbowen has quit [Remote host closed the connection]
marvin24_ has joined #asahi
marvin24 has quit [Ping timeout: 480 seconds]
jbowen has joined #asahi
aleasto has quit [Quit: Konversation terminated!]
bps has joined #asahi
jbowen has quit [Ping timeout: 480 seconds]
jbowen has joined #asahi
jbowen has quit [Quit: leaving]
<j_ey>
alyssa: moar screenshots!
<alyssa>
j_ey: cat /dev/zero > /dev/fb0
<alyssa>
should display the current state of my monitor :-p