#asahi · 2023-09-19 13:22
_jannau_u154s: that looks like pipewire/wireplumber is not running. what did you install?#asahi · 2023-09-19 13:22
opticronyeah, I just forgot about that#asahi · 2023-09-19 13:21
_jannau_opticron: speaker on the mac mini is enabled since ages#asahi · 2023-09-19 13:19
u154s@jannau methinks yes.#asahi · 2023-09-19 13:19
opticronman...I saw talk about speakers and thought I missed an announcement :(#asahi · 2023-09-19 13:18
_jannau_u154s: in a plasma session?#asahi · 2023-09-19 12:51
u154s@jannau unfortunately KDE's audio device configure GUI has the configure option greyed out. https://paste.pics/f75221005b4607944928606732611c4e#asahi · 2023-09-19 12:36
pitustthasti: thanks! that confirms my suspicions i guess#asahi · 2023-09-19 12:26
thastipitust: i filed an i3status PR a long time ago, but the tool seems ~unmaintained and I have switched to waybar in the meatime... https://github.com/i3/i3status/pull/504#asahi · 2023-09-19 11:04
pitustjannau: yeah, looks like an i3status issue. i guess this isn't very common, because on x86 it seems that the "time to discharge" number isn't reported (or at least it's not reported on my x86 laptop, anyway)#asahi · 2023-09-19 10:11
_jannau_u154s: at least KDE's audio device configure has a drop-down menu with "Off", "n/a" and "Pro Audio". ignore any meaning of "n/a", that's just caused by an oversight in our config. if you choose "n/a" audio should work#asahi · 2023-09-19 09:43
u154s@jannau Sorry, I was away for a while. I am not sure what "n/a" in this context means - not applicable / not available? And there are pipewire config files all over the place.... Sorry to be a bother.#asahi · 2023-09-19 08:56
_jannau_that means the speaker detection works now. I suspect pipewire audio config might be just wrong. Try to set the profile to "n/a"#asahi · 2023-09-19 08:50
u154s@jannau https://paste.debian.net/1292447/#asahi · 2023-09-19 08:47
u154s@jannau will do.#asahi · 2023-09-19 08:46
_jannau_u154s: that looks correct, can you install alsa-ucm-utils paste the the output of `alsaucm -c 0 dump text` to a pastebin#asahi · 2023-09-19 08:37
u154s@jannau this is my DetectSpeaker.conf now - https://paste.debian.net/1292444/ I still have no sound - have I overlooked something or done something wrong? Obviously, a reboot since the weekend. TIA.#asahi · 2023-09-19 07:39
jannaupitust: battery stats look like a bug in i3status, kernel specifies that it should be in seconds: Documentation/power/power_supply_class.rst#asahi · 2023-09-19 07:27
pitustmesa-asahi-edge, thanks.#asahi · 2023-09-19 06:48
jannauinstall mesa-asahi-edge, kernel should be already installed#asahi · 2023-09-19 06:42
chadmedinstall the -edge kernel#asahi · 2023-09-19 06:34
pitustwait, how do i get hardware acceleration working? right now i seem to be using llvmpipe which is unacclerated...#asahi · 2023-09-19 06:25
pitustand s2idle works so that's cool. i guess it's all working then! (except speakers or touchbar, but I understand that's coming soon™)#asahi · 2023-09-19 06:21
pitustbut it looks like seconds instead#asahi · 2023-09-19 06:21
pitusti think i3status expects /sys/class/power_supply/macsmc-battery/time_to_empty_now to be in milliseconds#asahi · 2023-09-19 06:16
pitustreporting to userspace is broken#asahi · 2023-09-19 06:14
pitust85% is also like what macos reported to#asahi · 2023-09-19 06:13
pitusttempty 498m = 8h#asahi · 2023-09-19 06:13
pitustthis is great: [ 359.888119] macsmc-power macsmc-power: In 0.000W Sys 4.336W 3V8 1.829W MPMU 0.000W SPMU 0.000W CLVR 0.000W CPU 0.834W Batt -4.276W 85% Tempty 498m#asahi · 2023-09-18 23:32
chadmed_i also have the same issue with the battery health measurements out of the smc, it jumps all over the place. last week it was 82% this morning it was 89%#asahi · 2023-09-18 23:31
chadmed_we know there is something up with the idle power draw on t600x but it shouldnt be 2 hours of battery bad...#asahi · 2023-09-18 23:31
chadmed_pitust: i can get about 6ish hours of light use with brightness at the same as you out of my 14" m1 pro machine#asahi · 2023-09-18 22:18
pitustthe laptop is definitely not dissipating 60 watts of heat#asahi · 2023-09-18 22:17
pitustbut linux's battery usage number makes no sense#asahi · 2023-09-18 21:22
unixpoetit looks like linux might be taking health into account for the charge percentage, the math more or less works out#asahi · 2023-09-18 21:22
unixpoetthree different pieces of software, three different answers \o/#asahi · 2023-09-18 21:21
pitustand linux was saying 77%#asahi · 2023-09-18 21:21
pitustand charge 90.9 when macos reports 96#asahi · 2023-09-18 21:20
pitustcoconutBttery reports health 79%#asahi · 2023-09-18 21:20
pitustunixpoet: thanks, that is very... *interesting*#asahi · 2023-09-18 21:19
pitusthmm okay#asahi · 2023-09-18 21:09
unixpoetfwiw, I noticed that macos will fib about battery life / percentages whereas apps like coconutbattery give a more truthful report#asahi · 2023-09-18 20:14
jannauthat's from my 14-inch m1 max, the m1 air should show lower values but if Tempty with a full battery is there also very low (60 - 120 minutes) then it might be interesting to look at the values#asahi · 2023-09-18 20:12
pitustwill test in a minute, probably#asahi · 2023-09-18 20:12
pitustokay got it#asahi · 2023-09-18 20:11
jannaupitust: after `echo 1 | sudo tee /sys/module/macsmc_power/parameters/log_power` there continuous log messages like "macsmc-power macsmc-power: In 0.000W Sys 10.392W 3V8 5.731W MPMU 0.854W SPMU 2.238W CLVR 1.673W CPU 4.015W Batt -10.437W 74% Tempty 221m" in the kernel log (dmesg -w)#asahi · 2023-09-18 20:09
pitustit also sounds unlikely in that macos reported 100% afterwards#asahi · 2023-09-18 20:09
pitustmhm#asahi · 2023-09-18 20:09
tpw_rulesi mean that's the math to discharge that battery in one hour#asahi · 2023-09-18 20:08
pitusta dissipation of 60 watts sounds... unlikely