Jump to content

bcowan

Members
  • Content Count

    68
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by bcowan

  1. Yes, sys-apps/rng-tools or sys-apps/haveged are almost necessities anymore for enough entropy on any system. Without, that delay will result, I'm surprised more users don't complain or report about it.
  2. Please check if /etc/boot.conf got updated and nomodeset added. If so, this needs removed and ego boot updated re-ran, then a system reboot. Seems to be the Bug du jour.
  3. most likely /etc/boot.conf got updated and nomodeset got added please remove the nomodeset and run ego boot update then reboot your box. hopefully all will be well then 🙂
  4. also by default nomodeset is in /etc/boot.conf, please try removing that and re-running ego boot update, reboot and see if that helps.
  5. if he used the first command he forgot the tilda before his username, could be the issue. shrug
  6. does normal https work? git clone https://code.funtoo.org/bitbucket/scm/~mauricev/skeleton-overlay.git
  7. If you're in a jam and really have to emerge a package in this situation you can run ego sync --config-only so profiles and everything is in alignment to allow emerges, but best practice is please wait and allow time for tree to be fixed. USE AT YOUR OWN RISK
  8. need to edit /etc/inittab and make sure the lines # TERMINALS #x1:12345:respawn:/sbin/agetty 38400 console linux #c1:12345:respawn:/sbin/agetty 38400 tty1 linux #c2:2345:respawn:/sbin/agetty 38400 tty2 linux #c3:2345:respawn:/sbin/agetty 38400 tty3 linux #c4:2345:respawn:/sbin/agetty 38400 tty4 linux #c5:2345:respawn:/sbin/agetty 38400 tty5 linux #c6:2345:respawn:/sbin/agetty 38400 tty6 linux are commented/REM'd like the above
  9. this should be fixed with latest ego sync, no need to modify anything
  10. Please refer to man boot.conf add an entry to /etc/boot.conf such as "Windows 7" { type win7 params root=/dev/sda3 params += chainloader=+1 }
  11. PR was merged last night, so this should be fixed with an ego sync hopefully ?
  12. I submitted a pull request to fix this, the patch is missing for the ebuild. Drobbins will hopefully fix when he gets some time :)
  13. I only have 3g ram in this old macbook and rust builds fine. You can try just editing the ebuild for the ram check and change it to 2g. This may fail, I 'm not guaranteeing it will build on every system. If it fails there is always rust-bin to fall back on.
  14. That page needs re-worked and is pretty dated. Portage snapshots are no longer valid afaik, everything is taken care of with git and ego sync. Here is a more in depth wiki page, but its a little involved, allot can be ignored. A simplified version of it is needed. https://www.funtoo.org/Funtoo_Linux_Installation_on_RPI
  15. 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
  16. 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 :)
  17. 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. T
  18. 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. T
  19. 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.
  20. It should print the name of the kernel it finds after label your kernel- is blank
  21. 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.
  22. 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 :)
  23. 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.
  24. 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
×
×
  • Create New...