<ElvishJerricco[m]>
I'm assuming that in the Asahi installer, "step2" refers to all the work that needs to be done in the recovery OS, right? If so, is it just the `step2.sh` script? None of the python stuff or any downloading or anything?
lgarylmtdlt^ has joined #asahi
artemist has quit [Quit: artemist]
artemist has joined #asahi
phiologe has joined #asahi
PhilippvK has quit [Ping timeout: 480 seconds]
lgarylmtdlt^ has quit [Remote host closed the connection]
marvin24_ has joined #asahi
artemist has quit [Quit: artemist]
marvin24 has quit [Ping timeout: 480 seconds]
hspak has quit []
hspak has joined #asahi
kov has quit [Quit: Coyote finally caught me]
hromwoomit^ has joined #asahi
Bai-Chiang has quit [Ping timeout: 480 seconds]
artemist has joined #asahi
nicolas17 has quit [Quit: Konversation terminated!]
<marcan>
correct
xfim has joined #asahi
<ElvishJerricco[m]>
marcan: Cool. Out of curiosity, how does the Finish Installation app get started? Is it something about that IAPhysicalMedia thing?
Ry_Darcy has joined #asahi
<ElvishJerricco[m]>
Also, is Rust nightly still needed to build m1n1 with chainloading, or is a sufficiently recent stable release enough?
<marcan>
yes, the IAPhysicalMedia thing tells it it's something like a USB installer (except it's just on the internal partition)
<marcan>
then when you boot that volume it instead goes into recovery mode and opens that app bundle
<marcan>
ElvishJerricco[m]: you need nightly
<marcan>
freestanding rust in practice still requires some features that stable doesn't have, no idea when they will finally make it
<ElvishJerricco[m]>
That is a very interesting way to accomplish that :)
<marcan>
much better than the old "go into recovery, pull up a terminal, and run this command" way ;)
<ElvishJerricco[m]>
Hm nightly will likely prevent me from packaging the installer in nixpkgs, as it doesn't have nightly. That's too bad. But at least I can have a separate Nix expression for it I guess
<ElvishJerricco[m]>
Well... never mind that. Apparently nixpkgs packages a number of things that require a nightly compiler, so they just set `RUSTC_BOOTSTRAP=1`, which apparently causes `rustc` to behave like a nightly compiler. Gross, but I can use it :P
<nico_32>
ElvishJerricco[m]: check if the compiler was called with -ffreestanding
<ElvishJerricco[m]>
nico_32: I assume it must've been, since that's in the default CFLAGS in the Makefile. But Nixpkgs does wrap the compiler to mess with the flags a bit... maybe it's removing that for some reason
hromwoomit^ has quit [Ping timeout: 480 seconds]
<ElvishJerricco[m]>
Looks like nixpkgs is adding a whole bunch of includes and stuff after. I can try an unwrapped clang
<ElvishJerricco[m]>
nico_32: I hadn't even seen that. Sounds like they had a completely different problem with macOS and got much further. Interesting
<nico_32>
it was before the addition of rust code in m1n1
<nico_32>
that's why I called it "ancient"
xfim has quit [Ping timeout: 480 seconds]
<ElvishJerricco[m]>
Well even with a nix expression that's virtually identical to theirs, I still get my errors instead of theirs. Might have to bisect... But I'll leave that for tomorrow
the_lanetly_052 has joined #asahi
<jannau>
ElvishJerricco[m]: `make -n` output after the error would be interesting since it prints the full compile command
<ElvishJerricco[m]>
wtf. Adding `-n` to the make command made the build work?
<ElvishJerricco[m]>
Literally the exact same nix expression, except one has `buildFlags = [... "-n"];`, and the "-n" one works
<jannau>
no, '-n' does nothing but printing the commands
<ElvishJerricco[m]>
I know. That's why this is weird
<ElvishJerricco[m]>
`buildFlags` are just passed to `make`, nothing else
<j`ey>
nix is bad!!
<nico_32>
race condition somewhere?
<jannau>
it does not build anything
<j`ey>
-n == --dry-run
<ElvishJerricco[m]>
Oh I see
<ElvishJerricco[m]>
Sorry, brain is not functioning this late at night :P
<j`ey>
it's 9am!
<nico_32>
it is always 9am somewhere :)
<ElvishJerricco[m]>
Well anyway the commands with `-n` look right to me. Issue seems to just be that nixpkgs adds a ton of includes args *after* all the args provided by the Makefile
<ElvishJerricco[m]>
But apparently some of them are needed because I get no such file errors if I use an unwrapped compiler
<ElvishJerricco[m]>
But now is sleep time
<j`ey>
probably related to -isystem $(shell $(CC) -print-file-name=include)
hromwoomit^ has joined #asahi
hromwoomit^ has quit [Remote host closed the connection]
jluthra has quit [Remote host closed the connection]
jluthra has joined #asahi
Ry_Darcy has quit [Remote host closed the connection]
<holyspirit[m]>
i hope you appreciate gentoo is the holyspirits software
<mps>
hehe, no it is alpine :D
<mps>
sorry for OT
MajorBiscuit has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #asahi
MajorBiscuit has quit [Ping timeout: 480 seconds]
the_lanetly_052 has quit [Ping timeout: 480 seconds]
<mps>
is there a way to get serial console on macbooks m1
<mps>
ttySAC0 and ttySAC1 are detected by linux
<j`ey>
mps: only with special uart hw
<j`ey>
or another m1, or use m1n1 hypervisor
<mps>
j`ey: it is active in m1n1 and visible on any other machine
<j`ey>
yup
<mps>
j`ey: by 'another m1' you mean another m1 running macos
<j`ey>
the other m1 can run linux I think
<mps>
ah nice, could check that
<j`ey>
or actually that might not be possible yet
<mps>
will check in few minutes
<jannau>
uart should work between two bare-metal m1 devices with linux, resetting via usb-pd is not possible under linux yet
<mps>
jannau: what it should be on 'client' machine ttySx or ttySACx
roxfan has joined #asahi
<jannau>
both ttySAC0, not sure how the usb ports like it
<mps>
hmm, doesn't work
the_lanetly_052 has joined #asahi
<mps>
maybe need to enable some usb drivers
<sven>
the m1-to-m1 uart does not use any usb drivers
<sven>
you do need to configure both usb pd controllers to that serial mode which can only be done from macOS for now and doesn’t stick after a reboot
<sven>
and you must use a usb c cable that actually connects the required lines
<sven>
probably easier to just use the emulated uart under the hv fwiw
<mps>
sven: thanks for explanation.
Gaspare has joined #asahi
Bai-Chiang has joined #asahi
bps has joined #asahi
bps has quit [Ping timeout: 480 seconds]
Gaspare has quit [Quit: Gaspare]
Gaspare has joined #asahi
<jannau>
I've assumed m1n1's init might be enough
xfim has joined #asahi
Gaspare has quit [Quit: Gaspare]
bps has joined #asahi
Gaspare has joined #asahi
<sven>
nope
<sven>
we could send the commands via i2c from m1n1 though
<sven>
macvdmtool switches modes on both sides fwiw
bps has quit [Ping timeout: 480 seconds]
<jannau>
I forgot that vdmtool does it on connect
dost^ has joined #asahi
Gaspare has quit [Quit: Gaspare]
xfim has quit [Ping timeout: 480 seconds]
linearcannon has quit [Ping timeout: 480 seconds]
dost^ has quit [Ping timeout: 480 seconds]
Tramtrist has left #asahi [#asahi]
<weapon_of_nix[m]>
i edited my fstab and broke booting. can i edit the asahi filesystem from mac? i can't seem to get into any kind of interactive terminal on the asahi boot
<SorunomeLuckySkies[m]>
if it is the fstab being broken, shouldn't you just be dropped into a busybox shell by initramfs so that you can fix it?
<tpw_rules>
no, this is macos
<tpw_rules>
and the apple silicon macs are completely helpless without an intact partition table and firmware partitions
<j`ey>
SorunomeLuckySkies[m] was talking about an earlier question from weapon_of_nix[m]
<tpw_rules>
oh
dost^ has joined #asahi
MajorBiscuit has joined #asahi
MajorBiscuit has quit [Quit: WeeChat 3.4]
MajorBiscuit has joined #asahi
xfim_ has quit [Ping timeout: 480 seconds]
<Sobek[m]>
What’s the equivalent of the sad SOS blink pattern for laptops (that don’t have a led but do have a screen AFAIK) ,
<Sobek[m]>
?
<marcan>
tpw_rules: did you try the tap-release-hold boot gesture?
<j`ey>
Sobek[m]: maybe just a sad face on the screen
<marcan>
it's supposed to tell you to restore as long as iBoot1 is intact
<marcan>
the Mac Mini used to do that too until Apple decided to nuke the display output altogether and replace it with the SOS thing...
<j`ey>
(For Reasons Unknown)
<marcan>
I heard a rumor that it was because it only worked over HDMI... so instead of, you know, making it also work over TB/DP, they just made it not work over anything, because that's consistent!
<tpw_rules>
marcan: can you elaborate on that gesture?
<marcan>
instead of holding, tap and hold
<marcan>
it should boot alternate/system recovery
<tpw_rules>
when do i press it again relative to the light turning on
<marcan>
quickly
<tpw_rules>
if i press it when the light is about half-bright it starts doing the SOS in the middle of the boot chime. i feel like that is it failing to start the system recovery
<marcan>
just a quick tap and hold, like all within 0.5s
<tpw_rules>
(the alternate is the light doesn't start flashing until the boot chime is finished)
<marcan>
then it might be properly borked, yeah
<tpw_rules>
i got idevicerestore to boot it to an apple logo with an empty progress bar, but after a couple minutes it just resets while idevicerestore says it is waiting to reconnect in recovery mode
<marcan>
make sure your usbmuxd is up to date
<marcan>
and the udev rules
<marcan>
you basically need git everythingt
<marcan>
*everything
<marcan>
I see that wasnot mentioned in the instructions, that's an omission
<marcan>
*was not
<tpw_rules>
does it need extra udev rules if i run it with sudo?
<marcan>
the udev rules are to launch/trigger usbmuxd on the right devices
<tpw_rules>
oh, i didn't realize usbmuxd was a separate process
<marcan>
it is
<marcan>
(also I wrote it, *ages* ago lol)
<tpw_rules>
so that makes sense, it doesn't use usbmuxd until then
<marcan>
yup
<tpw_rules>
what instructions are you referring to?
<marcan>
I need to get some sleep but hopefully that gets you on the right track
<marcan>
the .txt above
<tpw_rules>
ah. well if i can't figure it out i'll just use apple configurator. i didn't do this deliberately, but it's a good opportunity to make sure the instructions do actually work
<weapon_of_nix[m]>
<j`ey> "Sorunome ⚡️ Lucky Skies was..." <- no i just added a ramdisk but i suppose i did it wrong. now at boot it says bad mount point or something, i've forgotten the exact error. i just need to edit that line out of fstab and i should be dandy
<weapon_of_nix[m]>
on another note why is adding a ramdisk so complicated. i followed 3 different guides and none work 😥
<j`ey>
weapon_of_nix[m]: but do you get to a shell?
<weapon_of_nix[m]>
j`ey: it has text that implies i should be able to run some commands but all it says is press enter to try again
<j`ey>
are you sure it's not asking for a root password?
<weapon_of_nix[m]>
is there some key combination i can use to get into a terminal?
Major_Biscuit has joined #asahi
<j`ey>
oh.. the root account is locked... hm
rin20xx has joined #asahi
MajorBiscuit has quit [Ping timeout: 480 seconds]
<rin20xx>
heyo, im a long time lurker but this is my first time actually logging into the irc
<j`ey>
seems like thats when your root account doesnt have a password
<rin20xx>
trying to figure out what exactly i broke linux-side with headphone jack output audio on my base M1 Mac Mini
eroc1990 has joined #asahi
<weapon_of_nix[m]>
rin20xx: it's very flakey to begin with. better support will be coming out
<j`ey>
weapon_of_nix[m]: you can reboot and try adding 'init=/bin/sh' to your command line in grub
<rin20xx>
yeah ik, but after updating my arch-linux install earlier today, I lost any audio output whatsoever, when before (on a much older install, back from when the first alpha build released as i haven't booted into linux for a while) im pretty sure I had headphone jack output support?
<j`ey>
rin20xx: have you rebooted? its flakey so try rebooting
Major_Biscuit has quit []
<rin20xx>
tried rebooting twice; ill see if rebooting w.o my speakers plugged into the headphone jack works once i plug 'em back in in a bit
<rin20xx>
rebooted twice with the speakers plugged in, didnt work
<rin20xx>
rebooted with them *not* plugged in, haha! it works now!
<rin20xx>
flakey indeed
rin20xx has quit []
Polo has joined #asahi
<weapon_of_nix[m]>
<rin20xx> "rebooted with them *not* plugged..." <- btw something marcan suggested regarding video playback that has fixed these issues for me is toggling sound off and then back on
<Polo>
YOU
<weapon_of_nix[m]>
<j`ey> "weapon_of_nix: you can reboot..." <- how do i enter that into grub? i tried cancelling autoboot and typing it but nothing seems to have happened
dost^ has quit [Ping timeout: 480 seconds]
<psykose>
some cmdline setting, add it to the end
<weapon_of_nix[m]>
end of what
<psykose>
i.e. you see a `linux /something x=y a=b`, that line
<weapon_of_nix[m]>
i don't see anywhere to type it except the interactive command line that exists prior to autoboot
<weapon_of_nix[m]>
once the grub menu appears i only have two options, both which boot to that error stream i posted a photo of
<psykose>
on the list of things that has the timeout you can hit e to edit the option
<psykose>
if not that, no idea
<weapon_of_nix[m]>
oh yes i see that now
<weapon_of_nix[m]>
how do i save
<weapon_of_nix[m]>
i pressed control-x after making the edit but nothing has changed
derzahl has joined #asahi
Polo has quit [Ping timeout: 480 seconds]
<derzahl>
sweet...FINALLY got chromium working :D
<derzahl>
and even compiled with apple-m1 cpu optimiations