Jump to content
funtoo forums

All Activity

This stream auto-updates     

  1. Today
  2. OK, interesting, this means that as you found, the defaults in login.defs are not wonderful. From the useradd man page (see bolded part): SUB_GID_MIN (number), SUB_GID_MAX (number), SUB_GID_COUNT (number) If /etc/subuid exists, the commands useradd and newusers (unless the user already have subordinate group IDs) allocate SUB_GID_COUNT unused group IDs from the range SUB_GID_MIN to SUB_GID_MAX for each new user. So this means, when you created /etc/subuid, you magically enabled useradd to try to start assigning subuid ranges to new users. And by default, its subuid range conflicts with the one in our LXD docs -- LXD eats up this range. There is no point for useradd to be assigning subuids and subgids to new users it creates by default. It's a cool feature if you need it, I guess, but it should be off by default. So /etc/login.defs should have SUB_GID_COUNT and SUB_UID_COUNT set to 0 by default. Also see bcowan's bug report and my response here: https://bugs.funtoo.org/browse/FL-6773
  3. Yesterday
  4. mrl5

    funtoo and yubikey

    aaaand one more thing: if someone wants to work with yubikey and google chrome/chromium inside SELinux OS then this is useful: # setsebool -P chromium_rw_usb_dev on # setsebool -P chromium_read_system_info on
  5. Last week
  6. Glad that you've got things working again!
  7. Hi @jhan, @nrc, With your help, I manage to fix the issues. What I was missing was to remerge the linux-firmware after doing correct configuration of the mesa and xorg-drivers. Thanks a lot!
  8. Usually, that appears when defining an overlay with a different name than the name contained in the overlay's metadata. That's a little disturbing that somehow core-kit is involved...
  9. As plasma also has the wayland USE flag, I said it might be good to try to build the system without this USE flag first. To not have a "mixed state", where one part supports wayland and one not. As far as I know, wayland is not yet ready for "general use", there are too many things that don't work yet or still need the use of XWayland, depending on the desktop environment you want to use. Gnome seems to be working fine, KDE plasma e.g still has some problems (https://community.kde.org/Plasma/Wayland_Showstoppers) and no idea about the others. At the moment I wouldn't use it as my normal desktop, unless I have tested all applications under it first, probably on another computer. And if you say that Xorg+KDE seems to get stuck, how far does it get? How are you starting it? Any messages in the Xorg protocol or dmesg?
  10. @nrc, well not exactly, because it did not fail to start when using the radeon driver, only when I tried with the r600, then the fail message was "driver r600 not found".
  11. Hrm. Is there an error in the Xorg log file when it fails to start?
  12. Hi @nrc, according to the xorg log file that I've post previously I should set r600, which I tried and it didn't work saying the driver was not found. I changed to "fbdev" and it got even worse (I know this was going to happen, but I had to try) In fact I did generate the xorg.conf using "X -configure" after latest changes. @jhan, I don't mind to use "wayland" actually, because I don't even understand it yet, I've always used Xorg and KDE. But what happens is that after I remove the VIDEO_CARDS from the make.conf file and reemerged xorg-drivers and mesa I can't actually use Xorg + KDE (it try to load but it doesn't load, it seems stuck), I can only load my KDE when I change it to "wayland". I will read your link. Thanks!
  13. The radeon driver is correct. The name of the driver is just radeon but it supports many different versions of similar cards: https://www.x.org/releases/current/doc/man/man4/radeon.4.xhtml
  14. I'm running nvidia so I'm not sure. In my install the driver entry in the xorg.conf file matches the xorg log file entry for DRI driver. If that file was generated before your latest changes you might try regenerating it with "Xorg -configure"
  15. If you can only start wayland but don't want or need it. You could etiher remove the wayland mix-in (which you inherited) or use the '-wayland' USE flag. That should at least give you you the possibility to to start plasma normally.
  16. Thank you; for pointing me in the right direction -and- for a quick reply! After I learn a bit more about this, I'll post my results back to this post. Appreciate the help! update: I was able to add the gentoo overlay and install the acct-group. That did allow me to install flatpak. But now, with every emerge command I get aragon ~ # emerge -avl --pretend gnome-software !!! Repository name or alias 'gentoo', defined for repository 'core-kit', overrides existing alias or repository. and I wonder if I messed anything up ..
  17. This is a relatively new Gentoo convention. Gentoo is organizing dedicated users and groups into virtual packages, and to do this, they have created two new categories: acct-user and acct-group. Packages under these categories are virtual packages that create new Linux users and groups. The only thing that package does is make sure that the flatpak Linux group exists with a certain hard-coded gid. You may need to create a local overlay and pull that virtual package from Gentoo. I ran into this new convention when pulling the latest Emacs from Gentoo. I eventually pulled in the acct-group package that was needed and declared the two new categories: https://code.funtoo.org/bitbucket/users/klipkyle/repos/klipkyle-overlay/browse/profiles/categories Based on the error message, I think you can alternatively declare "custom" categories in /etc/portage/categories. More info about the specific situation I ran into: How to create a custom overlay: https://www.funtoo.org/Creating_Your_Own_Overlay I hope this helps, --Kyle
  18. Hi @nrc, I didn't have the xorg.conf file, in the directory /etc/X11/xorg.conf.d/ I had only 20opengl.conf and radeon.conf I did generate the xorg.conf by running X -configure, but I have had the same result with my graphic environment, see my conf files: /etc/X11/xorg.conf.d # cat 20opengl.conf Section "Files" EndSection /etc/X11/xorg.conf.d # cat radeon.conf Section "Device" Identifier "Radeon" Driver "radeon" EndSection /etc/X11/xorg.conf.d # cat xorg.conf Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/lib64/xorg/modules" FontPath "/usr/share/fonts/misc/" FontPath "/usr/share/fonts/TTF/" FontPath "/usr/share/fonts/OTF/" FontPath "/usr/share/fonts/Type1/" FontPath "/usr/share/fonts/100dpi/" FontPath "/usr/share/fonts/75dpi/" EndSection Section "Module" Load "glx" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: <i>: integer, <f>: float, <bool>: "True"/"False", ### <string>: "String", <freq>: "<f> Hz/kHz/MHz", ### <percent>: "<f>%" ### [arg]: arg optional #Option "Accel" # [<bool>] #Option "SWcursor" # [<bool>] #Option "EnablePageFlip" # [<bool>] #Option "ColorTiling" # [<bool>] #Option "ColorTiling2D" # [<bool>] #Option "RenderAccel" # [<bool>] #Option "SubPixelOrder" # [<str>] #Option "AccelMethod" # <str> #Option "ShadowPrimary" # [<bool>] #Option "EXAVSync" # [<bool>] #Option "EXAPixmaps" # [<bool>] #Option "ZaphodHeads" # <str> #Option "SwapbuffersWait" # [<bool>] #Option "DeleteUnusedDP12Displays" # [<bool>] #Option "DRI3" # [<bool>] #Option "DRI" # <i> #Option "TearFree" # [<bool>] Identifier "Card0" Driver "radeon" BusID "PCI:2:0:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection According to the xorg.conf file it is using the driver radeon, should it be r600? One thing after I generated the xorg.conf I did restart my machine, just make sure that I'm using the correct file.
  19. I'm trying to install flatpak and I've never used an overlay before. From all that I've searched, I think I'm 'almost there' and it seems the only thing stopping the emerge is Calculating dependencies | !!! 'acct-group/flatpak' has a category that is not listed in /etc/portage/categories ... done! I don't have a file or a directory in /etc/portage called categories aragon ~ # emerge -avl dev-util/flatpak-builder sys-apps/flatpak These are the packages that would be merged, in order: Calculating dependencies | !!! 'acct-group/flatpak' has a category that is not listed in /etc/portage/categories ... done! [ebuild N ] sys-fs/libostree-2019.4::flatpak-overlay USE="curl gpg http2 introspection libmount soup -avahi -doc -gnutls -man -openssl -systemd" 1,926 KiB [ebuild N ] sys-apps/xdg-desktop-portal-1.4.2-r1::flatpak-overlay USE="-doc -geolocation -screencast" 412 KiB [ebuild N ] sys-apps/xdg-desktop-portal-gtk-1.4.0::flatpak-overlay USE="X -wayland" 344 KiB [ebuild N ] sys-apps/flatpak-1.2.4::flatpak-overlay USE="gnome gtk introspection policykit -doc -seccomp" 1,140 KiB [ebuild N ] dev-util/flatpak-builder-1.0.9::flatpak-overlay USE="yaml -doc" 448 KiB Total: 5 packages (5 new), Size of downloads: 4,268 KiB !!! The following update has been skipped due to unsatisfied dependencies: sys-apps/flatpak:0 selected: (sys-apps/flatpak-1.2.4:0/0::flatpak-overlay, ebuild scheduled for merge) skipped: (sys-apps/flatpak-1.4.3:0/0::flatpak-overlay, ebuild scheduled for merge) (see unsatisfied dependency below) emerge: there are no ebuilds to satisfy "acct-group/flatpak". (dependency required by "sys-apps/flatpak-1.4.3::flatpak-overlay" [ebuild]) Would you like to merge these packages? [Yes/No] no I know I'm missing something .. Thank you!
  20. Check your xorg.conf file to make sure that your video driver is correct. Should be /etc/X11/xorg.conf.d/xorg.conf
  21. Hi @jhan, I did something right and something wrong. I manage to remove the VIDEO_CARDS from the make.conf and rebuild the mesa and xorg-drivers. Now it added in the VIDEO_CARDS the fbdev (not sure if it should happen), see: # emerge -pv mesa xorg-drivers These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] x11-base/xorg-drivers-1.20::xorg-kit INPUT_DEVICES="evdev keyboard mouse synaptics -elographics -joystick -libinput -tslib -vmmouse -void -wacom" VIDEO_CARDS="fbdev radeon -amdgpu -ast -dummy (-freedreno) -gallium-radeonsi -gallium-tegra (-geode) -glint -i915 -i965 -intel -mga -nouveau -nv -nvidia (-omap) -qxl -r128 -radeonsi -siliconmotion (-tdfx) (-tegra) (-vc4) -vesa -via -virtualbox -vmware (-voodoo)" 0 KiB [ebuild R ] media-libs/mesa-19.1.4::core-gl-kit USE="(X) (drm) (egl) (gbm) (gles1) (gles2) (glvnd) (glx) (llvm) (ocl-icd) (opengl) (shader-cache) (surfaceless) wayland -alternate-path -android -d3d9 -debug -extra-hud -haiku -opencl -pax_kernel -pic (-selinux) -sensors -test -unwind -valgrind" CPU_FLAGS_X86="-avx -avx2 -avx512bw -avx512er" VIDEO_CARDS="gallium-r600 (osmesa) radeon (swrast) vaapi vdpau xa xvmc -amdgpu -dri3 -gallium-freedreno -gallium-i915 -gallium-imx -gallium-nouveau -gallium-osmesa -gallium-pl111 -gallium-r300 -gallium-radeonsi -gallium-swr -gallium-swrast -gallium-tegra -gallium-v3d -gallium-vc4 -gallium-virgl -gallium-vivante -gallium-vmware -i915 -i965 -intel -nouveau -openmax -r100 -r200 -virgl -vulkan-amdgpu -vulkan-intel" 0 KiB Total: 2 packages (2 reinstalls), Size of downloads: 0 KiB This is after remerged. I also merged one more eselect module, which is: " xvmc Manage the XvMC implementation used by your system" And I set it with xorg-x11, because I have only this option: # eselect xvmc list Available XvMC implementations (* is current): [1] xorg-x11 * The OpenGL didn't changed: # eselect opengl list Available OpenGL implementations: [1] xorg-x11 * The X.org log: # cat /var/log/Xorg.0.log |grep DRI [ 1759.306] (II) RADEON(0): [DRI2] Setup complete [ 1759.306] (II) RADEON(0): [DRI2] DRI driver: r600 [ 1759.306] (II) RADEON(0): [DRI2] VDPAU driver: r600 [ 1759.306] (==) RADEON(0): DRI3 enabled [ 1759.308] (II) Initializing extension DRI3 [ 1759.312] (II) GLX: Initialized DRI2 GL provider for screen 0 [ 1759.312] (II) Initializing extension XFree86-DRI [ 1759.312] (II) Initializing extension DRI2 But after I did this, I can't open the KDE using Plasma, only using Plasma (Wayland). And in this Plasma (Wayland) I can't open glxgears nor play videos for instance. What am I missing here? Thanks!
  22. Yeah I've read about this a week or two ago. I feel very safe at /home, thankyouverymuch.
  23. That might be a good idea, as the VIDEO_CARDS setting in make.conf seems to have priority over the mix-ins setting. I tested that locally by adding the gfxcard-radeon mix-in but the USE flags for xorg-drivers and mesa only changed after I removed the VIDEO_CARDS line from make.conf. A 'emerge -pv mesa xorg-drivers' would probably enough to see if a rebuild would change anything.
  24. Hi @nrc, thanks for the reply. Yes, I do have the VIDEO_CARDS="radeon" in my make.conf. I'll remove it and build xorg and mesa again.
  25. He means to make sure that you don't have anything in make.conf or package.* that would be contradicting the video card settings being established by the mix-in. Make sure that you're not setting VIDEO_CARDS in make.conf, for example. Also try "equery u xorg-drivers" to verify that your USE settings are correct.
  26. Hi @jhan, what do you mean by "don't accidentally contain anything that would disable it?" I'm sure that I haven't added anything manually in this directory. Once I'm home I'll check the files and post here, but not sure how can be disabling. Thanks!
  27. If you have set gfxcard-radeon as a mix-in, gallium-r600 is already set as VIDEO_CARDS: farout $ more /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/mix-ins/gfxcard-radeon/make.defaults # reference: # https://www.x.org/wiki/RadeonFeature/ # https://wiki.gentoo.org/wiki/Radeon # profile covers: r600 <= chipset <= N.Islands # GFX Core 4 and 5 VIDEO_CARDS="radeon r600 gallium-r600" USE="glamor vdpau vaapi" But so is radeon, which makes your mesa warning above look a bit suspicious but I see no profile setting that would disable it. Are you sure your local /etc/portage/ files don't accidentally contain anything that would disable it? And my guess for the r600g would be that that is the gallium-r600.
  28. Hi @jhan, I do believe it is not the correct provider, but I don't have other (not sure how to install) Regarding the info: # LIBGL_DEBUG=verbose glxgears libGL: Can't open configuration file /etc/drirc: No such file or directory. libGL: Can't open configuration file /root/.drirc: No such file or directory. MESA-LOADER: failed to open r600 (search paths /usr/lib64/dri) libGL error: failed to load driver: r600 libGL: Can't open configuration file /etc/drirc: No such file or directory. libGL: Can't open configuration file /root/.drirc: No such file or directory. 3931 frames in 5.0 seconds = 786.019 FPS # glxinfo |grep DRI MESA-LOADER: failed to open r600 (search paths /usr/lib64/dri) libGL error: failed to load driver: r600 # cat /var/log/Xorg.0.log|grep DRI [ 25.994] (II) RADEON(0): [DRI2] Setup complete [ 25.994] (II) RADEON(0): [DRI2] DRI driver: r600 [ 25.994] (II) RADEON(0): [DRI2] VDPAU driver: r600 [ 25.995] (==) RADEON(0): DRI3 disabled [ 25.998] (II) Initializing extension DRI3 [ 26.000] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 26.000] (II) Initializing extension XFree86-DRI [ 26.000] (II) Initializing extension DRI2 When I had done this before, I thought the problem is because the mesa is not having the VIDEO_CARDS flag with the driver "r600" instead it is having "radeon". But in the USE flags it has only the "gallium-r600" and it sees to be incompatible to be merged together, see: # VIDEO_CARDS="gallium-r600" emerge -avt mesa These are the packages that would be merged, in reverse order: Calculating dependencies / !!! Problem resolving dependencies for media-libs/mesa ... done! !!! The ebuild selected to satisfy "mesa" has unmet requirements. - media-libs/mesa-19.1.4::core-gl-kit USE="(X) (drm) (egl) (gbm) (gles1) (gles2) (glvnd) (glx) (llvm) (ocl-icd) (opengl) (shader-cache) (surfaceless) wayland -alternate-path -android -d3d9 -debug -extra-hud -haiku -opencl -pax_kernel -pic (-selinux) -sensors -test -unwind -valgrind" CPU_FLAGS_X86="-avx -avx2 -avx512bw -avx512er" VIDEO_CARDS="gallium-r600 (osmesa) (swrast) -amdgpu -dri3 -gallium-freedreno -gallium-i915 -gallium-imx -gallium-nouveau -gallium-osmesa -gallium-pl111 -gallium-r300 -gallium-radeonsi -gallium-swr -gallium-swrast -gallium-tegra -gallium-v3d -gallium-vc4 -gallium-virgl -gallium-vivante -gallium-vmware -i915 -i965 -intel -nouveau -openmax -r100 -r200 -radeon -vaapi -vdpau -virgl -vulkan-amdgpu -vulkan-intel -xa -xvmc" The following REQUIRED_USE flag constraints are unsatisfied: video_cards_gallium-r600? ( video_cards_radeon ) The above constraints are a subset of the following complete expression: d3d9? ( video_cards_gallium-swrast ) opencl? ( llvm any-of ( video_cards_gallium-pl111 video_cards_gallium-radeonsi video_cards_gallium-r300 video_cards_gallium-r600 video_cards_gallium-nouveau video_cards_gallium-freedreno video_cards_gallium-vc4 video_cards_gallium-v3d video_cards_gallium-vivante video_cards_gallium-imx video_cards_gallium-tegra video_cards_gallium-i915 video_cards_gallium-vmware video_cards_gallium-virgl video_cards_gallium-swr ) ) at-most-one-of ( video_cards_i915 video_cards_gallium-i915 ) at-most-one-of ( video_cards_swrast video_cards_gallium-swrast ) at-most-one-of ( video_cards_osmesa video_cards_gallium-osmesa ) video_cards_vulkan-intel? ( video_cards_intel ) video_cards_i915? ( video_cards_intel ) video_cards_i965? ( video_cards_intel ) video_cards_gallium-i915? ( video_cards_intel ) video_cards_r100? ( video_cards_radeon ) video_cards_r200? ( video_cards_radeon ) video_cards_gallium-r300? ( video_cards_radeon ) video_cards_gallium-r600? ( video_cards_radeon ) video_cards_amdgpu? ( video_cards_radeon ) video_cards_vulkan-amdgpu? ( video_cards_radeon ) wayland? ( egl gbm ) video_cards_gallium-swrast? ( llvm ) video_cards_gallium-swr? ( any-of ( cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_avx512er cpu_flags_x86_avx512bw ) ) video_cards_gallium-imx? ( video_cards_gallium-vivante ) video_cards_gallium-tegra? ( video_cards_gallium-nouveau ) video_cards_gallium-r300? ( x86? ( llvm ) amd64? ( llvm ) ) video_cards_gallium-radeonsi? ( llvm egl? ( any-of ( drm surfaceless ) ) ) video_cards_gallium-pl111? ( video_cards_gallium-vc4 ) video_cards_gallium-virgl? ( egl? ( any-of ( drm surfaceless ) ) ) video_cards_gallium-vivante? ( gbm ) And one more thing I read in the "https://www.x.org/wiki/RadeonFeature/", that for 2D the kernel driver should be "radeon" and for 3D should be "r600g", but I'm not sure how to get this "r600g" . Thanks!
  1. Load more activity
  • Create New...