going

Quite interesting! If you try to explain your ultimate goal and the reasons that led you to this decision, perhaps I can give you some advice.

At the moment, I still don't understand the reason. Please publish the name of the eMMC chip, a piece of the schematic diagram of its connection. I will deal with this further.

If your device is in the same condition, I will ask you to provide some additional information about the downloaded operating system. Your case is unique. Your device and mine have the same OS and the same set of packages installed. But the armbian-install script behaves completely differently and crashes in your case. I need to understand why this is happening and correct the erroneous behavior. Please post the output of the following commands: cat /proc/cmdline | tr " " "\n" lsblk -Py df -h sudo blkid 1) You can use a utility from the manufacturer of the chip or device. If this software exists. 2) You can become a hacker, listen to the following harmful tips, or find them on the Internet: Boot the device in any way and get access to the command line with superuser rights. The bootloader, u-boot or other, can be written in whole or in parts to three locations on the eMMC: /dev/mmcblkXboot0 /dev/mmcblkXboot1 /dev/mmcblkX X - This is the number for your eMMC In order for the device not to boot from eMMC, it is necessary to clear those areas in which parts of the bootloader can be placed. sudo su echo 0 > /sys/block/mmcblkXboot0/force_ro dd if=/dev/zero of=/dev/mmcblkXboot0 bs=1M count=4 echo 0 > /sys/block/mmcblkXboot1/force_ro dd if=/dev/zero of=/dev/mmcblkXboot1 bs=1M count=4 dd if=/dev/zero of=/dev/mmcblkX bs=1M count=10 After these steps, your device will be able to boot from the SD card correctly. You can also use the helpful tips described in great detail in the wiki documentation for NanoPi R5S. With respect

Boot from the SD. Try to clear (write zeros) the first 10 megabytes on the /dev/mmcblk1 disk. Try the installation again from the CD.

Let's try to figure out where you are. Boot from the SD and print the output of the df -h command

Is your OS loaded from eMMC? Your OS is loaded from eMMC!! Insert the SD card on running OS and run armbian-install

leo@bananapim3:~$ sudo ./check-command.sh [sudo] пароль для leo: # ls =: /usr/bin/ls # grep =: /usr/bin/grep # awk =: /usr/bin/awk # blkid =: /usr/sbin/blkid # tr =: /usr/bin/tr # lsblk =: /usr/bin/lsblk # xargs =: /usr/bin/xargs # sync =: /usr/bin/sync # mount =: /usr/bin/mount # df =: /usr/bin/df # head =: /usr/bin/head # cat =: /usr/bin/cat # sed =: /usr/bin/sed # mktemp =: /usr/bin/mktemp # nl =: /usr/bin/nl # chroot =: /usr/sbin/chroot # lsof =: /usr/bin/lsof # parted =: /usr/sbin/parted # partprobe =: /usr/sbin/partprobe # mkfs =: /usr/sbin/mkfs # fdisk =: /usr/sbin/fdisk ===== root_partition_device=/dev/mmcblk0 emmccheck=/dev/mmcblk2 diskcheck=sda mmcblk2

No Create a check-command.sh file: #!/bin/bash cm="ls grep awk blkid tr lsblk xargs sync mount df head cat sed mktemp nl chroot lsof parted partprobe mkfs fdisk" for c in $cm do echo "# $c =: $(command -v $c)" done echo "=====" root_uuid=$(sed -e 's/^.*root=//' -e 's/ .*$//' < /proc/cmdline) root_partition=$(blkid | tr -d '":' | grep "${root_uuid}" | awk '{print $1}') root_partition_name=$(echo $root_partition | sed 's/\/dev\///g') root_partition_device_name=$(lsblk -ndo pkname $root_partition) root_partition_device=/dev/$root_partition_device_name emmccheck=$(ls -d -1 /dev/mmcblk* 2>/dev/null | grep -w 'mmcblk[0-9]' | grep -v "$root_partition_device") diskcheck=$(lsblk -l | awk -F" " '/ disk / {print $1}' | grep -E '^sd|^nvme|^mmc' | grep -v "$root_partition_device_name" | grep -v boot) echo "root_partition_device=$root_partition_device" echo "emmccheck=$emmccheck" echo "diskcheck=$diskcheck" and make it executable. chmod +x check-command.sh Run on board and publish sudo ./check-command.sh

