Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. 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!
  3. Thank you Cardinal, You have confirmed what I guessed based on that notice on the generic page. You are saying that the only difference between the different subarches is the cpuflags, I wasn't sure if that was true or if there was something else beyond that. Like I thought atom was a more radically different CPU type from the pentium/core types. I guess I'm not sure what is meant to convey by the atom brand. In the end, I went ahead with generic gnome, because what I'm really trying to do is make my own personal binary metadistribution (including my overlay for some obscure stuff I need) and I wanted to be as general as possible and support whatever non-arm hardware I may have. But I understand now I should have chosen nehalem subarch (if I want to support a couple of old core2 minipcs I have in addition to the silvermont one). I may try to change the subarch profile and emerge -e the system at some point, but not now.
  4. Excuse me, I did not realize that the login to the Bugs page is with the username only, unlike the forum page, where you can use the email account. Thank you very much cardinal.
  5. The username and password used for forums should work for bugs. Did you 2fa authenticate using your cell phone number with sms ? Try to login here: https://auth.funtoo.org/login, Fixed luit-1.1.1-r1 is masked in xorg-kit/1.20-release. Broken luit-1.1.1 which should be removed is unmasked and located in core-gl-kit/2.0-release. This is why we see the error again from FL-7169 Replacing luit-1.1.1.ebuild in core-gl-kit with luit-1.1.1-r1.ebuild solves the problem. Reference new bug report : https://bugs.funtoo.org/browse/FL-7308
  6. Last week
  7. Hello everyone, this is my first post, and my first time installing Funtoo. I have been a Gentoo user for a few years. I posted here, because I do not know how to create an account on bugs site, there was already a bug about this (FL-7169) created on the date 08 / May / 20 12:47 PM I am having the following problem installing xorg. localhost ~ # emerge -av xorg-x11 These are the packages that would be merged, in order: Calculating dependencies... done! !!! All ebuilds that could satisfy "x11-apps/luit" have been masked. !!! One of the following masked packages is required to complete your request: - x11-apps/luit-1.1.1::core-gl-kit (masked by: invalid: DEPEND: USE flag 'ppc-aix' referenced in conditional 'ppc-aix?' is not in IUSE) (dependency required by "x11-base/xorg-x11-7.4-r3::core-gl-kit" [ebuild]) (dependency required by "xorg-x11" [argument]) For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. My profile: localhost ~ # epro show === Enabled Profiles: === arch: x86-32bit build: current subarch: atom_32 flavor: desktop mix-ins: gfxcard-intel === Python kit: === branch: 3.7-release === All inherited flavor from desktop flavor: === workstation (from desktop flavor) core (from workstation flavor) minimal (from core flavor) === All inherited mix-ins from desktop flavor: === X (from workstation flavor) audio (from workstation flavor) dvd (from workstation flavor) media (from workstation flavor) mediadevice-audio-consumer (from media mix-in) mediadevice-base (from mediadevice-audio-consumer mix-in) mediadevice-video-consumer (from media mix-in) mediadevice-base (from mediadevice-video-consumer mix-in) mediaformat-audio-common (from media mix-in) mediaformat-gfx-common (from media mix-in) mediaformat-video-common (from media mix-in) console-extras (from workstation flavor) print (from desktop flavor) === All inherited mix-ins from gfxcard-intel mix-ins: === core-gl-kit:gfxcard-intel-classic (from gfxcard-intel mix-in)
  8. If this is still a current issue, it should be reported to the bug tracker, not the forums.
  9. 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.
  10. Hi All, core-gl-kit is now on 2.0-release by default. You will see updates to many packages. Now available are Intel Iris graphics, which is much faster and supported on modern Intel integrated graphics chipsets. To use Intel Iris, perform the following steps: # epro mix-ins -gfxcard-intel +gfxcard-intel-iris # emerge -auDN @world --jobs=3 If you want to continue with the classic drivers, or are not using Intel integrated graphics at all, you can just do the world update to get updates. Please report any issues you encounter to bugs.funtoo.org! There have been major updates to packages so I am expecting some bugs (and some have already been reported and fixed.)
  11. There's no 32bits iso livecd. but you can use the stage3 loading from another livecd.
  12. Hi, I have an HP low-power pc. The processor is a 32-bit athlonxp. I would like to install funtoo. I tried to download the 32-bit athlon file from the funtoo website, but it is not there. I downloaded the funtoo install cd iso and copied it to a usb. It won't boot on this 32-bit pc. My question: Is there a funtoo 32-bit iso image? Thanks, donjames
  13. Don't use a subarch that includes CPU_FLAGS that are not supported by the CPU of the target hardware(intel64-silvermont) or compiler(intel64-ivybridge). Reference the Funtoo CPU Guide to find it's subarch, then go to the subarch download page to find it's CPU_FLAGS. Reference intel64-nehalem subarch download page to find it's CPU_FLAGS. The atom(silvermont) cpu and the i5(ivybridge) cpu support all the CPU_FLAGS in the intel64-nehalem subarch. Yes, you could use the intel-nehalem subarch on the i5 to build software for the atom. It would be a problem if you are building to run on an older CPU that doesn't support all the nehalem CPU_FLAGS. If you are only building packages for the atom then use intel64-silvermont on the i5 . Don't use intel64-ivybridge subarch on the i5 to build packages for atom because the atom doesn't have avx. generic_64 : mmx mmxext sse sse2 intel64-nehalem : mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3 intel64-silvermont: aes mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3 intel64-ivybridge: aes avx mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3
  14. Earlier
  15. I've got an embedded machine with a 4 core atom CPU (C2758 @ 2.40GHz) that I've run reliably with silvermont subarch. I've not been able to upgrade from 1.3 to 1.4 without significant dependency issues. I want to convert an old laptop ( Core i5-3317U CPU @ 1.70GHz) to a development machine so I don't have significant downtime on the atom PC. The idea is I'll keep this old hardware around just for being a compile machine for bleeding edge packages that I'll then distribute out as a stage 4 tarball to upgrade and then continue upkeep with qpkg. I originally meant to just go with generic subarch and use this old laptop to serve out to the atom machine as well as some other machines that I don't want to be down for long. but as I went to get the generic_64 stage 3 I read on the webpage how the generic64 was discouraged and you should really use a nehalem stage 3 since it is good for all post 2009 intel CPUs and most recent AMD cpus. Does this include atom processors? I'm assuming generic_64 is truly generic for all x86_64, atom core or whatever. I'm not sure this istrue for the nehalem stage despite what the subarch page implies. PS I know my compile machine is slower than my target machine and this seems perverse. But compile time is not a huge issue it's downtime on the target that is a problem. Also due to Covid, I can't get in to touch my target machine right now, I have to just use what I've got on hand. target cpuino: processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 77 model name : Intel(R) Atom(TM) CPU C2758 @ 2.40GHz stepping : 8 microcode : 0x127 cpu MHz : 1200.000 cache size : 1024 KB physical id : 0 siblings : 8 core id : 7 cpu cores : 8 apicid : 14 initial apicid : 14 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb kaiser tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm arat bugs : cpu_meltdown spectre_v1 spectre_v2 bogomips : 4800.23 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: compiler cpuinfo: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz stepping : 9 microcode : 0x15 cpu MHz : 807.188 cache size : 3072 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf bogomips : 3392.34 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:
  16. I can't figure out why I don't get emails from Jira when someone updates a ticket that I've created or watched. Poked all around the Jira settings and account. Is it just me?
  17. This has been fixed ... reinstalled using the gnome-current stage
  18. thank you for the solution I have file bug report at FL-7275
  19. File an issue report at bugs.funtoo.org rj@funtoo ~ $ gimp (gimp:14880): GLib-GObject-CRITICAL **: 10:19:51.172: g_param_spec_internal: assertion 'is_valid_property_name (name)' failed gimp: fatal error: Segmentation fault (gimp-org-pagecurl:14912): LibGimpBase-WARNING **: 10:19:51.227: gimp-org-pagecurl: gimp_wire_read(): error Always try to start a program in terminal when it fails by clicking shortcut in start menu. The error message enabled me to find the closed upstream bug report and a temporary workaround. https://gitlab.gnome.org/GNOME/gimp/-/issues/4392
  20. Hi, just completed the upgrade for gnome 3.36.2 and and all went well, but now upon a fresh ego sync and emerge -avDN @world, i'm getting an X warning about my xdm file tux-x131e ~ # emerge -avDN @world These are the packages that would be merged, in order: Calculating dependencies... done! Total: 0 packages, Size of downloads: 0 KiB Nothing to merge; quitting. tux-x131e ~ # emerge --depclean * Always study the list of packages to be cleaned for any obvious * mistakes. Packages that are part of the world set will always * be kept. They can be manually added to this set with * `emerge --noreplace <atom>`. Packages that are listed in * package.provided (see portage(5)) will be removed by * depclean, even if they are part of the world set. * * As a safety measure, depclean will not remove any packages * unless *all* required dependencies have been resolved. As a * consequence of this, it often becomes necessary to run * `emerge --update --newuse --deep @world` prior to depclean. Calculating dependencies... done! >>> Calculating removal order... dev-libs/ocl-icd selected: 2.2.12-r1 protected: none omitted: none virtual/linux-sources selected: 2.6 protected: none omitted: none dev-libs/wayland selected: 1.17.0 protected: none omitted: none app-eselect/eselect-opencl selected: 1.2.0 protected: none omitted: none dev-util/opencl-clhpp selected: 20190207 protected: none omitted: none dev-util/opencl-headers selected: 20190412 protected: none omitted: none All selected packages: =app-eselect/eselect-opencl-1.2.0 =dev-util/opencl-headers-20190412 =dev-libs/wayland-1.17.0 =virtual/linux-sources-2.6 =dev-libs/ocl-icd-2.2.12-r1 =dev-util/opencl-clhpp-20190207 >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging (1 of 6) dev-libs/ocl-icd-2.2.12-r1... >>> Unmerging (2 of 6) virtual/linux-sources-2.6... >>> Unmerging (3 of 6) dev-libs/wayland-1.17.0... >>> Unmerging (4 of 6) app-eselect/eselect-opencl-1.2.0... >>> Unmerging (5 of 6) dev-util/opencl-clhpp-20190207... >>> Unmerging (6 of 6) dev-util/opencl-headers-20190412... Packages installed: 1073 Packages in world: 10 Packages in system: 81 Required packages: 1073 Number removed: 6 * GNU info directory index is up-to-date. * IMPORTANT: config file '/etc/conf.d/xdm' needs updating. * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS * sections of the emerge man page to learn how to update config files. tux-x131e ~ # We always try and start X on a static VT. The various DMs normally default # to using VT7. If you wish to use the xdm init script, then you should ensure # that the VT checked is the same VT your DM wants to use. We do this check to # ensure that you haven't accidentally configured something to run on the VT # in your /etc/inittab file so that you don't get a dead keyboard. CHECKVT=7 # What display manager do you use ? [ xdm | gdm | sddm | gpe | lightdm | entrance ] # NOTE: If this is set in /etc/rc.conf, that setting will override this one. DISPLAYMANAGER="gdm" I don't understand what or how it needs to be updated. X has started flickering and crashing since the update. It happens after 5 minutes when screen dims to go to sleep. Is there something i neglected to clean up? regards, Tom
  21. Installed gimp successfully but it fail to start having segmentation fault ``` GNU Image Manipulation Program version 2.10.10 git-describe: GIMP_2_10_8-775-g596f855749 C compiler: Using built-in specs. COLLECT_GCC=x86_64-pc-linux-gnu-gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../gcc-9.2.0/configure --disable-libssp --disable-multilib --enable-version-specific-runtime-libs --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/9.2.0 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/9.2.0 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/9.2.0/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/9.2.0/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include/g++-v9.2.0 --enable-clocale=gnu --host=x86_64-pc-linux-gnu --enable-obsolete --disable-werror --enable-libmudflap --enable-secureplt --enable-lto --with-system-zlib --without-cloog --with-bugurl=http://bugs.funtoo.org --with-pkgversion='Funtoo 9.2.0' --enable-stage1-checking=assert,runtime,misc,tree,gc,rtlflag --enable-checking=assert,runtime --enable-languages=c,c++,fortran --disable-libgcj --enable-threads=posix --enable-__cxa_atexit --enable-libstdcxx-time --enable-libgomp --enable-bootstrap --enable-shared --build=x86_64-pc-linux-gnu --disable-libsanitizer --enable-default-pie --enable-default-ssp --disable-libstdcxx-pch --disable-vtable-verify --disable-libvtv --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/9.2.0/python --enable-nls --with-included-gettext --with-tune=generic Thread model: posix gcc version 9.2.0 (Funtoo 9.2.0) using GEGL version 0.4.22 (compiled against version 0.4.22) using GLib version 2.64.2 (compiled against version 2.64.2) using GdkPixbuf version 2.40.0 (compiled against version 2.40.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.44.7 (compiled against version 1.44.7) using Fontconfig version 2.13.0 (compiled against version 2.13.0) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Segmentation fault Stack trace: ``` /usr/lib64/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x398)[0x7f570db78338] gimp-2.10(+0xd3710)[0x557292443710] gimp-2.10(+0xd3b38)[0x557292443b38] gimp-2.10(+0xd41a9)[0x5572924441a9] /lib/libpthread.so.0(+0x14670)[0x7f570d055670] gimp-2.10(gimp_param_spec_layer_id+0x64)[0x5572927c16e4] gimp-2.10(gimp_pdb_compat_param_spec+0x1c7)[0x5572926dc817] gimp-2.10(gimp_plug_in_handle_message+0x1197)[0x5572926e9207] gimp-2.10(gimp_plug_in_manager_call_query+0x191)[0x5572926f7811] gimp-2.10(gimp_plug_in_manager_restore+0x796)[0x5572926ef7a6] gimp-2.10(+0x39d34d)[0x55729270d34d] /usr/lib64/libgobject-2.0.so.0(g_closure_invoke+0x1a2)[0x7f570d2eefd2] /usr/lib64/libgobject-2.0.so.0(+0x26f06)[0x7f570d301f06] /usr/lib64/libgobject-2.0.so.0(g_signal_emit_valist+0xbdf)[0x7f570d30d54f] /usr/lib64/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f570d30dedf] gimp-2.10(gimp_restore+0x102)[0x55729270c8d2] gimp-2.10(app_run+0x4ab)[0x55729244303b] gimp-2.10(main+0x36e)[0x5572924427ce] /lib/libc.so.6(__libc_start_main+0xeb)[0x7f570ce92e9b] gimp-2.10(_start+0x2a)[0x55729244295a] ```
  22. Ok thank you drobbins, I have removed the gfxcard-intel mix-in. By cons I do not know how to register on bugs.funtoo.org to post the emerge error for the wpebackend-fdo package in bug FL-7195 for core-gl-kit.
  23. Please report bugs as needed. Also, yes, currently xf86-video-intel will keep getting pulled in if you have the mix-in for it enabled. You can either disable this mix-in or emerge --exclude xf86-video-intel for now.
  24. In response to drobbins about installing the new Intel Iris graphic driver, I can't uninstall the xf86-intel-driver package even when hiding it. By cons I can uninstall xf86-video-fbdev. Also, I have an installation error of the wpebackend-fdo package: * ERROR: gui-libs / wpebackend-fdo-1.6.0 :: core-gl-kit failed (prepare phase): * patch -p1 failed with /var/tmp/portage/gui-libs/wpebackend-fdo-1.6.0/files/1.6.0-eglmesaext-include.patch Regards.
  25. Hi All, If you are interested in testing Intel Iris graphics (new accelerated graphics for newer Intel chipsets), here's how you do it: First, make sure your system is up-to-date and you have the latest available version of ego installed (2.8.1) Next, add the following to /etc/ego.conf: [kits] core-gl-kit = 2.0-release xorg-kit = skip This will result in our 2.0-release core-gl-kit being activated, which completely replaces xorg-kit, as all of xorg has been integrated into core-gl-kit 2.0-release. We do not have a mix-in yet for intel Iris graphics. For now, set the following in /etc/make.conf: VIDEO_CARDS="$VIDEO_CARDS intel gallium-iris vulkan-intel xa xvmc vdpau" Now: # emerge -auDN @world *Unmerge* xf86-video-intel: # emerge -C xf86-video-intel Now, restarting X should result in Intel Iris being active. General feedback can be posted to this Funtoo issue: https://bugs.funtoo.org/browse/FL-7195 Specific failures can be reported in their own issues. Please be sure to report any problems including difficulty upgrading to core-gl-kit 2.0-release. Please note that 2.0-release core-gl-kit is BETA and I am actively working on redoing the xorg-server stack, so active development is going on in this kit branch.
  26. I've already found the issue and resolved it. 🙂 Fix should be in the tree on next regen, in about 25 minutes.
  1. Load more activity
×
×
  • Create New...