Jump to content

gartox

Members
  • Posts

    4
  • Joined

  • Last visited

  1. Hello, I had the same issue also. My screen has 3 input (DVI,HDMI,DP). My old laptop was connected using a HMDI>DVI cable and works OK, but when connecting the OPI5 I got nothing on screen not even the screen wakes up. But when connecting the OPI5 with HDMI>HDMI cable it works OK.
  2. I also think that everything happened after switching to Waylang for hw acceleration.
  3. Hello All, Do you also have this kind of messages in syslog ? [ 1601.687044] ------------[ cut here ]------------ [ 1601.687070] WARNING: CPU: 2 PID: 112 at drivers/gpu/drm/rockchip/rockchip_drm_vop2.c:2986 vop2_crtc_load_lut+0x54/0x310 [ 1601.687075] Modules linked in: bnep zstd joydev sch_fq_codel fuse ip_tables ipv6 r8152 panfrost gpu_sched [ 1601.687114] CPU: 2 PID: 112 Comm: kworker/u16:1 Tainted: G W 5.10.110-rockchip-rk3588 #trunk.0184 [ 1601.687117] Hardware name: Orange Pi 5 (DT) [ 1601.687127] Workqueue: events_unbound commit_work [ 1601.687134] pstate: 40c00009 (nZcv daif +PAN +UAO -TCO BTYPE=--) [ 1601.687138] pc : vop2_crtc_load_lut+0x54/0x310 [ 1601.687142] lr : vop2_crtc_load_lut+0x4c/0x310 [ 1601.687145] sp : ffffffc012d0bbd0 [ 1601.687148] x29: ffffffc012d0bbd0 x28: ffffff812bbbc000 [ 1601.687155] x27: ffffffc01113d020 x26: ffffff821141aa00 [ 1601.687162] x25: ffffff82108a0058 x24: ffffff81053b2080 [ 1601.687168] x23: 0000000000000400 x22: ffffffc011598cf8 [ 1601.687175] x21: ffffff81053b0080 x20: ffffff81053b0080 [ 1601.687182] x19: ffffff81053b00f8 x18: 0000000000000000 [ 1601.687189] x17: 0000000000000000 x16: 0000000000000000 [ 1601.687195] x15: 0000000000000010 x14: 0000000034325258 [ 1601.687202] x13: ffffffc012d0bb98 x12: ffffffffffffffff [ 1601.687208] x11: 0000000000000040 x10: 00000000fffffffe [ 1601.687214] x9 : ffffffc0107e6030 x8 : 0000000000000000 [ 1601.687221] x7 : ffffff81053d0080 x6 : 00000000000003ff [ 1601.687227] x5 : 0000000000000400 x4 : 00000000000003ff [ 1601.687233] x3 : 000000003fffffff x2 : 00000000000003ff [ 1601.687240] x1 : ffffffc012d05000 x0 : 0000000000000000 [ 1601.687247] Call trace: [ 1601.687253] vop2_crtc_load_lut+0x54/0x310 [ 1601.687258] vop2_crtc_atomic_flush+0x948/0xc18 [ 1601.687262] drm_atomic_helper_commit_planes+0x1c0/0x1c8 [ 1601.687269] rockchip_drm_atomic_helper_commit_tail_rpm+0xa4/0x144 [ 1601.687273] commit_tail+0x80/0x108 [ 1601.687277] commit_work+0x1c/0x28 [ 1601.687283] process_one_work+0x1d8/0x290 [ 1601.687287] worker_thread+0x1e0/0x270 [ 1601.687293] kthread+0xf4/0x104 [ 1601.687299] ret_from_fork+0x10/0x30 [ 1601.687302] ... followed by large dump in hex I really don't have any clue of where it may come from. I'm using the Armbian 22.11 Jammy Gnome Release date: Jan 23, 2023, and I unfreeze nighlies to have latest kernel updates/testings : Linux orangepi5 5.10.110-rockchip-rk3588 #trunk.0220 SMP Tue Jan 31 16:58:49 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux All seems to be working just fine. I would just like to report. thanks !
  4. @Tony3 It should be that you are running under X11. I had the same problem for 2 days turning around and finally followed @royk proposition : echo $XDG_SESSION_TYPE If result is not Wayland then logout and choose Gnome with Wayland. Then everything will be OK.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines