balbes150

This is a tricky shit that hides behind openness, but in fact tightly controls the main part-the loader. I.e., at any time, it can block or completely control any unwanted person's actions. It's funny, you described a whole theory about freedom, and as a result it all came down to advertising and pushing aml shit. For your information, aml imposes its BSP shit on everyone, which is stuffed with Trojans and bookmarks to gain full control over those who use their shit. They lie to all users about their hardware and actively cooperate with those you are trying to protect yourself from. In general, everything is as usual, if you remove the beautiful words about freedom, it all came down to the fact that "someone" would spend their time and money and provide the rest with free use of aml shit.

IMHO earlier, in all Armbian builds, autologin was enabled by default and all users are used to this behavior, so it is advisable to keep this in new versions (i.e. make autologin enabled by default and disable autologin yourself, through the armbian-config setting). For many users, this will preserve the usual behavior and at the same time allow you to disable autologin (if necessary).

Search the Internet for how to set up a fixed MAC address in Debian (hint, file) https://github.com/150balbes/Build-Armbian/blob/master/packages/bsp/common/etc/network/interfaces.default#L12

@NicoD Can you shoot a video on how to download and burn an Armbian image to an SD card using only a regular Android on P1 ? I. e. I am interested in a video how to run Armbian with only P1. This instruction allows any user, without any additional devices (PC, laptop, etc.) to get a working Armbian on any supported device.

Can you show a photo of the hat for M2 ?

Disabled the installation of the zsh package and the images began to be collected to build on x86.

Strange behavior of the CLI image build. When natively building an image for p1 (with any kernel, desktop branch), everything goes without errors and I get CLI images (sid bullseye focal), but when trying to build on x86, I get this error for sid bullseye focal, for hirsute the build goes without an error. I need to understand if this is my local problem (my build environment on x86) or if there is such a problem. (Reading database ... 37429 files and directories currently installed.) Preparing to unpack .../armbian-config_21.02.0-trunk_all.deb ... Unpacking armbian-config (21.02.0-trunk) ... Setting up armbian-config (21.02.0-trunk) ... Selecting previously unselected package zsh-common. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 37439 files and directories currently installed.) Preparing to unpack .../zsh-common_5.8-5_all.deb ... Unpacking zsh-common (5.8-5) ... Selecting previously unselected package zsh. Preparing to unpack .../archives/zsh_5.8-5_arm64.deb ... Unpacking zsh (5.8-5) ... Selecting previously unselected package libevent-2.1-7:arm64. Preparing to unpack .../libevent-2.1-7_2.1.12-stable-1_arm64.deb ... Unpacking libevent-2.1-7:arm64 (2.1.12-stable-1) ... Selecting previously unselected package tmux. Preparing to unpack .../archives/tmux_3.1c-1_arm64.deb ... Unpacking tmux (3.1c-1) ... Selecting previously unselected package armbian-zsh. Preparing to unpack .../armbian-zsh_21.02.0-trunk_all.deb ... Unpacking armbian-zsh (21.02.0-trunk) ... Setting up zsh-common (5.8-5) ... Setting up libevent-2.1-7:arm64 (2.1.12-stable-1) ... Setting up zsh (5.8-5) ... Setting up tmux (3.1c-1) ... Setting up armbian-zsh (21.02.0-trunk) ... Processing triggers for man-db (2.9.3-2) ... Processing triggers for libc-bin (2.31-9) ... qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault (core dumped) qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault (core dumped) dpkg: error processing package libc-bin (--configure): installed libc-bin package post-installation script subprocess returned error exit status 139 Errors were encountered while processing: libc-bin E: Sub-process /usr/bin/dpkg returned an error code (1)

Then the sensible option is to wipe the SPI and return to the initial startup state.

You didn't answer the question - what systems did you try before (before the SPI change), did HDMI work or not?

Connect directly, so that there are no intermediate elements that may not work correctly with the signals Which power supply do you use ?

This is not about physically connecting the UART, but about setting up the output of the system startup log from Armbian to UART. I am interested in connected devices (how and where HDMI, LAN USB, etc. is connected). Before recording SPI, did you have any systems working (the HDMI output was working) ? Why do you need to from SPI ? How do you plan to use the device ?

This is the official version, look for how to enable output to the UART console in it. What is connected to the HDMI output and how ? Describe in more detail the configuration of the hardware you are using. I know that P1 (board roc-rk3399-pc-plus) users have no problem running images for P1.

Devices that you connect in the same room ? Wifi is an evil that can only be used for mobile devices, which in principle cannot use a cable (LAN). You ruin your health and the health of others. Now there are a lot of idiots who are too lazy to lay a cable and they stupidly use WiFi shit.

Update for rk3288 20210113. I pay attention. The location of images on download sites has changed. Now it uses its own rk3288 directory. https://yadi.sk/d/fRZwre9HDgAKHw?w=1 https://mega.nz/folder/zxZCTJqB#s8scAu8aW7CD5e-w1btHiQ

Update for rk3188 20210113. Now you can download images for rk3188 with MEGA and https://users.armbian.com/balbes150/

Where is the UART log ?

No

To get rid of all the tails that are now on your SD card, I recommend doing a clean check. Download the image from the link, unzip it and burn it to the SD card. Do not change anything on the SD card, connect to the device and check the launch. https://users.armbian.com/balbes150/firefly_station_p1/ Model Fyrefly Station P1 = ROC-RK3399-pc-plus + eMMC module.

Check for the file at the specified path. /dtb/rockchip/rk3399-roc-pc-mezzanine.dtb I see you have dragged the necessary files to the root of the /BOOT partition (this is not correct)

APPEND root=LABEL=ROOTFS rootflags=data=writeback rw earlycon=uart8250,mmio32,0xff1a0000 console=tty1 console=ttyS2,1500000 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

Is this your model ? http://wiki.t-firefly.com/en/ROC-RK3399-PC-PLUS/debug.html I wrote about changing the value. If you delete a parameter, then you need to delete it all. console=uart8250,mmio32,0xff1a0000

Have you removed this parameter and not replaced it with anything ? Show the contents of extlinux.conf

Show the UART log

You need to find the right parameters for your model. APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff1a0000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 What exactly is your model, is there a link ?

Question. Is it possible to have different package settings for different architectures aarch64\arm64 (64 bits) and separately for armhf\arm (32 bits) ?