22:22CheetahPixie: How do I get 2D/3D acceleration working on Nouveau?
22:22CheetahPixie: Specifically, on an nv50.
22:23CheetahPixie: I have installed the supposedly required package, nouveau-firmware, in Kubuntu, yet I am still stuck on a modesetting driver.
22:23CheetahPixie: Well, the GL renderer says Nouveau, but on KDE I still have terrible performance.
22:24imirkin: nv50, like G80?
22:24imirkin: or just nv50-era
22:24CheetahPixie: G96, to be specific
22:25imirkin: well, sounds like you have it working
22:25imirkin: KDE on nouveau isn't great
22:25CheetahPixie: Then why am I getting horrid screen tearing?
22:25imirkin: you really don't want the modesetting driver, you want xf86-video-nouveau
22:25CheetahPixie: I have that.
22:25imirkin: pastebin xorg log?
22:25CheetahPixie: But xrandr --listproviders shows modesetting.
22:25imirkin: ok, so it's not getting used
22:26imirkin: some distros are force-disabling xf86-video-nouveau
22:26CheetahPixie: How do I check for this
22:26CheetahPixie: And why is this being done?
22:26imirkin: so you have to explicitly say Driver "nouveau"
22:26CheetahPixie: Where at?
22:26imirkin: check xorg log
22:26imirkin: debian and redhat have patches for this, i believe
22:26CheetahPixie: what am I looking for here?
22:26imirkin: modeset(0) or NOUVEAU(0)
22:27imirkin: but this won't necessarily help with tearing
22:28CheetahPixie: i'm seeing a bunch of modeset(G0)
22:28imirkin: can you just pastebin the log?
22:28CheetahPixie: give me a moment or two
22:28imirkin: instead of playing 20 questions
22:30CheetahPixie: on cursory examination before binning, i notice that the nouveau module has no LoadModule line
22:31CheetahPixie: but modesetting does, however
22:31joepublic: if only there were some way to see a log of what's going on
22:32CheetahPixie: well, there it is
22:32CheetahPixie: why is the nouveau driver being forcibly disabled by distros?
22:33imirkin: no clue - skeggsb authored the patch for redhat, and somehow debian copied it too
22:33imirkin: i think xf86-video-nouveau is almost always superior, with the very rare exception
22:33CheetahPixie: is this defined in a blacklist?
22:34imirkin: since he works for RH and is the official nouveau maintainer, not a ton i can do
22:34imirkin: it's a literal patch to skip over nouveau in the xorg module list
22:35CheetahPixie: so whatever is loading the modules just outright skips it
22:35CheetahPixie: so not in a blacklist?
22:35CheetahPixie: why wasn't it blacklisted instead of this?
22:36CheetahPixie: well anyway, how do i now "forcibly enable" it back?
22:37imirkin: add a Device section to your xorg.conf with Driver "nouveau" in it
22:37imirkin: should be all that's needed
22:37CheetahPixie: where would i create the xorg file?
22:38CheetahPixie: been forever since i had to touch that
22:42CheetahPixie: https://i.imgur.com/9NFKMyd.png and is this literally all the file needs?
22:45CheetahPixie: at this point, i'm hazarding a guess that that's it
22:46karolherbst: imirkin: btw, I am pretty convinced, that we actually have some memory leaks in mesa somewhere, which is probably causing most of the issues with the modesetting driver as other drivers don't see the same ENOMEM errors as we do with nouveau :/
22:46karolherbst: might make sense to investigate this deeper
22:46karolherbst: but I don't have a proper idea on how
22:47imirkin: CheetahPixie: yes, that's what needed. dump it on a 90-mine.conf file in /etc/X11/xorg.conf.d
22:47CheetahPixie: any specific reason for that name?
22:49CheetahPixie: unless this is a joke i am not getting
22:49imirkin: they're loaded in order
22:49imirkin: so 90 is a good prefix to use for your stuff
22:49CheetahPixie: so this loads last?
22:49imirkin: mine is ... my lack of imagination
22:49CheetahPixie: and the name is arbitrary, i'm guessing
22:49imirkin: it's done in lexical order of the filenames
22:49CheetahPixie: 90-reenable it is
22:50CheetahPixie: let's reboot and cross our fingers that this thing doesn't modeset after it
22:50imirkin: just have to restart X
22:50imirkin: no reboot required
22:50CheetahPixie: or that, either way
22:50CheetahPixie: so pkill -9 Xorg
22:50CheetahPixie: that work, i guess?
22:51imirkin: or just exit your WM
22:51CheetahPixie: either one
22:51CheetahPixie: i like the nuclear approach
22:51CheetahPixie: anyway, i'm off
22:51imirkin: then you should unplug power to be sure :p
23:21karolherbst: imirkin: any idea on how to implement a proper memory leak checker against vram? Or do you think it would be enough to track allocations in libdrm and dump all non fred memory on application exit?
23:22CheetahPixie: alright then
23:22CheetahPixie: i got it to load up with nouveau
23:22CheetahPixie: but i had to use a module section and a load order
23:22CheetahPixie: but now it's not detecting a display plugged into it
23:22CheetahPixie: that same display works when the boot logo is up for display
23:23CheetahPixie: at least the provider name is now nouveau
23:56karolherbst: CheetahPixie: well it might be a kernel bug, so it wouldn't matter what userspace driver is used
23:57CheetahPixie: after a bit of probing around, I noticed xorg picked the edid up
23:57CheetahPixie: ...and then i had the wild idea to check monitor settings for panels that were off
23:57CheetahPixie: lo and behold, there it was
23:57CheetahPixie: and now on
23:57CheetahPixie: and afaict properly accelerated
23:58karolherbst: ahh, but it should be accelerated with the modesetting driver as well.. but yeah, probably you will have less issues with the nouveau one
23:58CheetahPixie: although as soon as there's stuff on the display, I get very occasional hiccups in games
23:59karolherbst: stuff isn't perfect sadly