aprayoga

Members
  • Content Count

    43
  • Joined

  • Last visited

Reputation Activity

  1. Like
    aprayoga reacted to flower in Helios64 Support   
    Sadly buster.13 is still unstable. Got this after a few hours without much load. 
     
    [ 8251.657645] ------------[ cut here ]------------
    [ 8251.658075] kernel BUG at arch/arm64/kernel/traps.c:470!
    [ 8251.658551] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
    [ 8251.659038] Modules linked in: iptable_nat iptable_filter bpfilter wireguard libchacha20poly1305 poly1305_neon ip6_udp_tunnel udp_tunnel libblake2s libcurve25519_generic libblake2s_generic veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink br_netfilter bridge governor_performance zstd zram r8152 snd_soc_hdmi_codec snd_soc_rockchip_i2s leds_pwm snd_soc_core panfrost pwm_fan gpio_charger hantro_vpu(C) gpu_sched snd_pcm_dmaengine snd_pcm rockchip_vdec(C) rockchip_rga v4l2_h264 snd_timer videobuf2_dma_sg videobuf2_dma_contig snd rockchipdrm v4l2_mem2mem dw_mipi_dsi videobuf2_vmalloc videobuf2_memops dw_hdmi videobuf2_v4l2 soundcore analogix_dp videobuf2_common drm_kms_helper cec rc_core videodev fusb30x(C) gpio_beeper mc drm drm_panel_orientation_quirks sg cpufreq_dt lm75 ip_tables x_tables autofs4 raid456 async_raid6_recov async_memcpy
    [ 8251.659153]  async_pq async_xor async_tx raid1 multipath linear raid10 raid0 md_mod realtek dwmac_rk stmmac_platform stmmac mdio_xpcs adc_keys
    [ 8251.667928] CPU: 4 PID: 0 Comm: swapper/4 Tainted: G         C        5.8.16-rockchip64 #20.08.13
    [ 8251.668710] Hardware name: Helios64 (DT)
    [ 8251.669062] pstate: 00000085 (nzcv daIf -PAN -UAO BTYPE=--)
    [ 8251.669564] pc : do_undefinstr+0x2ec/0x310
    [ 8251.669931] lr : do_undefinstr+0x1e0/0x310
    [ 8251.670296] sp : ffff800011abbd50
    [ 8251.670593] x29: ffff800011abbd50 x28: ffff0000f6ea5700 
    [ 8251.671067] x27: ffff0000f6ea5700 x26: ffff800011abc000 
    [ 8251.671540] x25: ffff8000114f1d20 x24: 0000000000000000 
    [ 8251.672012] x23: 0000000040000085 x22: ffff800010df6d90 
    [ 8251.672484] x21: ffff800011abbf00 x20: ffff0000f6ea5700 
    [ 8251.672956] x19: ffff800011abbdc0 x18: 0000000000000000 
    [ 8251.673428] x17: 0000000000000000 x16: 0000000000000000 
    [ 8251.673900] x15: 0000000000000006 x14: 00000d554264da40 
    [ 8251.674372] x13: 0000000000000322 x12: 000000000000036f 
    [ 8251.674844] x11: 0000000000000001 x10: 0000000000000004 
    [ 8251.675316] x9 : ffff0000f77a8590 x8 : ffff0000f77a7bc0 
    [ 8251.675788] x7 : ffff0000f6211dc0 x6 : ffff800011abbda8 
    [ 8251.676260] x5 : 00000000d5300000 x4 : ffff800011806118 
    [ 8251.676731] x3 : 0000000034000000 x2 : 0000000000000002 
    [ 8251.677203] x1 : ffff0000f6ea5700 x0 : 0000000040000085 
    [ 8251.677676] Call trace:
    [ 8251.677900]  do_undefinstr+0x2ec/0x310
    [ 8251.678240]  el1_sync_handler+0x88/0x110
    [ 8251.678591]  el1_sync+0x7c/0x100
    [ 8251.678886]  check_preemption_disabled+0x30/0x108
    [ 8251.679305]  __this_cpu_preempt_check+0x1c/0x34
    [ 8251.679710]  irq_exit+0x70/0xe0
    [ 8251.679996]  handle_IPI+0x25c/0x3e8
    [ 8251.680312]  gic_handle_irq+0x154/0x158
    [ 8251.680655]  el1_irq+0xb8/0x180
    [ 8251.680938]  arch_cpu_idle+0x28/0x218
    [ 8251.681269]  default_idle_call+0x1c/0x44
    [ 8251.681622]  do_idle+0x210/0x288
    [ 8251.681912]  cpu_startup_entry+0x28/0x68
    [ 8251.682265]  secondary_start_kernel+0x140/0x178
    [ 8251.682673] Code: f9401bf7 17ffff7d a9025bf5 f9001bf7 (d4210000) 
    [ 8251.683223] ---[ end trace 47af1c5026823974 ]---
    [ 8251.683636] Kernel panic - not syncing: Attempted to kill the idle task!
    [ 8251.684232] SMP: stopping secondary CPUs
    [ 8251.684588] Kernel Offset: disabled
    [ 8251.684903] CPU features: 0x240022,2000600c
    [ 8251.685275] Memory Limit: none
    [ 8251.685562] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]---
  2. Like
    aprayoga reacted to jbergler in Helios64 Support   
    @aprayoga if you still need it here's a full boot log of the crash (the actual stacktrace of the crash is inconsistent for me)
     
     
     
  3. Like
    aprayoga reacted to jbergler in Helios64 Support   
    If you, like myself, installed on eMMC and are experiencing the crashes on 20.08.14 - I booted up via a 20.08.10 sdcard and fixed the environment on emmc
     
    # mount the emmc + get ready to chroot mkdir /mnt/chroot mount /dev/mmcblk1p2 /mnt/chroot/ mount /dev/mmcblk1p1 /mnt/chroot/media/mmcboot mount --bind /mnt/chroot/media/mmcboot/boot/ /mnt/chroot/boot/ mount --bind /dev /mnt/chroot/dev/ mount --bind /proc /mnt/chroot/proc/ mount --bind /tmp /mnt/chroot/tmp/ # chroot in and downgrade to 20.08.10 chroot /mnt/chroot/ /bin/bash apt install \ linux-dtb-current-rockchip64=20.08.10 \ linux-headers-current-rockchip64=20.08.10 \ linux-image-current-rockchip64=20.08.10 \ armbian-config=20.08.10 \ armbian-firmware=20.08.10 \ linux-focal-root-current-helios64=20.08.10 \ linux-u-boot-helios64-current=20.08.10 exit # now remove the sd card and hit reset  
    @aprayoga It's probably unrelated, but while working through the above I noticed that I ran out of space on /boot.
    I installed to eMMC the first version that was working, if that helps. I chose f2fs when I installed on eMMAC and this is the resulting partition layout
    mmcblk1 179:32 0 14.6G 0 disk ├─mmcblk1p1 179:33 0 96M 0 part └─mmcblk1p2 179:34 0 14.3G 0 part mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk Sadly I didn't grab enough info from what was in the boot partition before I nuked it and reinstalled the appropriate packages.
     
  4. Like
    aprayoga reacted to inconsistant in Helios64 Support   
    Ran an update and now on 20.08.13 but getting errors immediately. Thought maybe it was something I had done so was preparing to start with a fresh install. First boot on SD with 20.08.13 gets the following error on boot.
     
     
  5. Like
    aprayoga got a reaction from gprovost in Helios64 Support   
    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.
     
  6. Like
    aprayoga got a reaction from gprovost in Helios64 Support   
    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.
     
  7. Like
    aprayoga got a reaction from ebin-dev in Helios64 Support   
    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
  8. Like
    aprayoga got a reaction from TDCroPower in Helios64 Support   
    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
  9. Like
    aprayoga got a reaction from TDCroPower in Helios64 Support   
    @TDCroPower
    The eMMC boot fixed on this PR . The wiki instruction more on new install using new u-boot that able to emulate eMMC as USB Mass Storage.
    You should wait new Armbian update
  10. Like
    aprayoga reacted to antsu in Helios64 Support   
  11. Like
    aprayoga got a reaction from TDCroPower in Helios64 Support   
    To summarize current status
     

     
    Feature Support Status Feature Legacy Remarks Current Remarks Shutdown Issue Failed to shutdown PMIC and trigger crash, HDD already parked OK   Reboot Issue Similar like shutdown but Watchdog trigger the reboot so it appear successful OK   Suspend to RAM Not Supported Yet Failed to resume operation after wake up Not Supported Yet USB host controller refuse to enter suspend mode 2.5G Ethernet OK   Performance Issue Slightly improved with tx offload disabled Main Power/UPS Status OK Status can be read from sysfs OK Status can be read from sysfs Battery Charging Status Not Supported   OK Charging and Full charge can be read from sysfs UPS configuration Not Supported Yet Need user-space tool to monitor power status and trigger shutdown Not Supported Yet Need user-space tool to monitor power status and trigger shutdown USB Type C - Host OK   Not Supported Yet There are some issue with fusb302 driver and USB Host Controller driver USB Type C - Gadget OK   Not Supported Yet There are some issue with fusb302 driver and USB Controller driver USB Type C - DisplayPort OK   Not Supported Yet There are some issue with fusb302 driver and DisplayPort alternate driver eMMC Install Not Supported Yet The bootloader unable to load rootfs from eMMC Not Supported Yet The bootloader unable to load rootfs from eMMC SPI Boot Not Supported Yet   Not Supported Yet   Recovery key Not Supported Yet System can enter maskrom mode but need special OS image and rkdevelop Not Supported Yet System can enter maskrom mode but need special OS image and rkdevelop  
    We are still working on eMMC issue.
     
     
  12. Like
    aprayoga reacted to Igor in Helios64 Support   
    After 
    https://github.com/armbian/build/commit/d18323fcc358ddd5bd0836c4853cbc281b6293c6
    images were updated to v20.08.8 while populating update packages around our servers takes up to 24h.

    I don't know if this will solve problems mentioned above.
  13. Like
    aprayoga reacted to Pedro Lamas in NanoPi M4V2 randomly crashes   
    Entering day 3 with "ondemand" governor, min 600000 and max 1800000, and the custom overlay @piter75 provided... no issues at all!! I think we're on to something here!!
  14. Like
    aprayoga got a reaction from chwe in NanoPi M4V2 randomly crashes   
    @piter75 @Pedro Lamas
    Helios64 also encounter some random crash, yesterday we tried to redefine opp just 408 MHz and 1.4/1.8 GHz and we don't see any random crash anymore.
    It seems similar DVFS problem as discussed in this thread. Then our customer point us to odroid n1 issue at
    https://forum.odroid.com/viewtopic.php?t=30303
    Maybe you can give it a try on Nano Pi M4v2.
     
    We are still testing on Helios64 (with value 40000), so far with reboot and power cycle does not trigger any kernel crash.
  15. Like
    aprayoga got a reaction from Pedro Lamas in NanoPi M4V2 randomly crashes   
    @piter75 @Pedro Lamas
    Helios64 also encounter some random crash, yesterday we tried to redefine opp just 408 MHz and 1.4/1.8 GHz and we don't see any random crash anymore.
    It seems similar DVFS problem as discussed in this thread. Then our customer point us to odroid n1 issue at
    https://forum.odroid.com/viewtopic.php?t=30303
    Maybe you can give it a try on Nano Pi M4v2.
     
    We are still testing on Helios64 (with value 40000), so far with reboot and power cycle does not trigger any kernel crash.
  16. Like
    aprayoga got a reaction from Userlab in Helios64 Annoucement   
    as mentioned by @Werner, RK3399 runs best on the legacy, 4.4 kernel. Mainline, (LK 5.4), for example, still have some issue on DP over TypeC.
    We ran some burn-in test (stress-ng for cpu, parallel fio on all sata port, all usb port, emmc and microsd) under LK 4.4. we didn't encounter stability issue in 24 hours.
    Similar like Helios4, Helios64 will have legacy and current support.
     
    i have tried similar riser from Amazon, as you can see on following pictures, the riser is too long

     
    and M.2 modem is too wide

     
     
  17. Like
    aprayoga reacted to FrancisTheodoreCatte in Helios4 Support   
    After upgrading to the 4.19.104-mvebu kernel I also started experiencing the same complete cpu lockups, but here's the kicker: the lockups are continuing, even after downgrading to kernel 4.14.171-mvebu.
     
    Easy way for me to trigger it is by running echo check > /sys/block/md0/md/sync_action
     
    I managed to catch the CPU stall via the serial console:
    https://pastebin.com/C8yCQMAn
     
    Here's the output from armbianmonitor -u:
    http://ix.io/2h03
     
    edit:
    same lockup still happens when running an md data-check even after downgrading further, to 4.14.153-mvebu.
  18. Like
    aprayoga reacted to Heisath in Helios4 Support   
    Hi Xavier,
     
    Kernel 5.5 is currently not supported by us. Our current kernel 4.19 has complete hardware support, dev kernel (5.4; which you need to compile yourself with https://github.com/armbian/build) should also have working PWM. 

    If you need to use Kernel 5.5 you are on your own, you can try to use the patches from 5.4 (https://github.com/armbian/build) to get PWM working...
     
    Cheers,
    count-doku
  19. Like
    aprayoga reacted to Heisath in Armbian 20.02 (Chiru) Release Thread   
    Looks good, I like the definitive freeze / release dates. 
     
    I will do remaining work (mostly testing recent mvebu changes on Helios4) today.
     
    Another dev: @aprayoga
     
    EDIT:
    Not worth the extra post, I completed testing on Helios4 and Clearfog looks good:
    mvebu-legacy
        Helios4 lk 4.14.y u-boot 2018.11-armbian
       http://ix.io/27Ou
     
        Clearfog (Pro) lk 4.14.y u-boot 2018.01-armbian
        * SFP working but only up to 1Gbps    
       http://ix.io/27OL
     
    mvebu-current
        Helios4 lk 4.19.y u-boot 2019.04-armbian
       http://ix.io/27Ox  
     
        Clearfog (Pro) lk 4.19.y u-boot 2018.01-armbian
        * SFP working but only up to 1Gbps
       http://ix.io/27OM
  20. Like
    aprayoga got a reaction from gprovost in Helios4 Support   
    Between middle-to end of November 2019, Armbian change the version and branch naming.
    Version from something like 5.91 become something like 19.11.x, if i'm not mistaken Year.Month, like Ubuntu versioning.
    Then the branch name,
    DEFAULT become LEGACY NEXT become CURRENT To upgrade to new version, use armbian-config.
    sudo apt-get update sudo apt-get -y upgrade sudo armbian-config
     
    Select System > Other, to switch to other kernel

     
    Confirm the action

     
    And after some process, you will be presented by list of kernels

     
    Select linux-image-current-mvebu. The system will install the new kernel and automatically reboot.
    Confirm the kernel installed correctly and Armbian changed to new branch CURRENT by executing,
    uname -a grep "BRANCH" /etc/armbian-release  
  21. Like
    aprayoga reacted to Igor in Helios4 Support   
    Armbian buster with Linux 5.4.6-rockchip:
    I could change locales as expected and keyboard and CPU speed as well (on console). No issues here. Everything works as expected. http://ix.io/25TY
     
    It is normal that cpu-freq throws errors out ... since we don't have driver in 4.19.y ... well it could be suppressed. But the rest must work.
  22. Like
    aprayoga reacted to sirleon in Helios4 Support   
  23. Like
    aprayoga got a reaction from gprovost in Helios4 Support   
    Good to hear you got it working.  I tried the instructions first on my system and did not encounter such error. Could you share your u-boot version?
     
     
    I test on fresh Armbian_19.11.3_Helios4_buster_current_4.19.84.img
     
    1. I don't encounter such error when accessing the system from Windows using PuTTY or thru serial console
       UPDATE: i tried to SSH from my Ubuntu machine (got id_ID locale), indeed there are perl warning regarding locale but armbian-config is still usable to generate the locale, no need to manually edit file. After the locale generated by armbian-config, no more perl locale warning.

    2. Confirmed
    3. Confirmed.
    cat: /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies: No such file or directory cat: /sys/devices/system/cpu/cpufreq/policy0/scaling_available_governors: No such file or directory /usr/lib/armbian-config/jobs.sh: line 1075: Error: Expected at least 5 tokens for --menu, have 4. Use --help to list options. / 1000: syntax error in expression (error token is ": Expected at least 5 tokens for --menu, have 4. Use --help to list options. / 1000") The path is not exist, even though the driver is compiled. I will need to investigate further.
    ---
    I also tried using fresh Armbian 5.91 then upgraded to Armbian 19.11.3, but strangely i don't see the System - CPU menu.

     
    4. As mentioned on @sirleon link, apparently Buster make use nftables by default and on our kernel is not enabled. You could try to switch to iptables-legacy version.
    CONFIG_NF_TABLES=m CONFIG_NF_TABLES_SET=m # CONFIG_NF_TABLES_INET is not set # CONFIG_NF_TABLES_NETDEV is not set # CONFIG_NF_TABLES_IPV4 is not set # CONFIG_NF_TABLES_ARP is not set # CONFIG_NF_TABLES_IPV6 is not set # CONFIG_NF_TABLES_BRIDGE is not set meanwhile, i will try to enable those modules and test.
     
    @Igor, could you take a look whether armbian-config issues also occur on other board?
  24. Like
    aprayoga got a reaction from gprovost in Helios4 Support   
    Hi @sirleon, the tutorial is intended for moving the rootfs to USB thumb drive and due to spi_workaround it does not work with SATA seamlessly but you almost there..
    I suggest to move the rootfs to drive that connected to SATA0 (most likely /dev/sda), because there is known issue that u-boot failed to recognized SATA device other than on SATA0.
     
    To boot from SATA you need to:
    1. Move the rootfs with sata-nand-install while spi_workaround is disabled, and reboot.
        The system will boot from SD card.
    2.  Unmount /boot and copy over boot files from /media/mmcboot/boot to /boot
    umount /boot cp -rf /media/mmcboot/boot/* /boot/ 3.  Edit /etc/fstab and remove/comment 2 lines that have mount point to /media/mmcboot and /boot.
    4.  Reboot the system and cancel u-boot auto boot.
    5.  Run following commands on u-boot prompt to add sata boot and reboot
    setenv boot_targets "usb0 scsi0 mmc0 pxe dhcp" setenv bootcmd_scsi0 'devnum=0; run scsi_boot' saveenv You could reorder the boot order on boot_targets variable. On above command, it would tried to boot from USB and if failed try SATA/SCSI and so on.
     
  25. Like
    aprayoga got a reaction from sirleon in Helios4 Support   
    Hi @sirleon, the tutorial is intended for moving the rootfs to USB thumb drive and due to spi_workaround it does not work with SATA seamlessly but you almost there..
    I suggest to move the rootfs to drive that connected to SATA0 (most likely /dev/sda), because there is known issue that u-boot failed to recognized SATA device other than on SATA0.
     
    To boot from SATA you need to:
    1. Move the rootfs with sata-nand-install while spi_workaround is disabled, and reboot.
        The system will boot from SD card.
    2.  Unmount /boot and copy over boot files from /media/mmcboot/boot to /boot
    umount /boot cp -rf /media/mmcboot/boot/* /boot/ 3.  Edit /etc/fstab and remove/comment 2 lines that have mount point to /media/mmcboot and /boot.
    4.  Reboot the system and cancel u-boot auto boot.
    5.  Run following commands on u-boot prompt to add sata boot and reboot
    setenv boot_targets "usb0 scsi0 mmc0 pxe dhcp" setenv bootcmd_scsi0 'devnum=0; run scsi_boot' saveenv You could reorder the boot order on boot_targets variable. On above command, it would tried to boot from USB and if failed try SATA/SCSI and so on.