Jump to content

mrl5

Members
  • Content Count

    10
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by mrl5

  1. @zdavatz so I've checked your nvidia thread and I did not see any info that you are using SELinux. This forum topic is SELinux related and the described issue was fixed in FL-6772 Sorry if I missed something - did you cross-link this thread because of similarities in logs or there is some other reason? (EE) NVIDIA: Failed to initialize the NVIDIA kernel module BTW when I experienced this bug I was on kernel version 4 (4.9 afair) and you mentioned problems with 5.6 that do not occur in 5.5 BTW2 I see that gentoo did not merge my fix yet: https://github.com/gentoo/gentoo/pull/13350
  2. 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
  3. regarding question #2: I've found this cool blogpost and method described there fixes the problem. All I have to do is to run this command after every boot restorecon /dev/nvidiactl /dev/nvidia0 at this moment I've added it to /etc/init.d/xdm but I'll dig further for better solution so the question no #1 is still open. @drobbins any thoughts? EDIT: Q#1: answered here Q#2: opened bug FL-6772 related to OpenRC
  4. some questions regarding @drobbins announcement: https://forums.funtoo.org/topic/2997-selinux-packages-updated-in-14-and-selinux-next-development/ 1. If I (as funtoo user) report bugs (found on funtoo machine) to Gentoo Hardened SELinux project . Do I also need to report them to bugs.funtoo.org? (example: FL-6753 and 697564). Thats not a problem for me but I don't know what about devs? 2. I think that I found one sec-policy bug related to nvidia which I suspect is funtoo specific. I connect it with this change but I can't tell if it's valid for Gentoo and should
  5. hm.. looks like it's described here: https://www.funtoo.org/Package:NVIDIA_Linux_Display_Drivers @temptorsent could you pls comment is it still expected behavior?
  6. I dont see nvidia in eselect opengl list and eselect opencl list # eselect opengl list Available OpenGL implementations: [1] xorg-x11 * # eselect opencl list Available OpenCL implementations: [1] ocl-icd * # epro show === Enabled Profiles: === arch: x86-64bit build: current subarch: core2_64 flavor: desktop mix-ins: lxde mix-ins: gfxcard-nvidia (...) # emerge -pv nvidia-kernel-modules nvidia-drivers These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] x11-drivers/nvidia-drivers-430.26-
  7. I'm sandboxing some applications and I want to have a sound. I did what's written here: https://wiki.gentoo.org/wiki/Simple_sandbox#Configure_Firefox_to_output_sound_to_larry.27s_PulseAudio_daemon echo -e ".include /etc/pulse/default.pa\nload-module module-native-protocol-unix auth-anonymous=1 socket=/tmp/pulse-socket" > ~larry/.config/pulse/default.pa but I dont like that /tmp/pulse-socket has 777 (rwxrwxrwx) permissions. I found this link: https://gist.github.com/Earnestly/4acc782087c0a9d9db58 created pulseaudio user, added other users to that group and changed `auth-anonymou
  8. mrl5

    funtoo and yubikey

    one more note. If someone plans to play with yubikey-personalization-gui - adding /etc/udev/rules.d/69-yubikey.rules is also needed: https://github.com/Yubico/yubikey-personalization/blob/master/69-yubikey.rules ACTION!="add|change", GOTO="yubico_end" # Udev rules for letting the console user access the Yubikey USB # device node, needed for challenge/response to work correctly. # Yubico Yubikey II ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0010|0110|0111|0114|0116|0401|0403|0405|0407|0410", \ ENV{ID_SECURITY_TOKEN}="1" LABEL="yubico_end"
  9. mrl5

    funtoo and yubikey

    thank you very much! the only thing that I had to do to work with YubiKey on google-chrome was to add this file https://github.com/Yubico/libu2f-host/blob/master/70-u2f.rules to the /etc/udev/rules.d. Installing pam_u2f yubikey-personalization-gui yubikey-manager-qt was not needed at all # cat /etc/udev/rules.d/70-u2f.rules # Copyright (C) 2013-2015 Yubico AB # # This program is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1, or (at your option) # any late
  10. I can not use my YubiKey 5 NFC on funtoo. The device works on Windows. I was testing it on this webpage: https://demo.yubico.com/webauthn-technical/registration with google-chrome. The green LED is present when I plug the device and after I tap it. So far I've installed pam_u2f and added my user to the plugdev group $ dmesg | tail [ 3058.732019] usb 7-1: new full-speed USB device number 7 using uhci_hcd [ 3058.917036] usb 7-1: New USB device found, idVendor=1050, idProduct=0407 [ 3058.917039] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3058.917041] usb 7-1: Pro
  11. That's interesting and I'm concerned. Does anyone can confirm and/or provide examples?
  12. Thank you for so many answers. @savasten good point, thanks! FL-6294, FL-6295 and FL-6297. And I'm okay with it - I would be even more okay if Funtoo would adopt something like this: https://nodejs.org/en/about/releases/ or make it more visible, because I've searched for it and after 5-10 minutes I stopped to search
  13. So I had to update my desktop system from version 1.2 to 1.3 and I've chosen to do the fresh install from the stage3 (stage3-core2_64-1.3-release-std-2019-02-05). But.. During the process I've noticed some (at least for me) ugly things that I would like to inform developers about: TL;DR: metalog is NOT added to any runlevel by default. I think it should be added to default/boot runlevel by default sshd IS added to the default runlevel by default. I think it's bad - this should be disabled by default ... if you want to read further please be advised that I'll be grumpy
×
×
  • Create New...