Jump to content
funtoo forums


Funtoo Linux BDFL
  • Content Count

  • Joined

  • Last visited

  • Days Won


drobbins last won the day on August 19

drobbins had the most liked content!

About drobbins

  • Rank



  • Location
    Albuquerque, NM, USA
  • Interests
    Cycling, Cars, Motorcycle.... Funtoo :)

Recent Profile Visitors

3,822 profile views
  1. Hey everyone, 1.4 is almost ready to be released. Thanks so much to everyone who has contributed pull requests for 1.4 and tested 1.4. There's still a bunch of work to do, but there always will be and I believe 1.4 will be our most well-tested release so far. After 1.4 is released, we will start development on 2.0, to be released some time in the Fall (Sept/Oct timeframe). I've been thinking about the release schedule a lot and I think that aiming for a .0 release every Fall seems to be a good idea. This means the work is completed well before the winter holidays, and fall in the US is a good season of change and looking forward to new things. What I have left to do for 1.4 is to update the ARM builds to 1.4 and then also to update our documentation, release notes, upgrade steps and related docs. I want to incorporate the new video cards mix-ins into the official installation steps and not leave it to just be a "First Steps" item after install. This way, people can use the install docs to get their desktop environment of choice up and running, too. I hope to get all this completed in the next few days.
  2. Everything is working well as of now πŸ™‚ Yesterday there were a few conflicts as I integrated mesa-gl-headers into the mix and updated the opengl virtual. All should be good now.
  3. Yes, I think that ~ is necessary -- otherwise it won't find it.
  4. This was my fault -- and should now be fixed. I created a new ebuild called mesa-gl-headers which contains only the headers for mesa. But I included a lot of extra headers by mistake. I didn't get it fixed until the evening but is now definitely resolved πŸ™‚
  5. Oh, also, welcome to the 4K club (written from my thinkpad p1 πŸ™‚
  6. So when the system boots, grub will display, and it will potentially set a resolution. Is the grub resolution OK? If you are using UEFI, it may be too small at GRUB. This is important to know because we need to figure out at what point it should be fixed πŸ™‚ If it is getting really small during boot, this is due to kernel modesetting which is something different. If grub is at a decent resolution, then booting with the "nomodeset" kernel parameter will prevent things from getting too small at boot. You will need modesetting for many graphics drivers, but this is a quick fix to avoid using a magnifying glass when you are setting up your system πŸ™‚
  7. So, it turns out I had a few little things I needed to fix -- currently running through continuous integration to ensure everything is good. Will post here when I've confirmed this.
  8. Hey Everyone, I recently upgraded to a newer Thinkpad Laptop (P1) and decided this was a good time to upgrade Funtoo's graphics stack to sort of finish the work that TemptorSent had started. You'll recall that if you tested 1.4, media-libs/mesa could be quite picky with USE vars/VIDEO_CARDS settings. This should now be fixed. One thing that bugged me when I installed Funtoo on my P1 was that video acceleration wasn't working well. So I've tried very hard to address this so that "out of the box" with minimal/no configuration, you will have good video acceleration support in Funtoo. New documentation on this system that is now in 1.4 can be found here: https://www.funtoo.org/Make.conf/VIDEO_CARDS In particular, see here: https://www.funtoo.org/Make.conf/VIDEO_CARDS/Mix-ins (This table is also included in the main page linked above.) You'll also see extensive documentation on the new VIDEO_CARDS settings that are available and all map directly to a particular graphics driver now (eliminating confusion between gallium and DRI drivers that existed.) The workstation and desktop flavors will now auto-enable Open Source Intel integrated graphics (DRI) and Radeon Gallium graphics (Gallium) -- enabling Vulkan for both. I did not enable nvidia or nouveau by default as I leave this choice of proprietary vs. open source to the user (for Intel and Radeon, the best choices are obvious so safe to enable these.) This should be a big step towards getting everyone optimal video performance in Funtoo without significant work! Be sure to give https://www.funtoo.org/Make.conf/VIDEO_CARDS/Mix-ins and the parent page a good read. And if you use firefox, play around with the h264ify plugin to optimize YouTube video playback and see if it helps reduce your CPU usage. Enjoy!
  9. Just a note -- be sure to submit pull requests for anything like this so we can get fixes into Funtoo, if you haven't already πŸ™‚ Thanks πŸ™‚
  10. Just a note --I am not sure if you used our cinnamon mix-in or not. Hopefully it will make things easier. If it needs any fixes or improvements for 1.3 or 1.4, please do not hesitate to open an issue on the bug tracker or submit a PR to code.funtoo.org.
  11. I've removed the PDEPEND from nvidia-drivers so they don't automatically install nvidia-kernel-modules. But nvidia-kernel-modules has nvidia-drivers as a dependency. So if you are installing on bare metal, do emerge nvidia-kernel-modules and you will get everything you need, and if you are installing in container, emerge nvidia-drivers and it will skip the modules. This should be in the live tree for 1.4 already.
  12. None that I can think of. And I will start the 1.4 AWS builds soon as well.
  13. In my testing, the --exclude method did not work and I manually modified the PDEPEND in nvidia-drivers in /var/git/meta-repo/kits for now as a local work-around. Just a note -- you will likely need to do this too. Other option is to also --exclude nvidia-drivers and then do an emerge -1 nvidia-drivers --exclude nvidia-kernel-modules after the big emerge.
  14. If you hit EAPI errors like this, be sure to report bugs to bugs.funtoo.org and be sure to include the release of Funtoo you're using and what you tried to emerge that died and we'll get them fixed! πŸ™‚
  15. Also note that for now, if you are using nvidia drivers, add an --exclude nvidia-kernel-modules to your emerge line when emerging everything. The nvidia-kernel-modules won't build in containers and you don't need them anyway. I will look into a fix for this.
  • Create New...