MisterC707

Hello @Efe Çetin I was able to compile that branch and it works with the LCD screen now. I did have to copy the rk3588s-orangepi-5b.dtb from my old installation because the rk3588s-orangepi-5.dtb that was compiled from that kernel tree didn't see the onboard emmc. I am having an issue (that I had before with the Orangepi provided kernel and gnome/wayland on armbian but not on OrangePI Ubuntu) where the touchscreen stops responding after you open any application. I'll comb through the logs and see what I can find as it doesn't appear to be a kernel issue so far. (UPDATE: it seems to work properly if I restart gdm3 so I'm guessing it's my cobbled together system, I'll probably start from scratch this weekend to make sure none of my cruft is causing problems) thanks -S

If it helps, here are the Armbian and OrangePi kernel config files armbian-lunar-config-5.10.110-rockchip-rk3588 orangepi-jammy--config-5.10.110-rockchip-rk3588

Sorry one more comment. I noticed that on the Orangepi image, touch screen response is good but on Armbian, unless you keep the display on portrait mode, the touch response is off by whatever rotation you have set, so if youre landscape, moving your finger up will move the pointer left, etc. I did some digging and OPI Ubuntu uses wayland while Armbian uses Xorg X11. Looks like I need to figure out the tweeks for the touchscreen orientation in Xinput.

I installed lunar and it was working withwifi but not the LCD Using the kernel and dtd from OrangePi's Ubuntu image on the same lunar installation enabled the LCDs but disabled the Wireless. [EDIT] I just realized I hadn't copied the module tree over, so right now, with Armbian's dtd, and orange pi's kernel and modules, it works just fine. Also the dmesg lines that show when the panel works: [ 10.613247] rockchip-drm display-subsystem: bound fde30000.dsi (ops 0xffffffc0111da7f0) [ 11.236857] dw-mipi-dsi2 fde30000.dsi: [drm:dw_mipi_dsi2_encoder_enable] final DSI-Link bandwidth: 403300 x 4 Kbps Thanks -Scott

Update: The "OrangePi OS" didn't bear fruit (sorry) but I tried their Ubuntu Jammy image (which is a "rebranding" of Armbian, complete with "orangepi-confiig" instead of "armbian-config") and that worked with the panel. Their LCD1 and LCD2 overlays are the same files as Armbian uses but their rk3588s-orangepi-5b dtd was different so I coped their kernel and dtd over and was able to get LCD working on my lunar installation but the wifi isn't working so I need to dig into that. On the Armbian kernel the following message appears a few times in dmesg: dw-mipi-dsi2 fde30000.dsi: [drm:dw_mipi_dsi2_bind] *ERROR* Failed to find panel or bridge: -517 On the OrangePi kernel that message appears once but then a second message establishing the connection to the LCD is logged and it turns on. Is there any additional information/debugging I can provide? Thakns

I have a 5B and it came in a kit with the 10.1" touchscreen because I wanted to try to do a kiosk. I used Armbian Lunar rolling to get the OS installed on the emmc but I haven't been able to get the touchscreen working. It uses a breakout board to split the LCD2 connector into two connections on the display (I'm assuming one is touch and one is display) and when it's all plugged together, nothing happens. I've tried enabling and disabling both orangepi5lcd dtds and it doesn't help. When I do a dmesg (regardless of the screen being attached) I have Goodix i2c error for touchscreen@14 I've been doing Rockchip SBCs for a while but never used a mipi display on them before. Thanks!

The rolling release (lunar) recognized the emmc once I changed the armbienEnv.txt to point at the proper dtb file: fdtfile=rockchip/rk3588s-orangepi-5b.dtb After that I was able to install to the emmc no problem.

Well, as my grandpappy used to say, "Well dip me in shit and call me stinky" Different SD card worked. So weird that apparently whatever flaw exists on the other one doesn't stop it from booting armbian on different hardware. Oh well, I'll take the win. Thanks for the response.

I have no doubt Armbian works as I have used it successfully on several other SBCs, even other RK3399 based ones, before, so this particular quirk was confusing to me I'll try a different SD card, since I suppose there could be a reason why the Armbian image isn't writing properly (even though it passes Etcher validation) but every other distro I've tried boots up just fine. I'll report back.

Just to add some info, I tried a community lunar build (CLI) and had the same issue. I was able to break out of the network boot loop and poke around in u-boot and something I noticed was when I did "mmc part" it returned "unknown partition table type 0" and then listed no partitions. I"m using Etcher on a Macbook (I've also tried dd to the rdisk device) so I would assume the partition table and type are built into the IMG file, right? Google doesn't seem to know much about that error

Hello! I'm trying to get Armbian jammy latest to boot on my new RockPro64. I've tried both the CLI and XFCE images, flashed with Balena to a good SanDisk uSD card. Both boot into U-Boot but then fail to find a partition on mmc 1. Checking the SD card there's only 1 Linux partition and no FAT one. I tested with a Debian image on the same SD card (DOS + Linux Partition) and it booted into the installer no problem. Any ideas? Thanks! (Also asked on Pine 64 Forums, I will update/close this if they resolve it or vice/versa.)