2025-02-10.log

+ Guest15 (~Guest15@50.37.92.249)00:00
+ aloo_shu_ (~aloo_shu@85.51.17.248)00:00
- Guest15 (QUIT: Client Quit) (~Guest15@50.37.92.249)00:00
- aloo_shu (QUIT: Ping timeout: 246 seconds) (~aloo_shu@85.51.18.130)00:03
* aloo_shu_ -> aloo_shu00:03
+ bkeys (~Thunderbi@h167.248.96.50.static.ip.windstream.net)00:15
hramrachaccount is needed also for matrix, discord, slack, ... and most liber channels when it comes to that00:16
L29Ahxmpp has anonymous logins00:17
L29Ahand room history00:17
hramrachxmpp has everything but you also have to ask which clients support it00:18
hramrachsomewhat similar to the USB C situation00:19
L29Ahto support anonymous logins, a client must not reject the user when they put nothing in the boxes00:20
L29Ahmuc history backlog is supported by every client that supports muc themselves, so pretty much every IM-oriented one00:20
kfxlibera.chat also supports the ircv3 ChatHistory request; would be pretty simple to patch in to the default client00:45
kfxcan also use chanserv to set a join message explaining that it can take a while for others to be present and respond00:48
- mtm (QUIT: Ping timeout: 244 seconds) (~textual@47.202.75.129)01:04
+ mtm (~textual@47.202.75.129)01:06
- MyNetAz (QUIT: Remote host closed the connection) (~MyNetAz@user/MyNetAz)01:17
+ MyNetAz (~MyNetAz@user/MyNetAz)01:28
+ aloo_shu_ (~aloo_shu@85.51.16.20)01:48
- aloo_shu (QUIT: Ping timeout: 268 seconds) (~aloo_shu@85.51.17.248)01:51
* aloo_shu_ -> aloo_shu01:51
ajrkfx: libera supports chathistory? https://ircv3.net/support/networks02:05
- paperManu (QUIT: Ping timeout: 268 seconds) (~paperManu@107.159.71.33)02:48
kfxajr: https://github.com/Libera-Chat/sable/issues/12002:54
- cobra (QUIT: Ping timeout: 252 seconds) (~cobra@user/Cobra)03:11
+ cobra (~cobra@user/Cobra)03:19
- qbit (QUIT: Ping timeout: 276 seconds) (~qbit@user/qbit)03:42
+ qbit (~qbit@user/qbit)03:42
- nsc (QUIT: Ping timeout: 252 seconds) (~nicolas@173-97-142-46.pool.kielnet.net)03:57
+ nsc (~nicolas@i5C74DEAF.versanet.de)03:58
- Manis (QUIT: Quit: Gateway shutdown) (01a66df340@185.72.67.185)04:01
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)04:08
- potatoespotatoes (QUIT: Ping timeout: 245 seconds) (~quassel@user/potatoespotatoes)04:09
+ potatoespotatoes (~quassel@user/potatoespotatoes)04:10
+ bkeys1 (~Thunderbi@h167.248.96.50.static.ip.windstream.net)05:04
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@h167.248.96.50.static.ip.windstream.net)05:04
* bkeys1 -> bkeys05:04
+ aloo_shu_ (~aloo_shu@85.51.16.245)06:06
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.16.20)06:09
* aloo_shu_ -> aloo_shu06:09
+ aloo_shu_ (~aloo_shu@90.166.99.43)06:23
- aloo_shu (QUIT: Ping timeout: 268 seconds) (~aloo_shu@85.51.16.245)06:26
* aloo_shu_ -> aloo_shu06:26
+ chomwitt1 (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)06:48
- nybble (QUIT: Ping timeout: 272 seconds) (~sprang@user/csprng)07:08
- jacqueline (QUIT: Ping timeout: 246 seconds) (~jacquelin@user/jacqueline)07:30
- chomwitt1 (QUIT: Ping timeout: 268 seconds) (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)07:53
+ Manis (01a66df340@185.72.67.185)08:05
abortretryfailso, uh. 5c2c4753 says "disable imx8mq hdmi for safety until solution is found". What broke HDMI?08:31
abortretryfailI was going to do a presentation on Friday and spent hours trying to figure out why the heck HDMI no longer worked. T_T08:32
joschabortretryfail: i found the problem08:47
joschabortretryfail: it is upstream commit 8a879141dcd15d2db876ce3adf88b9b01650b7fa08:47
abortretryfailI don't even know what the problem is08:47
joschabortretryfail: you could use the kernel built from this MR: https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/8008:47
joschabortretryfail: with that kernel i get hdmi again on imx8mq08:47
joschabortretryfail: i don't know what the problem is either -- i just bisect and revert patches :D08:48
abortretryfail"for safety"? 08:48
joschabortretryfail: the "for safety" bit is in the commit message because the HDMI dtb *also* disabled the internal screen08:49
joschabortretryfail: so "for safety" in the sense of: "make sure nobody is left without a working display"08:49
abortretryfailaha okay. That would have been a problem for sure.08:49
joschi'm afk for a bit now but if you like, please try out the kernel behind the MR -- i'd welcome feedback on whether it works for you as well :)08:49
abortretryfailI'll try to find a guide on testing kernels on Debian without making a mess. Thanks for the link @josch08:50
+ aloo_shu_ (~aloo_shu@90.166.98.73)08:56
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@90.166.99.43)08:59
* aloo_shu_ -> aloo_shu08:59
+ mjw (~mjw@gnu.wildebeest.org)09:07
- digitalrane (QUIT: Ping timeout: 268 seconds) (~rane@user/digitalrane)09:17
joschabortretryfail: i'm back -- did you find out how or do you need help?09:21
joschabortretryfail: you are on Debian unstable, right?09:21
joschabortretryfail: also, since you are on imx8mq, you have display support in u-boot, right? Are you using u-boot-menu?09:22
+ jacqueline (~jacquelin@user/jacqueline)09:22
joschabortretryfail: the easiest way to try out the kernel from that MR is to put this into your /etc/apt/sources.list:09:27
joschdeb [trusted=yes arch=arm64] https://source.mnt.re/reform/reform-debian-packages/-/jobs/7468/artifacts/raw/repo reform main09:27
joschafter running "sudo apt update" the output of "apt-cache policy linux-image-mnt-reform-arm64" should show you the kernel from that repo with version 6.12.10-1+reform20250125T235932Z09:29
joschso you want to install linux-image-6.12.10-mnt-reform-arm64 with that version09:29
joschif you also are using u-boot-menu then you can pick that kernel at boot-time09:29
+ voltaire28 (~voltaire2@194.153.110.6)09:32
+ aloo_shu_ (~aloo_shu@90.166.193.247)09:44
- aloo_shu (QUIT: Ping timeout: 246 seconds) (~aloo_shu@90.166.98.73)09:46
* aloo_shu_ -> aloo_shu09:46
- jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)10:04
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)10:05
+ aloo_shu_ (~aloo_shu@85.51.18.61)10:46
- aloo_shu (QUIT: Ping timeout: 248 seconds) (~aloo_shu@90.166.193.247)10:49
* aloo_shu_ -> aloo_shu10:49
* voltaire28 -> jeanmarc2811:20
+ aloo_shu_ (~aloo_shu@90.166.193.16)11:49
- laumann (QUIT: Read error: Connection reset by peer) (~quassel@user/laumann)11:51
- aloo_shu (QUIT: Ping timeout: 268 seconds) (~aloo_shu@85.51.18.61)11:52
* aloo_shu_ -> aloo_shu11:52
+ laumann (~quassel@2a0a-e5c0-2-2-0-c8ff-fe68-bef1.loves.ipv6.at.ungleich.ch)11:55
- laumann (QUIT: Changing host) (~quassel@2a0a-e5c0-2-2-0-c8ff-fe68-bef1.loves.ipv6.at.ungleich.ch)11:57
+ laumann (~quassel@user/laumann)11:57
+ _justin_kelly710 (~justinkel@user/justin-kelly/x-6011154)12:04
- _justin_kelly71 (QUIT: Ping timeout: 260 seconds) (~justinkel@user/justin-kelly/x-6011154)12:07
* _justin_kelly710 -> _justin_kelly7112:07
+ paperManu (~paperManu@107.159.71.33)12:50
+ gustav28 (~gustav@c-78-82-55-220.bbcust.telenor.se)13:02
- mtm (QUIT: Ping timeout: 260 seconds) (~textual@47.202.75.129)13:03
+ mtm (~textual@47.202.75.129)13:05
+ chomwitt1 (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)13:13
abortretryfailI started a compile on a imx8mq Reform and went to bed assuming it was going to take a while.13:17
abortretryfailI stopped using u-boot-menu when it kept breaking after updates leaving me without a laptop. :)13:18
joschabortretryfail: do you remember what broke? i'd be interested in fixing it13:19
abortretryfaillooks like it didn't compile, or didn't finish packaging, missing some python modules.13:19
abortretryfailI can't remember.13:19
joschabortretryfail: can i assist you in any way?13:19
abortretryfailNo, I was just up too late and didn't read README.md that had a list of all the stuff I should have installed.13:21
joschabortretryfail: you don't want to use the prebuilt artifacts?13:22
abortretryfailTbh, I want to be able to do this locally if I need to anyway. 13:23
abortretryfailThat line about deb [trusted=yes... does that point apt at Gitlab's CI? 13:24
joschyes13:24
abortretryfailMaybe I should have a cup of coffee before I continue working on this.13:25
abortretryfailOkay, let me give u-boot-menu another try and see what it does.13:38
minuteweird issues on my debian unstable pc:13:41
minutedpkg: error processing archive /var/cache/apt/archives/libcangjie3-data_1.4.0.really.1.4.0-4_all.deb (--unpack):13:41
minute trying to overwrite '/usr/share/libcangjie/cangjie.db', which is also in package libcangjie2-data (1.3-4)13:41
minute> sudo apt remove libcangjie2 libcangjie3 python3-pycangjie ibus-cangjie python3-pikepdf pdfarranger python3-img2pdf img2pdf13:42
joschminute: you should report this as an RC bug13:42
joschif libcangjie2-data cannot be co-installed with libcangjie3-data then they should either conflict in their dependencies, or should move files around so that they can be co-installed13:43
minutemhmm13:43
abortretryfailjosch: okay, my u-boot-menu problem still exists and came back when I reinstalled it. It tried all of the options and fails with ERROR: Did not find a cmdline Flattened Device Tree then eventually it runs boot.scr to a rescue shell.13:47
abortretryfailLast time it did this after an apt upgrade I got mad and just removed it.13:48
joschabortretryfail: when and what does fail? It fails with that error during boot?13:49
joschif yes, what are the contents of your /boot/extlinux/extlinux.conf?13:49
abortretryfailIt shows the menu with a few kernel options, but no matter which you select it gives that error and tries a different one which gives that error, until it goes through the whole list. 13:50
abortretryfailJust a sec i'll try to pastebin that file.13:51
joschthank you!13:51
abortretryfailhttps://paste.debian.net/hidden/1699c84c/13:54
joschindeed you are missing fdt entries there13:57
joschabortretryfail: what are the contents of your /etc/u-boot-menu/conf.d/reform.conf?13:58
abortretryfailSure am. If I wrote this file myself it would be straightforward to fix it.13:58
abortretryfailThere is no /etc/u-boot-menu/ :D13:58
joschabortretryfail: when was the last time you ran reform-display-config?13:59
joschthat script switches your imx8mq between single and dual display mode13:59
joschand it also sets up /etc/u-boot-menu/conf.d/reform.conf such that you get the correct entries in your /boot/extlinux/extlinux.conf13:59
abortretryfailLast Friday, when I was trying to get HDMI working to use the projector.13:59
abortretryfailSo I have to re-run that again now that I have u-boot-menu installed? 14:00
joschabortretryfail: and you are sure that your version of reform-tools is the latest one?14:00
abortretryfailI'm not sure of that, no.14:00
joschabortretryfail: can you also pastebin me the output of running sudo reform-check?14:00
joschreform-check does not yet check for the problem you have but since you ran into it, i guess it should14:01
joschlet me quickly add this now....14:01
abortretryfailIn its defense, the last time I ran reform-display-config, I did not have u-boot-menu installed.14:01
abortretryfailreform-tools is 1.66-1+reform1 according to apt14:02
joschabortretryfail: reform-display-config should create that file independent on whether you have u-boot-menu installed or not14:03
joschooooh14:03
abortretryfailI wonder if it's trying to create the file but not the parent dir14:03
joschit only creates that file if /etc/u-boot-menu/conf.d/ exists14:03
abortretryfail:)14:03
joschhrm...14:03
joschso it *does* only carry out this change if u-boot-menu is installed...14:04
joschindependent of that, there should be something in reform-check14:04
joschabortretryfail: can you try re-running reform-display-config again and see if that creates the file now? Then it should work once you reboot14:04
abortretryfailreform-check output: https://paste.debian.net/1349326/14:04
abortretryfailGussing I have to do sudo mkdir -p /etc/u-boot-menu/conf.d first.14:06
joschhuh14:07
abortretryfailYep, that's what it took14:07
joschright, u-boot-menu does not create it14:07
abortretryfailI thought that was weird. 14:07
joschokay, reform-display-config should absolutely create this directory itself i think14:07
joschchanging that now...14:07
abortretryfailMost packages in Debian come with their config files.14:07
abortretryfailOkay, I did mkdir -p, reform-display-config, then u-boot-update and now there are fdt lines in extlinux.conf. Going to reboot and see if it works.14:09
joschperfect, thank you!14:09
abortretryfailu-boot-menu works now and boots kernels again. I'll give that CI build a try now.14:19
josch\o/14:20
joschabortretryfail: thanks a lot for finding and reporting this issue :)14:20
joschit should be fixed with the next reform-tools release14:20
joschin case you have some spare cycles, you could try out this diff for reform-check: https://paste.debian.net/hidden/22402f0b/14:21
joschsince everything works fine on your system, it should not print out these new warnings14:21
joschhad this check been in place before, you would've been able to easily spot where the problem was14:21
+ aloo_shu_ (~aloo_shu@85.51.16.18)14:22
- chomwitt1 (QUIT: Ping timeout: 260 seconds) (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)14:24
- amospalla (QUIT: Ping timeout: 252 seconds) (~jordi@user/amospalla)14:24
- mjw (QUIT: Ping timeout: 244 seconds) (~mjw@gnu.wildebeest.org)14:25
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@90.166.193.16)14:25
* aloo_shu_ -> aloo_shu14:25
abortretryfailHmm, apt thinks that kernel is older than the 6.12.12 already installed14:27
abortretryfailI guess it's right since it's 6.12.10.14:28
joschabortretryfail: yes, the CI build has been done a while ago14:28
abortretryfailI'll try out that reform-check patch first before I go breaking kernels.14:28
joschi also wonder about the other output of reform-check in your paste. Did you manually change kernel arguments?14:29
- Guest3450 (QUIT: Quit: Leaving) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)14:29
joschalso this line is worrysome: E: /boot/dtb-* symlink does not reference freescale/imx8mq-mnt-reform2.dtb14:29
joschthat symlink should've been set correctly by flash-kernel14:29
joschlet me improve that check as well...14:29
abortretryfailI was monkeying around with those symlinks on Friday trying to figure out wtf gaslight nonsense was going on when reform-display-config didn't work and reform-check kept saying I had the non-HDMI machine 14:30
abortretryfailThen I realized all the dtbs are the same and gave up. Found the changes in Git yesterday.14:30
abortretryfailoutput of patched reform-check: https://paste.debian.net/hidden/77f97554/14:38
- bkeys (QUIT: Ping timeout: 244 seconds) (~Thunderbi@h167.248.96.50.static.ip.windstream.net)14:47
+ aloo_shu_ (~aloo_shu@90.166.193.132)14:54
- aloo_shu (QUIT: Ping timeout: 260 seconds) (~aloo_shu@85.51.16.18)14:57
* aloo_shu_ -> aloo_shu14:57
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)15:00
joschabortretryfail: right, there is still some problem somewhere with your system. Are you currently running the patched kernel with hdmi support?15:03
joschabortretryfail: the problem is, that your /proc/device-tree/model says that you are *not* running the hdmi dtb15:03
abortretryfailNo I am still trying to figure out how to get apt to install it without removing my currently working 6.12.1215:03
abortretryfailjosch: that's because the dtbs are all the same and it looks at the model name, which says MNT Reform, not MNT Reform HDMI15:04
joschokay, good then that's expected -- thank you for testing!15:04
joschabortretryfail: what package exactly are you trying to install and what package exactly is it saying it will remove?15:04
abortretryfaillinux-image-mnt-reform-arm64=6.12.10-1+reform20250125T235932Z is the one I'm trying to install15:05
abortretryfailit says it's downgrading that and removing linux-image-arm6415:06
joschdon't install that15:06
joschlinux-image-mnt-reform-arm64 is a meta-package15:06
joschyou leave that in its latest version15:06
abortretryfailI already goofed up once and now it thinks linux-image-mnt-reform-arm64 is explicitly installed. :/15:07
joschyou want to install linux-image-6.12.10...15:07
joschlinux-image-mnt-reform-arm64 *should* be explicitly installed15:07
abortretryfailI thought it was meta-installed via linux-image-arm6415:08
abortretryfailmeta meta? 15:08
joschno, linux-image-arm64 is the meta-meta package15:10
joschit explains that in the reform-check output as well15:10
joschgoing forward, you don't want the linux-image-arm64 package anymore15:10
abortretryfailYeah, I left that because when I tried to remove it, apt said it was going to remove the kernel I needed to boot, so I left it in spite of what reform-check said to do.15:10
abortretryfailsorry, I've used Debian off and on since the late 90s and still to this day apt confounds me with the things it does.15:11
joschyou are not alone15:11
joschthere were/are quite a few changes to how apt does things in the past years...15:11
abortretryfailI guess the package I need is linux-image-6.12.10-mnt-reform-arm64 maybe also linux-headers-6.12.10-mnt-reform-arm6415:12
joschyou need the former15:12
joschyou want the latter as well so that the dkms module can be built15:12
abortretryfailRight, I was thinking something needed that, LPC driver?15:12
joschexactly15:13
abortretryfailsorta why I was aiming for the meta package to not have to think about what else I was missing.15:13
joschyes, long term you want the linux-headers-mnt-reform-arm64 meta-package to pull in the right things15:14
joschwhat you do right now is temporary15:14
josch <= afk again for a few hours15:15
abortretryfailTbh it looks like apt just kind of leaves old kernels piling up anyway.15:15
abortretryfailI need to clean this machine up.15:15
joschabortretryfail: how are you upgrading?15:15
joschabortretryfail: if you use "apt full-upgrade" then apt will clean up old kernels automatically15:15
josch(but it will never remove the currently running kernel and the latest kernel)15:15
abortretryfailupgrade or dist-upgrade? I didn't even know there was a full-upgrade...15:16
+ mjw (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)15:16
abortretryfailI occasionally do autoremove.15:16
joschfull-upgrade is the new dist-upgrade15:16
abortretryfail🤦‍♂️15:17
joschdist-upgrade is the command you use with apt-get15:17
joschapt-get is what you use in scripts15:17
joschif you use apt interactively, you just use "apt"15:18
joschand then you don't use dist-upgrade but full-upgrade15:18
josch(see the respective man pages)15:18
chminute, josch: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082165 this was filed in september and is claimed fixed, maybe this is not true?15:19
joschabortretryfail: this might help: https://community.mnt.re/t/mnt-pocket-reform-essentials/2094/4415:19
joschreally afk now :)15:19
abortretryfailok bye, thx for the help.15:19
abortretryfailjosch: the 6.12.10 kernel from CI boots, uses the HDMI dtb and it looks like it detects displays when they are connected, but swaymsg -t get_outputs always reports them as power off and no amount of fiddling with swaymsg output enable power on etc will make it show any image.15:39
abortretryfailI also see that the eDP is running at 70hz still, which I remember being a problem w/HDMI? Isn't it supposed to go to a lower refresh rate in dual display mode?15:39
abortretryfailanyway, i also have to afk for a few hours to do work. later15:40
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone)15:49
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)15:49
- bkeys (QUIT: Client Quit) (~Thunderbi@38-146-94-247.echocast.zone)15:50
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)15:50
- bkeys (QUIT: Client Quit) (~Thunderbi@38-146-94-247.echocast.zone)15:52
+ chomwitt1 (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)15:52
+ bkeys1 (~Thunderbi@38-146-94-247.echocast.zone)15:52
- bkeys1 (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)15:53
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)15:54
+ aloo_shu_ (~aloo_shu@90.166.193.101)15:57
- bkeys (QUIT: Client Quit) (~Thunderbi@38-146-94-247.echocast.zone)15:58
+ bkeys1 (~Thunderbi@38-146-94-247.echocast.zone)15:58
- chomwitt1 (QUIT: Ping timeout: 248 seconds) (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)16:00
- bkeys1 (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)16:00
- aloo_shu (QUIT: Ping timeout: 260 seconds) (~aloo_shu@90.166.193.132)16:00
* aloo_shu_ -> aloo_shu16:00
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)16:01
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone)16:06
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)16:06
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)16:08
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)16:09
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone)16:14
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)16:15
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)16:20
+ bkeys1 (~Thunderbi@38-146-94-247.echocast.zone)16:20
- bkeys1 (QUIT: Ping timeout: 252 seconds) (~Thunderbi@38-146-94-247.echocast.zone)16:24
- gregori (QUIT: Quit: Client closed) (~gregori@c-174-165-127-77.hsd1.wa.comcast.net)16:26
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)16:29
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)16:31
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)16:31
- bkeys (QUIT: Client Quit) (~Thunderbi@38-146-94-247.echocast.zone)16:34
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)16:34
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)16:40
+ bkeys1 (~Thunderbi@38-146-94-247.echocast.zone)16:40
- bkeys1 (QUIT: Client Quit) (~Thunderbi@38-146-94-247.echocast.zone)16:42
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)16:42
- bkeys (QUIT: Client Quit) (~Thunderbi@38-146-94-247.echocast.zone)16:45
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)16:46
+ aloo_shu_ (~aloo_shu@85.51.18.114)17:00
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@90.166.193.101)17:03
* aloo_shu_ -> aloo_shu17:03
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone)17:04
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)17:04
+ mark_ (~mjw@gnu.wildebeest.org)17:08
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)17:08
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)17:08
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)17:11
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)17:12
+ chomwitt1 (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)17:13
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@38-146-94-247.echocast.zone)17:22
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)17:23
- bkeys (QUIT: Client Quit) (~Thunderbi@38-146-94-247.echocast.zone)17:26
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)17:26
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)17:35
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)17:35
- jeanmarc28 (QUIT: Quit: Client closed) (~voltaire2@194.153.110.6)17:36
- chomwitt1 (QUIT: Ping timeout: 260 seconds) (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)17:51
+ nybble (~sprang@user/csprng)17:53
+ chomwitt1 (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)18:18
joschabortretryfail: another thing you can try is the Debian Bookworm kernel 6.1 from reform.debian.net18:30
+ aloo_shu_ (~aloo_shu@85.51.17.20)18:33
- chomwitt1 (QUIT: Ping timeout: 246 seconds) (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)18:34
- aloo_shu (QUIT: Ping timeout: 265 seconds) (~aloo_shu@85.51.18.114)18:36
* aloo_shu_ -> aloo_shu18:36
+ aloo_shu_ (~aloo_shu@90.166.99.239)18:50
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.17.20)18:53
* aloo_shu_ -> aloo_shu18:53
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)19:06
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone)19:24
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)19:25
- cow321 (QUIT: Remote host closed the connection) (~deflated8@user/meow/deflated8837)19:29
+ cow321 (~deflated8@user/meow/deflated8837)19:39
+ aloo_shu_ (~aloo_shu@90.166.98.172)19:41
- aloo_shu (QUIT: Ping timeout: 246 seconds) (~aloo_shu@90.166.99.239)19:44
* aloo_shu_ -> aloo_shu19:44
minuteinteresting https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/424919:55
+ reform7704 (~michael@h081217090069.dyn.cm.kabsi.at)19:59
reform7704hello19:59
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone)20:00
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)20:01
* mjw -> Guest663020:14
- Guest6630 (QUIT: Killed (silver.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)20:14
* mark_ -> mjw20:14
+ Guest6630 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)20:15
- reform7704 (QUIT: Quit: Leaving) (~michael@h081217090069.dyn.cm.kabsi.at)20:22
chgraphics seems to be hard20:37
+ chomwitt1 (~chomwitt@2a02:587:7a13:5400:1ac0:4dff:fedb:a3f1)21:42
- Gooberpatrol66 (QUIT: Ping timeout: 260 seconds) (~Gooberpat@user/gooberpatrol66)21:43
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)21:44
- Gooberpatrol66 (QUIT: Client Quit) (~Gooberpat@user/gooberpatrol66)21:45
- gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-55-220.bbcust.telenor.se)22:15
- mtm (QUIT: Read error: Connection reset by peer) (~textual@47.202.75.129)22:35
- bkeys (QUIT: Ping timeout: 248 seconds) (~Thunderbi@38-146-94-247.echocast.zone)23:04
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)23:07
- bkeys (QUIT: Ping timeout: 248 seconds) (~Thunderbi@38-146-94-247.echocast.zone)23:26
abortretryfailjosch: 6.1 gives me the same result as 6.12.10.23:41
abortretryfailch:HDMI was made difficult on purpose.23:53

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