can you try 10.0.2 ? we have another bugreport for AMD
Can confirm 10.0.2 works. (haven't tried a nightly yet)
Posts by stan_k
-
-
I'll try a nightly. If it works in a future version consistently, that seems like a fine work-around for anyone else that encounters the same problem.
-
Well! 10.0.2 booted right up! I'm happy to help troubleshoot further if anyone wants to dive deeper, but otherwise, I'll just move on with my 10.0.2 life.
(mods, could this be recategorized as a bug report or something? let me know if i can help)
-
Additional logs: systemctl status xorg.service on system that's been sitting at flower splash screen for 5 or 10 minutes:
Code
Display More● xorg.service - Xorg Server Loaded: loaded (/usr/lib/systemd/system/xorg.service; disabled; vendor preset: disabled) Active: deactivating (final-sigterm) (Result: exit-code) Process: 1325 ExecStart=/usr/bin/xorg-launch -nolisten tcp vt01 $XORG_DEBUG (code=exited, status=1/FAILURE) Main PID: 1325 (code=exited, status=1/FAILURE) Memory: 360.0K CGroup: /system.slice/xorg.service └─1327 [Xorg] Oct 18 20:04:16 LibreELEC xorg-launch[1327]: (II) AMDGPU(0): Initializing Cursor Oct 18 20:04:16 LibreELEC xorg-launch[1327]: (==) AMDGPU(0): Silken mouse enabled Oct 18 20:04:16 LibreELEC xorg-launch[1327]: (II) AMDGPU(0): Initializing Xv Oct 18 20:04:16 LibreELEC xorg-launch[1327]: (II) AMDGPU(0): Set up textured video (glamor) Oct 18 20:04:36 LibreELEC xorg-launch[1327]: (II) AMDGPU(0): Initializing kms color map Oct 18 20:04:53 LibreELEC systemd[1]: xorg.service: State 'stop-sigterm' timed out. Killing. Oct 18 20:04:53 LibreELEC systemd[1]: xorg.service: Killing process 1327 (Xorg) with signal SIGKILL. Oct 18 20:04:53 LibreELEC systemd[1]: xorg.service: Killing process 1341 (n/a) with signal SIGKILL. Oct 18 20:04:53 LibreELEC systemd[1]: xorg.service: Killing process 1342 (n/a) with signal SIGKILL. Oct 18 20:04:53 LibreELEC systemd[1]: xorg.service: Killing process 1343 (n/a) with signal SIGKILL.I performance systemctl restart xorg.service, from ssh. command was hanging, so after about 20 seconds, checked journalctl, and saw:
CodeOct 18 20:07:22 LibreELEC xorg-launch[1374]: (II) AMDGPU(0): Initializing kms color map Oct 18 20:07:22 LibreELEC kernel: [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CONNECTOR:77:DP-1] flip_done timed outThat's the last successful status line, followed by a drm-related error.
Few minutes later, similar line:
Code
Display MoreOct 18 20:10:06 LibreELEC xorg-launch[1409]: (II) AMDGPU(0): Initializing kms color map Oct 18 20:10:06 LibreELEC kernel: [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CONNECTOR:77:DP-1] flip_done timed out Oct 18 20:10:12 LibreELEC systemd[1]: Starting Cleanup of Temporary Directories... Oct 18 20:10:12 LibreELEC systemd[1]: systemd-tmpfiles-clean.service: Succeeded. Oct 18 20:10:12 LibreELEC systemd[1]: Finished Cleanup of Temporary Directories. Oct 18 20:10:16 LibreELEC kernel: [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [PLANE:52:plane-3] flip_done timed out Oct 18 20:10:16 LibreELEC kernel: ------------[ cut here ]------------ Oct 18 20:10:16 LibreELEC kernel: WARNING: CPU: 2 PID: 1409 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7391 amdgpu_dm_atomic_commit_tail+ Oct 18 20:10:16 LibreELEC kernel: Modules linked in: 8021q bnep iwlmvm mac80211 iwlwifi btusb btrtl btbcm btintel wl(PO) bluetooth snd_usb_audio snd_hda_inte Oct 18 20:10:16 LibreELEC kernel: CPU: 2 PID: 1409 Comm: Xorg Tainted: P W O 5.10.146 #1 Oct 18 20:10:16 LibreELEC kernel: Hardware name: BESSTAR TECH LIMITED UM350/UM350, BIOS 5.14 03/24/2022 Oct 18 20:10:16 LibreELEC kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x2218/0x22a0 Oct 18 20:10:16 LibreELEC kernel: Code: ff ff 01 c7 85 9c fd ff ff 37 00 00 00 c7 85 a4 fd ff ff 20 00 00 00 e8 36 1e 13 00 e9 e5 fa ff ff 0f 0b e9 53 f9 ff Oct 18 20:10:16 LibreELEC kernel: RSP: 0018:ffffa1428bc2b950 EFLAGS: 00010002 Oct 18 20:10:16 LibreELEC kernel: RAX: 0000000000000002 RBX: 000000000000d369 RCX: ffffa14280c5c918 Oct 18 20:10:16 LibreELEC kernel: RDX: 0000000000000001 RSI: ffffffffb1b4859d RDI: ffffffffb24cc00a Oct 18 20:10:16 LibreELEC kernel: RBP: ffffa1428bc2bc50 R08: 0000000000000005 R09: 0000000000000000 Oct 18 20:10:16 LibreELEC kernel: R10: ffffa1428bc2b8a0 R11: ffffa1428bc2b8a4 R12: 0000000000000297 Oct 18 20:10:16 LibreELEC kernel: R13: ffffa1428c75f000 R14: ffffa14280c5c800 R15: ffffa14280c4d780 Oct 18 20:10:16 LibreELEC kernel: FS: 00007f19fe238d00(0000) GS:ffffa14308a80000(0000) knlGS:0000000000000000 Oct 18 20:10:16 LibreELEC kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 18 20:10:16 LibreELEC kernel: CR2: 0000000000fae090 CR3: 0000000106f6c000 CR4: 00000000001506a0 Oct 18 20:10:16 LibreELEC kernel: Call Trace: Oct 18 20:10:16 LibreELEC kernel: ? __irq_work_queue_local+0x57/0x70 Oct 18 20:10:16 LibreELEC kernel: ? irq_work_queue+0x2a/0x40 Oct 18 20:10:16 LibreELEC kernel: commit_tail+0x99/0x140 Oct 18 20:10:16 LibreELEC kernel: drm_atomic_helper_commit+0x12b/0x150 Oct 18 20:10:16 LibreELEC kernel: amdgpu_dm_atomic_commit+0x11/0x20 Oct 18 20:10:16 LibreELEC kernel: drm_atomic_commit+0x4a/0x60 Oct 18 20:10:16 LibreELEC kernel: drm_mode_obj_set_property_ioctl+0x152/0x3b0 Oct 18 20:10:16 LibreELEC kernel: ? drm_mode_obj_find_prop_id+0x50/0x50 Oct 18 20:10:16 LibreELEC kernel: drm_ioctl_kernel+0xb2/0x100 Oct 18 20:10:16 LibreELEC kernel: drm_ioctl+0x23c/0x430 Oct 18 20:10:16 LibreELEC kernel: ? drm_mode_obj_find_prop_id+0x50/0x50 Oct 18 20:10:16 LibreELEC kernel: ? _raw_spin_unlock_irqrestore+0x2a/0x30 Oct 18 20:10:16 LibreELEC kernel: ? __pm_runtime_resume+0x60/0x90 Oct 18 20:10:16 LibreELEC kernel: ? trace_hardirqs_on+0x37/0xe0 Oct 18 20:10:16 LibreELEC kernel: amdgpu_drm_ioctl+0x4e/0x90 Oct 18 20:10:16 LibreELEC kernel: __x64_sys_ioctl+0x99/0xc0 Oct 18 20:10:16 LibreELEC kernel: do_syscall_64+0x38/0x50 Oct 18 20:10:16 LibreELEC kernel: entry_SYSCALL_64_after_hwframe+0x61/0xc6 Oct 18 20:10:16 LibreELEC kernel: RIP: 0033:0x7f19fe3451a7 Oct 18 20:10:16 LibreELEC kernel: Code: 3c 1c 48 f7 d8 49 39 c4 72 b9 e8 24 ff ff ff 85 c0 78 be 4c 89 e0 5b 5d 41 5c c3 0f 1f 84 00 00 00 00 00 b8 10 00 00 Oct 18 20:10:16 LibreELEC kernel: RSP: 002b:00007ffc4c1e0cf8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Oct 18 20:10:16 LibreELEC kernel: RAX: ffffffffffffffda RBX: 00007ffc4c1e0d30 RCX: 00007f19fe3451a7 Oct 18 20:10:16 LibreELEC kernel: RDX: 00007ffc4c1e0d30 RSI: 00000000c01864ba RDI: 0000000000000009 Oct 18 20:10:16 LibreELEC kernel: RBP: 00000000c01864ba R08: 0000000000000061 R09: 00000000cccccccc Oct 18 20:10:16 LibreELEC kernel: R10: 0000000000000fff R11: 0000000000000246 R12: 0000000001ea05f0 Oct 18 20:10:16 LibreELEC kernel: R13: 0000000000000009 R14: 0000000000000000 R15: 0000000000000003 Oct 18 20:10:16 LibreELEC kernel: ---[ end trace 9ee4a97896bb032b ]--- Oct 18 20:10:16 LibreELEC kernel: ------------[ cut here ]------------ -
Hey. First time libreelec installer, plenty of previous Linux experience if you need more info, but I'm not very well-versed on Xorg and driver stuff.
Trying to install 10.0.3 on a new x86 minipc (https://store.minisforum.com/collections/am…x-manjaro-linux) that has a Ryzen 5 3550H with Vega 8 graphics. This came pre-installed with Manjaro, and that worked swimmingly.
Current experience
1. Bootup is a blank screen for a long time (maybe 2-3 minutes?)
2. Eventually gets the Flower logo splash screen, which hangs.
This happens both when running installed on an nvme and also from a usb stick running "live". I was able to run "live ssh", and get logs:
Logs: http://ix.io/4dxa
Search for "cut here" and you'll see a series of warnings, not sure if they are relevant: WARNING: CPU: 7 PID: 1 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7391 amdgpu_dm_atomic_commit_tail+0x2218/0x22a0
I can see that it can tell what kind of gpu I have, and uses the appropriate xorg config:
Oct 18 19:00:16.316034 LibreELEC systemd[1]: Starting configure Xorg Server for amdgpu...
..
Oct 18 19:00:16.405926 LibreELEC Xorg[487]: ### starting Xorg with ' vt01 -s 0 -noreset -allowMouseOpenFail -config /etc/X11/xorg-amdgpu.conf' ###
There are some various warnings around the audio and bluetooth startup that seem like red herrings to me. In this particular startup, I'm connected with the onboard audio disabled at bios, but that didn't change the outcome.
Here's /var/log/Xorg.0.log.old, as well: http://ix.io/4dxj I'm not sure if there is an old version because it did some kind of x restart.. again, this is the liveusb, so that should all be fresh from memory wipe.
Other things I've tried:
1. Removed all USB devices, disconnected network.. just power and HDMI
2. Removed all USB devices, disconnected network.. just power and DPORT
3. Tried it on a different display
4. Disabled AMD CSM in BIOS
5. Disabled onboard audio in BIOS
6. boot params: live radeon.si_support=0 amdgpu.si_support=1 (i'm really not too familiar with recent history in amd/radeon support, so why not randomly type things i googled)
7. boot params: live radeon.cik_support=0 amdgpu.cik_support=1 (yeah, googled a bit more and these seem like relics, but at least I tried.)
Haven't tried:
1. Downgrading and installing 10.0.2 or whatever previous versions.. new user, so I have no idea what's useful to try there.
No changes in behavior from any tests. Please let me know if I can provide other logs, or if I can run other experiments, and thanks in advance for your time.
