#asahi · 2022-03-27 17:17
VinDuvpparker[m]: yes#asahi · 2022-03-25 11:41
VinDuvhttps://github.com/AsahiLinux/docs/wiki/Partitioning-cheatsheet#asahi · 2022-03-25 07:26
VinDuvSkirmisher: Maybe try to get the m1n1 logs if you can (you need a second computer and a USB-A to C cable), since it’s also possible that the display initialization chooses the wrong resolution for your monitor#asahi · 2022-03-25 07:12
VinDuvSkirmisher: you’re using HDMI on the mini, right? HDMI -> DVI -> ADC?#asahi · 2022-03-25 07:02
VinDuvYou can try to turn the monitor on at the same time that m1n1 starts and/or disable automatic input switching if your monitor has it#asahi · 2022-03-25 07:00
VinDuvSkirmisher: yes there are some monitors that apparently lose link while getting out of sleep mode. See https://github.com/AsahiLinux/m1n1/issues/159#asahi · 2022-03-23 21:01
VinDuv WhyNotHugo: <kernel> and <initramfs> are placeholders#asahi · 2022-03-11 07:42
VinDuvaw#asahi · 2022-03-11 07:39
VinDuvnot sure if it works with the mini though#asahi · 2022-03-11 07:39
VinDuvIIRC macvdmtool reboot is able to start up a MBP from normal$ shutdown#asahi · 2022-03-05 16:08
VinDuvpugguu[m]1: apt install live-task-standard possibily (I think the Debian installer installs this when you check “Usual system tools” during install)#asahi · 2022-03-03 13:18
VinDuvMaybe something is hardcoded to try loading <current video driver>_dri.so…#asahi · 2022-03-01 19:59
VinDuvfirst-boot adds it to fstab too#asahi · 2022-02-27 08:48
VinDuvI will try to wrap all this into a nice shell script#asahi · 2022-02-27 08:44
VinDuvYou can replace "Some App" "SomeApp" and "myscript" with whatever you want. I think ProductBuildVersion and ProductVersion are customizable but need to follow a certain format for the disk to be recognized by the boot menu#asahi · 2022-02-27 08:42
VinDuvGlanzmann: Here are the files you need on the USB disk/volume: https://paste.debian.net/plainh/47c9f2fb#asahi · 2022-02-27 06:59
VinDuvThis is also not limited to external USB drives; it also works if the files are in an APFS volume in internal storage, which I guess might be useful to have a Asahi Recovery boot option in the boot menu or something.#asahi · 2022-02-27 06:56
VinDuvSo the installation workflow from 1TR could be “plug in a USB stick, hold the power button, select Install Asahi” instead of having to manually open the terminal and run curl | sh. The installer doesn’t even need to be graphical since it’s possible for the launched shell script to start the recovery environment’s Terminal and giving it an arbitrary command to run.#asahi · 2022-02-27 06:54
VinDuv(it works even if the app is just a shell script) and it looks like it’s in 1TR mode.#asahi · 2022-02-27 06:54
VinDuvSo I’ve been looking at how macOS installation from USB works on M1 Macs and I think it might be interesting for the Asashi installer. The way it works is that there’s a hidden plist file on the USB drive that references a macOS application on the drive; if this file is present, the USB drive will show up in the power-button-held boot menu, and when selected, it will run the application. It doesn’t seem to care about file signature #asahi · 2022-02-26 14:13
VinDuvHow does grub finds the ESP “normally”? Even on a x86 PC you can have multiple disks so multiple ESP#asahi · 2022-02-26 09:38
VinDuvGlanzmann: Mounting it twice doesn’t make a difference in my case; I tried it to see if it would make a difference, but it didn’t#asahi · 2022-02-26 08:40
VinDuvSo I wrote a shell script to test this further (https://paste.debian.net/hidden/b1a06a35/ , requires a /mnt/test directory), and it works every time#asahi · 2022-02-26 08:39
VinDuvGlanzmann: I’m very confused. After you said that the tune2fs on loop0 didn’t work, I retried on my side, and it failed. Today I tried it again, and it worked.#asahi · 2022-02-25 20:44
VinDuvCan you try manually attaching the file to the loop device, executing mkfs.ext4 -O metadata_csum on the loop device, and then mounting it? That’s what I did#asahi · 2022-02-25 20:43
VinDuvGlanzmann: This is on a debian stable VM. Interestingly if I follow your steps I can reproduce your problem. Weird#asahi · 2022-02-25 20:35
VinDuvSeems to work here. Try doing it during the mke2fs#asahi · 2022-02-25 20:24
VinDuvah, that’s why it says it will take time#asahi · 2022-02-25 20:22
VinDuvweird, I tried after switching the filesystem to read-only, and it still failed but tune2fs added a "(and reboot afterwards!)" at the end of its error message#asahi · 2022-02-21 20:05
VinDuvbut if you have energy_full in sysfs it should use that for the battery capacity#asahi · 2022-02-21 20:05
VinDuvas400[m]: from what I can tell, upowerd might be doing some calculations depending on what’s available in sysfs https://github.com/freedesktop/upower/blob/master/src/linux/up-device-supply.c#L574#asahi · 2022-02-21 19:43
VinDuvas400[m]: which upower metric are you talking about? energy-full?#asahi · 2022-02-21 13:55
VinDuvGlanzmann: Some TVs cut the edges of the image when receiving an HDMI signal#asahi · 2022-02-20 15:48
VinDuv(I think I tried doing the wait/set_mode after swap_end; it worked and the monitor stayed up, but it was blank, probably because the framebuffer address changed)#asahi · 2022-02-20 15:46
VinDuvwhich is probably extremely not like things should be done#asahi · 2022-02-20 15:46
VinDuvit does the wait and the set_mode after swap_begin and before swap_end#asahi · 2022-02-20 15:43
VinDuvI’m also pretty sure that it only starts waking up on dcp_ib_swap_begin, not dcp_ib_set_mode#asahi · 2022-02-20 15:40
VinDuvtpw_rules: one of them yes, the other one still occasionally fails (power-up then “no signal”) with 11.x#asahi · 2022-02-20 15:06
VinDuvtpw_rules: I see. I guess whatever delays iBoot uses are not sufficient with your monitors. I’m still wondering if iBoot somehow manages to avoid the disconnect/reconnect wait period in my case, or if it waits for it asynchronously while booting the rest of the system#asahi · 2022-02-20 06:59
VinDuvtpw_rules: did you test your monitor with <12.0 iBoot? (i.e. before a 12.0 macOS ever got installed)#asahi · 2022-02-18 14:10
VinDuv(yes idevicerestore has a -l option that automatically downloads the right ipsw… but if you happen to run out of disk space while it downloads the files, it produces confusing error messages, unfortunately)#asahi · 2022-02-18 14:09
VinDuvWhen I restored the mini, idevicerestore downloaded a 13.2 GiB ipsw and extracted 11.8 GiB of files out of it for a total of 24.9 GiB used#asahi · 2022-02-18 08:56
VinDuv(ok given that this is USB maybe saying “any USB cable” is a bit optimistic :)#asahi · 2022-02-18 08:55
VinDuvThe other machine doesn’t even needs to have USB3 ports, USB2 will work fine#asahi · 2022-02-18 08:54
VinDuvDavid[m]12345678: any USB cable which can be connected to the USB-C port on the Mac and to a USB-A or USB-C port on the other machine should work#asahi · 2022-02-18 08:49
VinDuvidevicerestore works fine in my experience but you need to install the right parts from source, start usbmuxd beforehand and have sufficient disk space#asahi · 2022-01-29 08:43
VinDuvAlso I’m not sure if it’s safe to install 12.0+ m1n1 on a <12.0 Mac. My understanding is that the macOS installer upgrades iBoot automatically when 12.0+ is installed, but I’m not sure if that happens when m1n1 is installed#asahi · 2022-01-29 08:26
VinDuvchadmed: nitpick: in step 3, the “Loading startup options...” message might not be visible on 12.0+ Mac mini, and may be localized. The boot menu itself is also localized. Maybe add something like “do not let go until you see Loading startup options... appear under the Apple logo, or a cog icon appear on the screen”?#asahi · 2022-01-26 19:51
VinDuvconcatenating payloads to m1n1.raw should work I think#asahi · 2022-01-26 19:50
VinDuvoh wait you’re talking about uboot, sorry