going

On my board: After the reboot: All these output texts are received in the minicom console and a physical connection to the board via a USB-UART adapter. SSH connection: > ssh leo@192.168.100.101 leo@192.168.100.101's password: ____ ____ _ __ __ _____ | __ )| _ \(_) | \/ |___ / | _ \| |_) | | | |\/| | |_ \ | |_) | __/| | | | | |___) | |____/|_| |_| |_| |_|____/ Welcome to Armbian 23.10 Bookworm with Linux 6.4.10 No end-user support: built from trunk & unsupported (bookworm) userspace! System load: 1% Up time: 8 min Memory usage: 5% of 1.96G IP: 192.168.100.101 CPU temp: 43°C Usage of /: 6% of 15G [ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ] Last login: Sat Jan 27 12:07:12 2024 leo@bananapim3:~$ sudo apt update [sudo] пароль для leo: Пол:1 http://security.debian.org bookworm-security InRelease [48,0 kB] Пол:2 http://deb.debian.org/debian bookworm InRelease [151 kB] ...... I have not tested HDMI and other connected devices. I communicate with the device only via UART or SSH. You will have to install the graphical environment yourself.

https://github.com/The-going/armbian-build branch: pbs-master git clone --depth=120 --branch=pbs-master https://github.com/The-going/armbian-build

https://armbian.hosthatch.com/dl/bananapim3/archive/Armbian_23.11.1_Bananapim3_bookworm_current_6.1.63.img.xz @Gunjan Gupta U-Boot SPL 2023.10-armbian (Oct 13 2023 - 19:18:50 +0000) DRAM: 2048 MiB Trying to boot from MMC1 ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2023.10-armbian (Oct 13 2023 - 19:18:50 +0000) Allwinner Technology CPU: Allwinner A83T (SUN8I 1673) Model: Banana Pi BPI-M3 DRAM: 2 GiB sunxi_set_gate: (CLK#6) unhandled Core: 67 devices, 21 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial,usbkbd Out: serial Err: serial Net: eth0: ethernet@1c30000 starting USB... Bus usb@1c19000: No host cable detected: Port not available. Bus usb@1c1a000: USB EHCI 1.00 scanning bus usb@1c1a000 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Card did not respond to voltage select! : -110 Card did not respond to voltage select! : -110 No EFI system partition No EFI system partition Failed to persist EFI variables BootOrder not defined EFI boot manager: Cannot load any image Card did not respond to voltage select! : -110 Device 0: unknown device ethernet@1c30000 Waiting for PHY auto negotiation to complete.... done BOOTP broadcast 1 DHCP client bound to address 192.168.100.101 (4 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-01-24-eb-24-3d *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A86465 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A8646 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A864 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A86 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A8 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0 *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default-arm-sunxi *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default-arm *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/default *** ERROR: `serverip' not set Config file not found BOOTP broadcast 1 DHCP client bound to address 192.168.100.101 (4 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET BOOTP broadcast 1 DHCP client bound to address 192.168.100.101 (3 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET For https://armbian.hosthatch.com/archive/bananapim3/archive/Armbian_23.8.1_Bananapim3_bookworm_current_6.1.47.img.xz uboot worked correctly. Loaded the kernel. The kernel starts running and prints a panic. Stop. Do you need more detailed information?

@Tu Hu Until we do the verification, you can use my image. It was created in my version of the build system. Armbian_23.10_Bananapim3_bookworm_edge_6.4.10_minimal.zip

Please link to the image. I'll check it out. A counter question. Which external devices are connected to the board? Does your power supply provide enough power to power the board and the external device?

Extract dts from the file system on a running device dtc --sort -I fs -O dts /sys/firmware/devicetree/base > dts-$(uname -r).txt This is especially useful when you are trying to apply a dtbo overlay on boot.

There are a lot of interesting things here: Documentation/devicetree P.S. In fact, there are a lot of differences between which source code the kernel for your image was compiled from. Feel free to provide additional information.