I'm shocked. We use the same versions of the system packages. There is something else that needs to be checked. Wait for me to type it now.

@sami Please publish your OS and BASH version. leo@bananapim3:~$ lsblk --version lsblk from util-linux 2.38.1

It looks very strange. It looks like this to me: leo@bananapim3:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 0B 0 disk mmcblk0 179:0 0 7,4G 0 disk └─mmcblk0p1 179:1 0 7,4G 0 part /var/log.hdd / mmcblk2 179:8 0 7,3G 0 disk └─mmcblk2p1 179:9 0 7,2G 0 part mmcblk2boot0 179:16 0 4M 1 disk mmcblk2boot1 179:24 0 4M 1 disk zram0 253:0 0 1005,7M 0 disk [SWAP] zram1 253:1 0 50M 0 disk /var/log zram2 253:2 0 0B 0 disk leo@bananapim3:~$ bash --version GNU bash, версия 5.2.15(1)-release (arm-unknown-linux-gnueabihf) leo@bananapim3:~$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Armbian_community 24.8.0-trunk.104 bookworm Release: 12 Codename: bookworm I booted from the SD card and sudo armbian-install

Please try to replace the /usr/sbin/armbian-install file with this new version: packages/bsp/common/usr/sbin/armbian-install Please show the output of the `lsblk` command. Please post screenshots of the armbian-install dialog.

Cubietruck log : [ 11.673947] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43362-sdio for chip BCM43362/1 [ 11.677634] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43362-sdio.cubietech,cubietruck.bin failed with error -2 [ 11.677685] brcmfmac mmc1:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43362-sdio.cubietech,cubietruck.bin .... [ 12.141976] Bluetooth: hci0: BCM20702A [ 12.142021] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000 [ 12.144184] cfg80211: failed to load regulatory.db [ 12.418687] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43362-sdio.clm_blob failed with error -2 [ 12.418731] brcmfmac mmc1:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43362-sdio.clm_blob [ 12.453585] EXT4-fs (zram1): mounted filesystem 4d22a70b-63d9-448d-86f1-00d5d3260b7f r/w without journal. Quota mode: none. [ 12.457556] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 12.457592] Bluetooth: hci0: BCM: 'brcm/BCM20702A1.cubietech,cubietruck.hcd' [ 12.457602] Bluetooth: hci0: BCM: 'brcm/BCM20702A1.hcd' [ 12.457611] Bluetooth: hci0: BCM: 'brcm/BCM.cubietech,cubietruck.hcd' [ 12.457621] Bluetooth: hci0: BCM: 'brcm/BCM.hcd' .... [ 12.756951] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 12.756988] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [ 12.757625] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43362/1 wl0: Apr 22 2013 14:50:00 version XXX.XXX.195.89.6 FWID 01-b30a427d .... [ 27.278196] ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred [ 27.278246] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5 I do not know what to do about it. 😁 The armbian patches contain many fixes for h616(8) chips including AC 200. I just can't make a decision when changing the fixes. Just because I can't check how to do it right, one way or the other. Is it possible to add another column with the names of the chips so that it looks something like this: Board name | cpu | Kernel version | --------------------|-----|------------------------| Orange Pi Zero Plus | h5 | 6.6.43-current-sunxi64 | --------------------|-----|------------------------| Cubietruck | a20 | 6.6.43-current-sunxi | --------------------------------------------------- And the question. Is there a message distribution service if the test contains any error?

@FRANK333 Try to install this kernel: linux-6.6.43/linux-image-current-sunxi_24.8.0-trunk.510_armhf linux-dtb-current-sunxi/linux-dtb-current-sunxi_24.8.0-trunk.510_armhf__6.6.43 In order to analyze the situation, we need to see part of the DMESG command with an error or part of the system log with an error.

Which core is in the latest test (uname -r)? What is the name of the utility shown in the screenshot?

This feature is not available at the stage of image assembly using the Armbian assembly system. Why? I don't know. P.S. The Armbian build system does not build and distribute source packages. Only binary packages are collected and provided. Why? I don't know.

Congratulations. We will be watching, but the first comment is already available.

