These are all the BIOS options @brahma
you have also a fly problem haha 
in the bios under advanced options, what is the operating mode option?
ok, test with windows, if it has also issues it probably is a hardware problem…
@brahma I’ve installed windows 10 and after updating the system to download graphic drivers I’ve got this error windows unexpected kernel mode trap So looks like something is failing on the hardware 
it really looks like a hardware problem…
were you overclocking your cpu/gpu?
check this link and follow the steps number: 1,3,5,6…
I think I didn’t overclock it… Regarding to operating mode options are: silent mode and performance mode
so if you didnt overclock it, its probably a hardware issue… maybe the overheating that you mentioned damaged something…
I believe so, but that happened at mid July and it failed after the system update bug I faced. So that’s why I’m a bit confused about this stuff 
Do you think is better to purchase another computer in the meanwhile or try to repair this one?
Depends what is broken, perhaps just replace the broken parts cheaper.
maybe purchase another AMD replacement?
you could get it serviced for some diagnostics, tell them that the gpu is probably broken, and what the options are, before buying a new pc…
that would be the best if you could just replace the amd, but since its a notebook, it will probably be integrated into the motherboard…
Hi,
Just an additional test you can do :
Fully disconnect your battery for a few minutes to see if this resets some hardware chips that would be stuck in a wrong status
To elaborate a bit further on this,
I have an old Thomson Tablet PC from 2015-2016 more or less, basically a cheap copy of the Asus T100.
The tablet came in with a dual boot Windows 8 / Android 4.
The Windows 8 part was upgraded to Windows 10 and I used it for some years before it became impossible to run it with 2gb of RAM only and 17Gb of reserved hard disk space.
I then dedcided to move to Manjaro XFCE.
Before that, I made a Clonezilla copy of the Win10/Android disk.
I installed Manjaro 64bit with a 32bit UEFI grub, configured everything, corrected the autorotation initiallly not working, install all the apps I like… as all of this is quite time-consuming, I decided to made another Clonezilla copy of this fully functional system to have some sort of backup easy to go to in case of problem…
Then, for fun, I decided to check if my Clonezilla copy of Win10/Android was working. So i restored it and everything was ok.
After that, quite happy, I restored the Clonezilla copy of the fully configured and functional Manjaro but…
I had no more sound, blutooth, touchscreen, rotation…
Even when starting a live Manjaro XFCE session from a USB key, I had the same issue !
However, the touchscreen was functional in the Bios… so it was not a hardware problem but somehow, the hardware was hiding the presence of some components to the operating system on boot.
For this reason, I decided to open the beast in order to reset all bios power/parameters.
I did not find any CMOS battery as the tablet is using directly the main battery to keep the bios parameters, date and time… alive.
So I disconnected the main battery for a while, reconnected it and restarted under a live Manjaro session.
Now, the touchscreen was back !
After rebuilding the kernels and inputting the proper bios settings, my Manjaro Clonezilla copy was fully functional again (writing this post from within now).
So, it may be worth a try before you discard it or bring it to a repair shop…
Hope it helps,
Multiple Edits : typo/spelling corrections…
1 Like
Hello everybody, I’ve just purchased a second hand laptop, slimbook pro14, same as the one I have but smaller.
I’ve just moved my old NVMe and the 2 32GBM RAM to the new laptop and I’ve booted a live USB to fix some EFI issue trying to load windows instead of manjaro (I believe something I made wrong when I tested adding the other NVMe and installing there windows as suggested by @brahma )
Anyways, I"ve reinstalled EFI as I’ve followed this guide.
Once OS has started I’ve executed this to check the GPU and I’ve got this log:
sudo journalctl -b0 -p4 | grep 'amdgpu'
[sudo] password for urko:
nov 27 22:33:10 urko kernel: amdgpu 0000:04:00.0: amdgpu: psp gfx command LOAD_TA(0x1) failed and response status is (0x7)
nov 27 22:33:10 urko kernel: amdgpu 0000:04:00.0: amdgpu: psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4)
nov 27 22:33:10 urko kernel: amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
nov 27 22:33:10 urko kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
there is this old patch ,
https://lists.freedesktop.org/archives/amd-gfx/2023-May/093287.html
may be others versions psp 10.0 need these point
those secure display logs are related to a new feature implemented by amd… here is more info on what it is:
you should ignore them… it may be fixed in some future update…
1 Like