balbes150

I am interested in the output of this command only on the 6.1 kernel (the latest image). Without connecting other devices (USB and M2). When starting a clean system from an SD card or USB flash drive.

The built-in Wi-Fi has nothing to do with M2\PCIe, this is a separate chip that uses SDIO. You may have damaged some of the components that are responsible for power \ control. What the command shows "ip a" ? Is there an interface in the system ?

The Wi-Fi chip built into P2 now works with the latest versions on core 6.1 (I can see the WiFi network and can connect to it on P2).

What are you going to compile ? Are you trying to use these developments for other devices\systems?

New version 20221111 of edge images with core 6.1. Added support for NVMe and WiFi. I checked the installation of the system on NVMe - everything works, the system starts with NVMe, while the SATA SSD disk is also visible and accessible. This will allow you to have both a small NVMe (expensive and fast) to accommodate the system and frequently used directories and a large SATA SSD (large and cheap) to accommodate large archives\data).

All support work has been stopped.

This device is not included in the list of supported devices. Perhaps other DTBS are needed for it (I do not know which ones)

ver 20221101 kernel 5.19.17 and 6.0.7

https://github.com/armbian/build/pull/4380 This fixes the startup. Tomorrow the new corrected images will be on my yandex resource for use. After the adoption of PR, the new official versions will also be fixed.

The "media" core uses patches from LE, so the core has everything that is in LE for HW video. Only applications\libraries compiled using LE patches (ffmpeg mpv kodi etc) are missing. Previously , @JMCC had already built an intermediate test version of all KODI packages using this main kernel and it worked well with HW . If you have the opportunity (time), it is better to build DEB packages using the latest media-6 kernel, it is now used in LE (and patches from LE are included in this kernel). This will allow, by analogy with the JMC media script, to provide the ability to install HW support for all systems that use the kernel with the necessary patches. The ideal option is to add an extension to the build system that will collect packages (ffmpeg mkv code etc) using the latest LE patches and put them in the Armbian repository. This will allow you to easily install everything you need by any user through regular tools (apt synaptic etc). @jock By the way, it would be interesting to check the MEDIA core for the rest of the rk3328\3399\3288 etc devices that you have. In the future, can combine their capabilities.

One patch was lost, I will return it soon.

LE OPiRK3399 version =! LE OPi-800 but there is no LAN yet and you need to manually add firmware and module settings to enable WiFi (USB WiFi should work), I hope to release LE next week with the correction of these bugs.

It uses the old 5.18.5 kernel (with a lot of hacks in the code) and the "manual" addition of "presets". They got the equipment long before us, let's see what happens at least in a few months Due to the simplicity of the packaging and assembly system, they easily take "other people's developments" in different directions and use them at home. But this build system has a big disadvantage (for me) - this system cannot be used in certified conditions, it is a "floating" distribution without a certificate. Such a system can only be used at home, it is not suitable for serious use in corporate settings. Have you tried Armbian versions with 5.18 kernel ? The best system for video playback is LibreELEC. Only it has all the most advanced and best for these purposes. 😛 Hmm, everything works for me. But I have seen some problems with turning on the built-in speaker, if you insert and pull it into the 3.5 jack (turning it on/off again solves the problem), perhaps the switch contacts in the connector are not fully restored when pulling out the external connector.

Upd image 20221031 5.19.17 and 6.0.6

Check the version with kernel 5.18. If you configure which device to use by default (for example, through the Volume Control plug-in), I have not seen any problems with switching audio and output to HDMI on all cores. Have you checked all the images since 5.18 ? There is a difference in them. And it's better to use Ubuntu for tests. I didn't see any problems with the VGA color. Have you tried running with VGA only ? The new 6.0.6 images (with Wi-Fi) are still in the build process and will be available on the site only tomorrow.

This is for a 8Gb RAM 64Gb eMMC + 1TB SSD kit. The minimum version is 2\32 for 159

the overlay with extlinux.conf works from a running system. But I doubt the usefulness of this feature for the opi 800.

Hi. The kernel itself works well with all functions on RK3399 (has patches from LE). For the 1920x1080 video mode, 3399 features are quite enough for full-screen video in Armbian. For full-screen 4k video playback on Armbian there is not enough ffmpeg\HW decoder, but for such modes (4k video), I prefer to use a specialized distribution - LibreELEC, which works great for these purposes. If build the latest versions of ffmpeg\mpv\kodi using patches from LE, all HW 4k functions will work in Armbian. I remember that @JMCC was building a test version of these components using the 5.10 kernel and everything worked fine. VGA does not work on it yet. All functions work on the first version of images with the 5.18.5 kernel (in fact, this is the "legacy" kernel from OPI)

I have not tested the compatibility of the Android bootloader (the StationOS system is Android) with Armbian in multi-boot mode. In theory, it is possible to configure the system\bootloader to run different systems, but so far this can only be done through the UART console (video output and USB keyboard are not working yet). I don't understand the question.

Maybe someone will be interested in it. https://bbs.stationpc.com/forum.php?mod=viewthread&tid=343&extra=page%3D1%26filter%3Dauthor%26orderby%3Dlastpost The uniqueness of this model is in the mechanism of a very simple installation of a standard SATA SSD drive. p.s. According to information from one client who uses this equipment in serious industrial operation - P2 worked without problems for many days with a full load (24\7) in harsh conditions without failures and failures, at the same time, they tried to use R4S, which froze and turned off after 20 hours.

Hmm, you use SSD for the whole system, but why is /boot on the Sd card? Why not follow the standard installation procedure (via armbian-config) and have a full-fledged system? Due to the fact that you use a non-standard file location, the system may collapse during the update (there will be a wrong kernel update)

There is another difference (important for me) - the presence of a power button, this turns the Station P1 pro into a full-fledged mini PC, it will not need to pull out the power supply to turn it on after the program shutdown. This is a small nuance, but it greatly changes the usability of the equipment, for example, as a replacement for a regular PC. p.s. Tnx Andy, Firefly responded quickly to my request for a sample, I hope I will receive a P1 pro sample for support soon

You have not answered the questions, it is important for other users so that they do not encounter such a situation.

In theory, I can move Helios 64 support to the "media" group (and fix build errors), but I'm not sure if this is a good idea (I don't have real hardware for quick testing and debugging) . This will significantly change the entire structure (switching to a different startup option and a different kernel). And before doing this, you need to discuss it with all those interested and those who will be affected by it.

Details are not specified - the kernel\system version before and after the update. It is not specified what you have changed in the system.