#
…

2023-11-28

00:07leif has joined #asahi
00:16leif is now known as leif_s
00:18leif_s has quit [Quit: leif_s]
00:18rndm has joined #asahi
00:23rndm has quit [Remote host closed the connection]
00:24kidplayer666 has quit [Quit: Connection closed for inactivity]
00:25rndm has joined #asahi
00:25leif has joined #asahi
00:40i509vcb has joined #asahi
00:57pounce has quit [Ping timeout: 480 seconds]
01:03pounce has joined #asahi
01:27jmr2 has joined #asahi
01:37jmr2mps/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.
01:38jmr2 has quit [Quit: Page closed]
01:42Brainium has quit [Quit: Konversation terminated!]
02:19possiblemeatball has joined #asahi
02:33leif has quit [Quit: leif]
03:16rvalue has quit [Ping timeout: 480 seconds]
03:17ptudor has joined #asahi
03:21ptudor_ has quit [Ping timeout: 480 seconds]
03:26hightower3 has joined #asahi
03:33hightower2 has quit [Ping timeout: 480 seconds]
03:47rvalue has joined #asahi
04:14crabbedhaloablut has joined #asahi
04:14jeisom has quit [Read error: Connection reset by peer]
04:14jeisom has joined #asahi
04:25i509vcb has quit [Quit: Connection closed for inactivity]
04:28tbodt has quit []
04:28tbodt has joined #asahi
04:32jeisom has quit [Ping timeout: 480 seconds]
04:40possiblemeatball has quit [Quit: Quit]
04:56marvin24_ has joined #asahi
04:59marvin24 has quit [Ping timeout: 480 seconds]
06:54kidplayer666 has joined #asahi
06:55veebop has joined #asahi
06:57beevop has joined #asahi
06:58beevop has quit []
07:02elvishjerricco has quit [Read error: No route to host]
07:03elvishjerricco has joined #asahi
07:04capta1nt0ad has joined #asahi
07:35richyliu2 has quit [Ping timeout: 480 seconds]
07:39richyliu2 has joined #asahi
08:11cisco87 has quit [Quit: No Ping reply in 180 seconds.]
08:24capta1nt0ad has quit [Ping timeout: 480 seconds]
08:33pjakobsson_ has quit [Ping timeout: 480 seconds]
08:36capta1nt0ad has joined #asahi
08:54capta1nt0ad has quit [Remote host closed the connection]
08:55capta1nt0ad has joined #asahi
09:04kidplayer666 has quit [Quit: Connection closed for inactivity]
09:18capta1nt0ad has quit [Ping timeout: 480 seconds]
09:22zealouscupuacu has joined #asahi
09:41ten15723774324 has quit [Remote host closed the connection]
09:42ten15723774324 has joined #asahi
10:02kidplayer666 has joined #asahi
10:11ten15723774324 has quit [Remote host closed the connection]
10:11ten15723774324 has joined #asahi
10:16jmplans_ has quit [Ping timeout: 480 seconds]
10:17jadesoturi_ has joined #asahi
10:19jadesoturi has quit [Ping timeout: 480 seconds]
10:58b03481824694f37ce3a7003bdc4aa9 has quit []
11:04capta1nt0ad has joined #asahi
11:13capta1nt0ad has quit [Ping timeout: 480 seconds]
11:18russelltg has quit [Quit: Connection closed for inactivity]
11:19RoguePlanet has joined #asahi
11:19RoguePlanet has quit []
11:20luna has joined #asahi
11:22luna has left #asahi [#asahi]
11:43Moprius has joined #asahi
11:59Brainium has joined #asahi
12:31ydalton has joined #asahi
12:33ydaltonany plans to support an immutable variant of fedora asahi? something like fedora silverblue
12:35j`eyeric curtin has started to look into it
12:35ydaltoncuz i just nuked my system by a mistake that would have probably been prevented had i been using an immutable distro
12:36j`eyit uses osbuild (current images use kiwi)
12:36ydaltonfor building images?
12:36j`eybut I guess it shouldnt matter too much
12:39j`eyalso https://pagure.io/fedora-asahi-remix-ostree which is based on how I think the normal silverblue etc images are built
12:41ydaltonwould be a lovely thing to try out
12:41ydaltonsince afaik it's closer to what macOS does
12:42j`eyyeah Im interested in it too (why I know all these links :P)
12:43ydaltoni mean you seem to know all the links for everything asahi
12:44sventhere's also nixos which takes this a step further I think
12:44jmplans has joined #asahi
12:52ydaltonafaik nixos uses a config file for systems but it's not immutable?
12:53FoxboronNot in the ostree-sense, it's not.
12:53FoxboronBut you can do snapshots between config changes and have some rollback support, so it sorta works in the same way
13:02ydaltonnixos uses images?
13:09arydalton: usually not. you can generate system full system images with nixos, but that's not the way it's typically used
13:14Szadek6367 has joined #asahi
13:14jeisom has joined #asahi
13:16arydalton: and while /nix/store (directory where nix persistently stores all of the configuration files/packages/whatever) isn't immutable per-se, it's made readonly for normal processes/users, including root (through namespacing magic). and while you can do, essentially, "mount -o remount,rw /nix/store", it requires conscious attempt at doing so
13:21Szadek636 has quit [Ping timeout: 480 seconds]
13:24darkapex1 has quit [Ping timeout: 480 seconds]
13:25jeisom has quit [Quit: Leaving]
13:28arnot sure how updating/changing configurations works with ostree. it generates whole system images every time?
13:29arif so, nixos is a bit more flexible. (grossly simplifying stuff for clarity) configuration changes and updates create "generations", every "generation" has references to all packages, configuration files and so on that it uses; different generations can reference the same packages/generated configuration files and such from /nix/store if they're identical; you can switch between
13:29argenerations at runtime (to certain extent; IIRC generation changes that would require systemd downgrade can fail), or even just within a given shell/interactive session to test things out.
13:31nicolas17 has quit [Ping timeout: 480 seconds]
13:31j`eyar: ostree (AFAIU) has hardlinks, so each new image shouldnt take up double the space
13:32j`eybut now Im not sure how that works if you download a new image for an update.. some magic I guess
13:36arif so, probably ends up using less disk space than nixos then. determining if things are "identical" in nix/nixos sense is a bit more involved and takes into account also identicality of all dependencies a thing has. hardlinks can be used to reduce disk space usage, but many things have things like paths from /nix/store in them
14:05Moprius has quit [Quit: bye]
14:12j`eyDannyB: hey, can you join #asahi-alt?
14:21ml| has quit [Ping timeout: 480 seconds]
14:29john-cabaj has joined #asahi
14:31ml| has joined #asahi
14:41FoxboronIt's probably easier to explain nixos as a symlink farm, that also rewrites rpath in binaries
14:42FoxboronIt's not.. an elegant solution when you peak under the hood
14:46Brainium has quit [Quit: Konversation terminated!]
14:49nicolas17 has joined #asahi
14:57ydalton has quit [Remote host closed the connection]
15:04delsol has joined #asahi
15:06possiblemeatball has joined #asahi
15:12darkapex1 has joined #asahi
15:42pounce has quit [Ping timeout: 480 seconds]
15:53pounce has joined #asahi
15:53nimprod3l has joined #asahi
16:33possiblemeatball has quit [Remote host closed the connection]
16:36possiblemeatball has joined #asahi
16:42possiblemeatball has quit [Remote host closed the connection]
16:54delsol has quit [Remote host closed the connection]
17:02delsol has joined #asahi
17:04pounce has quit [Ping timeout: 480 seconds]
17:06pounce has joined #asahi
17:13zealouscupuacu has quit [Ping timeout: 480 seconds]
17:17pounce has quit [Ping timeout: 480 seconds]
17:39pounce has joined #asahi
17:42delsol has quit [Remote host closed the connection]
17:51pounce has quit [Ping timeout: 480 seconds]
17:57ihaveamac has quit [Quit: fail]
17:59ihaveamac has joined #asahi
18:03delsol has joined #asahi
18:03pounce has joined #asahi
18:05elvishjerricco has quit [Ping timeout: 480 seconds]
18:16nimprod3l has quit [Read error: Connection reset by peer]
18:17nimprod3l has joined #asahi
18:20nyx_o has quit [Ping timeout: 480 seconds]
18:28pounce has quit [Ping timeout: 480 seconds]
18:29chaxor has joined #asahi
18:32chaxor has quit []
18:39chaxor has joined #asahi
18:43chaxorIs there a way to get the brightness backlight changing capabilities of "org.kde.powerdevil.backlighthelper" from the plasma desktop install, but on the minimal setup? I am interested in making a simpler system on awesomewm (or sway if wayland is required / preferred), but battery life is one of the most important aspects of a mac laptop experience (>40h work time is the goal), so very low backlight
18:43chaxorcapability and hibernation is key.
18:44chaxorUnfortunately at the moment 'powerdevil' ends up installing essentially the entire KDE plasma workspace for some reason.
18:45j`eychaxor: what exactly does that do? You can just change the backlight manually
18:45Brainium has joined #asahi
18:52PaulFertserchaxor: yes, just write whatever you want to /sys/class/backlight/*/brightness or wdym?
18:54j`eybetter yet you can use dbus to do it as non-super-user
18:54chaxorAh, I think I see the issue. I installed the plasma and removed it with 'pacman -Rns (kde/plasma stuff)'. That seemed to remove all devices and files in /sys/class/backlight . Perhaps the minimal install includes this /sys/class/backlight/* files? (Perhaps not?)
18:55j`eyuh, they should be there
18:55j`eyoh, archlinux..
18:55j`eychaxor: I would suggest using fedora, the arch variant is not as well maintained
18:55j`eybut if you have to use arch, you need the -edge linux package, to get the backlight
18:56chaxorInstalling the entire plasma kde desktop again adds those files back again so the brightness can be changed by altering those files. Perhaps I can try to remove everything again and *somehow* (?) keep the backlight files to adjust and look into hibernate as well
18:57j`eythat doesnt make sense, those files are from the kernel
18:57PaulFertserchaxor: everything in /sys is provided by the kernel, that's not affected by any userspace you install.
18:57nicolas17they are not files installed by a package, they are pseudo-files created at runtime by the kernel
18:57j`eyplasma doesnt add those
18:57nicolas17they don't exist on disk
18:57chaxorOK thanks, I haven't tried fedora and am more familiar with arch, but suppose it's worth a shot. I'm on edge now.
18:57PaulFertserProbably it's some subdirectory in graphics/drm etc, try find /sys -name backlight
18:58chaxorPaulFertser you mean when switching to sway? They show up on plasma
18:59nicolas17I suppose it's possible that removing plasma also removes or unloads some kernel module that takes care of the backlight sys files
18:59j`ey'show up on plasma'?
18:59nicolas17but even that is a stretch
18:59j`eychaxor: just try find them from the terminal, it shouldnt matter if plasma is there or not
19:00chaxoryeah this is indeed strange. They werent there on sway, show up when getting into plasma. No idea why. I used the grub update way before and did many things in sway and awesomewm without seeing them. Started up plasma and now they're there which is odd
19:00chaxoryeah from terminal just using ls
19:01j`eydid you upgrade to edge before or after installing sway?
19:06chaxorI think it was install full plasma asahi -> install awesomewm immediately -> switch into awesomewm and delete kde/plasma things -> install sway (thought it was wayland issue potentially) -> install edge -> try many things over several days to get backlight change or suspend/hibernate (including powerdevil) -> just installed plasma and switched into it and the GUI stuff on the bar 'just works'. Perhaps I
19:06chaxorcan just keep all the KDE junk sitting around and not use it, and just set the backlight file in sway if it stays there.
19:07j`eyright, we dont know what you tried to get the backlight working on sway/awesome
19:07j`eybut it was working *after* you installed edge
19:07j`eytry this: busctl call org.freedesktop.login1 /org/freedesktop/login1/session/auto org.freedesktop.login1.Session SetBrightness ssu backlight apple-panel-bl 20
19:07chaxorOh maybe you mean sway needs to be installed after update grub due to some linking issues? I don't know a lot about kernel things really
19:08j`eyafter you installed edge, that's when you got backlight support, and the above command should work
19:10chaxoryeah that works and seems to be similar to echo '20' | sudo tee /sys/class/backlight/apple-panel-bl/brightness
19:11chaxor has quit [Quit: Lost terminal]
19:11j`eyright, so brightness is working
19:13chaxor has joined #asahi
19:14chaxorOK just switched into sway and the echo / tee command into the backlight works now
19:14j`eymy guess is that you were trying on sway before installing edge
19:15chaxorJust had to install plasma/kde/powerdevil and login to it for some strange reason I guess? Yeah perhaps that was it too
19:15j`eyit's definitely unrelated to the plasma thing
19:15chaxorI'll try removing plasma stuff again and see if it sticks
19:15chaxorThank you!
19:15j`eyhibernation doesnt work, only 's2idle'
19:16chaxordoes that persist to disk? I got suspend which takes 2% per hour unfortunately
19:16chaxorI'll go read up on it
19:17nicolas17it doesn't persist to disk
19:17j`eys2idle is suspend
19:18nicolas17afaik neither hibernate nor suspend work, "s2idle" is basically "pause all userspace processes" and not a *full* sleep (but Apple Silicon is so efficient that it's actually pretty low power usage)
19:18nicolas17I'm not sure if macOS is actually doing deep-sleep of the SoC?
19:21PaulFertserOne can use "powertop" to see how many wake ups how often are caused by which processes. s2idle is that kind of suspend where all of them are fully stopped.
19:33delsol has quit [Remote host closed the connection]
19:39chaxor has quit [Remote host closed the connection]
19:56ydalton has joined #asahi
20:02ydaltonnice, libvirt seems to work out of the box in fedora asahi 39
20:11pounce has joined #asahi
20:16ydalton has quit [Remote host closed the connection]
20:16ydalton has joined #asahi
20:25nimprod3l has quit [Ping timeout: 480 seconds]
20:34pounce has quit [Ping timeout: 480 seconds]
20:35crabbedhaloablut has quit []
20:44ydaltonwhat's holding back gpu acceleration support in flatpaks? i thought the asahi mesa drivers were already included in mainline mesa
20:44leioflatpak SDKs provide mesa
20:45j`eyydalton: probably old versions
20:45leiothere was some chatter in GNOME about it, don't remember where it went
20:47ydaltonleio: that makes sense, cuz i don't see mesa among my flatpaks whereas i had them before
20:49leioiirc they are in freedesktop SDKs
20:49leiothere's support for extensions of some kind, maybe it'd be possible to ship it that way as an add-on sort of thing
20:49ydaltonyep, i launched a shell inside one of the flatpaks and there was no apple_dri.so in `/usr/lib64/dri`
20:49jannegwhile most of the code is in mainline mesa the UAPI code is not as long as the kernel driver is not (about to) merged
20:53ydaltonjanneg: well that shouldn't matter right? the only ones (presumably) using the mesa asahi drivers are using the asahi kernel anyways
20:53ydaltonas for flatpaks, does it mean every single flatpak needs to be recompiled to have `asahi_dri.so`?
20:55jannegno, the idea is to build flatpak host extension and install that as package
20:56elvishjerricco has joined #asahi
20:58ydaltoni dunno if i did it right, because i tried building that myself but it didn't make a difference
20:59j`eybuild and installed?
21:01ydaltonwell it was listed when i did `flatpak list`
21:03ydaltoni'll try building it again
21:13j`eyydalton: did you check out the right tag of mesa?
21:15Brainium_ has joined #asahi
21:15Brainium_ has quit []
21:21Brainium has quit [Ping timeout: 480 seconds]
21:21ydalton has quit [Remote host closed the connection]
21:21Moprius has joined #asahi
21:21ydalton has joined #asahi
21:25ydaltonit seems to be cloning libdrm from mesa but fetching a tarball from asahi/mesa
21:26j`eyydalton: dont you have to check it out manually?
21:27elvishjerricco has quit [Remote host closed the connection]
21:27ydaltonwdym, switch to a different branch?
21:28blazra3 has joined #asahi
21:28j`eyydalton: did you download mesa, or did it happen automatically?
21:29ydaltoni ran a command `flatpak build-dir <file>.yml` and it started building the flatpak automatically
21:30blazra has quit [Remote host closed the connection]
21:30blazra3 is now known as blazra
21:30j`eyinteresting, to me it looks like you need to get the tarball manually, but maybe theres some magic
21:32j`eyah, the 'main' branch of mesa-asahi-flatpak checks out the tarball automatically
21:34ydaltoni think i need to check out this branch
21:34ydaltoni was linked to a different branch
21:42elvishjerricco has joined #asahi
21:45eichin__ has quit [Read error: Network is unreachable]
21:45mustache_ride______ has quit [Read error: Network is unreachable]
21:45qyousef has quit [Write error: connection closed]
21:45mustache_ride______ has joined #asahi
21:45eichin__ has joined #asahi
21:45qyousef has joined #asahi
21:46kuruczgy has quit [Read error: Connection reset by peer]
21:46bendodroid has quit [Read error: Connection reset by peer]
21:46asimpson has quit [Read error: Connection reset by peer]
21:46gpanders has quit [Read error: Connection reset by peer]
21:46wa9ace has quit [Read error: Connection reset by peer]
21:46brettgilio has quit [Remote host closed the connection]
21:46d4ve has quit [Read error: Connection reset by peer]
21:46coder_kalyan has quit [Read error: Connection reset by peer]
21:46signaryk has quit [Read error: Connection reset by peer]
21:46alethkit has quit [Write error: connection closed]
21:46handlerug has quit [Write error: connection closed]
21:46swapgs has quit [Write error: connection closed]
21:46probie has quit [Write error: connection closed]
21:46mrCyborg has quit [Write error: connection closed]
21:46akspecs has quit [Write error: connection closed]
21:46dorkbutt has quit [Write error: connection closed]
21:46pitust has quit [Write error: connection closed]
21:46okt has quit [Write error: connection closed]
21:46jleightcap has quit [Write error: connection closed]
21:46patwid has quit [Write error: connection closed]
21:46tsujp has quit [Write error: connection closed]
21:46z812 has quit [Write error: connection closed]
21:46rosefromthedead has quit [Write error: connection closed]
21:46pldtf has quit [Write error: connection closed]
21:46shinobi57474858 has quit [Remote host closed the connection]
21:46jfy has quit [Write error: connection closed]
21:46ella-0 has quit [Write error: connection closed]
21:46cds has quit [Write error: connection closed]
21:46dubiousness has quit [Write error: connection closed]
21:46johnhamelink has quit [Write error: connection closed]
21:46elvishjerricco has quit [Remote host closed the connection]
21:46asimpson has joined #asahi
21:46cds has joined #asahi
21:46probie has joined #asahi
21:46z812 has joined #asahi
21:46wa9ace has joined #asahi
21:46swapgs has joined #asahi
21:46tsujp has joined #asahi
21:46brettgilio has joined #asahi
21:46bendodroid has joined #asahi
21:46gpanders has joined #asahi
21:46coder_kalyan has joined #asahi
21:46okt has joined #asahi
21:46signaryk has joined #asahi
21:46kuruczgy has joined #asahi
21:46mrCyborg has joined #asahi
21:46handlerug has joined #asahi
21:46pitust has joined #asahi
21:46rosefromthedead has joined #asahi
21:46dorkbutt has joined #asahi
21:46alethkit has joined #asahi
21:46johnhamelink has joined #asahi
21:46akspecs has joined #asahi
21:46pldtf has joined #asahi
21:46shinobi57474858 has joined #asahi
21:46dubiousness has joined #asahi
21:46jfy has joined #asahi
21:46ella-0 has joined #asahi
21:46d4ve has joined #asahi
21:46patwid has joined #asahi
21:46jleightcap has joined #asahi
21:46esden has quit [Ping timeout: 480 seconds]
21:47esden has joined #asahi
21:49ydaltonugh, this is so much work, i think i will leave it be
21:49ydaltonor get to it another day
21:56Brainium has joined #asahi
22:00delsol has joined #asahi
22:05jole has quit [Remote host closed the connection]
22:05jole has joined #asahi
22:07kidplayer666I have been getting a really weird issue from time to time. (both on gnome and kde). During normal usage, without too much open, the swap randomly starts getting filled, and closing apps only mitigates the issue, as the swap starts filling up again, even with everything closed. Weird part is, htop says RAM consumption is pretty low, being filled mostly with cached data.
22:07kidplayer666it leads to a system freeze if left unchecked, and i need to force a shutdown
22:08jole has quit [Remote host closed the connection]
22:08jole has joined #asahi
22:20nicolas17"sudo smem -s swap" will show processes sorted by swap usage
22:20kidplayer666Next time this happens
22:20kidplayer666Problem is that I don’t have much time
22:20kidplayer666Between noticing the issue
22:21kidplayer666And it crashing
22:28ydaltonnow that i think about it, can't you check htop to see ram usage per process?
22:28kidplayer666 Not sure regarding swap tho
22:28kidplayer666I just gotta try it out next time it happens
22:28kidplayer666Problem really is replicating
22:32kidplayer666(To me the mildly competent user, obviously)
22:35ydalton has left #asahi [ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.0.92)]
22:35ydalton has joined #asahi
22:39jeisom has joined #asahi
22:50Moprius has quit [Quit: bye]
22:51delsol has quit [Remote host closed the connection]
22:54kidplayer666(To the devs, it’s actually finding where the issue is and getting a fix)
23:05ydalton has quit [Ping timeout: 480 seconds]
23:13so101 has joined #asahi
…