Jump to content

drobbins

Funtoo Linux BDFL
  • Content Count

    435
  • Joined

  • Last visited

  • Days Won

    209

drobbins last won the day on November 29

drobbins had the most liked content!

About drobbins

  • Rank
    Administrator

Online

Personal

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

Recent Profile Visitors

6,715 profile views
  1. I do not have the UI built out for this yet, but you can contact me via PM on the forums and I can change it for you.
  2. @rekena I am not seeing anything obvious from what you posted indicating a problem. As @lego12239 asked, what specifically are you seeing? Based on what you originally said, it sounds like GRUB is not even loading for you? If this is the case, then we want to make sure grub bootloader has been installed, so.... Make sure you have run the "grub-install (with arguments from install docs)" command from the install instructions. This will install the boot loader. Then run "ego boot update" in chroot. Then when you reboot grub should load. If grub is loading, but the kernel can't find the root filesystem, then this is a *different* issue related to partition naming and what I assume @pnoecker was thinking. But you are saying that grub isn't starting. So I don't think we should look here. In any case, please clarify exactly what you are seeing 🙂
  3. This is normal. The grub.cfg paths are relative to /boot.
  4. This is probably not the problem and shouldn't be the first advice to try to address the issue.
  5. Hey everyone, I have updated our Development Guide to contain information on the "Funtoo Way". The "Funtoo Way" is a really important philosophy about how we do things at Funtoo and I strongly encourage everyone to read it, even if you don't consider yourself a "developer". It helps to explain how our community works and how we can work together. https://www.funtoo.org/Development_Guide Best, Daniel
  6. Note that basic stage3 is up. GNOME stage is being worked on.
  7. Now that the Sabayon collaboration has been announced, yes, it does open up the possibility that Funtoo might provide binaries in the future. It is not a high priority at the moment but I could see this eventually being added to what Funtoo offers.
  8. @davidvs If there is a package in Gentoo that you want in Funtoo, you can open a bug for it explaining why you would like it and we can most likely add it. This is the easiest way rather than messing with getting it working yourself.
  9. I tried to make this clear in the announcement, but it is worth explaining in more detail -- Sabayon Linux and Funtoo Linux are going to remain distinct things. We will make the Funtoo tree work for Sabayon so we can all contribute to the same set of packages. There is no implied change to either Funtoo or Sabayon, besides Sabayon moving to use the Funtoo tree, by announcing this collaboration. Each project continues to make decisions for its own community with no obligation to switch to different technologies unless one project decides it wants to. Over time, we will be collaborating on technology and some technology will be shared -- because it will be designed to make both Sabayon and Funtoo communities happy. Due to the nature of ebuilds, we can build two separate projects using the same base as a start. Sabayon has not had a lot of public activity because they have been heavily working on their next evolution of the OS. They have been very busy, but it has been behind the scenes. Best, Daniel
  10. The short answer is that Funtoo is going to remain independent of systemd upstream. I do believe that startup scripts and management of the system are part of what give a Linux distribution its personality. It is central to the experience. Sabayon needs systemd. It will be added to Funtoo's tree for Sabayon, but not enabled in Funtoo. That way, everyone is happy.
  11. The situation with the -bin packages can best be explained this way. For some browsers such as Chrome, we are getting security fixes from Google at the pace of at least once a week, sometimes more. Chrome is a big thing to compile over and over again. It is also some effort to keep the ebuild updated to deal with all upstream changes at this pace. So a big part of this is based on the many releases we are getting from upstream projects that have a huge amount of source code. For us, it is easy to auto-update these -bin packages using metatools (which happens automatically) than rush to manually re-tool and test an ebuild to build it all from sources (possibly with new dependencies that if we update them, will break other things on your system.) This is not an ideological decision but a practical one. For now, for browsers in particular, this is by far the easiest way to "keep up" with all the churn upstream. We support having from-source builds of Chrome, Firefox, etc. as well but these updated ebuilds do require some effort and testing. As always, PRs are welcome! (So, if our non-bin version is a bit older than the -bin, it just means no one has gotten around to doing the work to update it yet. But you can help with that 🙂 Best, Daniel
  12. Hey everyone, I'm pleased to announce that Funtoo Linux and Sabayon (https://www.sabayon.org) are joining forces! Now to explain what this means and how it came about. Sabayon is one of the great Open Source projects and has an amazing reputation for delivering an easy-to-use Linux desktop that is built using Gentoo. For quite a while, Funtoo has been supporting the Sabayon effort because we believe in what they do. Over the past several months, in chatting with the Sabayon team, it became really clear that we had a shared vision for creating a friendly and innovative community. We also were working on several next-generation technologies that were a good complement to one another. We decided it would be more powerful -- and fun -- to combine our efforts into one larger effort. So that is what we are doing. What this means is that while each project will maintain its own personality, projects and management, we will be logically combining into a larger effort and there will be a tremendous amount of cross-project collaboration. This collaboration immediately multiplies our capabilities for delivering some next generation technologies that we have been working on and are excited to share with you. The most immediate result of this collaboration is that moving forward, Sabayon OS efforts will be built on Funtoo. This, however, is just the first step. What I can say is that there will be much sharing of technology which will benefit both projects, and many new things. For existing users of Sabayon and Funtoo, the communities you know and love will have new strength, support and ability to tackle a new phase of Linux Open Source innovation. I am really excited about this collaboration. Welcome, Sabayon team! Best, Daniel Robbins
  13. Funtoo Linux stages have been updated to contain the latest stuff in Funtoo: GNOME 3.36.2, latest Mesa/GL stack, support for Intel Iris graphics ("epro mix-in -gfxcard-intel +gfxcard-intel-iris; emerge -auDN @world for those who want to try), and many other updates. Download here: https://www.funtoo.org/Subarches Install docs here: https://www.funtoo.org/Install Enjoy!
  14. If this is still a current issue, it should be reported to the bug tracker, not the forums.
  15. Just going to follow up with some more info. First, thanks to pross for pointing out I had a typo in the 'epro' command above, now fixed! 🙂 The difference between Intel Iris and 'classic' Intel is that 'classic' Intel uses the xf86-video-intel driver (with ebuild of same name), which has classically been the way you get accelerated video with Intel Integrated graphics. The Iris graphics uses the more generic 'modesetting' driver (no special ebuild for this), and uses a gallium-based driver which is now a part of media-libs/mesa so xf86-video-intel is not used at all. During testing I found that if you have xf86-video-intel installed, you *won't* get the Iris graphics. xf86-video-intel seems to have priority and will get initialized first. So if you are doing troubleshooting or not using the magic mix-ins, you'll want to make sure that xf86-video-intel is not installed if you want to use Iris. The way to check what driver is being used -- the definitive way -- is to look at /var/log/Xorg.0.log and search for 'modesetting' and 'intel' and determine which if any are initialized. In some circumstances, you may see references to both so you need to look very carefully at the end to see which one is active. Now, about the mix-ins themselves which handle all the complication for you, so you just set the right one and don't have to tweak everything by hand. The gfxcard-intel (gfxcard-intel-classic) and gfxcard-intel-iris mix-ins do the 'magic' for you -- gfxcard-intel-iris will MASK xf86-video-intel, and enable video_cards_gallium-iris, which along with a dep in xorg-drivers will BLOCK xf86-video-intel from being installed (forcing it to be uninstalled.) Thus, the "magic" that gets your system in the proper state for Iris. The mix-ins live in /var/git/meta-repo/kits/core-gl-kit/profiles/funtoo/mix-ins if you want to look at their exact settings. You will see there also associated USE flags associated with each mix-in that are passed to the mesa ebuild which are different for the classic and Iris configuration.
×
×
  • Create New...