balbes150

There is no need to save the current set of packages, I just brought them to the general state. So that the set in the new DESKTOP branch is (if possible) equal to the current state in the official versions. It's like a starting point for a merge. Perhaps then it is worth having a minimal configuration (set of packages) for DE ? That is, the minimum configuration describes (includes in the assembly) only the components that are necessary to form the DE ? Move all other additional application packages to groups ? But then need to decide (discuss) which applications should be included in the basic delivery of the official version of DE XFCE, so that this set is the same for all official versions of Ubuntu\Debian with an officially supported DE (XFCE). this is necessary in order to form caches of package sets, by analogy, as it is now for DE XFCE for the MASTER branch. Perhaps to simplify control (so as not to check which mandatory groups are included when building the official version of DE) it is easier to have a fixed configuration that is selected automatically when building official versions, for example config_armbian (with a description of all packages and applications in one place\file)?

u-boot works correctly and the system is started using extlinux.conf. See the output Remove this from the settings root=/dev/mmcblk1p2 rootfstype=vfat console=uart8250,mmio32,0xff1a0000 And show the full contents of the "extlinux.conf" file What exactly image (full image name) are you trying to run, what steps are you doing ?

Now I tested the latest versions of Armbian with Ubuntu Hirsute on rk3399. Firefox plays yuotube at full screen 1080p without brakes (without any additional settings, immediately after starting the system). And most importantly - (when using Armbian supported devices) I get immediately working LAN WiFi BT HDMI sound, without any dancing with a tambourine and manual finishing with an unknown result will you have it work on an unknown (but cheap) noname TV box. Only a specialist of the Armbian developer level who can independently guarantee their work can afford to buy cheap shit boxes. if you do not have such skills (are not able to develop) - it is better to forget that cheap piece of crap, the result clearly disappoint you (i.e. you potrata time, nerves and energy, but don't get what you want). @JMCCHe is a developer of medascript (for working with media content) in Armbian and I advise you to listen carefully to his advice, it will save you money and nerves. Especially now there are interesting options for full-fledged devices (ready for the end user) that can work as a mini-PC and at the same time as a media device (TV box).

This is the correct dtb. I don't use this software and have no idea what it requires.

If follow this logic, the current set of additional groups should correspond (when selecting all groups) to the current official set of packages for DE XFCE, which is currently used by the master branch. Otherwise, there is ambiguity. Some of the package groups must be selected to get a match, but other package groups will be "optional" (there are none in the current DE XFCE).

I think it's just a typo, meant rk3328. Tip - don't spend money on Amlogic, this shit won't work properly.

For all fans of writing nonsense, spam, provocative messages, piracy ads, and so on. All your posts and topics will be deleted without warning. Information for everyone. The old Amlogic kernel contain a large number of Trojans and the security system is completely destroyed, which allows all sorts of freaks and scammers to access the system with these cores. Therefore, all information about images with old Amlogic cores will be deleted without warning.

fix bionic bullseye sid hirsute https://github.com/150balbes/build/tree/armbian-tv-next/config/desktop/bionic/environments/xfce/config_default https://github.com/150balbes/build/tree/armbian-tv-next/config/desktop/bullseye/environments/xfce/config_default https://github.com/150balbes/build/tree/armbian-tv-next/config/desktop/sid/environments/xfce/config_default

Option for "soft" integration into the main build system. 1. For each distribution, a default configuration is created, the composition of packages is equal to those used in the current version of the MASTER branch for official versions. 2. Each created set should be independent (references to "neighboring" distributions should not be used). This will allow to accurately track the required set of packages, which applies only to the selected distribution (this is analogous to how it is now written in the script "configure.sh", all special packages for the distribution in its group https://github.com/150balbes/build/blob/master/lib/configuration.sh#L202 ). And if necessary, it is easy to modify the set of packages strictly for the selected distribution, without breaking the assembly of other versions.

I tried adding a new configuration to the build system that is (if possible) close to the current set of master branch packages when building a default image with DE XFCE. I checked the native build with this configuration option, the build passes without errors and the images work on P1\M1. If someone has time, please look and check the received configuration, maybe I missed some necessary packages (or added extra ones). Links to package lists for focal and buster. https://github.com/150balbes/build/tree/armbian-tv-next/config/desktop/buster/environments/xfce/config_default https://github.com/150balbes/build/tree/armbian-tv-next/config/desktop/focal/environments/xfce/config_default I plan to send the PR after the other interested developers confirm that the configuration is correct.

I understand correctly, the new system (the desktop branch when building rootfs) uses the same set of packages to get the basic part, the difference is only in the composition of packages\scripts that are used for a set of packages that are described in variables PACKAGE_LIST_DESKTOP in the master branch ?

no

On rockpi 4B, I use only USB 2.0 ports to run from USB. Note that u-boot is a mini-system and, unlike the usual kernel, all the algorithms for polling USB devices may not work here, as in the usual kernel. Just as important is the order of connected devices, as far as I remember, u-boot uses USB0 to search for the system. On the RK3399, it doesn't make sense to use USB to host the entire system for permanent use. There are much faster NVMe devices for this.

Try connecting the USB to all the connectors and changing the order in which the other devices are connected.

video HW for rk3188 https://forum.libreelec.tv/thread/20823-unofficial-le-version-for-rk3328-rk3399-3288-3188/?postID=148770#post148770 Please note that to run external systems on rk3188, you need to update the firmware to the version that supports running external systems from the SD card.

LE uses its own settings management system (including audio), which consists of many different additional components (these are not components of KODI itself). For Armbian + mediascript, you must first set the necessary settings in the system (if the system supports them, not all settings are possible in Armbian) and then switch to KODI. In Armbian, the KODI application is limited in setting different hardware settings, it uses system settings.

On rockpi 4B, I built and installed this version in SPI a long time ago (installation according to the instructions for the official version, only you need to replace the official files with the version from the link) and run all test builds from USB\SD. eMMC has the main working system installed, which I use on rockpi 4B. Previously, I used NVMe without eMMC, but then I disabled the NVMe module and switched to eMMC (as a mini PC). https://yadi.sk/d/OPIkX9eh48BCWQ?w=1 PS the patch to run from USB I include in all my builds for RK3399. If you install my build on eMMC (or you can replace just the u-boot), then without using SPI you can to run from USB (i.e. the system is on eMMC and you can run any systems from USB \ SD).

Ver 20210105

Image for rk3188 add image Debian Sid https://yadi.sk/d/7wqSh5Z5bv9q1g?w=1

For everyone, in order to avoid problems and have a guaranteed working device with a desktop (DE XFCE \ Mate\Lxde\KDE\IceWM etc), I recommend using proven models. Now full-fledged devices are available that can completely replace the PC. Entry-level device Firefly Station M1 (rk3328). For those who need maximum performance Firefly Station P1 (rk3399). For these models, there are versions of ArmbianTV Armbian LibreELEC (there are versions with HW acceleration). https://www.stationpc.com/ P.S. I have both models available, you can draw conclusions yourself ....

Good news. Working version of Libreelec for rk3188 (thanks to @knaerzche for providing the source code). I tested it on my UT2 (rk3188). I wrote the image to the SD card, connected it to UT2, and the system automatically started. Works with HDMI audio and HW acceleration for video (not all formats are supported yet). My LAN hasn't worked yet. Important - now there is a working version of the kernel and u-boot for rk3188, I hope to build a version of Armbian with these sources in the near future. Thank you to @knaerzche for the work done to add support for rk3188 with a modern kernel and u-boot. https://yadi.sk/d/S1atbTqQcLOxnA?w=1

Ver 20201226. Added support for HDMI audio.

There is no "new" kernel for P1, I use the rockchip64 kernel (all patches are regular from the build system only added patches for DTB), the difference is only in the kernel configuration + adding drivers for WiFi.

Try using my "armbian-tv-next" branch to build images for P1\M1. It has changes that use a different kernel for legacy. I am not creating a PR yet, until it is agreed with the rest of the interested developers which legacy kernel is best to use for P1\M1.

Armbian ver 20201225 kernel 5.10 https://yadi.sk/d/KIvG9oQzIuvUyw?w=1