aprayoga

  • Posts

    138
  • Joined

  • Last visited

Everything posted by aprayoga

  1. @mrjpaxton Yes, it is a known issue. Try the following workaround on the other thread
  2. Hi @crosser, what Armbian version do you use? Could elaborate what did you do with the NFS? Maybe you were doing big file transfer.
  3. Hi everyone, thank you for all of your support. I'll be still around but not in full time as before. I saw Helios64 has several issues in this new release. I will start looking into it.
  4. Hi all, you could download the SATA firmware update at https://cdn-kobol-io.s3-ap-southeast-1.amazonaws.com/Helios64/SATA_FW/Helios64_SATA_FW_update_00021_200624.img.xz Instruction: 1. Download the sd card image 2. Flash the image into a microSD card 3. Insert microSD card into Helios64 and power on. Helios64 should automatically boot from microSD. If Helios64 still boot from eMMC, disable the eMMC 4. Wait for a while, the system will do a reboot and then power off if firmware flashing succeed. If failed, both System Status and System Fault LEDs will blink 5. Remove the microSD card and boot Helios64 normally. See if there is any improvement. Our officially supported stock firmware can be downloaded from https://cdn-kobol-io.s3-ap-southeast-1.amazonaws.com/Helios64/SATA_FW/Helios64_SATA_FW_factory_00020_190702.img.xz. If there is no improvement on newer firmware, please revert back to this stock firmware. SHA256SUM: e5dfbe84f4709a3e2138ffb620f0ee62ecbcc79a8f83692c1c1d7a4361f0d30f *Helios64_SATA_FW_factory_00020_190702.img.xz 0d78fec569dd699fd667acf59ba7b07c420a2865e1bcb8b85b26b61d404998c5 *Helios64_SATA_FW_update_00021_200624.img.xz
  5. It could be caused by power supply failure. Could you check the following thread ?
  6. ## Executing script at 09000000 Bad Linux ARM64 Image magic! @scottf007, it could be filesystem corruption or something wrong during update and kernel symlink was not updated to correct file. If you have access to Linux PC, you can use recovery button to enter UMS mode and do fsck or fixed the symlink. @wurmfood, it is not a problem. Rockchip loader expect the storage to be partitioned and formatted in certain way but it also can load using raw offset. Armbian does not use GPT, so the loader will print such errors.
  7. @SIGSEGV @clostro the service is triggered by udev rules. @wurmfood, I didn't realize the timer fill the the log every 20s. Initial idea was one time timer, poweroff after 10m of power loss event. Then it was improved to add polling of the battery level and poweroff when threshold reached. Your script look good, we are considering to adapt it to official release. Thank you
  8. Thank you for the report. The error code is different compared to the one reported here, which already fixed on this PR. We will investigate this issue
  9. bus-width 4 because of microsd card, not eMMC. As we already put warning note on our wiki, it is not supported out of box, because it could break the system. There are several cards that are not compatible and show error during the test. When those card used as boot drive (for the test, Helios4 boot from USB drive), it won't boot. Too risky to be included out of box. IMO, the card and the host controller should try to use lower/normal speed if higher one failed. but we don't see such case during our test.
  10. @jbergler could you modify /boot/armbianEnv.txt and add/modify following lines: verbosity=7 console=serial extraargs=earlyprintk ignore_loglevel It should make the serial console more verbose and output the systemd services to serial. Could you also post a step by step to set up and reproduce the crash? maybe also the detail of ZFS pool and HDD model and size.
  11. @antsu Could you post a step by step to set up and reproduce the crash? maybe also the detail of ZFS pool and HDD model and size.
  12. @crosser please modify /boot/armbianEnv.txt and add/modify following lines: verbosity=7 console=serial extraargs=earlyprintk ignore_loglevel It should make the serial console more verbose. mortomanos is referring to Armbian Device Tree Overlays
  13. The bootloader (u-boot) is configured to try loading OS from SD card first, then if it failed, it will try internal eMMC. You need to remove the jumper just before Linux initialized, otherwise the eMMC would not be detected. More info on our wiki.
  14. @kabo is this new fresh sd card image? I assume it is not, looking on u-boot build date that is quite old. Did you recently update & upgrade the Armbian? You can try my instruction on following thread:
  15. @JMCC Thanks for the hint. i'll take a look.
  16. @qrthi it seems something wrong during writing to eMMC. Your log show these lines Wrong image format for "source" command SCRIPT FAILED: continuing... How did you write the image? We recommend to use Etcher because it has write verification. The boot mode jumper only needed if for some reason the bootloader corrupted and to fix it you need to completely bypass the boot device. If the bootloader (u-boot) just fine, it will load Armbian from the sdcard first. The "Card did not respond to voltage select" is because you removed the sdcard. If you put Armbian sdcard, the lines would be Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 6 ms (517.6 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 My suggestion, 1. Download latest Armbian image. 2. Since you already have u-boot on your eMMC, no need to download and write the helios64_sdcard_u-boot-only.img.xz into sdcard. 3. Power on and enter UMS recovery mode 4. Write the image using Etcher. No need to extract the image. Etcher can handle it just fine. 5. Reboot Helios64.
  17. What do you mean? Have you managed to get serial console working? Have you checked our wiki?
  18. @apocrypha, theoretically Helios4 could support USB gadget since the SoC support USB OTG at one of the USB controller, i forgot which one, upper or lower. Unfortunately, Helios4 does not have circuitry to support this operation. Both of the USB is USB Host only. If you're referring to the micro usb port, it is not part of the USB controller of the armada 388. it using external USB to Serial converter IC
  19. @lalaw unfortunately i never use Mac, i have no idea why it always recognized only 210 GB.
  20. Did you see any error during upgrade? If there is no error, then it should be safe to reboot. There is no automated method that i'm aware of. You could modify the rootdev=UUID= to point to UUID of the SATA partition. Modify /etc/fstab on the SATA drive, find line with /media/mmcboot , change the existing UUID to UUID of the eMMC sudo blkid use the value of UUID not PARTUUID
  21. @Mydogboris the system could be encounter kernel crash. Have you tried to limit the cpu speed and governor? Change CPU governor to Performance, and optionally reduce the CPU speed to keep the system run cool. armbian-config > System > CPU Minimum CPU speed = 1200000 Maximum CPU speed = 1200000 CPU governor = performance
  22. CURRENT branch (Linux Kernel 5.10) Feature Support Status Remarks Shutdown OK Reboot OK Suspend to RAM Not Supported USB host controller refuses to enter suspend mode 2.5G Ethernet (2.5G speed) OK TX offload disabled by default, can be enabled for better performance 2.5G Ethernet (1G speed) Performance issue Requires hardware fix. Main Power/UPS status OK Status can be read from sysfs Battery Charging OK Status can be read from sysfs UPS configuration OK Auto shutdown after 10 min of power loss. USB Type C - Host OK use dwc3-0-host overlay. Enable P13 jumper to be able to use USB 2.0 device. USB Type C - Gadget OK use overlay to enable USB device mode. refer to this link USB Type C - DisplayPort OK eMMC Boot OK SPI Boot Not Supported Recovery Button OK To use maskrom, jumper P13 must be enabled. USB LED Not Supported usbport led trigger does not support activity and only works with USB 2.0 device LAN LED Supported default to eth0 activity Wake On LAN Not Supported Suspend still have issue Armbian 21.02 Note: - UPS action will be changed into based on battery voltage threshold rather than countdown timer. (PR 2259) - To change LAN LED network device, change eth0 on /etc/systemd/system/helios64-heartbeat-led.service at line 9 into eth1
  23. @edwinistrator we did recommend the Debian maintainer to try the following tweak at that time, and according to Uwe, it does improve the stability. currently we still use the lower freq but we are considering to also disable those lower freq and maybe also disable DVFS (just use one fixed clock speed), since we received many instability reported and some has good outcome when cpu clock limited to 1200 MHz.
  24. yes, it is expected since pressing the reset button will force the system reset and skip graceful shutdown procedure, which one of the step flaggging the filesystem as clean. therefore next boot will read the filesystem dirty and do fsck to checck if there is any corruption. Have you tried to limit the cpu speed and governor? Change CPU governor to Performance, and optionally reduce the CPU speed to keep the system run cool. armbian-config > System > CPU Minimum CPU speed = 1200000 Maximum CPU speed = 1200000 CPU governor = performance
  25. i have no idea why. Initially i thought you were exporting just the partition but your next reply show you exported the whole array. Any error or warning on Mac side? don't export just the partition (sdf1) but the whole disk (sdf). It does not have partition table.