• Content Count

  • Joined

  • Last visited


About guidol

  • Rank

Profile Information

  • Gender
  • Location

Recent Profile Visitors

5603 profile views
  1. maybe you should - like on my Pinebook- set the display brightness via /etc/rc.local? #set display brightness pkexec /usr/sbin/xfpm-power-backlight-helper --set-brightness 8 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 A value of 10 (max.?)was to bright for me
  2. does work fine (console-edition) on my Sunvell T95K Pro (S912) _ ____ __ __ __ _ _ / \ | _ \| \/ | / /_ | || | / _ \ | |_) | |\/| |_____| '_ \| || |_ / ___ \| _ <| | | |_____| (_) |__ _| /_/ \_\_| \_\_| |_| \___/ |_| Welcome to Armbian 20.09 Buster with Linux 5.9.0-rc5-arm-64 No end-user support: built from trunk package bsp-kernel[20.09] u-boot[20.09] dtb [KhadasVim2] firmware [20.09] config[20.09] branch[dev] System load: 1% Up time: 7 min Local users: 2 Memory usage: 8% of 1.85G
  3. In the past I did also install vsftpd, but some time ago I did see that the package oppenssh not only has openssh-client / openssh-server... As third part there is the openssh-sftp-server which armbian does install. So I never installed vsftpd additionally again The 3 packets in armbian (on my installation) are: openssh-client 1:8.2p1-4ubuntu0.1 arm64 secure shell (SSH) client, for secure access to remote machines openssh-server 1:8.2p1-4ubuntu0.1 arm64 secure shell (SSH) server, for secure access from remote machines openssh-sftp-server 1:8.2p1-4ubuntu0.1 arm64 sec
  4. I used Kernel 5.9.0 rc2/rc4 and a NanoPi Neo Core2 - I dont have a Odroid N2
  5. @Igordid see also this partprobe-error-message while transfer from MicroSD to emmc on the NPi Neo Core2 Is this also the reason, why we got this wierd "mountpoint" /var/log.hdd for root?: root@npi-duo-113( mount /dev/mmcblk0p1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk0p1 on /var/log.hdd type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) root@npi-neo-core2-21( mount|grep mmc /dev/mmcblk2p1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/log.hdd type ext4
  6. @Igor normally this message should go away when the file /var/run/resize2fs-reboot isnt there/deleted: I tested to delete that file and rebooted, but its recreated at restart System diagnosis information will now be uploaded to Welcome to Armbian 20.11.0-trunk Buster with Linux 5.9.0-rc4-sunxi package bsp-kernel[20.11.0-trunk] u-boot[20.11.0-trunk] dtb [20.11.0-trunk] firmware [20.11.0-trunk] config[20.11.0-trunk] branch[dev] root@npi-duo-113( rm /var/run/resize2fs-reboot root@npi-duo-113( ls -l /var/
  7. isnt a new problem, but I didnt found also a actual solution I did use the little trick to play short "empty" .wav file, wait 2 seconds then play the .wav that should be played. with that the amplifier is enabled (and in 2 secondes it doesnt go in sleep-mode again) so you will hear also the start of your .wav-file aplay -D plughw:0,0 /tmp/empty.wav 2>/dev/null sleep 2 aplay -D plughw:0,0 /tmp/espeak.wav 2>/dev/null
  8. @jscax with lower frequencies than 480Mhz you wouldnt save power or heat... its only a nice lower number
  9. resize message is also here on a actual compiled 5.9.0rc4 and doesnt go away on a NanoPi Neo Core2, but disk is already resized System diagnosis information will now be uploaded to Warning: a reboot is needed to finish resizing the filesystem Please reboot the system as soon as possible root@npi-neo-core2-21( df Filesystem 1K-blocks Used Available Use% Mounted on microsd /dev/mmcblk0p1 7455192 1363500 5983732 19% / emmc /dev/mmcblk2p1 7444644 1402308 5647084 20% / root@npi-neo-core2-21( resize2fs /dev/mmcblk2p1
  10. I dont know if it works for a samba-dialog-box, but you could try the following options with apt-get (not only apt): root@npi-neo2-22( man apt-get|grep yes -y, --yes, --assume-yes Automatic yes to prompts; assume "yes" as answer to all prompts and run non-interactively. If an Force yes; this is a dangerous option that will cause apt to continue without prompting if it is Force yes; this is a dangerous option that will cause apt to continue without prompting if it is --force-yes Force yes; this is a dangerous opti
  11. @5kft Yes - does work now correctly. I compiled the kernel/dtb 5.9.0.rc4 after your commit and installed all files. Then I activated the 1.0Ghz/1.1v dtbo and rebooted. All dtbo-files are now loaded correctly: And all CPU-frequencies are available up to the 1008Mhz (1.01Ghz)
  12. it looks like you got some devices connected via usb: hub [ 2.593856] usb 4-1: New USB device found, idVendor=05e3, idProduct=0612, bcdDevice=92.26 [ 2.593869] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2.593875] usb 4-1: Product: USB3.1 Hub [ 2.593880] usb 4-1: Manufacturer: GenesysLogic hdd-controller/drives [ 3.231356] usb 5-1: New USB device found, idVendor=18a5, idProduct=0237, bcdDevice= 5.10 [ 3.231368] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3.231374] usb 5-1: Product:
  13. maybe it does help running htop after the login and checking which processes may block the system in the first place... or running dmesg -w after login if there is a kernel-message?
  14. @5kft could you please tell us when @Igor has accepted this commit? I couldnt see the accept at the url above...
  15. @5kft - No Problem - its nice to help getting a stable armbian I could recognize what your fix for the overlay patch will do What will I see as rection when I would recompile the kernel/dtb? For now I edited the dtbs on v1.0 and v1.1 Neo2 that also 960Mz and 1008Mhz is using the same voltage as 816Mhz - so I got these frequencies again (because they where stable for me the last years ) : root@npi-neo2-24( cpufreq-info hardware limits: 480 MHz - 1.01 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz current policy: frequen