Jump to content
funtoo forums

bcowan

Members
  • Content Count

    15
  • Joined

  • Last visited

  • Days Won

    2

bcowan last won the day on February 3 2018

bcowan had the most liked content!

About bcowan

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. man boot.conf has most all the settings you are looking for. So edit your /etc/boot.conf and place them in there and run ego boot update
  2. rfkill is provided by util-linux in recent versions which is part of @system. There may be an oversight somewhere that lost the dependency on the stand-alone version that is needed if you have sys-apps/util-linux-2.29.2-r1. just my thoughts :)
  3. bcowan

    lvm trips up grub

    Now that you have concisely written down the steps you were doing and what you expected vs. what was happening, I do not see this as a bug but expected behavior. Grub-install indeed needs a mounted /boot or passed another writeable directory with the —boot-directory argument. This is done one single time only during your initial install. ( it writes a few files, notably grub.env and device.map ) You should not have to run grub-install again unless you corrupted something or another OS etc overwrites it. You then can run boot-update. It seems you are doing these steps in the wrong order. The install page documents these steps in the correct order. Boot should not need to be mounted for a working startup. The only thing that should need ran again is boot-update when you change kernels etc, never a grub-install. weird that the forum top posted my reply a couple hours ago????
  4. bcowan

    lvm trips up grub

    Now that you have concisely written down the steps you were doing and what you expected vs. what was happening, I do not see this as a bug but expected behavior. Grub-install indeed needs a mounted /boot or passed another writeable directory with the —boot-directory argument. This is done one single time only during your initial install. ( it writes a few files, notably grub.env and device.map ) You should not have to run grub-install again unless you corrupted something or another OS etc overwrites it. You then can run boot-update. It seems you are doing these steps in the wrong order. The install page documents these steps in the correct order. Boot should not need to be mounted for a working startup. The only thing that should need ran again is boot-update when you change kernels etc, never a grub-install.
  5. I would use —usepkgonly or -K instead of —usepkg or -k to emerge libtool and binutils from packages you built. Then try binutils-config -l to list and set it again with binutils-config 2 or whatever. I’m still thinking this is a binutils problem breaking compiler/toolchain links.
  6. bcowan

    lvm trips up grub

    It should print the name of the kernel it finds after label your kernel- is blank
  7. bcowan

    lvm trips up grub

    Your last post shows the output of boot-update not finding a kernel and the second output shows it automounting sda1 as your /boot when not mounted. Also its grub.cfg not grub.conf if that is not just a typo you wrote in the post.
  8. bcowan

    Can't Compile vanilla-sources Kernel

    dang, your binutils-config and gcc-config "look" correct. "looks" can be deceiving. Have you changed CFLAGS or anything? maybe have a bad flag. Might want to post a gcc -v and maybe emerge --info so we have allot of the info bases covered :)
  9. bcowan

    lvm trips up grub

    This post still confuses me. /boot not being mounted has nothing to do with grub. Grub uses its own abstraction layer to read grub.cfg which points it to a initrd/kernel. This "abstraction layer" never "mounts" anything, grub has no knowledge of mounts. So only your grub.cfg could be wrong, or not written because you didn't manually mount /boot, but pretty sure boot-update automounts /boot so grub-mkconfig can write grub.cfg unless specified to not automount.
  10. bcowan

    Can't Compile vanilla-sources Kernel

    If your system has been switched over to kits/meta-repo ( which should be the case ) /usr/portage has been deprecated in favor of /var/git/meta-repo and /var/cache/portage/distfiles instead of /usr/portage/distfiles. looking at your last post, does gcc-config --list-profiles output anything? should spit out something like [1] x86_64-pc-linux-gnu-5.4.0
  11. bcowan

    Can't Compile vanilla-sources Kernel

    On a side note : there is a Funtoo system resurrection guide @ https://www.funtoo.org/System_resurrection that details the steps @palica just correctly described, but it needs some "modernization/lovin" to reflect the /usr/portage move to /var/cache and /var/git plus some other minor technical details.
  12. bcowan

    Can't Compile vanilla-sources Kernel

    Sorry, I was offering advice based on your initial problem with make oldconfig for vanilla sources. Which points to broken binutils. From your original question you were rebuilding @world so it appeared that you were able to emerge/build packages. From that point on the thread has evolved into a hodgepodge of many broken things that may or may not have happened after the first question. At this point though it seems now your compiler links are broken.
  13. bcowan

    Can't Compile vanilla-sources Kernel

    I would try rebuilding binutils first since it provides the assembler. But if that fails you can rebuild a sane toolchain. emerge in this order gcc binutils glibc eselect gcc list and eselect gcc set your compiler and source /etc/profile
  14. bcowan

    apr-util-1.6.0.tar.bz2 ERROR 404: Not Found

    bug was filed a few days ago and should be fixed now. bug FL-4743
  15. bcowan

    TTY (console) colour changed after OpenRC start

    I thought 4.14.12 was latest stable marked kernel with all the meltdown, spectre patches and that the latest linux-firmware has updated drivers for it. Probably want the latest microcode too. could be some PTI thing?? IDK maybe worth a shot making sure you have latest kernel? just throwing out ideas.
×