Jump to content
funtoo forums

vchipk985

Members
  • Content Count

    16
  • Joined

  • Last visited

Everything posted by vchipk985

  1. From the error: install twm and xterm emerge -av twm xterm instead of revdep-rebuild use: emerge -av @preserved-rebuild and after a kernel update: emerge -av @module-rebuild
  2. see if you have: gfxcard-nvidia or gfxcard-nvidia-legacy(old cards) mix-ins enabled to set VIDEO_CARDS flags x11-drivers/nvidia-kernel-modules emerged. Rebuild if it was installed before kernel change.
  3. My guess: something wrong with .Xresources https://askubuntu.com/questions/283830/how-to-change-the-font-of-various-terminal-emulators see terminator section.
  4. 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.
  5. Usually is at /var/log/Xorg.0.log if DISPLAY=:0
  6. 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. 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.
  7. 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?
  8. 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
  9. Side note: You can use eix [app-portage/eix] too.
  10. 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
  11. 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)?
  12. Same here. It went well after that.
  13. 1- Your system seems updated; 2- https://bugs.funtoo.org/browse/FL-5329
  14. 1- make.conf 2- /etc/portage.use 3- profile In my opinion.
  15. Funtoo page about Layman: https://www.funtoo.org/Package:Layman
  16. on chrom_pqv: www-client/chromium-67.0.3377.1 on gentoo's bugzilla https://bugs.gentoo.org/651872 mask it and try the 66.0.3359.139 (stable)
  17. I followed the steps in https://forums.funtoo.org/topic/1608-12-funtoo-linux-release/ ego.conf
  18. Changing to kits 1.2 solved the issue for me (gcc 6.4.0 + clang-6.0.0-r1).
×
×
  • Create New...