Orange Pi 4 -> SOC rk3399 -> The driver for the bus on this SOC drivers/i2c/busses/i2c-rk3x.c Documentation/i2c Check the status of this driver in the kernel on a running OS: grep -n I2C_RK3X /boot/config* There are nine i2c controllers on this SOC and they are described in this file. As far as I can tell from the rk3399-orangepi.dts file, the first five controllers (i2c0-i2c4) are already occupied (in use). Is your temperature sensor unique? Why do you want to write a unique driver for it? In any case, you must enable (activate) a free bus controller, for example i2c7 or i2c8 in the dts file for the temperature sensor driver used. In the Armbian OS, you can do this using an overlay. examples for allwinner SOC. overlay for rockchip64 With respect

I'm using atomic OS updates on my work computer right now. And this is what is provided to me by default by the openSUSE General Purpose Operating System. I'm asking myself a question. And what does the Armbian OS have to do with it? Armbian is a general purpose OS. It is not an embedded OS in the classical sense of the term. Embedded OS, for example, is what you have built using buildroot or Yocto. In this case, you may need these tools as rauc or swupdate. Apt does not violate anything. They violate improperly assembled packages that it installs. You will probably have to control this process yourself. In other words, to assemble some packages yourself and before sending them to your own repository, test them in practice locally in your laboratory. To use atomic updates of multiple packages, you can use the BTRFS snapshot mechanism, for example. In any case, you need to look for help on specialized forums of system administrators. With respect

Thanks for the feedback. Everything else is not an Armbian problem. LLVM is not used when building Armbian images.

@rockmusic64 You can attract the user's attention in two ways: 1) Start typing the username with the @ prefix and click on the suggested option 2) User's quote Unfortunately, I have never used this functionality. Please describe what you want to connect in this mode. I have two devices (OPI-4B rk3399b chip, BPI-f3 k1 chip) with a USB-Type-C connector. How can I physically verify the correctness of the operation when the code is added to the kernel? We learn from each other.

You are looking at the master branch. We need an orange-pi-6.9 branch. See: https://megous.com/git/linux/tree/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts?h=orange-pi-6.9#n729 But simply adding this node will not bring results. A set of patches from this rk3399-typec-6.9 branch is needed and there may be something else. Use the instructions to get the necessary README Look at the contents\history (git log -p megi/rk3399-typec-6.9) of the received branches. Special attention is paid to: megi/tcpm-6.9 megi/typec-extcon-6.9 megi/rk3399-typec-6.9 megi/fusb302-6.9

A little theory: The listener is sitting in the 10th row in the center of the hall. An orchestra is playing music on stage. In the left ear, the sound from the instruments located on the left will be more intense than from the instruments located on the right. The sound from the instruments located on the right will be shifted in phase in the left ear relative to the sound entering the right ear. This is stereo sound from the front. The sound travels through the entire hall and is reflected from the walls and ceiling. It also enters the left and right ears of lower intensity and with a different phase shift. This is a quadro effect. In practice, when recording an audio track, the sound of individual instruments is recorded into separate audio tracks and then mixed using special equipment and recorded into two parallel audio tracks. This is stereo sound from the front. The difference lies in how we listen to the recorded track. If these are simple stereo headphones, then additional mixers allow us to create the effect of presence in the hall. This is a pseudo quadro effect. If you use a good sound card and it has 4 or more outputs and you listen to music through speakers located around the perimeter of the room, then with the help of mixers you can achieve almost the full effect of presence in the concert hall. With respect.

This is not required. First you need to understand what is going on.

Oh. It seems you just don't see anything that's going on? In this case, you need to connect the UART for debugging. _________________ FTDI232 BPI Board | _________________ | | 3.3v |_____ ____ UART GND o|---------------|o GND o| | || | | Linux TX o|---------------|o RX o| | USB|| |====USB cable===| console RX o|---------------|o TX o |____||____| | "minicom" _________________| |________5v______| At the first start of the OS, Armbian tries to get a timestamp from a remote server in order to set the clock to the current time. If she doesn't get it, she waits and kind of freezes. In other words, the download process is not completed and you don't see anything. You will also not be able to connect via ssh, since the user has not yet been installed in the system. Try to configure the router so that it distributes IP addresses via DHCP. With respect