you contradict yourself. if it is running as a service, it means there is no fullscreen video through the KODI screen on this device. fullscreen video and working with DE are mutually exclusive.
To run KODI to play fullscreen video in Armbian with DE (or another Linux distribution), you first disable DE, so there will be no use of DE applications.
Last edited by balbes150 on 2022-12-1 18:51 Editor
Good news. A test version of the Armbian+EDK2 system (UEFI\grub) is available.
The system startup control is performed as on a regular PC - through the menu on the monitor screen, therefore, to fully use all the features of selective startup, you need to have a connected monitor and keyboard
unpack and burn it to a USB drive (8-16GB flash drives are recommended, I haven't checked other options).
Connect the SD card and USB drive. Turn on the power.
If the system does not start immediately, go to settings and select the device to start.
On the EDK2 boot screen, select "Maintaining Manager boot" in the menu item and configure the device used for startup in it (change "none" to "UEFI ...."). Select Reset. If you did everything correctly, after restarting EDK2, you will receive a GRUB menu with a choice of system\kernel.
If you do not select anything, the default system will be started in 5 seconds, and in 10-20 seconds (depending on the type of USB flash drive) there will be a standard Armbian customizer for the first launch.
If desired, you can place the entire system on an SD card, but additional steps will be required at startup.
At startup, the kernel switches the UART console to the correct value for RK (1500000) and you can monitor the kernel startup process and control the system through the UART console.
That is, the parameters 115200 can only be useful for viewing the primary output from EDK2 itself, but this is only necessary for developers, for ordinary users, kernel output and system management are more useful, so I recommend using the standard value for Rockchip of 150000.
you contradict yourself. if it is running as a service, it means there is no fullscreen video through the KODI screen on this device. fullscreen video and working with DE are mutually exclusive.
To run KODI to play fullscreen video in Armbian with DE (or another Linux distribution), you first disable DE, so there will be no use of DE applications.
At the moment, 4k in the main core is not supported for any rk35xx.
BTW, DE that you said is Develop Environment, is not it?
Do you know if it has spicific time plan for LE?
DE = ICEWM\XFCE\Mate\KDE5 etc
No
While running KODI, I intend to be not running a DE application, but a background service based on a virtual machine.
Docker ?
Good news. A test version of the Armbian+EDK2 system (UEFI\grub) is available.
The system startup control is performed as on a regular PC - through the menu on the monitor screen, therefore, to fully use all the features of selective startup, you need to have a connected monitor and keyboard
To use this option.
Download the EDK2 image.
https://disk.yandex.ru/d/kK6KIqHShRHLyw
Unpack and burn to SD card.
Download the Armbian image (kernel 6.1.0-rc7),
https://disk.yandex.ru/d/5XuGz9WgF7FGCg
unpack and burn it to a USB drive (8-16GB flash drives are recommended, I haven't checked other options).
Connect the SD card and USB drive. Turn on the power.
If the system does not start immediately, go to settings and select the device to start.
On the EDK2 boot screen, select "Maintaining Manager boot" in the menu item and configure the device used for startup in it (change "none" to "UEFI ...."). Select Reset. If you did everything correctly, after restarting EDK2, you will receive a GRUB menu with a choice of system\kernel.
If you do not select anything, the default system will be started in 5 seconds, and in 10-20 seconds (depending on the type of USB flash drive) there will be a standard Armbian customizer for the first launch.
If desired, you can place the entire system on an SD card, but additional steps will be required at startup.
At startup, the kernel switches the UART console to the correct value for RK (1500000) and you can monitor the kernel startup process and control the system through the UART console.
That is, the parameters 115200 can only be useful for viewing the primary output from EDK2 itself, but this is only necessary for developers, for ordinary users, kernel output and system management are more useful, so I recommend using the standard value for Rockchip of 150000.
https://github.com/150balbes/quartz64_uefi