Hi, Ilia. Sorry for such a big delay in answering. Real life and that stuff...
I am a newcomer so, please, if I do something wrong regarding my quoting style or whatever, just let me know and I'll quickly improve. :) El lun., 30 mar. 2020 a las 13:38, Ilia Mirkin (<imir...@alum.mit.edu>) escribió: > > Yes, GF108 is Fermi (F = Fermi). Reclocking is currently not available > for that generation, unfortunately. You should be able to otherwise > use your GPU just fine, but I'm guessing it'll come up in the "07" > state when it powers on (in the state as-is it appears powered off, > which it will do automatically when not in use), which as you can see > is a fraction of the total GPU available perf. Yes, it comes up in 07 when I launch, let's say glxgears in DRI_PRIME=1. It performs similarly to the intel chip, or maybe a bit worse. For the rest, yes, it mostly works. But it's no good of course. > There's a very experimental branch that does enable reclocking for > Fermi at https://github.com/skeggsb/nouveau/commits/devel-clk . > However I believe it was only tested with a single GPU, and my testing > with an identical such GPU was negative. On the other hand, you don't > have a display hanging off the card, which greatly increases chances > of success. Feel free to join #nouveau on irc.freenode.net if you plan > on exploring this. I fetched that and tried to compile it. First failed because of missing envyas, which I compiled and installed. Then failed with some undefined symbol kind of error which right now I don't have the time to diagnose. If I can get this to compile I'll get back to this thread. Any recommendations on kernel version, compiler or whatever might work better for that branch is welcome though. CCLD bin/nv_rd16 CCLD bin/nv_ws32 CCLD bin/nv_ri08 CCLD bin/nv_wi32 CCLD bin/nv_wi16 CCLD bin/nv_init CCLD bin/nv_ws16 CCLD bin/nv_ri16 CCLD bin/nv_rd32 CCLD bin/nv_rd08 CCLD bin/nv_rs08 CCLD bin/nv_rv32 CCLD bin/nv_perfmon bin/nv_perfmon.c: En la función ‘ui_perfmon_query_signals’: bin/nv_perfmon.c:316:40: aviso: el argumento de ‘sizeof’ en la llamada ‘strncpy’ es la misma expresión que el origen; ¿pretendía usar el tamaño del destino? [-Wsizeof-pointer-memaccess] strncpy(sig->name, args.name, sizeof(args.name)); ^ CCLD bin/nv_rv08 CCLD bin/nv_rs32 CCLD bin/nv_wv08 CCLD bin/nv_wv16 CCLD bin/nv_wf16 CCLD bin/nv_wi08 CCLD bin/nv_rf16 /usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: /tmp/ccYJvy7g.o: undefined reference to symbol 'keypad' /usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: /lib64/libtinfo.so.6: error al añadir símbolos: DSO faltante desde línea de orden collect2: error: ld devolvió el estado de salida 1 -- Jesús Guerrero Botella _______________________________________________ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
