guidol

Members
  • Content Count

    1184
  • Joined

  • Last visited

About guidol

Profile Information

  • Gender
    Male
  • Location
    Mudanya

Recent Profile Visitors

3418 profile views
  1. Yesterday I compiled Armbian_5.97_Pinebook-a64_Debian_buster_dev_5.3.0-rc8_desktop for my non-Pro Pinebook. While booting the screen was very dim So I searched on the net for a command and came to the one you had in your error-message above But the value 51 for brightness was too high to be set. I did read out the actual dim value as 2: #read-out display brightness pkexec /usr/sbin/xfpm-power-backlight-helper --get-brightness 2 and I did set (via /etc/rc.local) a for-me-default value of 8: #set display brightness pkexec /usr/sbin/xfpm-power-backlight-helper --set-brightness 8 A value of 10 was to bright for me
  2. The Emulator compiled even on a Pinebook A64, but is slower than on the NanoPi K1 Plus
  3. I got such a problem (waiting for root device) with a RPi 3B after recreating partitions on a SDCard for getting a bigger partition 1 (FAT32) and restoring the old contents. While creatng the new partitions they do get a new PARTUUID, which is configured in /etc/fstab (and on the RPi 3B also in /boot/cmdline.txt). With the command blkid I searched for the IDs and did put the new value in /etc/fstab. After that my RPi 3B did boot properly from the new created SDCard. Here my sample: root@rpi3-aiy(192.168.6.206):~# more /etc/fstab proc /proc proc defaults 0 0 PARTUUID=21fbfeb1-01 /boot vfat defaults 0 2 PARTUUID=21fbfeb1-02 / ext4 defaults,noatime 0 1 # a swapfile is not a swap partition, no line here # use dphys-swapfile swap[on|off] for that
  4. Maybe someone here knows the 8-Bit Guy and the project of his Dream-Computer - the Commander X16 You could see the actual state of the real hardware at YT-Video from the 8-Bit Guy: (Building my Dream Computer - Part 2) https://www.youtube.com/watch?v=sg-6Cjzzg8s Since the hardware isnt ready/completed yet there is a Emulator which uses SDL2 and can be compiled now (since r30) also on Linux ARM Github-page of the emulator: https://github.com/commanderx16/x16-emulator https://github.com/commanderx16/x16-emulator/releases Source: https://github.com/commanderx16/x16-emulator/archive/r30.zip or https://github.com/commanderx16/x16-emulator/archive/r30.tar.gz Linux-Binary for PC including the 2 ROMs: https://github.com/commanderx16/x16-emulator/releases/download/r30/x16emu_linux-r30.zip libsdl2-dev hasnt to be compiled from source for armbian, because we have already a installable package and the runtime libsdl2-2.0-0 is already installed in the desktop image. For compiling the Emulator I used on my NanoPi K1 Plus a fresh compiled (with armbian-build-system) dev-image: Armbian_5.97_Nanopik1plus_Debian_buster_dev_5.3.0-rc8_desktop For to have all programs for compiling the application I did use sudo apt install gcc git make libsdl2-dev zip unzip -y Then we do create a directory and download the source and extract it: mkdir x16 cd x16 wget https://github.com/commanderx16/x16-emulator/archive/r30.tar.gz tar -xvf r30.tar.gz Now we change in the newly created directory and do compile with make: cd x16-emulator-r30/ make For running the emulator we do need the 2 ROMs chargen.bin and rom.bin out of the archive https://github.com/commanderx16/x16-emulator/releases/download/r30/x16emu_linux-r30.zip in the same directory as the compile x16emu binary. Now we can run the emulator (here with german keymap): ./x16emu -keymap de Unfortunately the emulator doesnt run very fast, do use only one CPU-core and hasnt idle-support - so the CPU will get really fast very hot (70 Degree). A AMD Phenom II X4 with 4x3GHz max. is about 2 times more faster (100%+200%=300%) than the X16 on the NanoPi K1 Plus X16_r30_ROMs.zip
  5. @Igormaybe we need ony a "old" fix-commit again for his device? https://github.com/armbian/build/commit/76ac54aae381714cee7bf1b03d4bce097b1630de
  6. I had this some months ago, but now @rain45 has it - but I dont know with wich version...
  7. before the freeze-temperatures we had this error-message on some boards. So we are where we were before. This error was in/with newer kernels (dtb?)
  8. @Igor @martinayotte the bad "freezeing"-temperatures seems to be fixed with the new kernel/dtb with date-code 190913: Debian Buster with Armbian Linux 5.3.0-rc8-sunxi package bsp-kernel[5.96.190913] u-boot[5.96] dtb[5.96.190913] firmware[5.96] config[5.96] which I received via apt upgrade Many thanks to who did fix this!
  9. Its the first time that I did see a date after the package version for armbian-packages after a apt upgrade Welcome to Debian Buster with Armbian Linux 5.3.0-rc8-sunxi package bsp-kernel[5.96.190913] u-boot[5.91] dtb[5.96.190913] firmware[5.95] config[5.95] Temperature looks "OK" for a OPi Zero with 72 degree... With that kernel and DTB the temperature is working, but this OPi Zero has been updated since serveral armbian-versions. The problem with these "freeze"-temperatures I did see mainly on new installed H3/H5 devices where a freshly compiled image has been installed... [EDIT] these .190913 packages seem to fix the "freeze"-temperatures After the OPi Zero I did update my OPi One and now I got real temperatures again Welcome to Debian Buster with Armbian Linux 5.3.0-rc8-sunxi package bsp-kernel[5.96.190913] u-boot[5.96] dtb[5.96.190913] firmware[5.96] config[5.96] root@opi-one(192.168.6.114):~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 21:04:26: 1008MHz 0.24 16% 8% 6% 0% 0% 0% 54.1°C 0/4 21:04:32: 480MHz 0.22 0% 0% 0% 0% 0% 0% 53.9°C 0/4 21:04:37: 480MHz 0.20 1% 0% 0% 0% 0% 0% 52.7°C 0/4
  10. Today I did test to install pihole 4.3.1 on a Odroid C2 with Debian Buster with Armbian Linux 5.3.0-rc8-meson64 package bsp-kernel[5.96] u-boot[5.96] dtb[5.96] firmware[5.96] config[5.96] The installer did quit while setting up php (serveral times) So I did a apt upgrade and apt did complete to install 9 packages (including php). After that I restarted the pihole installer - he did found the php-installation and did install pihole FTLL an so on... and completed the installation successfully
  11. Hmmm - how much time has gone since RC3? - because thermal/THS before 8 days: "remove a83t-OPP and H3-H5-THS patches since Megous 5.3.0-RC6 have them" martinayotte committed 8 days ago https://github.com/armbian/build/commit/b53556a5f1ada29169d08b6a106a01f87d763774 could something like this change it? H3/H5 and RC6 would make it a "good" nominee?
  12. the login-motd hasnt a temperature readout (because of?) [ 11.543638] thermal thermal_zone0: failed to read out thermal zone (-110) but armbianmonitor -m and htop does show this very low temperature: root@npi-duo(192.168.6.113):~# more /sys/class/thermal/thermal_zone0/temp -207152
  13. 5.3.0 RC8 also has these low temperatures: Debian Buster with Armbian Linux 5.3.0-rc8-sunxi package bsp-kernel[5.96] u-boot[5.96] dtb[5.96] firmware[5.96] config[5.96] root@nanopiduo(192.168.6.151):/sys/class/leds# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 20:30:48: 1008MHz 0.35 12% 2% 8% 0% 1% 0% -203885°C 0/4 20:30:53: 480MHz 0.32 0% 0% 0% 0% 0% 0% -205337°C 0/4 20:30:58: 480MHz 0.29 0% 0% 0% 0% 0% 0% -205458°C 0/4 20:31:04: 480MHz 0.32 0% 0% 0% 0% 0% 0% -205700°C 0/4 @Igor @martinayotte Do you know something about some a commit/merge or else which did change some of the .DTBs for Allwinner-devices like NPi/OPi which apply after 5.3.0 RC3?
  14. As I remember on some other board there was a error like this, because they changed in production the type of the chip (in the past ram chip) but maybe they changed the emmc chip. maybe you could compare with other users board. my berry hasnt a emmc.
  15. on my OPi Zero (non LTS) I got "working" temps with kernel 5.2.2: Debian Buster with Armbian Linux 5.2.2-sunxi root@opi-zero(192.168.6.99):~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU 18:11:14: 1008MHz 1.67 0% 0% 0% 0% 0% 0% 82.2°C 18:11:19: 1008MHz 1.69 17% 3% 4% 0% 9% 0% 79.6°C 18:11:24: 1008MHz 1.64 33% 8% 23% 0% 1% 0% 77.8°C 18:11:30: 1008MHz 1.59 21% 2% 13% 0% 5% 0% 80.5°C 18:11:35: 1008MHz 2.58 37% 8% 26% 0% 2% 0% 77.4°C 18:11:40: 1008MHz 2.45 26% 3% 21% 0% 1% 0% 83.5°C but now after the update to kernel 5.3.0-RC6 it also has freezing temperatures: Debian Buster with Armbian Linux 5.3.0-rc6-sunxi root@opi-zero(192.168.6.99):~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 18:14:01: 1008MHz 1.21 28% 13% 13% 0% 1% 0% -172062°C 0/4 18:14:06: 480MHz 1.11 1% 0% 0% 0% 0% 0% -173998°C 0/4 18:14:11: 480MHz 1.02 0% 0% 0% 0% 0% 0% -174966°C 0/4 18:14:16: 480MHz 0.94 0% 0% 0% 0% 0% 0% -175208°C 0/4 its seems that there are in the newer dtb/dts some fewer cpu-temp stages (no warm - only cpu-hot and cpu-very-hot) and there is a thermal ths calibration, which I didnt see before in the dtb/dts like : ths_calibration = "/soc/eeprom@1c14000/thermal-sensor-calibration@34"; eeprom@1c14000 { reg = < 0x1c14000 0x400 >; compatible = "allwinner,sun8i-h3-sid"; #address-cells = < 0x01 >; #size-cells = < 0x01 >; phandle = < 0x3b >; thermal-sensor-calibration@34 { reg = < 0x34 0x04 >; phandle = < 0x28 >; }; };