2023-02-26
00:04possiblemeatball has joined #asahi-alt
00:58hightower2 has quit [Ping timeout: 480 seconds]
00:59Leo3418 has quit [Quit: Applying updates]
01:00Leo3418 has joined #asahi-alt
01:00Leo3418 has quit []
01:01Leo3418 has joined #asahi-alt
01:16nela has quit [Ping timeout: 480 seconds]
01:36nela has joined #asahi-alt
02:05winter0 has joined #asahi-alt
02:07sam_ has quit [resistance.oftc.net larich.oftc.net]
02:07winter has quit [resistance.oftc.net larich.oftc.net]
02:07vivithecanine has quit [resistance.oftc.net larich.oftc.net]
02:07zv has quit [resistance.oftc.net larich.oftc.net]
02:07zv_ has joined #asahi-alt
02:07vivithecanine has joined #asahi-alt
02:08sam_ has joined #asahi-alt
02:24kesslerd_ has joined #asahi-alt
02:49winter0 has quit []
03:40cylm has joined #asahi-alt
05:05possiblemeatball has quit [Quit: Quit]
05:17kesslerd has quit [Remote host closed the connection]
05:18kesslerd_ has quit [Remote host closed the connection]
05:19kesslerd has joined #asahi-alt
05:34kesslerd has quit [Remote host closed the connection]
10:08wixde has joined #asahi-alt
11:38hightower2 has joined #asahi-alt
11:42wixde has quit [Ping timeout: 480 seconds]
11:45ChaosPrincess has quit [Quit: WeeChat 3.8]
11:46ChaosPrincess has joined #asahi-alt
13:11possiblemeatball has joined #asahi-alt
13:20arndjannau: after upgrading from 6.1 to 6.2 with the current asahi/bits/200-dcp branch (a2482bcc06), I no longer get the HDMI to be turned back on after I turn off the monitor over night. The only kernel message I get about this is "Feb 26 13:40:21 studio kernel: apple-dcp 38bc00000.dcp: crtc_atomic_check: disconnected but no modeset". Any idea?
13:21arndit's my own kernel config, and I only included the branches that I thought I needed, so it's possible something is issing, but everything else seems to work fine
13:26kesslerd has joined #asahi-alt
13:28kesslerd has quit []
13:38jannauarnd: does switching to a different vt (and back) fixes it? I assume you have already tried to turn the monitor off and on again?
13:39arndjannau: not any more. I used to have this problem occasionally in the past, and then switching to vt1 and back solved it. With my current kernel, it seems to happen every time, and the vt switch no longer helps
13:39maria6 has joined #asahi-alt
13:39jannaudoes it only happen if the monitor is off longer or can you reproduce it with switching the display off and on
13:39maria has quit [Ping timeout: 480 seconds]
13:39maria6 is now known as maria
13:39arndI tried unplugging the HDMI cable, using the monitor power button or the external power switch (which turns off my speaker etc as well), no differences
13:40arndit just happened after turning it off briefly using the moniotor's power switch. Can't see what I type any more now
13:43jannauok, sound broken. Can you get me the dcp kernel log from before switching the monitor off? I'm still on on v6.2-rc3 (asahi-wip)
13:45arndHmm, this time switching to vt1 worked, but then switching back to xfce got it into the broken state where it no longer came back. I'll reboot and try to find the log file
13:55arndjannau: here is the entire 'journalctl --system' output from boot to shutdown for the session that just broke: https://pastebin.com/CMGnvK6J
13:56arndthe source tree is v6.2 with bits/000-devicetree, bits/010-mailbox, bits/020-t6000-dart, bits/030-misc, bits/040-dwc3, bits/050-nvme, bits/110-smc, bits/120-spmi, bits/150-xhci-firmware, bits/170-atcphy and bits/200-dcp
14:07jannauarnd: looks like runtime pm suspend and resume are running concurrently. clearly a bug in dcp. simplest workaround would be to merge bits/200-dcp only up to 125aeecbc011d
14:08jannauhas you v6.1 branch the same bits/200-dcp or was it based on bits/200-dcp from around the v6.1 release?
14:17arndjannau: this survived all combinations of power off/on and unplug that previously crashed it. I'm happy enough with this, thanks for the quick help!
14:22arndxfce4 is a little annoying by always showing me 'Display Settings' windows every time I turn the screen back on sincen it noticed the monitor config changing twice, bu there is probably not much that can be done about that in DCP
14:29jannaunot sure, quite possible that dcp does something unexpected on display power off/on. I'll try if I can find what triggers displaying the display settings in xfce4
14:40wixde has joined #asahi-alt
14:43Cromulent has joined #asahi-alt
15:44kesslerd has joined #asahi-alt
15:53wixde has quit [Ping timeout: 480 seconds]
15:56wixde has joined #asahi-alt
16:59cy8aer has quit [Remote host closed the connection]
17:13cylm has quit [Ping timeout: 480 seconds]
18:31Cromulent has quit [Quit: Connection closed for inactivity]
18:34possiblemeatball has quit [Quit: Quit]
19:08possiblemeatball has joined #asahi-alt
19:35Dementor has quit [Read error: Connection reset by peer]
19:35Dementor has joined #asahi-alt
20:58wixde has quit [Read error: Connection reset by peer]
21:27jacksonchen666 has joined #asahi-alt
21:35jacksonchen666 has quit [Quit: WeeChat 3.8]
22:05qdot has quit [Read error: Connection reset by peer]
22:05qdot has joined #asahi-alt
23:40possiblemeatball has quit [Quit: Quit]
23:53stipa is now known as Guest6002
23:53stipa has joined #asahi-alt
23:55Guest6002 has quit [Ping timeout: 480 seconds]