| Summary: | kmod-nvidia package needs kernel-uname-r, but that's not available | ||
|---|---|---|---|
| Product: | Fedora | Reporter: | Daniel Brooks <db48x> |
| Component: | nvidia-kmod | Assignee: | Stewart Adam <s.adam> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | fedora, kwizart |
| Priority: | P5 | ||
| Version: | 10 | ||
| Hardware: | All | ||
| OS: | GNU/Linux | ||
| namespace: | |||
|
Description
Daniel Brooks
2009-02-20 22:33:02 CET
On which system do you have the bug ? Do you have compiled your own kernel ? Oh, my apologies. I see this happening on two F10 systems, one upgraded gradually from F3, the other a new install. I'm using the stock Fedora kernels, one is an x86-64 (as you can see from the messages I pasted), and the other is i386. Not completely sure from the details you gave (see below comment), but there is afaics nothing we can do about it on the RPM Fusion site. Afaics the problem is this: - you had kmod for some kernel from F9 installed - you updated from F9 to F10 - anaconda or something else removed those older kernels during the update. But it left the kmod arounds; that should not happen, as the kmods have a strict dependency on the kernel, hence yum (when used by anaconda) should remove them when it uninstalls the kernels from F9 (and in fact yum does that normally when doing regular updates within a release) (In reply to comment #2) > Oh, my apologies. I see this happening on two F10 systems, one upgraded > gradually from F3, the other a new install. I'm using the stock Fedora kernels, > one is an x86-64 (as you can see from the messages I pasted), and the other is > i386. This gets confusing. I guess the errors in the initial report where from the updated machine? Are you sure the error messages on the others are the same issue? (In reply to comment #3) > Not completely sure from the details you gave (see below comment), but there is > afaics nothing we can do about it on the RPM Fusion site. Afaics the problem is > this: > > - you had kmod for some kernel from F9 installed > - you updated from F9 to F10 > - anaconda or something else removed those older kernels during the update. But > it left the kmod arounds; that should not happen, as the kmods have a strict > dependency on the kernel, hence yum (when used by anaconda) should remove them > when it uninstalls the kernels from F9 (and in fact yum does that normally when > doing regular updates within a release) Hmm. Indeed, I do have a few extra copies of kmod-nvidia around that don't correspond to installed kernel versions. Let's see what happens when I remove them all, and attempt to install a new one… Yes, now it works. However, so does my other machine. Did the dependencies change last night? > > (In reply to comment #2) > > Oh, my apologies. I see this happening on two F10 systems, one upgraded > > gradually from F3, the other a new install. I'm using the stock Fedora kernels, > > one is an x86-64 (as you can see from the messages I pasted), and the other is > > i386. > > This gets confusing. I guess the errors in the initial report where from the > updated machine? Are you sure the error messages on the others are the same > issue? > Yes. It was complaining that it cannot install kmod-nvidia because of the same missing dependency, kernel-uname-r (In reply to comment #4) > Hmm. Indeed, I do have a few extra copies of kmod-nvidia around that don't > correspond to installed kernel versions. Let's see what happens when I remove > them all, and attempt to install a new one… > > Yes, now it works. good > However, so does my other machine. Did the dependencies change last night? I guess that was a different error. Likely https://www.redhat.com/archives/fedora-devel-list/2008-August/msg00041.html |