2023-08-17.log

- bgs (QUIT: Remote host closed the connection) (~bgs@212-85-160-171.dynamic.telemach.net)00:37
- mjw (QUIT: Ping timeout: 248 seconds) (~mjw@45.83.234.184)00:45
unixpoetI also don't see any TLS issue; the most common causes for TLS errors are either a desynced system clock or missing system packages, so look into those things01:34
- nsc (QUIT: Ping timeout: 252 seconds) (~nicolas@55-99-142-46.pool.kielnet.net)01:34
+ nsc (~nicolas@231-48-142-46.pool.kielnet.net)01:46
mhoyejosch: I'm trying one of them now, thank you.01:47
- ajr (QUIT: Quit: Connection closed for inactivity) (uid609314@user/ajr)01:51
- mtm (QUIT: Ping timeout: 252 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)02:04
violetjosch: correct, hdmi isnt working right. im on the latest kernel from the mnt debian repos02:12
violetas mentioned i can convince it to work by manually setting the status to `on` (only AFTER i plug in/turn on the monitor) and then i have to manually set it to off afterwards. so the hdmi "works" but the handling for plugging in / unplugging the cable does not02:13
violetlike at the driver level02:13
violetminute: i do still get the TLS issue yes02:14
violeti sort of wonder that i would not get the issue if i was going over ipv4 but im not sure if theres a way i can force it to go over ipv402:15
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)03:18
- nsc (QUIT: Ping timeout: 246 seconds) (~nicolas@231-48-142-46.pool.kielnet.net)03:45
+ nsc (~nicolas@56-48-142-46.pool.kielnet.net)03:48
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)04:09
- kws (PART: !!unknown attribute: msg!!) (3596bb3a9b@2604:bf00:561:2000::43f)05:09
joschviolet: it is not unlikely that i either broke something when i rebased the cadence patches on top of linux 6.407:10
joschviolet: i don't have a hdmi device at home so i cannot test myself07:10
joschand even if i could, i have no clue about kernel stuff XD07:10
joschmaybe minute can confirm your observation with hdmi on linux 6.4?07:11
joschin related news: just a few days ago, version 8 of the hdmi patch got submitted upstream: https://lore.kernel.org/all/20230808083243.3113192-1-Sandor.yu@nxp.com/07:12
+ bgs (~bgs@212-85-160-171.dynamic.telemach.net)07:27
minuteviolet: it sounds like a hw problem. can you try a different cable?10:16
violetminute: no change with different cables. additionally, my thinkpad does not have this problem12:22
violetthough- let me try to reboot, because with this other cable i DO see the "cable plug in" in dmesg correctly that i was not seeing with the other cable12:23
violetthe other cable showed "cable plug out" when i plugged it in12:23
violetso maybe its just stuck in manual mode from me using the other cable- one moment12:24
violethuh, now both cables work! maybe the cable was slightly loose in the monitor in a way where plug/unplug detection was broken but the data connections were fine?? (rebooting had not fixed it yesterday)...12:26
violetwell thats weird as hell, but ok then!12:27
joschviolet: it works now?12:27
violetyeah12:27
joschnice!!12:27
violeti guess it was just plugged in slightly badly to the monitor. whatever, im not gonna complain about it working12:28
violetunrelated, i finally got around to asking my friend to 3d print the keyboard pcb stabilizers and im quite pleased with the results12:29
violeti have 3 of them in there spread around the center and its a nice improvement to the acoustics (and has more of a noticeable effect on the typing feel than i expected tbh)12:31
violetevne with them, typing acoustics are still boomier, but eh this thing is a big box with a lot of empty space, you're just gonna have that12:32
violets/still boomier/still boomier than i'd like/12:32
violetimportant thing is it doesnt immediately feel misophonic to me the way it did previously, especially if i have headphones in12:33
* mark_ -> mjw12:41
joschi'm still experimenting with different brace designs: https://mister-muffin.de/p/MxMH.png12:52
joschi liked the idea to press it against the bottom acrylic12:53
vkoskivCurious bug yesterday, I was at roughly ~33% battery, plugged in to charge, and it jumped to 100% immediately13:34
vkoskivIt was still charging, but the amperage was dropping like it was nearing the end of a charge13:34
vkoskivWeird thing is that all the cells seem to be at voltages that don't indicate 33% :D13:35
vkoskivI'll just do a drain/charge cycle to recalibrate.13:35
- mtm (QUIT: Ping timeout: 260 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)14:02
- bgs (QUIT: Remote host closed the connection) (~bgs@212-85-160-171.dynamic.telemach.net)14:02
+ andreas-e (~Andreas@2001:861:c4:f2f0::c64)14:23
joschoh great, data breach at nxp.com14:24
sevanjosch: hopefully it's all the NDA'd documentation?14:34
joschhahaha :)14:38
+ mtm (~mtm@71.228.84.213)16:08
+ marty_mcfly88 (~marty@2603-6000-8c01-0f3e-83a3-2225-dc4f-48ea.res6.spectrum.com)16:29
- marty_mcfly88 (QUIT: Remote host closed the connection) (~marty@2603-6000-8c01-0f3e-83a3-2225-dc4f-48ea.res6.spectrum.com)16:30
- arminweigl (QUIT: Ping timeout: 245 seconds) (~arminweig@sourcehut/user/arminweigl)17:18
mjwminute, is that a giant inflatable rocketship?17:47
mjwApparently I should know that (but don't). Lots of pictures of it here https://commons.wikimedia.org/wiki/Category:Fairydust17:52
+ mark_ (~mjw@45.83.234.184)18:00
joschmjw: last time i was there it felt quite solid -- not really inflatable :)19:10
+ ajr (uid609314@user/ajr)19:45
- GNUmoon (QUIT: Ping timeout: 246 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon)20:31
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)20:34
- jacobk (QUIT: Ping timeout: 246 seconds) (~quassel@47-186-105-85.dlls.tx.frontiernet.net)21:31
- mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@45.83.234.184))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)21:32
* mark_ -> mjw21:32
+ mark_ (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)21:33
+ TerminalPanic (~term@5.13.169.217.in-addr.arpa)21:51
+ jacobk (~quassel@2603-8080-b200-7b02-77cb-6304-f9db-dda1.res6.spectrum.com)22:30
- andreas-e (QUIT: Quit: Leaving) (~Andreas@2001:861:c4:f2f0::c64)22:43
- TerminalPanic (QUIT: Ping timeout: 245 seconds) (~term@5.13.169.217.in-addr.arpa)22:45
- jacobk (QUIT: Ping timeout: 246 seconds) (~quassel@2603-8080-b200-7b02-77cb-6304-f9db-dda1.res6.spectrum.com)23:01
+ TerminalPanic (~term@5.13.169.217.in-addr.arpa)23:19
- TerminalPanic (QUIT: Client Quit) (~term@5.13.169.217.in-addr.arpa)23:22
+ TerminalPanic (~term@5.13.169.217.in-addr.arpa)23:25
- Asmadeus (QUIT: Ping timeout: 246 seconds) (~asmadeus@240b:13:8c80:d300::42:13)23:34
+ Asmadeus (~asmadeus@240b:13:8c80:d300::42:13)23:44
- TerminalPanic (QUIT: Ping timeout: 246 seconds) (~term@5.13.169.217.in-addr.arpa)23:58

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