Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. Same problem with samba 4.11.0. Network is static configuration. I think I need run samba after network init. Any new solution in 2020? Add: I look at logs samba is started after network, but in samba logs network address is not assigned.
  3. Yesterday
  4. This is indicating some issues with OpenGL rendering which would prevent Steam from running. What kernel/nvidia drivers version are you using?
  5. 1/ steam-nvidia-launcher attach seems to work, but it does not come up as the steam-container 'user' on the command line prompt. You can see the prompt name in the photo. 2/ pacat works 3/ glxgears fails. (see attached photo) Note, glxgear works in a regular terminal session as shown in the second photo.
  6. Last week
  7. There are troubleshooting steps here: https://www.funtoo.org/Steam#Container_Validation Try them, let us know your results.
  8. @cardinal that isn't really a fix for the issue, just a workaround. @kundor yes, this is a bug. A couple of weeks ago, our upstream vim had issues, so I forked vim and vim-core. But I did not grab gvim. It should be reported to bugs.funtoo.org and we'll get it fixed. Thanks 🙂
  9. Greetings during unusual times -- I wanted to let everyone know that the following ebuilds are currently being auto-updated using our new, amazing autogen framework. That means we will always have current versions: www-client/firefox-bin www-client/google-chrome www-client/google-chrome-beta www-client/google-chrome-unstable www-client/brave-bin app-admin/pass app-admin/passwordsafe net-misc/anydesk-bin mail-client/thunderbird-bin net-im/discord-bin net-im/zoom-bin net-im/slack-bin More are on the way! For those working remotely, I recommend checking out zoom-bin (Zoom meetings) as well as anydesk-bin (AnyDesk) for fast remote desktop. They work great under Funtoo. Enjoy, and stay safe. -Daniel
  10. Hello all, Setup according to the funtoo.org/Steam page. I'm trying to get Steam working on my box here. In the photo you can see the steam-nvidia-launcher starts the container and then launches Steam. The issue is, although it says "it may take up to 10 seconds before steam comes up" steam never comes up, it just sits there as shown in the second photo. Any ideas? Does the nvidia driver HAVE to be a minimum 435.21-r1? If so, is there another way of getting steam setup without having to go through the steam-nvidia-launcher? Any help, and/or suggestions, would be most welcome. Thanks, Dave
  11. I have a freshly installed funtoo system, consisting only of the stage3 tarball, X server and the proprietary nvidia driver. I set the language to german ("de_DE.utf8" for everything when I type "locale") and the keyboard for X to "de". Everything looking fine. I decided to go for xfce4 as my desktop environment, so i installed the meta package. Xfce4 runs just fine, but the UI is in English and there is no possibility th change that in the settings. How can I change it to german? Mm.
  12. I use https://github.com/fusion809/fusion809-overlay
  13. NOTE: I've reposted this in the Desktop help, where I think it's more appropriate. Can someone delete this, as I cannot find how to. Hello all, Setup according to the funtoo.org/Steam page. I'm trying to get Steam working on my box here. As you can see by the photos, steam-nvidia-launcher starts the container and then Steam. My problem is, as the message states, it may take up to 10 seconds before steam comes up. My problem is, steam never comes up, it just sits there as shown in the second photo. Any ideas? Does the nvidia driver HAVE to be a minimum 435.21-r1? If so, is there another way of getting steam setup without having to go through the steam-nvidia-launcher? Any help, and/or suggestions, would be most welcome. Thanks, Dave
  14. try booting again using a livecd, then chroot (following the steps here - pay close attention to the mount procedure, its options, etc) then: # emerge grub cryptsetup lvm2 # emerge intel-microcode iucode_tool linux-firmware # emerge debian-sources-lts # emerge @module-rebuild
  15. When I try to `emerge gvim`, I get emerge: there are no ebuilds to satisfy "~app-editors/vim-core-8.2.0430". (dependency required by "app-editors/gvim-8.2.0430::editors-kit" [ebuild]) Indeed, there only seems to be vim-core 8.2.0378. Is there a workaround to get gvim to emerge?
  16. Earlier
  17. I should add that I've tried other color modes as well, but they don't take, either. Is the more information that is needed? Are there mores than 1 framebuffer device drivers that could be used, needing different parameters each?
  18. I had come across these posts before, and they do not solve the problem. I've tried both the variant of just the resolution and the resolution with the color bit, and the system never boots up in 1920x1080 mode. I've placed the display module on its own section. What else is going on?
  19. It worked. I'll study about the /etc/portage/package.accept_keywords. Thank's man!
  20. Enable lilyterm-99999.ebuild funtoo /home/rj # echo "x11-terms/lilyterm **" >> /etc/portage/package.accept_keywords/lilyterm funtoo /home/rj # emerge -av x11-terms/lilyterm These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N *] x11-terms/lilyterm-99999::desktop-kit 0 KiB Total: 1 package (1 new), Size of downloads: 0 KiB Would you like to merge these packages? [Yes/No]
  21. I'm trying to install lilyterm, but I receive the following error: I've installed vte, but didn't worked. I've removed the ":0" in the ebuild file (/var/git/meta-repo/kits/desktop-kit/x11-term/lilyterm/lilyterm-0.9.9.4-r2.ebuild), but it gives the error: I've googled it, but didn't find any solution. What the ':0' in the vte means, and how can I solve this?
  22. Don't give up! Your BIOS doesn't have any options for changing between discrete and integrated cards? What's the order your modules are being loaded? Are you using Nvidia's prorietary blob or nouveau?
  23. I've found the problem: My motherboard. I don't have the option to choose between the graphics cards, and the nvidia card is the first one. For Bumblebee to work, the intel graphical card must be the first one. Following the Arch's Bumblebee tutorial, I realized this. Every time the bumblebeed service was started, the system froze. So, given this, it's impossible for me.
  24. Hello, everyone! I have an issue that I haven't been able to resolve yet. Funtoo is running on my system, but I would like to modify the parameters at boot so the boot screen was running in 1920x1080 mode. I believe it is in 1024x768 mode currently, as shown by the "videoinfo" command that I run at the Grub command-line stage. I've modified the /etc/boot file to have a "params += GRUB_GFXMODE=1920x1080-24,auto GRUB_GFXPAYLOAD_LINUX=keep" (along with the root info, of course), but this does not seem to work after I 'ego boot update'. I also modified the file at '/etc/default/grub' to reflect these values (with the (x)x(y)-(b) format which a GTX 970 apparently needs), to no avail. Does 'ego boot update' also process 'grub-mkconfig -o /boot/grub/grub.cfg' when it runs? This seems like a simple matter to resolve, but I've tried many suggestions over the past week, and nothing seems to be working. Thank you for any suggestions!
  25. Hey there, Pennine, Did you ever get an answer to this? I'm curious, as I was having a devil of a time with LVM at install and had to go to a vanilla partition strategy to get it installed.
  26. I answered my own question. In playing around, I had skipped some sections about setting up XDM and SDDM for OpenRC. Going back to the guide and following that, and filling in the blanks with the Gentoo documentation of SDDM with OpenRC helped. (https://wiki.gentoo.org/wiki/SDDM ) Sometimes, it pays to pay close attention to the Wikis!
  27. Hello, everyone, I'm a new convert to Funtoo, I've been playing around with the distribution for the last three weeks, and I think I have almost everything to how I like it. The problem is that it seems that KDE is not installed correctly. I followed the Funtoo Wiki for installing it, and it worked very well upon first booting in after install with the "sddm" command as root. I then powered down, and then booted up again, to find that KDE is defaulting to a software renderer, Plasma seems to not be working correctly, and PulseAudio is not detecting my sound cards anymore. All of this worked before the reboot. Please, let me know what log files I should be looking at in order to correct this. glxinfo shows direct rendering is enabled, glxgears displays properly, nVidia drivers are selected in eselect. Also, when booting up SDDM from TTY1, the screen will flicker, default back to TTY1, and then I will have to manually switch back to 7 with ctrl-alt-F7 in order to see the session. I'm beginning to think that there might be a bus issue in this installation preventing certain modules from communicating with each other. Any advice on where to dig up more information or what to do would be appreciated! Regards, Funtoo Newb
  28. I think this may be a carry-over from the Python mess going on in Gentoo. I had a similar situation with Ruby at install, and corrected it for the time being with this line in make.conf: RUBY_TARGERT="ruby27" I think a PYTHON_TARGETS is what you may need with a new-use rebuild. But, check with others who are more experienced first. I'm just relaying my situation. Regards,
  1. Load more activity
×
×
  • Create New...