public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gummiboot does not display new kernel
Date: Tue, 10 Mar 2015 14:45:24 +0100	[thread overview]
Message-ID: <4325952.VCq9E0xK2v@andromeda> (raw)
In-Reply-To: <54FD56E3.7010707@xunil.at>

On Monday, March 09, 2015 09:16:35 AM Stefan G. Weichinger wrote:
> On 08.03.2015 23:20, Fernando Rodriguez wrote:
> > On Sunday, March 08, 2015 10:37:22 PM Stefan G. Weichinger wrote:
> >> ... why my initrd is 21M is another question ..)
> > 
> > Do you have proprietary video drivers in it? fglrx alone is 13 megs and if
> > it's for plymouth it doesnt use them so it's just taking space.
> 
> Seems like, yes.
> 
> My dracut.conf was back to default (no options set) so it put everything
> in there.
> 
> I now set
> 
> hostonly="yes"
> 
> and the initrd went from 21M to ~7M ... nice!
> 
> thanks!
> 
> -
> 
> I rebuilt all the kernels/initrds and now have these loader-entries:
> 
> # ls -l loader/entries/
> total 2
> -rwxr-xr-x 1 root root 329  9. Mär 09:04
> e55a6b6a09bd2b1c50216272545a8d1f-3.19.0-gentoo.conf
> -rwxr-xr-x 1 root root 329  9. Mär 09:01
> e55a6b6a09bd2b1c50216272545a8d1f-3.19.1-gentoo.conf
> -rwxr-xr-x 1 root root 311  9. Mär 09:06
> e55a6b6a09bd2b1c50216272545a8d1f-4.0-rc2.conf
> -rwxr-xr-x 1 root root 329  8. Mär 17:34 stefan.conf
> 
> And the 3.19.1 still does not get displayed at boot time!
> 
> ;-)

Just a guess, but is it possible the length of the file is such that gummiboot 
thinks the 3.19.0 and 3.19.1 config file is the same (based on 
"right(filename,x)" with 'x' being the length up to ....3.19 ?

I don't use gummiboot (or UEFI yet) to test myself.

--
Joost




  reply	other threads:[~2015-03-10 13:46 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
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 [this message]
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=4325952.VCq9E0xK2v@andromeda \
    --to=joost@antarean.org \
    --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