#asahi · 2023-12-01 21:43
kidplayer666j`ey: did you hear about the printer that refused to print on Thursdays?#asahi · 2023-12-01 21:43
holidayjanneg: oh oki will try rn#asahi · 2023-12-01 21:42
jannegholiday: the step2.sh remains on disk in "Finish Installation" but using repair from the installer is the safer/easier option#asahi · 2023-12-01 21:42
kidplayer666Not the only one who heard it then#asahi · 2023-12-01 21:42
kidplayer666Ah nice#asahi · 2023-12-01 21:42
j`eyyeah I know the story :)#asahi · 2023-12-01 21:42
kidplayer666Saw some story online#asahi · 2023-12-01 21:42
kidplayer666j`ey: that happened once allegedly#asahi · 2023-12-01 21:42
j`eykidplayer666: hah#asahi · 2023-12-01 21:40
kidplayer666j`ey: sounds as silly as only being able to send an email 500 miles away#asahi · 2023-12-01 21:40
kidplayer666holiday: holy cow, that’s my mac. Kinda wary to update now…#asahi · 2023-12-01 21:36
holidayhow do i repeat the step 2 of the install tho#asahi · 2023-12-01 21:35
holidaydamn#asahi · 2023-12-01 21:35
jannegwe have no idea why that happens#asahi · 2023-12-01 21:34
jannegit appears that macos updates sometimes invalidate the custom boot object on other installations#asahi · 2023-12-01 21:34
holidaybase 13 inch#asahi · 2023-12-01 21:34
holidayjanneg: m1 macbook pro#asahi · 2023-12-01 21:33
jannegholiday: which device? you can probably restore by either repeating step2 of the install or using the installer in recovery mode to "repair" the 1st stage m1n1#asahi · 2023-12-01 21:31
holidayand now asahi is in a boot loop#asahi · 2023-12-01 21:31
holidayi updated to macOS 14.1.2#asahi · 2023-12-01 21:30
holidayguys#asahi · 2023-12-01 21:30
j`eyI can't find any reason for it!#asahi · 2023-12-01 21:29
kidplayer666kinda weird to only be 1/5 times#asahi · 2023-12-01 21:16
j`eymaybe it's a race condition :/#asahi · 2023-12-01 21:15
veloekj`ey: I'll let you know if that happens, but it hasn't so far.#asahi · 2023-12-01 21:05
nicolas17cy8aer: afaik macOS 14.1.2 is only a Safari security update#asahi · 2023-12-01 20:27
j`eyveloek: I'd be interested to know if it ever fails for you, seems to be about 1/5 boots it fails for me#asahi · 2023-12-01 20:09
j`eyveloek: thanks#asahi · 2023-12-01 20:08
veloekj`ey: yes, on a fresh boot of fedora on my m1 air speakersafetyd is active and running.#asahi · 2023-12-01 17:39
j`eysomeone with an air.. on a clean/fresh boot, has speakersafetyd.service already started?#asahi · 2023-12-01 16:57
j`eyok, nothing in the udev logs between a working and a failing boot#asahi · 2023-12-01 16:45
j`eyI only once managed to get verbose logs with udev_log, seems like it's ignored every other time ive passed it :/#asahi · 2023-12-01 16:43
j`eyok, the snd-soc-macaudio and tas etc modules are not possible to probe twice, got a splat while trying that#asahi · 2023-12-01 16:35
j`eyok wtf, journal -u systemd-udevd is.. confusing. it seems like it doesnt do *anything* in the case the speakers dont work#asahi · 2023-12-01 16:30
cy8aerHas anyone discovered any new bugs in 14.1.2, or is it safe to update (from 14.1.1)?#asahi · 2023-12-01 16:22
PaulFertserProbably it's getting used by pipewire right away? And before you stop pipewire you can't unload the module?#asahi · 2023-12-01 16:19
j`eydamnit, even when the daemon doesnt start, it says snd-soc-macaudio is in use :/#asahi · 2023-12-01 16:15
j`eytrying to reboot into a non working state again, trying for the 4th time..#asahi · 2023-12-01 16:14
j`eyand can't remove the module, it's in use#asahi · 2023-12-01 16:11
j`eyyeah, even when the daemon didnt load, I had some pcmC* files in sysfs#asahi · 2023-12-01 16:10
PaulFertserProbably makes sense to run "udevadm monitor" and then in another console "modprobe -r snd-soc-macaudio; modprobe snd-soc-macaudio" or something like that.#asahi · 2023-12-01 16:09
PaulFertserBut then it's a question of whether you have "pcmC*D2c" created at all.#asahi · 2023-12-01 16:09
j`eyand no, not running systemctl as root#asahi · 2023-12-01 16:09
j`eythat's what should be happening#asahi · 2023-12-01 16:08
PaulFertserIf you want to run it from a udev rule then yes, you need to have it disabled and started from a rule.#asahi · 2023-12-01 16:08
PaulFertserBut it is supposed to be started by default, it should be part of "multi-user.target" no?#asahi · 2023-12-01 16:07
PaulFertserAre you running systemctl with root permissions when getting status and logs?#asahi · 2023-12-01 16:07
j`eydoesnt disabled just mean not started by default?#asahi · 2023-12-01 16:07
PaulFertserHm, strange it's "disabled" as if you run "systemctl disable speakersafetyd.service" somewhere.#asahi · 2023-12-01 16:04
j`eyjournalctl shows no entries for this boot