17:32ilgaz: I got some bad news. Screen blanks. nv79 (yes that evil one)
17:32karolherbst: ilgaz: sounds like an annoying issue. Was it always like that or just after an update?
17:34ilgaz: I used ubuntu a bit with nvidia 340. Now back to openSUSE Tumbleweed with kernel 5.17.2-1 , I believe this started to happen in 5.17 era
17:34ilgaz: "nouveau 0000:02:00.0: Direct firmware load for nouveau/nvac_fuc084d failed with error -2" this message is mysterious too
17:34karolherbst: shouldn't cause the blanking though
17:34ilgaz: no results on google which is amazing
17:35karolherbst: does nv79 even exist? :P
17:35karolherbst: mind sharing your dmesg? maybe there is something odd in there
17:35ilgaz: er. whatever this nvidia 9400 on mac mini 3.1 with nvidia chipset
17:35karolherbst: I think I have that one as well
17:36karolherbst: MCP7a I think
17:36karolherbst: ohh wait
17:36karolherbst: it's the other one
17:36karolherbst: MCP79.. right...
17:37karolherbst: "DRM: unknown connector type 20" ehh...
17:37karolherbst: let me check what that one is
17:37ilgaz: my dmesg. There is also nostalgic amiga like flickering issue once you switch from their software rendering to nouveau
17:38ilgaz: forgot to tell, openSUSE TW guys seems to have switched to software rendering lvmpipe or something by default
17:38karolherbst: ilgaz: does it have ADC?
17:38karolherbst: ehh wait
17:38karolherbst: it's both hex
17:39karolherbst: then it's some DVI-S-video stuff
17:39karolherbst: yeah.. probably doesn't matter then
17:39ilgaz: I am connected via some adapter from adc (mini?) to hdmi
17:40ilgaz: BTW I physically unconnected the cable and re connected, it looks better now
17:40karolherbst: if it's really ADC then there might be something special we need to do it, but I think ADC was just power + DCI
17:41karolherbst: ahh and USB
17:42ilgaz: Heard the tech support trick when they think cable is not connected at all? "Sir, please remove the cable and remove dust on it, plug it again". Guy figures he didn't plug it in but doesn't say a word
17:42karolherbst: let's see
17:42karolherbst: ilgaz: ahh no, it's mini DVI on the 3,1
17:42karolherbst: and mini DP
17:43ilgaz: karolherbst: I am in TV business, is the monitor losing sync and blanking like "reset" ?
17:43karolherbst: hard to tell without seeing what happens, we could also just configure the hardware incorrectly
17:44karolherbst: cable could be broken too
17:44ilgaz: karolherbst: one more thing. This thing went crazy once the monitor did DPMS off, it started to blank every 20 secs or so
17:44karolherbst: could also be a software bug
17:44ilgaz: I disabled power saving as result and installed xscreensaver
17:45karolherbst: wouldn't be the first time I've heard about dpms just being super broken in X
17:47ilgaz: There is no easy way to fetch the current tree from git, build it and try if something changed right?
17:47karolherbst: anyway, at this point I can't rule out if it's a nouveau bug or something else, which makes this stuff annoying to debug
17:47karolherbst: mhh.. well.. you could build the linux kernel
17:47karolherbst: but that will take ages on that 3,1 mini
17:48ilgaz: lol when it finished kernel 5.18 may ship *g*
17:48ilgaz: It seems fine for now (knocks on wood) let me wait a while
17:51ilgaz: karolherbst: ah you should see the message I saw on ubuntu 20.04 sway when I launched it with nvidia 340. They toned it down now :-)
17:55ilgaz: This is the flickering bug BTW https://bugzilla.opensuse.org/show_bug.cgi?id=1198662
17:56ilgaz:remembered his Amiga video toaster days
18:02karolherbst: ilgaz: ohh... so changing the refresh rate fixes it?
18:03karolherbst: it could be that a modeset does fix something
18:03karolherbst: not sure if we do anything when booting
18:05ilgaz: nouveau does query monitor refresh rate right? I mean if not set
18:06karolherbst: sure, but nobody guarantees us that the VBIOS has a sane mode for real desktop usage pre configured
18:06karolherbst: so if changing the mode once does fix something, that could mean that we just need to do a modeset on boot on certain cards
18:06karolherbst: but normally the idea is to reuse whatever the firmware provides
18:08ilgaz: karolherbst: BTW you just need to do it once and it settles after that
18:09karolherbst: yeah.. then something is just broken when booting
18:09karolherbst: mind checking the output of "xrandr" right after boot?
18:09ilgaz: subsequent reboots= doesn't happen too
18:09ilgaz: ok rebooting
18:10ilgaz: err why reboot? here is the paste https://paste.opensuse.org/23403186
18:11ilgaz: karolherbst: actually this lenovo monitor can do 75hz/1080p but this chip can't go up that level.
18:11ilgaz: on intel hd5500 it is 75hz
18:11karolherbst: yeah.. shouldn't be an issue though
18:12karolherbst: ilgaz: mhhh.. does it boot into the same mode on a cold reboot?
18:12karolherbst: this interlaced mode makes me curious
18:12karolherbst: I am sure if you use those, things break
18:13ilgaz: OK here is exactly what happened: 1) I noticed system uses lvvm-pipe 2) installed nouveau* 3) rebooted 4) noticed flickering 5) went to kde refresh rate setting changed it to 50 hz (flickering stops) and 60 hz (apply)
18:14karolherbst: yeah.. but UIs are kind of weird about interlaced modes
18:14ilgaz: Man if I was in USA or something, I would send this machine to you right away for a month
18:14karolherbst: not sure if you can even select those
18:14ilgaz: karolherbst: absolutely not, there is just 50hz and 60hz
18:15ilgaz: my fault was not checking monitor's "info" panel to see which refresh it is on
18:15karolherbst: there is a way to set those via xrandr, but.. I don't know for sure :)
18:15karolherbst: ilgaz: yeah.. so weird flickering issues can happen with interlaced, if the hw doesn't really support that. You even have an adapter, which can mess things up badly, and I know systems, where the interlaced mode is used by default
18:15karolherbst: for whatever reason
18:16ilgaz: It was around 32 hz if you ask me :-) I mean real amiga like
18:16karolherbst: so if you switch over to progressive ones, you simply don't run into interlaced issues
18:16karolherbst: yeah.. well
18:16karolherbst: interlaced is just half the rate
18:16karolherbst: just cheated to be double that
18:17karolherbst: I had some other interlaced bugs on other GPUs, and it was just a total mess on the display :)
18:18karolherbst: ilgaz: I think you can select interlaced like "xrandr --mode 1920x1080i --rate 60.00" but...
18:18ilgaz: karolherbst: You know people from Fedora/Redhat etc? I noticed some misinformation/outdated info about video acceleration
18:18karolherbst: might have to add an "--output DVI-I-1"
18:18ilgaz: with not so professional language
18:18karolherbst: ilgaz: it happens that I work at RedHat
18:19ilgaz: aha! good. Let me check interlace first and send you the page
18:19karolherbst: okay, cool
18:20karolherbst: btw, need to do some grocery shopping before shops close here, so I'll be gone for a bit
18:20ilgaz: ok yes! this is the interlace mode I saw
18:20karolherbst: okay... cool
18:20ilgaz: with xrandr command
18:20karolherbst: so we figured out what was causing those issues :)
18:22ilgaz: karolherbst: when you are back https://fedoraproject.org/wiki/Firefox_Hardware_acceleration#Video_decoding_on_NVIDIA
18:23ilgaz: perhaps a sidenote about nouvau may help since I _use_ video acceleration even on this chip