You are not logged in.

#1 2025-02-05 17:00:53

alexanderzhirov
Member
Registered: 2022-05-12
Posts: 40
Website

The problem of switching to text mode after running Plymouth

Hello everyone.

I want to use my own service instead of agetty. I'll show the problem using the example of launching Midnight Commander.

I created the systemd service

[Unit]
Description=MyProgram on tty1
After=systemd-user-sessions.service plymouth-quit-wait.service getty-pre.target
After=rc-local.service

[Service]
Environment=TERM=linux
ExecStart=/usr/bin/mc
StandardInput=tty
StandardOutput=tty
TTYPath=/dev/tty1
TTYReset=yes
TTYVHangup=yes
TTYVTDisallocate=yes
Restart=always

[Install]
WantedBy=multi-user.target

Disabled the launch of the service getty@tty1.service and turned on mc.service.

After restarting, I see the usual loading of plymouth and after it Midnight Commander starts. But the problem is that switching to text mode takes place a little later, and Midnight Commander adapts to the standard screen size, without adjusting the encoding.

screen 1

If, when booting, I remove the quiet splash parameters from the kernel parameters and the Plymouth does not load, then Midnight Commander starts correctly after booting.

screen 2

I found a workaround with downloading with Plymouth. Just before Midnight Commander starts, put something on the screen via the "echo" so that the text is displayed. Then some kind of screen adjustment takes place and Midnight Commander loads correctly.

There is an assumption that Plymouth switches to framebuffer mode and does not correctly switch back to text mode, which leads to this problem.

Do you have any thoughts about this? Is it possible to solve the problem without using some additional output for auto-configuration of the display?

Last edited by alexanderzhirov (2025-02-05 17:02:53)

Offline

Board footer

Powered by FluxBB