Here is my problem. My laptop has an NVidia Geforce 310 M graphic card. And since kernel 2.6 I had problems with the display. I had to use nomodeset option in the grub, if not my screen will be off when the xorg starts even though my computer is running.

Fortunately, this problem was fixed in early 3.0 kernels. It was fine until kernel 3.4.x in which the problem was back. So I've been using the old kernel(3.3.x) from my grub list, and reported a bug at bugzilla. But they never replied to my questions about the bug on bugzilla.

Now, the real problem is the update manager says there are software updates and it want to remove the old kernel and install some 3.4.x kernel which I'm not sure if they fixed the problem. If I don't get display, I lost my fedora I should re-install some other OS or OS with kernel 3.3.x

What should I do?

  • How about creating a backup and then trying the new kernel?
    – scai
    Commented Aug 9, 2012 at 13:11

3 Answers 3


If you want to keep your current kernel, I'd suggest installing the yum-plugin-versionlock package, and run yum versionlock kernel-$(uname -r) (while you're booted into the kernel you want to keep). This will tell yum to never replace that version of the kernel.

  • I think this the best answer shu I go for it? I'm still not sure, will there be any problem with dependencies or somehing like that?
    – pahnin
    Commented Aug 10, 2012 at 14:17
  • Error: Package: kmod-VirtualBox-3.5.0-2.fc17.x86_64-4.1.18-1.fc17.3.x86_64 (rpmfusion-free-updates) Requires: kernel-uname-r = 3.5.0-2.fc17.x86_64 Installed: kernel-3.3.7-1.fc17.x86_64 (@updates) ................................................... .............................................. Available: kernel-debug-3.5.0-2.fc17.x86_64 (updates) kernel-uname-r = 3.5.0-2.fc17.x86_64.debug You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
    – pahnin
    Commented Aug 11, 2012 at 6:32
  • @pahnin,you can also versionlock the kmods you have installed.
    – jsbillings
    Commented Aug 13, 2012 at 13:54

I think this is a tricky question...There's no way we could recommend to update or not without being in same situation as you are right now.

@darnir made a good suggestion, my approach would be really close to it, upgrade but keep your old kernel close enough so you can always go back to it. Either downloading the RPM file or backing the kernel itself, its initramfs and its modules.

Also have look at how you could protect a package from being removed:


Also...I was just wondering, which driver are you using? Open source (nouveau) or close source (Nvidia), have you tried both? maybe your bug is only hit on one of them.

I agree with @darnir, your bug report might be helpful.

  • noeavu Nvdia's graphic driver never worked for me
    – pahnin
    Commented Aug 11, 2012 at 6:40
  • The link helped and I updated by by adding 3.3 kernel to pretected.conf and kernel 3.5 is working fine for me. Thanks
    – pahnin
    Commented Aug 12, 2012 at 20:34

Try backing up the current kernel that you are using and make an entry for it in your grub.cfg before you upgrade to the latest one. If the kernel update does not solve your problem, you will always have your current kernel to fallback to.

However, I would suggest you to check online if the problem you are facing has been solved in the current version. You could check forums or the official kernel documentation for bug fixes.

Could you please link me to the bug report you filed for more information?


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .