Dmesg output showing amdgpu

Ask Fedora
1

Hello,

I am not running Fedora KDE 52, no more Kinoite (at the moment).

Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.16.7-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics
Memory: 16 GiB of RAM (14,8 GiB usable)
Graphics Processor 1: AMD Radeon 680M
Graphics Processor 2: NVIDIA GeForce RTX 3060 Laptop GPU
Manufacturer: LENOVO
Product Name: 82RG
System Version: Legion 5 Pro 16ARH7H

Since I still have problems copying/moving files from the laptop to my nas, where the system freezes although the data transfer continues, I was looking at journalctl and dmesg outputs. I saw something in dmesg and re-started it filtering out all the lines with amdgpu in it. This is the result:

 User jan @ Server Fedora-KDE-Lenovo in Folder ~ : Sat Sep 20 - 10:04:35
$ sudo dmesg --time-format ctime | grep amdgpu
[Sat Sep 20 06:53:24 2025] [drm] amdgpu kernel modesetting enabled.
[Sat Sep 20 06:53:24 2025] amdgpu: vga_switcheroo: detected switching method \_SB_.PCI0.GP17.VGA_.ATPX handle
[Sat Sep 20 06:53:24 2025] amdgpu: ATPX version 1, functions 0x00000001
[Sat Sep 20 06:53:24 2025] amdgpu: ATPX Hybrid Graphics
[Sat Sep 20 06:53:24 2025] amdgpu: Virtual CRAT table created for CPU
[Sat Sep 20 06:53:24 2025] amdgpu: Topology: Add CPU node
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: enabling device (0006 -> 0007)
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: detected ip block number 0 <nv_common>
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: detected ip block number 1 <gmc_v10_0>
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: detected ip block number 2 <navi10_ih>
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: detected ip block number 3 <psp>
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: detected ip block number 4 <smu>
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: detected ip block number 5 <dm>
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: detected ip block number 6 <gfx_v10_0>
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: detected ip block number 7 <sdma_v5_2>
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: detected ip block number 8 <vcn_v3_0>
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: detected ip block number 9 <jpeg_v3_0>
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: Fetched VBIOS from VFCT
[Sat Sep 20 06:53:24 2025] amdgpu: ATOM BIOS: 113-REMBRANDT-X37
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: vgaarb: deactivate vga console
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used)
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
[Sat Sep 20 06:53:24 2025] [drm] amdgpu: 512M of VRAM memory ready
[Sat Sep 20 06:53:24 2025] [drm] amdgpu: 7578M of GTT memory ready.
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: [drm] Loading DMUB firmware via PSP: version=0x04000045
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: Found VCN firmware Version ENC: 1.33 DEC: 4 VEP: 0 Revision: 3
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: reserve 0xa00000 from 0xf41e000000 for PSP TMR
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: RAS: optional ras ta ucode is not available
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: RAP: optional rap ta ucode is not available
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: SECUREDISPLAY: optional securedisplay ta ucode is not available
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: SMU is initialized successfully!
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: [drm] Display Core v3.2.334 initialized on DCN 3.1
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: [drm] DP-HDMI FRL PCON supported
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x04000045
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: [drm] Using ACPI provided EDID for eDP-1
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: [drm] PSR support 0, DC PSR ver -1, sink PSR ver 0 DPCD caps 0x20 su_y_granularity 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: [drm] PSR support 0, DC PSR ver -1, sink PSR ver 0 DPCD caps 0x0 su_y_granularity 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: [drm] PSR support 0, DC PSR ver -1, sink PSR ver 0 DPCD caps 0x0 su_y_granularity 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: [drm] PSR support 0, DC PSR ver -1, sink PSR ver 0 DPCD caps 0x0 su_y_granularity 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: [drm] PSR support 0, DC PSR ver -1, sink PSR ver 0 DPCD caps 0x0 su_y_granularity 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: [drm] PSR support 0, DC PSR ver -1, sink PSR ver 0 DPCD caps 0x0 su_y_granularity 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: [drm] PSR support 0, DC PSR ver -1, sink PSR ver 0 DPCD caps 0x0 su_y_granularity 0
[Sat Sep 20 06:53:24 2025] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[Sat Sep 20 06:53:24 2025] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
[Sat Sep 20 06:53:24 2025] amdgpu: Virtual CRAT table created for GPU
[Sat Sep 20 06:53:24 2025] amdgpu: Topology: Add dGPU node [0x1681:0x1002]
[Sat Sep 20 06:53:24 2025] kfd kfd: amdgpu: added device 1002:1681
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: SE 1, SH per SE 2, CU per SH 6, active_cu_number 12
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: Runtime PM not available
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: amdgpu: [drm] Using custom brightness curve
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: [drm] Registered 4 planes with drm panic
[Sat Sep 20 06:53:24 2025] [drm] Initialized amdgpu 3.64.0 for 0000:34:00.0 on minor 1
[Sat Sep 20 06:53:24 2025] fbcon: amdgpudrmfb (fb0) is primary device
[Sat Sep 20 06:53:24 2025] amdgpu 0000:34:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[Sat Sep 20 06:53:26 2025] snd_hda_intel 0000:34:00.1: bound 0000:34:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[Sat Sep 20 07:07:28 2025] amdgpu 0000:34:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32786)
[Sat Sep 20 07:07:28 2025] amdgpu 0000:34:00.0: amdgpu:  in process brave pid 3643 thread brave:cs0 pid 3684
[Sat Sep 20 07:07:28 2025] amdgpu 0000:34:00.0: amdgpu:   in page starting at address 0x00004000ff000000 from client 0x1b (UTCL2)
[Sat Sep 20 07:07:28 2025] amdgpu 0000:34:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501431
[Sat Sep 20 07:07:28 2025] amdgpu 0000:34:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
[Sat Sep 20 07:07:28 2025] amdgpu 0000:34:00.0: amdgpu:          MORE_FAULTS: 0x1
[Sat Sep 20 07:07:28 2025] amdgpu 0000:34:00.0: amdgpu:          WALKER_ERROR: 0x0
[Sat Sep 20 07:07:28 2025] amdgpu 0000:34:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
[Sat Sep 20 07:07:28 2025] amdgpu 0000:34:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Sat Sep 20 07:07:28 2025] amdgpu 0000:34:00.0: amdgpu:          RW: 0x0
[Sat Sep 20 07:07:28 2025] amdgpu 0000:34:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32786)
[Sat Sep 20 07:07:28 2025] amdgpu 0000:34:00.0: amdgpu:  in process brave pid 3643 thread brave:cs0 pid 3684
[Sat Sep 20 07:07:28 2025] amdgpu 0000:34:00.0: amdgpu:   in page starting at address 0x00004000ff000000 from client 0x1b (UTCL2)
[Sat Sep 20 07:07:38 2025] amdgpu 0000:34:00.0: amdgpu: Dumping IP State
[Sat Sep 20 07:07:38 2025] amdgpu 0000:34:00.0: amdgpu: Dumping IP State Completed
[Sat Sep 20 07:07:38 2025] amdgpu 0000:34:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
[Sat Sep 20 07:07:38 2025] amdgpu 0000:34:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
[Sat Sep 20 07:07:38 2025] amdgpu 0000:34:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[Sat Sep 20 07:07:38 2025] amdgpu 0000:34:00.0: amdgpu: Dumping IP State
[Sat Sep 20 07:07:38 2025] amdgpu 0000:34:00.0: amdgpu: Dumping IP State Completed
[Sat Sep 20 07:07:38 2025] amdgpu 0000:34:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
[Sat Sep 20 07:07:38 2025] amdgpu 0000:34:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
[Sat Sep 20 07:07:38 2025] amdgpu 0000:34:00.0: amdgpu: ring gfx_0.1.0 timeout, but soft recovered
[Sat Sep 20 07:13:09 2025] amdgpu 0000:34:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32786)
[Sat Sep 20 07:13:09 2025] amdgpu 0000:34:00.0: amdgpu:  in process brave pid 3643 thread brave:cs0 pid 3684
[Sat Sep 20 07:13:09 2025] amdgpu 0000:34:00.0: amdgpu:   in page starting at address 0x00008000ff000000 from client 0x1b (UTCL2)
[Sat Sep 20 07:13:09 2025] amdgpu 0000:34:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501431
[Sat Sep 20 07:13:09 2025] amdgpu 0000:34:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
[Sat Sep 20 07:13:09 2025] amdgpu 0000:34:00.0: amdgpu:          MORE_FAULTS: 0x1
[Sat Sep 20 07:13:09 2025] amdgpu 0000:34:00.0: amdgpu:          WALKER_ERROR: 0x0
[Sat Sep 20 07:13:09 2025] amdgpu 0000:34:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
[Sat Sep 20 07:13:09 2025] amdgpu 0000:34:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Sat Sep 20 07:13:09 2025] amdgpu 0000:34:00.0: amdgpu:          RW: 0x0
[Sat Sep 20 07:13:09 2025] amdgpu 0000:34:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32786)
[Sat Sep 20 07:13:09 2025] amdgpu 0000:34:00.0: amdgpu:  in process brave pid 3643 thread brave:cs0 pid 3684
[Sat Sep 20 07:13:09 2025] amdgpu 0000:34:00.0: amdgpu:   in page starting at address 0x00008000ff000000 from client 0x1b (UTCL2)
[Sat Sep 20 07:13:19 2025] amdgpu 0000:34:00.0: amdgpu: Dumping IP State
[Sat Sep 20 07:13:19 2025] amdgpu 0000:34:00.0: amdgpu: Dumping IP State Completed
[Sat Sep 20 07:13:19 2025] amdgpu 0000:34:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
[Sat Sep 20 07:13:19 2025] amdgpu 0000:34:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
[Sat Sep 20 07:13:19 2025] amdgpu 0000:34:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[Sat Sep 20 07:13:19 2025] amdgpu 0000:34:00.0: amdgpu: Dumping IP State
[Sat Sep 20 07:13:19 2025] amdgpu 0000:34:00.0: amdgpu: Dumping IP State Completed
[Sat Sep 20 07:13:19 2025] amdgpu 0000:34:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
[Sat Sep 20 07:13:19 2025] amdgpu 0000:34:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
[Sat Sep 20 07:13:19 2025] amdgpu 0000:34:00.0: amdgpu: ring gfx_0.1.0 timeout, but soft recovered
[Sat Sep 20 07:16:10 2025] amdgpu 0000:34:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32786)
[Sat Sep 20 07:16:10 2025] amdgpu 0000:34:00.0: amdgpu:  in process brave pid 3643 thread brave:cs0 pid 3684
[Sat Sep 20 07:16:10 2025] amdgpu 0000:34:00.0: amdgpu:   in page starting at address 0x0000000040000000 from client 0x1b (UTCL2)
[Sat Sep 20 07:16:10 2025] amdgpu 0000:34:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501431
[Sat Sep 20 07:16:10 2025] amdgpu 0000:34:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
[Sat Sep 20 07:16:10 2025] amdgpu 0000:34:00.0: amdgpu:          MORE_FAULTS: 0x1
[Sat Sep 20 07:16:10 2025] amdgpu 0000:34:00.0: amdgpu:          WALKER_ERROR: 0x0
[Sat Sep 20 07:16:10 2025] amdgpu 0000:34:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
[Sat Sep 20 07:16:10 2025] amdgpu 0000:34:00.0: amdgpu:          MAPPING_ERROR: 0x0
[Sat Sep 20 07:16:10 2025] amdgpu 0000:34:00.0: amdgpu:          RW: 0x0
[Sat Sep 20 07:16:10 2025] amdgpu 0000:34:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32786)
[Sat Sep 20 07:16:10 2025] amdgpu 0000:34:00.0: amdgpu:  in process brave pid 3643 thread brave:cs0 pid 3684
[Sat Sep 20 07:16:10 2025] amdgpu 0000:34:00.0: amdgpu:   in page starting at address 0x0000000040000000 from client 0x1b (UTCL2)
[Sat Sep 20 07:16:21 2025] amdgpu 0000:34:00.0: amdgpu: Dumping IP State
[Sat Sep 20 07:16:21 2025] amdgpu 0000:34:00.0: amdgpu: Dumping IP State Completed
[Sat Sep 20 07:16:21 2025] amdgpu 0000:34:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
[Sat Sep 20 07:16:21 2025] amdgpu 0000:34:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
[Sat Sep 20 07:16:21 2025] amdgpu 0000:34:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[Sat Sep 20 07:16:21 2025] amdgpu 0000:34:00.0: amdgpu: Dumping IP State
[Sat Sep 20 07:16:21 2025] amdgpu 0000:34:00.0: amdgpu: Dumping IP State Completed
[Sat Sep 20 07:16:21 2025] amdgpu 0000:34:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
[Sat Sep 20 07:16:21 2025] amdgpu 0000:34:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
[Sat Sep 20 07:16:21 2025] amdgpu 0000:34:00.0: amdgpu: ring gfx_0.1.0 timeout, but soft recovered

