going

@Tu Hu @AaronNGray I tested this image on my board: Armbian_23.10_Bananapim3_bookworm_edge_6.4.16_minimal.img Please confirm that the OS is loaded and working properly. If you have problems downloading, please the output in the UART console and post it here.

@Gunjan Gupta I apologize. The machine translator wrote changing the meaning. It should be tested by someone who has these boards. First of all, it's me. Yes. I'm not suggesting anything. I'm just thinking. I will not make the decisions to do this or that. My thoughts on the code: function post_config_uboot_target__extra_configs_for_bananapipro() { display_alert "$BOARD" "set dram clock" "info" run_host_command_logged scripts/config --set-val CONFIG_DRAM_CLK "384" } I didn't see the difference in the names bananapipro and bananapim3. I'm sorry, the glasses are on my nose. But that doesn't change the point. The user will only see the message: bananapipro set dram clock What if he added his own custom patch? Does the build system allow the user to add patches today? Maybe give the user the opportunity to set the value of this variable? For example: UBOOT_CONFIG_DRAM_CLK="${UBOOT_CONFIG_DRAM_CLK:-384}" function post_config_uboot_target__extra_configs_for_bananapipro() { display_alert "$BOARD" "set dram clock to $UBOOT_CONFIG_DRAM_CLK" "info" run_host_command_logged scripts/config --set-val CONFIG_DRAM_CLK "$UBOOT_CONFIG_DRAM_CLK" } Please don't listen to my grumbling, but do as you see fit.

____ ____ _ __ __ _____ | __ )| _ \(_) | \/ |___ / | _ \| |_) | | | |\/| | |_ \ | |_) | __/| | | | | |___) | |____/|_| |_| |_| |_|____/ Welcome to Armbian 23.10 Bookworm with Linux 6.4.16 No end-user support: built from trunk & unsupported (bookworm) userspace! System load: 11% Up time: 0 min Memory usage: 5% of 1.96G IP: 192.168.100.101 CPU temp: 45�°C Usage of /: 14% of 7.2G The system has become more responsive. For my board, changes are good.

This is a very big problem of the build system. Manufacturers solder different chips in different batches, but the name of the board remains the same. The most active members of the community receive the boards first and the probability that they have these devices from the same manufacturer's batch is very high. As a result, a patch appears that suits everyone. But the next batch of the manufacturer makes us strain answering questions on the forum. To remove a patch is to deprive the support of those users for whom it is good. We should be able to change some settings on the fly without making changes to the algorithm and code of the build system itself. Check it out: armbian/build> grep -nr CONFIG_DRAM_CLK ./* First, you need to check how the changes will work for different users, and then we will think about how to make universal changes.

Armbian_23.10_Bananapim3_bookworm_edge_6.4.16_minimal.img P.S. Only for the test Changes for u-boot: CONFIG_DRAM_CLK <= 480 /* DDR3-1066G @480MHz, timings: 8-8-8-18 */ .cas = 8, .tpr0 = 0x34b28890, .tpr1 = 0xa0c0, .tpr2 = 0x23200, .emr2 = 0x8,

Unfortunately, the build system does not guarantee to reproduce the build, but this information helped me find out that the uboot RAM settings were changed after the time this image was created. @Gunjan Gupta Today, the CONFIG_DRAM_CLK parameter is set to 384 for this BPI-M3 board. This happens both in the patch for this board and encoded in the build system. But the author of the topic uses an image where this parameter in uboot is left by default and is equal to 480. I assumed that the uboot developers had the same fee. I ran the build with these changes in uboot -> CONFIG_DRAM_CLK=480.

sudo dpkg-reconfigure locales

I tried to "kill" the flash drive and the OS on it by pulling the plug out of the socket. It's on the image: Armbian_community_24.2.0-trunk.449_Bananapim3_bookworm_current_6.6.13 It didn't work out. There is a slight freeze for 1 minute, and then everything continues to work. The reboot & poweroff commands are working fine.

The repository is in a shaky state. A configuration file is required. Tomorrow I'll try to build something and publish a working configuration file. By the way, you can rebuild any system source package in this branch.

That's the problem! While I was reading and comparing logs, you seem to have found it. Can't you pull the plug out of the socket, just turn off the power? It is necessary to turn off the poweroff command!

Works

Unfortunately, this happens. In order to understand the difference, let's try to compare the output of this working image with what you provided last time. To do this, please publish the dmesg output file from this working image without timestamps: dmesg --notime >lod_5.83_notime.txt P.S. Please add the DTB file from this image

Try to set the encoding en_US.UTF-8 both in the system on the BPI-M3 and in the terminal window in which you receive the log.

I checked my image. In the minicom console (BPI-M3 -UART -> FTD232 -> USB - Host Linux), in the SSH session, and on the monitor screen connected via HDMI, I see the same greeting pictures: ____ ____ _ __ __ _____ | __ )| _ \(_) | \/ |___ / | _ \| |_) | | | |\/| | |_ \ | |_) | __/| | | | | |___) | |____/|_| |_| |_| |_|____/ 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: 4 min Memory usage: 6% of 1.96G IP: 192.168.100.101 CPU temp: 46�°C Usage of /: 6% of 15G leo@bananapim3:~$ dmesg | grep -i hdmi [ 0.000000] Kernel command line: root=UUID=41970142-87ec-4b91-8231-1b55ee68d69f rootwait rootfstype=ext4 splash=verbose console=ttyS0,115200 console=1 [ 0.084376] platform 1ee0000.hdmi: Fixed dependency cycle(s) with /soc/lcd-controller@1c0d000/ports/port@1/endpoint@1 [ 0.086788] platform connector: Fixed dependency cycle(s) with /soc/hdmi@1ee0000/ports/port@1/endpoint [ 2.327031] sun8i-dw-hdmi 1ee0000.hdmi: supply hvcc not found, using dummy regulator [ 2.327713] sun8i-dw-hdmi 1ee0000.hdmi: Detected HDMI TX controller v1.32a with HDCP (sun8i_dw_hdmi_phy) [ 2.328344] sun8i-dw-hdmi 1ee0000.hdmi: EVENT=plugin [ 2.328730] sun8i-dw-hdmi 1ee0000.hdmi: registered DesignWare HDMI I2C bus driver [ 2.329389] sun4i-drm display-engine: bound 1ee0000.hdmi (ops 0xc0baecbc) [ 2.330594] sun8i-dw-hdmi 1ee0000.hdmi: read_hpd result: 1 [ 43.228319] sun8i-dw-hdmi 1ee0000.hdmi: EVENT=plugin [ 44.121951] sun8i-dw-hdmi 1ee0000.hdmi: EVENT=plugin Observation: My monitor is very smart. He thinks he has correctly identified the entrance from the three possible ones. But he was wrong. I had to press the button with my hand to switch the mode and see the command prompt for entering the password.

Is the terminal connected via HDMI?

P.S. @Tu Hu There is no watch with a battery on this device. You must have an Ethernet connection. During startup, the system will request the exact time from an external server and if it does not receive it, then it will freeze (i.e. it will wait for a response) or it will be in the past with respect to the timestamps of the file system and will not be able to work.

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