Yes! man apt-mark ..... PREVENT CHANGES FOR A PACKAGE hold hold is used to mark a package as held back, which will prevent the package from being automatically installed, upgraded or removed. unhold unhold is used to cancel a previously set hold on a package to allow all actions again. showhold showhold is used to print a list of packages on hold in the same way as for the other show commands. .... sudo apt-mark hold linux-image-edge-sunxi

The version of the package from Armbian is the release number. Judging by the screenshot you provided, it is 23.8.1. The version of my package is 6.4.14-Armbian.23.10 that is, it will always be less than the Armbian. It probably needs to be frozen from updates. Try to check it out. Type: sudo apt upade sudo apt --list upgradable P.S.I don't use their repository. I assemble all the packages and the image myself.

#!/usr/bin/bash url="https://github.com/The-going/PKG_test/raw/master/linux-edge-sunxi-6.4.14/" pkg="linux-headers-edge-sunxi_6.4.14-Armbian.23.10_armhf.deb \ linux-libc-dev_6.4.14-Armbian.23.10_armhf.deb \ linux-image-edge-sunxi_6.4.14-Armbian.23.10_armhf.deb" for p in $pkg do wget ${url}${p} done create dl.sh in target dir chmod +x dl.sh ./dl.sh sudo dpkg -i linux-image-edge-sunxi_6.4.14-Armbian.23.10_armhf.deb

wget https://github.com/The-going/PKG_test/raw/master/linux-edge-sunxi-6.4.14/linux-image-edge-sunxi_6.4.14-Armbian.23.10_armhf.deb

And what is the user waiting for? Can you formulate that?

The devils are hiding in the details! Some hardware vendors claim that NPUs in their processors work on some operating systems. This is the OS on their cores. Which specific chip are you interested in?

____ ____ _ __ __ _____ | __ )| _ \(_) | \/ |___ / | _ \| |_) | | | |\/| | |_ \ | |_) | __/| | | | | |___) | |____/|_| |_| |_| |_|____/ Welcome to Armbian 23.10 Bookworm with Linux 6.4.14 No end-user support: built from trunk & unsupported (bookworm) userspace! System load: 6% Up time: 3 min Memory usage: 5% of 1.96G IP: 192.168.100.101 CPU temp: 38°C Usage of /: 12% of 7.3G ========================================================================== leo@bananapim3:~$ armbianmonitor -m Two CPU clusters are available for monitoring Stop monitoring using [ctrl]-[c] Time CPU_cl0/CPU_cl1 load %cpu %sys %usr %nice %io %irq Tcpu C.St. 12:35:38 1344/1152 MHz 0.14 8% 1% 1% 0% 5% 0% 39.1 °C 0/5 12:35:43 1344/1344 MHz 0.13 0% 0% 0% 0% 0% 0% 38.7 °C 0/5 12:35:48 1344/ 768 MHz 0.12 0% 0% 0% 0% 0% 0% 39.5 °C 0/5 12:35:54 1152/1344 MHz 0.11 0% 0% 0% 0% 0% 0% 38.8 °C 0/5 12:35:59 1344/1152 MHz 0.10 0% 0% 0% 0% 0% 0% 39.4 °C 0/5 12:36:04 1344/1152 MHz 0.09 0% 0% 0% 0% 0% 0% 39.7 °C 0/5 12:36:09 768/1344 MHz 0.08 0% 0% 0% 0% 0% 0% 39.7 °C 0/5 12:36:14 1152/1344 MHz 0.08 0% 0% 0% 0% 0% 0% 39.4 °C 0/5^C This is my last kernel build for this platform. It shows the temperature correctly. You can simply download and install this kernel at: https://github.com/The-going/PKG_test/tree/master/linux-edge-sunxi-6.4.14 The *dtb*.deb package is not required.

@bahtiyar57 I am aware of this regression in the latest kernel changes for sunxi. Try installing an older kernel using the armbian-config utility, for example: for current - 5.15.93-sunxi for edge - 6.1.11-sunxi If you want to build the kernel yourself, write here. I will provide you with the necessary changes for the A83T processor.

Try updating the kernel

Try updating the kernel

@Maksimarm What do you mean by that? Can you explain it in an expanded form?

There is not enough space on the disk that is mounted in the /boot folder. df -h ls -al /boot this will give you a hint

