New arch install - cant reboot or shutdown pc

DinoNugget1337 · 2023-09-28 22:52:12

Hello,

I just newly installed Arch for the first time and my pc doesn't shut down or reboot. The screen turns black but the power just doesn't shut down so I have to hold the power button for a couple of seconds to power it down. I had a look at the wiki and had a look at similar posts but can't resolve that issue. In other posts I saw them posting their log output of journalctl -b -1 so here is a pastebin to it: https://pastebin.com/Pki0CWi8

I'm quite new to Arch and only used Linux Mint before so let me know if anything else is needed.

OS: Arch Linux x86_64
Host: Z390 AORUS MASTER
Kernel: 6.5.5-273-tkg-bore (happens on default linux kernel as well)
Uptime: 40 mins
Packages: 907 (pacman)
Shell: bash 5.1.16
Resolution: 2560x1440, 1920x1080
DE: Cinnamon 5.8.4
WM: Mutter (Muffin)
Theme: Orchis-Grey-Dark-Compact [GTK2/3]
Icons: ePapirus-Dark [GTK2/3]
Terminal: gnome-terminal
CPU: Intel i9-9900K (16) @ 5.000GHz
GPU: AMD ATI 03:00.0 Device 747e
Memory: 2872MiB / 32013MiB

seth · 2023-09-29 07:08:59

There're no errors in that boot and the system shuts down uninhibited. There's even an almost suspicious absence of ACPI errors.

Sep 29 00:01:23 stoepselArch kernel: ntfs3: sda1: volume is dirty and "force" flag is not set!
Sep 29 00:05:11 stoepselArch kernel: ntfs3: sda1: It is recommened to use chkdsk.
Sep 29 00:05:11 stoepselArch kernel: ntfs3: sda1: volume is dirty and "force" flag is not set!
Sep 29 00:05:14 stoepselArch kernel: ntfs3: sda1: It is recommened to use chkdsk.
Sep 29 00:05:14 stoepselArch kernel: ntfs3: sda1: volume is dirty and "force" flag is not set!
Sep 29 00:06:12 stoepselArch kernel: ntfs3: sda1: It is recommened to use chkdsk.
Sep 29 00:06:12 stoepselArch kernel: ntfs3: sda1: volume is dirty and "force" flag is not set!
Sep 29 00:07:41 stoepselArch kernel: ntfs3: sda1: It is recommened to use chkdsk.
Sep 29 00:07:41 stoepselArch kernel: ntfs3: sda1: volume is dirty and "force" flag is not set!

Is there a paralllel windows installation?
=> 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Did you try the LTS kernel?

DinoNugget1337 · 2023-09-29 08:01:14

Yes, there is a parallel Windows 11 installation. Fastboot is disabled in BIOS and "(GP "HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Power")."HiberbootEnabled" in Windows returns 0.

Is having Windows not shown in Grub a problem related to this? I can only see Arch there and have to boot into Windows by manually selecting it in the list when pressing F12 on startup.

jl2 · 2023-09-29 09:18:19

So is the not-BIOS setting disabled or not?
https://www.windowscentral.com/software … windows-11

The Journal quits correctly, can you set a high loglevel and see anything after the journal shuts down?

DinoNugget1337 · 2023-09-29 09:33:16

jl2 wrote:

So is the not-BIOS setting disabled or not?
https://www.windowscentral.com/software … windows-11

If you refer to "Turn on fast startup" in Windows, that one is disabled

jl2 wrote:

The Journal quits correctly, can you set a high loglevel and see anything after the journal shuts down?

I'm a noob, sry. How do I do that?

jl2 · 2023-09-29 11:23:22

add logelevel=7 or loglevel=8 or ignore_loglevel to your kernel cmdline
https://wiki.archlinux.org/title/Kernel_parameters

seth · 2023-09-29 13:15:50

The journal will/can not show any problems to tell the ACPI to cut power after the halt.
Make sure that windows fast-start is still disabled (because windows re-enables it w/ updates and your problem is very much adjacent to the condition)

Can you "systemctl reboot"?

Next step would be to lie to the BIOS

acpi_osi=! acpi_osi="Windows 2015"

https://learn.microsoft.com/en-us/windo … inacpi-osi
https://wiki.archlinux.org/title/Kernel_parameters

gcb · 2023-09-29 13:58:24

> Is having Windows not shown in Grub a problem related to this?

personal opinion: nowadays i'd use bootd (systemd, bootclt) instead of grub.

Nothing on the logs is weird. But also, if you don't see windows in the boot menu (assuming you installed arch after windows) it might be a hint to a problem. You might have both OSes fighting for some partition which also explains the fsck errors.

my dual boot recipe is, install windows first, leave partitions for linux empty, install linux later, using lvm on the partition left and sharing (not formating!) the EFI.

basically, install windows first and:
SHIFT+F10... winpart... select disk X. select partition X... delete all... create parition ufi size=1024... create part msr size=16...

windows needs 3 partitions, including the UEFI (above uses 1Gb, highly recommend). leave the 4th for linux.

on arch install, format 4th partition as you wish (ideally with https://wiki.archlinux.org/title/Dm-cry … VM_on_LUKS ) and then simply mount the UEFI parition in /mnt/boot (/mnt during install, obviously)

and make sure you included in your pacstrap

linux linux-firmware amd/intel-ucode base efitools

DinoNugget1337 · 2023-09-29 14:45:39

seth wrote:

Make sure that windows fast-start is still disabled (because windows re-enables it w/ updates and your problem is very much adjacent to the condition)

Checked again, still disabled. "Turn on fast startup(reccomended)" is unchecked

seth wrote:

Can you "systemctl reboot"?

Nope, same issue

seth wrote:

Next step would be to lie to the BIOS
acpi_osi=! acpi_osi="Windows 2015"
https://learn.microsoft.com/en-us/windo … inacpi-osi
https://wiki.archlinux.org/title/Kernel_parameters

Do i need to specify that windows with ' or "? "Windows 2015" gave me an issue while grub-mkconfig that 2015 isn't recognized but 'Windows 2015' worked. So edited it like seen below and did sudo grub-mkconfig -o /boot/grub/grub.cfg, rebooted, still same issue.
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet acpi_osi=! acpi_osi='Windows 2015'"

Edit: Also want to note that Linux Mint always shutdown correctly (before I installed arch). Also had it installed with Grub and Windows Dualboot. Haven't done anything in Windows in the meantime except checking fast boot. Oh, and I now correctly have Windows in my grub after installing os-prober and setting GRUB_DISABLE_OS_PROBER=false in /etc/default/grub

Last edited by DinoNugget1337 (2023-09-29 14:50:49)

seth · 2023-09-29 14:57:52

Do i need to specify that windows with ' or "?

To the kernel this is irrelevant but the grub-mkconfig script will get knocked out by the nested quotes.
I highly recommend to try these kinds of parameters exclusively by editing the kernel commandline in the bootloader, so that, if anything goes wrong, you default without them.

Nope, same issue

Can you reboot w/ any of
* "reboot=pci"
* "reboot=bios"
* "reboot=efi"
* "reboot=triple"
* "reboot=acpi"

Also want to note that Linux Mint always shutdown correctly

With what kernel?

seth wrote:

Did you try the LTS kernel?

Last edited by seth (2023-09-29 14:59:22)

DinoNugget1337 · 2023-09-29 15:49:12

seth wrote:

Can you reboot w/ any of
* "reboot=pci"
* "reboot=bios"
* "reboot=efi"
* "reboot=triple"
* "reboot=acpi"

Also doesn't work.

On Linux Mint I always compiled the lastest tkg kernel. The last one I used was 6.5.5

Just tried the LTS kernel and that actually works! The weird thing is that my monitor resolution is lower and my second monitor doesn't work at all. Is it because my RX 7800XT is newer and requires a newer kernel?

loqs · 2023-09-29 16:02:57

DinoNugget1337 wrote:

On Linux Mint I always compiled the lastest tkg kernel.

You could do the same on Arch? linux-tkg#arch--derivatives.

DinoNugget1337 · 2023-09-29 16:09:33

loqs wrote:

DinoNugget1337 wrote:
On Linux Mint I always compiled the lastest tkg kernel.
You could do the same on Arch? linux-tkg#arch--derivatives.

Already am: Kernel: 6.5.5-273-tkg-bore

loqs · 2023-09-29 16:17:10

DinoNugget1337 wrote:

Already am: Kernel: 6.5.5-273-tkg-bore

Missed that from your first post. Did you copy the config across from the Mint install? So config differences can be ruled out as the cause.
You can find older versions of the linux package in the ALA. If you try a 6.4, 6.3 and 6.2 release, do those have the issue?

DinoNugget1337 · 2023-09-29 16:55:56

Didn't copy the Mint config from tkg kernel but it should be the same as I only change _default_cpu_gov="performance"

I tried with other kernels:
6.2.13 - same as LTS, bad display resolution but shuts down
6.3.1 - 6.3.3 - those don't even boot up? after selecting arch in grub it's just a "_" rest is black
6.3.4 / 6.3.7 / 6.4.16 - don't shut down, same as current one

seth · 2023-09-29 17:53:06

Can you please post a system journal from the (working) lts kernel?
Also try to reboot/shutdown the system from the multi-user.target (2nd link below)

DinoNugget1337 · 2023-09-29 18:23:40

seth wrote:

Can you please post a system journal from the (working) lts kernel?

https://0x0.st/HVUJ.txt

seth wrote:

Also try to reboot/shutdown the system from the multi-user.target (2nd link below)

Doesn't work either

seth · 2023-09-29 18:27:01

Sep 29 20:00:32 stoepselArch kernel: ------------[ cut here ]------------
Sep 29 20:00:32 stoepselArch kernel: WARNING: CPU: 7 PID: 250 at drivers/gpu/drm/ttm/ttm_bo.c:356 ttm_bo_release+0x332/0x350 [ttm]
Sep 29 20:00:32 stoepselArch kernel: Modules linked in: usbhid(+) amdgpu(+) drm_ttm_helper ttm gpu_sched nvme drm_buddy nvme_core drm_display_helper spi_intel_pci crc32c_intel xhci_pci nvme_common spi_intel video cec xhci_pci_rene>
Sep 29 20:00:32 stoepselArch kernel: CPU: 7 PID: 250 Comm: (udev-worker) Not tainted 6.1.55-1-lts #1 2953eb1dc2513ffffee996027d73b3d9ba61d99f
Sep 29 20:00:32 stoepselArch kernel: Hardware name: Gigabyte Technology Co., Ltd. Z390 AORUS MASTER/Z390 AORUS MASTER-CF, BIOS F11 11/05/2021
Sep 29 20:00:32 stoepselArch kernel: RIP: 0010:ttm_bo_release+0x332/0x350 [ttm]
Sep 29 20:00:32 stoepselArch kernel: Code: 00 e8 32 a1 e6 ce 48 8b 43 e8 eb a7 be 03 00 00 00 e8 c2 43 ba ce e9 d6 fd ff ff e8 f8 7d e6 ce e9 cc fd ff ff 4c 89 e0 eb 89 <0f> 0b 48 83 7b 20 00 0f 84 06 fd ff ff 0f 0b e9 ff fc ff ff>
Sep 29 20:00:32 stoepselArch kernel: RSP: 0018:ffffaa9440ffb958 EFLAGS: 00010202
Sep 29 20:00:32 stoepselArch kernel: RAX: 0000000000000000 RBX: ffff9788ce2385c0 RCX: ffff9788d0265d70
Sep 29 20:00:32 stoepselArch kernel: RDX: 0000000000000001 RSI: ffff9788d0265d70 RDI: ffff9788ce2385c0
Sep 29 20:00:32 stoepselArch kernel: RBP: ffff9788ce238458 R08: ffff9788d0265d70 R09: ffff9788cf5d3468
Sep 29 20:00:32 stoepselArch kernel: R10: 0000000000001000 R11: ffff9788cf5d3440 R12: ffff9788d0265538
Sep 29 20:00:32 stoepselArch kernel: R13: 00000000ffffffea R14: 0000000000400000 R15: ffff9788c2336000
Sep 29 20:00:32 stoepselArch kernel: FS:  00007f6f144aa480(0000) GS:ffff97905dbc0000(0000) knlGS:0000000000000000
Sep 29 20:00:32 stoepselArch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 29 20:00:32 stoepselArch kernel: CR2: 000056206e4e8158 CR3: 0000000100fa4002 CR4: 00000000003706e0
Sep 29 20:00:32 stoepselArch kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 29 20:00:32 stoepselArch kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 29 20:00:32 stoepselArch kernel: Call Trace:
Sep 29 20:00:32 stoepselArch kernel:  <TASK>
Sep 29 20:00:32 stoepselArch kernel:  ? ttm_bo_release+0x332/0x350 [ttm a99f1b9fdfcdb7f2164e9df1068a7cb4f955b41e]
Sep 29 20:00:32 stoepselArch kernel:  ? __warn+0x7d/0xd0
Sep 29 20:00:32 stoepselArch kernel:  ? ttm_bo_release+0x332/0x350 [ttm a99f1b9fdfcdb7f2164e9df1068a7cb4f955b41e]
Sep 29 20:00:32 stoepselArch kernel:  ? report_bug+0xe6/0x150
Sep 29 20:00:32 stoepselArch kernel:  ? handle_bug+0x3c/0x80
Sep 29 20:00:32 stoepselArch kernel:  ? exc_invalid_op+0x17/0x70
Sep 29 20:00:32 stoepselArch kernel:  ? asm_exc_invalid_op+0x1a/0x20
Sep 29 20:00:32 stoepselArch kernel:  ? ttm_bo_release+0x332/0x350 [ttm a99f1b9fdfcdb7f2164e9df1068a7cb4f955b41e]
Sep 29 20:00:32 stoepselArch kernel:  ? ttm_resource_move_to_lru_tail+0x1a2/0x1e0 [ttm a99f1b9fdfcdb7f2164e9df1068a7cb4f955b41e]
Sep 29 20:00:32 stoepselArch kernel:  amdgpu_bo_create_kernel_at+0x1dc/0x1f0 [amdgpu 9e87e2f441f62c8c1e5a30f6727b14085580b35e]
Sep 29 20:00:32 stoepselArch kernel:  amdgpu_ttm_init+0x2e4/0x450 [amdgpu 9e87e2f441f62c8c1e5a30f6727b14085580b35e]
Sep 29 20:00:32 stoepselArch kernel:  ? _printk+0x6c/0x87
Sep 29 20:00:32 stoepselArch kernel:  gmc_v11_0_sw_init+0x298/0x3c0 [amdgpu 9e87e2f441f62c8c1e5a30f6727b14085580b35e]
Sep 29 20:00:32 stoepselArch kernel:  amdgpu_device_init.cold+0x12e3/0x1e9b [amdgpu 9e87e2f441f62c8c1e5a30f6727b14085580b35e]
Sep 29 20:00:32 stoepselArch kernel:  amdgpu_driver_load_kms+0x19/0x110 [amdgpu 9e87e2f441f62c8c1e5a30f6727b14085580b35e]
Sep 29 20:00:32 stoepselArch kernel:  amdgpu_pci_probe+0x12b/0x370 [amdgpu 9e87e2f441f62c8c1e5a30f6727b14085580b35e]
Sep 29 20:00:32 stoepselArch kernel:  local_pci_probe+0x42/0x80
Sep 29 20:00:32 stoepselArch kernel:  pci_device_probe+0xc1/0x250
Sep 29 20:00:32 stoepselArch kernel:  ? sysfs_do_create_link_sd+0x6e/0xe0
Sep 29 20:00:32 stoepselArch kernel:  really_probe+0xdb/0x380
Sep 29 20:00:32 stoepselArch kernel:  ? pm_runtime_barrier+0x54/0x90
Sep 29 20:00:32 stoepselArch kernel:  __driver_probe_device+0x78/0x120
Sep 29 20:00:32 stoepselArch kernel:  driver_probe_device+0x1f/0x90
Sep 29 20:00:32 stoepselArch kernel:  __driver_attach+0xd2/0x1c0
Sep 29 20:00:32 stoepselArch kernel:  ? __device_attach_driver+0x110/0x110
Sep 29 20:00:32 stoepselArch kernel:  bus_for_each_dev+0x88/0xd0
Sep 29 20:00:32 stoepselArch kernel:  bus_add_driver+0x1b2/0x200
Sep 29 20:00:32 stoepselArch kernel:  driver_register+0x8d/0xe0
Sep 29 20:00:32 stoepselArch kernel:  ? 0xffffffffc0df1000
Sep 29 20:00:32 stoepselArch kernel:  do_one_initcall+0x5a/0x230
Sep 29 20:00:32 stoepselArch kernel:  do_init_module+0x4a/0x1e0
Sep 29 20:00:32 stoepselArch kernel:  __do_sys_finit_module+0xac/0x120
Sep 29 20:00:32 stoepselArch kernel:  do_syscall_64+0x5d/0x90
Sep 29 20:00:32 stoepselArch kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Sep 29 20:00:32 stoepselArch kernel:  ? do_syscall_64+0x6c/0x90
Sep 29 20:00:32 stoepselArch kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Sep 29 20:00:32 stoepselArch kernel:  ? do_syscall_64+0x6c/0x90
Sep 29 20:00:32 stoepselArch kernel:  ? do_syscall_64+0x6c/0x90
Sep 29 20:00:32 stoepselArch kernel:  entry_SYSCALL_64_after_hwframe+0x64/0xce
Sep 29 20:00:32 stoepselArch kernel: RIP: 0033:0x7f6f14f5f68d
Sep 29 20:00:32 stoepselArch kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 73 96 0c 00 f7 d8 64 89>
Sep 29 20:00:32 stoepselArch kernel: RSP: 002b:00007fff0dba0b18 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Sep 29 20:00:32 stoepselArch kernel: RAX: ffffffffffffffda RBX: 000056206e4f70b0 RCX: 00007f6f14f5f68d
Sep 29 20:00:32 stoepselArch kernel: RDX: 0000000000000000 RSI: 00007f6f1506c343 RDI: 0000000000000010
Sep 29 20:00:32 stoepselArch kernel: RBP: 00007f6f1506c343 R08: 0000000000000000 R09: fffffffffffffe90
Sep 29 20:00:32 stoepselArch kernel: R10: 0000000000000010 R11: 0000000000000246 R12: 0000000000020000
Sep 29 20:00:32 stoepselArch kernel: R13: 000056206e4f7ae0 R14: 000056206e4f70b0 R15: 000056206e4fabc0
Sep 29 20:00:32 stoepselArch kernel:  </TASK>
Sep 29 20:00:32 stoepselArch kernel: ---[ end trace 0000000000000000 ]---
Sep 29 20:00:32 stoepselArch kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* sw_init of IP block <gmc_v11_0> failed -22
Sep 29 20:00:32 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_init failed
Sep 29 20:00:32 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: Fatal error during GPU init
Sep 29 20:00:32 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: amdgpu: finishing device.
Sep 29 20:00:32 stoepselArch kernel: amdgpu: probe of 0000:03:00.0 failed with error -22

What if you boot "nomodeset"?

DinoNugget1337 · 2023-09-29 18:30:26

seth wrote:

What if you boot "nomodeset"?

Into LTS or one that doesn't shutdown/reboot?

seth · 2023-09-29 18:31:19

The one that doesn't shutdown.

DinoNugget1337 · 2023-09-29 18:44:04

Then I can't boot any kernel anymore. It's just a black screen with "_" after grub like 6.3.1 - 6.3.3 described above

seth · 2023-09-29 18:45:33

Pair it w/ the multi-user.target (the graphical.target won't work and that's probably what you see)

DinoNugget1337 · 2023-09-29 18:56:33

Yep, then it works. Tried it multiple times, every time it's correctly rebooting or powering off.

seth · 2023-09-29 19:21:58

LTS

Sep 29 20:00:32 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Sep 29 20:00:32 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: MEM ECC is not presented.
Sep 29 20:00:32 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: SRAM ECC is not presented.
Sep 29 20:00:32 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: VRAM: 16368M 0x0000008000000000 - 0x00000083FEFFFFFF (16368M used)
Sep 29 20:00:32 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
Sep 29 20:00:32 stoepselArch kernel: [drm] Detected VRAM RAM=16368M, BAR=256M
Sep 29 20:00:32 stoepselArch kernel: [drm] RAM width 256bits GDDR6
Sep 29 20:00:32 stoepselArch kernel: ------------[ cut here ]------------
Sep 29 20:00:32 stoepselArch kernel: WARNING: CPU: 7 PID: 250 at drivers/gpu/drm/ttm/ttm_bo.c:356 ttm_bo_release+0x332/0x350 [ttm]
Sep 29 20:00:32 stoepselArch kernel: Modules linked in: usbhid(+) amdgpu(+) drm_ttm_helper ttm gpu_sched nvme drm_buddy nvme_core drm_display_helper spi_intel_pci crc32c_intel xhci_pci nvme_common spi_intel video cec xhci_pci_rene>

TKG

Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: CP RS64 enable
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: [drm:jpeg_v4_0_early_init [amdgpu]] JPEG decode is enabled in VM mode
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: vgaarb: deactivate vga console
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: MEM ECC is not presented.
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: SRAM ECC is not presented.
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: VRAM: 16368M 0x0000008000000000 - 0x00000083FEFFFFFF (16368M used)
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
>>>>>>>>>>> Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF
Sep 29 00:01:01 stoepselArch kernel: [drm] amdgpu: 16368M of VRAM memory ready
Sep 29 00:01:01 stoepselArch kernel: [drm] amdgpu: 16006M of GTT memory ready.
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x0000003f, smu fw program = 0, smu fw version = 0x00503400 (80.52.0)
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully!
Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Sep 29 00:01:01 stoepselArch kernel: amdgpu: HMM registered 16368MB device memory
Sep 29 00:01:01 stoepselArch kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
Sep 29 00:01:01 stoepselArch kernel: kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
Sep 29 00:01:01 stoepselArch kernel: amdgpu: Virtual CRAT table created for GPU
Sep 29 00:01:01 stoepselArch kernel: amdgpu: Topology: Add dGPU node [0x747e:0x1002]

Do you still have a journal from a Mint boot?

Sep 29 00:01:01 stoepselArch kernel: amdgpu 0000:03:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF

DinoNugget1337 · 2023-09-29 19:35:35

seth wrote:

Do you still have a journal from a Mint boot?

Nope, sadly not

Arch Linux

#1 2023-09-28 22:52:12

New arch install - cant reboot or shutdown pc

#2 2023-09-29 07:08:59

Re: New arch install - cant reboot or shutdown pc

#3 2023-09-29 08:01:14

Re: New arch install - cant reboot or shutdown pc

#4 2023-09-29 09:18:19

Re: New arch install - cant reboot or shutdown pc

#5 2023-09-29 09:33:16

Re: New arch install - cant reboot or shutdown pc

#6 2023-09-29 11:23:22

Re: New arch install - cant reboot or shutdown pc

#7 2023-09-29 13:15:50

Re: New arch install - cant reboot or shutdown pc

#8 2023-09-29 13:58:24

Re: New arch install - cant reboot or shutdown pc

#9 2023-09-29 14:45:39

Re: New arch install - cant reboot or shutdown pc

#10 2023-09-29 14:57:52

Re: New arch install - cant reboot or shutdown pc

#11 2023-09-29 15:49:12

Re: New arch install - cant reboot or shutdown pc

#12 2023-09-29 16:02:57

Re: New arch install - cant reboot or shutdown pc

#13 2023-09-29 16:09:33

Re: New arch install - cant reboot or shutdown pc

#14 2023-09-29 16:17:10

Re: New arch install - cant reboot or shutdown pc

#15 2023-09-29 16:55:56

Re: New arch install - cant reboot or shutdown pc

#16 2023-09-29 17:53:06

Re: New arch install - cant reboot or shutdown pc

#17 2023-09-29 18:23:40

Re: New arch install - cant reboot or shutdown pc

#18 2023-09-29 18:27:01

Re: New arch install - cant reboot or shutdown pc

#19 2023-09-29 18:30:26

Re: New arch install - cant reboot or shutdown pc

#20 2023-09-29 18:31:19

Re: New arch install - cant reboot or shutdown pc

#21 2023-09-29 18:44:04

Re: New arch install - cant reboot or shutdown pc

#22 2023-09-29 18:45:33

Re: New arch install - cant reboot or shutdown pc

#23 2023-09-29 18:56:33

Re: New arch install - cant reboot or shutdown pc

#24 2023-09-29 19:21:58

Re: New arch install - cant reboot or shutdown pc

#25 2023-09-29 19:35:35

Re: New arch install - cant reboot or shutdown pc

Board footer