• Content Count

  • Joined

  • Last visited

About Vin

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. configurating after the installation over serial connection is no problem. the problem is that apparently the installation "breaks" something in the ip configuration. despite set up a static ip in OMV multiple times, after every boot its back to dhcp and resolv.conf is empty. also the startup of the kernel hangs for like 5 minutes until the OS is available
  2. Hello together, i experienced network problems with Helios64 and latest Debian Buster Image. I cannot setup a static ip address after installation of OMV5, moreover it crashes on install. I double checked it on a fresh image without any changes and an immediate installation of OMV over softy. The result is the same. After the crash OMV is in fact available, but the network configuration is broken and a static setup doesnt work over the OMV UI, nor armbian-config, also the boot takes about 2-5 minutes due to whatever reason.
  3. Hello tparys, thank you for you reply service network status Unit network.service could not be found. /etc/network/interfaces.d its empty armbianmonitor -u tried nmcli con mod "Wired connection 1" ipv4.addresses "" ipv4.gateway "" ipv4.dns "," ipv4.dns-search "lan" ipv4.method "manual" didnt do the trick EDIT2: I just tried a fresh install and apparently the OMV installation breaks something regarding networking. I
  4. Hello everybody, im running a Helios64 with most current Debian Buster5.10.16 image. I was freshly setting up the device and i am now failing to assign a static ip address to it. I installed Pi-hole, Home assistant and openmediavault over softy. During the pihole installation i can setup a static ip address, but after a reboot i still get the old DHCP addess. I assigned it over the OMV interface but its not applied after a reboot, the armbian-config tool doesnt open when i want to change to static and i also tried netplan. DHC
  5. Both, the affected HDDs and Ports are random Plugging them in another Port solves the problem, but they can get affected again at a later point, plugging them back to the original ports solves the problem.
  6. SATA Ports are firm, also connection to the HDDs are proper. Just restarted and did a fresh install of the new februar update, two out of three HDDs are not recognized anymore, even though they were recognized before and have not been unplugged.
  7. Hello everybody, im experiencing a similar problem. Sometimes my WD RED 12 TB HDD is not recognized in that slot its in, when i change it to any other it works again. Nevertheless it seems this problem doesnt only apply to one specific slot, but is changing from time to time. EDIT: The LED of that slot doesnt turn on, yet the drive starts and runs Do anybody experience the same problem, or know any help? Thank you in advance. Best Regards.
  8. Hello togehter, I did a fresh os install on the Rock64, but even though it installs correctly and initially works, it stops after a reboot. Already tried different kernels and even the nightly version. docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 6dc24654d9f9 homeassistant/raspberrypi4-64-homeassistant:0.118.5 "/init" About an hour ago Exited (255) About an hour ago homeassista
  9. Found the solution to this problem, just start it witout sudo docker run -d \ --name=deconz \ --net=host \ --restart=always \ -v /etc/localtime:/etc/localtime:ro \ -v /opt/deconz:/root/.local/share/dresden-elektronik/deCONZ \ --device=/dev/ttyACM0 \ -e DECONZ_VNC_MODE=1 \ -e DECONZ_WEB_PORT=82 \ -e DECONZ_WS_PORT=8443 \ marthoc/deconz JMCC thanks anyway for the reply
  10. Hello together, for a few months im running into this problem, where i cannot initiate a docker container, it will return following error message. docker: unknown server OS: sudo -u Username docker run -d \ --name=deconz \ --net=host \ --restart=always \ -v /etc/localtime:/etc/localtime:ro \ -v /opt/deconz:/root/.local/share/dresden-elektronik/deCONZ \ --device=/dev/ttyACM0 \ -e DECONZ_VNC_MODE=1 \ -e DECONZ_WEB_PORT=82 \ -e DECONZ_WS_PORT=8443 \ marthoc/deconz Linux rock64 5.8.13-rockchip64 #20.08
  11. Hello gprovost, I´m very excited about the upcoming Helios64 and I´m following it since it was announced. I would like to know about the customs status for shipments going to EU, as well as estimated shipping time. Another very vital point is software support, for what i can tell the RK3399 doesnt seem to run all too stable on other devices so far? I´m running armbian for quite some years on different devices and I´m feeling with the developers who are more than patient with enduser critics and still doing that job more or less for free on a dail
  12. Wanted to give you the feedback that the latest update ARMBIAN 5.60 stable Ubuntu 18.04.1 LTS 4.4.156-rockchip64 works flawlessly, thank you so much for your hard work you put into it, very happy to be back to the armbian distro. Best regards Vin
  13. sorry was cought up at work this week. Regarding the SD card, I m using two different Samsung EVO Plus Micro SDXC 64GB, as well as a Samsung Speicherkarte MicroSDHC 32GB EVO Plus UHS-I and various different SanDisk and Samsung Cards My Ethernet Chip is as well a RTL8211F Tried five different Cards so far with the newest 155 iso, still not booting up
  14. sorry didnt know you were waiting for feedback from me tried to unplug/plug the HDMI nothing changed also tried the 155 test build, unfortunately no change, will going to test more cards tomorrow after work best regards and thank you very much for the big effort all of you put into this.