Jump to content
funtoo forums

adcdam

Members
  • Content count

    113
  • Joined

  • Last visited

  • Days Won

    6

adcdam last won the day on August 13 2017

adcdam had the most liked content!

About adcdam

  • Rank
    Advanced Member

Personal

  • Location
    La Plata, Buenos Aires, Argentina

Recent Profile Visitors

168 profile views
  1. Thanks, i was able to install vulkan-loader-1.0.51.0, masking the latest version, thanks a lot.
  2. * ERROR: media-libs/vulkan-loader-1.0.54.0::xorg-kit failed (compile phase): * emake failed *
  3. gentoo sources kernel help and questions

    Got the gentoo-sources kernel working some weeks ago!!
  4. Hi i have a amd ryzen cpu, i built Gentoo sources 4.15.10 kernel but it doesnt boot, i just get a black screen https://wiki.gentoo.org/wiki/AMD_microcode what should i type in this part? External firmware blobs to build into the kernel binary if i select this it say enter a string value what should i type there? another question i have this: https://paste.pound-python.org/show/cZFm0t6HofywSleQ0xQc/ Device: 06:00.0 Class: SATA controller Vendor: ASMedia Technology Inc. Device: ASM1062 Serial ATA Controller SVendor: ASRock Incorporation SDevice: Motherboard Rev: 02 ProgIf: 01 Driver: ahci Module: ahci and Device: 12:00.2 Class: SATA controller Vendor: Advanced Micro Devices, Inc. [AMD] Device: FCH SATA Controller [AHCI mode] SVendor: Advanced Micro Devices, Inc. [AMD] SDevice: FCH SATA Controller [AHCI mode] Rev: 51 ProgIf: 01 Driver: ahci Module: ahci what should i select in device drivers serial Ata and parallel Ata drivers of the kernel menu? the Debian generic Debian kernel boot so is not a hardware problem or something
  5. Thanks a lot i installed again the root and copy back my old /etc and /var/lib/portage/world and /home, my system is working now but i can not make gentoo sources kernel to boot, im using a generic Debian kernel.
  6. I was using a Fx8320 until it stop working i bought a ryzen 1600, but i can not boot now or chroot, i was using amd64 piledriver subarch i get ilegal instruction when i chroot, i get the same using partedmagic usb , from my installed artix linux, and from systemrescuecd usb to chroot i did this mkdir /mnt/funtoo mount /dev/sda4 /mnt/funtoo mount /dev/sda2 /mnt/funtoo/boot mount /dev/sda5 /mnt/funtoo/home cd /mnt/funtoo mount -t proc none /mnt/funtoo/proc mount --rbind /dev /mnt/funtoo/dev mount --rbind /sys /mnt/funtoo/sys chroot /mnt/funtoo /bin/bash i always get illegal instruction, how can i chroot?
  7. Ravenports by Marino, Opinions?

    Before Ravenports Marino created a port building tool called synth programed in Ada Languaje for FreeBSD and DragonFly BSD, i tried it and it was much better than portmaster , it would be nice if Daniel, Oleg, Palica talk with Marino, perhaps new ideas will come, or something to improve portage (which is great) even more...
  8. http://ravenports.ironwolf.systems/
  9. i installed Runit i posted a video in the general discussion section. its really nice!!
  10. This is how it went, everything ok!! a very kind Russian guy with tons of knowledge and patience explain me how to install and use it. https://vimeo.com/254601362
  11. openrc-0.35.0_beta1 failed to compile

    Hi, thanks that was the problem portage owns distfile directory but not git3-src i changed that and i was able to install openrc 0.35 but when booting it say rc is deprecated, please use openrc instead and etc/init.d/udev use runscript, please convert to openrc udev
  12. openrc-0.35.0_beta1 failed to compile

    Hi, yes portage is able to write there, i updated today and there are lots of new version packages is in /var/cache /portage/distfiles so portage is able to write there, openrc was the only package that wasnt able to update. if i manually create OpenRC_openrc.git dir inside /var/cache/portage/distfiles/git3-src i get this >>> Emerging (1 of 1) sys-apps/openrc-0.35.0_beta1::core-kit >>> Unpacking source... * Fetching https://github.com/OpenRC/openrc.git ... git fetch https://github.com/OpenRC/openrc.git +HEAD:refs/git-r3/HEAD fatal: Not a git repository: '/var/cache/portage/distfiles/git3-src/OpenRC_openrc.git' * ERROR: sys-apps/openrc-0.35.0_beta1::core-kit failed (unpack phase): * Unable to fetch from any of EGIT_REPO_URI * * Call stack: * ebuild.sh, line 121: Called src_unpack * environment, line 3219: Called git-r3_src_unpack * environment, line 2165: Called git-r3_src_fetch * environment, line 2159: Called git-r3_fetch * environment, line 2081: Called die * The specific snippet of code: * [[ -n ${success} ]] || die "Unable to fetch from any of EGIT_REPO_URI"; * * If you need support, post the output of `emerge --info '=sys-apps/openrc-0.35.0_beta1::core-kit'`, * the complete build log and the output of `emerge -pqv '=sys-apps/openrc-0.35.0_beta1::core-kit'`. * The complete build log is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/environment'. * Working directory: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work' * S: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work/openrc-0.35.0_beta1' >>> Failed to emerge sys-apps/openrc-0.35.0_beta1, Log file: >>> '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/build.log' * Messages for package sys-apps/openrc-0.35.0_beta1: * ERROR: sys-apps/openrc-0.35.0_beta1::core-kit failed (unpack phase): * Unable to fetch from any of EGIT_REPO_URI * * Call stack: * ebuild.sh, line 121: Called src_unpack * environment, line 3219: Called git-r3_src_unpack * environment, line 2165: Called git-r3_src_fetch * environment, line 2159: Called git-r3_fetch * environment, line 2081: Called die * The specific snippet of code: * [[ -n ${success} ]] || die "Unable to fetch from any of EGIT_REPO_URI"; * * If you need support, post the output of `emerge --info '=sys-apps/openrc-0.35.0_beta1::core-kit'`, * the complete build log and the output of `emerge -pqv '=sys-apps/openrc-0.35.0_beta1::core-kit'`. * The complete build log is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/environment'. * Working directory: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work' * S: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work/openrc-0.35.0_beta1'
  13. Hi, i get this: how can i solve that? >>> Unpacking source... mkdir: cannot create directory ‘/var/cache/portage/distfiles/git3-src/OpenRC_openrc.git’: Permission denied * ERROR: sys-apps/openrc-0.35.0_beta1::core-kit failed (unpack phase): * (no error message) * * Call stack: * ebuild.sh, line 121: Called src_unpack * environment, line 3219: Called git-r3_src_unpack * environment, line 2165: Called git-r3_src_fetch * environment, line 2159: Called git-r3_fetch * environment, line 1956: Called _git-r3_set_gitdir 'https://github.com/OpenRC/openrc.git' * environment, line 476: Called die * The specific snippet of code: * mkdir "${GIT_DIR}" || die; * * If you need support, post the output of `emerge --info '=sys-apps/openrc-0.35.0_beta1::core-kit'`, * the complete build log and the output of `emerge -pqv '=sys-apps/openrc-0.35.0_beta1::core-kit'`. * The complete build log is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/environment'. * Working directory: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work' * S: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work/openrc-0.35.0_beta1' >>> Failed to emerge sys-apps/openrc-0.35.0_beta1, Log file: >>> '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/build.log' * Messages for package sys-apps/openrc-0.35.0_beta1: * ERROR: sys-apps/openrc-0.35.0_beta1::core-kit failed (unpack phase): * (no error message) * * Call stack: * ebuild.sh, line 121: Called src_unpack * environment, line 3219: Called git-r3_src_unpack * environment, line 2165: Called git-r3_src_fetch * environment, line 2159: Called git-r3_fetch * environment, line 1956: Called _git-r3_set_gitdir 'https://github.com/OpenRC/openrc.git' * environment, line 476: Called die * The specific snippet of code: * mkdir "${GIT_DIR}" || die; * * If you need support, post the output of `emerge --info '=sys-apps/openrc-0.35.0_beta1::core-kit'`, * the complete build log and the output of `emerge -pqv '=sys-apps/openrc-0.35.0_beta1::core-kit'`. * The complete build log is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/temp/environment'. * Working directory: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work' * S: '/var/tmp/portage/sys-apps/openrc-0.35.0_beta1/work/openrc-0.35.0_beta1'
  14. i really like to try Runit as init and supervisor, anyone using Runit with Funtoo? i know that i can use Runit with Openrc but i would like to use just Runit. a tutorial on how to migrate init would be nice!
  15. qbittorrent failed to compile

    i rebuild libtorrent-rastebar and then i was able to compile qbittorrent witout problems, thanks!!
×