going

This is a key importance for me and for you. Perhaps some hints exist in man fstrim On my SSD, which is 50% full, the slowdown is observed after about 2 months. I just run the command in this case and wait (do nothing). This repeats itself when I start to observe a slowdown. To be honest, I do not know of any other tool for this functionality than dmesg messages when mounting a file system.

Working with loop devices in BASH is similar to opening a file for reading and closing it after completing the operation in the C language. In the build system, there is a code that remembers the open loop device and there is a code that should delete\close the loop device. But for some reason this does not happen. May it be necessary to wait for the operation to complete? The problem is in the build system. Perhaps the new kernel is faster?

Maybe we should first discuss what is driving your desire in this direction? What is the ultimate goal?

Okay, let's move on. When I mount an ext4 FS, sudo mount -v -o rw,noatime,nodiratime,discard,errors=remount-ro,commit=600 /dev/sdf1 /mnt dmesg reports: [28422.686388] EXT4-fs (sdf1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. [28422.717550] EXT4-fs (sdf1): mounted filesystem with ordered data mode. Opts: errors=remount-ro. Quota mode: none. [28612.985794] EXT4-fs (sdf1): mounting with "discard" option, but the device does not support discard [28612.985800] EXT4-fs (sdf1): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,commit=600. Quota mode: none. When I mount an btrfs FS, sudo mount -o rw,relatime,ssd,space_cache,subvolid=5,subvol=/ /dev/sdf /mnt dmesg reports: [35708.200591] BTRFS: device label test-btrfs devid 1 transid 5 /dev/sdf scanned by mkfs.btrfs (24307) [35708.283831] BTRFS info (device sdf): disk space caching is enabled [35708.283837] BTRFS info (device sdf): has skinny extents [35708.283839] BTRFS info (device sdf): flagging fs with big metadata feature [35708.286642] BTRFS info (device sdf): checking UUID tree [36135.461701] BTRFS info (device sdf): disk space caching is enabled [36135.461706] BTRFS info (device sdf): has skinny extents [36268.307315] BTRFS info (device sdf): enabling ssd optimizations [36268.307322] BTRFS info (device sdf): disk space caching is enabled [36268.307324] BTRFS info (device sdf): has skinny extents EXT4 reports that there is no trim support. BTRFS informs you that everything is included. Perhaps I am mistaken and this is the presence/absence of support in the kernel drivers. I have two more devices, adapters for SATA. One is directly soldered to the BPI-M3. The other is an external PCIe-SATA. I'll check them later.

partprobe /dev/loop2 Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,........ ........... This is the result of incorrect processing of operations with the loop device in the assembly system itself. Some versions of Linux kernels have a delay with these operations, and the BASH script continues without waiting for the operation to complete. As a result, we see a lot of open loop devices. @Igor Are further explanations required?

I need time to think. P.S. Test: OS openSUSE 15.4, desktop computer SATA3 <-> SSD_SATA3 sudo fstrim -v / good work USB2.0 <-> USB2-SATA_adaptor <->SSD_SATA3 fstrim: /mnt: the discard operation is not supported USB2.0 <-> USB3-SATA_adaptor <->SSD_SATA3 fstrim: /mnt: the discard operation is not supported USB3.0 <-> USB3-SATA_adaptor <->SSD_SATA3 fstrim: /mnt: the discard operation is not supported > sudo mount -v -o rw,noatime,nodiratime,discard,errors=remount-ro,commit=600 /dev/sdf1 /mnt > sudo mount | grep /mnt /dev/sdf1 on /mnt type ext4 (rw,noatime,nodiratime,discard,errors=remount-ro,commit=600) > sudo fstrim -v /mnt fstrim: /mnt: the discard operation is not supported I think it's some kind of hardware limitation. You have a newer generation USB3-SATA3 adapter and it supports the function when connected to a USB3 port. Mine is not. Armbian has nothing to do with this. @Crossplatform Vlad I intentionally ran the test on my work computer, not on a banana.

uname -r ? Have you updated the kernel on this distribution? @Crossplatform Vlad My recommendations: Make a new installation of the distribution based on ubuntu 22.04. The build system works on this version. Why is that? Do you need further explanations?

This is a common Linux issue and we usually do not provide assistance. But you have interested me in this fact. If I understood correctly, then the same SSD drive connected via the SATA connector - trim mode is possible, and connected via a USB-SATA adapter - trim mode is impossible? Publish the DMESG output of the line where the USB-SATA adapter is defined. I have a lot of these things. I'll check it out.

Absolute agreement. And this is part of the user's research. A millivoltmeter and knowledge of the measuring point is something that cannot be programmed and provided.

