#
✕ nick:flokli
#asahi-dev · 2026-03-28 15:35
flokliIf not, I could take a stab at it
#asahi-dev · 2026-03-28 15:34
flokliJamesCalligeros[m]: does this include the switch to dynamic users? https://github.com/AsahiLinux/speakersafetyd/pull/26#issuecomment-2779886212
#asahi-dev · 2026-03-21 10:08
flokliHichens[m]: seems there's a new issue now: https://github.com/bluez/bluez/issues/1976
#asahi-dev · 2026-03-21 07:33
flokliMaybe something for the last of yaks to shave, so it gets traction
#asahi-dev · 2026-03-21 07:33
flokliThis is the proposed non hacky solution: https://github.com/bluez/bluez/issues/722#issuecomment-2044866434
#asahi-dev · 2026-03-21 07:32
flokliHichens[m]: yeah that's a hack and it would be very nice if you wouldn't need to run some bash loop 😂
#asahi-dev · 2026-03-21 07:21
flokliHichens[m]: check if your wifi is connected to 2.4 or 5
#asahi-dev · 2026-01-14 12:03
flokliWay more characters to process, lol
#asahi-dev · 2025-12-28 09:11
flokliCool! I might pass by and grab a sticker if you still have some :-)
#asahi-dev · 2025-12-28 09:10
floklisven: you're around at the assembly?
#asahi-dev · 2025-08-22 15:54
flokli<3
#asahi-dev · 2025-08-04 13:48
flokli(scnr)
#asahi-dev · 2025-08-04 13:48
floklionly one nibble at a time?
#asahi-dev · 2025-08-04 13:48
flokli> the bug doesn't eat (much) data
#asahi-dev · 2025-07-16 17:27
flokliSo the wifi issue above is definitely OWE related, it is fine on the same APs when using 802.11x, and deleting the other config.
#asahi-dev · 2025-07-15 17:42
flokli^ DannyB on the wifi stuff
#asahi-dev · 2025-07-15 16:30
flokliHmmh nope, the wifi thing is not stable, even with disabled power management. I wonder if there's a chance to try with other firmware.
#asahi-dev · 2025-07-15 13:09
flokliI added this to my iwd config, as per https://man.archlinux.org/man/iwd.config.5#DriverQuirks 's PowerSaveDisable= option. I'll see how stable it is.
#asahi-dev · 2025-07-15 13:06
flokliGoogling around a bit seems to hint at power saving to be part of the issue, and a `iw wlan0 set power_save off` and some more toggling seems to have made it associate for now.
#asahi-dev · 2025-07-15 13:00
floklirebooted with that kernel, still the same traces in dmesg: https://paste.linuxlounge.net/BU
#asahi-dev · 2025-07-15 12:59
flokliok
#asahi-dev · 2025-07-15 12:54
floklisame for the simple-mfd-spmi kernel module
#asahi-dev · 2025-07-15 12:49
floklijannau: I can verify it builds now. Though now some later tooling cannot find the nvmem_spmi_mfd kernel module. Was that removed?
#asahi-dev · 2025-07-15 12:24
flokliI'll try 1.88
#asahi-dev · 2025-07-15 12:23
floklichadmed: it does not build with 1.86, same error message
#asahi-dev · 2025-07-15 12:00
floklihttps://dpaste.com/AKQAZBFDM is the full build log
#asahi-dev · 2025-07-15 11:59
floklichaos_princess: 1.87.0
#asahi-dev · 2025-07-15 11:14
floklichaos_princess: fails to buils with https://paste.linuxlounge.net/W4, "the trait bound `*mut kernel::bindings::fwnode_handle: Default` is not satisfied"
#asahi-dev · 2025-07-15 10:54
flokliok, will build 5c2a16cd2eafc8485aefc601d5727b40203d3d3b from 28mins ago
#asahi-dev · 2025-07-15 10:53
floklichaos_princess: asahi-wip branch, you mean?
#asahi-dev · 2025-07-15 10:51
flokli6.14.8-asahi, M2 Air
#asahi-dev · 2025-07-15 10:48
floklihttps://paste.linuxlounge.net/NU
#asahi-dev · 2025-07-15 10:47
flokliI'm at a camping event with wifi, and the wifi driver seems really really unhappy about something happening there, I guess OWE. Getting kernel traces every second or so
#asahi-dev · 2025-07-01 14:05
floklinothing in my logs from the last 2 months
#asahi-dev · 2025-05-10 22:39
floklity, I can confirm the noise is gone from the logs :-)
#asahi-dev · 2025-05-09 20:08
flokliI assume that's a wrong error code somewhere? Power over air doesn't seem to be a thing yet :-)
#asahi-dev · 2025-05-09 20:08
floklicat: /sys/class/power_supply/macsmc-ac/input_current_limit: Operation not possible due to RF-kill
#asahi-dev · 2025-05-09 20:08
floklicat /sys/class/power_supply/macsmc-ac/input_current_limit
#asahi-dev · 2025-05-06 15:11
flokliI don't have the setup for that. The only thing I could think of is that something during handover between normal system and systemd-shutdown retriggers a ping, or resets a timeout
#asahi-dev · 2025-05-06 14:34
floklididn't set RuntimeWatchdogSec= or any of the other ones
#asahi-dev · 2025-05-06 14:33
flokliI think it's logged twice because we use the shutdown ramfs thing
#asahi-dev · 2025-05-06 14:32
floklihttps://paste.linuxlounge.net/6M
#asahi-dev · 2025-05-06 14:27
flokli257.3 here
#asahi-dev · 2025-05-06 14:11
flokliYup, and here is the watchdog firing at 240s. So that was the fix.
#asahi-dev · 2025-05-06 14:09
flokliand implementing the behaviour seems to work, at least it didn't get rebooted yet
#asahi-dev · 2025-05-06 14:09
flokliI agree on watchdog-core, but watchdog-kernel-api.rst, L197 says otherwise
#asahi-dev · 2025-05-06 13:36
flokliyeah, looks like we need to use min(timeout_secs, max_hw_timeout_secs), which I didn't do. Will test with that patch and roll a v2.
#asahi-dev · 2025-05-06 13:15
flokliso there's something fishy with this patch
#asahi-dev · 2025-05-06 13:15
flokliwithout the kernel patch and setting a timeout of 90secs it does survive up to 70s (before I ctrl-c'ed it)
#asahi-dev · 2025-05-06 13:09
flokliI guess I can retry with something like 90secs and without my patch. maybe some of the math, or reading the clk rate is already broken.

plus ›