Mageia forum

Hello,

I just buy a new PC and a new graphic card ASUS Radeon RX 6400 DUAL 4G, I proceed to a fresh install of Mageia 8 on this new PC, the installation run fine, but after that I can't get the system to boot successfully : I always get a black screen and I'm stuck there...

I can start Mageia only if I start it in "recovery mode" : when reaching the password admin step, I do a CTRL+D, and then Plasma launches and I can use Mageia normaly.

I have a multiboot system with Windows 11 and Mageia 8, and the graphic card runs perfectly on Windows 11 with the driver provided by AMD.

I suspect a driver issue.

This is the driver used with Mageia :
Module: ‎Card:AMD Southern Islands and later (amdgpu)

Has somebody encountered the same behaviour ?

Will it be possible that Mageia be compatible with this graphic card in the future ?

Thanx in advance for any suggestion.

You need to activate online sources whilst installation and do a full system update. The RX 6400 release was after Mageia 8 release. So you need a full up to date system to run this card...

Add online sources and perform an update:
https://wiki.mageia.org/en/Install_medi ... _beginners

Hello sturmvogel and thank you.

I had done exactly what you write : I activated the update meanwhile the installation.
But that didn't work :/

ylyco wrote:I can start Mageia only if I start it in "recovery mode" : when reaching the password admin step, I do a CTRL+D, and then Plasma launches and I can use Mageia normaly.

Doesn't really sound like a graphics driver issue - if it would be, you wouldn't be able to start graphical server at all.
After next fresh boot, once you started up plasma, please open a terminal and as root run the following command:

Code: Select all: journalctl -ab > /tmp/journal.log

and later attach the file /tmp/journal.log here.

Also please add the output of

Code: Select all: lspcidrake -v

Thank you Doktor5000 :

