00:01skeggsb_: no, but my guess would be "something subtle"
00:08pmoreau: And it happens to another guy when using his G84 as a secondary card and an AMD as main (see https://bugs.freedesktop.org/show_bug.cgi?id=82714), so it doesn't like I can blame Apple this time.
00:08pmoreau: s/like/look like
00:13pmoreau: Or rather he has the same issue starting with 4.0-rc6.
05:26millerthegorilla: hi, I've got a gm107 750ti card and I was wondering if I could help in any way. I'm primarily a desktop user but I do a little programming now and again in c and python etc
05:27millerthegorilla: I'm going to try doing a mmiotrace and extract the blob to get the nouveau driver working with my xubuntu
05:37marcus: hi all. i am using nouveau on the latest 4.0.0-1 kernel and got the following effect: when booting with kms enabled, the GDM display manager input (keyboard / mouse) lags. The desktop environment works correctly afterwards.
05:37marcus: using nomodeset, everything works as expected
05:43mupuf: millerthegorilla: hey, update to linux 4.0
05:43mupuf: you won't need fw with this kernel
05:44mupuf: and you may do some testing
06:05millerthegorilla: gm107 support in kernel 4? yay!
06:07marcus: at least kms handover does not seem to work yet exactly with this card
06:09millerthegorilla: will i need nomodesetting option?
06:40mupuf: millerthegorilla: nope
06:41mupuf: marcus: what do you mean by kms handover? Do you mean seamless plymouth -> gdm transition?
08:35millerthegorilla: I just tried the kernel 4.0 with the nouveau driver on a fresh install of xubuntu daily build with a 750ti gm107 and I've got some problems. Firstof all, the screen boots up as white, and on mouseclick shows the login screen. Then I set the display to show a secondary monitor, not mirrored, and now when I login, I get a white screen that then returns me direct to the login screen.
08:38millerthegorilla: Also, I can't change the primary display resolution from 1024x768. The resolution is incorrectly reported at first, and when I try and change the resolution xubuntu resets to the login screen after a white out.
08:45millerthegorilla: do you know if other ttys other than lightdm will be available eventually with the gm107?
08:55imirkin: millerthegorilla: 4.1 will have GM107 acceleration support... 4.0 doesn't
08:55imirkin: millerthegorilla: the white thing is weird
08:56millerthegorilla: I just resumed from recovery mode and no problems but I don't know which kernel command line options to set to acheive the same result.
08:57imirkin: probably 'nomodeset'
09:01millerthegorilla: yh, I just checked and it is nomodeset. The problem with this is that my secondary monitor is not detected.
09:06millerthegorilla: immirkin: do you know when the first 4.1 kernel will be available to test accelerated nouveau gm107?
09:08imirkin: millerthegorilla: you could grab http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next
09:10millerthegorilla: thanks, do I then compile the drm source from there as a module?
09:10millerthegorilla: Or do I have to add it to the source tree of the kernel source and recompile the kernel?
09:11imirkin: oh, if you already have a built source tree, you can build
09:11imirkin: cd drm; make -j8
09:11imirkin: that will build just a nouveau.ko module
09:13imirkin: btw, is the "white screen" thing new as of 4.0?
09:15millerthegorilla: I think so, I'll have to login again on the vivid standard kernel but I have to warn you, this is a mac pro 1.1 and I have other issues, such as the card not being detected on the primary pci-e slot due to most likely a efi 32 bit incompatibility
09:24millerthegorilla: So I just tried the 3.19 kernel that comes installed with the dailybuild and the same white screen problem. I'm sure it is fine with no modeset- Earlier here, I was informed that - marcus> at least kms handover does not seem to work yet exactly with this card
09:24imirkin: i think he was talking about his own issues
09:25millerthegorilla: oh yh. sorry.
09:26imirkin: several people with GM107's have been using them just fine
09:26imirkin: i'm not 100% sure that they had multiple screens, but i think it's possible
09:26imirkin: btw -- you're not doing something funky like trying to use DP MST are you?
09:26imirkin: coz that won't work :)
09:26millerthegorilla: perhaps it is a daily build xfce issue. I've read others getting login restarts
09:26millerthegorilla: dunno what dp mst is?
09:26imirkin: how are the screens connected?
09:27millerthegorilla: same card, vga for the primary and hdmi for the secondary
09:29imirkin: you're good then -- DP MST is when you have multiple displays attached to a single DP port
09:31millerthegorilla: ok. I am starting with nomodeset in the meantime, but have no secondary monitor. Arandr doesn't detect it. Do you have any ideas?
09:31imirkin: yeah. you're using vesa. one monitor.
09:32millerthegorilla: oh yh, nouveau requires modesetting. forgot. So I need to remove the nomodeset option but I get the white screen relogin issue. bummer.
09:34imirkin: if possible, try using the DVI port
09:42millerthegorilla: I can't, the dvi ports are dvi-d and I don't have a working dvi-d monitor
09:43imirkin: well, HDMI == DVI-D
09:43imirkin: if you can get an adapter
09:43imirkin: but i'm guessing you don't have one on-hand
09:49millerthegorilla: unfortunately not. I'm just starting the machine with the hdmi only in place and no whitescreen with nouveau driver. Perhaps it is due to two screens attached in that configuration? I'll try starting on just the vga as well.
09:50imirkin: try with just HDMI, and then attach the VGA after things have started up
09:50imirkin: (things == nouveau)
09:52millerthegorilla: tried that, no vga detected by arandr
09:53imirkin: can you pastebin your dmesg and output of 'xrandr'?
09:54millerthegorilla: what is the pastebin address? (I'm a bit of a noob at irc if you can paste it here somehow :-)
09:54imirkin: i like hastebin -- http://hastebin.com/
09:58imirkin: millerthegorilla: so... it sees your VGA screen
09:59imirkin: millerthegorilla: xrandr --output VGA-1 --left-of HDMI-1 --auto
10:01millerthegorilla: tried it with right-of. Same white-screen relogin screen issue.
10:01millerthegorilla: perhaps an xinit issue. I'll reboot and check the xsession-errors.
10:02imirkin: which screen became white?
10:02millerthegorilla: both of them
10:02millerthegorilla: with a mouse cursor over both of them (mirrored display)
10:03imirkin: sounds like a disp/gm107 fail -- skeggsb_ --^
10:03imirkin: millerthegorilla: can you open a bug on bugs.freedesktop.org (xorg -> Driver/nouveau), and attach your vbios (available at /sys/kernel/debug/dri/0/vbios.rom)
10:03millerthegorilla: could be. When I first installed, I tried the guest account and like the main account, the login prompt was being displayed over the top of the booting dekstop manager
10:13millerthegorilla: ok. done that.
10:14millerthegorilla: if the new 4.1 module gives acceleration will the gallium 9 d3d drivers work?
10:18millerthegorilla: many thanks for your help btw.
10:25imirkin_: millerthegorilla: in theory, yes
10:25imirkin_: millerthegorilla: btw, it'd be worth trying that standalone repo i pointed you to, perhaps your issue is magically fixed
10:25imirkin_: although... i don't think it is
10:28millerthegorilla: will there ever be support for multiple vts?
10:29imirkin_: that's not a nouveau feature... it's a linux feature
10:29imirkin_: afaik one it's had since the earliest days
10:30imirkin_: although i wouldn't bet that linus's original linux kernel release back in the day had them
10:36millerthegorilla: why doesn't the latest nouveau support it?
10:36imirkin_: pretty sure it has nothing to do with nouveau :)
10:36imirkin_: if you don't have vt's, it's coz you did something funny
10:36imirkin_: like disabled CONFIG_VT or who knows what else
10:36imirkin_: (or perhaps you just don't have getty's running on the other vt's which makes it seem like you don't have them)
10:37imirkin_: i think i heard something about arch only setting up 1 vt by default
10:37imirkin_: perhaps it was another distro
10:51millerthegorilla: its xubuntu vivid, so there should be other vts. I'm running the same distro on my radeon laptop, and I've got vts ok. Its really annoying not having them
10:52imirkin_: yeah, i'd ask the xubuntu folk -- pretty sure this has nothing to do with nouveau
10:52imirkin_: btw the vbios you uploaded was not the vbios :)
10:53imirkin_: it was the literal text of the vbios path i gave you...
10:55millerthegorilla: How do I transfer it to a file to upload. Can I just steer the upload dialog to the path you gave me?
10:55imirkin_: you probably need to be root to read it
10:55imirkin_: do like... cat /sys/class/... > nv117-vbios.rom
10:55imirkin_: and then upload that file
11:02millerthegorilla: ok. uploaded that now.
11:03imirkin_: much better :)
11:04imirkin_: and to confirm, on the physical board, you have VGA, DVI-D, and HDMI, right?
11:08millerthegorilla: hdmi, vga and 2 x dvi-d
11:08imirkin_: oh right. that's actually exactly what your vbios says.
11:10imirkin_: weird. both VGA and HDMI appear to be on OR1 -- i didn't think that was allowed
11:11imirkin_: millerthegorilla: can you confirm that vga + hdmi work fine on that particular card with a different setup? (e.g. windows, or nvidia blob drivers)
11:12imirkin_: or have you not tried?
11:16millerthegorilla: I'm farily certain that I've had it working ok before but with different ubuntu. lxde lubuntu I think
11:16imirkin_: and presumably nvidia blob drivers
11:16millerthegorilla: I know the nvidia works ok
11:17imirkin_: ok just checking
11:17millerthegorilla: although I haven't tested it recently, and I still can't get the card recognised at all in slot 0
11:17imirkin_: meh, it's not about recency... just that on that particular card, both vga and hdmi can be turned on at the same time
11:44millerthegorilla: what dependencies do i need for the darktama build?
11:46millerthegorilla: and when I have the nouveau.ko file how do put it in tree?
11:46millerthegorilla: I've not compiled standalone modules before.
11:50imirkin_: you just insmod it like any other
12:27millerthegorilla: just installed that module and no joy, although arandr can now see the monitor ok when I plugin the vga. I'll try a reboot with it plugged in and see what happens
12:27imirkin_: millerthegorilla: but at least it should be accelerated now :)
12:31millerthegorilla: so, I rebooted and still the white screen login. I pulled out the vga, and then logged in from the hdmi monitor on what looked like the vesa. It immediately logged out (no white screen) but back in the nouveau. Logged in fine. How do I test the acceleration? glxgears?
12:32imirkin_: hastebin the output of glxinfo
12:32millerthegorilla: hang on, just did all that with the wrong kernel. doh.
12:39millerthegorilla: same result. still, glxinfo at hastebin.com/ojipunepac.avrasm
12:40imirkin_: you don't have accel
12:40imirkin_: are you sure you loaded the new nouveau.ko file?
12:40imirkin_: can you pastebin dmesg?
12:41millerthegorilla: doesn't the modinfo say its the right module?
12:41millerthegorilla: nouveau project?
12:42imirkin_: modinfo doesn't provide any useful information about currently running thing
12:42millerthegorilla: oh dmesg lots of complaints
12:42imirkin_: it provides fairly generic type info about the file you have in /lib/...
12:42millerthegorilla: I'll paste it now
12:44millerthegorilla: direct firmware load failure...
12:47imirkin_: yeah you're not loading the new module
12:47imirkin_: you're still loading the old one
12:47millerthegorilla: I ran the make command, do I need to run make install?
12:48imirkin_: not sure what that would do
12:48imirkin_: i generally don't trust stuff like that
12:49imirkin_: personally i would blacklist nouveau from being loaded on boot, boot into init 3 (i.e. no X on start), and then manually load in the new nouveau
12:49imirkin_: [actually recent distros still start X in init 3 -- very annoying]
12:49millerthegorilla: well, I'm running the kernel 4.0, which I built from source. I then cloned the darktama into home/src/nouveau and entered the drm folder and then ran make -j 6 (I've only got four processors). I then rebooted.
12:49imirkin_: [and by recent, i mean like 10y old and newer]
12:51millerthegorilla: if i had spare vts then I could shutdown lightdm and rmmod noveau. but I'll have to restart i guess.
12:52imirkin_: actually rmmod nouveau is trickier than it sounds
12:52millerthegorilla: so I'm starting now. If I start in recovery mode is that ok? or should I edit the grub boot line?
12:52imirkin_: no clue what recovery mode is
12:54imirkin_: my suggestion may have been for the "advanced" user... so do whatever way makes the most sense for you
12:57millerthegorilla: ok, I have booted into the recovery mode and have removed nouveau (rmmod nouveau). How do i defintiely modprobe the built nouveau driver?
12:58imirkin_: insmod path/to/nouveau.ko
12:59imirkin_: although the rmmod of nouveau probably left your hw into a horridly bad state
12:59imirkin_: you need to make sure it doesn't get loaded in the first place
12:59millerthegorilla: ok. I'll blacklist it and start again.
13:00imirkin_: (problem is that fbcon binds to nouveau, and so you'd have to unbind it manually)
13:00imirkin_: there are instructions for doing it here: http://nouveau.freedesktop.org/wiki/KernelModeSetting/
13:07millerthegorilla: I've just blacklisted the noveau module and rebooted. Lsmod doesn't show noveau. I ran modprobe path/to/noveau.ko and modprobe states that nouveau.ko is not found despite it being present on a directory listing of that path. Do the permissions need to be set or the ownership changed?
13:08imirkin_: insmod, not modprobe
13:09imirkin_: also you need to modprobe its dependencies
13:09imirkin_: modinfo the nouveau.ko file and modprobe its dependenceis manually
13:09imirkin_: (modprobe normally takes care of this)
13:13millerthegorilla: I've tried modprobing the dependencies manually and modprobe shows no message when I do, but lsmod later shows they are not loaded.
13:13imirkin_: like 'modinfo ttm' didn't work?
13:13imirkin_: 'modprobe ttm'
13:14millerthegorilla: oh hang on a second, I might need to remove the blacklist file.
13:14imirkin_: unless you blacklisted a lot more than nouveau
13:15millerthegorilla: no. I created a file in /etc/modprobe.d/ called blacklist-nouveau.conf with the contents 'blacklist nouveau'. This prevented nouveau from loading when I booted into runlevel 1.
13:16imirkin_: so now 'modprobe ttm' and 'modprobe wmi'
13:16millerthegorilla: I then tried modprobe /home/user/src/nouveau/drm/nouveau/nouveau.ko
13:16imirkin_: that definitely won't work
13:16imirkin_: you have to insmod.
13:17imirkin_: modprobe is an annoyingly almost-useful tool. unfortunately it seems a bunch of functionality got removed from it a while back. and some of it it never had.
13:17imirkin_: loading modules is one of the features it doesn't have.
13:17RSpliet: while insmod doesn't handle dependencies :-(
13:18imirkin_: and i want to murder whoever removed 'modprobe -l'
13:18RSpliet: lsmod not good enough?
13:18millerthegorilla: okayyyyyy.... I always thought that modprobe loaded modules. Ah well, I just insmod and its now there. When I resume, the recovery mode boots with nomodeset, If I reboot, will the custom nouveau driver still be there?
13:18imirkin_: RSpliet: lsmod lists loaded modules...
13:19imirkin_: RSpliet: modprobe -l listed all modules available for loading
13:19RSpliet: oh right
13:19imirkin_: now i have to use find, after forgetting that modprobe -l is gone and cursing
13:19millerthegorilla: wow, that sounds useful.... wtf
13:20millerthegorilla: linux. being buried in complexity and misdirection...
13:20millerthegorilla: think I might get one of those new windows linx tablets....
13:20imirkin_: every system is going to have quirks
13:20imirkin_: esp once you go off the beaten path
13:21millerthegorilla: find is a fairly lengthy way of going about things...
13:21millerthegorilla: in comparison
13:21imirkin_: find /lib/modules/`uname -r`
13:21imirkin_: or ls -lR the same thing
13:21millerthegorilla: ok. cool.
13:22RSpliet: but it sounds like an interesting addition to modinfo imho
13:22imirkin_: or modprobe :)
13:22RSpliet: modinfo -F alias * :p
13:23RSpliet: (no, that doesn't actually work)
13:23millerthegorilla: if I've entered the system with nomodeset, can I start kms?
13:23imirkin_: just insmod nouveau
13:23imirkin_: insmod ignores the kernel cmdline
13:24imirkin_: or rather, insmod doesn't painstakingly parse the kernel cmdline to take stuff that has no business being there and pass it onto modules
13:26millerthegorilla: it doesn't look right. lsmod lists the nouveau driver as loaded, but the resolution is 1024x768 when it should be 1360x768. I think the recovery mode has booted into vesa. I'll try again
13:27RSpliet: 'd you shut down X before loading?
13:27RSpliet: wait, runlvl 1
13:27millerthegorilla: well its recovery mode
13:27imirkin_: millerthegorilla: dmesg will have the story :)
13:28RSpliet: yeah, sorry, I should make a habit of reading the full story before chiming in
13:38millerthegorilla: ok - the custom nouveau is loaded, but now I have font errors, with text disappearing
13:38imirkin_: pastebin glxinfo
13:38millerthegorilla: its barely noticeable! I'll do that now.
13:39millerthegorilla: doh... glxinfo resets to login prompt. lol.
13:39imirkin_: yeah..... the glamor integration in nouveau is kinda teh suck
13:40imirkin_: and i've been lazy about completing the last 5% of my EXA impl
13:40imirkin_: perhaps i'll do that tonight
13:41millerthegorilla: dmesg lists a whole load of unknown symbols. I'll pastebin the output if you don't mind taking a look.
13:42imirkin_: that's probably coz you tried to insmod nouveau before its dependencies were loaded
13:42millerthegorilla: I ran through the dependencies listed in modinfo and modprobed them all. I'll check though.
13:43imirkin_: before you ever tried to insmod nouveau?
13:43imirkin_: just pastebin the log already...
13:44imirkin_: it takes 20x longer when you try to describe what you see isntead of just providing the paste...
13:45imirkin_: yeah. you had tried to load nouveau before inserting its deps. but then you got it right and it's all fine.
13:45imirkin_: looks like everything is happy in dmesg.
13:45imirkin_: ok now pastebin your Xorg.0.log from the crashed X
13:51imirkin_: [ 444.085] (II) AIGLX: Screen 0 is not DRI2 capable
13:51imirkin_: [ 444.085] (EE) AIGLX: reverting to software rendering
13:52imirkin_: i have nfc why that happens
13:52millerthegorilla: does this mean the monitor is not good?
13:52imirkin_: has nothign to do with monitors
13:52imirkin_: stupid glamor
13:52imirkin_: it's the cause of all of humanity's problems :p
13:52millerthegorilla: perhaps if I add oibaf's experimental ppa or maybe xorg-edgers?
13:53millerthegorilla: I know oibaf's is dri2 and dri 3 potentially.
13:53imirkin_: not sure what that's got to do with anything
13:53imirkin_: iirc you had a pretty up-to-date mesa
13:53imirkin_: and you have xf86-video-nouveau 1.0.11 so that's all in order
13:54imirkin_: what you need is EXA support in the ddx so you don't have to use the glamor bs
13:54imirkin_: [actually glamor works just fine for other drivers, so i suspect it's something in nouveau that's causing it to destroy the universe]
13:56millerthegorilla: ah well, it was worth a try. The good news is the dual monitors work, albeit with cool flashing text...
13:56imirkin_: wait, so dual monitors work just fine now?
13:58imirkin_: i wonder what caused the change...
13:58imirkin_: there are no related fixes in that tree since the code that's in 4.0...
13:59millerthegorilla: well, I guess its the custom nouveau with this gm107. Well, never mind. I'll have to wait until its released. Thanks for your help.
14:00imirkin_: if you're willing to test some patches to xf86-video-nouveau, stick around, i might have some soonish, but i don't have a GM107 to test on
14:01imirkin_: (soonish meaning in the next few days or so)
14:01millerthegorilla: yh fine. I'm in the uk, so I'll only be on for another hour, but I can login all tomorrow. I should be able to patch the code, and I can read and write code a little.
14:02imirkin_: def won't have anything in the next hour
14:02millerthegorilla: ok. Are you on this irc thing all day normally?
14:02millerthegorilla: or a forum?
14:03imirkin_: yeah, i'm on irc 24/7
14:03imirkin_: (not always in front of the irc client though)
14:03imirkin_: but i read scrollback and whatnot
14:04millerthegorilla: once I have insmoded nouveau, can I remove the blacklist and expect the same module to load?
14:04imirkin_: you can replace the module you have in /lib/modules though
14:05imirkin_: which is where modprobe looks
14:05millerthegorilla: oh cool
14:07millerthegorilla: where do you publish your patches? Can I clone from darktama repo like tomorrow or something?
14:08imirkin_: usually on github, sometimes i just mail them...
14:08imirkin_: the patch won't be to the kernel module though
14:09millerthegorilla: do you have a github address?
14:10imirkin_: not entirely sure what you're looking for tbh
14:10millerthegorilla: no worries, I'll come back here and shout you. thanks for your help.
16:00voxadam: I've been playing around with the values in /sys/devices/pci.../hwmon/hwmon0 to reduce the noise of the fan on my GPU when idle. I've found some better settings but I'm not sure how to make them permanent.
16:00voxadam: I'm running Fedora BTW.
16:03imirkin_: apply those settings via a script after nouveau loads?
16:05voxadam: I guess I'll write a little systemd unit.
16:06voxadam: How exactly do they hyst (hysteresis) values in hwmon work?
16:07imirkin_: afaik it's just +/- around rising/falling
16:07imirkin_: i.e. if the trip point is, say, 50, and hyst, is, say, 10
16:07imirkin_: then it'll trip at 60 going up and 40 going down
16:07imirkin_: that way if you're hovering around 50, it doesn't keep going up/down
16:08voxadam: Nicely designed. That'll make it easier to really get it dialed in how I want.
16:09imirkin_: i assume you're futzing with the temp settings, not writing to pwm directly?
16:10voxadam: I've been carefuly playing with the pwm_min but not directly controlling the PWM.
16:10voxadam: Automatic control should be done in kernel space.
16:10imirkin_: ok. well dropping pwm_min below like 35 or 30 or whatever isn't recommended
16:11imirkin_: among other things, it'll mess up tachometer readings, although that by itself isn't necessarily a good reason
16:11imirkin_: [depends a lot on the specific hw, could be fine]
16:13voxadam: I've set it as low as zero while carefully watching and logging the temperature. :)
16:13voxadam: It's never dropped the fan below 25.
16:14voxadam: The GPU temp stays around 50°C.
16:17voxadam: I'd love it if I could get the fan to slow even more but it seems to want to stay around 1100 RPM even while idle.
16:18voxadam: I suppose I could rip the card apart and replace the stock fan.
16:38voxadam: imirkin_: Is it possible to hot(un)plug and power down a GPU while a system is idle but keep the main CPU, memory, and whatnot awak to do thier things and then restore the graphics interface when needed?
16:41imirkin_: sure, but you need platform support for that
16:41imirkin_: it's implemented in nouveau using 'runpm' (which is on by default)
16:41imirkin_: it looks for the ACPI methods to do that
16:41imirkin_: and powers the gpu down when nothing's using it
16:41voxadam: Interesting. I'll definitely read up on it.
16:42imirkin_: but that only works in a laptop
16:42imirkin_: or i've heard of super-high-end motherboards which let you do pci hotplug
16:42imirkin_: but i've never actually seen one
16:43voxadam: I don't actually need to physically remove the card, just power it down.
16:43imirkin_: yeah, but the two are closely related :)
16:43imirkin_: i'm not aware of any desktop-class hardware that'll let you do that
16:43imirkin_: but... i could be out of date on it
16:44voxadam: Maybe coreboot could be of help. I was thinking about playing with it for other reasons.
17:28airlied: voxadam: don't think any desktop hw comes with the power off a pcie 16x slot ability
17:28airlied: though I though AMD were looking into it at one point
17:35voxadam: airlied: Interesting. Do current GPUs not support power states as low as a modern CPU's C-states?
19:29koz_desktop: How do I check my reclocking parameters again?
19:29koz_desktop: I remember having to cat something, but I forgot what.
19:33karlton: koz_desktop: cat /sys/class/drm/card0/device/pstate
19:34koz_desktop: Should I be getting a 'no such file or directory'?
19:36koz_desktop: The nouveau driver seems to be working...
19:36koz_desktop:checks kernel params.
19:38koz_desktop: Yeah, why is there no /sys/class/drm/card0/device/pstate for me....
19:39koz_desktop: Fuck yes, my card reclocks correctly!
19:40koz_desktop: Thank you, all you wonderful nouveau developers.
19:40koz_desktop: You are all officially awesome people.
19:40karlton: koz_desktop: that is where it is for me after adding nouvea.pstate=1 to the kernel line
19:41koz_desktop: karlton: I have the following:
19:41koz_desktop: nouveau.pstate=1 nouveau.config=NvClkMode=15,NvForcePost=1
19:41koz_desktop: Although for some reason, I still have awful FPS on Minetest.
19:45karlton: worst fps I have ever gotten on minetest is 25-30
19:46koz_desktop: karlton: What's your card?
19:46koz_desktop: And under what settings?
19:47karlton: gtx 650 ti sc but I only get less than 60 if I turn on full vis range and have lots of trees full settings
19:48koz_desktop: I have a 650.
19:48koz_desktop: And on full settings, even underground, I get, like, 15.
19:49karlton: something is wrong then, because I get better than that even on intel graphics
19:49koz_desktop: Let me try it above ground.
19:50koz_desktop: So it's not the card?
19:50koz_desktop: What else could cause such a big choke on graphical performance?
19:52karlton: I don't know, fps on minetest have never been that bad for me
19:53karlton: that almost sounds like your not using hardware acceleration
19:53koz_desktop: karlton: How could I check this?
19:54karlton: "glxinfo | grep rendering" I think
19:55karlton: it shoudl say yes
19:56koz_desktop: What should I install to get the glxinfo command?
19:56koz_desktop: Because currently, i don't have it.
19:57karlton: it depends on what distro, because for gentoo it comes with mesa
19:58koz_desktop: Never mind, found it. Installing.
19:58koz_desktop: It *does* say yes.
19:59koz_desktop: Could it be something in my Minetest settings?
19:59karlton: I think with 4.12 you should choose OpenGL for rendering in the settings tab
20:00koz_desktop: I did.
20:02karlton: hmm, is minetest the only game that is slow?
20:02koz_desktop: I haven't tried any others. Let me give something else a go.
20:02koz_desktop: StuntRally ought to be a good test.
20:15karlton: koz_desktop: iirc, if you have the GDDR3 version of the card, you can reclock all way to the highest rate
20:16karlton: which means you probably should get the same if not better performance than I am getting
20:41koz_desktop: karlton: I do have that version.
20:44koz_desktop: karlton: On Impossible settings, I get like, 6fps.
20:47koz_desktop: karlton: Even on Normal settings, I get less than 60 fps.
20:47koz_desktop: Is the rest of my machine underpowered or something?
20:50karlton: well, I think I have heard of someone getting 20 fps on a raspberrypi using lowest settings
20:51karlton: if every other game runs fine, something must be wrong with your minetest install
20:52karlton: like it is using software rendering or something
20:55koz_: Well, are those results from StuntRally what I should expect?
20:57karlton: I haven't played it before, but I know something is wrong just not sure what
20:59karlton: did you build minetest from source?
21:01koz_: No - but I can try that.
21:37voxadam: I'd been experiencing lockups/freezes related to Nouveau, well, they were at least video related but I haven't experienced any locksups since upgrading to a 4.0 kernel.
21:37voxadam: Are there any tools to excercise Nouveau and my GPU?
21:38voxadam: The locks often occurred during animated alpha blends and other GL magic.