FireFly station P2 on Armbian 22.11 Bullseye XFCE does not work on a 4K monitor.

[smatsak]

Hi
FireFly station P2 on Armbian 22.11 Bullseye XFCE does not work on a 4K monitor.
When turned on, ripples appear on the screen. Examples of images from links.

The same problem at station M2. 
station m2 and station p2 do not work on a 4k monitor both

 

Edited January 14, 2023 by smatsak
typos and inaccuracies in my message

[Myron]

Provide diagnostic logs with ...

armbianmonitor -u

... and post the link here.  It'll may help others determine what the issue is.

[smatsak]

I have two monitors and both are 4K, there are no others, if I don't see what is displayed on the screen, how can I execute the command you specified?

[Werner]

You know it is Armbian, not Arabian, right? 😄

[smatsak]

2 минуты назад, Werner сказал:

You know it is Armbian, not Arabian, right?

Of course, a funny typo turned out.
Armbian Armbian Armbian 

[SteeMan]

20 minutes ago, smatsak said:

I have two monitors and both are 4K, there are no others, if I don't see what is displayed on the screen, how can I execute the command you specified?

ssh in

[smatsak]

Только что, SteeMan сказал:

ssh in

this is a fresh installation, without users, without ssh. If there is no other solution, i will have to look for another monitor.

[Myron]

Yup. That's an oops on my part.  If you've got one, use a USB to Serial card to connect a computer to the serial debug port on the SBC and you'll be able to login to the system that way and then try diagnose the issue that way.

See: https://wiki.t-firefly.com/en/ROC-RK3568-PC/debug.html

 

When I started with my Banana Pi Pro I could not get any video to display on the HDMI port right from the beginning.  When I got a USN-to-Serial bridge I completed the initial setup using that method and, mysteriously, the HDMI port started to work and still works to this day.

[smatsak]

30 минут назад, Myron сказал:

If you've got one, use a USB to Serial card to connect a computer to the serial debug port on the SBC and you'll be able to login to the system that way and then try diagnose the issue that way.

On Tuesday or Wednesday I will get to the office there I have other monitors and a usb-serial cable. If there is no way without a report, then we will wait a little. I'm a little sick now I can only be at home. Thanks for the support.

Edited January 14, 2023 by smatsak

[SteeMan]

2 hours ago, smatsak said:

this is a fresh installation, without users, without ssh. If there is no other solution, i will have to look for another monitor.

On a fresh install, the ssh daemon is running and listening on port22.  You should be able to get the dynamically assigned ip address from your router and then log in as root with the default armbian root password.  Then since this would be the first login, it will run through the initial setup in your ssh session, and prompt to the new root password, setup initial user, etc.

[smatsak]

10 часов назад, SteeMan сказал:

On a fresh install, the ssh daemon is running and listening on port22.  You should be able to get the dynamically assigned ip address from your router and then log in as root with the default armbian root password.  Then since this would be the first login, it will run through the initial setup in your ssh session, and prompt to the new root password, setup initial user, etc.

Great idea. It worked. Thanks.

[smatsak]

13 часов назад, Myron сказал:

Provide diagnostic logs with ...

armbianmonitor -u

... and post the link here.  It'll may help others determine what the issue is.

root@station-p2:~# armbianmonitor -u
System diagnosis information will now be uploaded to https://paste.armbian.com/togakopafo
Please post the URL in the forum where you've been asked for.

https://paste.armbian.com/togakopafo

is that all?

[smatsak]

And this is a link for a similar problem on m2
root@station-m2:~# armbianmonitor -u
System diagnosis information will now be uploaded to https://paste.armbian.com/juyobokico
Please post the URL in the forum where you've been asked for.