Jump to content

Search the Community

Showing results for tags 'boot-update'.

  • 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

  • drobbins' Blog
  • It's a Bear's life
  • haxmeister's Blog
  • psychopatch's Blog
  • 666threesixes666's Blog
  • decision theory
  • Chris Kurlinski's Blog
  • Sandro's Blog
  • danielv's Blog
  • Not So Stupid Admin Tricks
  • maldoror's Blog
  • andreawilson's Blog
  • Simple Step-by-Step Server Setup
  • saraedward's Blog
  • eusanpe
  • Linux Container Club - LXD/LXC's Blog
  • Funtoo Perl Hackers's Perl on Funtoo

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


web


First Name


Last Name


Location


Interests

Found 9 results

  1. 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 no
  3. 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.
  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 f
  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
  6. 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 * [
  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 * [
  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? O
×
×
  • Create New...