2022-01-17
00:45user982492 has joined #asahi
00:50user982492 has quit []
00:51user982492 has joined #asahi
02:00hays has quit []
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: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: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: But I'm also thinking of modifying the debian installer that it just works.
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: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: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:15ChristianvonElm[m] okay I'll try
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: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: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: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: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?
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:33GlanzmannHowever grub-install should make it bootable, and it did before, but it does not seem to.
15:34kovI found this, but not sure it's related https://patchwork.ozlabs.org/project/uboot/patch/20210428135401.22365-1-peng.fan@oss.nxp.com/
15:34kovGlanzmann, I used the initrd trick, got the initrd and bundled it with the m1n1 and the kernel
15:35kovthe one mentioned here https://github.com/AsahiLinux/docs/wiki/SW:Linux#running-linux-via-usb-cable
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: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:36Glanzmannkov: I see. But you should be able to install grub manually from the installer seperate window.
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:37Glanzmannkov: Just to be clear you run the installer by using the netboot linux kernel and initrd and said not to load modules?
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: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:42_jannau_Glanzmann: I tried it with the network installer and the installer itself will will not advance
15:42GlanzmannHere it is: https://wiki.debian.org/DebianInstaller/Arm/OtherPlatforms 'Inside Debian-Installer'.
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:44GlanzmannThe dd is here: It requires a 1 GB partition to dd it on. YOu can do it from macos or Linux.
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:54h_ has joined #asahi
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
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:05yuyichao has quit [Quit: Konversation terminated!]
16:06yuyichao has joined #asahi
16:14h_ has quit [Ping timeout: 480 seconds]
16:32hays has joined #asahi
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: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: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: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:43jannauGlanzmann: was using the tiny option with just the initrd https://deb.debian.org/debian/dists/bullseye/main/installer-arm64/current/images/netboot/debian-installer/arm64/
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: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:19GlanzmannSo, now I'm back at I don't know how to install grub anylonger ... perfect. Lets try kov's workaround.
21:24thevar1able has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
21:25thevar1able has joined #asahi
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: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: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:12Glanzmannhttps://pbot.rmdir.de/HsD1yezL7pYZwkjlToP_gg https://pbot.rmdir.de/26uzMdBenUWuY57dJH55QQ
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:30kyeh[m] has joined #asahi
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: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: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:57thevar1able has joined #asahi
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: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: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: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:44thevar1able has quit [Quit: Textual IRC Client: www.textualapp.com]