Jump to content
funtoo forums

drobbins

Funtoo Linux BDFL
  • Content Count

    343
  • Joined

  • Last visited

  • Days Won

    155

Everything posted by drobbins

  1. OK, thanks for testing and reporting this. I should be able to fix it. If you have some time, can you report an official bug on bugs.funtoo.org and then I will reference it in the commit that fixes this issue. Thanks.
  2. 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.
  3. 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.
  4. Yes, I think that ~ is necessary -- otherwise it won't find it.
  5. 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 🙂
  6. Oh, also, welcome to the 4K club (written from my thinkpad p1 🙂
  7. 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 🙂
  8. 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.
  9. 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!
  10. 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 🙂
  11. 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.
  12. 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.
  13. None that I can think of. And I will start the 1.4 AWS builds soon as well.
  14. 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.
  15. 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! 🙂
  16. 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.
  17. Also, it should now be possible to post replies here if you are an active forums member.... hopefully it's working 🙂
  18. Hey everyone, I have added documentation on how to essentially get Steam running in Funtoo using LXD. First, you will want to follow these instructions to get LXD running: https://www.funtoo.org/LXD Then, follow these instructions, which will get you to the point of setting up a multilib Gentoo container that can run glxgears. At that point, getting Steam running should be pretty straightforward: https://www.funtoo.org/LXD/GPU_Acceleration Please test it out and let me know how it works.
  19. Also note -- kde5-plasma *should* also merge cleanly. While I don't personally use this desktop environment, I have started testing plasma builds. Please report any issues you encounter.
  20. Hey everyone, Just wanted to let you know that as of last night, I am happily running GNOME 3.32 with no issues (I did need to fix librsvg to get SVG's to display properly, but after that, it's working great.) I successfully upgraded my dev workstation from 1.3 to 1.4. If you want to upgrade from 1.3, or install a fresh 1.4 using one of our 1.4 stages (now available for Intel only), things should work well. One thing to note, on both the beta 1.4 stages and a 1.3 upgrade, you will need to manually run "eselect python set --python3 python3.7" to set python3.7 to be the default python interpreter instead of 3.6. Our stages will be fixed to have this set already but this is not done yet. I will also include a copy of my post from another place on the forums about upgrading from 1.3: So, upgrade is pretty easy this time around.I will have instructions soon. But you can basically use "standard" upgrade steps. I recommend emerge -1 glibc gcc first, then emerge -auDN @world should generally work. Report any bugs related to upgrade like failed builds because often this can be fixed by tweaking dependencies. Overall the upgrade is MUCH easier than 1.2 -> 1.3. One trick is to remember to "eselect python set --python3 python3.7" after python-3.7 is emerged to make it default. Also, mesa right now is very picky about USE flags related to video card. For example, if you don't have a card that supports vulkan, you cannot have vulkan in USE. Same with xa and other things that were more "permissible" before. As of yesterday, I am now happily running gnome 3.32 and it is working perfectly. I would still call things "in beta" but the remaining issues (there is a "reboot doesn't work" issue currently active, due to a missing /run/initctl -> /dev/initctl symlink) should be worked out with minor package updates.
  21. So, upgrade is pretty easy this time around.I will have instructions soon. But you can basically use "standard" upgrade steps. I recommend emerge -1 glibc gcc first, then emerge -auDN @world should generally work. Report any bugs related to upgrade like failed builds because often this can be fixed by tweaking dependencies. Overall the upgrade is MUCH easier than 1.2 -> 1.3. One trick is to remember to "eselect python set --python3 python3.7" after python-3.7 is emerged to make it default. Also, mesa right now is very picky about USE flags related to video card. For example, if you don't have a card that supports vulkan, you cannot have vulkan in USE. Same with xa and other things that were more "permissible" before. As of yesterday, I am now happily running gnome 3.32 and it is working perfectly. I would still call things "in beta" but the remaining issues (there is a "reboot doesn't work" issue currently active, due to a missing /run/initctl -> /dev/initctl symlink) should be worked out with minor package updates.
  22. Been doing automated tests all day today, adding fixes as I find things, and also added a fix so kde-plasma-5 should merge fine now.
  23. More fixes added for a bunch of build issues I detected overnight. Ibus, gnome-settings-daemon and mutter compilation without wayland enabled, and others. Will continue doing build tests over here to try to find any issues I can.
  24. I found a last-minute bug related to xorg-server building with some new tweaks to mesa and libglvnd. I have applied some fixes and as of right now the tree is being regenerated. When you have the fixes, 'glvnd' global USE will be enabled with workstation or desktop profile. And you may need to re-emerge mesa-19.1 if xorg-server doesn't build. Since it's a beta, I won't always make things perfectly smooth -- that is the goal for the release 😉
  25. Everyone, 1.4-release is now in BETA -- GNOME 3.32 should now build and be ready to test. Please file bug reports for any bugs you encounter. Best, Daniel
×
×
  • Create New...