• Content Count

  • Joined

  • Last visited


About guidol

  • Rank

Profile Information

  • Gender
  • Location

Recent Profile Visitors

5194 profile views
  1. NanoPi Neo3 could now ordered - but not with a metalic case. Dont know how it will heat up in there And with this cas you couldnt use the 2 additional 2 USB 2.0 ports or fan-support.... which is available on the pin headers...
  2. You dont have to, because its available as Chess-engine for Android at: (see page ) or in the Play-Store at Or dp you need a playable grahical Interface for it? Then use
  3. you could try to replace with see:
  4. Ubuntu Disco STS was only supported until January 2020: 18.04 LTS until Aril 2023 19.04 STS Disco until January 2020 18.10 STS Cosmic until July 2019 19.10 STS Eon only until Juli 2020 20.04 LTS until April 2025 LTS = „Long Term Support“ STS = „Short Term Support“
  5. If I read your following post, then I would think (like @Igor) it would be a good idea to go with a value like 600Mhz?:
  6. @tkaiser nice to read you No Iam not kidding, but you are also right that something must be differnt on the R2S against the Renegade. In my mind: when one company could - reading teh temperature - get right to work (Renegade), then it shouldnt be hard for another company to gain the same result. Maybe the RK3328 isnt nowthing like a Quadcore-A53, but its working and we will loose the Allwinner H5. So FriendyARM sint taking the H6 and do try to be "friendly" to Rockchip I personally dont understand what the problem - in the year 2020 - to get a correct temperature-readout or usinf the right voltage for a chipset? On the other hand the last 1-2 years FriendlyARM has some better meta-cases like other companys I remember what I did wrote, but the hope isnt gone that we do get a good temperature-readout, when the SBCs do so much more the right "boring" way
  7. which is the wrong and which is the right governor? (and maybe why?)
  8. I hope that the NanoPi Neo3 wouldnt get that heat-problems, because it seems to get the same CPU as the R2S ;( The Allwinner CPUs were - as of my point of view - not getting that hot as the Rockchip-CPUs. If we would ever see a NanoPi Neo6 with H6-CPU?
  9. root@nanopi-a64:~# timedatectl show -p TimeUSec --value Sun 2020-06-28 16:16:39 +03 My Browser is on Windows: Google Chrome, Version 83.0.4103.116 (Official Build) (64-Bit) You did Updates - but the Update-function doesnt show anything new Is there any place/page where we could see the actual installed version-number? When not - could you please include it on the Dashboad or Updates-Page?
  10. Ahh That looks/works much better Now my USB-Stick is recognized - but more important: The system is accessable via WebGUI and SSH after the reboot. What I would set as reminder: - You ask the Password only once (with the chance to view via the eye-icon) - You dont ask for a user name - I did try root for login AFTER admin - Volume-name cant be changed - I did set it to sda but now Iam using partition sda1 - Users seem to have only full R/W access? cant see a option for read-only - in the Groups view/configuration I miss users and sudo as shown in the users view at the admin-user - the date has a comma-char to much in the front
  11. I think you cant "bridge" them. You cant only (when paired & trusted a device) you a specific /etc/asound.conf to make your BlueALSA-device as default: CREATING a BlueALSA /etc/asound.conf: # ================================================= pcm.!default "bluealsa" ctl.!default "bluealsa" defaults.bluealsa.interface "hci0" defaults.bluealsa.device "00:11:67:3F:9B:18" defaults.bluealsa.profile "a2dp" # =================================================
  12. Also on a NanoPi A64 its the same WebUI & SSH not accessable, but the system is pingable. Installation did crash the armbian-image Now for me its enough - maybe some one else would try the next install with more success....
  13. I tested curl -s | sudo bash /dev/stdin but at the end of the script I did get BINMAN u-boot-sunxi-with-spl.bin CFGCHK u-boot.cfg \033[36m make boot.scr.\033[0m mkimage: Can't stat /tmp/u-boot/r40_boot.cmd: No such file or directory \033[36m copying binary u-boot sd.\033[0m 461+1 records in 461+1 records out 472571 bytes (473 kB, 461 KiB) copied, 0.00600794 s, 78.7 MB/s \033[36m copying new dtb sd.\033[0m \033[36m Please reboot Now.\033[0m root@bananapim2berry:~# ls /tmp/u-boot/ api Kbuild u-boot.img arch configs Kconfig test board disk lib tools boot.scr doc Licenses u-boot u-boot-nodtb.bin build drivers MAINTAINERS u-boot.bin u-boot.srec cmd dts Makefile u-boot.cfg u-boot-sunxi-with-spl.bin common env net u-boot.cfg.configs u-boot.sym examples post u-boot.dtb fs README u-boot-dtb.bin scripts u-boot-dtb.img include spl u-boot.dtb.out After reboot root@bananapim2berry:~# aplay -l aplay: device_list:272: no soundcards found...
  14. Now its the 3rd time and the same bad result I configured a static IP and skipped the Network configuration in the WebGUI, but after reboot ssh gives "Connection refused" and the webinterface isnt accessable anymore Static IP ( is pingable. root@npi-neo2-24( ssh -l root ssh: connect to host port 22: Connection refused Is it correct that my user/config-drive is 0? (the m2berry has mmc0 = sdcard and sda = 32GB USB Stick) Could it be a problem that the M2Berry isnt 64bit (like Intel or your Ordoids?) The next try I could do on a NanoPi A64 with 64Bit (aarch64)
  15. should I test it with my M2Berry now? With which kernel version should it work?