Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

vchipk985

Members
 View Profile  See their activity

  • Posts

    22

  • Joined

  • Last visited

 Content Type 

Posts posted by vchipk985

  3. Renamed to Issues with Steam, Xorg, PulseAudio, and Docker

    in General Help

    Posted

    Cannot emerge the new steam-nvidia-launcher.

    output of emerge -av steam-nvidia-launcher: 

    These are the packages that would be merged, in order:

Calculating dependencies... done!

emerge: there are no ebuilds to satisfy "app-emulation/nvidia-container".
(dependency required by "games-platforms/steam-nvidia-launcher-1.4::games-kit" [ebuild])
(dependency required by "steam-nvidia-launcher" [argument])

    Cannot find "app-emulation/nvidia-container" when i search for nvidia-container (emerge -s nvidia-container) 

    [ Results for search key : nvidia-container ]
Searching...

*  app-emulation/libnvidia-container-bin
      Latest version available: 1.0.2-r1
      Latest version installed: 1.0.2-r1
      Size of files: 298 KiB
      Homepage:      https://github.com/NVIDIA/libnvidia-container
      Description:   NVIDIA container runtime library and nvidia-container-cli tool
      License:       NVIDIA

*  app-emulation/nvidia-container-runtime
      Latest version available: 1.0.2
      Latest version installed: 1.0.2
      Size of files: 1,681 KiB
      Homepage:      https://github.com/NVIDIA
      Description:   nvidia-container-runtime (clone of runc with nvidia hooks) and the hook itself.
      License:       Apache-2.0

*  virtual/libnvidia-container
      Latest version available: 1.0.2
      Latest version installed: 1.0.2
      Size of files: 0 KiB
      Homepage:      
      Description:   A virtual for libnvidia-container(-bin)
      License:       

[ Applications found : 3 ]

     

  4. PYTHON_TARGETS troubles

    in General Help

    Posted

    On 12/3/2019 at 11:52 AM, escy said:

    Where does my system get those PYTHON_TARGETS settings from? I thought they should be defined via eselect python?

    They came from profiles, make.conf or package.use.

    On 12/3/2019 at 11:52 AM, escy said:

    emerge -avuDN world gives: 

    
!!! The ebuild selected to satisfy "dev-vcs/git" has unmet requirements.
- dev-vcs/git-2.22.0::core-kit USE="blksha1 curl gpg iconv nls pcre pcre-jit perl python threads webdav -cgi -cvs -doc -emacs -gnome-keyring -highlight -libressl -mediawiki -mediawiki-experimental (-ppcsha1) -subversion -test -tk -xinetd" 
PYTHON_SINGLE_TARGET="python3_7 -python2_7 -python3_5 -python3_6" PYTHON_TARGETS="python3_6 -python2_7 -python3_5 -python3_7"

  The following REQUIRED_USE flag constraints are unsatisfied:
    python? ( python_single_target_python3_7? ( python_targets_python3_7 ) )

     Strange thing: PYTHON_TARGETS="python3_6" but PYTHON_SINGLE_TARGET="python3_7" 

  8. ERROR nvidia-legacy-drivers for my geforce gtx570

    in General Help

    Posted

    On 10/3/2019 at 5:38 AM, morphmex said:

    I rebooted and I have this error

    https://ibb.co/wSHwBbp

    From the error: install twm and xterm

    emerge -av twm xterm

     

    1 hour ago, morphmex said:

     

      
    
