Bug 831868 - kernel update failed
Summary: kernel update failed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: rt3
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Ralf Corsepius
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-14 00:37 UTC by Gary McKnight
Modified: 2012-06-14 07:00 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-06-14 07:00:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Gary McKnight 2012-06-14 00:37:08 UTC
Description of problem:

While installing updates I am getting following results:

ERROR with transaction check vs depsolve:
kernel-uname-r = 2.6.35.14-100.fc14.x86_64 is needed by kmod-nvidia-2.6.35.14-100.fc14.x86_64-1:280.13-2.fc14.3.x86_64
kernel-uname-r = 2.6.35.14-103.fc14.x86_64 is needed by kmod-nvidia-2.6.35.14-103.fc14.x86_64-1:280.13-2.fc14.4.x86_64
kernel-uname-r = 2.6.35.14-106.fc14.x86_64 is needed by kmod-nvidia-2.6.35.14-106.fc14.x86_64-1:280.13-2.fc14.6.x86_64


I isolated this to a Linux Kernel update:
The Linux Kernel
kernel-3.3.7-1.fc16 (64-Bit)

Which during or after the install attempt offers the following:

nividia kernel module(s) for 3.3.1-3.fc16x86_64
kmod-nvidia-3.3.1-3.fc16x86_64-1:295.33-2fc16.3(64-bit)

Attempting to install the Nividia update results in another error message:
Failed to process

The package id's '' are not valid



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Petr Pisar 2012-06-14 07:00:37 UTC
The kmod-nvidia is not provided by Fedora. You need to report this bug to right developers---RPM Fusion (https://bugzilla.rpmfusion.org/buglist.cgi?query_format=advanced&order=Importance&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=nvidia-kmod&product=Fedora).


Note You need to log in before you can comment on or make changes to this bug.