Code: Select all: [regis@Asus2022 ~]$ lspcidrake -v unknown : Advanced Micro Devices, Inc. [AMD]|Cezanne Data Fabric; Function 5 [BRIDGE_HOST] (vendor:1022 device:166f) unknown : Advanced Micro Devices, Inc. [AMD]|Device 43ea [BRIDGE_PCI] (vendor:1022 device:43ea) i2c_piix4 : Advanced Micro Devices, Inc. [AMD]|FCH SMBus Controller [SERIAL_SMBUS] (vendor:1022 device:790b subv:1043 subd:87e1) (rev: 51) unknown : Advanced Micro Devices, Inc. [AMD]|Cezanne Data Fabric; Function 7 [BRIDGE_HOST] (vendor:1022 device:1671) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir PCIe Dummy Host Bridge [BRIDGE_HOST] (vendor:1022 device:1632) xhci_pci : Advanced Micro Devices, Inc. [AMD]|500 Series Chipset USB 3.1 XHCI Controller [SERIAL_USB] (vendor:1022 device:43ee subv:1b21 subd:1142) snd_hda_intel : Advanced Micro Devices, Inc. [AMD/ATI]|Renoir Radeon High Definition Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:1002 device:1637 subv:1043 subd:8809) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne PCIe GPP Bridge [BRIDGE_PCI] (vendor:1022 device:1634) unknown : Advanced Micro Devices, Inc. [AMD]|500 Series Chipset Switch Upstream Port [BRIDGE_PCI] (vendor:1022 device:43e9) unknown : Advanced Micro Devices, Inc. [AMD]|Cezanne Data Fabric; Function 0 [BRIDGE_HOST] (vendor:1022 device:166a) unknown : Advanced Micro Devices, Inc. [AMD]|Device 43ea [BRIDGE_PCI] (vendor:1022 device:43ea) xhci_pci : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne USB 3.1 [SERIAL_USB] (vendor:1022 device:1639 subv:1043 subd:87e1) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir PCIe GPP Bridge [BRIDGE_PCI] (vendor:1022 device:1633) unknown : Advanced Micro Devices, Inc. [AMD]|Cezanne Data Fabric; Function 2 [BRIDGE_HOST] (vendor:1022 device:166c) unknown : Advanced Micro Devices, Inc. [AMD]|Cezanne Data Fabric; Function 4 [BRIDGE_HOST] (vendor:1022 device:166e) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir Internal PCIe GPP Bridge to Bus [BRIDGE_PCI] (vendor:1022 device:1635) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne Root Complex [BRIDGE_HOST] (vendor:1022 device:1630 subv:1043 subd:8809) snd_hda_intel : Advanced Micro Devices, Inc. [AMD/ATI]|Navi 21/23 HDMI/DP Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:1002 device:ab28) unknown : Advanced Micro Devices, Inc. [AMD]|Cezanne Data Fabric; Function 6 [BRIDGE_HOST] (vendor:1022 device:1670) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne IOMMU (vendor:1022 device:1631 subv:1043 subd:8809) unknown : Advanced Micro Devices, Inc. [AMD]|Zeppelin/Raven/Raven2 PCIe Dummy Function (vendor:1022 device:145a subv:1043 subd:8809) (rev: c8) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne PCIe GPP Bridge [BRIDGE_PCI] (vendor:1022 device:1634) unknown : Advanced Micro Devices, Inc. [AMD/ATI]|Navi 10 XL Upstream Port of PCI Express Switch [BRIDGE_PCI] (vendor:1002 device:1478) (rev: c7) unknown : Advanced Micro Devices, Inc. [AMD]|500 Series Chipset SATA Controller [STORAGE_SATA] (vendor:1022 device:43eb subv:1b21 subd:1062) unknown : Advanced Micro Devices, Inc. [AMD]|FCH LPC Bridge [BRIDGE_ISA] (vendor:1022 device:790e subv:1043 subd:87e1) (rev: 51) unknown : Advanced Micro Devices, Inc. [AMD]|Device 43ea [BRIDGE_PCI] (vendor:1022 device:43ea) ccp : Advanced Micro Devices, Inc. [AMD]|Family 17h (Models 10h-1fh) Platform Security Processor [CRYPT_OTHER] (vendor:1022 device:15df subv:1043 subd:8809) igc : Intel Corporation|Ethernet Controller I225-V [NETWORK_ETHERNET] (vendor:8086 device:15f3 subv:1043 subd:87d2) (rev: 03) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir PCIe Dummy Host Bridge [BRIDGE_HOST] (vendor:1022 device:1632) unknown : Advanced Micro Devices, Inc. [AMD/ATI]|Navi 10 XL Downstream Port of PCI Express Switch [BRIDGE_PCI] (vendor:1002 device:1479) unknown : Advanced Micro Devices, Inc. [AMD]|Cezanne Data Fabric; Function 1 [BRIDGE_HOST] (vendor:1022 device:166b) xhci_pci : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne USB 3.1 [SERIAL_USB] (vendor:1022 device:1639 subv:1043 subd:87e1) unknown : Sandisk Corp|WD Blue SN570 NVMe SSD (vendor:15b7 device:501a) k10temp : Advanced Micro Devices, Inc. [AMD]|Cezanne Data Fabric; Function 3 [BRIDGE_HOST] (vendor:1022 device:166d) snd_hda_intel : Advanced Micro Devices, Inc. [AMD]|Family 17h/19h HD Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:1022 device:15e3 subv:1043 subd:87c5) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir PCIe Dummy Host Bridge [BRIDGE_HOST] (vendor:1022 device:1632) Card:AMD Southern Islands and later (amdgpu): Advanced Micro Devices, Inc. [AMD/ATI]|Navi 24 [Radeon RX 6400 / 6500 XT] [DISPLAY_VGA] (vendor:1002 device:743f subv:1043 subd:0502) (rev: c7) hub : Linux 5.15.79-desktop-1.mga8 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002) usbhid : AsusTek Computer Inc.|AURA LED Controller [Human Interface Device|No Subclass|None] (vendor:0b05 device:1939) hub : Genesys Logic, Inc.|USB2.0 Hub [Hub|Unused|Full speed (or root) hub] (vendor:05e3 device:0608) hub : ALCOR|Generic USB Hub [Hub|Unused|Full speed (or root) hub] (vendor:058f device:9254) usbhid : Microsoft|Wired Keyboard 600 [Human Interface Device|Boot Interface Subclass|Keyboard] (vendor:045e device:0750) usbhid : HP|HP Wireless Mouse 220 [Human Interface Device|Boot Interface Subclass|Mouse] (vendor:03f0 device:2141) usbhid : Device|2Port KVMSwitcher [Human Interface Device|No Subclass|None] (vendor:10d5 device:55a2) hub : Linux 5.15.79-desktop-1.mga8 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0003) hub : Linux 5.15.79-desktop-1.mga8 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002) hub : Linux 5.15.79-desktop-1.mga8 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0003) hub : Linux 5.15.79-desktop-1.mga8 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002) hub : Linux 5.15.79-desktop-1.mga8 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0003) hid_generic : AsusTek Computer Inc. AURA LED Controller hid_generic : Device 2Port KVMSwitcher hid_generic : Microsoft Wired Keyboard 600 hid_generic : HP HP Wireless Mouse 220 hid_generic : Microsoft Wired Keyboard 600 [regis@Asus2022 ~]$

