Jump to content

aprayoga

Members
  • Posts

    138
  • Joined

  • Last visited

Everything posted by aprayoga

  1. @JohnnyMnemonic no, it does not disable the ability to use USB-C for a terminal. On your PC there will be 2 device connected, one is USB serial and the other one is LInux File-Stor Gadget. Under Linux, the DAS acting as USB 3.0 device while under bootloader (U-Boot) it acting as USB 2.0 device (shared with USB serial signals)
  2. could you attached the log? full console message since power on
  3. @ShadowDance have you tried to unplug and replug the SATA cable from the board? I have similar issue (reset link and downgraded to 3.0 Gbps) in the past and it was fixed after i unplug and replug the sata cable. At that time i used off the shelf sata cable, atx power supply and 5x 2.5" sandisk sata ssd I tried to reproduce issue with hardware i have, 3x WD20EFRX and 2x ST1000DM010-2EP102. The WD drives connected to SATA port 3, 4, 5 and configured as mdadm raid 5. I scrub the array which took ~4hrs to finish. no ata issue occurred. then i prepared the drive for hotplug, mdadm -S md127 echo 1 > /sys/block/sdc/device/delete remove the drive, wait for a while then replug the drive and re-assemble the array. The drive still connected at 6.0Gbps The log I use Armbian 20.11 Buster (LK 5.9.10) for the test
  4. Can you manually control the fan speed by following instruction on our wiki ? make sure to stop fancontrol beforehand. sudo systemctl stop fancontrol use 0 to stop the fan and 255 to set full speed.
  5. @slymanjojo to use DAS on LK 5.9, you would need to configure the USB-C as device mode. In your helios64, create a file dwc3-0-device.dts contains following code /dts-v1/; /plugin/; / { compatible = "rockchip,rk3399"; fragment@0 { target = <&usbdrd_dwc3_0>; __overlay__ { dr_mode = "peripheral"; }; }; }; add and enable to user overlay sudo armbian-add-overlay dwc3-0-device.dts and reboot Now, you can follow instruction on our wiki to enable DAS. If you are using Windows, you might need to unplug and replug the usb cable after enabling the DAS mode. --- If you want to use USB-C in Host mode, you need to remove folloing line from /boot/armbianEnv.txt user_overlays=dwc3-0-device and enable host mode overlay on armbian-config > System > Hardware and tick dwc3-0-host
  6. Could you try to install using Maskrom mode ?
  7. @jbergler Could you try the attached u-boot ? This u-boot contains updated Rockchip blob (DDR driver & ATF) install with dpkg -i linux-u-boot-current-helios64_20.11.0-trunk_arm64.deb After that, run armbian-config > System > Install > 5 Install/Update the bootloader on SD/eMMC If you are using SD card, make sure to clean bootloader on the eMMC. you can run dd if=/dev/zero of=/dev/mmcblk1 seek=64 count=30000 Power cycle the system. The system should boot with new bootloader. Please take note at binaries version DDR Version 1.24 20191016 RevNocRL NOTICE: BL31: Built : 14:31:03, May 19 2020 U-Boot 2020.07-armbian (Nov 25 2020 - 07:14:05 +0700) Try to trigger the kernel crash. --- If you want to restore the original u-boot you can run apt install linux-u-boot-helios64-current=20.08.21 and update the u-boot using armbian-config --- There is built in memory tester on Linux kernel, just add this line to /boot/armbianEnv.txt extraargs=memtest=10 you can change number of loop (10). It took quite some time to run the test. you can see the result using dmesg linux-u-boot-current-helios64_20.11.0-trunk_arm64.deb
  8. 1. As mentioned on wiki, you can download the driver from https://www.ftdichip.com/Drivers/VCP.htm 2. Which fan connector that does not work? Could you try to swap the fan, to check whether this is fan problem or the control signal.
  9. Did you follow the instruction and binaries from the wiki ? I recall got the "Test Device Fail" message when i used old version of DriverAssistant and AndroidTool.
  10. @Protxch the error led should not turned on, since it's software controlled. Make sure the front panel does not touch the casing
  11. LEGACY branch (Linux Kernel 4.4) Feature Support Status Remarks Shutdown Partial Fails to shutdown PMIC and triggers crash, HDD already parked Reboot Partial Similar like shutdown but Watchdog triggers the reboot so it appears successful Suspend to RAM Not Supported Fails to resume operation after wake up 2.5G Ethernet (2.5G speed) OK 2.5G Ethernet (1G speed) Performance issue Requires hardware fix. Main Power/UPS Status OK Status can be read from sysfs Battery Charging Status Not Supported UPS configuration OK Auto shutdown after 10 min of power loss. USB Type C - Host OK USB Type C - Gadget OK Use g_mass_storage kernel module 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 LAN LED Not Supported Wake On LAN Not Supported Suspend still have issue Armbian 21.02
  12. What was the max cpu freq you set? Could you try with performance governor at 1.2GHz and at 816 MHz? How did you load the system? Did you encounter kernel crash on 20.08.10 ?
  13. @i5Js maybe similar issue with the one we encounter on Helios64. The PCIe SATA controller failed in PCIe Gen1 training if Linux kernel do a reset through ep-gpio. you can try to remove ep-gpios on nano pi device tree like in this commit: https://github.com/armbian/build/pull/2213/files#diff-f8fb8dd7f6933c824a8b57561c4ed874d35aae33928cc1b5c797ae5d035a3cddR19
  14. To continue discussion from Helios64 Support Could you boot from micro SD card? Please use Armbian 20.08.10 image, version 20.08.13 known to have stability problem on many users. After setting up Armbian on the micro SD, reboot (to finish the setup) and login as root, you can check eMMC for filesystem error fsck -p /dev/mmcblk1p1 You can try to change the password of Armbian on the eMMC: After finished you can poweroff the system, remove the micro SD card and power on the system again. See if you can boot to your system on eMMC.
  15. To continue discussion from Helios64 Support Noted, we will enable ZFS support after Armbian 20.11 released. I will need your help to test since i don't have system with ZFS.
  16. To continue discussion from Helios64 Support Currently there is no plan to support to disable the power but it's interesting to know such use case. If we implemented this feature, you would need to go u-boot prompt to enable and disable the power. would this acceptable for you? Under Linux device tree, the power rail declared as regulator node with regulator-always-on property. This prevent kernel (and user) to turn off the regulator. Unless we are able to create device node for the SATA port, to act as consumer of the regulator, we can't remove the regulator-always-on property.
  17. 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 OK default to eth0 activity Wake On LAN Not Supported Suspend still have issue Armbian 21.02
  18. It seem you get a kernel crash. You should connect to serial console to get the kernel crash log. The network activity led is still not implemented yet. You are using old U-Boot. It couldn't get the required device tree file. There was file renaming applied to Armbian 20.08.8 (released on 13 Oct 2020). You can do 1. Get serial console 2. When U-Boot appear, spam Enter key until you get U-Boot prompt (=> ) 3. enter this command setenv fdtfile "rockchip/rk3399-kobol-helios64.dtb" bootd 4. After boot to Linux and login create symlink to new dtb sudo ln -sf rk3399-kobol-helios64.dtb /boot/dtb/rockchip/rk3399-helios64.dtb 5. Upgrade the bootloader using armbian-config, System > Install > 5 Install/Update the bootloader on SD/eMMC On next boot you should see U-Boot with more recent build date. Unfortunately the Reset and Power button wired directly to PMIC and no configuration on the PMIC to disable it. However, short press Power button (graceful shutdown) can be disabled by editing /etc/systemd/logind.conf and set HandlePowerKey=ignore
  19. You should see something like this when capturing serial console from power on We are investigating what change causing this crash, what changes on upstream kernel could have an impact. Meanwhile, if you want to revert to previous kernel, 5.8.14, used on Armbian 20.08.10, you could use armbian-config > System > Other or you could also get previous image from https://archive.armbian.com/helios64/archive/
  20. I forgot to answer this. the power staggering is handled by bootloader and not user configurable. We have tested various HDD brand/model and the highest current during spin up can go up to 7 seconds. We are considering the delay to be user configurable in future. Strange, that kind of crash should be fixed since 20.08.8. I don't encounter such crash on latest image. Could you get the serial console log start from power up?
  21. Could you try edit the /boot/armbianEnv.txt and add idVendor and idProduct of your drive to usbstoragequirks ? usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x174c:0x5106:u,0x1e68:0x003a:u reboot the system and see whether your external USB drive can be recognized.
  22. The LED brightness is not adjustable. You would need to use semi transparent plastic/tape to reduce the brightness, or change the resistor on front panel board. Does FTDI USB serial still connected to your PC? That image should switch USB MUX to RK3399 internal USB and you would see the FTDI disconnected on your PC. On Windows, if you ever installed rockusb driver then you would need uninstall it otherwise it will be recognized as rockusb device instead of usb drive. How did you test? After remove the file, shutdown the system and unplug the power supply, then the system would automatically power on without need to press power button when power supply re-plugged. Ah i just remember, do you have RTC battery or the UPS battery? the batteries is needed to make auto power on working correctly. More info will be described on the wiki. As mentioned by @flower, those are just symlinks generated by udev rules. The reason is similar like we have done in Helios4, the hwmon order could be changed depend on kernel version or kernel module loading order. With this symlink, fancontrol configuration can just refer to /dev/fan-*. The first boot should not take time more than 5 minutes, unless you were using 64GB/128GB card. As suggested by other, you need to shave the cable so it can connect properly. You definitely need access to serial console for system setup. You could get supply for your fan from pin 1 or 2 and pin 3 on GPIO header but i'm not sure whether the additional fan would help much.
  23. Armbian 20.08.10 has been released with eMMC boot fixed. Please do a fresh install. If you want to boot from eMMC, you can transfer using armbian-config > System > Install > 2 Boot from eMMC - system on eMMC
  24. you could re-enable auto power on by removing /lib/systemd/system-shutdown/disable_auto_poweron . You can check the file to see how to control the gpio pin for the auto power on feature. The auto power on is always enabled by bootloader. As @flower answered, SPI boot is not yet working. Theoretically after boot from SPI you could change boot target to first SATA drive
  25. You could use armbian-config, System->Other to switch branch but we are not recommend it. It might break the system. You can poll /sys/class/power_supply/gpio-charger/online to check main power supply status. Yes, this is performance issue mentioned on our table. Our iperf test shown, only a few first transfer correctly at 2.5gbits
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines