01:40Tashtari: Anyone have any insights about the issue I posted before? :)
01:43joepublic: I commiserate with you that it's frustrating to have things not always work as expected.
01:44Tashtari: Boy, is it ever.
01:46joepublic: And for the record I am very thankful that my three-monitor desktop "just works" with GTX 760+nouveau
02:27karolherbst: Tashtari: sounds like something is broken with your system config
02:27karolherbst: like X won't start
02:27karolherbst: probably some config thing
02:27karolherbst: check the X logs
02:27Tashtari: karolherbst: Possibly, but the variable is definitely the video - like I said, everything works fine on the mobo's onboard video.
02:28karolherbst: but maybe that can be explained by whatever is in the log or the config
02:28karolherbst: onboard is intel I guess?
02:29karolherbst: uhh, do you have some kind of custom xorg.conf file?
02:29Tashtari: Nope, unmodified distro default.
02:30karolherbst: it could be some stupid thing like X starts still on the aspeed GPU
02:30karolherbst: as the firmware selects it as the default output
02:31karolherbst: can you change the selected GPU inside the bios or something?
02:31Tashtari: When I put the GeForce 210 card in, I disabled it by a jumper on the motherboard, it doesn't show up in lspci.
02:32Tashtari: disabled the onboard video, I mean
02:32karolherbst: sounds good enough
02:32karolherbst: then the Xorg log would help
02:32karolherbst: it's inside /var/log
02:33Tashtari: Looking at it now... the only error in it is that it tried and failed to load the module "nv".
02:33karolherbst: what deskopt btw? gnome, plasma, something else?
02:33karolherbst: well, the log is quite verbose with errors even if they won't matter
02:34karolherbst: mind uploading the log somewhere?
02:34Tashtari: Sure, hang on a tick...
02:38karolherbst: Tashtari: mhh, so there is a display connected via HDMI, correct?
02:38karolherbst: are you on that machine via SSH or something?
02:38Tashtari: No, the framebuffer console works fine, it's just that X doesn't. Or, I guess, whatever you term the thing that you get when you ctrl-alt-F7.
02:38karolherbst: I could imagine that this is simply some xrandr messup
02:39karolherbst: and you could check the xrandr output while X is running with "DISPLAY=:0 xrandr"
02:39karolherbst: normally there should be a line like that: 3840x2160 60.00*+ 59.98 59.97
02:39karolherbst: * means selected and + default?
02:39karolherbst: dunno for sure
02:39Tashtari: "No protocol specified", "Can't open display :0"
02:39karolherbst: X is running?
02:40karolherbst: DISPLAY=:7 then I think?
02:40Tashtari: "Can't open display :7"
02:40karolherbst: allthough those things aren't that much related
02:40karolherbst: yeah... should be :0 nonetheless
02:40karolherbst: the log wass called Xorg.0.log, right?
02:40Tashtari: Yeah. /var/log/Xorg.0.log
02:41karolherbst: what I am wondering about is, that X stops
02:41karolherbst: or well, maybe it doesn't?
02:41Tashtari: There is a process running /usr/lib/xorg/Xorg
02:41karolherbst: you aren't root, right?
02:41Tashtari: No, I am.
02:41karolherbst: I am not 100% sure how that works if you start into the login manager
02:42Tashtari: Do those "ERROR 1" lines I pasted earlier mean anything of significance?
02:43karolherbst: I highly doubt those are related
02:44karolherbst: can you stop X via your service manager and then start it with "startx" yourself?
02:44Tashtari: Well, I can try...
02:45Tashtari: Hmm. `service slim stop` (slim is the default X display manager) said it failed, but it did kill the Xorg proces.
02:45Tashtari: Should I do startx as root or as a regular user?
02:45karolherbst: as root
02:48Tashtari: Hmm. It blurted out a few lines of output, then it did basically the same thing as before, only taking over tty1 instead. Like, it sits frozen until I do, for example, ctrl-alt-F2, then a couple seconds after that, I get tty2.
02:48Tashtari: Then if I ctrl-alt-F1 again, the screen still shows tty2 but the cursor disappears.
02:51Tashtari: I killed the Xorg process and it pulled me back to tty1, which dumped me back in the shell
02:51karolherbst: are new messages appearing in dmesg when doing that?
02:52karolherbst: Tashtari: ohh, but this time we could check xrandr actually. Try to start X like this: "Xorg :0" and then in a different tty do that "DISPLAY=:0 xrandr"
02:52Tashtari: Nope. I see the elogind messages for logging in to tty1 and tty2, nothing interesting between or after them.
02:52Tashtari: Ah, okay. Hang on.
02:53Tashtari: "Can't open display :0"
02:56karolherbst: huh, that's weird
02:56karolherbst: or something is seriously broken
02:57karolherbst: normally that should just work when X is running
02:57karolherbst: X didn't quite while switching the ttys, correct?
02:57Tashtari: Nope, Xorg and xinit processes are still running.
02:58Tashtari: I'm assuming those bottom two lines about suspending AIGLX clients for VT switch is me switching to tty2...
02:59karolherbst: maybe it uses :1 but I highly doubt this
02:59karolherbst: it's more likely that X somehow doesn't start correctly or something?
02:59Tashtari: Ooh, it looks like it does use :1.
02:59karolherbst: ahh, k
03:00Tashtari: Hang on, I'll post its output too...
03:01karolherbst: mhh, that looks correct
03:02karolherbst: I guess a "DISPLAY=:1 glxinfo" also just prints tons of stuff?
03:04Tashtari: Well, that's weird... I had su'd to a regular user to run the web server I was using to download the log snippet, and I was closing that shell to go back to root... and the X server terminated.
03:04Tashtari: With error 1.
03:04Tashtari: Hang on, let me post that too.
03:06Tashtari: So I did startx again then switched to tty2 and did `DISPLAY=:1 glxinfo`. It said "name of display: :1", and the cursor is blinking below that like it's still trying to do something...
03:08karolherbst: maybe you need to switch to X before it can continue
03:09Tashtari: Ah, yeah, that accomplished something, switching to tty1 (where I did startx) and back to tty2. Big long thing of output. You want me to capture and post it?
03:10karolherbst: mhh, not really
03:11karolherbst: if it isn't an error it's fine
03:11karolherbst: that just means that X more or less works
03:11karolherbst: mind doing glxgears instead of glxinfo?
03:11karolherbst: maybe it does show something
03:12Tashtari: That one sat until I paged in and out too. When I came back, it said "302 frames in 5.0 seconds = 60.370 FPS"
03:13Tashtari: Paged in and out again, there are several lines saying similar things
03:13Tashtari: And one oddball saying "70 frames in 54.6 seconds = 1.281 FPS"
03:14Tashtari: Possibly that was it being suspended while I was on tty2.
03:14karolherbst: mhh so, nothing gets displayed
03:14karolherbst: stuff still works
03:15Tashtari: Yeah, seems like it...
03:15karolherbst: no idea what causes that though
03:15karolherbst: maybe something in #xorg knows?
03:15Tashtari: I guess I'll find out!
03:15Tashtari: Thanks for trying in any case.
03:16karolherbst: it's a weirdo issue
08:08rhyskidd: karolherbst: my test series on efi pci option rom parsing: https://github.com/envytools/envytools/compare/master...Echelon9:test/pci-option-rom-v1
08:08rhyskidd: working on pre-GP108 at this stage, will need to integrate with your earlier multi-part bios fix
11:34__user_: does anyone here have an authenticated program/bytecode for falcon uC v5 (and its accompanying signature)?
12:58karolherbst: __user_: we have what nvidia published (inside linux-firmware)
19:43filipdevuan_: hey i wonder why windows games under wine say i have geforce gtx 750 gpu if laptop has 940mx same with terminal it shows nv117 but 940mx is nv118 thank you :)
19:49karolherbst: filipdevuan_: because wine
19:50karolherbst: I don't think vanilla wine has means to actually get the correct chipset
19:50karolherbst: and they just do whatever they feel like
19:50filipdevuan_: ok thats fair enough then, nothing needed more to say haha :P cheers
19:50filipdevuan_: but then i wonder why in terminal its nv117 not nv118
19:50karolherbst: wine-staging does handle that correctly afaik
19:51karolherbst: well, why do you think your gpu is nv118 and not nv117?
19:52karolherbst: nouveau uses whatever the GPU reports it is, if the GPU says it is a nv117, then nouveau just uses that information
19:53filipdevuan_: i checked https://nouveau.freedesktop.org/wiki/CodeNames/
19:53filipdevuan_: and it says geforce 940m[x] is nv118
19:53karolherbst: that's in no way reliable
19:53filipdevuan_: ohh ;p
19:53filipdevuan_: okay then
19:53filipdevuan_: no no im not ranting at nouveau just been wondering
19:54karolherbst: but the differences are so insignificant I doubt they even matter to us in any way
19:54karolherbst: nv117 vs nv118 that is
19:54filipdevuan_: yeah the most important thing is that i get very good experience playing diablo 3 on nouveau...
19:54karolherbst: with the d3dnine stuff?
19:54filipdevuan_: cuz i mainly bought a laptop to play d3
19:54filipdevuan_: uhh yeah directx9?? :p
19:55karolherbst: I mean, there are patches for wine to use d3d on linux
19:55karolherbst: instead of opengl
19:55karolherbst: but... maybe d3 can do opengl directly?
19:55karolherbst: anyway, using nine for dx9 games or opengl gives better perf than mapping dx9 over opengl
19:55orbea: karolherbst: nine is entirely broken with nouveau still
19:55karolherbst: orbea: howso?
19:56orbea: let me link the issue
19:56karolherbst: I know there are some issues with a handful of games, but generally it should work
19:56filipdevuan_: uhh im not fan of opengl under linux
19:56filipdevuan_: and i didnt even know theres something different
19:56orbea: https://github.com/iXit/Mesa-3D/issues/308 and https://bugs.freedesktop.org/show_bug.cgi?id=106577
19:57orbea: karolherbst: all games I tried are broken in some way
19:57filipdevuan_: i only downloaded wine-staging and bnet appw ith diablo 3 i run d3 32bit with dri_prime=1
19:57orbea: there is a workaround, but its not nice
19:57karolherbst: filipdevuan_: yeah, that's most likley using the nine stuff then
19:57orbea: imirkin was going to fix it, but I guess that never happened
19:58karolherbst: I am a little aware of that issue
19:58karolherbst: trace would help
19:58filipdevuan_: yeah for example games like path of exile or world of warcraft run like shieet. but its not a bad thing i decided if game isnt playable under nouveau then its not worth it, i dont wanna install proprietary nvidia drivers that overheats my gpu freaking easily
19:58orbea: there is one, but that server I hosted it on died. I am pretty sure the nine devs have it still
19:59orbea: i asked in #d3d9 if they still have it
20:04orbea: karolherbst: i might have to make a new one later, I'll get back to you
21:05HungGarRebel: hi guys, I'm having an issue with HDMI being labelled (unplugged) by pavucontrol
21:05HungGarRebel: it works sometimes, but I can't seem to find a consistent usecase
21:06HungGarRebel: according to google, it's been a not uncommon issue but nowhere details any kind of actually solution that I've been able to find
21:06HungGarRebel: would you guys have any experience in this issue?
21:11karolherbst: HungGarRebel: you mean audio over HDMI?
21:13HungGarRebel: karolherbst: yes, I'm running my audio through a HDMI screen
21:14karolherbst: never experienced those kind of issues
21:14HungGarRebel: karolherbst: the screen obviously works fine and the audio has worked in the past, everytime I reset my computer the default seems to be from pavucontrol (pulse audio) to label my HDMI audio device unplugged
21:15karolherbst: it could be some driver issue not being able to properly detect that audio can be used over HDMI
21:15karolherbst: but... mhh
21:16HungGarRebel: I'm using latest nouveau driver in 4.14.82-gentoo, and the drivers are all loaded fine
21:17HungGarRebel: like I said, sound has worked in the past. From what I've been able to tell from google-fu, nouveau isn't registering the device as online and seems to be a problem with offical drivers too
21:18HungGarRebel: either that or it's Pulse audio conflicting in some way something
21:20karolherbst: but the audio device shows up, correct?
21:23karolherbst: HungGarRebel: btw, is this on a laptop or just a normal desktop card?
22:00HungGarRebel: karolherbst: it's on a normal desktop GTX950
22:04karolherbst: HungGarRebel: mhh, interesting. I know that there might be some issue with selecting the proper HDMI channel. Like you can have multiple HDMI outputs but only one is the correct one
22:04karolherbst: but besides that I am not aware of anything
22:07HungGarRebel: karolherbst: at the moment they are all labelled as (unplugged) by pavucontrol
22:15karolherbst: HungGarRebel: mhh, what happens if you unplug and plug the monitor again?
22:15karolherbst: I am not entirely sure who is actually responsible here
22:15karolherbst: but the chances are high that most of that isn't handled by nouveau
22:15karolherbst: might be worth the time asking some alsa or pulse devs
22:21HungGarRebel: karolherbst: I'm looking into that now, #pulseaudio has been very helpful. the problem seems to be below that layer, so I'm hoping #alsa can help me to dig something up