For what it's worth: I just installed the 4.13.2 kernel from the kernel-stabilization repo, and the nvidia akmod module (from negativo17 repo) failed to build (as expected). But after rebooting with the new kernel, the system uses the fallback to nouveau correctly - without any manual intervention. So, from my point of view, it seems everything works as it is supposed to (well, except the compilation failure, but that's got nothing to do with fedora).
Fabio On Fri, Sep 22, 2017 at 10:58 PM Nicolas Chauvet <kwiz...@gmail.com> wrote: > 2017-09-22 20:46 GMT+02:00 <mcatanz...@gnome.org>: > > Oh boy. :) > > > > Does anyone know if the fallback is working properly? Because if so, then > Just restoring the fact here, because despite the fallback idea is > hans/WG the implementation is "RPM Fusion Community" original works. > (1) > So yet as soon as you are using "RPM Fusion", it works as expected. > > And furthermore, if you want to switch from nvidia to nouveau while > the nvidia driver remains installed, you just need to unblacklist > nouveau from cmdline (remove rd.driver.blacklist=nouveau > modprobe.blacklist=nouveau). > This is only implemented by the RPM Fusion "clean design". > > And could even be improved: > https://bugzilla.redhat.com/show_bug.cgi?id=1489317 if anyone cares... > > > (1) > https://bugzilla.rpmfusion.org/show_bug.cgi?id=4498 > > > -- > - > > Nicolas (kwizart) > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org >
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
