Re: [gentoo-user] grub2 boots only older kernel

[wireless@tampabay.rr.com]

On 05/19/14 19:00, wraeth wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 20/05/14 05:26, James wrote:
>> Hello,
>
> Greetings :-)
>
>> I even copied of the .config file from 3.13.6 to 3.14.4, answered the
>> questions and issued:
>
> By "answered the questions" can I assume this to mean `make oldconfig`?
>
>> make && make modules_install cp arch/x86_64/boot/bzImage
>> /boot/kernel-3.14.4-gentoo cp System.map /boot/System.map-3.14.4-gentoo cp
>> .config /boot/config-3.14.4-gentoo grub2-mkconfig -o /boot/grub/grub.cfg
>
> This looks fine.
>
>> GRUB_DEFAULT=kernel-3.14.4-gentoo GRUB_HIDDEN_TIMEOUT=3 GRUB_TIMEOUT=10
>> GRUB_GFXMODE=1024x768 GRUB_DISABLE_RECOVERY=true
>
> This also looks fine
>
>> I need ideas as where to look, what to fix  to get a newer kernel booting
>> from grub2.  Not any changes since 3.13 series was first used: (3.13.1)
>> Note this problem started with kernel 3.13.7-gentoo and has persisted
>> through 3.14.4.  I have even diff the .config files [1]
>
> For anyone to give you a useful answer, we would need more detailed
> information about your specific issue - for example:
>
> - - how far through the boot process does the "broken" kernel get?
> - - Are there any error messages or stack traces?
> - - Is there any display at all?
> - - What is the kernel cmdline used to boot the kernel?
> - - Do you use an initramfs?

It never tries to boot. Grub just sits there  withe phrase (did not copy 
it down) where it says what version it will boot on the screen
and it does nothing (locked up?) I have to <cntl><alt><del> or push
a manual reset. It never tries to load the kernel. Does not matter if
I try a 3.13.7 or 3.14.x, I've rebuilt them quite a few times and did
all the grub2 steps, but none of the newer kernels will boot.

Nothing was done to the bios. The only change was to get rid of ATI 
Frame buffer support as suggested upon a recent update:

* Checking for suitable kernel configuration options...
         *   CONFIG_FB_RADEON:    should not be set. But it is.
         * Please check to make sure these options are set correctly.
         * Failure to do so may cause unexpected problems.




James