Please understand me correctly. I don't see much need to change the installation script. All other issues are general Linux administration issues and they are very well covered on the Internet.

Hello, Frédéric From France. There are many questions here. 1) fault tolerance. 2) recovery after exiting the working state of the root file system. (1) CD card, eMMC, are all flash drives. Technologically, they are different, but they all have a limited resource for recording. Armbian tries to reduce the number of write transactions using the overlay file system. In fact, system write transactions occur in a file located in RAM and are synchronized with the real file system on the drive at longer intervals than the system ones. (2) You want to place the entire root file system on an LVM partition whose type is linear. In this case, you have to recreate the initrd to make it work. And if your drive at the physical level starts to fail or the LVM partition is full, you get very big difficulties for data recovery. packages/bsp/common/usr/sbin/armbian-install This is a very simple script that makes a copy of the OS on your CD card from which you booted and work on an empty nand, SATA, eMMC or NVME. Your drives are eMMC and NVME. What would I do at the very beginning of the journey, when both drives are clean? Boot from the SD card and install the system on eMMC. Boot from eMMC. (for health check) Mark up the NVME drive as LVM or as BTRFS. (The BTRFS file system will provide you with all the necessary functionality.) Make logical partitions for target folders "/opt" "/var" "/srv" "/home". Boot from the SD card and copy the contents of each target folder to the corresponding logical partition while retaining all rights for files. Add the necessary mount entries in the /etc/fstab file located on the eMMC. Boot from eMMC. You are the master of the situation!

Hello, Frederick. Will you be able to explain a little. Why exactly this configuration. Based on the information you provided, I would do the following: 1) Make a standard "Armbian" image for the selected Operating system. 2) Record the image on the SD card. 3) Check the quality of work by booting from the SD. 4)For training, insert a USB-CD adapter with a clean SD card into the USB. 5) Using only the command line and the command (fdisk or parted) to create a partition table and create the required number of partitions. Write down the sequence of actions in a text file. This will serve as a template for writing a script. 6) Format the partitions to the selected file system using /usr/sbin/mkfs.FSTYPE 7) To manipulate the LVM partition, use the command '/usr/sbin/lvm'. Write down the sequence of actions in a mylvm text file in which the first line will contain: #!/usr/sbin/lvm Details in 'man lvm' The lvm command represents its own shell with its own set of commands, so a separate script is needed for it. You can call it at the required stage in your main BASH script. Write the main BASH script and check if it works correctly.

If you use this instruction, you will get branches in the repository named: megi/orange-pi-6.4 megi/orange-pi-6.5 megi/orange-pi-6.6 These branches are the result of combining 27 branches with the corresponding branch kernel.org the repository. If you extract one of these branches to the working directory and extract the difference as a series of patches with the command "git format-patch v6.5.7..HEAD -o /path/to/tmpdir" you will get more than 600 files. These patch files are already available in the build system. All megi patches in tree patch/kernel/archive/sunxi-6.5/series.megous But only those necessary for sunxi are used. The minus (-) sign in the first position indicates that the patch file is not applied and does not adapt to the current version. Copy the patches.megous folder and the series.megous file somewhere, for example: mkdir -p patch/kernel/archive/megi-6.5 cp patch/kernel/archive/sunxi-6.5/series.megous patch/kernel/archive/megi-6.5/ cp -r patch/kernel/archive/sunxi-6.5/patches.megous patch/kernel/archive/megi-6.5/ cp patch/kernel/archive/megi-6.5/series.megous patch/kernel/archive/megi-6.5/series.conf Delete all minus (-) signs in the patch/kernel/archive/megi-6.5/series.conf file. After that, you have to adapt the patches to the current kernel version yourself. Apply them to the git repository as the "git am" command in the sequence order in the series file. When the work is finished and all the patches are applied, you will be able to extract them using a mk_format_patch script. Specify an existing patch/kernel/archive/megi-6.5/patches.megous folder to extract. The changed patches will be replaced. P.S. All other questions please in a personal conversation.

"OMV" is strictly tied to the Debian distribution version. This is written in the documentation. https://docs.openmediavault.org/en/6.x/releases.html#releases