• Posts

  • Joined

  • Last visited

Everything posted by aprayoga

  1. @mortomanos looks like something wrong with the eMMC. It works intermittently. on your first log, there are several error like this [ 3.351947] mmc1: mmc_select_hs200 failed, error -110 [ 3.352420] mmc1: error -110 whilst initialising MMC card On your second log, it failed for several times but finally it initialized [ 3.577160] mmc1: mmc_select_hs200 failed, error -110 [ 3.577624] mmc1: error -110 whilst initialising MMC card [ 3.577761] of_cfs_init [ 3.578449] of_cfs_init: OK [ 3.631765] usb 3-1: New USB device found, idVendor=2109, idProduct=2815, bcdDevice= 7.04 [ 3.632503] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.633140] usb 3-1: Product: USB2.0 Hub [ 3.633594] usb 3-1: Manufacturer: VIA Labs, Inc. [ 3.685522] hub 3-1:1.0: USB hub found [ 3.686115] hub 3-1:1.0: 4 ports detected [ 3.739853] mmc1: Command Queue Engine enabled [ 3.740269] mmc1: new HS200 MMC card at address 0001 [ 3.741441] mmcblk1: mmc1:0001 AJTD4R 14.6 GiB [ 3.742111] mmcblk1boot0: mmc1:0001 AJTD4R partition 1 4.00 MiB [ 3.742891] mmcblk1boot1: mmc1:0001 AJTD4R partition 2 4.00 MiB [ 3.743579] mmcblk1rpmb: mmc1:0001 AJTD4R partition 3 4.00 MiB, chardev (243:0) [ 3.745394] mmcblk1: p1 Could you check whether you have P10 jumper enabled?
  2. As we have mentioned on the wiki, you can watch the System LED as visual cue. When it blink once, release the button. There are roughly 2 second delay to release the button. https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-rockchip64-mainline/general-support-recovery-button.patch#L131-L137 Another visual cue you can check is through serial console. U-Boot 2020.07-armbian (Nov 23 2020 - 16:22:15 +0100) SoC: Rockchip rk3399 Reset cause: POR DRAM: 3.9 GiB PMIC: RK808 SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB MMC: mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Helios64 Revision: 1.2 - 4GB non ECC using mmc0 device for download mode rockchip_dnl_mode = ums mode as soon as you see rockchip_dnl_mode = ums mode, release the button.
  3. You can check the PSU by measuring the output voltage. You can check the motherboard by following instruction on the older support thread. You can also find our recommendation for replacement PSU
  4. Do you have OMV installed? Last time (long time ago) I tried to install both, it left my system broken due to dependencies conflict. Is this after you installed Nextcloud? Are you able to access Helios4 through serial console? Does the network interface connected and got IP?
  5. No, that is not an issue. Please provide complete serial console log. Is this the first time setup? Did you upgraded from previous version? Where did you install the Armbian, eMMC or micro SD card?
  6. Providing logs with armbianmonitor -U helps with troubleshooting and significantly raises chances that issue gets addressed. copy paste the log here Did you mean via USB-C serial console? Which network interface you use? on Armbian 20.11.3, the driver for eth1 (2.5Gb Ethernet) accidentally removed. Have you tried the 1G ethernet?
  7. @jlaurencin it's just a warning, not a problem. https://www.denx.de/wiki/view/DULG/WarningBadCRCUsingDefaultEnvironment
  8. @Niglix How did you install the OMV? using armbian-config? The installation process took roughtly half an hour. You can use serial console to access your Helios64 if for some reason the network down. You would also see screen like this in serial console after OMV installed
  9. The buzzer pin on Helios64 is designed for active buzzer. The one on your photo is passive buzzer. Passive buzzer requires the system to generate tone while the active one, system just need to supply power (on/off switch). The buzzer itself that generate the tone. you can buy the passive buzzer at electronic component store, the one that sell Arduino etc.
  10. @obynio since you have a Linux system, could you modified the /boot/armbianEnv.txt ? add following lines console=serial earlycon=on extraargs=ignore_loglevel you could modify the file on the sdcard if you are going to test with sd card. or you could also modify the file on eMMC by mounting it in ums mode.
  11. Apparently @Igor removed the driver in this commit. The driver in mainline kernel, only support RTL8152/R8153
  12. @Cpz, Orange light up if the link speed 1G (and 2.5G on eth1) and green if the link speed is 10/100M. either led will blink/flashing when there is network activity. As already suggested by @m11k, you should get log from serial console.
  13. @0utc45t, try legacy image. if it still not working, make sure your cable has converter chip inside. There are at least 2 standards regarding display signal in USB Type-C. one is DisplayPort Alternate Mode, which is the one supported on Helios64 (RK3399) and the other one is HDMI Alt mode. If you have cable that use HDMI Alt mode, it won't work on Helios64. @RussianNeuroMancer, yes. on legacy, HDMI+Hub combo working fine. The problem with mainline driver, it does not support OTG. You have to define the port as "host" or "peripheral" in device tree. That PR comment, before i knew https://github.com/armbian/build/pull/2299 HDMI+hub combo working fine in LK5.9 if you also enable rockchip-dwc3-0-host overlay.
  14. there are several other packages than 'linux-current-image' to switch. You could use armbian-config > System > Other to switch to current. That being said, we are still recommend to do fresh install using CURRENT image rather than switch from LEGACY.
  15. @mortomanos do you have other Linux system ? edit the boot/armbianEnv.txt and add extraargs=ignore_loglevel
  16. I don't recall if i ever have issue with 1G ethernet. Was it idle? regarding USB-C support, what do you want to do? Currently the only issue with USB C support in LK 5.9 is switching role "on the fly".
  17. yes, mv_xor loaded late. i think after async_tx loaded. mdadm RAID5 use the xor engine
  18. @mortomanos Did you manage to see the problem in serial console?
  19. @FloBaoti you can get 2.14 source from https://github.com/wget/realtek-r8152-linux and compile using docker similar like in this thread
  20. Maybe it is not necessary and rely on SATA soft reset. U-Boot definitely needs to be modified to differentiate reboot and power on.
  21. That is strange. First it won't stop after shutdown, then now it won't run at all. when it stopped? after running sudo systemctl stop fancontrol ? or since power on?
  22. @Z06Frank you can create the file at your home (~) folder, the armbian-add-overlay will do the rest
  23. yes, TDM3421 is implemented as high-side switch. According to your measurement, indeed, the MOSFET seems faulty
  24. @Zageron run echo ledtrig-netdev | sudo tee -a /etc/modules add the modules into auto load list. apparently /etc/modules is not modified during upgrade.