Since Matthew Saltzman was clear about it: "I'm surprised the thread has gone on this long without pointing this out: "If you install the akmod-nvidia package, it will rebuild the driver automatically when you boot a new kernel." http://www.mail-archive.com/fedora-list@xxxxxxxxxx/msg49518.html and there certainly was no strong disagreement, after I received the 2.6.29.6-217.2.7.fc11.x86_64 kernel, I installed akmod-nvidia and rebooted. It didn't work. About 2 hours later, the kmod module was available and I knew it had worked well until now. So, I uninstalled akmod and rebooted. It didn't work. I un/reinstalled the kernel. Didn't work. Uninstalled/installed kmod. Didn't work. On the first reboot, I got something like: audit(xxx):auid=xxx ses=xxx subj=system_u:system_r:readahead_t:50 op=remove rulekey=(null) list=2 res=1 audit(xxx):audit_enabled=0 old=1 auid=xxx ses=xxx subj=system_u:system_r:readahead_t:50 res=1 Then, when I reboot, the boot process stops at eth0:link up or Starting atd: [OK]. Then it freezes. Of course, YMMV, but, as far as I'm concerned, I wouldn't advise anybody to use akmod-nvidia. Any way out of this mess? -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