Using revdep-rebuild repeatedly I get this message. I can't get the consistent system.

    https://ibb.co/wgJFsRQ

    instead of revdep-rebuild use: emerge -av @preserved-rebuild

    and after a kernel update: emerge -av @module-rebuild

  11. Screen Freezing

    in Desktop Help

    Posted

    Line 57:

    [ 46346.003] (II) LoadModule: "intel"
    [ 46346.003] (WW) Warning, couldn't open module intel
    [ 46346.003] (EE) Failed to load module "intel" (module does not exist, 0)
    [ 46346.003] (II) LoadModule: "modesetting"
    [ 46346.003] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
    [ 46346.004] (II) Module modesetting: vendor="X.Org Foundation"
    [ 46346.004]     compiled for 1.20.5, module version = 1.20.5
    [ 46346.004]     Module class: X.Org Video Driver
    [ 46346.004]     ABI class: X.Org Video Driver, version 24.0
    [ 46346.004] (II) LoadModule: "fbdev"
    [ 46346.004] (WW) Warning, couldn't open module fbdev
    [ 46346.004] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 46346.004] (II) LoadModule: "vesa"
    [ 46346.004] (WW) Warning, couldn't open module vesa
    [ 46346.004] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 46346.004] (II) modesetting: Driver for Modesetting Kernel Drivers: kms

    Its loading on kms modeset instead on intel module (module does not exist on your output)

    See if fbdev, intel, i915 and i965 are enabled on VIDEO_CARDS with emerge --info. Also, see if they are enabled on xorg-drivers: emerge -pv xorg-drivers.

    The log didn't show the freeze, but it can be related to the missing intel module.

  13. Screen Freezing

    in Desktop Help

    Posted

    3 hours ago, bitterbitbasher said:

    About installing debian-sources, I installed it but it did not solve the freeze problem.

    If you did everything right, it is not kernel related. As I said before: upload the Xorg full log. Without it we can only guess what is happening.

    3 hours ago, bitterbitbasher said:

    Picking OpenAL Soft. If your desired device was missing, make sure you have the appropriate 32-bit libraries installed.

    Since 1.3 update, funtoo doesn't use multilib. And the error is telling you to use 32-bits libraries.

    But you were using funtoo 1.3 before and it was working, which is strange.

     

  14. Screen Freezing

    in Desktop Help

    Posted

    You can try 2 things:

    Install a non gtk browser, ex: falkon (qt), maybe its gtk related.

    Or

    Install debian-sources, probably you have installed debian-sources-lts. We can see if its kernel related.

    Can you upload the X log and show the errors?

  15. emerge x11-drivers/nvidia-drivers-430.26-r2 fails

    in Portage Help

    Posted

    Hello,

    After sometime emerging 

    emerge -auDN @world xorg-x11 --jobs

    on container (using funtoo 1.4) x11-drivers/nvidia-drivers-430.26-r2 fails with:

     * ERROR: x11-drivers/nvidia-drivers-430.26-r2::core-gl-kit failed (install phase):
     *   Can not read .manifest!
     *
     * Call stack:
     *     ebuild.sh, line   93:  Called src_install
     *   environment, line 5276:  Called nv_parse_manifest
     *   environment, line 4438:  Called die
     * The specific snippet of code:
     *       [ -r .manifest ] || die "Can not read .manifest!";

    What should I do to proceed? Is this happening on container only?

    Thanks in advance

  17. [solved] lxd/lxc no .config in the kernel source directory

    in Portage Help

    Posted

    2 hours ago, drobbins said:

    LXD GPU-accelerated containers requires Funtoo Linux 1.4. It looks like you may be using Funtoo Linux 1.3?

    The nvidia-drivers in 1.4 has been significantly modified to work properly inside containers and not require a kernel. The 1.3 one hasn't.

    Hello Daniel,

    I'm using Funtoo 1.4 on host for 2 weeks by now, thanks for the release.

    About the problem: After a emerge --sync today on gentoo guest the error is gone (at least for now, still in emerge process),

    Thanks for the help

  18. [solved] lxd/lxc no .config in the kernel source directory

    in Portage Help

    Posted

    Hello,

    I'm trying to set up a LXD GPU-accelerated container.

    First time doing so i used https://www.funtoo.org/LXD/GPU_Acceleration

    but on emerge -auDN @world xorg-x11 --jobs step  x11-drivers/nvidia-drivers fails with:

     * Could not find a usable .config in the kernel source directory.                                                                        
     * Please ensure that /usr/src/linux points to a configured set of Linux sources.
     * If you are using KBUILD_OUTPUT, please set the environment var so that
     * it points to the necessary object directory so that it might find .config.         
     * ERROR: x11-drivers/nvidia-drivers-430.40::gentoo failed (pretend phase):           
     *   Kernel not configured; no .config found in /usr/src/linux

    Should I compile a kernel for the container? (manual or genkernel)

    Or should i use the host .config (debian-sources)?

×
×
  • Create New...