14:06 noobie: hey folks
14:07 noobie: that's probably the 100000x dual monitor help request (sorry for that) but I just can't get it to work properly, so maybe someone has some advice for me :)
14:08 noobie: I have one screen connected via displayport and one old screen via vga - if i boot with both connected the displayport screen keeps turning on and off and flickers
14:08 noobie: if i boot with only one of them connected each works just fine
14:10 noobie: Any idea what could fix this?
14:11 gnarface: mess with xrandr
14:12 gnarface: i can't be more specific at the moment sorry
14:13 noobie: well, setting different refresh rates and resolutions didn't help, and I'm afraid my knowledge comes at its limit here for any other settings
14:13 noobie: s/at/to/
14:43 FLHerne: karolherbst: I thought the idea was that they disable FP64 resources on non-Quadro chips, for market segmention
14:43 FLHerne: (and/or yield management if they get ones with faulty FP64 blocks)
14:44 karolherbst: FLHerne: right sure, but I was wondering if this is purely sw controlled or not
14:44 karolherbst: well
14:44 karolherbst: on some chips
14:44 karolherbst: if they produce others without fp64 high perf variants then they can just skip it
14:49 FLHerne: Hm
14:51 FLHerne: According to forum, it was possible on older chips by copying the VBIOS and fiddling with resistors on the board https://www.eevblog.com/forum/chat/hacking-nvidia-cards-into-their-professional-counterparts/550/
14:52 FLHerne: One reason for the signed vbios/firmware?
14:52 FLHerne: (assuming they use different keys)
15:17 RSpliet: Well, copyng the VBIOS is a dangerous thing to do these days unless the boards use the exact same DRAM chips too.
15:21 imirkin: noobie: pastebin xrandr output and xorg log
15:23 noobie: imirkin: just a sec, gotta reboot. I should add that if I boot with only the displayport connected and then connect the dvi screen both work fine
15:25 imirkin: surprising.
15:30 noobie: xrandr: http://paste.debian.net/1011917/
15:31 noobie: xorg:http://paste.debian.net/1011918/
15:32 imirkin: which one flickers? DP or VGA?
15:33 noobie: DP
15:33 noobie: it's actually DVI (not VGA) sorry
15:33 imirkin: well, it's analog
15:33 noobie: true
15:33 imirkin: ok, well i don't see anything odd in the logs
15:34 noobie: starting only with DP and connecting VGA later swaps the CRTC values, not sure if this means anything though
15:34 imirkin: the most reasonable reason for DP screen flickering is if for some reason the driver keeps retraining it
15:34 imirkin: it could.
15:34 imirkin: can you boot with drm.debug=0x1e nouveau.debug=disp with both plugged in?
15:36 noobie: yup
15:36 imirkin: and then grab dmesg
15:36 imirkin: it does seem like there's something flaky in the vga screen
15:36 imirkin: the modelines are printed for it a bunch of times in the xorg log
15:36 imirkin: perhaps you plugged/unplugged it a bunch to test?
15:42 noobie: I didn't for this boot at least
15:42 noobie: brb
15:51 noobie: https://pastebin.com/4uVvBtVm
15:53 imirkin: something keeps reprobing modes
15:53 imirkin: which in turn causes a link retrain
15:53 imirkin: which in turn causes flickering
15:57 karolherbst: broken cable?
15:57 imirkin: or software that keeps trying to reprobe
15:58 noobie: well, since it works with the prorietary nvidia drivers and when plugging the vga in after booting I'd guess it's not the cable
15:58 karolherbst: right, but trying a different cable might be faster to test
15:58 imirkin: i'm sure cable is fine
15:58 karolherbst: finding sw issues with broken hw is always pain
15:58 karolherbst: just saying
15:59 noobie: which cable would I change ? dp or vga ?
15:59 noobie: I only have one dp cable so there's no way of testing it
15:59 imirkin: noobie: up it maybe, nouveau.debug=disp=trace ?
15:59 imirkin: not really sure what i'm looking for though
15:59 noobie: ay
15:59 imirkin: skeggsb may have some suggestions
16:00 imirkin: he'll be up in 8h or so
16:00 imirkin: (if he's not around now)
16:00 noobie: cool, thanks so far imirkin!
16:06 noobie: https://pastebin.com/kXvdRN6h
16:06 noobie: looks like I might have to increase the buffer size
16:07 imirkin: hmmm
16:07 imirkin: doesn't look like it's actually retraining
16:07 imirkin: nevermind
16:07 imirkin: then i got nothin'
16:09 noobie: thanks :)
16:41 noobie: real pro workaround: I'm using a kvm switch no and use the button to disable the shitty vga screen before boot :o
16:41 noobie: s/no/now
17:00 imirkin: i have no idea what would be special about crtc 1 vs 2
17:00 imirkin: vga uses pior, so it's not like the sor assignment would change... dunno
23:32 noobie: connected another vga monitor, same result :(