• Content Count

  • Joined

  • Last visited

1 Follower

About guidol

  • Rank

Profile Information

  • Gender
  • Location

Recent Profile Visitors

4249 profile views
  1. On a test of stockfish v11 I did found that inetd isnt installed as default anymore and does throw a error-message when installed and started Failed to start inetd.service: Unit inetd.service not found. So I did switch to the newer xinetd ( xinetd - replacement for inetd with many enhancements ): sudo apt install xinetd (and maybe if installed : apt purge inetutils-inetd update-inetd ) So then there is no /etc/inetd.conf anymore, but now we have to create a file for each tcp stream like /etc/xinet.d/stockfish11: # Stockfish remote engine service stockfish11 { disable = no server = /usr/games/stockfish_11_64 socket_type = stream protocol = tcp user = guido wait = no port = 1024 # only_from = localhost } the file /etc/services has to be configured as before To restart xinetd and check the status of xinetd you could use: sudo systemctl restart xinetd sudo systemctl status xinetd As reference/information I used the following page:
  2. [EDIT] couldnt wait until tomorrow Worked fine like on the v10 version and resulted in: but in the documentation it seems I deleted one endif to much So the part of the Makefile where I deleted the else-tree should look like: ifeq ($(COMP),gcc) comp=gcc CXX=g++ CXXFLAGS += -pedantic -Wextra -Wshadow ifeq ($(ARCH),armv7) ifeq ($(OS),Android) CXXFLAGS += -m$(bits) LDFLAGS += -m$(bits) endif endif ifneq ($(KERNEL),Darwin) LDFLAGS += -Wl,--no-as-needed endif endif and the part for armv7 and aarch64 should look like: ifeq ($(ARCH),armv7) arch = armv7 prefetch = yes endif ifeq ($(ARCH),aarch64) arch = any prefetch = yes bits = 64 endif On my NanoPi K1 Plus where these 2 gcc++ versions installed: root@npi-k1-plus( dpkg -l|grep 'g++' ii g++ 4:9.2.1-3.1 arm64 GNU C++ compiler ii g++-9 9.2.1-22 arm64 GNU C++ compiler so I used the following command to compile stockfish v11: make build ARCH=aarch64 COMP=gcc COMPCXX=g++-9 which did work well: Have fun with this actual chess-engine
  3. Stockfish v11 is out (since 15.01.2020) Maybe I will test a 64bit compile tomorrow on my NanoPi K1 Plus
  4. what do you want to read? Or what can be read as usre if you know the trigger? = here heartbeat root@npi-k1-plus( more /sys/class/leds/nanopi:green:status/trigger none usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrl lock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usbport mmc0 mmc1 mmc2 disk-activity di sk-read disk-write ide-disk mtd nand-disk [heartbeat] cpu cpu0 cpu1 cpu2 cpu3 activity default-on panic rfkill-any rfkill-none rc-feedback rfkill0 0.2:00:link 0.2:00:1Gbps 0.2:00:100Mbps 0.2:00:10Mbps
  5. Yesterday pihole 5.0 Beta was announced As a test-device I took a NanoPi K1 Plus where I installed armbian bullseye kernel 5.5.0-rc6 and installed pihole 4.3.2 bullseye needs the same apt upgrade and second install restart, but installs pihole 4.3.2 successfully after the 4.3.2 installation I could update to the 5.0 Beta with echo "release/v5.0" | sudo tee /etc/pihole/ftlbranch pihole checkout core release/v5.0 pihole checkout web release/v5.0 5.0 Beta is now running on my test-system
  6. I got some Sunxi/Sunxi64 board running 5.5.0-rc2 running for some days (one or two weeks) and couldnt find any freezes. Today dev is going on my systems to 5.5.0-rc6 - I will see if there will be any freezes. Running Boards are OPi Zero, OPi One, BPI M2 Berry, NanoPi A64, NanoPi Neo2
  7. @nylonatathep Thanks for the solution I can confirm it also for the Orange Pi One DTB to DTS: dtc -I dtb -O dts /boot/dtb/sun8i-h3-orangepi-one.dtb -o /boot/dtb/sun8i-h3-orangepi-one.dts DTS to DTB: dtc -I dts -O dtb /boot/dtb/sun8i-h3-orangepi-one.dts -o /boot/dtb/sun8i-h3-orangepi-one.dtb Kernel: Linux opi-one 5.5.0-rc2-sunxi #19.11.5 SMP Tue Dec 31 13:30:06 +03 2019 armv7l GNU/Linux PS: as usual - the corrected .dtb gets lost via a apt upgrade if you doesnt set it on hold apt-mark hold linux-dtb-dev-sunxi sun8i-h3-orangepi-one.dtb sun8i-h3-orangepi-one.dts
  8. Yes a working overlay would be fine if there is also support included for the 5102A in the kernel see config SND_SOC_PCM5102A tristate "Texas Instruments PCM5102A CODEC - I2S" above...
  9. "unofficial"? the Khadvas vim2 (.dtb included) is supported by the TV-Box armbian-version from @balbes150: see
  10. the WN8200ND v1 uses RTL8192CU but the v2 uses a RTL8192EU You could try to use the source from another github-page (here for v2):
  11. why didnt you use the install instructions from the github page? or do use a newer kernel? for which board you will use the driver? whats the model name of you usb device?
  12. cpufreq-info/armbian-config says only up to 1.01.GHz: Hardwarebedingte Grenzen der Taktfrequenz: 480 MHz - 1.01 GHz mögliche Taktfrequenzen: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz I think because of the OPi One .dtb and dmesg tells me: [ 6.314991] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 6.315012] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000) [ 6.315163] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 6.315174] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000) [ 6.315297] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 6.315308] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000) [ 6.315451] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 6.315462] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000) without proper voltage-regulator more than 1.01.Ghz isnt stable
  13. its the same on kernel 5.5 (debian 11 bullseye) for the OPi One - BUT as I did read in the past that shouldnt be a big problem, because at 480Mhz the CPU shouldnt be hotter than on 120Mhz. Also I did read that the system could have problems reading memory/devices/drives at 120Mhz and is switching to 480Mhz for that. So the system isnt reacting at 120Mhz not fast enough for some tasks.
  14. I did compile with ./ EXPERT=yes WIREGUARD=no AUFS=no BUILD_KSRC=no and it did also work for for my non-64Bit-sunxi SBCs OPi Zero, OPi One and my BPi M2 Berry At this time I have no need for WireGuard.
  15. My sunxi64-dev SBCs (3x NPI Neo2 + NPi A64) does startup fine: Neo2: Welcome to Armbian Buster with Linux 5.5.0-rc2-sunxi64 package bsp-kernel[19.11.5] u-boot[19.11.5] dtb[19.11.5] firmware[19.11.5] config[19.11.5] branch[dev] A64: Welcome to Debian Buster with Armbian Linux 5.5.0-rc2-sunxi64 package bsp-kernel[19.11.5] u-boot[19.11.5] dtb[19.11.3] firmware[19.11.5] config[19.11.5] branch[dev] Thanks Now I could start to compile for sunxi-dev