keeping kmod-nvidia and kernel upgrades "in sync"
Thorsten Leemhuis
fedora at leemhuis.info
Sat Aug 12 07:06:00 UTC 2006
Lonni J Friedman schrieb:
> On 8/11/06, Dr. Michael J. Chudobiak <mjc at avtechpulse.com> wrote:
>> I've just started using the livna nvidia driver,
>> kmod-nvidia-1.0.8762-2.2.6.17_1.2157_FC5 . This is obviously meant for
>> use with the 2.6.17_1.2157_FC5 kernel. However, yum is pulling in the
>> latest kernel, 2.6.17-1.2174_FC5 (and making it the default kernel),
>> even though no matching kmod-nvidia is available... isn't yum supposed
>> to look after dependencies like this?
>>
>> How are kernel and kmod-* supposed to be kept in sync? (I'd rather not
>> use yum excludes, if I don't have too).
>
> My guess is that livna hasn't caught up with the kernel yet.
The livna buildsys is unreachable ATM so we couldn't build kmod's for
the new kernel yet. Sorry for the delay. Don't know when it will be
reachable again.
CU
thl
More information about the fedora-list
mailing list