On Thu, 2009-08-20 at 11:22 -0400, Tom Horsley wrote: > On Thu, 20 Aug 2009 10:59:40 -0400 > William Case wrote: > > > If you have any guidance or gotcha's that are worth mentioning before I > > write such a script, your wisdom would be appreciated. > > If you are using the rpmfusion nvidia driver, it is quite > difficult to turn off without uninstalling it. It installs > the "nvidia" service that runs at init time to > force xorg.conf point at the nvidia driver. > I am using the rpmfusion nvidia driver. > If you just want to make sure you have an nvidia driver > that matches your kernel, I never had a problem with > installing akmod-nvidia. All it does is build the driver > rpm and install it if it isn't already installed. > I never had a problem with akmod-nvidia either. I have been using it for a least a year now -- until the 2.6.29.6-217.2.8.fc11.x86_64 kernel and the 2.6.29.6-217.2.7.fc11.x86_64 kernel. They wouldn't rebuild but my system would default to the vesa driver after akmod-nvidia was removed. The 2.6.29.6-217.2.3.fc11.x86_64 kernel works fine. > For me it always worked fine. If the rpmfusion repos were > up to date, I'd get the kmod-nvidia from the repo when > I updated, if they weren't up to date, I'd take longer > to boot and I'd get the rpm the akmod built for me. > I removed the akmod-nvidia and reinstalled, just to see. On rebooting, both the .7 and the .8 kernels freeze during init with "r8169: eth0: link up" showing on an otherwise blank screen. I have waited for over 5 minutes for the kernel(s) to rebuild but my machine just remained inactive. That is why I started to use "nouveau". With akmod-nvidia removed and "nouveau" as the device driver, everything worked. Well, kinda! -- Regards Bill Fedora 11, Gnome 2.26.3 Evo.2.26.3, Emacs 23.1.1 -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
