Lost mipi-dsi display after recent update

[Learnincurve]

Hi.

I have been running mainline on a Pine64 with mipi-dsi lcd Feiyang display since Focal release.

I default application ran directly on framebuffer without X, with startup log rolling until the application loaded, but after recent update including kernel 6.6.44 the display is completely black, all the way from boot.

I can see that the screen is being identified at boot, but not sure what else to check.

Here are relevant lines from dmesg and modules:

$ dmesg | grep mipi
[   10.113223] sun6i-mipi-dsi 1ca0000.dsi: Attached device fy07024di26a30d

 

$ lsmod | grep fy0702*
panel_feiyang_fy07024di26a30d    12288  0

 

Please can anyone say where should I continue checking?

BR

[DasFisch]

Hey, I know you are seeking answers for your Question, but I've seen you answering many questions related to the Pine A64 and the 7 inch LCD Display. Does it still work for you? I tried to get it working on the 6.62 stable release but IT doesn't work. I tried to Install it with the armbianEnv.txt and adding gt9xxf_fs to modules and activated it in the DT overlay in the armbian-config. Can you please help me? (I'm sorry for asking a question in response to a question) 

[Learnincurve]

Hi,

 

It was working fine up to the update that broke the display, so no.  My problem now is that I have very little time for this, so no progress since it broke.

Your best approach would be tto post a new topic with as much detail as possible aboput what is not working.  Post exactly how you installed and configured and output from dmesg.

Posting to an existing thread covering a different topic is not great as it pulls the thread off-topic and is unlikely to attract the answers that you are looking for.

Good luck getting it working.

[robertoj]

I dont have a Pine64, but I have some experience with LCD displays.

 

Did you try the latest kernel, available by building armbian with the "Edge Linux" option?

 

Can you roll back to the working kernel, get the LCD working again, and examine "dmesg | grep mipi"? If there's no difference, there might be more information in "armbian-monitor -u"

 

DasFisch: in armbianEnv.txt, there is no explicit option to activate ko modules. You can activate armbian or custom user dtbos (overlays), which tell Linux what driver it may use in such port or address.

[Learnincurve]

Thanks robertoj.  I'll try playing with the kernel when I get some time.  Not sure that it is kernel-related though as the screen is picked up successfully during boot (just not displaying anything).