journal.log: Here is the file; (243.4 KiB) Downloaded 316 times

Well, the journal log doesn't help at all because it doesn't show the issue as you booted in failsafe mode.
Please do the same, but without booting in "rescue mode" as we need to see why it fails during a normal boot.

Hi Doktor5000,
if I run on normal mode, then I can't get the possibility to access to plasma neither the terminal : I can only reboot...

so alfter the black screen session, I pressed Ctrl+Alt+Del and booted on the recovery mode, and then I run the command : journalctl -ab -1 > /tmp/journal.log

I hope this is more usefull ?... with -1 as parameter, I have the previous boot journal session, don't I ?

Here is the new journal file :

journal.log: (162.22 KiB) Downloaded 333 times

Thank you.

ylyco wrote:if I run on normal mode, then I can't get the possibility to access to plasma neither the terminal : I can only reboot...

No, you can also login into a tty, and run the command there. When plasma should have started, then switch to another tty using e.g. Ctrl+Alt+F2
and login there as root. Then run the command as mentioned before, and if you have booted normally later on, attach it here.
The log from after recovery mode does not help at all.

The point is that when I start in normal mode, Plasma can't launch : I get a black screen, and nor CTRL+ALT+F2 (or F3, F4, etc) don't change anything, the screen keeps black and no access is possible to the system.

The only way to have some control is to start in recovery mode : then I can type my root password or the CTRL+ALT+F2 (both work out), or doing a simple CTRL+D launch Plasma.

In normal boot I have a black screen and can't do nothing, only a CTRL+ALT+DEL is possible.

That's the reason why I used this command (with "-1" parameter) :
journalctl -ab -1 > /tmp/journal.log
In order to have the previous journalctl instead of the last one : the last one is create with the recovery mode, and the previous one with the normal mode.
The "-1" parameter is not a good practice ?

I can't access to any command in the system except in recovery mode...

ylyco wrote:In order to have the previous journalctl instead of the last one : the last one is create with the recovery mode, and the previous one with the normal mode.
The "-1" parameter is not a good practice ?

Sorry, overlooked that, yes that also works - will check the log.

Hard to tell why and where something goes wrong, there's not much in the log about display manager starting.
Your network interface gets started, and afterwards seems the system receives your reboot command and then starts to shutdown/reboot.
There are only ~25 seconds between that:

déc. 19 13:42:52 Asus2022 systemd[1]: Started Simple Desktop Display Manager.
[...]
déc. 19 13:42:52 Asus2022 systemd[1]: Reached target Multi-User System.
déc. 19 13:42:52 Asus2022 systemd[1]: Reached target Graphical Interface.
[...]
déc. 19 13:42:56 Asus2022 NET[1764]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf
déc. 19 13:42:56 Asus2022 ifplugd(enp8s0)[1281]: client: Unknown parameter "-r". Use --help for help.
déc. 19 13:42:56 Asus2022 ifplugd(enp8s0)[1281]: client: [ OK ]
déc. 19 13:42:56 Asus2022 ifplugd(enp8s0)[1281]: Program executed successfully.
[...]
déc. 19 13:43:24 Asus2022 systemd[1]: Received SIGINT.
déc. 19 13:43:24 Asus2022 systemd[1]: Removed slice Slice /system/getty.
déc. 19 13:43:24 Asus2022 systemd[1]: Removed slice Slice /system/modprobe.
déc. 19 13:43:24 Asus2022 systemd[1]: Stopped target Graphical Interface.
déc. 19 13:43:24 Asus2022 systemd[1]: Stopped target Multi-User System.
déc. 19 13:43:24 Asus2022 systemd[1]: Stopped target Login Prompts.

