hobbes1069 at gmail.com
Tue Aug 18 02:30:39 UTC 2009
On Mon, Aug 17, 2009 at 5:29 PM, <gilpel at altern.org> wrote:
> Since Matthew Saltzman was clear about it:
> "I'm surprised the thread has gone on this long without pointing this
> "If you install the akmod-nvidia package, it will rebuild the driver
> automatically when you boot a new kernel."
> and there certainly was no strong disagreement, after I received the
> 18.104.22.168-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?
I know I've been guilty of it at times but you have to be careful
drawing those types of conclusions from one experience. I've used the
akmod-nvidia package for some time without issue and since this is the
first posting I've read where someone did have an issue it doesn't
look to be that common.
First I have to ask, did you install kernel-headers & kernel-devel for
the kernel you're booting? I can't remember off hand but at least one
if not both of those packages are needed. Second, I would suggest
subscribing to the rpmfusion users list since akmod-nvidia is not a
fedora provided package.
More information about the users