#
…

2022-01-17

00:45user982492 has joined #asahi
00:50user982492 has quit []
00:51user982492 has joined #asahi
02:00hays has quit []
02:02marcanlol, I didn't expect 1920x2160 to be a thing
02:03hays has joined #asahi
02:31user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
02:39user982492 has joined #asahi
02:55user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
03:09Dcow has joined #asahi
03:17Dcow has quit [Quit: Dcow]
03:28user982492 has joined #asahi
03:30PhilippvK has joined #asahi
03:33phiologe has quit [Ping timeout: 480 seconds]
03:34kov has quit [Quit: Coyote finally caught me]
03:34kov has joined #asahi
03:43kit_ty_kate1Glanzmann: a video guide would be really awesome to have for sure imo
03:53darkapex2 has joined #asahi
03:58darkapex1 has quit [Ping timeout: 480 seconds]
04:20anparra[m] has joined #asahi
04:53marvin24_ has joined #asahi
04:55marcanjannau: thanks for the testing :)
04:55marcanI think iBoot has a ~5 second timeout, judging by how long it used to take extra to boot the Mini without a display
04:55marcanbut we probably don't want to delay that long, it always felt like overkill
04:57marvin24 has quit [Ping timeout: 480 seconds]
04:58user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
05:28user982492 has joined #asahi
05:55torstenvl has joined #asahi
07:32jeffmiw has quit [Ping timeout: 480 seconds]
07:32Glanzmannkit_ty_kate1: I'll make one.
07:32Glanzmannkit_ty_kate1: But I'm also thinking of modifying the debian installer that it just works.
07:32GlanzmannBecause then this would be close to the final state marcan wants anyway.
07:56VinDuvI did a test of jannau's branch on my 1080p monitor. It now lights up, but says “no signal” and goes back to sleep. I’ll get the serial output in a few hours.
08:11nzzz is now known as z
08:11z has quit [Remote host closed the connection]
08:12jannauVinDuv: did that monitor work with macos 11 iboot? does it work after a chainload?
08:13nzzz has joined #asahi
08:23VinDuvjannau: I never had a chance to try the old iBoot, unfortunately. (When I got the mini, 12.0.1 was already out and I installed it right away). Will try the chainload later.
08:25VinDuv(I always had some odd issues with that monitor so I wouldn’t be surprised if it didn’t work…)
08:29MajorBiscuit has joined #asahi
09:26aleasto has joined #asahi
10:03landscape15[m]VinDuv: I think you can do a full DFU to downgrade to Big Sur, since the ipsw is still signed.
10:03landscape15[m]* full DFU restore to downgrade
10:36darkapex has joined #asahi
10:36darkapex2 has quit [Remote host closed the connection]
10:37_jannau_downloading the big sur installer from the app store and create installer medium also works
10:40darkapex1 has joined #asahi
10:44darkapex has quit [Ping timeout: 480 seconds]
10:56landscape15[m]I don’t think it works. With Intel macs you can’t install a previous macOS version than the one the Mac is shipped with, even from an external USB, because it doesn’t downgrade the EFI firmware.
10:57landscape15[m]But I don’t know how it works on Apple Silicon. I’m sure with a DFU restore, also the original firmware is restored.
11:07VinDuvI actually installed 11 on the mini after the fact (via USB), but I don’t thing that downgraded iBoot
11:07_jannau_landscape15[m]: it works, I've done it
11:07VinDuv(I mean with the 11 installer on a USB stick, not the DFU restore)
11:08ChristianvonElm[m] has joined #asahi
11:08_jannau_VinDuv: there is a installtion specific iboot stage that initializes the display even with the system iboot is already based on macos 12
11:10_jannau_but I don't think it's worth to spend any effort on macos 11. The minimal supported version will be macos 12.1 now that mini hdmi blocker has been mostly resolved
11:11mpsI made kernel patch on top of asahi which add nice 12x24 bold terminus fonts on console, looks fine on MBP
11:13landscape15[m]jannau: good to know, thanks.
11:13ChristianvonElm[m]sorry if that is a total noob mistake, but im trying to boot the Linux Kernel according to the SW:Linux guide in the Wiki but I'm getting a "VFS cannot open root device "(null)" or unknown block (0,0): error -6" error, can anyone help me?
11:15mpsChristianvonElm[m]: you have to pass kernel cmdline params with root=whatever, I guess
11:16mps'whatever' is actual root filesystem
11:19landscape15[m]Christian von Elm: you can directly add the parameter inside the kernel config if you want
11:24rkjnsn[m]marcan: Re iBoot waiting ~5 seconds, did it support displays attached via Thunderbolt, or just HDMI? I've had a Tunderbolt→dock→HDMI→monitor setup before that always took a few extra seconds for the display to come up versus a direct HDMI connection.
11:29user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
11:43user982492 has joined #asahi
11:43torstenvl has quit [Remote host closed the connection]
11:44torstenvl has joined #asahi
11:49VinDuvGot the logs for my 1080p monitor: https://paste.debian.net/hidden/b4bb9fcd/ (both cold boot and chainload; when chainloading, the screens powers up briefly as well)
11:52torstenvl has quit [Ping timeout: 480 seconds]
11:54marcanrkjnsn[m]: just HDMI, it has never supported dispext
11:54marcanif you were using a TB monitor, that was never working until macos loads the DCP driver
11:55marcanwhich is now the state of affairs for everyone
11:56marcanlandscape15[m]: booting 11.x macos from 12.x firmware works, because the 11.x DCP/iBoot2 will initialize the display (just a bit later)
11:56marcanyou don't get the apple logo though, which is hilarious - just a progress bar until DCP loads
11:57marcanyou can install m1n1 on that, except for the kmutil issue if you have 12.1 firmware
11:57marcanwhich is another reason why I wanted to get this mess over with asap
11:57marcanI don't want people to waste time making workarounds for older versions
11:58marcanit all ends up wasted work in the long term, and it's not helping anyone in the short term because we're not at the point where we desperately need wider testing
12:06landscape15[m]marcan: thanks. Does this mean that the latest firmware is backward compatible with old macOS versions? If yes, then this could change in the future and Linux can be installed only if you have the latest macOS version installed.
12:14kovmarcan, I've noticed you use a tool called areset if I'm not mistaken to power cycle on the streams, is that something custom?
12:14j`ey*areboot
12:15kovareboot that's it
12:15kovwondering if that is something I can use or if it would require some kind of special hardware
12:15j`eykov: pretty sure its using https://github.com/AsahiLinux/vdmtool which only works if you have the hardware uart thing
12:16kovah I see
12:17kovj`ey, nice, that may help me actually =) thank you!
12:19kovjannau, aha, thank you!
12:20j`eykov: I used the m1n1 hv usually, works well to reboot
12:35ChristianvonElm[m] has left #asahi [#asahi]
12:41VinDuvRebuilt m1n1 with RTKIT_SYSLOG enabled: https://paste.debian.net/hidden/2c8254dc/ It looks like DCP doesn’t like something about my monitor?
12:58kovj`ey, heh, macvdmtool worked after I *ahem* used the DFU port on the controlling m1
12:59j`eykov: yay :)
13:04marcanlandscape15[m]: the system is designed to be backwards compatible
13:04marcanwe only care that you have at least the minimum required version or newer for the installer to work
13:46torstenvl has joined #asahi
13:54torstenvl has quit [Ping timeout: 480 seconds]
14:45yuyichao has quit [Ping timeout: 480 seconds]
15:12yuyichao has joined #asahi
15:17kovGlanzmann, I followed your u-boot guide (thank you for the guides!), except I installed the system with d-i and I'm booting the m1n1-uboot bundle with m1n1's chainload, are any of those expected to be a problem?
15:18kovu-boot runs, finds the bootaa64.efi file, but then it errors out with a bunch of Invalid Parameter errors
15:32Glanzmannkov: I've seen that exact error before, but I have no glue where it comes from.
15:33Glanzmannkov: What worked for me is, that I dd'ed a 'efi' parition from my macbook air over.
15:33GlanzmannHowever grub-install should make it bootable, and it did before, but it does not seem to.
15:33Glanzmannkov: How were you able to boot the debian installer with an updated kernel?
15:34kovGlanzmann, I used the initrd trick, got the initrd and bundled it with the m1n1 and the kernel
15:35Glanzmannkov: Okay, what I don't get when I did this the first time, I ran grub-install --removable /path/to/device and it worked.
15:35GlanzmannNow that does not seem to work anymore and I don't know why.
15:35kovd-i works well, you only need to tell it you're ok with not loading modules and it won't install grub of course =)
15:36kovGlanzmann, weird
15:36Glanzmannkov: I see. But you should be able to install grub manually from the installer seperate window.
15:37kovI wonder if I can just mount and copy the files from the main EFI partition over... hmm
15:37Glanzmannkov: I'll try it again later tonight and see if I can figure it out. If you find the reason, please ping me in irc.
15:37kovGlanzmann, will do, thanks!
15:37Glanzmannkov: Just to be clear you run the installer by using the netboot linux kernel and initrd and said not to load modules?
15:38GlanzmannSo a self compiled linux kernel and the initrd from the installer?
15:38kovGlanzmann, I use a custom built kernel and the d-i initrd yeah
15:38GlanzmannAnd that's it and than you we're able to install?
15:38Glanzmannkov: Did you run that using m1n1 or did you build an ISO that you dded on a usb stick?
15:39kovI think the only 2 non-usual dialogs I see are it asking if I want to continue without loading modules and then that it did not install grub
15:39kovGlanzmann, oh, I ran the asahi installer first yeah
15:39kovso m1n1, custom kernel, d-i initrd
15:39user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:40_jannau_kov: the debian installer seems now to refuse to run if the kernel doesn't match its modules, even when the kernel has everything built-in
15:41Glanzmannjannau: I found a website which says it installs fine if you say no to the kernel, install the custom kernel yourself after the installation finished and install grub.
15:41GlanzmannI was about to paste the debian wiki page where this is documented, but I have not written it down apparantly.
15:41kovGlanzmann, how did you get the EFI image out of the macbook?
15:42_jannau_Glanzmann: I tried it with the network installer and the installer itself will will not advance
15:42kov_jannau_, weird, was that with the latest stable?
15:43Glanzmannkov: So I have an air which has a working grub efi partition.
15:43kovGlanzmann, oh I see
15:43GlanzmannI dded that of the macbook air and dded that onto the mac mini and it booted.
15:43kovGlanzmann, would you mind sharing the image?
15:43kovI'll see if I can figure out what's different
15:43GlanzmannOnce booted, I tried to do a proper installation using grub-install as I have done on the air before, and I get the exact same error you see. No idea why.
15:44kovI wonder if it's different grub version
15:44GlanzmannThe dd is here: It requires a 1 GB partition to dd it on. YOu can do it from macos or Linux.
15:44kovI was thinking of trying to downgrade it
15:44kovwill do it later today
15:44kovGlanzmann, thank you!
15:45GlanzmannIf you find anything out, let me know, I'll do the same.
15:45kovGlanzmann, 404 here
15:45GlanzmannWe're once inch away from making the debian installer work.
15:45kovlooking forward to that!
15:45Glanzmann/u/ was missing, as I always forget to add it.
15:45_jannau_kov: debian stable aarch64 network installer from last autumn
15:45kovGlanzmann, worked, thanks!
15:47torstenvl has joined #asahi
15:49kovhmm first differences that catch my eye are debian vs BOOT and ubootefi.var, but I wonder if that is put there by u-boot after itself?
15:52Glanzmannyou need boot.
15:52GlanzmannIf you don't have boot, u-boot does not pick it up.
15:52kovwell copying your EFI files over makes it work
15:53Glanzmannthat is what grub-install --removable or the dpkg-reconfigure grub-efi-arm64 does.
15:53kovGlanzmann, what, sorry?
15:54h_ has joined #asahi
15:54Glanzmannefivars is new. Some grub utility creates it, but to my knowledge you don't need it.
15:54GlanzmannYou just need this one binary: EFI/BOOT/BOOTAA64.EFI
15:55hays has quit [Ping timeout: 480 seconds]
15:55torstenvl has quit [Ping timeout: 480 seconds]
15:57kovyeah so I removed everything and kept only the BOOTAA64.EFI and grubaa64.efi files from your image and grub is started
15:58kovso I think it's indeed very likely a problem caused by a newer grub version, I'll try with an older one and let you know Glanzmann
15:59ketteniskov: regarding that u-boot fix you mentioned, that may indeed not be present in the version of u-boot you're using
15:59mpsI have no idea how any distro could make installer because of firmware licensing problem
15:59kovkettenis, it isn't, you think that may be the problem?
16:00kettenisas it is based on u-boot master from roughly a year ago
16:00Glanzmannkov: Thanks. Yes, I saw that grub was recently updated in testing.
16:00kovI'll look into that possibility as well
16:04ketteniskov: I don't know; but I'm upstreaming things and I'll probably create a branch based on current u-boot master soon
16:04mpskettenis: are you patches merged
16:04mpss/you/your/
16:05kovlet's see, it's a one-liner patch I can test it quickly
16:05kettenissome of them are merged, some of them are not
16:05mpskettenis: I saw some are but didn't saw latest one in git repo yet
16:05yuyichao has quit [Quit: Konversation terminated!]
16:06mpss/one/ones/ (huh)
16:06yuyichao has joined #asahi
16:06kovhmm it reboots with the patch
16:06mps(making too much typing errors today)
16:06kovit goes through the probing of the NVME and reboots
16:14h_ has quit [Ping timeout: 480 seconds]
16:28kovGlanzmann, so, fun discovery, removing this file makes it work it seems fbaa64.efi
16:29kovthat's the 'fallback' program I guess?
16:32hays has joined #asahi
16:43kettenisso the debian EFI setup is unecessarily complicated because it uses shim
16:57mazyeah, and they deprecated it just before the stable release.
16:57maz(not that I care about secure boot, but hey...)
17:03kettenisit should all work with u-boot when set up correctly
17:05kettenisbut apparently it si easy to break
17:07ketteniskov: looking at the screenshot you posted, those messages directly above "## Application failed, r = 2" don't come from U-Boot but from your bootaa64.efi
17:24eta has quit [Quit: wolp]
17:24kovyeah, makes sense... it'll be a problem for fedora and others as well
17:43eta has joined #asahi
17:48Gues__________________________ has joined #asahi
17:49Gues__________________________ is now known as thevar1able
17:49thevar1able has quit []
17:49Gues__________________________ has joined #asahi
17:49Gues__________________________ has quit []
17:50thevar1able has joined #asahi
17:53Glanzmannkov: I see. I'll try it later tonight. Thank you for figuring that out.
17:55torstenvl has joined #asahi
18:10gladiac is now known as Guest784
18:10gladiac has joined #asahi
18:15JamesB192 has left #asahi [http://quassel-irc.org - Chat comfortably. Anywhere.]
18:16Guest784 has quit [Ping timeout: 480 seconds]
18:24thevar1able has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
18:26MajorBiscuit has quit [Ping timeout: 480 seconds]
18:44ArjunKarangiya[m] has joined #asahi
19:01qeeg has joined #asahi
19:07qeeg_ has quit [Ping timeout: 480 seconds]
19:20darkapex2 has joined #asahi
19:24darkapex1 has quit [Ping timeout: 480 seconds]
19:27Glanzmannkov: I tried to reinstall grub on the macbook air and it rebooted afterwards even with the fbaa64.efi.
19:27GlanzmannI have to try more things and reinstall my macbook air with Linux to figure out where it goes wrong.
19:31Glanzmannjannau: When you tried the Debian installer, were you trying the graphical or the text based installer?
19:34jannauGlanzmann: the net-installer is iirc text-only
19:40Glanzmannjannau: I was looking at https://cdimage.debian.org/debian-cd/current/arm64/iso-cd/debian-11.2.0-arm64-netinst.iso In the grub menu there is Install, graphic install and multiple other options see: https://pbot.rmdir.de/iGajJ6UyMb3y5_WnVyjn9Q
19:45Glanzmannjannau: I see. Thank you for the link I was looking for this.
19:48jannauit's linked under "Network boot" on https://www.debian.org/distrib/netinst
19:53aleasto has quit [Remote host closed the connection]
20:16Glanzmannjannau: Thank you. Previously I was always browsing the /debian dir until I found it. But somehow I was never finding it for arm64 ...
21:01thevar1able has joined #asahi
21:02thevar1able has quit []
21:07Glanzmannkov: I now also broke my macbook air grub installation with the very same error and I try to recover it.
21:08thevar1able has joined #asahi
21:08Glanzmannmps: I think the idea with the installers is that you either install using an ethernet card/dongle or you put the the firmware somewhere where the installer can pick it up.
21:13thevar1able has quit []
21:13thevar1able has joined #asahi
21:14mpsGlanzmann: this is what I also think, using usb ethernet or wifi dongle, but not all (end) users have these devices
21:14mpsbut looks like only option left to us
21:16jannauthe installer will create the efi system partition and save a tarball with the extracted firmware there
21:17mpsjannau: so distro installer can unpack firmware and then run iwd/wpa_supplicant? sound good idea
21:18jannauthe installer needs cutom handling to make them available before it loads brcmfmac
21:18mpsyes, makes sense
21:19jannaua little annoying but manageable
21:19GlanzmannSo, now I'm back at I don't know how to install grub anylonger ... perfect. Lets try kov's workaround.
21:20mpsinstaller is in python, but I don't have experience with python to adapt it distro
21:22Glanzmannkov: You workaround works. Thank you.
21:22GlanzmannNow lets see if I can fix the usb boot.
21:24thevar1able has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
21:25jannaumps: there are two possible integration paths for custom distro installers
21:25thevar1able has joined #asahi
21:26jannau1. installer iso/usb stick which can be bootet via u-boot/efi
21:27mpsjannau: I'm preparing (slowly) 1.
21:28jannau2. integration in asahi-installer. too early for this but I don't think it will require much integration work into asahi-installer
21:28Glanzmannkov: Were you able to boot the installer, if so did you take the one from the iso or from the netboot directory?
21:30mpsjannau: yes, these two options are in my minds, but we have time (I think) to chose one which would be better
21:30jannauin the simplest case ith will be just a shell script / binary asahi-installer executes after it has setup the efi system partition (maybe only after step2.sh)
21:30Glanzmannjannau: For debian that would be pretty easy. We could just dd a rootfs and do a resize2fs and done. Asahi once talked about this.
21:31Glanzmanns/asahi/marcan/g
21:31jannau1. has the advantage that asahi-installer and the distro installer are completly separate
21:31mpsgood thing for alpine users is that we expect of our users they know how to do basic things and follow guides and not just clicking or pressing enter key
21:32jannau2. has the advantage that it doesn't require writing an installer image onto an usb stick
21:33mpshmm, we want/prefer to distribute signed installer images
21:35kettenisthen 1. is for you
21:37mpskettenis: I think so, with asahi installer to first prepare ESP with firmware tarball and possibly(?) install u-boot
21:39kettenisthe idea is that the asahi installer will indeed set up the machine with m1n1+u-boot payload
21:39jannauit should be possible to bundle asahi-installer on the image (readable by macos recovery) for offline installations
21:44mpsI really don't know much about macos (actually very little), so firmware could be extracted in 1TR booted iiuc
21:47Glanzmannkov: The thing is, when I first did that, I just copied the one file to the mentioned directory.
22:10GlanzmannI try to boot the debian installer with a custom kernel but it does not pick up the usb stick (/dev/sda1) I made sure that the usb_storage and xhci-hcd is compiled into kernel (not as a module). Has someone an Idea how I can tell the kernel to scan for the usb devices? I also notice that when I boot in a working installation, the usbstick shows up but is only detected after systemd is runing.
22:12GlanzmannThis is the output from the same kernel booting into debian (not debian installer) and the output of lsusb -t
22:14j`eyunrelated, but good to see you got "ieee80211 phy0: brcmf_p2p_send_action_frame: Unknown Frame: category 0x5, action 0x4" too
22:16Glanzmannjannau: yes, I have that, too. I'm on a wpa3 network. :-)
22:30kyeh[m] has joined #asahi
22:44kovGlanzmann, I used the initrd from netboot yeah
22:44kovthe external usb worked for me, I don't remember doing anything special
22:45kovlast install I did was on the nvme though
22:46kovin other news, is there a way to tell m1n1 to ignore the payload? or the only way to go back to "proxy" mode is kmutil?
22:48j`eyfor now I think thats it
22:49j`eymarcan did suggest, in the past, maybe nvram can be used to set a 'proxy or payload' mode
22:49thevar1able has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
22:50kovI'd put m1n1 as an option on the grub prompt but the problem is the usb keyboard is not working at that point heh
22:51j`eyI would have though usb keyboard worked with grub through u-boot
22:52kovhrm what did I do wrong then
22:52kovthis is on a mini
22:53kovwith latest m1n1 including the dcp fix
22:54Glanzmannkov: Did you take the initrd from 'stable' or 'testing'? Did you take it from the iso or the path on the debian http site?
22:56kovGlanzmann, hmm I think I actually took it from buster, from the url mentioned here https://github.com/AsahiLinux/docs/wiki/SW:Linux#running-linux-via-usb-cable
22:57Glanzmannkov: I see.
22:57thevar1able has joined #asahi
22:57Glanzmannkov: Which kernel config did you use?
23:01kovGlanzmann, let me upload the one I'm using it should be the same I used for the usb install
23:03Glanzmannkov: You're using a mini?
23:03kovGlanzmann, yeah
23:04kovso, funny thing kettenis, apparently my wireless usb keyboard doesn't work at all, I plugged in a cabled usb keyboard and if I hit keys to stop uboot from auto booting then the keyboard also works on grub
23:04kovbut not otherwise
23:06Glanzmannkov: Thank you. So with the mini you have the advantage that the network card is working out oft the box.
23:06GlanzmannWith the air you need to get USB working which I'm unable at the moment with the initrd of the debian installer.
23:06kovGlanzmann, yeah... when I was playing with the air I was using a usb dongle
23:07kovI included the drivers for the ethernet in it on the kernel
23:08Glanzmannkov: I see, I thought I have drivers in, but somehow I don't see the usb device show up, not for the usb stick and also not for my ethernet dongle.
23:08dominic_ has joined #asahi
23:09dominic_ has quit []
23:13Glanzmannkov: For the usb I was missing some drivers, try to compile them in right now.
23:20Glanzmannkov: At the moment I have the problem that when I boot the debian installer it does not show the device for the usb stick or network card, but to the drivers are compiled in.
23:21GlanzmannBut I have to hit bed now. Search for it another day.
23:21Glanzmannkov: Thank you for find the issue with the fbaa64.efi. I updated the instructions.
23:31kovGlanzmann, o/ thank you!
23:44thevar1able has quit [Quit: Textual IRC Client: www.textualapp.com]
…