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 (<imirkin at 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
On Fri, Apr 10, 2020 at 2:06 PM Jes?s J. Guerrero Botella <jesus.guerrero.botella at gmail.com> wrote:> > 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. :)Perfect so far!> > El lun., 30 mar. 2020 a las 13:38, Ilia Mirkin > (<imirkin at 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.Note that glxgears is primarily a measure of PCIe bandwidth in these setups than actual render performance (basically it's just ferrying those frames over the PCIe bus as fast as possible to the Intel GPU). Not sure which intel chip you have ... if it's a SNB, it should be faster and more featureful (you get GL 4.3 advertised and all the GL 4.5 and most 4.6 exts). If it's IVB or HSW, then it'll be a bit slower, I expect (esp HSW).> > 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.I'm impressed you got this far. You shouldn't need envyas to build, by the way, only to regenerate after editing fuc source. So ... this is a funny repository. Basically it's meant to work alongside the linux kernel tree. It also includes some utilities (like the ones in bin/*) which essentially run nouveau in userspace. This can be useful for nouveau development, but most likely not in your case. What you want to do is grab kernel v4.16-rc5 (or v4.16 if you're feeling lucky), build + run that (or alternatively, ask Ben to rebase the branch on a more recent thing ... or even try that yourself). Then go into the "drm" directory and run "make" there. That should cause the nouveau module to get built against your kernel. Then use that built module for your testing (you could make modules_install from there, as I recall). Cheers, -ilia
Hi! Rrright, I will be giving this a try today or tomorrow, as time permits. Hints will come in handy, certainly. First thing I'll need is gcc 7.5, since that kernel version won't compile on 8 or 9 which are the versions I have at hand at the momment. So compiling that now. It'll take a bit on my laptop. I will come back when I have some (maybe useful) feedback. Cheers and thank you for all the guidance, it's quite appreciated. El vie., 10 abr. 2020 a las 20:23, Ilia Mirkin (<imirkin at alum.mit.edu>) escribi?:> > On Fri, Apr 10, 2020 at 2:06 PM Jes?s J. Guerrero Botella > <jesus.guerrero.botella at gmail.com> wrote: > > > > 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. :) > > Perfect so far! > > > > > El lun., 30 mar. 2020 a las 13:38, Ilia Mirkin > > (<imirkin at 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. > > Note that glxgears is primarily a measure of PCIe bandwidth in these > setups than actual render performance (basically it's just ferrying > those frames over the PCIe bus as fast as possible to the Intel GPU). > Not sure which intel chip you have ... if it's a SNB, it should be > faster and more featureful (you get GL 4.3 advertised and all the GL > 4.5 and most 4.6 exts). If it's IVB or HSW, then it'll be a bit > slower, I expect (esp HSW). > > > > > 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. > > I'm impressed you got this far. You shouldn't need envyas to build, by > the way, only to regenerate after editing fuc source. > > So ... this is a funny repository. Basically it's meant to work > alongside the linux kernel tree. It also includes some utilities (like > the ones in bin/*) which essentially run nouveau in userspace. This > can be useful for nouveau development, but most likely not in your > case. > > What you want to do is grab kernel v4.16-rc5 (or v4.16 if you're > feeling lucky), build + run that (or alternatively, ask Ben to rebase > the branch on a more recent thing ... or even try that yourself). Then > go into the "drm" directory and run "make" there. That should cause > the nouveau module to get built against your kernel. Then use that > built module for your testing (you could make modules_install from > there, as I recall). > > Cheers, > > -ilia-- Jes?s Guerrero Botella