How long do you wait when booting up, once bootsplash display finishes, to allow for display manager / plasma to load ?
Also, did you set a proper hostname during installation? What does hostnamectl return when booted normally and in rescue mode, and what do you have in your /etc/hosts ?

The failed start contains:

Code: Select all: déc. 19 13:42:45 Asus2022 kernel: amdgpu 0000:03:00.0: Direct firmware load for amdgpu/beige_goby_sos.bin failed with error -2 déc. 19 13:42:45 Asus2022 kernel: amdgpu 0000:03:00.0: amdgpu: failed to init sos firmware déc. 19 13:42:45 Asus2022 kernel: [drm:psp_sw_init [amdgpu]] *ERROR* Failed to load psp firmware! déc. 19 13:42:45 Asus2022 kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* sw_init of IP block <psp> failed -2 déc. 19 13:42:45 Asus2022 kernel: amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_init failed déc. 19 13:42:45 Asus2022 kernel: amdgpu 0000:03:00.0: amdgpu: Fatal error during GPU init déc. 19 13:42:45 Asus2022 kernel: amdgpu 0000:03:00.0: amdgpu: amdgpu: finishing device. déc. 19 13:42:45 Asus2022 kernel: amdgpu: probe of 0000:03:00.0 failed with error -2 déc. 19 13:42:45 Asus2022 kernel: [drm] amdgpu: ttm finalized

Whereas the first line on a succesfull start is:

Code: Select all: déc. 17 16:16:18 Asus2022 kernel: amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware

How long do you wait when booting up, once bootsplash display finishes, to allow for display manager / plasma to load ?
Also, did you set a proper hostname during installation? What does hostnamectl return when booted normally and in rescue mode, and what do you have in your /etc/hosts ?

Since I press CTRL+D at the boot in recovery mode, when root password or ctrl+d is asked :
I wait 5 seconds to reach the bootsplash.
And from the bootsplash to the desktop ready :
I wait 6 seconds.

Code: Select all: [regis@Asus2022 ~]$ hostnamectl Static hostname: Asus2022 Icon name: computer-desktop Chassis: desktop Machine ID: 8009e3cf2ac44428b59fa0a5f5793588 Boot ID: 8f3195cb92474812a2d7615cebd6de81 Operating System: Mageia 8 Kernel: Linux 5.15.79-desktop-1.mga8 Architecture: x86-64 [regis@Asus2022 ~]$

Code: Select all: [regis@Asus2022 ~]$ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 [regis@Asus2022 ~]$

Thank you both

Good news :
I just update the system, and a new kernel has been installed, and Mageia starts successfully now !

here is the new system :

Code: Select all: [regis@Asus2022 ~]$ hostnamectl Static hostname: Asus2022 Icon name: computer-desktop Chassis: desktop Machine ID: 8009e3cf2ac44428b59fa0a5f5793588 Boot ID: 80d2418c8c354b1999ef5799e3d6becb Operating System: Mageia 8 Kernel: Linux 5.15.82-desktop-1.mga8 Architecture: x86-64 [regis@Asus2022 ~]$

My problem just solved !

I will inform you if the issue comes up again.

Note :
If you have an explanation I will be interested to know what it is...

Thanks guys

Wonderful then

You could dive into the kernel change logs.. there is a loooot to read... https://advisories.mageia.org/MGASA-2022-0477.html

Or maybe your update also included some related firmware?

There were very few packages to update from what I recall, and almost all were related to Kernel.

Mageia forum

[SOLVED] Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

[SOLVED] Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: [SOLVED] Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue

Re: [SOLVED] Mageia8 and ASUS Radeon RX 6400 DUAL 4G issue