kery

Fix and bug Report here: https://bugs.funtoo.org/browse/FL-11061

Progress report: Disabling the MATE Software Compositor (System->Prefrences->Look and Feel->Windows) made stuff like VLC playing smooth, but started graphics tearing. No solution at all, but info maybe helps others somehow (or watching videos temporarily stutter free 😂 ).

Hi, after managing to install stage3 MATE variant and enabling gfxcard-intel mix-in (for Mobile GME965/GLE960 Integrated Graphics Controller, in particular a GLE960) + updating the entire system, i still get bad video performance on players like vlc (stuttering and high cpu usage). The high cpu usage, bad video quality and stuttering is a clear indication that there is very likely no hw acceleration involved or wrong/missing codecs. Any ideas what to fix or look at to find the cause? I had a live NomadBSD usb pen at hand and checked just for testing purposes the video output and quality there. Hw acceleration works out of the box and video quality was excellent, no stutter, no (too) high cpu usage. epro show: === Enabled Profiles: === arch: x86-64bit build: next subarch: core2_64 flavor: desktop mix-ins: mate mix-ins: gfxcard-vmware mix-ins: gfxcard-kvm mix-ins: gfxcard-radeon mix-ins: gfxcard-amdgpu mix-ins: gfxcard-nvidia mix-ins: gfxcard-intel === Python kit: === branch: next === 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-vmware mix-ins: === core-gl-kit:gfxcard-vmware (from gfxcard-vmware mix-in) === All inherited mix-ins from gfxcard-kvm mix-ins: === core-gl-kit:gfxcard-kvm (from gfxcard-kvm mix-in) === All inherited mix-ins from gfxcard-radeon mix-ins: === core-gl-kit:gfxcard-radeon (from gfxcard-radeon mix-in) === All inherited mix-ins from gfxcard-amdgpu mix-ins: === core-gl-kit:gfxcard-amdgpu (from gfxcard-amdgpu mix-in) === All inherited mix-ins from gfxcard-nvidia mix-ins: === core-gl-kit:gfxcard-nvidia (from gfxcard-nvidia mix-in) === All inherited mix-ins from gfxcard-intel mix-ins: === core-gl-kit:gfxcard-intel (from gfxcard-intel mix-in) core-gl-kit:gfxcard-intel-iris (from core-gl-kit:gfxcard-intel mix-in) lshw -C display: *-display:0 description: VGA compatible controller product: Mobile GME965/GLE960 Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 0c width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:16 memory:e0400000-e04fffff memory:d0000000-dfffffff ioport:2000(size=8) memory:c0000-dffff Thanks in advance K.

Yes. It took some time for me to figure that out 😕

Core2 stage3 works flawless on Intel Pentium P6200.

More on this gnome-* apps execution session crash thing (can be considered solved) here: https://bugs.funtoo.org/browse/FL-11051

Solved that isse. (Partially) my fault. Reason was the missing gfxcard-intel mix-in for the on board intel gfx chip . But the install tutorial needs to be revised/improved in between the steps 16 and 17. I will place a improvement request on the bug tracker and explain why. Improvement suggestion here: https://bugs.funtoo.org/browse/FL-11051

Hi, trying to run anything gnome-* and some other gui applications on fresh install&update core2 gnome stage3 (gnome-stage3-core2_64-next-2023-01-30.tar.xz) crashes entire session and sends back to login screen. Impossible to enter places like gnome-control-center. Whatever needs to be "adjusted" has to be done via terminal/shell. Where to start to find the cause? tia K.

...booting into gnome stage3 works without any issue. Login into session works too, but whenever i try to start something related to gnome-*, like gnome-control-center, the entire session crashes and sends me back to the login screen. Some applications work flawless, other crash entire session. As said, mostly gnome-* binaries 😞

The Core2 stage3 works!

Nehalem also failed. That silent fchroot/chroot fail (ill open a bug report on it later). The Core2 march seems to meet the requirement by your gcc check. Ill give it a try now and report here.

Hi, at first i wanted to build a system around the latest stage3 from the westmere build available here: https://build.funtoo.org/next/x86-64bit/intel64-westmere/2023-01-31/ But it failed always either on chrooting into the new system from the live system with a "Illegal Instruction" exception or failed with a manually created disk (copy stage3, create user, fstab etc.) from scratch and boot into the system from grub shell. Again here i got a kernel panic with "Atempted to kill init! exitcode=0x00000004". For 0x00000004, i again found some "Illegal Instruction" issue (this is for ARM cpu, but i guess the kernel exception code 0x00000004 will be same for all architectures on illegal instructions): https://stackoverflow.com/questions/54303119/kernel-panic-with-exitcode-0x00000004-after-init I found several reports on that issue here: https://bugs.funtoo.org/browse/FL-5730?jql=text ~ "westmere" https://bugs.funtoo.org/browse/FL-6327 https://bugs.funtoo.org/browse/FL-5730 all have something to do with lack of instructions (eg. aes,sse4_x) on lower end cpus. The actual westmere stage states in the build info that it is compiled with aes, sse4_x instructions. My P6200 definitly does not support it. cpuid2cpuflags gives me this: CPU_FLAGS_X86: mmx mmxext popcnt sse sse2 sse3 ssse3 lscpu flags info also does not include any aes or sse4_x instructions So the question here is: What stage should i use to get best performance results on my P6200 cpu? The last comment from drobbins here says that one should use the intel64-nehalem stage3: https://bugs.funtoo.org/browse/FL-5730 But having a look at the flags also show aes and sse4_x flags:' https://build.funtoo.org/next/x86-64bit/intel64-nehalem/2023-01-30/build-info.json So the question already asked in the title is: What stage3 to use for Pentium 6200 (westmere) to get best performance results? As a very, very new Funtoo user i didnt expect all these obstacles, but hey, if its too easy, its not fun 🙂 Thanks in advance K.

Manually set up the box as suggeted by lego12239 Starting from Grub (kernel and initramfs loaded successfully), leads to a kernel panik of sort "Atempted to kill init! exitcode=0x00000004". The exception is similar to this one here: https://stackoverflow.com/questions/54303119/kernel-panic-with-exitcode-0x00000004-after-init As said before, the Generic64 gnome stage3 works fine! Kinda frustrating 😕

Now did try a generic64 stage3 build and it works fine. Installation did succed without any problems. Well, i guess the build for the stage3 https://build.funtoo.org/next/x86-64bit/intel64-westmere/ really has some compiled binaries with instructions my cpu doesnt know. The P6200 is a westmere, at least it qualifies as one within the funtoo cpu database. cpuid2cpuflags gives me this: CPU_FLAGS_X86: mmx mmxext popcnt sse sse2 sse3 ssse3

I manually tried to chroot into the environment by running this series of commands from the Install Tutorial: root # cd /mnt/funtoo root # mount --rbind /proc proc root # mount --rbind /sys sys root # mount --rbind /dev dev root # cp /etc/resolv.conf /mnt/funtoo/etc/ root # chroot . /bin/su --login The last line "chroot . /bin/su --login" greets me with a "Illegal Instruction" 🤔 Possibly a executable with some unsupported opcode compiled into?