jan-k

It's a kernel thing, CONFIG_ARM64_64K_PAGES are biting us. I had a bad feeling about it from the beginning, when I first saw it in the config. Will file an PR to remove it. For preempt-rt, it's off already.

Thank you jan-k. This solution is a first try to understand if we can support a GUI on the Basic IOT2050. LXDE is not so fast, maybe a simple webclient could be the solution.

Can I change something inside meta-iot2050 to fix chromium problem?

The change is trivial, see https://github.com/siemens/meta-iot2050/pull/7/files

Regarding UI: There are plans to explore the GPU usage and, thus, decent acceleration. As far as I heard (waiting for my DP adapter to arrive to check this), the current usability of desktop environments is indeed rather limited. Using a framebuffer screen with a simple UI may already work, though.

Hello,

Yes the goal is to display directly on the DP port of the iot2050.

I will try your solution this week.

I will keep you informed of the results.

Thank you so much

 Hello,

So I used the openbox solution with chromium and it works great.

However, I still have a problem: the screen does not automatically wake up after a restart of the iot!

Do you have a solution for this problem?

Thanks in advance 

Jerome_mabeo

Hello,

Yes the goal is to display directly on the DP port of the iot2050.

I will try your solution this week.

I will keep you informed of the results.

Thank you so much

Jerome_mabeo

 Hello,

So I used the openbox solution with chromium and it works great.

However, I still have a problem: the screen does not automatically wake up after a restart of the iot!

Do you have a solution for this problem?

Thanks in advance 

Jerome_mabeo

Hello,

Yes the goal is to display directly on the DP port of the iot2050.

I will try your solution this week.

I will keep you informed of the results.

Thank you so much

 Hi, I'm as well intresting it a solution for using the IO2050 as a GUI to display a webpage. What do you mean with the "openbox solution" ?

I will get my IOT2050 on monday...

Thanks for your feedback. Stephan

Hi,

I use this link : https://willhaley.com/blog/debian-fullscreen-gui-kiosk/

Bye

Hi all.

I follow instructions from the URL suggested and the kiosk-mode is running well.

There are two unclear points :

1) if I change last line into autostart script from

-- kiosk "http://www.google.com" & TO -- kiosk "localhost:1880/ui" &

the system launch the same page as before, the browser homepage.

2) With some nodes running, in node-red the CPU load rise costantly and the communication between browser and node-red goes down after few minutes.

Some ideas to fix these problems?

BR