#
✕ nick:JMR2
#asahi · 2025-10-24 02:18
JMR2Just found the Oct. 1st discussion on a very similar (same?) topic in the log. And issues #410 and #413 in github. I'll add the Battery-Toolkit fix link there. Apologies for the noise.
#asahi · 2025-10-24 01:52
JMR2See https://github.com/mhaeuser/Battery-Toolkit/commit/64c97cc34896c95f2ee26f9ba5bed0e67ca6c5a3
#asahi · 2025-10-24 01:51
JMR2The equivalent MacOS apps (AlDente, Battery-Toolkit) both report having to make change due to new firmware in MacOS 15.7/26.
#asahi · 2025-10-24 01:51
JMR2I'm getting Input/output error since somewhere in September.
#asahi · 2025-10-24 01:51
JMR2Hello. Is echo inhibit-charge |sudo tee /sys/class/power_supply/macsmc-battery/charge_behaviour still supposed to work?
#asahi · 2023-12-01 03:25
jmr2mps/povik: the missing kernel config that was causing my soc_component_write_no_lock TAS2770 issue is REGULATOR_FIXED_VOLTAGE.
#asahi · 2023-11-28 01:37
jmr2mps/povik: was a solution found to the soc_component_write_no_lock issue that was discussed on Nov. 18? I have a similar one on TAS2770/J313 that goes away when switching from my custom kernel config to the ARCH official one. I'm still digging.
#asahi · 2023-11-09 04:47
jmr2My point was that so far, I was the only known case, but now there likely are two.
#asahi · 2023-11-09 04:46
jmr2Banning the whole range make sense, but this is the code where you check that version. Given that I was stuck on 12.2.1, my understanding is that I have been in the banned range with no way to fix the issue.
#asahi · 2023-11-09 00:44
jmr2*fixed
#asahi · 2023-11-09 00:43
jmr2I fised it with a DFU firmware restore, but since version 0 doesn't seem to have consequences, the fix is probably unnecessarily risky.
#asahi · 2023-11-09 00:42
jmr2bendodroid: SystemRecovery version 0 is what I started seeing after marcan fixed the error I reported on Oct. 31. See the channel logs. Glad to see I'm not the only occurrence.
#asahi · 2023-11-05 04:24
jmr2Conclusion for my recent issues (System rOS stuck @ 12.2.1 and missing SystemRecovery in iSCPreboot): idevicerestore (in revive mode, with the 14.1 files) fixed both without any data loss. YMMV.
#asahi · 2023-11-02 02:56
jmr2Anyway, I cleaned it up, deleted the last old m1n1 stub, and it's back, with a newer stage1 m1n1 and based on a 13.5. stub. I'll check after the next MacOS update if it helped.
#asahi · 2023-11-02 02:56
jmr2Even considering that deleting partitions changed the GPT indexes, I don't see how that could work.
#asahi · 2023-11-02 02:56
jmr2So it was really booting using m1n1 from the new EFI partition, but grub data from the old one.
#asahi · 2023-11-02 00:36
jmr2OK, there's really some mixup, because there's no EFI folder on the new EFI partition.
#asahi · 2023-11-02 00:29
jmr2Here's the current partition list, to make it more visual https://pastebin.com/qaAN8YEc Thanks!
#asahi · 2023-11-02 00:29
jmr2Is it really that simple, or do I have some mixups in my stub + ESP associations? Can I safely delete the old m1n1 stub & EFI?
#asahi · 2023-11-02 00:29
jmr2Except that I don't have to do it - regardless if I use the old or the new bootpicker entry, I get the grub menu, with my usual entries and configs, and everything boots as it used to.
#asahi · 2023-11-02 00:29
jmr2I ran the current ALARM installer, non-expert, in m1n1/UBoot/ESP mode. The plan was to keep the same rootfs, move the content of my (custom) ESP to the new one, and then delete the last old m1n1 install.
#asahi · 2023-11-02 00:29
jmr2I used to have three installation of m1n1 - with 12.01, 12.1 and 12.3, with only the 3rd one paired with an ESP. Deleted the two oldest.
#asahi · 2023-11-02 00:29
jmr2Hey folks... a little help please. Following the discovery that my SystemRecovery is still 12.2.1, I decided to do come cleanup.
#asahi · 2023-11-01 08:07
jmr2I'm still undecided whether I'll wipe the machine to try to fix it or not. Probably not in the short term.
#asahi · 2023-11-01 08:06
jmr2Tested, all good. It's reporting zero from MacOS as well as single & double-tap recovery. Thanks.
#asahi · 2023-11-01 05:26
jmr2I wish I knew. Your plan LGTM.
#asahi · 2023-10-31 21:50
jmr2marcan: just tried sw_vers in both single and double-tap recovery. Single reports 14.1. Double reports 12.2.1.
#asahi · 2023-10-31 18:28
jmr2No worries at all. I'll keep an eye on the channel, ping me if I can help. Have a good night!
#asahi · 2023-10-31 18:17
jmr2It also ran some MacOS 12 beta IIRC.
#asahi · 2023-10-31 18:14
jmr2Would a diskutil list be useful?
#asahi · 2023-10-31 18:13
jmr2Bought in early 2021 with MacOS 11, did pretty much all the updates as they came out. It still has 12.0 and a 12.1 Asahi Stub. Was multi-boot MacOS11/MacOS12 at one point IIRC.
#asahi · 2023-10-31 18:08
jmr2marcan: here you go: https://pastebin.com/B8HnhT5a
#asahi · 2023-10-31 17:20
jmr2curl https://alx.sh | sh currently fails for me with FileNotFoundError: [Errno 2] No such file or directory: '/System/Volumes/iSCPreboot/SystemRecovery'; M1 Air, MacOS 14.1 running in MacOS, not recovery.
#asahi · 2023-02-10 04:21
jmr2Err... this one: https://pypi.org/project/pyliblzfse/
#asahi · 2023-02-10 04:20
jmr2(Note that I'm just a user, not a dev, so YMMV.)
#asahi · 2023-02-10 04:20
jmr2Given that the installer is in python, you might as well start with a python implementation, like this one. Good luck!
#asahi · 2023-02-10 04:19
jmr2The idea would be to be able to install on a partition smaller than 2.5GB, so compression would need to happen on the stream, not on an existing file.
#asahi · 2023-02-10 04:19
jmr2dgb: nice! If you want to go all the way, I thing the end goal would be a pull request on code that would integrate that into the asahi installer.
#asahi · 2023-01-04 18:39
jmr2Agreed. But I still don't really understand why fetch -t isn't the default fetch behavior - and what the implications are. Anyway, this is getting quite off-topic. Thanks again.
#asahi · 2023-01-04 18:29
jmr2jannau: thanks. I'm just wondering if the warning on https://github.com/AsahiLinux/linux/commit/ee25c42 means that it'll be garbage-collected at some point.
#asahi · 2023-01-04 18:21
jmr2marcan: FYI, the linux/asahi-6.1-3 tag no longer resolves - commit ee25c42 is gone. asahi-6.1-2 is still available.
#asahi · 2022-12-17 04:04
jmr2It's now available, and it includes the correct patch. Tested, and 1.6.2-3 doesn't have the issue. Cool. Thanks again for making it happen.
#asahi · 2022-12-17 01:16
jmr2Although I'm surprised - the commit you asked for is for loongarch64, not aarch64. 1.6.2-3 is so fresh that I can't find its source at this time. I guess we'll see.
#asahi · 2022-12-17 00:59
jmr2Scratch that - your patch was already accepted: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026217 Congrats!
#asahi · 2022-12-17 00:53
jmr2Glanzmann: should you wish to add more info to the bug report, there's a partial stack trace in journalctl. Example: http://paste.debian.net/plain/1264341
#asahi · 2022-12-17 00:39
jmr2Glanzmann: thank you for the pointers. Looks like I haven't been paying attention for too long. Reverting to libunwind8_1.3.2-2 fixed it.
#asahi · 2022-12-16 01:29
jmr2I was hoping for a missing option in my trimmed-down kernel config, but it looks like that's not it.
#asahi · 2022-12-16 00:56
jmr2Hello. Just in case... anyone else running Debian Testing on M1 has Xorg dumping core on startup? Only started yesterday, following an apt update. My previous update was on Dec 9.
#asahi · 2022-11-24 00:47
jmr2Great work everyone! Thanks!
#asahi · 2022-11-24 00:46
jmr2Only thing that caught me off-guard was that I used to use the u-boot dtbs, which at this time are causing a "apple_soc_cpufreq_init: failed to get cluster info" error in dmesg. Easily fixed by using the kernel ones.

plus ›