public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gummiboot does not display new kernel
Date: Sun, 8 Mar 2015 11:09:15 -0600	[thread overview]
Message-ID: <CADPrc83=UOd1ADTWBQtFnu7B6xK-YDg9forveTxdLr5gwNCBWg@mail.gmail.com> (raw)
In-Reply-To: <54FC7AD1.3070202@xunil.at>


[-- Attachment #1.1: Type: text/plain, Size: 1132 bytes --]

On Sun, Mar 8, 2015 at 10:37 AM, Stefan G. Weichinger <lists@xunil.at>
wrote:
[...]
> moved e55a6b6a09bd2b1c50216272545a8d1f-3.19.1-gentoo.conf to simply
> "stefan.conf" ... then it gets displayed (and boots fine as well)
>
> maybe we should name the conf-files in a different way?

For the sake of testing it, I copied my 3.19.0 entry into a 3.18.9 and
3.19.1 entries and rebooted. Here it works fine Stefan (see attached
image); I don't know why it doesn't with yours.

I see you have some grub related files in your /boot directory. I don't
have those:

# tree -L 2 /boot
/boot
├── db93dd0e1382198eb26650c05430b171
│   ├── 3.18.9
│   ├── 3.19.0
│   └── 3.19.1
├── EFI
│   ├── Boot
│   ├── gummiboot
│   └── Microsoft
└── loader
    ├── entries
    ├── gentoo.bmp
    └── loader.conf

10 directories, 2 files

I don't think it has anything to do, but AFAICS, it's the only difference.

Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

[-- Attachment #1.2: Type: text/html, Size: 1494 bytes --]

[-- Attachment #2: gummiboot.jpg --]
[-- Type: image/jpeg, Size: 136369 bytes --]

  parent reply	other threads:[~2015-03-08 17:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08 15:34 [gentoo-user] gummiboot does not display new kernel Stefan G. Weichinger
2015-03-08 15:59 ` 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 [this message]
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='CADPrc83=UOd1ADTWBQtFnu7B6xK-YDg9forveTxdLr5gwNCBWg@mail.gmail.com' \
    --to=caneko@gmail.com \
    --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