Jump to content

TDCroPower

Members
  • Posts

    83
  • Joined

  • Last visited

Reputation Activity

  1. Like
    TDCroPower reacted to Igor in Upgrading to Bullseye (troubleshooting Armbian 21.08.1)   
    eMMC troubles has been reported on other RK3399 boards such as Nanopi T4. Since we didn't do anything in this area I suspect someone pushed bad code upstream. Need analysis, while I don't see possibility to check and fix in the following weeks. 
  2. Like
    TDCroPower reacted to ebin-dev in Upgrading to Bullseye (troubleshooting Armbian 21.08.1)   
    This was already answered in this thread.
     
     
  3. Like
    TDCroPower reacted to IcerJo in Upgrading to Bullseye (troubleshooting Armbian 21.08.1)   
    Thank you for the Rsync guide, I'm going to give this a try real quick, I had to modify the parameters since i had my usb SD card reader mounted as /media/USB, the rsync just finished. I'm going to shutdown, and pop the SD Card in and see what happens
     
  4. Like
    TDCroPower reacted to ebin-dev in Upgrading to Bullseye (troubleshooting Armbian 21.08.1)   
    The easiest way to downgrade linux on emmc now would be to copy those files to /mnt/system (root directory of your emmc) - and then change root with  'chroot /mnt/system' and install the packages with 'dpkg -i *.deb'   (while your active system is on SD).
     
    You can leave the chrooted environment by typing 'exit'. emmc should now be bootable again. If not, you need to update the bootloader on emmc as described earlier in this thread.
  5. Like
    TDCroPower reacted to IcerJo in Upgrading to Bullseye (troubleshooting Armbian 21.08.1)   
    I opted to just setup an SD Card with the latest, and redo my OMV install on it, since that's technically all I use it for at this time, I was able to get the old system booted with no problems by pushing re-pushing the bootloader but wasn't able to install the Deb files, and I am not that confident in my linux skill set, though i learned a few new tips and tricks during the troubleshooting! I'll repush to EMMC once issues have eventually been resolved, or i may downgrade the kernel and push, i'll see later.
     
    Thank you @ebin-dev for your advice and assistance and thank you @TDCroPower for the RSync article!
  6. Like
    TDCroPower got a reaction from IcerJo in Upgrading to Bullseye (troubleshooting Armbian 21.08.1)   
    ok i got a little further.
    I wrote the armbian image 21.02.3 with 5.10.21-rockchip64 on a SD and triggered the boot from microSD via jumper 10...
    https://wiki.kobol.io/helios64/troubleshoot/#how-to-force-boot-from-microsd
     
    i am back on the box and was able to mount the emmc under /dev/mmcblk2p1...
     
    root@helios64:~# ll /mnt/ total 0 root@helios64:~# mkdir -p /mnt/system root@helios64:~# mount /dev/mmcblk2p1 /mnt/system root@helios64:~# cd /mnt/system/ root@helios64:/mnt/system# ll total 80 lrwxrwxrwx 1 root root 7 Aug 30 2020 bin -> usr/bin drwxr-xr-x 3 root root 4096 Sep 1 03:01 boot drwxr-xr-x 2 root root 4096 Oct 15 2020 dev drwxr-xr-x 110 root root 12288 Sep 1 03:01 etc drwxr-xr-x 2 root root 4096 Sep 22 2020 export drwxr-xr-x 5 root root 4096 Jun 10 04:12 home lrwxrwxrwx 1 root root 7 Aug 30 2020 lib -> usr/lib drwx------ 5 root root 4096 Oct 5 2020 lost+found drwxr-xr-x 4 root root 4096 Oct 15 2020 media drwxr-xr-x 2 root root 4096 Feb 9 2021 mnt drwxr-xr-x 4 root root 4096 Dec 2 2020 opt dr-xr-xr-x 2 root root 4096 Oct 15 2020 proc drwx------ 7 root root 4096 Aug 31 23:36 root drwxr-xr-x 2 root root 4096 Oct 15 2020 run lrwxrwxrwx 1 root root 8 Aug 30 2020 sbin -> usr/sbin drwxrwxr-x 2 root root 4096 Oct 5 2020 selinux drwxr-xr-x 6 root root 4096 Jun 10 03:18 srv dr-xr-xr-x 2 root root 4096 Oct 15 2020 sys lrwxrwxrwx 1 root root 42 Sep 1 03:01 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0 drwxrwxrwt 2 root root 4096 Oct 15 2020 tmp drwxr-xr-x 12 root root 4096 Nov 27 2020 usr drwxr-xr-x 14 root root 4096 Oct 6 2020 var root@helios64:/mnt/system#  
    remains only the question how/where I install the packages that were described here...
    https://forum.armbian.com/topic/18855-upgrading-to-bullseye/?tab=comments#comment-128189
     
    maybe it has something to do with the boot/ directory....
    root@helios64:/mnt/system# ll boot/ total 64696 -rw-r--r-- 1 root root 166 Sep 1 03:01 armbianEnv.txt -rw-r--r-- 1 root root 1536 Oct 15 2020 armbian_first_run.txt.template -rw-r--r-- 1 root root 38518 Oct 15 2020 boot.bmp -rw-r--r-- 1 root root 3113 Oct 15 2020 boot.cmd -rw-r--r-- 1 root root 3185 Oct 15 2020 boot.scr -rw-r--r-- 1 root root 221489 Aug 25 20:56 config-5.10.60-rockchip64 lrwxrwxrwx 1 root root 22 Sep 1 02:31 dtb -> dtb-5.10.60-rockchip64 drwxr-xr-x 6 root root 4096 Sep 1 02:30 dtb-5.10.60-rockchip64 lrwxrwxrwx 1 root root 26 Sep 1 02:31 Image -> vmlinuz-5.10.60-rockchip64 -rw-r--r-- 1 root root 15767106 Sep 1 02:32 initrd.img-5.10.60-rockchip64 -rw-r--r-- 1 root root 5839373 Aug 25 20:56 System.map-5.10.60-rockchip64 lrwxrwxrwx 1 root root 26 Sep 1 02:32 uInitrd -> uInitrd-5.10.60-rockchip64 -rw-r--r-- 1 root root 15767170 Sep 1 02:32 uInitrd-5.10.60-rockchip64 -rw-r--r-- 1 root root 28580352 Aug 25 20:56 vmlinuz-5.10.60-rockchip64 root@helios64:/mnt/system#  
  7. Like
    TDCroPower got a reaction from IcerJo in Upgrading to Bullseye (troubleshooting Armbian 21.08.1)   
    I don't have a clean backup of the eMMC unfortunately, will probably have to introduce in the future to have a backup for such a step.
    I found the following tutorial to clone the system from the emmc to a connected media....
    https://averagelinuxuser.com/backup-and-restore-your-linux-system-with-rsync/
    After that I would have to somehow downgrade my emmc backup on the media?
    Does anyone have a tip which files have to be replaced?
    After that I should clone from the fixed medium to a new SD and boot from it, now I should see my system again or?
    And then in the armbian-config with...
    System&security -> Install to -> system on emmc, boot from emmc
    ... to clone the image again on the emmc...
    https://wiki.kobol.io/helios64/install/transfer/
  8. Like
    TDCroPower reacted to gprovost in Helios64 - What's New !   
    Thanks to the Armbian team, we have now this forum club dedicated to Kobol products.
     
    Feel free to create new topics to report issues, discuss features or share experience with Helios64.
  9. Like
    TDCroPower reacted to gprovost in Helios64 - What's New !   
    We just added 2 new pages on our wiki :
     
    Transfer Installed OS - How to transfer your OS install from microSD card to eMMC, USB or HDD/SSD.
    Troubleshooting - Basic troubleshooting guide when starting with Helios64.
  10. Like
    TDCroPower got a reaction from flower in Helios64 Support   
    you can use the boot mode jumper to switch between eMMC (P10) and microSD (P11) boot, see the Helios wiki...
    https://wiki.kobol.io/helios64/jumper/
     
     
    @Helios Team...
    what is the current image status?
    Is it now possible to upgrade from 20.08.10 to the current version?
    By now we are already at 20.08.22...
    armbian-config/buster,buster 20.08.22 all [upgradable from: 20.08.10] armbian-firmware/buster,buster 20.08.22 all [upgradable from: 20.08.10] libfreetype6/stable,stable 2.9.1-3+deb10u2 arm64 [upgradable from: 2.9.1-3+deb10u1] libldap-2.4-2/stable,stable 2.4.47+dfsg-3+deb10u3 arm64 [upgradable from: 2.4.47+dfsg-3+deb10u2] libldap-common/stable,stable,stable,stable 2.4.47+dfsg-3+deb10u3 all [upgradable from: 2.4.47+dfsg-3+deb10u2] linux-buster-root-current-helios64/buster 20.08.21 arm64 [upgradable from: 20.08.10] linux-dtb-current-rockchip64/buster 20.08.21 arm64 [upgradable from: 20.08.10] linux-image-current-rockchip64/buster 20.08.21 arm64 [upgradable from: 20.08.10] linux-libc-dev/stable,stable 4.19.152-1 arm64 [upgradable from: 4.19.146-1] linux-u-boot-helios64-current/buster 20.08.21 arm64 [upgradable from: 20.08.10] openmediavault-omvextrasorg/buster,buster 5.4.2 all [upgradable from: 5.4.1] openmediavault/usul,usul,usul,usul 5.5.16-1 all [upgradable from: 5.5.12-1] salt-common/usul,usul,usul,usul 3002.1+ds-1 all [upgradable from: 3001.1+ds-1] salt-minion/usul,usul,usul,usul 3002.1+ds-1 all [upgradable from: 3001.1+ds-1] tzdata/stable-updates,stable-updates 2020d-0+deb10u1 all [upgradable from: 2020a-0+deb10u1]  
  11. Like
    TDCroPower got a reaction from Borromini in Helios64 Support   
    Soldering? No problem here !
    I can help users from Germany to fix their helios board once the solution is released.
  12. Like
    TDCroPower reacted to gprovost in Helios64 Support   
    @TDCroPower Here the small hardware tweak ;-)
     
    WARNING Please understand we are not responsible for any damage you might do to the board !
     

     

  13. Like
    TDCroPower got a reaction from Werner in Helios64 Support   
    Soldering? No problem here !
    I can help users from Germany to fix their helios board once the solution is released.
  14. Like
    TDCroPower got a reaction from Lili13400 in Helios64 Support   
    Soldering? No problem here !
    I can help users from Germany to fix their helios board once the solution is released.
  15. Like
    TDCroPower got a reaction from flower in Helios64 Support   
    Soldering? No problem here !
    I can help users from Germany to fix their helios board once the solution is released.
  16. Like
    TDCroPower reacted to flower in Helios64 Support   
    apt install glances
    it also has a web interface - but it is resource intensive
  17. Like
    TDCroPower got a reaction from flower in Helios64 Support   
    @aprayoga 
    was once again very active, so we can look forward to further optimizations in the next armbian releases ...
     
    https://github.com/armbian/build/commit/079b467342fffa7678f903793c589e9fe9fb8b69
    https://github.com/armbian/build/commit/5e62c071f0c4bafd1d25ef5f5259bb485935a77e
  18. Like
    TDCroPower got a reaction from gprovost in Helios64 Support   
    After several weeks of testing and trying I finally put my Helios64 into production.
    With the 20.08.10 and the possibility to run the firmware over the eMMC I can finally sleep more calmly again.
     
    The front view mounted:

     

     
    The back view connected:

     
    And to prevent my wife from killing me because there is a lighting party going on in the hallway I taped the front LEDs with insulating tape...

     
     
    And for all who have problems with the included USB-C cable at the USB-C port of the Helios64.
    You have to remove the plastic so that the connector looks like this...

     

     
    The black plastic of the USB-C cable must NOT touch the backside of the Helios64, this ensures that the Cable is 100% plugged in.
  19. Like
    TDCroPower reacted to antsu in Helios64 Support   
    A little advice for anyone planning to use nand-sata-install to install on the eMMC and has already installed and configured OMV:
    nand-sata-install will break OMV, but it's easy to fix if you know what's happening. It will skip /srv when copying the root to avoid copying stuff from other mounted filesystems, but OMV 5 stores part of its config in there (salt and pillar folders) and will throw a fit if they're not there when you boot from the eMMC. Simply copy these folders back from the microSD using your preferred method.
    If you have NFS shares set in OMV, make sure to add the entry /export/* to the file /usr/lib/nand-sata-install/exclude.txt BEFORE running nand-sata-install, or it will try to copy the content of your NFS shares to the eMMC.
    Lastly, if you're using ZFS, which by default mounts to /<pool_name>, make sure to add its mountpoint to /usr/lib/nand-sata-install/exclude.txt before nand-sata-install as well.
  20. Like
    TDCroPower reacted to aprayoga 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
  21. Like
    TDCroPower reacted to aprayoga 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
  22. Like
    TDCroPower reacted to aprayoga 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.
     
     
  23. Like
    TDCroPower 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.
  24. Like
    TDCroPower got a reaction from lanefu in Problem: install MongoDB for Unifi Controller   
    thank you for the tip you gave me about the docker container.
    I have successfully run the controller through Docker and it works perfectly.
    The best thing about the Docker solution, I can quickly delete or renew the "installation".
     
    docks@OrangePi:/opt/docker$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES dc14b6ce9fa3 linuxserver/unifi-controller "/init" 20 minutes ago Up 3 minutes 0.0.0.0:6789->6789/tcp, 0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcp, 0.0.0.0:8843->8843/tcp, 0.0.0.0:3478->3478/udp, 0.0.0.0:10001->10001/udp, 0.0.0.0:8880->8880/tcp, 8081/tcp unifi docks@OrangePi:/opt/docker$  
  25. Like
    TDCroPower reacted to umiddelb in Problem: install MongoDB for Unifi Controller   
    https://oversun.jp/?p=55
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines