Hello, I have 2 orange pi PC plus units that upon booting go to no signal when lightdm service starts (the suppose to be slick greeter screen). This is with Ubuntu XFCE 22.11 trunk 59 image, and the same is with 22.11 trunk 1.

 

Here are some details:

- switching to tty works fine. Display returns. 1920x1080

- xrandr says no display

- running bin files that use graphical says failed to open display

- changing lightdm resolution in conf file to 1280x720 does nothing

- this happens to both units

- using HDMI 1.4 cable that works with a laptop outputting the same 1920x1080 resolution, so not a cable or TV issue.

 

Questions:

 

- is this an issue with Wayland and x11? If so, how to make the handshake work with the screen?

- could the HDMI ports be somehow bad on both units?

- could the TV be lying about the resolution then? Confusing the graphical rendering for the pi?

- unfortunately there is no way for me to force an EDID handshake with a bin extraction method, no windows laptop with admin priveleges. Is there another way?

moved

Providing logs with 

armbianmonitor -u

 helps with troubleshooting and significantly raises chances that issue gets addressed.

disable ligthdm with "sudo systemctl disable lightdm" and reboot.

 

Log in with text mode. Run "sudo startx". If you see a gray screen with cursor, then X11 is working fine.

 

If not, then you will see a lot of debugging messages. Write down those that start with (EEE). Quit X11 by right-click and "Exit"

 

If you want to abandon X11, try compiling pi-greeter: a "greeter" for lightdm which avoids X11

 

https://github.com/robertojguerra/opiz3-labwc-setup/blob/main/4-pi-greeter.md

 

Related post: https://forum.armbian.com/topic/55882-critique-or-improve-my-method-to-get-a-lightweight-labwc-desktop/#comment-227469

 

Re-enable lightdm with "sudo systemctl disable lightdm"

Edited Tuesday at 04:39 PM5 days by robertoj

Thank you, Roberto, 

Did as you suggested with startx, here's what happened:

- screen went to black then to no signal. 

- I brought tty back and try to start startx again, said xinit connection to x server lost. Then waiting for x server to shutdown, successfuly terminated, closing log file. 

- no EE

 

Here's something I noticed:

- On kernel command line, disp.screen0_output_mode=1366x768p60 and hdmi.audio=EDID:0

 

My guess is that the TV is the culprit and needs an auto resolution script for lightdm, or to force a resolution with lightdm that can handshake with this screen.

 

Now I'm sort of a beginner with this, how can I go about telling lightdm to resolve the handshake with auto detect? 

Since sunxi kernel does it well and has no issues, can a script be made with xrandr for lightdm to force the program into auto detect?

Not to hijack the thread but I have a similar problem on a beelink X2 of older model. When I install the Enlightment desktop everything seems fine, the desktop works, I install a few applications and update the system and on next reboot the graphic screen just goes black. The consoles works fine. Lightdm is running, what else to look for?

Seems like the issue is fixed, although I believe this is more of a temporary solution. 

Here's what I did:

 

- Upon a freshly flashed image, I created a sudo account without a password and let the pi boot to slick greeter screen.

- When the screen went to no signal, I waited a few seconds to make sure login box is there and pressed enter on keyboard.

- Once the NumLock light on keyboard came on, I unplugged the HDMI cable on the pi and plugged it back in. Screen came on displaying multi-display setup and the full desktop environment.

- I ran xrandr | grep "connected"

1-None-1 1920x1080+0+0 0mm x 0mm

2-HDMI-1-1 1920x1080+0+0 708mm x 398mm

 

I am now confused because the manufacturer says native is 1366x768, as does the sunxi kernel, yet the display allows rendering at 1920x1080. I set display 2 to default and set resolution to 1366x768 just in case.

 

Also ID of screen 2, which is my TV says MS Telematica 52", which is also not the manufacturer OR right size.

 

Now, is there a permanent fix to remove this ghost screen set on 1? Or is this a quirk of the pi?