datasheet: [ LPDDR3 ] * VDD1 = 1.8V (1.7V to 1.95V) * VDD2, VDDCA and VDDQ = 1.2V (1.14V to 1.30) * HSUL_12 interface (High Speed Unterminated Logic 1.2V datasheet; e·MMC consists of NAND flash and a MMC controller. 3V supply voltage is required for the NAND area (VDDF) whereas 1.8V or 3V dual supply voltage (VDD) is supported for the MMC controller. Maximum MMC interface frequency of 200MHz and maximum bus widths of 8 bit are supported MMC I/F Clock Frequency : 0 ~ 200MHz MMC I/F Boot Frequency : 0 ~ 52MHz Temperature : Operation(-25C ~ 85C), Storage without operation (-40C ~ 85C) Power : Interface power → VDD (1.70V ~ 1.95V or 2.7V ~ 3.6V), Memory power → VDDF (2.7V ~ 3.6V)

Individual settings for the memory chip such as timings, power supply voltage in the uboot bootloader can solve some problems. Maybe we can compare what is soldered on our boards? @Tu Hu @dd5xl @AaronNGray My board: Bpi-M3 v1.1 ___________ AXP813 ___________ RTL8211E _______________ SUMSUNG 319 KLM8G1GEAC-B001 _______________ SKhynix H9CCNNNBJTML ARNUM 521A UTMBA023HA _______________

Do these images work for your BPI? Is there an internet connection when you launch them? When you run your BPI on your current image without going online, is there normal operation?

I did not immediately notice (drew attention to) the fact that in the logs posted in both topics you can find messages about the missing Internet. The voltage was applied to the device. When booting, system services try to reach the time server and set the current date and time. They can't do it and the system ends up in the past. A system failure is occurring. And as a result, a reboot. You and I cannot know on which images the system services are working correctly, and in which cases a failure occurs. In my memory, this part of the functionality has changed. I remember that there was a script that remembered the current time before shutdown and restored it by adding one hour.

It seems that the reason is the lack of Internet access. It's like air. While he is there, he is not noticed. It's gone and the "coffee makers" are starting to glitch in different corners

@dd5xl Igor, what kind of kernel is working at the same time? I don't see any temperature readings. What is the value of the CONFIG_DRAM_CLK parameter ?

You won't believe it, but sometimes it seems to me that artificial intelligence begins to mock my messages. I apologize.

A search for Ali on the FTDI232 line yielded 216 results. Is that not enough?

A short comment on the discussion. I never use armbian-config. It doesn't help me figure out the essence of the problem. I am considering the overlays that are provided by Armbian as a template for possible use. A script that switches something can be harmful. I'm just turning it off. Next, I pull out the DTB from the working system, which was actually applied. I open the schematic diagram of the printed circuit board and the schematic diagram of the device that I want to attach to the board. I write out the available pin numbers in the table that I could use. I take an overlay file found on the Internet or an existing one as a basis and rewrite it to suit my needs. Next, compile this file, add it to the download and check its operability. This algorithm ensures that nothing superfluous appears in the applied device tree. We can add a lot of automation. We can even connect neural networks to recognize circuit diagrams.😁 But an experienced user will still try to get around (ignore) all this. And an inexperienced user will not understand why something is not working for him. He just did not extract the DTB from the running OS and he does not see the real state of things. It seems to me that helping the user to start thinking with his own head is the best solution.

When the maintainer regularly updates the kernel configuration file in the source repository, you can rely on the correctness of this file. Unfortunately, I did not do this. Until now, this repository was only my personal one and I didn't need to follow some rules to publish. My pbs-master branch was created from the master branch, which is now abandoned and not being developed. I just continued to develop it and added 118 commits on top. There are no mistakes in this. This download script sets up the carl program to be very chatty.

Sometimes there may be large files in the root (/*). sometimes a lot of files can accumulate in the /var folder, for example, in the apt cache. Just go through them all. Run the 'mc' command. Go to the root of the file system. - find "show size" in the menu. Find the folder with the maximum size. Go to it. Repeat "show size"

du -hs /home ls -al / 😄 🤣 😁

@bahtiyar57 _________________ FTDI232 BPI | _________________ | | 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______| o| 3.3v o| This is the jumper on the device. I use this scheme. Everyone uses this scheme. It's safe.

If you downloaded a banana from the SD card and a failure occurred, simply turn off the device, take out the SD card and connect it to a Linux computer via the adapter. Find the latest system logs and review them.

du -hs /mnt/m4v20/home ls -al /mnt/m4v20/

Does not seem to build for me on Ubuntu-22.04.3 LTS git pull cp config/templates/config-test.conf userpatches/ ./compile.sh test BUILD_ONLY=default