Everything posted by going
-
Missing trim support for SSD on USB 2.0
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.
- worked im for Banana Pi M3
-
worked im for Banana Pi M3
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)
-
worked im for Banana Pi M3
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 _______________
- worked im for Banana Pi M3
-
worked im for Banana Pi M3
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.
- worked im for Banana Pi M3
- worked im for Banana Pi M3
- None of the images work.. OrangePi Zero2
- None of the images work.. OrangePi Zero2
-
Orange Pi Zero 3
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.
-
worked im for Banana Pi M3
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.
-
Root partition thinks it's full
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"
- Root partition thinks it's full
-
Banana Pi M3 crashes if ETH plugged
@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.
- Banana Pi M3 crashes if ETH plugged
- Root partition thinks it's full
- worked im for Banana Pi M3
-
worked im for Banana Pi M3
As far as I know, the default system cross compiler is used today. Try using the key SKIP_EXTERNAL_TOOLCHAINS=no What is the difference? You can check it out: ${prefix}-gcc -v In this particular case, it's my human eye and pressing the mouse button. If the eye has noticed the difference, it is already significant. Switching the processor frequency with increasing load (when a resource-intensive process is started) is faster.
-
Banana Pi M3 crashes if ETH plugged
I have a question. If it works well, why switch to another interface (Ethernet)? This device does not have a battery-powered clock and it requires the Internet to get an accurate time stamp from the time server and set the SOC's internal clock in real time. You have disabled WI-FI and connected Ethernet. Do the settings in the connection management system look correct now? Is the network cable working? Does the banana receive the DHCP settings from the router? Did the router have Internet access at the time of banana connection? You didn't write anything about it. Just for reference. There has been a strong magnetic storm on our planet for the last two days. My Internet went down several times for one hour or more.
- Banana Pi M3 crashes if ETH plugged
- worked im for Banana Pi M3
- worked im for Banana Pi M3
- worked im for Banana Pi M3
-
Root partition thinks it's full
set command: > ls /usr/sbin | grep fsck > sudo fsck --help > man fsck dmesg | tail ..... [29283.479644] sdf: sdf1 [29283.482102] sd 4:0:0:0: [sdf] Attached SCSI removable disk [29283.882104] EXT4-fs (sdf1): mounted filesystem with writeback data mode. Opts: errors=remount-ro. Quota mode: none. fs is mounted!! > df -h .... /dev/sdf1 7,2G 1004M 6,1G 14% /run/media/leo/armbi_root > sudo umount /run/media/leo/armbi_root > sudo fsck.ext4 /dev/sdf1 e2fsck 1.46.4 (18-Aug-2021) armbi_root: clean, 28006/470112 files, 295400/1907712 blocks it is good The first three lines are for reference dmesg | tail - Get information where the SD card was mounted The disk with the SD card file system must be unmounted. If the fsck team finds bad blocks, it will ask questions. They must be answered in the affirmative. Sometimes it takes a long time. > sudo fsck.ext4 -fcy /dev/sdf1 e2fsck 1.46.4 (18-Aug-2021) Checking for bad blocks (read-only test): done armbi_root: Updating bad block inode. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information armbi_root: ***** FILE SYSTEM WAS MODIFIED ***** armbi_root: 28006/470112 files (0.1% non-contiguous), 295400/1907712 blocks fsck.ext4 -fcy - it is forced to check and fix (It took about 7 minutes).