Jump to content
  • 0

boot-update doesnt see 4.0.1


hellomynameisphil
 Share

Question

I recently upgraded vanilla-sources to 4.0.1. I used eselect to select this kernel and went to /usr/src/linux (symlinked to linux-4.0.1) and built the kernel as per http://www.funtoo.org/Building_a_Kernel_from_Source  (using the 'less advanced' instructions). This appears to have been successful. Here is /boot:

phuntoo ~ # ls /boot/

config-3.19.0  config-4.0.1  config-4.0.1.old  initramfs.cpio.gz  System.map-3.19.0  System.map-4.0.1  System.map-4.0.1.old  vmlinuz-3.19.0  vmlinuz-4.0.1  vmlinuz-4.0.1.old

Here is my boot.conf:

boot {

    generate grub



    # Below, you can specify the kernel image to boot by default,

    # or the default boot entry name



    default Funtoo Linux

    # default Windows 7

}



display {

    gfxmode "1366x768"

}



"Funtoo Linux" {

    kernel vmlinuz-4.0.1 vmlinuz-3.19.0

    initrd /initrams.cpio.gz

    params += resume=/dev/sda6

}



"Windows 7" {

    type win7

    params root=/dev/sda3

}

Here is the output of boot-update:

phuntoo ~ # boot-update



boot-update 1.7.2 /

Copyright 2009-2015 Funtoo Technologies



 [use option "-l" for license info, "-h" for help]



 * Generating config for grub...



 DEFAULT > Funtoo Linux - vmlinuz-3.19.0

           Windows 7

 * NOTE : Detected MBR boot. Configuring for Legacy MBR booting.

 * Completed successfully.

Why is boot-update not seeing 4.0.1?

Link to comment
Share on other sites

6 answers to this question

Recommended Posts

  • 0

Figured it out.

 

I generally have /boot on a separate partition. This partition seems to get unmounted automatically after booting is complete. So when I was compiling 4.0.1 and installing the linux kernel binary, it was to a directory called boot in my root file system which is inaccessible when the boot partition is mounted on /boot.

 

I am typing this from 4.0.1. Thanks to all who made suggestions.

Link to comment
Share on other sites

  • 0

Thanks, but that doesnt work either. As per man boot.conf, I should be able to specify which specific kernels I wants to use, all one line. Doing it your way, I only get:

 

 

Funtoo Linux - vmlinuz-3.19.0
Funtoo Linux - vmlinuz-3.19.0.old
Windows 7

 

which is the reason I specified particular kernels; I don't want those crufty *.olds to show up in my boot menu.

Link to comment
Share on other sites

  • 0

Hmm, well you've got me there then.  I specify the kernel line as I suggested and I'm running 4.0.1 just fine.

Of course, the best way to not have those "crufty *.olds" not show up is to delete them before running boot-update, solves the problem and keeps things clean, but that's up to you.

So it seems something is different about your 4.0.1, I agree, man boot.conf says you should be able to do it that way.

Link to comment
Share on other sites

  • 0
  • Funtoo Linux Developer

This is not a valid solution but can still help to figure out the issue: does it work if you set something like this in your boot.conf?

"Funtoo Linux" {

    kernel vmlinuz-3.19.0

    initrd /initrams.cpio.gz

    params += resume=/dev/sda6

}

"Funtoo Linux Test" {

    kernel vmlinuz-4.0.1

    initrd /initrams.cpio.gz

    params += resume=/dev/sda6

}
Link to comment
Share on other sites

  • 0

I'm just guessing here, but I think it is due to trying to make a "generic" initramfs.  Note that both 3.19 versions are working fine as you reported.  I build a new initramfs for each kernel, I think I tried that in the beginning and found out what you are having trouble with.  Also, there's this:

boot # diff initramfs-funtoo-4.0.0 initramfs-funtoo-4.0.1
Binary files initramfs-funtoo-4.0.0 and initramfs-funtoo-4.0.1 differ
boot # ls -l init*
-rw------- 1 root root 8367938 Apr 28 18:58 initramfs-funtoo-4.0.0
-rw------- 1 root root 8366709 Apr 30 05:25 initramfs-funtoo-4.0.1

 

My initramfs' in the boot dir.  Yet they were made in exactly the same way, no changes to dracut.conf, only the kernel referred to dracut changed.  I believe there is more of a difference than just a "0" changed to a "1".  Anyhow, easy to check.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...