#asahi · 2026-08-08 11:20
twbon linux?#asahi · 2026-08-08 11:20
chaos_princessm1pro is around 4W with screen off and mostly-idle#asahi · 2026-08-08 11:18
twbThe numbers I see on a T490 are 10-20 hours and on a macbook 15-25 (linux) and capped at 50h (macos), although admittedly that's after doing everthing to get the number up#asahi · 2026-08-08 11:17
fl0_idespeciallz not if sth decides to do things in the background or I forgot aobut some vm...#asahi · 2026-08-08 11:16
fl0_idtwb seems about right. on the m3 max, I don|t even get that on macos I think...#asahi · 2026-08-08 11:15
chaos_princesslike, the backlight can use 10W at max power#asahi · 2026-08-08 11:15
chaos_princessit _highly_ depends on brightness#asahi · 2026-08-08 11:14
twbonly 6 hours battery life from 100% on a mac armbook?#asahi · 2026-08-08 00:15
jjlooks like about ~5-6 hours now on medium-low brightness. big improvement! it was somewhere around 3 or 4 before#asahi · 2026-08-08 00:13
jjokay, lovely, this was indeed the issue. my battery life looks to have gone up +1 hour, sweet#asahi · 2026-08-07 23:51
jji asked the robot to debug. it pointed me to m1n1 itself. it looks like on fedora asahi remix m1n1 is sourced from upstream fedora repos, which are on version 1.5.2, while version 1.6 from the end of june has in its release notes "PMP initialization in kboot", which i'd imagine is handy for having PMP enabled#asahi · 2026-08-07 23:49
JamesCalligeros[m]You can point the update-m1n1 script to whichever directory you want using the DTBS env var#asahi · 2026-08-07 23:49
chaos_princessisn't it somewhere nearby? at least on fedora#asahi · 2026-08-07 23:48
JamesCalligeros[m]Who could have predicted this#asahi · 2026-08-07 23:44
jjthe robot has lied to me, tragic#asahi · 2026-08-07 23:32
jjhmm, ok. a large language model is telling me that copying the built .dtb to /boot/dtb/apple/ and running update-m1n1 should work. this sounds about right given my understanding of what m1n1 does, i'll give it a whirl#asahi · 2026-08-07 23:25
chaos_princessyou can probably compile just the dtb file and not the entire kernel, but idk how to do that properly#asahi · 2026-08-07 23:25
jjicic, found the .dts files#asahi · 2026-08-07 23:24
chaos_princessyep#asahi · 2026-08-07 23:24
jjah, will i have to rebuild + manage my kernel versions manually?#asahi · 2026-08-07 23:23
jjwhere are .dts files usually located? i can't seem to find them#asahi · 2026-08-07 23:21
chaos_princessyou edit the .dts file that corresponds to your device and add `#define APPLE_USE_PMP 1` on top#asahi · 2026-08-07 23:20
jjhow might i enable the PMP? per https://asahilinux.org/2026/04/progress-report-7-0/#:~:text=APPLE%5FUSE%5FPMP, it sounds stable but not yet merged upstream... the blog post mentions i can "define APPLE_USE_PMP in (my) device's Devicetree", but i don't know how to do this. is there a guide handy somewhere?#asahi · 2026-08-07 15:44
leioif it finds v4l2slh265dec doesn't support it on the hardware and v4l2 drivers being used*#asahi · 2026-08-07 15:43
leiothe debug log#asahi · 2026-08-07 15:43
leioI'm not sure how good in this situation gstreamer capabilities checks are, but in theory if you use a different video, it might use a different decoder if it finds it doesn't support it; AVD or at least the asahi impl doesn't support all cases yet afaiu, so that MIGHT gracefully be falling back to software decoding in gstreamer, but am not sure; point being, it showing v4l2slh265dec for that particular video file doesn't mean a different one would show the same in #asahi · 2026-08-07 15:41
leioif you see avdec_h265 or avdec_h264 in there, that's typically the software decoder it'd use; theoretically also openh264dec would be software, but that only supports a limited set of h264 features, so typically wouldn't work outside constrained webrtc use cases#asahi · 2026-08-07 15:40
leioif it's using v4l2slh265dec, I don't think it has any other way to be displaying you video right now than v4l2 stateless decoder, which on asahi could only be via AVD, yes :)#asahi · 2026-08-07 15:13
albinyes, and I think resource usage is pretty low, with no fans spinning (MBP M2 Pro), so I suppose hw decode works then?#asahi · 2026-08-07 15:09
leiocreating element "v4l2slh265dec" - seems to be using AVD then if it shows you video#asahi · 2026-08-07 15:08
albinhttps://pastebin.com/ME4eaMiw#asahi · 2026-08-07 15:06
leionone of those are the video decoder, you can use a pastebin service if you want me to try to find it from my end#asahi · 2026-08-07 15:06
leiothat is just the rendering sink, there should be tons more when you start playing#asahi · 2026-08-07 15:06
albinh265parse, capsfilter, avdec_aac, and more#asahi · 2026-08-07 15:05
albincreating element "gtk4paintablesink"#asahi · 2026-08-07 15:05
leioso what video decoder element did it shows as creating?#asahi · 2026-08-07 15:04
albinWhen running with GST_DEBUG... I got the same result except a lot of info logging containing GST_ELEMENT_FACTORY gstelementfactory.c:490:gst_element_factory_create_with_properties and similar#asahi · 2026-08-07 14:59
leioIf you see from that something like creating element "avdec_h265" (or avdec_h264), it's using software; if you see the v4l2sl* stuff without errors, it presumably is using hardware#asahi · 2026-08-07 14:59
leiogstreamer using app by running it with a debug env var, something like `GST_DEBUG=*FACTORY*:4 showtime path/to/file`#asahi · 2026-08-07 14:59
leioalbin: I don't have first-hand experience with that, but you need to have the necessary gstreamer elements (via plugins) available on your system, which includes v4l2slh264dec for H.264 and v4l2slh265dec for H.265, and the appropriate demuxer elements and more, so those other things would hopefully be there already if something played. You can check if you have those elements via e.g. `gst-inspect-1.0 v4l2slh264dec` and what elements are getting actually used by a #asahi · 2026-08-07 14:46
albinleio: Yes, that makes sense; so do you suggest I uninstall the software decoder packages? Will it then use the dedicated hardware directly?#asahi · 2026-08-07 14:31
leioalbsod: that's beside the point though, that aspect is mostly regarding the software decoder packages for AVC and HEVC, which is exactly what you don't want to be using anyways in your ongoing testing here.#asahi · 2026-08-07 13:06
AnEagle[m]yeah, legal issues. h264 is going to fully free in 2030#asahi · 2026-08-07 12:57
albsodyes, I suppose fedora aren't allow to make all codecs in their official distribution available#asahi · 2026-08-07 12:57
albsodthe current video I'm testing now is hvec#asahi · 2026-08-07 12:56
AnEagle[m]h264 is a bit weird on fedora#asahi · 2026-08-07 12:55
AnEagle[m]albsod: probably the multimedia group#asahi · 2026-08-07 12:55
albsodshowtime works now. I suppose that installing the new packages did something to help#asahi · 2026-08-07 12:55
AnEagle[m]If you're having an issue you can always create a bug report on the github#asahi · 2026-08-07 12:55
AnEagle[m]the 3 gstreamer video players I'm aware of are Clapper, Totem and Showtime