Jump to content
funtoo forums

Search the Community

Showing results for tags 'boot-update'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Funtoo Discussion Forums
    • News and Announcements
    • General Discussion
    • Dev Central
    • Funtoo Hosting
    • Funtoo Infrastructure
  • Help Central
    • General Help
    • Installation Help
    • Portage Help
    • Desktop Help
    • Server Help
  • Funtoo Services

Blogs

There are no results to display.

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


freenode


github


Location


Interests

Found 9 results

  1. Oleg Vinichenko

    ego-2.6.0 released

    ego-2.6.0 released with lot of fixes. This version now also incorporates the boot-update, which was previously a standalone package. To update to new version of ego following steps required: # ego sync # emerge --deselect boot-update # emerge -auDN @world
  2. I followed the instructions in this thread: Now after running "ego sync" and "emerge -auND @world" when I run "emerge -cp" I get the following output: >sudo emerge -cp Password: * Always study the list of packages to be cleaned for any obvious * mistakes. Packages that are part of the world set will always * be kept. They can be manually added to this set with * `emerge --noreplace <atom>`. Packages that are listed in * package.provided (see portage(5)) will be removed by * depclean, even if they are part of the world set. * * As a safety measure, depclean will not remove any packages * unless *all* required dependencies have been resolved. As a * consequence of this, it often becomes necessary to run * `emerge --update --newuse --deep @world` prior to depclean. Calculating dependencies... done! >>> Calculating removal order... >>> These are the packages that would be unmerged: sys-boot/grub selected: 2.02-r1 protected: none omitted: none sys-boot/efibootmgr selected: 15 protected: none omitted: none media-libs/freetype selected: 2.8 protected: none omitted: none sys-libs/efivar selected: 35 protected: none omitted: none All selected packages: =sys-boot/efibootmgr-15 =sys-boot/grub-2.02-r1 =sys-libs/efivar-35 =media-libs/freetype-2.8 >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. Packages installed: 434 Packages in world: 22 Packages in system: 81 Required packages: 430 Number to remove: 4 I have not removed any of the packages listed in the output and wanted to ask if this is expected and intended behavior. Pulling out grub seems a little bit reckless. If I remember correctly, following the Funtoo Install Guide caused grub to be pulled in as a dependency of boot-update. Perhaps the upgrade instructions for ego 2.6.0 should be expanded to cover this. In the meantime I'll just add sys-boot/grub to my world file.
  3. tefrem34

    [Solved]"boot-update" Error

    Hello, I am back at it again. I have not been able to get grub to boot for me. I reinstalled grub and made sure that I changed my grub.cfg to show the "genkernel". However, when I run "boot-update" I get these errors: # boot-update boot-update 1.8.2 / Copyright 2009-2017 Funtoo Technologies [use option "-l" for license info, "-h" for help] * Generating config for grub... * NOTE: Detected UEFI boot. Configuring for UEFI booting. * WARN: Image for section memtest86+ not found - /memtest86.bin * WARN: No boot/default match found - using first boot entry by default. * NOTE: Intel microcode will be loaded at boot-time. * Completed successfully with warnings. I have installed "sys-apps/memtest86+" and I still get the errors. I thank you for the help.
  4. Hi, funtoo noob here. I've just finished installing funtoo on my mid2009 macbook pro (and I'm already very excited about it). Prior to the installation I had installed rEFInd, yet whenever I reboot instead of rEFInd welcome screen (which I do get in my other 'testing' macbook where I also just installed funtoo) I get the grub menu with the only option to boot Funtoo. It's perfectly OK for me to bypass rEFInd and boot directly from grub and I understand that this is possible. My question is how to configure /etc/boot.conf so that I can add a "Mac Os X" entry in my grub menu and boot Os X from there? (Note that my mac Os X partition is /dev/sda2) thanks m
  5. I screwed up my boot partition the other day and had to create the filesystem again and reconfigure grub. I believe that I have everything setup like it was, but for some reason I cannot get it to boot. When I ran the grub-install command, everything seemed to work. (chroot) sysresccd / # grub-install --no-floppy /dev/sda Installation finished. No error reported. But when I ran boot-update, I got an error message that I haven't seen before. Any one know how to fix this? I searched via Google, but didn't see anything definitive. (chroot) sysresccd / # boot-update Traceback (most recent call last): File "/sbin/boot-update", line 15, in <module> import funtoo.boot.config ImportError: No module named funtoo.boot.config Here is my grub.cfg set timeout=10 insmod part_msdos insmod ext2 set root=(hostdisk//dev/sda,msdos1) search --no-floppy --fs-uuid --set eb03fe8e-058d-4e83-83e5-4625800511f8 if loadfont /grub/unifont.pf2; then set gfxmode=1440x900 insmod gfxterm insmod vbe terminal_output gfxterm fi set menu_color_normal=cyan/black set menu_color_highlight=black/cyan menuentry "Funtoo Linux - Gentoo Kernel 3.14.5 - bzImage_linux-3.14.5-gentoo" { insmod part_msdos insmod ext2 set root=(hostdisk//dev/sda,msdos1) search --no-floppy --fs-uuid --set eb03fe8e-058d-4e83-83e5-4625800511f8 linux /bzImage_linux-3.14.5-gentoo rootfstype=ext4 root=/dev/sda3 set gfxpayload=text } set default=0 Here is my /etc/fstab. Pretty simple setup. # <fs> <mountpoint> <type> <opts> <dump/pass> /dev/sda1 /boot ext4 noauto,noatime 1 2 /dev/sda2 none swap sw 0 0 /dev/sda3 / ext4 noatime 0 1 And also /etc/boot.conf boot { generate grub default "Funtoo Linux - Gentoo Kernel 3.14.5" timeout 10 } display { gfxmode 1440x900 #background /boot/ } color { normal cyan/black highlight black/cyan } "Funtoo Linux - Gentoo Kernel 3.14.5" { kernel bzImage_linux-3.14.5-gentoo } "Funtoo Linux genkernel" { kernel kernel[-v] initrd initramfs[-v] params += real_root=auto }
  6. ballsystemlord

    boot-update can't find bzImage

    Hello, I installed funtoo according to the guide but I decided to custom compile the kernel and I used the gentoo-sources and boot-update is complaining about a missing bzImage. I have vmlinux and no initrd, I'm using UEFI booting and I do get the b/w screen. What should I do?
  7. In a fresh funtoo installation i have the problem just after compiling and installing a new kernel with its respective better-initrafms ready to work, the next logical step now is to install a boot loader, in this case i'm following the funtoo installation tutorial: emerge boot-update but fails in the part of emerging grub: Failed Patch: 0002-grub-install-support-for-partitioned-partx-loop-devi.patch ! Ii'm attaching the build log here : [32;01m * [39;49;00mPackage: sys-boot/grub-2.02_beta2-r3 [32;01m * [39;49;00mRepository: gentoo [32;01m * [39;49;00mMaintainer: funtoo [32;01m * [39;49;00mUSE: amd64 binfont elibc_glibc grub_platforms_efi-64 grub_platforms_pc kernel_linux nls userland_GNU [32;01m * [39;49;00mFEATURES: preserve-libs sandbox >>> Unpacking source... >>> Unpacking grub-2.02~beta2.tar.xz to /var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work >>> Unpacking unifont-7.0.01.pcf.gz to /var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work >>> Unpacking unifont-1.0.pf2.xz to /var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work >>> Source unpacked in /var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work >>> Preparing source in /var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work/grub-2.02~beta2 ... [32;01m*[0m Applying various patches (bugfixes/updates) ... [32;01m*[0m 0001-Makefile.util.def-Link-grub-ofpathname-with-zfs-libs.patch ... [A[123C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m 0002-grub-install-support-for-partitioned-partx-loop-devi.patch ... [31;01m*[0m Failed Patch: 0002-grub-install-support-for-partitioned-partx-loop-devi.patch ! [31;01m*[0m ( /usr/portage/sys-boot/grub/files/2.02_beta2/0002-grub-install-support-for-partitioned-partx-loop-devi.patch ) [31;01m*[0m [31;01m*[0m Include in your bugreport the contents of: [31;01m*[0m [31;01m*[0m /var/tmp/portage/sys-boot/grub-2.02_beta2-r3/temp/0002-grub-install-support-for-partitioned-partx-loop-devi.patch.out [31;01m*[0m ERROR: sys-boot/grub-2.02_beta2-r3 failed (prepare phase): [31;01m*[0m Failed Patch: 0002-grub-install-support-for-partitioned-partx-loop-devi.patch! [31;01m*[0m [31;01m*[0m Call stack: [31;01m*[0m ebuild.sh, line 93: Called src_prepare [31;01m*[0m environment, line 4635: Called epatch [31;01m*[0m environment, line 1951: Called die [31;01m*[0m The specific snippet of code: [31;01m*[0m die "Failed Patch: ${patchname}!"; [31;01m*[0m [31;01m*[0m If you need support, post the output of `emerge --info '=sys-boot/grub-2.02_beta2-r3'`, [31;01m*[0m the complete build log and the output of `emerge -pqv '=sys-boot/grub-2.02_beta2-r3'`. [31;01m*[0m The complete build log is located at '/var/tmp/portage/sys-boot/grub-2.02_beta2-r3/temp/build.log'. [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/sys-boot/grub-2.02_beta2-r3/temp/environment'. [31;01m*[0m Working directory: '/var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work/grub-2.02~beta2' [31;01m*[0m S: '/var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work/grub-2.02~beta2' Also i have here the patch.out info: ***** 0002-grub-install-support-for-partitioned-partx-loop-devi.patch ***** PWD: /var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work/grub-2.02~beta2 PATCH TOOL: patch -> /usr/bin/patch VERSION INFO: GNU patch 2.7.5 Copyright (C) 2003, 2009-2012 Free Software Foundation, Inc. Copyright (C) 1988 Larry Wall License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by Larry Wall and Paul Eggert =========================================================================== PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < '/usr/portage/sys-boot/grub/files/2.02_beta2/0002-grub-install-support-for-partitioned-partx-loop-devi.patch' =========================================================================== can't find file to patch at input line 20 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |From e407b6f1e9bf71877104eee2ed513b4065667f60 Mon Sep 17 00:00:00 2001 |From: Mike Gilbert <floppym@gentoo.org> |Date: Sun, 26 Jan 2014 02:56:04 +0100 |Subject: [PATCH 2/5] grub-install: support for partitioned partx loop | devices. | | * grub-core/osdep/linux/getroot.c (grub_util_part_to_disk): Detect | /dev/loopX as being the parent of /dev/loopXpY. | |Conflicts: | ChangeLog |--- | grub-core/osdep/linux/getroot.c | 13 +++++++++++++ | 1 file changed, 13 insertions(+) | |diff --git a/grub-core/osdep/linux/getroot.c b/grub-core/osdep/linux/getroot.c |index 772de0a..19581d3 100644 |--- a/grub-core/osdep/linux/getroot.c |+++ b/grub-core/osdep/linux/getroot.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored patch program exited with status 1 =========================================================================== PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < '/usr/portage/sys-boot/grub/files/2.02_beta2/0002-grub-install-support-for-partitioned-partx-loop-devi.patch' =========================================================================== can't find file to patch at input line 20 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |From e407b6f1e9bf71877104eee2ed513b4065667f60 Mon Sep 17 00:00:00 2001 |From: Mike Gilbert <floppym@gentoo.org> |Date: Sun, 26 Jan 2014 02:56:04 +0100 |Subject: [PATCH 2/5] grub-install: support for partitioned partx loop | devices. | | * grub-core/osdep/linux/getroot.c (grub_util_part_to_disk): Detect | /dev/loopX as being the parent of /dev/loopXpY. | |Conflicts: | ChangeLog |--- | grub-core/osdep/linux/getroot.c | 13 +++++++++++++ | 1 file changed, 13 insertions(+) | |diff --git a/grub-core/osdep/linux/getroot.c b/grub-core/osdep/linux/getroot.c |index 772de0a..19581d3 100644 |--- a/grub-core/osdep/linux/getroot.c |+++ b/grub-core/osdep/linux/getroot.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored patch program exited with status 1 =========================================================================== PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < '/usr/portage/sys-boot/grub/files/2.02_beta2/0002-grub-install-support-for-partitioned-partx-loop-devi.patch' =========================================================================== can't find file to patch at input line 20 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |From e407b6f1e9bf71877104eee2ed513b4065667f60 Mon Sep 17 00:00:00 2001 |From: Mike Gilbert <floppym@gentoo.org> |Date: Sun, 26 Jan 2014 02:56:04 +0100 |Subject: [PATCH 2/5] grub-install: support for partitioned partx loop | devices. | | * grub-core/osdep/linux/getroot.c (grub_util_part_to_disk): Detect | /dev/loopX as being the parent of /dev/loopXpY. | |Conflicts: | ChangeLog |--- | grub-core/osdep/linux/getroot.c | 13 +++++++++++++ | 1 file changed, 13 insertions(+) | |diff --git a/grub-core/osdep/linux/getroot.c b/grub-core/osdep/linux/getroot.c |index 772de0a..19581d3 100644 |--- a/grub-core/osdep/linux/getroot.c |+++ b/grub-core/osdep/linux/getroot.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored patch program exited with status 1 =========================================================================== PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < '/usr/portage/sys-boot/grub/files/2.02_beta2/0002-grub-install-support-for-partitioned-partx-loop-devi.patch' =========================================================================== can't find file to patch at input line 20 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |From e407b6f1e9bf71877104eee2ed513b4065667f60 Mon Sep 17 00:00:00 2001 |From: Mike Gilbert <floppym@gentoo.org> |Date: Sun, 26 Jan 2014 02:56:04 +0100 |Subject: [PATCH 2/5] grub-install: support for partitioned partx loop | devices. | | * grub-core/osdep/linux/getroot.c (grub_util_part_to_disk): Detect | /dev/loopX as being the parent of /dev/loopXpY. | |Conflicts: | ChangeLog |--- | grub-core/osdep/linux/getroot.c | 13 +++++++++++++ | 1 file changed, 13 insertions(+) | |diff --git a/grub-core/osdep/linux/getroot.c b/grub-core/osdep/linux/getroot.c |index 772de0a..19581d3 100644 |--- a/grub-core/osdep/linux/getroot.c |+++ b/grub-core/osdep/linux/getroot.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored patch program exited with status 1 =========================================================================== PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < '/usr/portage/sys-boot/grub/files/2.02_beta2/0002-grub-install-support-for-partitioned-partx-loop-devi.patch' =========================================================================== can't find file to patch at input line 20 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |From e407b6f1e9bf71877104eee2ed513b4065667f60 Mon Sep 17 00:00:00 2001 |From: Mike Gilbert <floppym@gentoo.org> |Date: Sun, 26 Jan 2014 02:56:04 +0100 |Subject: [PATCH 2/5] grub-install: support for partitioned partx loop | devices. | | * grub-core/osdep/linux/getroot.c (grub_util_part_to_disk): Detect | /dev/loopX as being the parent of /dev/loopXpY. | |Conflicts: | ChangeLog |--- | grub-core/osdep/linux/getroot.c | 13 +++++++++++++ | 1 file changed, 13 insertions(+) | |diff --git a/grub-core/osdep/linux/getroot.c b/grub-core/osdep/linux/getroot.c |index 772de0a..19581d3 100644 |--- a/grub-core/osdep/linux/getroot.c |+++ b/grub-core/osdep/linux/getroot.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored patch program exited with status 1 Do i need to mask the grub-2.02_beta2-r3? Thanks in advance :)
  8. In a fresh funtoo installation i have the problem just after compiling and installing a new kernel with its respective better-initrafms ready to work, the next logical step now is to install a boot loader, in this case i'm following the funtoo installation tutorial: emerge boot-update but fails in the part of emerging grub: Failed Patch: 0002-grub-install-support-for-partitioned-partx-loop-devi.patch ! Ii'm attaching the build log here : [32;01m * [39;49;00mPackage: sys-boot/grub-2.02_beta2-r3 [32;01m * [39;49;00mRepository: gentoo [32;01m * [39;49;00mMaintainer: funtoo [32;01m * [39;49;00mUSE: amd64 binfont elibc_glibc grub_platforms_efi-64 grub_platforms_pc kernel_linux nls userland_GNU [32;01m * [39;49;00mFEATURES: preserve-libs sandbox >>> Unpacking source... >>> Unpacking grub-2.02~beta2.tar.xz to /var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work >>> Unpacking unifont-7.0.01.pcf.gz to /var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work >>> Unpacking unifont-1.0.pf2.xz to /var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work >>> Source unpacked in /var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work >>> Preparing source in /var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work/grub-2.02~beta2 ... [32;01m*[0m Applying various patches (bugfixes/updates) ... [32;01m*[0m 0001-Makefile.util.def-Link-grub-ofpathname-with-zfs-libs.patch ... [A[123C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m 0002-grub-install-support-for-partitioned-partx-loop-devi.patch ... [31;01m*[0m Failed Patch: 0002-grub-install-support-for-partitioned-partx-loop-devi.patch ! [31;01m*[0m ( /usr/portage/sys-boot/grub/files/2.02_beta2/0002-grub-install-support-for-partitioned-partx-loop-devi.patch ) [31;01m*[0m [31;01m*[0m Include in your bugreport the contents of: [31;01m*[0m [31;01m*[0m /var/tmp/portage/sys-boot/grub-2.02_beta2-r3/temp/0002-grub-install-support-for-partitioned-partx-loop-devi.patch.out [31;01m*[0m ERROR: sys-boot/grub-2.02_beta2-r3 failed (prepare phase): [31;01m*[0m Failed Patch: 0002-grub-install-support-for-partitioned-partx-loop-devi.patch! [31;01m*[0m [31;01m*[0m Call stack: [31;01m*[0m ebuild.sh, line 93: Called src_prepare [31;01m*[0m environment, line 4635: Called epatch [31;01m*[0m environment, line 1951: Called die [31;01m*[0m The specific snippet of code: [31;01m*[0m die "Failed Patch: ${patchname}!"; [31;01m*[0m [31;01m*[0m If you need support, post the output of `emerge --info '=sys-boot/grub-2.02_beta2-r3'`, [31;01m*[0m the complete build log and the output of `emerge -pqv '=sys-boot/grub-2.02_beta2-r3'`. [31;01m*[0m The complete build log is located at '/var/tmp/portage/sys-boot/grub-2.02_beta2-r3/temp/build.log'. [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/sys-boot/grub-2.02_beta2-r3/temp/environment'. [31;01m*[0m Working directory: '/var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work/grub-2.02~beta2' [31;01m*[0m S: '/var/tmp/portage/sys-boot/grub-2.02_beta2-r3/work/grub-2.02~beta2' Do i need to mask the grub-2.02_beta2-r3? Thanks in advance :)
  9. I installed Funtoo yesterday, and while configuring grub, boot-update failed while running. The specific error message was: Copyright 2009-2012 Funtoo Technologies [use option "-l" for license info, "-h" for help] * Generating config for grub... * ERROR : /usr/sbin/grub-probe --device auto --target=abstraction * Did not complete successfully. After running grub-probe manually, it returned the error: grub-probe: info: cannot open `/boot/grub/device.map': No such file or directory. grub-probe: error: failed to get canonical path of udev. Has this problem been experienced before? Or is my system misconfigured?
×