drobbins

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.
 

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.
 

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.
 

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.
 

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.
 

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.
 

Looks great -- good work!

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.

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.

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!

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!

need to edit /etc/inittab and make sure the lines
# TERMINALS
#x1:12345:respawn:/sbin/agetty 38400 console linux
#c1:12345:respawn:/sbin/agetty 38400 tty1 linux
#c2:2345:respawn:/sbin/agetty 38400 tty2 linux
#c3:2345:respawn:/sbin/agetty 38400 tty3 linux
#c4:2345:respawn:/sbin/agetty 38400 tty4 linux
#c5:2345:respawn:/sbin/agetty 38400 tty5 linux
#c6:2345:respawn:/sbin/agetty 38400 tty6 linux

are commented/REM'd like the above

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.

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.

Also, it should now be possible to post replies here if you are an active forums member.... hopefully it's working ?

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.

Hey all,
I've been really busy this month -- in Funtoo-land as well as on other projects (currently in Washington, DC area doing some work.)
I've just moved 1.4-release to ALPHA status (it was "in development" status) and will be working on getting some alpha builds available. I've updated the snapshot that 1.4 is based upon and frozen 1.4 so 1.4 will be based on a June 21, 2019 snapshot of Gentoo. I will also be looking to start a non-frozen variant of Funtoo again...
New Firefox and firebox-bin are now in the tree to address security issues.
I've also added the latest version of dev-lang/dart to the tree. This is a very interesting language that comes from Google and recently received a major revamp to make it really nice. Here's an interesting article about it: https://hackernoon.com/why-i-moved-from-java-to-dart-8f3802b1d652 . I am using Dart to do multi-platform development using Google's flutter (which uses Dart) -- and I've enjoyed my experience so far.
More updates to come...
Best,
Daniel

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.

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.

Everyone,
I have just started getting kit-fixups ready for 1.4-release development. Some key changes that are coming in 1.4-release:
move away from eselect opengl and to libglvnd. official support of container-based solution for steam, etc. updates to pam and pambase 1.4-release will be tracking "current" gentoo for a while and will freeze sometime this summer, likely in June 2019. If you want to get involved, chat on #funtoo and look at the latest commits to kit-fixups on code.funtoo.org. I'll also be doing some introductory videos on how to get involved with the new release of Funtoo.
-Daniel

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.

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.

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.

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.

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.