Re: [gentoo-user] Getting WiFi to work
On 09.04.24 15:23, Peter Humphrey wrote: Hello list, I want to move my Intel i5 NUC box to a place where Ethernet is not available, nor like to become so. That means I have to get WiFi working, but I've had no success so far. The wiki pages are many, confusing and contradictory, so I'd like the panel's advice on the way to proceed. The first thing I tried was the traditional wpa_supplicant, which seemed to go well - except that I couldn't get the link out of the DOWN state. Then I tried NetworkManager, and failed with that too. This is the hardware: # lspci -v -s 00:14.3 00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi WiFi (rev 01) --->8 Kernel driver in use: iwlwifi Kernel modules: iwlwifi And this is dmesg: $ dmesg | grep -i wifi [1.622343] Intel(R) Wireless WiFi driver for Linux [1.622432] iwlwifi :00:14.3: enabling device ( -> 0002) [1.625069] iwlwifi :00:14.3: Detected crf-id 0x400410, cnv-id 0x80400 wfpm id 0x8020 [1.625121] iwlwifi :00:14.3: PCI dev 51f1/0094, rev=0x370, rfid=0x2010d000 [1.625313] Loading firmware: iwlwifi-so-a0-gf-a0-86.ucode [1.626644] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41 [1.626902] iwlwifi :00:14.3: loaded firmware version 86.fb5c9aeb.0 so- a0-gf-a0-86.ucode op_mode iwlmvm [1.643426] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz, REV=0x370 [1.651382] iwlwifi :00:14.3: WRT: Invalid buffer destination [1.809375] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20 [1.809385] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f [1.809394] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x90 [1.809401] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0 [1.809403] Loading firmware: iwlwifi-so-a0-gf-a0.pnvm [1.810724] iwlwifi :00:14.3: loaded PNVM version e28bb9d7 [1.810817] iwlwifi :00:14.3: RFIm is deactivated, reason = 4 [1.825831] iwlwifi :00:14.3: Detected RF GF, rfid=0x2010d000 [1.897387] iwlwifi :00:14.3: base HW address: f4:6d:3f:2a:33:3e Would net-wireless/iwd get me a bit further? Meanwhile, I'll keep on exploring with the results of sys-apps/hw-probe. Hey Peter This might be the wrong firmware being loaded. Are you building your the iwlwifi driver not as a module but directly into the kernel? Are you including your firmware into the kernel? If you do the above, try loading the driver as a module. Also enable both DVM and MVM Firmware support. Then emerge sys-kernel/linux-firmware without USE=savedconfig. Finally reboot and check wther it works. If it works, check which firmware is loaded in your dmesg.
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
Hey Michael Thank you for helping me. I have finally solved the issue by upgrading to kernel 6.8.4, see this: https://forums.gentoo.org/viewtopic-t-1168150.html Have a very nice week! Regards Nanderty
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On 05.04.24 08:31, Paul Sopka wrote: On 05.04.24 00:55, Michael wrote: Your toolchain is now correct. Can you show the output of: equery u media-libs/libjpeg-turbo and emerge --info media-libs/libjpeg-turbo However, it could be this is a bug, you can check here for reports: https://bugs.gentoo.org/buglist.cgi?quicksearch=media-libs%2Flibjpeg-turbo If this is the only package you're getting a problem with, you can run: emerge --resume --skipfirst to complete your migration to profile 23.0, then try again to emerge libjpeg- turbo on its own. Also one or two weeks ago I successfully emerged with emptytree after migrating to profile 23.0.
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On 05.04.24 00:55, Michael wrote: Your toolchain is now correct. Can you show the output of: equery u media-libs/libjpeg-turbo and emerge --info media-libs/libjpeg-turbo However, it could be this is a bug, you can check here for reports: https://bugs.gentoo.org/buglist.cgi?quicksearch=media-libs%2Flibjpeg-turbo If this is the only package you're getting a problem with, you can run: emerge --resume --skipfirst to complete your migration to profile 23.0, then try again to emerge libjpeg- turbo on its own. Unfortunately I have this issue with many packages. I can confirm it with media-libs/libjpeg-turbo: * Found these USE flags for media-libs/libjpeg-turbo-3.0.2: U I + + abi_x86_32 : 32-bit (x86) libraries - - java : Add support for Java - - static-libs : Build static versions of dynamic libraries as well and dev-util/vulkan-headers as well as sci-libs/netcdf: * Found these USE flags for sci-libs/netcdf-4.9.2-r1: U I - - blosc : Allow using blosc compression via dev-libs/c-blosc + + bzip2 : Enable bzip2 compression support + - dap : Support for remote data access with the built-in OPeNDAP client - - doc : Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally - - examples : Install examples, usually source code - - hdf : Build with HDF4 read capability(sci-libs/hdf, sci-libs/hdf5 and sys-libs/zlib required). + - hdf5 : Add support for the Hierarchical Data Format v5 - - mpi : Add MPI (Message Passing Interface) layer to the apps that support it - - szip : Use the szip compression library - - test : Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently) + + zstd : Enable support for ZSTD compression My emerge --info media-libs/libjpeg-turbo: Portage 3.0.63 (python 3.11.8-final-0, default/linux/amd64/23.0, gcc-13, glibc-2.39-r2, 6.8.2-gentoo x86_64) = System Settings = System uname: Linux-6.8.2-gentoo-x86_64-13th_Gen_Intel-R-_Core-TM-_i5-13600KF-with-glibc2.39 KiB Mem: 32699852 total, 27956992 free KiB Swap: 0 total, 0 free Timestamp of repository gentoo: Thu, 04 Apr 2024 18:19:20 + Head commit of repository gentoo: 45b6803c7d0c2f6e0bbb7247385e9a3095dc172b Timestamp of repository guru: Thu, 04 Apr 2024 17:48:38 + Head commit of repository guru: ae5669fdb3157526d19cdfab0661a2719f00170b Timestamp of repository steam-overlay: Thu, 04 Apr 2024 01:22:27 + Head commit of repository steam-overlay: aca6eb772e0d5474b6d44072998af0082f36d08a Timestamp of repository wayland-desktop: Thu, 04 Apr 2024 01:22:35 + Head commit of repository wayland-desktop: 559692d775352c785aecfec52d940f20f5c9b800 sh dash 0.5.12 ld GNU ld (Gentoo 2.42 p3) 2.42.0 app-misc/pax-utils: 1.3.7::gentoo app-shells/bash: 5.2_p26::gentoo dev-build/autoconf: 2.13-r8::gentoo, 2.72-r1::gentoo dev-build/automake: 1.16.5-r2::gentoo dev-build/cmake: 3.29.0::gentoo dev-build/libtool: 2.4.7-r4::gentoo dev-build/make: 4.4.1-r1::gentoo dev-build/meson: 1.4.0-r1::gentoo dev-java/java-config: 2.3.3-r1::gentoo dev-lang/perl: 5.38.2-r2::gentoo dev-lang/python: 3.11.8_p1::gentoo, 3.12.2_p1::gentoo dev-lang/rust-bin: 1.76.0::gentoo sys-apps/baselayout: 2.15::gentoo sys-apps/openrc: 0.53.1::gentoo sys-apps/sandbox: 2.38::gentoo sys-devel/binutils: 2.42-r1::gentoo sys-devel/binutils-config: 5.5::gentoo sys-devel/clang: 17.0.6::gentoo, 18.1.2::gentoo sys-devel/gcc: 13.2.1_p20240210::gentoo sys-devel/gcc-config: 2.11::gentoo sys-devel/lld: 17.0.6::gentoo sys-devel/llvm: 17.0.6::gentoo, 18.1.2::gentoo sys-kernel/linux-headers: 6.8-r1::gentoo (virtual/os-headers) sys-libs/glibc: 2.39-r2::gentoo Repositories: gentoo location: /var/db/repos/gentoo sync-type: git sync-uri: https://github.com/gentoo-mirror/gentoo.git priority: -1000 volatile: False guru location: /var/db/repos/guru sync-type: git sync-uri: https://github.com/gentoo-mirror/guru.git masters: gentoo volatile: False steam-overlay location: /var/db/repos/steam-overlay sync-type: git sync-uri: https://github.com/gentoo-mirror/steam-overlay.git masters: gentoo volatile: False wayland-desktop location: /var/db/repos/wayland-desktop sync-type: git sync-uri: https://github.com/gentoo-mirror/wayland-desktop.git masters: gentoo volatile: False crossdev location: /var/db/repos/crossdev masters: gentoo priority: 10 volatile: False Binary Repositories: gentoobinhost priority: 1 sync-uri:
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On 04.04.24 00:44, Michael wrote: No, this is not normal. I wonder if your make.conf settings are correct. Start with some safe CFLAGS as suggested here: https://wiki.gentoo.org/wiki/Safe_CFLAGS Then use the package 'app-portage/cpuid2cpuflags' to set the correct CPU flags: https://wiki.gentoo.org/wiki/CPU_FLAGS_* At this point you should be able to use gcc with no further problems. You can try to optimise your settings further by taking a look at suggestions here: https://wiki.gentoo.org/wiki/GCC_optimization A little correction, even though the "-march=" change removed the warning gcc threw, it unfortunately didn't solve the issue. I just recompiled dev-lang/nasm, and after that recompiled libjpeg-turbo, and I have the same hang on "Detecting C compiler ABI info" again. Good night Nanderty
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On 04.04.24 00:44, Michael wrote: No, this is not normal. I wonder if your make.conf settings are correct. Start with some safe CFLAGS as suggested here: https://wiki.gentoo.org/wiki/Safe_CFLAGS Then use the package 'app-portage/cpuid2cpuflags' to set the correct CPU flags: https://wiki.gentoo.org/wiki/CPU_FLAGS_* At this point you should be able to use gcc with no further problems. You can try to optimise your settings further by taking a look at suggestions here: https://wiki.gentoo.org/wiki/GCC_optimization Thank you for pointing into the right direction. After changing -march=raptorlake to -march=alderlake on an i5-13600KS and running the following three times: In case you haven't done it yet, if you rebuild the toolchain things should hopefully self-correct on your system: emerge --sync emerge -1av sys-devel/binutils emerge -1av --nodeps sys-devel/gcc Use 'gcc-config -l' to check you are using the correct gcc version. emerge -1av sys-libs/glibc emerge -1av dev-build/libtool env-update && source /etc/profile I don't get the hang at "-- Detecting C compiler ABI info" anymore. It now hangs later on "-- Looking for a ASM_NASM compiler". My CPU_FLAGS_* are correct, I checked them with app-portage/cpuid2cpuflags to make sure they are up to date and they were. Do you have any idea for this? Thank you Nanderty
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On 03.04.24 09:40, Michael wrote: In case you haven't done it yet, if you rebuild the toolchain things should hopefully self-correct on your system: emerge --sync emerge -1av sys-devel/binutils emerge -1av --nodeps sys-devel/gcc Use 'gcc-config -l' to check you are using the correct gcc version. emerge -1av sys-libs/glibc emerge -1av dev-build/libtool env-update && source /etc/profile Good evening Michael Thank you for your suggestions, I tried them, but unfortunately it didn't help. Also, i found out that removing CPU_FLAGS_X86 made the issue disappear, but another issue appeared later. I experience a similar hang, at "-- Looking for a ASM_NASM compiler". Further, compiling GCC throws the following warnings: * QA Notice: Installing libtool files (.la) without corresponding static libraries! * /usr/libexec/gcc/x86_64-pc-linux-gnu/13/liblto_plugin.la * QA Notice: Found the following implicit function declarations in configure logs: * /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/32/libgfortran/config.log:4628 - fpsetmask * /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-gnu/libgfortran/config.log:4536 - fpsetmask * Check that no features were accidentally disabled. * See https://wiki.gentoo.org/wiki/Modern_C_porting. * QA Notice: Package triggers severe warnings which indicate that it * may exhibit random runtime failures. * /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec.h:316: warning: ‘free’ called on unallocated object ‘accesses’ [-Wfree-nonheap-object] * /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec.h:316:10: warning: ‘free’ called on unallocated object ‘dest_bbs’ [-Wfree-nonheap-object] * /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec.h:316: warning: ‘free’ called on unallocated object ‘accesses’ [-Wfree-nonheap-object] * /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/gcc/vec.h:316:10: warning: ‘free’ called on unallocated object ‘dest_bbs’ [-Wfree-nonheap-object] * /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/libsanitizer/hwasan/hwasan.cpp:539:52: warning: format ‘%zd’ expects a matching ‘signed size_t’ argument [-Wformat=] * Please do not file a Gentoo bug and instead report the above QA * issues directly to the upstream developers of this software. * Homepage: https://gcc.gnu.org/ Is this normal? Hope you all have a nice evening Nanderty
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On 02.04.24 21:43, Paul Sopka wrote: On 02.04.24 20:50, J. Roeleveld wrote: Did you upgrade GCC recently? If yes, did you follow the gcc-upgrade guide: https://wiki.gentoo.org/wiki/Upgrading_GCC ? -- Joost Thank you for your answer Joost. As far as I know, I didn't upgrade GCC recently. I just rebuilt libtool to be sure, but that didn't help. Nanderty I rebuilt with emptytree over night from tty. The system didn't crash, but it hung up at the first program to use this, media-libs/libjpeg-turbo.
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
On 02.04.24 20:50, J. Roeleveld wrote: Did you upgrade GCC recently? If yes, did you follow the gcc-upgrade guide: https://wiki.gentoo.org/wiki/Upgrading_GCC ? -- Joost Thank you for your answer Joost. As far as I know, I didn't upgrade GCC recently. I just rebuilt libtool to be sure, but that didn't help. Nanderty
[gentoo-user] System crash on "Detecting C compiler ABI info"
Hello Gentoo, my entire system crashes reliably on "Detecting C compiler ABI info" when compiling some packages, happened on sci-libs/netcdf and media-libs/svt-av1. I am pretty sure it isn't a hardware instability since I can compile everything that doesn't run "Detecting C compiler ABI info" without any issues at all. Does anybody have an idea why this happens? I wish you all a nice afternoon! Nanderty
Re: [gentoo-user] Issues with amdgpu driver: Compositor hangs, sysfs not working
AMDGPU-PRO is not a driver, but a set of libraries containing opencl,vulkan and advanced media framework. It operates on top of amdgpu. Mesa is the open source implementation of OpenGL, Vulkan, et al. graphics API specifications. If you are using proprietary AMD drivers then I understand all the graphics API instructions will go through these proprietary drivers, instead of being translated by Mesa. As you said, it could be seen as an alternative to mesa, but will not change anything about the firmware or the amdgpu driver. It therefore will not change anything about the framebuffer, since this is handled by the driver. That said, I do not have the described problems when starting gamescope from a tty, so my guess now is that its a Hyprland issue. I filed a bug there. I will also try to start Hyprland using amdgpu-pro instead of mesa. Thank you for your time
Re: [gentoo-user] Issues with amdgpu driver: Compositor hangs, sysfs not working
Thank you for your reply. Hello everybody, I installed an AMD Radeon RX 7900 XTX today, switching from Nvidia. But once I enable FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y to have a tty once the driver is up, the following happens: 1) My Wayland compositor (Hyprland) takes very long to start. 2) reading from sysfs (e.g. running "cat /sys/class/drm/card0/device/gpu_busy_percent") does not work and causes a hang. Once I disable FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=n, I have no issues with the starting speed of the compositors at all and the mentioned command works. But this leads to a black tty. You'd normally need this enabled to get a fb display on the console, but I don't know if this would be provided by proprietary drivers instead for your card - see below. I made a mistake here, sorry. The issue causing setting is DRM_FBDEV_EMULATION=y, which on itself works with the open source driver, but causes issues as soon as I start Hyprland. It could be both. I don't think there's any Linux firmware released yet for this card - but I don't follow the latest & greatest so I could be wrong. You'd need the AMD amdgpu-pro on top of the amdgpu driver, to bring in the proprietary OpenGL, OpenCL, Vulkan and AMF components: https://wiki.gentoo.org/wiki/AMDGPU-PRO This is what's in portage today: ~ $ eix -l amdgpu-pro * dev-libs/amdgpu-pro-opencl Available versions: ~20.40.1147286 ^fmsd[ABI_X86="32 64"] ["|| ( abi_x86_32 abi_x86_64 )"] Homepage: https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-20-40 Description: Proprietary OpenCL implementation for AMD GPUs * media-libs/amdgpu-pro-vulkan Available versions: ~21.50.2.1384496-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~22.10.4.1452060-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~22.20.5.1511376-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~22.40.6.1580631-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~23.10.3.1620044-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~23.20.0.1654522-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] Homepage:https://www.amd.com/en/support Description: AMD's closed source vulkan driver, from Radeon Software for Linux * media-video/amdgpu-pro-amf Available versions: ~1.4.24.1452059 ^md ~1.4.26.1511376 ^md ~1.4.29.1580631 ^md ~1.4.30.1620044 ^md ~1.4.31.1654522 (0/31)^md Homepage:https://www.amd.com/en/support Description: AMD's closed source Advanced Media Framework (AMF) driver Found 3 matches The firmare seems good, since it is loaded just fine, "dmesg | grep amdgpu | grep firmware" returns: [ 16.905914] Loading firmware: amdgpu/psp_13_0_0_sos.bin [ 16.905916] Loading firmware: amdgpu/psp_13_0_0_ta.bin [ 16.905917] Loading firmware: amdgpu/smu_13_0_0.bin [ 16.905917] Loading firmware: amdgpu/dcn_3_2_0_dmcub.bin [ 16.905918] Loading firmware: amdgpu/gc_11_0_0_pfp.bin [ 16.905919] Loading firmware: amdgpu/gc_11_0_0_me.bin [ 16.905919] Loading firmware: amdgpu/gc_11_0_0_rlc.bin [ 16.905920] Loading firmware: amdgpu/gc_11_0_0_mec.bin [ 16.905921] Loading firmware: amdgpu/gc_11_0_0_imu.bin [ 16.905922] Loading firmware: amdgpu/sdma_6_0_0.bin [ 16.905923] Loading firmware: amdgpu/vcn_4_0_0.bin [ 16.906095] Loading firmware: amdgpu/gc_11_0_0_mes_2.bin [ 16.906096] Loading firmware: amdgpu/gc_11_0_0_mes1.bin [ 16.906496] amdgpu :03:00.0: amdgpu: Will use PSP to load VCN firmware Also the mesa libraries work just fine, if I disable DRM_FBDEV_EMULATION=n, I just get a black tty, but Hyprland starts and I can play games with the expected performance.
[gentoo-user] Issues with amdgpu driver: Compositor hangs, sysfs not working
Hello everybody, I installed an AMD Radeon RX 7900 XTX today, switching from Nvidia. But once I enable FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y to have a tty once the driver is up, the following happens: 1) My Wayland compositor (Hyprland) takes very long to start. 2) reading from sysfs (e.g. running "cat /sys/class/drm/card0/device/gpu_busy_percent") does not work and causes a hang. Once I disable FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=n, I have no issues with the starting speed of the compositors at all and the mentioned command works. But this leads to a black tty. The only two error messages from amdgpu I find in dmesg are: [ 66.757500] amdgpu :03:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x0029 SMN_C2PMSG_82:0x [ 66.757502] amdgpu :03:00.0: amdgpu: Failed to disable gfxoff! and [ 870.087856] amdgpu :03:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x0029 SMN_C2PMSG_82:0x [ 870.087858] amdgpu :03:00.0: amdgpu: Failed to export SMU metrics table! Did I forget anything or is this a bug?