Not all, but most of the lines are printed in red which I’m guessing is not good.
Is there a way to show the red lines as red here as well to make it easier to separate the good from the bad lines?
I have no idea what the lines mean so I am asking for help. Is something wrong and if so, how can it be fixed?
Thanks.

AMDGPU errors in journal
3
  • brave (browser?) did something some part of amdgpu didn’t handle well
  • PERMISSION_FAULTS: 0x3 led to: ROCm #2766

I’d try setting amdgpu.vm_update_mode=3.

4

It must be my Firefox appreciation day :slight_smile: As for the third time I’m going to say “does it happen with Firefox?”

At the bottom there it days “soft recovery” so not too bad…

And at the top shows you got switcheroo which I found out the other day switches between amd and nvidia when needed. So looks okay to me… lets see what others say.

5

Thanks for your post, but if you don’t mind, can you help me a bit more?
What does
I’d try setting amdgpu.vm_update_mode=3.`
mean? Where do I do that, how do I do that?
I really don’t know. Sorry, but I am just a computer user.

6

I have been using Firefox since I saw your post, although together with Brave and now I don’t see any dmesg messages anymore since 10.34, while it is now 12.58.
Journalctl just goes on and spits out one message after the other, everything which happens is reported, mostly lines in black, some in yellow(ish) and also some in red.

7

With journalctl, it is more verbose than a politician.

If you don’t notice any problems as a user, you can ignore it’s output. Black is completely fine, yellow is maybe something is perfect and red is an error, but errors happen.

Welcome back to ‘regular’ Fedora and Firefox, it’s a great combo.

8

Sorry to disappoint you, but I am not going to use Firefox as my daily browser. Reason: I simply don’t like it. If there would be a Qt version of Firefox then I could give it a chance although I know the outcome already.
No, I just did some things in Firefox just now to see if I would get messages, but no, but also not from Brave.

I’m now fighting with the correct way to setup locales cause sometimes I see message about that. I guess I have a complicated setup. I now have:

LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=nl_NL.UTF-8
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=nl_NL.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=nl_NL.UTF-8
LC_NAME=nl_NL.UTF-8
LC_ADDRESS=nl_NL.UTF-8
LC_TELEPHONE=nl_NL.UTF-8
LC_MEASUREMENT=nl_NL.UTF-8
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

I used the KDE system settings for that, as I always do, but is this the correct way, or do I have to do it somehow in the terminal?
What could it mean that the en_US entries are between quotes and the nl_NL not? When I do locale -a I see all possibilities without quotes.

9

I don’t think it makes a difference. Like in command line, one can put “quotes” around a file name with a space such as “file name.jpg” but if there is no space the quotes are not needed. It’s likely coming from how the lang codes habe been saved in KDE.

If setting your lang works in KDE, use that. If not, set it in terminal. It’s all good.

Don’t worry, I’m not so much a Firefox fanboi! Use what you prefer. My usual rule is if it is in the Fedora or RPM Fusion repos I use it. If not I’d have to really need it.

10

You’ll have to share the error messages, I’ve never see that.

11

When I see them I will send them.
But, the system-settings way is a correct way to set the locales? Or should I use the cli way and maybe do something extra which the settings program doesn’t do?
I did find out that Fedora is doing the cli way differently than what I could find, but I will keep searching. I now have time to look deeper into Linux distro’s because I stopped working in the summer, and since I enjoy doing this I will.

1 Like
12

To answer the side question about the output of locale, here is a quote from the manual page:

Values for variables set in the environment are printed without double quotes, implied values are printed with double quotes.

1 Like
13

Are you sure this wasn’t due to grep?
sudo dmesg --time-format ctime | grep --color=never amdgpu

FYI, you can go kind of nuts with journalctl for things like this.
From man journalctl

When outputting to a tty, lines are colored according to priority: lines of level ERROR and higher are colored red; lines of level WARNING are colored yellow; lines of level NOTICE
are highlighted; lines of level INFO are displayed normally; lines of level DEBUG are colored grey.

To get the kernel output:
journalctl -k

To get the kernel ouptut grepping for amdgpu:
journalctl -k -g amdgpu

note: -k implies the current boot
If you wanted to get the logs from the previous boot:
journalctl -b-1 -k

You can also filter based on the priority with -p

Filter output by message priorities or priority ranges. Takes either a single numeric or textual log level (i.e. between 0/“emerg” and 7/“debug”), or a range of numeric/text log
levels in the form FROM..TO. The log levels are the usual syslog log levels as documented in syslog(3), i.e. “emerg” (0), “alert” (1), “crit” (2), “err” (3), “warning” (4),
“notice” (5), “info” (6), “debug” (7). If a single log level is specified, all messages with this log level or a lower (hence more important) log level are shown. If a range is
specified, all messages within the range are shown, including both the start and the end value of the range. This will add “PRIORITY=” matches for the specified priorities.

journalctl -b0 -p3
would display everything from the current boot that was error(3) or more severe.

journalctl -b-1 -pwarning..debug
would display everything from the previous boot that was in the range warning(4) to debug(7)

You can also do things based on time with --since and --until.
journalctl -perr --since=-24h
Would display everything from the last 24 hours that was error(3) or more severe.

If you’re copy/pasting for support or using a pastebin I’d suggest using the --no-pager and --no-hostname options

ref: journalctl