yum update from 3.14.4 looks ok, but still stuck 3.14.4-200.fc20.x86_64

Sudhir Khanger sudhir at sudhirkhanger.com
Sun Jun 15 02:44:00 UTC 2014


On Sun, Jun 15, 2014 at 8:09 AM, Jackson Byers <byersjab at gmail.com> wrote:
> Solved:aaaaaa
> after
> "grub2-install /dev/sda"
> and rebooting, I now get 3.14.7:
> $ uname -rsvp
> Linux 3.14.7-200.fc20.x86_64 #1 SMP Wed Jun 11 22:38:05 UTC 2014 x86_64
>
>
>  what  still puzzles me :
>  sometimes I don't need the
>  "grub2-install /dev/sda"
> when doing yum update...
>
> Jack
>
>
> On Sat, Jun 14, 2014 at 5:19 PM, Jackson Byers <byersjab at gmail.com> wrote:
>>
>> yum update from 3.14.4 looks ok
>> in /boot
>> vmlinuz-3.14.3-200.fc20.x86_64
>> vmlinuz-3.14.4-200.fc20.x86_64
>> vmlinuz-3.14.7-200.fc20.x86_64
>>
>> I can't seem to get 3.14.7 to 'take'
>> after reboot still in 3.14.4
>>
>> exact command used for update:
>>
>> yum update && grub2-mkconfig -o /boot/grub2/grub.cfg
>>
>> followed by a reboot,
>>
>> still get:
>> $ uname -r
>> 3.14.4-200.fc20.x86_64
>>
>
> --
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>

You only have to do "grub2-install /dev/sda" when you install the
system, Anaconda does that for you, or if you mess your grub. And
after that you recreate grub.cfg. When a new kernel is installed, it
automatically recreates the grub.cfg.

If you have to reinstall grub2 at every kernel upgrade that should
probably go to bugzilla.

-- 
Regards,
Sudhir Khanger.
sudhirkhanger.com
https://github.com/donniezazen


More information about the users mailing list