| View previous topic :: View next topic |
| Author |
Message |
JumboAg
Apprentice
Joined: 03 Mar 2007
Posts: 191
Location: Dallas, TX
|
 Posted: Mon Jun 05, 2023 5:41 pm Post subject: black screen on orangepi 4 LTS |
 |
|
I've got a black screen issue I cant resolve with an orangepi 4 LTS. When the system is up and running, black screen though there is a signal going to the monitor. If I reboot, it will flash the text of the reboot sequence temporarily.
I appear to have a good framebuffer driver running
| Code: | $ dmesg|grep fb
[ 1.983936] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[ 1.983962] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[ 7.878039] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device
|
| Code: | /sys/class/graphics/fb0 $ cat modes
U:1920x1080p-0
|
I've tried feeding it nothing, 1920x1080 and 1024x768 as video variables to the kernel command line:
| Code: | Kernel command line: root=UUID=aa2e0262-1674-4033-bfcf-963dff22d21a rootwait rootfstype=btrfs bootsplash.bootfile=bootsplash.orangepi console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=00000000-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u "video=1920x1080" cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
|
Any ideas? |
|
| Back to top |
|
 |
pingtoo
l33t
Joined: 10 Sep 2021
Posts: 932
Location: Richmond Hill, Canada
|
| Posted: Tue Jun 06, 2023 3:16 pm Post subject: |
|
|
My guess your kernel missing fbcon setup.
Did you build your own kernel or you are using stock kernel from orangipi?
Can you share | Code: | | zcat /proc/config.gz | grep CONSOLE |
|
|
| Back to top |
|
|
JumboAg
Apprentice
Joined: 03 Mar 2007
Posts: 191
Location: Dallas, TX
|
| Posted: Wed Jun 07, 2023 2:32 pm Post subject: |
|
|
A little from column A, a little from column B. I compiled the kernel myself but used their source git repository for it.
| Code: | $ zcat /proc/config.gz | grep CONSOLE
CONFIG_NETCONSOLE=m
CONFIG_NETCONSOLE_DYNAMIC=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_VT_CONSOLE_SLEEP=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_AMBA_PL010_CONSOLE=y
CONFIG_SERIAL_AMBA_PL011_CONSOLE=y
CONFIG_SERIAL_MESON_CONSOLE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_SCCNXP_CONSOLE=y
CONFIG_SERIAL_XILINX_PS_UART_CONSOLE=y
CONFIG_VIRTIO_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_DUMMY_CONSOLE_COLUMNS=80
CONFIG_DUMMY_CONSOLE_ROWS=25
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER is not set
CONFIG_U_SERIAL_CONSOLE=y
# CONFIG_PSTORE_CONSOLE is not set
CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7
CONFIG_CONSOLE_LOGLEVEL_QUIET=4
|
something else that may be of value:
| Code: | $ dmesg|grep -i console
[ 0.000000] Kernel command line: root=UUID=aa2e0262-1674-4033-bfcf-963dff22d21a rootwait rootfstype=btrfs bootsplash.bootfile=bootsplash.orangepi console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=00000000-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u "video=1920x1080" cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[ 0.002047] Console: colour dummy device 80x25
[ 0.002128] printk: console [tty1] enabled
[ 2.501804] printk: console [ttyS2] enabled
[ 3.228609] systemd[1]: Started systemd-ask-password-console.path.
[ 3.243455] systemd[1]: Starting systemd-vconsole-setup.service...
[ 3.259802] systemd[1]: Finished systemd-vconsole-setup.service.
[ 5.824875] dw-apb-uart ff1a0000.serial: forbid DMA for kernel console
[ 6.186413] systemd[1]: Started systemd-ask-password-console.path.
[ 144.083296] Console: switching to colour frame buffer device 240x67
|
|
|
| Back to top |
|
|
pingtoo
l33t
Joined: 10 Sep 2021
Posts: 932
Location: Richmond Hill, Canada
|
| Posted: Wed Jun 07, 2023 3:58 pm Post subject: |
|
|
I have a NanoPi R4S, it is also based on RK3399.
I don't have /sys/class/graphics/fb0, Instead I have /sys/class/graphics/fbcon.
I wonder may be the "rockchipdrmfb" is causing trouble. In my case because my box run headless. so the dmesg about the "rockchipdrmfb" is | Code: | # dmesg|grep rockchip
[ 1.169735] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[ 1.169787] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[ 1.169818] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[ 1.170335] rockchip-pcie f8000000.pcie: no vpcie12v regulator found
[ 1.285446] rockchip-vop ff8f0000.vop: Adding to iommu group 2
[ 1.286749] rockchip-vop ff900000.vop: Adding to iommu group 3
[ 1.293119] rockchip-drm display-subsystem: bound ff8f0000.vop (ops 0xffffffc010ea0478)
[ 1.296056] rockchip-drm display-subsystem: bound ff900000.vop (ops 0xffffffc010ea0478)
[ 1.366077] rockchip-usb2phy ff770000.syscon:usb2-phy@e460: Requested PHY is disabled
[ 1.457457] rockchip-usb2phy ff770000.syscon:usb2-phy@e460: Requested PHY is disabled
[ 1.592710] rockchip-rga ff680000.rga: HW Version: 0x03.02
[ 1.593457] rockchip-rga ff680000.rga: Registered rockchip-rga as /dev/video0
[ 1.605245] dwmmc_rockchip fe320000.mmc: IDMAC supports 32-bit address mode.
[ 1.605920] dwmmc_rockchip fe320000.mmc: Using internal DMA controller.
[ 1.606534] dwmmc_rockchip fe320000.mmc: Version ID is 270a
[ 1.607109] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 36,32 bit host data width,256 deep fifo
[ 1.611872] rockchip-saradc ff100000.saradc: failed to get regulator, -517
[ 1.679417] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[ 1.680063] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[ 1.680822] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[ 1.682131] rockchip-pcie f8000000.pcie: no vpcie12v regulator found
[ 1.687673] rockchip-drm display-subsystem: bound ff8f0000.vop (ops 0xffffffc010ea0478)
[ 1.690239] rockchip-drm display-subsystem: bound ff900000.vop (ops 0xffffffc010ea0478)
[ 1.691153] dwhdmi-rockchip ff940000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY)
[ 1.693097] rockchip-drm display-subsystem: bound ff940000.hdmi (ops 0xffffffc010ea4410)
[ 1.694747] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
[ 1.695933] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
[ 1.709375] rockchip-saradc ff100000.saradc: failed to get regulator, -517
[ 1.710336] dwmmc_rockchip fe320000.mmc: IDMAC supports 32-bit address mode.
[ 1.711018] dwmmc_rockchip fe320000.mmc: Using internal DMA controller.
[ 1.711622] dwmmc_rockchip fe320000.mmc: Version ID is 270a
[ 1.712215] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 36,32 bit host data width,256 deep fifo
[ 1.717734] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[ 1.718382] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[ 1.719141] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[ 1.720410] rockchip-pcie f8000000.pcie: no vpcie12v regulator found
[ 1.764109] rockchip-saradc ff100000.saradc: failed to get regulator, -517
[ 1.766178] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[ 1.766675] dwmmc_rockchip fe320000.mmc: IDMAC supports 32-bit address mode.
[ 1.766827] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[ 1.767471] dwmmc_rockchip fe320000.mmc: Using internal DMA controller.
[ 1.768198] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[ 1.768793] dwmmc_rockchip fe320000.mmc: Version ID is 270a
[ 1.770082] rockchip-pcie f8000000.pcie: no vpcie12v regulator found
[ 1.770115] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 36,32 bit host data width,256 deep fifo
[ 1.772132] dwmmc_rockchip fe320000.mmc: Got CD GPIO
[ 1.801445] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[ 2.225217] dwmmc_rockchip fe320000.mmc: Successfully tuned phase to 171
[ 2.717122] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes |
So my interpretation of the last line seems to indicate the drm is not working.
And my kernel is stock frindlyfly v5.10. which have kernel drm config like | Code: | # zcat /proc/config.gz | grep -i drm
CONFIG_DRM=y
CONFIG_DRM_MIPI_DSI=y
# CONFIG_DRM_DP_AUX_CHARDEV is not set
# CONFIG_DRM_DEBUG_MM is not set
# CONFIG_DRM_DEBUG_SELFTEST is not set
CONFIG_DRM_KMS_HELPER=y
CONFIG_DRM_KMS_FB_HELPER=y
# CONFIG_DRM_DEBUG_DP_MST_TOPOLOGY_REFS is not set
CONFIG_DRM_FBDEV_EMULATION=y
CONFIG_DRM_FBDEV_OVERALLOC=100
# CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM is not set
CONFIG_DRM_LOAD_EDID_FIRMWARE=y
# CONFIG_DRM_DP_CEC is not set
CONFIG_DRM_GEM_CMA_HELPER=y
CONFIG_DRM_GEM_SHMEM_HELPER=y
# CONFIG_DRM_I2C_CH7006 is not set
# CONFIG_DRM_I2C_SIL164 is not set
# CONFIG_DRM_I2C_NXP_TDA998X is not set
# CONFIG_DRM_I2C_NXP_TDA9950 is not set
# CONFIG_DRM_HDLCD is not set
# CONFIG_DRM_MALI_DISPLAY is not set
# CONFIG_DRM_KOMEDA is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_AMDGPU is not set
# CONFIG_DRM_NOUVEAU is not set
# CONFIG_DRM_VGEM is not set
# CONFIG_DRM_VKMS is not set
CONFIG_DRM_ROCKCHIP=y
CONFIG_DRM_UDL=m
# CONFIG_DRM_AST is not set
# CONFIG_DRM_MGAG200 is not set
# CONFIG_DRM_RCAR_DW_HDMI is not set
# CONFIG_DRM_RCAR_LVDS is not set
# CONFIG_DRM_QXL is not set
# CONFIG_DRM_BOCHS is not set
# CONFIG_DRM_VIRTIO_GPU is not set
CONFIG_DRM_PANEL=y
# CONFIG_DRM_PANEL_ARM_VERSATILE is not set
# CONFIG_DRM_PANEL_ASUS_Z00T_TM5P5_NT35596 is not set
# CONFIG_DRM_PANEL_BOE_HIMAX8279D is not set
# CONFIG_DRM_PANEL_BOE_TV101WUM_NL6 is not set
# CONFIG_DRM_PANEL_LVDS is not set
CONFIG_DRM_PANEL_SIMPLE=y
# CONFIG_DRM_PANEL_ELIDA_KD35T133 is not set
# CONFIG_DRM_PANEL_FEIXIN_K101_IM2BA02 is not set
# CONFIG_DRM_PANEL_FEIYANG_FY07024DI26A30D is not set
# CONFIG_DRM_PANEL_ILITEK_IL9322 is not set
# CONFIG_DRM_PANEL_ILITEK_ILI9881C is not set
# CONFIG_DRM_PANEL_INNOLUX_P079ZCA is not set
# CONFIG_DRM_PANEL_JDI_LT070ME05000 is not set
# CONFIG_DRM_PANEL_KINGDISPLAY_KD097D04 is not set
# CONFIG_DRM_PANEL_LEADTEK_LTK050H3146W is not set
# CONFIG_DRM_PANEL_LEADTEK_LTK500HD1829 is not set
# CONFIG_DRM_PANEL_SAMSUNG_LD9040 is not set
# CONFIG_DRM_PANEL_LG_LB035Q02 is not set
# CONFIG_DRM_PANEL_LG_LG4573 is not set
# CONFIG_DRM_PANEL_NEC_NL8048HL11 is not set
# CONFIG_DRM_PANEL_NOVATEK_NT35510 is not set
# CONFIG_DRM_PANEL_NOVATEK_NT39016 is not set
# CONFIG_DRM_PANEL_MANTIX_MLAF057WE51 is not set
# CONFIG_DRM_PANEL_OLIMEX_LCD_OLINUXINO is not set
# CONFIG_DRM_PANEL_ORISETECH_OTM8009A is not set
# CONFIG_DRM_PANEL_OSD_OSD101T2587_53TS is not set
# CONFIG_DRM_PANEL_PANASONIC_VVX10F034N00 is not set
# CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN is not set
# CONFIG_DRM_PANEL_RAYDIUM_RM67191 is not set
# CONFIG_DRM_PANEL_RAYDIUM_RM68200 is not set
# CONFIG_DRM_PANEL_RONBO_RB070D30 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6D16D0 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E3HA2 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E63J0X03 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E63M0 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E88A0_AMS452EF01 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E8AA0 is not set
# CONFIG_DRM_PANEL_SEIKO_43WVF1G is not set
# CONFIG_DRM_PANEL_SHARP_LQ101R1SX01 is not set
# CONFIG_DRM_PANEL_SHARP_LS037V7DW01 is not set
# CONFIG_DRM_PANEL_SHARP_LS043T1LE01 is not set
# CONFIG_DRM_PANEL_SITRONIX_ST7701 is not set
# CONFIG_DRM_PANEL_SITRONIX_ST7703 is not set
# CONFIG_DRM_PANEL_SITRONIX_ST7789V is not set
# CONFIG_DRM_PANEL_SONY_ACX424AKP is not set
# CONFIG_DRM_PANEL_SONY_ACX565AKM is not set
# CONFIG_DRM_PANEL_TPO_TD028TTEC1 is not set
# CONFIG_DRM_PANEL_TPO_TD043MTEA1 is not set
# CONFIG_DRM_PANEL_TPO_TPG110 is not set
# CONFIG_DRM_PANEL_TRULY_NT35597_WQXGA is not set
# CONFIG_DRM_PANEL_VISIONOX_RM69299 is not set
# CONFIG_DRM_PANEL_XINPENG_XPP055C272 is not set
CONFIG_DRM_BRIDGE=y
CONFIG_DRM_PANEL_BRIDGE=y
# CONFIG_DRM_CDNS_DSI is not set
# CONFIG_DRM_CHRONTEL_CH7033 is not set
# CONFIG_DRM_DISPLAY_CONNECTOR is not set
# CONFIG_DRM_LONTIUM_LT9611 is not set
# CONFIG_DRM_LVDS_CODEC is not set
# CONFIG_DRM_MEGACHIPS_STDPXXXX_GE_B850V3_FW is not set
# CONFIG_DRM_NWL_MIPI_DSI is not set
# CONFIG_DRM_NXP_PTN3460 is not set
# CONFIG_DRM_PARADE_PS8622 is not set
# CONFIG_DRM_PARADE_PS8640 is not set
# CONFIG_DRM_SIL_SII8620 is not set
# CONFIG_DRM_SII902X is not set
# CONFIG_DRM_SII9234 is not set
# CONFIG_DRM_SIMPLE_BRIDGE is not set
# CONFIG_DRM_THINE_THC63LVD1024 is not set
# CONFIG_DRM_TOSHIBA_TC358762 is not set
# CONFIG_DRM_TOSHIBA_TC358764 is not set
# CONFIG_DRM_TOSHIBA_TC358767 is not set
# CONFIG_DRM_TOSHIBA_TC358768 is not set
# CONFIG_DRM_TOSHIBA_TC358775 is not set
# CONFIG_DRM_TI_TFP410 is not set
# CONFIG_DRM_TI_SN65DSI86 is not set
# CONFIG_DRM_TI_TPD12S015 is not set
# CONFIG_DRM_ANALOGIX_ANX6345 is not set
# CONFIG_DRM_ANALOGIX_ANX78XX is not set
CONFIG_DRM_ANALOGIX_DP=y
# CONFIG_DRM_I2C_ADV7511 is not set
# CONFIG_DRM_CDNS_MHDP8546 is not set
CONFIG_DRM_DW_HDMI=y
# CONFIG_DRM_DW_HDMI_AHB_AUDIO is not set
CONFIG_DRM_DW_HDMI_I2S_AUDIO=y
# CONFIG_DRM_DW_HDMI_CEC is not set
CONFIG_DRM_DW_MIPI_DSI=y
# CONFIG_DRM_ETNAVIV is not set
# CONFIG_DRM_ARCPGU is not set
# CONFIG_DRM_HISI_HIBMC is not set
# CONFIG_DRM_HISI_KIRIN is not set
# CONFIG_DRM_MXSFB is not set
# CONFIG_DRM_CIRRUS_QEMU is not set
# CONFIG_DRM_GM12U320 is not set
# CONFIG_TINYDRM_HX8357D is not set
# CONFIG_TINYDRM_ILI9225 is not set
# CONFIG_TINYDRM_ILI9341 is not set
# CONFIG_TINYDRM_ILI9486 is not set
# CONFIG_TINYDRM_MI0283QT is not set
# CONFIG_TINYDRM_REPAPER is not set
# CONFIG_TINYDRM_ST7586 is not set
# CONFIG_TINYDRM_ST7735R is not set
# CONFIG_DRM_PL111 is not set
# CONFIG_DRM_LIMA is not set
# CONFIG_DRM_PANFROST is not set
# CONFIG_DRM_TIDSS is not set
# CONFIG_DRM_LEGACY is not set
CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=y |
since you dmesg output | Code: | | [ 144.083296] Console: switching to colour frame buffer device 240x67 |
I think your system is working except may be the later rc runlevel have something switch the frame buffer for X so you see a black screen.
Do you get some messages after uboot load kernel, then at some point the screen become black? |
|
| Back to top |
|
|
JumboAg
Apprentice
Joined: 03 Mar 2007
Posts: 191
Location: Dallas, TX
|
| Posted: Wed Jun 14, 2023 3:09 am Post subject: |
|
|
| yes, it will very briefly flash something during boot. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gentoo on ARM
