It got worse with the new u-boot? I no longer have a /dev/fb0 and this is reported by the kernel:
# journalctl | grep drm May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: Adding to iommu group 0 May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: bound 5100000.mixer (ops 0xffffffff80c5f628) May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: bound 5200000.mixer (ops 0xffffffff80c5f628) May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: Adding to iommu group 0 May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: bound 5100000.mixer (ops 0xffffffff80c5f628) May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: bound 5460000.tcon-top (ops 0xffffffff80c63ca8) May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: bound 5200000.mixer (ops 0xffffffff80c5f628) May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: bound 5460000.tcon-top (ops 0xffffffff80c63ca8) May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: No panel or bridge found... RGB output disabled May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: bound 5461000.lcd-controller (ops 0xffffffff80c5c6d8) May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: bound 5470000.lcd-controller (ops 0xffffffff80c5c6d8) May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: No panel or bridge found... RGB output disabled May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: bound 5461000.lcd-controller (ops 0xffffffff80c5c6d8) May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: bound 5470000.lcd-controller (ops 0xffffffff80c5c6d8) May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: bound 5500000.hdmi (ops 0xffffffff80c5e718) May 25 16:58:49 sipeed kernel: [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0 May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: bound 5500000.hdmi (ops 0xffffffff80c5e718) May 25 16:58:49 sipeed kernel: [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0 May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: [drm] Cannot find any crtc or sizes May 25 16:58:49 sipeed kernel: sun4i-drm display-engine: [drm] Cannot find any crtc or sizes May 25 16:58:50 sipeed systemd[1]: Starting Load Kernel Module drm... May 25 16:58:50 sipeed systemd[1]: Starting Load Kernel Module drm... May 25 16:58:50 sipeed systemd[1]: [email protected]: Deactivated successfully. May 25 16:58:50 sipeed systemd[1]: Finished Load Kernel Module drm. May 25 16:58:50 sipeed systemd[1]: [email protected]: Deactivated successfully. May 25 16:58:50 sipeed systemd[1]: Finished Load Kernel Module drm. May 26 09:28:15 sipeed sudo[1098]: sipeed : TTY=pts/0 ; PWD=/home/sipeed ; USER=root ; COMMAND=/bin/grep sun4i-drm /var/log/syslog May 26 09:28:40 sipeed sudo[1124]: sipeed : TTY=pts/0 ; PWD=/home/sipeed ; USER=root ; COMMAND=/bin/grep -a sun4i-drm /var/log/syg Also, backlight is off now. I grabbed the tgz and then built: u-boot-d1-2022-05-26 and ran mkimage again, and dd'd the toc1. On Fri, May 27, 2022 at 7:33 AM Samuel Holland <[email protected]> wrote: > On 5/26/22 11:33 AM, Bram Stolk wrote: > > I will document what I can find about the RV86 screen, here: > > https://linux-sunxi.org/Lichee_RV_86_Panel > > I figured out what was wrong with mainline -- I had forgotten the pinctrl > node > in the devicetree for the RGB LCD interface. As a result, all of the > data/clock > pins were tri-stated, and of course that meant no picture. It turns out the > driver itself was fine. > > If you update to the latest U-Boot tag, that will come with the fixed > devicetree, and the panel should start working: > > https://github.com/smaeul/u-boot/releases/tag/d1-2022-05-26 > > Regards, > Samuel > -- Owner/Director of Game Studio Abraham Stolk Inc. Vancouver BC, Canada [email protected] -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/linux-sunxi/CABYXEksPmW3KsF_xXRd0uPOA01hjyF5nsQveEVup2C6qJp_DTQ%40mail.gmail.com.
