2025-03-08.log

- glu_ (QUIT: Remote host closed the connection) (~glu@user/glu)00:07
- wytch (QUIT: Quit: Leaving.) (~wytch@user/wytch)00:08
minutegrimmware: woop, need to update00:31
- chomwitt (QUIT: Ping timeout: 260 seconds) (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)00:34
+ glu_ (~glu@user/glu)00:40
+ robin_ (~robin@user/terpri)00:46
- robin (QUIT: Ping timeout: 260 seconds) (~robin@user/terpri)00:49
- glu_ (QUIT: Ping timeout: 265 seconds) (~glu@user/glu)01:28
+ glu_ (~glu@user/glu)01:32
+ robin__ (~robin@user/terpri)02:01
- robin_ (QUIT: Ping timeout: 252 seconds) (~robin@user/terpri)02:04
- glu_ (QUIT: Ping timeout: 260 seconds) (~glu@user/glu)02:12
+ bkeys (~Thunderbi@50.96.248.167)02:37
- bkeys (QUIT: Remote host closed the connection) (~Thunderbi@50.96.248.167)02:50
+ bkeys (~Thunderbi@50.96.248.167)02:51
- nsc (QUIT: Ping timeout: 246 seconds) (~nicolas@i5C74DF7A.versanet.de)03:20
+ nsc (~nicolas@i5C74DE17.versanet.de)03:22
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org)03:35
- paperManu (QUIT: Ping timeout: 272 seconds) (~paperManu@107.159.71.33)03:38
- Ar|stote|is (QUIT: Ping timeout: 252 seconds) (~linx@149.210.20.81)04:24
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@50.96.248.167)04:29
+ bkeys1 (~Thunderbi@50.96.248.167)04:29
* bkeys1 -> bkeys04:31
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)05:11
- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)07:17
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)07:18
+ Ar|stote|is (~linx@149.210.11.180)07:38
- Ar|stote|is (QUIT: Ping timeout: 252 seconds) (~linx@149.210.11.180)08:11
+ glu_ (~glu@user/glu)09:40
+ gustav28 (~gustav@c-78-82-52-230.bbcust.telenor.se)10:02
- jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)10:04
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)10:05
- networkstring (QUIT: Quit: ZNC 1.8.2+deb3.1 - https://znc.in) (~networkst@2001:67c:2b44:100:2ecf:67ff:fe27:2be5)10:41
- mesaoptimizer (QUIT: Quit: WeeChat 4.0.4) (~mesa@user/PapuaHardyNet)11:27
+ mesaoptimizer (~mesa@user/PapuaHardyNet)11:27
- mesaoptimizer (QUIT: Quit: WeeChat 4.0.4) (~mesa@user/PapuaHardyNet)11:41
+ mesaoptimizer (~mesa@user/PapuaHardyNet)11:42
- mesaoptimizer (QUIT: Client Quit) (~mesa@user/PapuaHardyNet)11:42
+ mesaoptimizer (~mesa@user/PapuaHardyNet)11:43
- mesaoptimizer (QUIT: Client Quit) (~mesa@user/PapuaHardyNet)11:45
+ mesaoptimizer (~mesa@user/PapuaHardyNet)11:45
- mesaoptimizer (QUIT: Client Quit) (~mesa@user/PapuaHardyNet)11:46
+ mesaoptimizer (~mesa@user/PapuaHardyNet)11:46
- mesaoptimizer (QUIT: Client Quit) (~mesa@user/PapuaHardyNet)11:46
+ mesaoptimizer (~mesa@user/PapuaHardyNet)11:55
- mesaoptimizer (QUIT: Quit: WeeChat 4.0.4) (~mesa@user/PapuaHardyNet)12:07
+ mesaoptimizer (~mesa@user/PapuaHardyNet)12:07
- mesaoptimizer (QUIT: Client Quit) (~mesa@user/PapuaHardyNet)12:12
+ mesaoptimizer (~mesa@user/PapuaHardyNet)12:13
- mesaoptimizer (QUIT: Client Quit) (~mesa@user/PapuaHardyNet)12:14
+ mesaoptimizer (~mesa@user/PapuaHardyNet)12:15
- mesaoptimizer (QUIT: Client Quit) (~mesa@user/PapuaHardyNet)12:15
+ mesaoptimizer (~mesa@user/PapuaHardyNet)12:17
- mesaoptimizer (QUIT: Client Quit) (~mesa@user/PapuaHardyNet)12:21
+ chomwitt (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)12:25
+ mesaoptimizer (~mesa@user/PapuaHardyNet)12:29
- mesaoptimizer (QUIT: Client Quit) (~mesa@user/PapuaHardyNet)12:29
- chomwitt (QUIT: Ping timeout: 252 seconds) (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)12:29
+ mesaoptimizer (~mesa@user/PapuaHardyNet)12:39
- mtm (QUIT: Ping timeout: 272 seconds) (~textual@47.202.75.129)13:04
+ mtm (~textual@47.202.75.129)13:06
+ mjw (~mjw@gnu.wildebeest.org)13:15
+ paperManu (~paperManu@107.159.71.33)13:29
- mesaoptimizer (QUIT: Quit: WeeChat 4.0.4) (~mesa@user/PapuaHardyNet)13:32
+ mesaoptimizer (~mesa@user/PapuaHardyNet)13:35
minutegrimmware: i also have the oscillation/slight flicker on grey now, but i think in my case it is because i didn't notice that the pocket didn't fully shut down last night. the reason is i only installed the kernel image package but not the headers/sources so reform2-lpc didn't get rebuilt for this test kernel. so the computer was on all night in this limbo state and then i power cycled it a few13:41
minuteminutes ago.13:41
grimmwareI rebuilt the lpc but on an older branch, I’ll give it a go on main when I get home and see if it fixes it14:36
grimmwareWhat’s the interaction with the lpc that impacts here?14:36
chthe lpc driver tells the sysctl to power off15:33
chwhen its not there, that doesnt work :)15:33
- gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-52-230.bbcust.telenor.se)15:55
- bkeys (QUIT: Remote host closed the connection) (~Thunderbi@50.96.248.167)16:04
+ bkeys (~Thunderbi@h167.248.96.50.static.ip.windstream.net)16:04
- qbit (QUIT: Remote host closed the connection) (~qbit@user/qbit)16:12
minutegrimmware: yep, what ch said. and when remaining in "not fully turned off state", the display gets unhappy16:19
+ qbit (~qbit@user/qbit)16:26
- MyNetAz (QUIT: Remote host closed the connection) (~MyNetAz@user/MyNetAz)16:31
+ MyNetAz (~MyNetAz@user/MyNetAz)16:43
chkernel seems good to me from a very brief test16:56
- glu_ (QUIT: Ping timeout: 244 seconds) (~glu@user/glu)17:19
minutei made kind of a long post about or impending new approach for GNOME integration https://community.mnt.re/t/gnome-integration-notes-issue-tracking/3168 cc josch17:21
+ gustav28 (~gustav@c-78-82-54-147.bbcust.telenor.se)17:29
josch"Link to discussion in mutter Gitlab: Making sure you're not a bot!" haha :D17:41
joschminute: "As sleep/resume is broken on all our current platforms" -- suspend/resume works fine for me on imx8mq ;)17:42
minutejosch: oh right, i should add that, thanks :D17:42
joschlooks like a lot of pocket specific stuff -- a couple of these things probably have to be set up by reform-setup-wizard instead of being shipped in /etc/skel because the latter will also be deployed on non-pocket platforms17:47
joschif reform-setup-wizard is the wrong place, we can extend the firstboot systemd unit to do more device specific setup on first boot17:47
minutejosch: reform-setup-wizard is probably an OK location for this17:55
joschhrm...17:57
joschthis also gets me thinking...17:57
joschwe moved /etc/skel from reform-tools to reform-system-image because dumping stuff into /etc makes it a config file and thus harder to change with package upgrades17:57
joschthe downside to that approach is, that now users need to check the reform-system-image git to see the current defaults17:58
joschwhat if we moved /etc/skel from reform-system-image back to reform-tools but install the directory structure into /usr/share/reform-tools under a machine-specific path?17:58
joschand then reform-setup-wizard just picks the correct /usr/share/reform-tools/skel directory depending on the platform it is running on17:59
joschthis allows reform-setup-wizard to remain relatively stable as we keep putting device-specific "hacks" into reform-tools instead of having it spread across different packages18:00
minutejosch: sounds good!18:03
joschanother motivation for having skel back into reform-tools is, that this would help other distros packaging reform-tools to also ship these 18:04
joschalso nice to see kicad casually running in the back on your rk3588 reform -- opening the motherboard 2.5 pcb on a311d to figure out my power draw issues is... an experience...18:05
minutejosch: yeah, i actually just did real work on the reform next motherboard on this machine, and it was almost no difference in perf to my i9-9900 desktop with a radeon gpu...18:14
minutejosch: i.e. this: https://mastodon.social/@mntmn/114127928098101903 but it's a smaller board than the classic reform motherboard.18:15
joschzsh: segmentation fault  kicad nref-motherboard/nref-motherboard.kicad_pro18:18
joschwell, kicad tried XD18:18
minuteaww.. is it kicad 9 already? 9 seems to work better18:19
joschgood point -- kicad 9 got uploaded to backports a few days ago... lets try...18:21
joschwow, massive difference!18:26
joschnow even motherboard 2.5 loads in a few seconds and is actually okay for browsing the schematic18:26
minutegreat18:35
joschminute: to figure out the list of required dconf schema settings, you diff the output of "gsettings list-recursively" against the default or how do you plan to do this? Is that something you do or I do?18:45
- amospalla (QUIT: Quit: WeeChat 4.5.1) (~jordi@user/amospalla)18:52
- Gooberpatrol66 (QUIT: Ping timeout: 260 seconds) (~Gooberpat@user/gooberpatrol66)19:02
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)19:06
* robin__ -> robin19:45
- helgoman_ (QUIT: Ping timeout: 248 seconds) (~helgoman@adsl-178-38-58-229.adslplus.ch)20:05
+ helgoman__ (~helgoman@5.180.61.45)20:05
- helgoman__ (QUIT: Client Quit) (~helgoman@5.180.61.45)20:05
minutejosch: i think i would probably manually look at gsettings but the diffing and then cherry picking sounds like a good idea20:07
minutei wonder when this is gonna land in debian :3 https://github.com/amazingfate/chromium-debian-build/blob/really-fix-libsync/debian/patches/fixes/libsync-rk3588-panthor.patch20:07
+ glu_ (~glu@user/glu)20:14
- glu_ (QUIT: Ping timeout: 248 seconds) (~glu@user/glu)21:10
+ glu_ (~glu@user/glu)21:10
- glu_ (QUIT: Read error: Connection reset by peer) (~glu@user/glu)21:38
+ glu_ (~glu@user/glu)21:39
- glu_ (QUIT: Ping timeout: 265 seconds) (~glu@user/glu)21:44
- gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-54-147.bbcust.telenor.se)22:15
+ Ar|stote|is (~linx@149.210.16.94)22:21
+ BoostisBetter (4a410829d7@irc.cheogram.com)22:27
+ chomwitt (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)22:43
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)23:06
- gordon1 (QUIT: Remote host closed the connection) (~gordon1@citadel.niflheim.info)23:12
+ glu_ (~glu@user/glu)23:13
joschminute: for rk3588, imx8mp and a311d we have set the EMMC_BOOT variable to "warn" so that users who want to flash u-boot onto their eMMC have to first read and explicitly agree to a warning message telling them that they may soft-brick their device if something goes wrong.23:28
joschminute: the BPI-CM4 platform is the only one who has EMMC_USE variable set to "false", completely forbidding use of eMMC for writing the /boot partition (not u-boot) to23:29
joschminute: should EMMC_USE also become a tri-state variable and be set to "warn" on BPI-CM4 just as is already the case for EMMC_BOOT?23:30

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!