Jump to content

faultyuseflag

Members
  • Content Count

    7
  • Joined

  • Last visited

About faultyuseflag

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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?
  2. 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?
  3. 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!
  4. 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.
  5. 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!
  6. 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
  7. 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,
×
×
  • Create New...