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
<chadmed>
i didnt make an assumption, i asked a question. a question by which i meant no offence. interesting that amw needed to manually remove the synaptics package and install libinput instead if its a dependency in the debian xorg input metapackage
marvin24_ has joined #asahi
marvin24 has quit [Ping timeout: 480 seconds]
off^ has quit [Ping timeout: 480 seconds]
Glanzmann has joined #asahi
<Glanzmann>
amw: Glad that you found that, I add it under tripwires in my text document.
<Glanzmann>
marcan[m]: Wifi is stable on the mini. I ran https://tg.st/u/wifitest.sh for approx 8 hours. No dmesg output, transfer logs are consistent: https://tg.st/u/wifi.log.gz (this was with 2 GHz). As soon as I find out how to use 5 GHZ, I will try that as well.
<Glanzmann>
amw: I'll rewrite the guide to use stable, since there is probably no reason to use testing and you can always ugprade if you need it easily.
<Glanzmann>
amw: I always run echo 'APT::Install-Recommends "false";' > /etc/apt/apt.conf.d/06norecommends # first. This is probably why I did not had the synaptics tocuh pad driver to beginn with.
zimsneexh has quit [Quit: Leaving.]
Major_Biscuit has joined #asahi
Major_Biscuit has quit []
MajorBiscuit has joined #asahi
<rkjnsn[m]>
marcan, are you still looking for folks to test the brcmfmac-do-not-release-d11-resets.patch on other hardware?
<rkjnsn[m]>
Assuming I applied the patch properly (relatively new to NixOS, but it did build a new kernel when I added the patch to my config), I see no change in behavior versus without that patch.
<rkjnsn[m]>
I do see "AXI timeout; APB Bridge 0" coming out of hibernate, but it looks like that happens without the patch, too, so not a regression.
<rkjnsn[m]>
This is a 2015 MBP (Firmware: BCM43602/1 wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8)
sailorek1234 has joined #asahi
<mps>
xorg synaptics driver works for me on alpine, I used it some time because touchpad is too sensitive and can't set touch high/low threshold with libinput driver
<Glanzmann>
Strange.
<Glanzmann>
I'll test it myself later.
<rkjnsn[m]>
FWIW, adding the "Pass PMK in binary" patch also works for me.
joske has joined #asahi
<joske>
hello, been following for a while now and today decided to take the plunge and install asahi
<joske>
I've followed the steps by glanzmann, was able to resize the macOS partition and run the installer
<joske>
however, when in 1TR, when running step2.sh it fails
<j`ey>
ok, if you have the m1n1.bin, you need to run the kmutil command shown there ^
<joske>
ok thx, trying
<joske>
the step2.sh is read only, so I guess I only need to run the kmutil command manually?
<j`ey>
yeah
<joske>
and m1m1.bin from m1m1/build folder?
<j`ey>
yup
<joske>
now kmutil says you must move to medium security (using startup disk)
<joske>
I've set the startup disk to Linux and then got back into 1TR, and now step2.sh works
<joske>
and m1n1 has booted
<j`ey>
joske: step2.sh.. un changed worked or?
<joske>
yes
<j`ey>
joske: in the installer, what macOS stub version did you pick?
<joske>
the default one 12.01 IIRC
<FireFox317>
j`ey, there is no 12.1 IPSW in the asahi-installer yet
<j`ey>
firefox317: ok
<j`ey>
joske: next step is kernel + rootfs or initramfs (or both!)
<FireFox317>
I guess it kinda makes sense it works then, because you will go into the 1TR of the OS stub you just installed, instead of using the systemwide one
<j`ey>
yep
<joske>
trying to run m1n1 shell but python says No module named 'serial.tools'
<joske>
I'm on manjaro, installed serial via pip3 install serial
<joske>
ERROR: Could not find a version that satisfies the requirement serial.tools
<joske>
ERROR: No matching distribution found for serial.tools
<joske>
Defaulting to user installation because normal site-packages is not writeable
<FireFox317>
joske, please use some pastebin next time to show these messages. Im not sure what you are missing here
<joske>
sorry not very used to IRC
<chengsun>
no, serial.tools only provides a binary iirc
<chengsun>
the "serial" package is not what you want, that's completely unrelated
<chengsun>
pyserial provides the "serial" library that you want, and i'm going to guess there's some naming conflict caused by you also installing serial
<FireFox317>
joske, also make sure you are actually using the correct python version, maybe you have to call python3 or whatever
<chengsun>
the wiki instructions don't ask you to pip install serial
<chengsun>
so try uninstalling that
<joske>
yes I saw on stackoverflow
<joske>
YEs! m1n1 prompt :-D
<j`ey>
joske: ^_^
<joske>
now trying to follow the asahi.txt again, trying to chainload m1n1.macho that I built
<joske>
but it gives uart timeout
<joske>
ah I think the notes are wrong
<joske>
should be M1N1DEVICE=/dev/ttyACM0
<FireFox317>
joske, sometimes it gets assigned to ttyACM0 and sometimes to ttyACM1, there is a way in udev to make it consistent tho
<joske>
I've got penguins on my screen!!!1!!
<joske>
but it fails to mount root as I forgot to create the linux partition :-S
Major_Biscuit has joined #asahi
MajorBiscuit has quit [Ping timeout: 480 seconds]
caef^ has joined #asahi
<Glanzmann>
sven: Should I try your NVMe branch or is it not ready for junior developers? :-)
<sven>
Yeah, that branch should be fine to test
<sven>
it’ll
<sven>
it will still have that sync/flush issue
<Glanzmann>
sven: No issue, I'll give it a try. Marcan also mentioned on -dev that he will merge it soon.
<Glanzmann>
joske: If you managed to boot from the usb stick, you can also create the linux partition with parted. That is what I did the last time.
<Glanzmann>
I really have to write a howto and record a video how to install Debian Linux in 10 minutes on a m1 machine.
rose_ has joined #asahi
<joske>
Glanzmann, boot from USB stick?
<joske>
I did not read/understand that from your notes
<amw>
Glanzmann: Thanks for updating your notes. Does the firmware grabging step work on 11.x MacOS ?
<amw>
Thanks my next step - for tomorrow though
<Glanzmann>
amw: I only tried on 12.1 but I send you a message
<amw>
I guess I can tested it for others.... - thanks again.
<marcan>
Redecorating[m]: I have a 4364b3 too on this T2 I'm borrowing, so let's see what I can find
<marcan>
building linux now...
<marcan>
(holy shit these intel machines really are terribad at power consumption... even just idle with an external screen the fans are already annoyingly loud, since I guess that clocks up the GPU?)
<marcan>
amw: it should work on any version
<Glanzmann>
joske: It says in the notes that you should extract the rootfs to a usb stick. Than on your first boot you have to say root=/dev/sda1 or something.
<Glanzmann>
But I'll write a better howto and do a recording
<amw>
marcan: Excellent!
<Glanzmann>
joske: Once you boot from the usb stick you can than use debootstrap. But I'll modify the howto to be simpler and also build a rootfs that you can just dd on your partition. Than you need only one machine and it will be easy to install Linux in 10 minutes or so.
<joske>
Glanzmann, maybe I'm too stupid, but it was not clear to me, I only see root=/dev/nvme... in the notes
<rose_>
hey, i've just been handed this m1 mini which apparently has u-boot and m1n1 on it and been asked to get macos back. i booted into 1tr and clicked the big "install macos big sur" button but once it finished and rebooted it told me "custom kernel failed to boot". apparently u-boot was installed with this guide:
<rose_>
https://wiki.netbsd.org/ports/evbarm/apple/ which seems to use kmutil to configure u-boot instead of the macos kernel - does anyone know how i can fix this and boot macos again?
<Glanzmann>
joske: I did not mention it explicitly.
<Glanzmann>
joske: So the idea in the howto is to get a usb stick, partition it, create an ext4, put the rootfs on it.
<dottedmag>
rose_: Another option to consider: connect to another Mac and use Apple Configurator 2 to wipe it.
<Glanzmann>
Boot once from the usb stick, create an ext4 on the nvme partition and copy rootfs over or run debootstrap.
<Glanzmann>
I'll do this evening a 10 minute quickstart guide for Debian.
<Glanzmann>
And do a video recording of it how to do it.
<rose_>
thanks for the suggestions. i tried bputil -n just now and it "failed to create local policy" which might be something to do with me cancelling the second attempt at reinstalling macos :P
<rose_>
so i'll let it run all the way through this time and try again, and if that doesn't work i'll get the other mac and try the configurator thing
<Redecorating[m]>
marcan: on t2macs you need patches to applesmc + a patched version of mbpfan to get fan control. It makes it quieter, but I doubt it'll be as quiet as m1 macs. There's no harm in not getting fan control, but if you want it, see patches 3001-3006 here https://github.com/aunali1/linux-mbp-arch and https://wiki.t2linux.org/guides/fan/
<FireFox317>
rose_, there is also idevicerestore which let you restore it from linux instead
<joske>
Glanzmann, OMG booted manjaro ARM!! touchpad doesn't seem to work though
<joske>
neither does keyboard
<Glanzmann>
joske: It might be the kernel.
<Glanzmann>
Maybe try the asahi branch instead of the wifi branch.
<Glanzmann>
joske: Which m1 machine do you have?
<joske>
MBA
<marcan>
Redecorating[m]: the fans are automatically scaling properly, and it does this on macOS too
<marcan>
the machines are just bad
<Glanzmann>
Same as me. So I can test.
<joske>
Glanzmann, Ok, first trying to install on NVMe
<marcan>
I disabled applesmc since upstream fails horribly on T2
<Glanzmann>
joske: Btw, I just prepared an ext4 image, that you can disk dump on the partition
<_jannau_>
there's no difference in keyboard/trackpad support between asahi and wifi-take1. Make sure CONFIG_SPI_HID_APPLE and CONFIG_PINCTRL_APPLE_GPIO are set in the kernel config
<Glanzmann>
jannau: I thought so, thank you for the clarification.
<Glanzmann>
It my config CONFIG_SPI_HID_APPLE=m and CONFIG_PINCTRL_APPLE_GPIO=y.
<_jannau_>
that means the keyboard/trackpad will only work once the module is loaded
<Glanzmann>
jannau: I see, so I'll enable it. Thank you for the tip.
<joske>
touchpad/keyboard now work with new kernel config
<rose_>
for those following the macos installation saga the 3rd attempt at reinstalling using 1tr failed after nearly an hour. now onto idevicerestore
<Glanzmann>
rose_: I was able to do it without idevicerestore, but it took 3 - 5 tries until it worked.
<rose_>
using 1tr?
<Glanzmann>
rose_: I lost 1tr and had to recover my macbook air from another m1 machine.
<Glanzmann>
By loosing I mean, I had now idea that the 1tr partition was 1tr and deleted it ... afterwards everything was fine except that I could no longer update macos.
<rose_>
also im quickly realising i dont know what im doing with idevicerestore lol like how do i even plug it in to my laptop
<rose_>
do i use the usb c ports?
<rose_>
okie i plugged in a usb c cable and my laptop sees it on lsusb so im gonna try like this
<Glanzmann>
rose_: I always use the usb ports that are closest to the power on the mini and farer away from me on the macbook air.
<rose_>
nice, that's the one i guessed :D
<rose_>
(from idevicerestore -ln)
<rose_>
ERROR: Unable to discover device mode. Please make sure a device is attached.
<rose_>
i am starting to see this computer as an enemy
<FireFox317>
rose_, you might have to put it in this dfu/recovery mode first?
<rose_>
if i use kmutil to point the bootloader at m1n1, surely i can use kmutil to point the bootloader at macos' kernel? only problem is i don't know where on the disk macos' kernel is
<FireFox317>
im not sure how to do that, since i never did that xd
<rose_>
thanks i'll look into that
<FireFox317>
rose_, well using bputil -n that should work, but that doesnt work right?
<rose_>
after csrutil clear and reboot, csrutil disable gives "failed to create local policy" :(
<FireFox317>
rose_, i guess you dont have the credentials of the machine owner right? in that case i think the only way to restore such a machine would be with with idevicerestore or another mac device
<rose_>
i have the credentials
<rose_>
well, i have the password that it asks for when i run these things, i don't know if there's any other credentials
<rose_>
honestly i'd like to just do it with idevicerestore but even that doesn't want to work
<FireFox317>
oh okay, well im kinda out of ideas xd
<rose_>
oh wait i forgot to try the dfu thing
chadmed has quit [Quit: Konversation terminated!]
<rose_>
ok now the led is amber and idevicerestore sees it (if i run it as root) but it is "unable to discover device type"
<rose_>
fixed by upgrading to idevicerestore master
<FireFox317>
rose_, make sure you have the latest idevice
<FireFox317>
lol
<FireFox317>
yeah exactly
zimsneexh has joined #asahi
Gaspare has joined #asahi
<Glanzmann>
marcan: Using the asahi installer I created a 11.5.2 boot environment. Than it told me the m1n1.macho with the following command line: kmutil configure-boot -c m1.bin --raw --entry-point 2048 --lowest-virtual-address 0 -v /Volumes/Linux
<Glanzmann>
Now it tells me 'custom kernel failed to boot'. Any ideas what I'm doing wrong.
<Glanzmann>
j`ey: I see, thanks. I'll try with the oldest one.
<j`ey>
hm, actually now im unsure, when you have a paired recoveryOS, is it the same version as the stub, or is it the latest version?
<Glanzmann>
j`ey: I think it is the latest version.
<Glanzmann>
But I was able to install a few days asahi. in my macbook air but I used the oldest available version. So now I'm trying and let you know how it went.
<Glanzmann>
I don't want to use the newest due to hdmi not initalizing on the mini.
<mps>
firefox317: but iirc marcan told me that I have to boot with hypervisor if I want to run any of proxy commands
<j`ey>
mps: no, you need to just have a plain m1n1, that doesnt have uboot appended
<mps>
will try later when finish with some alpine packages upgrades
<mps>
j`ey: that is what marcan told me
<mps>
and I trust asahi devs :)
<j`ey>
mps: you misunderstood, you just need to get to the proxy, to be able to run that script, then you can run with or without the hypervisor, but anyway, an smc driver will appear at some point and make all this not needed :P
<joske>
Glanzmann, I now ran the pcie script but still no wifi
<mps>
j`ey: so that means it is not make difference if I boot target with hypervisor or 'bare metal' boot?
<j`ey>
mps: for wifi, no. but you have to currently have a bare m1n1 (aka not m1n1+uboot), to be able to run the python script
<Glanzmann>
joske: Can you post the output of lspci; ip l s; dmesg; find /usr/lib/firmware/brcm somewhere?
yuyichao_ has quit [Ping timeout: 480 seconds]
<j`ey>
Glanzmann: just noticed that you applied the patch to the wrong file, it was for m1n1-raw.ld not m1n1.ld
<mps>
j`ey: aha, thanks. will try to check all this to see do I understand all these
sailorek1234 has quit [Quit: sailorek1234]
<Glanzmann>
j`ey: Fixed, now I get no build errors.
<Glanzmann>
Uploaded +ASSERT(_base + 2048 == _start, "_start must be first!")
<Glanzmann>
Than I'll go with the newest one for now.
<joske>
as soon as I powered my USB C dock, the wifi appeared???
<joske>
so wifi is working if powered?
<FireFox317>
joske, probably be coincidence, shouldnt matter
<joske>
anyway good progress :-)
<joske>
gotta go now, will probably be back later tonight
<Glanzmann>
j`ey: Sorry about the wrong patch apply. Good catch the paste bot stripped the last \n so it was not applying. So I edited manually and did a mistake. This pbot does not strip newlines: https://tg.st/p
<j`ey>
Glanzmann: no worries, I was confused when I downloaded your m1n1 and verified the offsets were right!
<Glanzmann>
joske: For debian it loads the module very early. But you can also manuall load it.
<Glanzmann>
j`ey: :-) I'll now try the latest version.
joske has quit [Ping timeout: 480 seconds]
Gaspare has quit [Quit: Gaspare]
<Glanzmann>
j`ey: I ran the asahi installer again with the newest version and it worked. I have no longer video on the mini, but it worked.
rose_ has quit [Quit: Connection closed]
rose_ has joined #asahi
<rose_>
alright, now idevicerestore makes decent progress, but when the mini reboots, idevice waits for it to enter restore mode so it can continue talking over usb, but this doesn't happen and both sides eventually time out. im getting an apple logo and an empty progress bar on the screen, and after a while the mac falls off lsusb and displays a link to
<rose_>
apple support. idevice tells me to make sure usbmuxd is running, and i have done. why do the gods hate me
<rose_>
hmm, dmesg is showing the mini *dis*connecting twice as "Apple Mobile Device (Recovery Mode)" and once as "Mac mini"
yuyichao_ has joined #asahi
bgb has joined #asahi
Gaspare has joined #asahi
Dcow has joined #asahi
rusty-nail[m] has joined #asahi
joske has joined #asahi
Dcow__ has quit [Ping timeout: 480 seconds]
joske has quit [Ping timeout: 480 seconds]
bgb has quit [Ping timeout: 480 seconds]
leo60228- has joined #asahi
leo60228 has quit [Ping timeout: 480 seconds]
<mps>
how to 'enter' target machine to mode to accept m1n1.macho over usb cable? poweroff it?
<Glanzmann>
mps: You need to kmutil an unmodified m1n1.macho or m1n1.bin
<tpw_rules>
if it's ready it will have the asahi linux logo in the middle and say "Running proxy..." at the bottom
<tpw_rules>
but yes, if m1n1 has u-boot or a kernel appended to it, it will launch that automatically instead of starting the proxy
<Glanzmann>
Than power off, power on. It loads m1n1 and waits, than you can do all the commands using a second linux system conencted via usb cable.
Gaspare has quit [Quit: Gaspare]
<mps>
Glanzmann: ah, so m1n1.macho must be on Linux macos partition (not sure about macos terminology)
<mps>
not possible with currently chailoded m1n1+kernel+dtb
<mps>
I see
<Glanzmann>
mps: No you boot in 1tr.
<Glanzmann>
Than you use curl to download it.
<mps>
Glanzmann: I know these
<Glanzmann>
Than you run the command from the wiki. It will it copy it somewhere.
<Glanzmann>
mps: But it is not possible with the chainloaded.
<Glanzmann>
Because the chainloaded starts immediately
<mps>
just wanted to check I have to add bare m1n1 there, not full chainload
<mps>
I tested all this about two months ago but that vanished from the head and I don't take notes
<Glanzmann>
mps: This always happened to me. Btw. I'm no longer able to install m1n1.macho on 11.x on the mini
<Glanzmann>
It worked a week ago and I have no idea why. So I can't use my mini at the moment with a screen.
<Glanzmann>
Maybe I'm doing something wrong, maybe there was a macos update, don't know.
<mps>
Glanzmann: iirc I had to upgrade to 12.0 to install m1n1 on MBP
<Glanzmann>
mps: On the air I don't have a problem with latest because the monitor works.
<mps>
I prepared cables and other things, just have to upgrade kernel on machine from which I will control target
<mps>
I don't have experience with macos so I don't dare to upgrade to 12.1
rose_ has quit [Quit: Connection closed]
<tpw_rules>
Glanzmann: did you try using the raw command but with the macho file?
<Glanzmann>
No, I did not try.
<Glanzmann>
Should that work?
<Glanzmann>
I only tried the installer for the macho file.
<Glanzmann>
Oh I tried once with a chainloaded kernel which also did not work.
<tpw_rules>
i don't know what that means
<Glanzmann>
tpw_rules: So I'm on the lates macos, I run asahi installer, I choose number 1 (the oldest) I also tried 2 (second oldest). Than I boot in 1tr. Than I get the error that I can't kmutil the m1n1.macho.
<tpw_rules>
maybe you can ignore the error and use kmutil yourself
<Glanzmann>
tpw_rules: I tried that. Did not work.
<tpw_rules>
how did you try it
<Glanzmann>
I thought the command from the wiki, but I will try one more time and report back. Takes a while because I have to do the delete partition free up space dance.
<tpw_rules>
why?
<Glanzmann>
tpw_rules: Because once it did not work I isntalled the latest and greatest.
<Glanzmann>
The one with the hdmi
<tpw_rules>
oh
<Glanzmann>
sorry, without the hdmi.
<Glanzmann>
But, I'll try and report back.
<Glanzmann>
tpw_rules: Btw. I'm working on a guide using your tar trick to dd a debian rootfs. Almost finished, but I'm unable to install m1n1 on the mini (at least not with hdmi)
<tpw_rules>
did you ever see the updated version of it?
<tpw_rules>
i redid it to use uefi and grub
<Glanzmann>
tpw_rules: No, I did not.
<tpw_rules>
theoretically it should be able to boot the debian installer off usb if you know how to build one with the right kernel
<Glanzmann>
I searched for it today but was unable to find it, can you send me the link please.
<Glanzmann>
tpw_rules: I see, this is why could not find it. I wrote down the url now. And took a backup just to be sure.
<tpw_rules>
the old ones are still in the git history. but i'm not sure a backup is great because this all changes pretty quickly.
<tpw_rules>
i mean the trick is basically that if you have a .tar.gz with one file which is your rootfs image, you can use tar -xO to extract it in recoveryOS
<Glanzmann>
chromium on Debian stable on m1 just segfaults, interesting.
<mps>
Glanzmann: also on alpine
<zimsneexh>
The segfault has to do with pagesize, afaik
<Glanzmann>
jannau: On Debian stable the touchpad and keyboard works. But the middle and right click does no longer work: 2 finger click (right) and 3 finger click (middle) if multitouch is working - any idea what I need to do to enable multitouch?
<Glanzmann>
zimsneexh: I see.
<Glanzmann>
tpw_rules: About the mini and m1n1. Which version did you choose in the asahi installer?
<tpw_rules>
currently i'm using 11.4. but i never installed 12.1
<Glanzmann>
Oh I see.
<zimsneexh>
With 12.1 you need the --raw flag, you are using the .bin file instead of the .macho right?
<tpw_rules>
like i said i think if you are using 12.1 with an 11.4 stub, you might be able to use --raw and the macho
<zimsneexh>
Doesn't that depend on the version of 1tr instead of the stub version?
<mps>
got wifi in lspci out and module loaded but dmesg says it can't find firmware though I installed firmware but kernel tries to load some other files
<mps>
do anyone have firmware tar for MBP
<jannau>
Glanzmann: that might depend on the libinput configuration. does right click by clicking in lower right part of the touchpad work?
<mps>
created symlinks for missed firmware and now 'modprobe brcmfmac' loads them but I see this in dmesg: [ 952.204243] brcmfmac 0000:01:00.0: brcmf_pcie_download_fw_nvram: FW failed to initialize
<SamAdams[m]>
On Ubuntu 22.04 Daily Build, the touchpad is working great! I can even swipe through the gnome workspaces with the 3 finger swipe, scrolling works great, and tap to click is even supported! It's actually very responsive. Pinching to zoom is more responsive than Mac OS!
thasti has joined #asahi
<kettenis>
mps: does it do that on every boot?
<mps>
kettenis: tried just two times
<mps>
marcan: you asked me about week ago to send dump from tools/dump_pmgr.py, here it is in case you still need it https://tpaste.us/8Ea8
<mps>
kettenis: tried boot once more but same result
Gaspare has joined #asahi
Major_Biscuit has quit []
<Glanzmann>
jannau: I see. It seems to always do the same no matter where I click. I'm on debian stable maybe I update to testing.
<Glanzmann>
SamAdams[m]: For me scrolling, left, middle and right click was working on Debian Testing out of the box as well in fvwm2
MajorBiscuit has joined #asahi
<Glanzmann>
Can someone talk me through how I downgrade my mac mini to 11.x?
<zimsneexh>
Glanzmann: I assume you could do that with idevicerestore?
<Glanzmann>
zimsneexh: I have all the usb cables and devices, but never used idevicerestore before.
Gaspare has quit [Quit: Gaspare]
nobodynada has joined #asahi
nobodynada has quit [Quit: Lost terminal]
<Glanzmann>
zimsneexh: What m1 device do you have? Wifi is working for you with 5 Ghz, correct?
<marcan>
zimsneexh: it depends on both
<marcan>
kmutil in 12.1 will let you use --raw and then 11.4 iBoot will load it as a macho
<marcan>
mps: you shouldn't need to symlink any firmwares, if you do something is wrong
<Glanzmann>
marcan: regading kmutil, does that mean I can kmutil --raw the macho file and than it will boot in 11.4 partition?
<marcan>
I think so
<marcan>
I'm not sure if anyone has tried it yet
<Glanzmann>
I'll try it and report back.
<marcan>
anyway, I don't know why people keep using 11.4 stubs? just use 12.0 beta8, that one should work on the mac mini with HDMI and won't have problems with kmutil
<Glanzmann>
marcan: I'll try that.
<marcan>
I really want people to stop using 11.x, it's going to be deprecated soon enough and the only reason I haven't nuked it from the installer is that 12.0.1 has the stupid HDMI problem left to solve
<marcan>
the system recovery mismatch stuff is just one of many problems with 11.x
<marcan>
it was a rushed release and Apple fixed a ton of stuff for 12.x
<mps>
marcan: I followed your guide only. Also Glanzmann told me that on his machine have same problem
joske has joined #asahi
<Glanzmann>
marcan: I also send mps my firmware dump, same content. But to be honest on my air I only tried once, and I copied the firmware after the boot and unloaded and loadded the module.
<marcan>
so do you know what firmware is supposedly missing? that's more useful to know than "I symlinked something" :p
<Glanzmann>
I also have not figured out how to use 5 Ghz on the mini. But the 2 GHZ is rock stable. 9 hour endless loop burst transfers in both directions.
<mps>
marcan: I will look tomorrow again and post list of symlinks I made