public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] gummiboot does not display new kernel
Date: Sun, 08 Mar 2015 16:34:28 +0100	[thread overview]
Message-ID: <54FC6C04.6030705@xunil.at> (raw)



Hmm, what is my mistake ...

I compiled the latest gentoo-sources-3.19.1 with Canek's kerninst tool.

It is configured to generate a "loader-entry" for the gummiboot bootloader.

That bootloader is the default entry in the UEFI boot order and it works
... I can boot the older kernels ... but it does not show me the latest
kernel 3.19.1 .... but why?

I edited /boot/loader/loader.conf ... a changed timeout gets read ...
but 3.19.1 is never displayed.

-

See the content of my ESP here ->

# tree -L 1 /boot/loader/entries/
/boot/loader/entries/
├── e55a6b6a09bd2b1c50216272545a8d1f-3.18.6-gentoo.conf
├── e55a6b6a09bd2b1c50216272545a8d1f-3.19.0-gentoo.conf
└── e55a6b6a09bd2b1c50216272545a8d1f-3.19.1-gentoo.conf

# tree /boot/e55a6b6a09bd2b1c50216272545a8d1f/
/boot/e55a6b6a09bd2b1c50216272545a8d1f/
├── 3.18.6-gentoo
│   ├── initrd
│   └── kernel
├── 3.19.0-gentoo
│   ├── initrd
│   └── kernel
└── 3.19.1-gentoo
    ├── initrd
    └── kernel

# tree -L 2 /boot
/boot
├── e55a6b6a09bd2b1c50216272545a8d1f
│   ├── 3.18.6-gentoo
│   ├── 3.19.0-gentoo
│   └── 3.19.1-gentoo
├── EFI
│   ├── Boot
│   ├── EFI
│   ├── gentoo
│   ├── grub_3
│   └── gummiboot
├── grub
│   ├── fonts
│   ├── grub.cfg
│   ├── grubenv
│   ├── locale
│   ├── themes
│   └── x86_64-efi
├── loader
│   ├── entries
│   └── loader.conf
└── memtest86plus
    ├── memtest
    └── memtest.netbsd


             reply	other threads:[~2015-03-08 15:36 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08 15:34 Stefan G. Weichinger [this message]
2015-03-08 15:59 ` [gentoo-user] gummiboot does not display new kernel Tom H
2015-03-08 16:10   ` Stefan G. Weichinger
2015-03-08 16:37     ` Stefan G. Weichinger
2015-03-08 16:53       ` Canek Peláez Valdés
2015-03-08 16:59       ` Tom H
2015-03-08 17:09       ` Canek Peláez Valdés
2015-03-08 18:10         ` Stefan G. Weichinger
2015-03-08 19:57           ` Stefan G. Weichinger
2015-03-08 20:17             ` Canek Peláez Valdés
2015-03-08 21:35               ` Stefan G. Weichinger
2015-03-08 20:21             ` Fernando Rodriguez
2015-03-08 21:37               ` Stefan G. Weichinger
2015-03-08 22:20                 ` Fernando Rodriguez
2015-03-09  8:16                   ` Stefan G. Weichinger
2015-03-10 13:45                     ` J. Roeleveld
2015-04-02 21:06                     ` Stefan G. Weichinger
2015-04-02 21:14                       ` Canek Peláez Valdés
2015-04-02 21:21                         ` Stefan G. Weichinger
2015-04-02 21:27                           ` Stefan G. Weichinger
2015-04-02 21:19                       ` Fernando Rodriguez
2015-03-08 16:51     ` Tom H
2015-03-08 16:56       ` Canek Peláez Valdés
2015-03-08 17:15         ` Tom H
2015-03-08 16:51   ` Canek Peláez Valdés
2015-03-08 17:00     ` Tom H
2015-03-08 17:05     ` Neil Bothwick
2015-03-08 17:11       ` Canek Peláez Valdés
2015-03-11  7:11         ` J. Roeleveld
2015-03-11  7:14           ` Canek Peláez Valdés
2015-03-08 17:23       ` Tom H

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54FC6C04.6030705@xunil.at \
    --to=lists@xunil.at \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox