04:11 kingsley: I'm happy to report that an electronic recycler is willing to sell used video cards to me, super cheaply.
04:11 kingsley: Can you suggest where I might find lists of video cards that 1.) work reliably under linux and 2.) are supported by the most open software?
06:32 phillipsjk: Don't have a list, Bit most ATI/AMD cards should work. Older nvida cars should work, but you will probably have trouble with newer ones. Not sure how well older Matrox cards are supported these days You may have trouble with stuff over 10 years old.
06:34 phillipsjk: Old card dating back to the 90's will have drivers, but modern window managers will be dog slow on hardware that old.
06:37 phillipsjk:is not sure how much 3D is assumed to be accelarated these days: from ~2000 to 2013, mostly lived without 3D accelaration.
08:41 Mittttens: hi
08:42 Mittttens: is anyone aware of an issue (specifically with GK104) of setting gamma to cause horizontal artifacts?
08:43 Mittttens: this happens using software like redshift or gnome's night shift
08:44 Mittttens: although it only occurs using redshift's randr method and not the "vidmode" method
08:45 Mittttens: it also occurs on gnome with night shift turned off, but using gnome-shell by itself does not cause the artifacts
09:07 Mittttens: https://bugs.freedesktop.org/show_bug.cgi?id=111841 posted a bug report here
14:55 stahlsau: servus
14:56 stahlsau: is it known that on some configurations (mine, for example) severe hardlocks occure under X, using nouveau? using a RTX2060
14:59 stahlsau: other specs: Ryzen 2600X (non-OC, non-bug-version,...), linux-5.3.1, ..dunno what else ;-)
15:02 stahlsau: i ruled everything else out (ryzen-bugs, acpi-stuff, energysaving (C6, downvoltings etc.), the hardlocks only stopped when i was using fbdev instead of nouveau. Actually, the system was rock-stable in tty, but in X it locked hard (poweroff needed) after 1 - 30 minutes.
15:07 HdkR: Blacklist Nouveau until it supports Turing? :)
15:10 stahlsau: yep...well, as i read it id does support it, no?
15:11 HdkR: Enough to bring up the display. You won't get any 3D accel
15:12 stahlsau: yes, that's what i thought. but it froze all the time. Just wanna give you a heads up, not complaining
18:29 raket: anyone know how to get nouveau work with svgalib? i wanna play 320x200@154hz on my old crt connected to DVI-I
18:29 raket: (GM200 - GTX 980ti), quakeworld, sourcecode available
18:42 karolherbst: uhm
18:42 karolherbst: raket: I am sure svgalib is super incompatible to modern machines
18:43 raket: but it can use fbdev, but shows no output at all
18:43 raket: (unloading nvidia.ko and using no driver at all it works the vga driver, but limited to 70hz on a crt)
18:44 karolherbst: mhh no idea if that even works with the nvidia driver
18:44 karolherbst: the open source drivers have a compatibility layer to fbdev I think
18:44 karolherbst: but that might be disabled?
18:44 karolherbst: there is _something_ in the kernel for that
18:44 karolherbst: "DRM_FBDEV_EMULATION"
18:45 karolherbst: raket: can you check if modeset isn't set for the nouveau driver?
18:45 karolherbst: the nvidia installer does weird thinks like that and keeps the config files to do that
18:45 karolherbst: kms is kind of required for that fbdev emulation
18:45 karolherbst: (might even work with nvidia_drm.modeset=1)
18:46 karolherbst: "$ grep nouveau /etc/modprobe.d/*" should tell you
18:47 karolherbst:has to go for a few minutes
18:48 raket: zgrep DRM_FBDEV_EMULATION /proc/config.gz
18:48 raket: CONFIG_DRM_FBDEV_EMULATION=y
18:49 raket: karolherbst: i will use the noueveau driver if it works.
18:50 joepublic: if /dev/null is fast I will use it
19:00 raket: karolherbst: thanks for your help! hope you get back soon
19:02 kingsley: phillipsjk: Thank you. I'll try to proceed wisely.
19:09 karolherbst:is back
19:09 karolherbst: raket: did you find any signs of modeset=0 being set on the nouveau driver?
19:11 raket: karolherbst: no there's no modeset=0 set at all, when booting witn nouveau.. well i need to reboot (but it goes from 80x24 to some framebuffer)
19:11 raket: be back in approx 20 minutes.
19:37 karolherbst: raket: no idea why it wouldn't work then... do you get some error message or something?
20:08 raket: karolherbst: back now, let's see what we can do, i uncommented chipset FBDEV in /etc/vga/libvga.config
20:08 raket: karolherbst: nothing really happens, like it's not initalized, do you need a strace dump or something?
20:11 karolherbst: mhhh
20:11 karolherbst: maybe an strace could help here
20:11 karolherbst: please pass in "-s 1024" or something when doing an strace
20:12 raket: strace -fF -s 65536 -o svga.dump ./ezquake.svga is that enough?
20:13 karolherbst: sounds good
20:25 raket: 3693 ioctl(6, FBIOPUT_VSCREENINFO, 0xffa801d0) = -1 EINVAL (Invalid argument)
20:28 raket: karolherbst: http://upload.foppa.dk/files/2019-09-27-22-26-30-cest-svga.dump.xz
20:36 karolherbst: raket: I don't think it's related to the FBIOPUT_VSCREENINFO calls
20:36 karolherbst: not all of them fail
20:37 karolherbst: it would be easier to track down if there would be some kind of error message thrown out by svgalib
20:37 raket: https://github.com/meag/ezquake-source/blob/trunk/vid_svgalib.c
20:42 karolherbst: where is that SIGINT comming from though?
20:43 raket: well it really runs but nothing is displayed on the screen...
20:44 karolherbst: makes sense, mhhh
20:44 raket: did you check vid_svgalib.c ? might the be something that has to be changed?
20:44 karolherbst: people not using fbdev would be the biggest part
20:45 karolherbst: raket: that's the source code right? Maybe I will just try to run it locally
20:47 raket: it's not even developed any more in that old branch, it will only compile on 32bit (u need multilib, and change Makefile to ARCH = x86) and downloads the lib's from https://github.com/ezQuake/ezquake-libs-OBSOLETE
20:48 raket: well it compiles on 64bit and runs fine but will get SIGSEV
20:48 raket: maybe svgalib needs a nouveau driver :-)
20:48 karolherbst: mhh, I miss the assets
20:49 raket: check pm
20:52 karolherbst: mhhh, but it does compile against SDL2 here
20:52 karolherbst: why do you need svgalib?
20:53 raket: because i want to play in 320x200 with the software renderer which was i did from 1997 till 2013
20:56 alkisg:hasn't read anything from this chat except the last line... but.... I was able to get 320x200 in xorg by using low horizsync/vertrefresh values, and it was very funny running trying to run a desktop there
20:56 raket: alkisg: you should use 320 200 308 and add doublescan... :-)
20:57 raket: if your monitor supports 154hz... in 320x200
21:27 raket: Thanks for your help! bye