• Content count

  • Joined

  • Last visited

About guidol

  • Rank
    Embedded member

Profile Information

  • Gender
  • Location
  1. Iam using the OPi Zero only with Ethernet, because I use the little black Cube-case - and this is to small for the WiFi Antenna. On my 2 OPi Zero I got working Audio with these two armbian-versions: ARMBIAN 5.41.180208 nightly Ubuntu 16.04.3 LTS 4.14.18-sunxi Linux orangepizero 4.14.18-sunxi #31 SMP Fri Feb 9 11:11:15 CET 2018 armv7l armv7l armv7l GNU/Linux and ARMBIAN 5.38 stable Ubuntu 16.04.3 LTS 3.4.113-sun8i Linux orangepizero 3.4.113-sun8i #18 SMP PREEMPT Wed Jan 24 22:10:49 CET 2018 armv7l armv7l armv7l GNU/Linux
  2. ARMBIAN for Amlogic S905 and S905X

    The only solution I know are - if you free some space on the filesystem - GParted to resize partitons (under Linux oder Live-CD) and then under Windows Win32Diskimager should have in a newer version a tick/click option to same only allocated space in the image-file.
  3. Did you enable Analog-Codec as Hrdware in armbian-config? Normally the Zero has no Audio-Out (only via extension) - so default its disabled.
  4. Now the client with 72.000 Request is blocked ( , but my Raspberry Pi "MyCroft" AI does 4.000 Request since 13:00 a clock:
  5. Hmm on legacy I got: ARMBIAN 5.38 stable Ubuntu 16.04.3 LTS 3.4.113-sun8i root@orangepizero:~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 13:25:35: 768MHz 0.49 3% 2% 0% 0% 0% 0% 65°C 1/7 13:25:40: 240MHz 0.45 3% 2% 0% 0% 0% 0% 65°C 1/7 13:25:46: 240MHz 0.42 5% 3% 1% 0% 0% 0% 65°C 1/7 13:25:51: 240MHz 0.38 5% 3% 1% 0% 0% 0% 66°C 1/7 but on mainline it wont get down to 240Mhz ARMBIAN 5.41.180208 nightly Ubuntu 16.04.3 LTS 4.14.18-sunxi root@orangepizero:~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 10:27:08: 960MHz 1.77 45% 12% 28% 0% 3% 0% 70.2°C 3/8 10:27:13: 960MHz 1.71 27% 4% 22% 0% 0% 0% 71.1°C 3/8 10:27:19: 1008MHz 1.57 8% 2% 5% 0% 0% 0% 66.9°C 2/8 10:27:24: 1104MHz 1.45 3% 1% 0% 0% 0% 0% 64.5°C 1/8 10:27:29: 1104MHz 1.33 2% 1% 0% 0% 0% 0% 64.4°C 1/8 10:27:34: 1200MHz 1.22 3% 2% 0% 0% 0% 0% 63.8°C 0/8 10:27:39: 1200MHz 1.13 2% 1% 0% 0% 0% 0% 64.4°C 0/8 10:27:44: 1200MHz 1.04 2% 1% 0% 0% 0% 0% 64.0°C 0/8 10:27:49: 1200MHz 0.95 3% 2% 0% 0% 0% 0% 63.5°C 0/8 10:27:54: 1200MHz 0.88 2% 1% 0% 0% 0% 0% 63.2°C 0/8 10:27:59: 1200MHz 0.81 2% 1% 0% 0% 0% 0% 64.7°C 0/8
  6. Armbian for Amlogic S802/S812

    Yes VCC is 5 or 3.3V but you dont need VCC because the USB-Dongle and the mainboard/pc has its own power You can connect the cable as written in the Picture (RX<->TX, TX<->RX, GND<->GND) On some other USB-Dongles it could be to connect RX<->RX and TX<->TX - but mostly not
  7. Today my /var/log was also full. pihole.log was about 31MB and so cant logrotated. There is a "problem" when pi-hole get too much requests, then the 50MB log2ram isnt enough. Mostly then there is a client which sends much to moch requests: If have identified my "wild client" as my Google Home. Here in Tuerkey and are blocked (dont know why), but if the Google Home once has been instructed to play a TuneIn-channel and cant it here he send the whole day DNS-request to this domains So the last day I did found 72.000 requests - thats why my /var/log is full ands cant be logrotated. Additionally you could check the size of the long term DB: DBFILE=/etc/pihole/pihole-FTL.db Informations about setting some DB configuration is at: The file /etc/pihole/pihole-FTL.conf has to be created - I will try my luck with the follwoing entrys: MAXDBDAYS=7 DBINTERVAL=5.0 DBFILE=/etc/pihole/pihole-FTL.db MAXLOGAGE=24.0 Only 7 days for the DB, writing to the DB every 5 minutes (not every 1.0 minutes), DB is the normal location, MaxlogAge in Ram is also the normal 24 Hours. I have now blacklisted and - hope this will shrink the log. BTW: because Pi-Hole is the only App running on my OPi One I will increase the size of log2ram, which is configured in the file /etc/default/log2ram : # size of the tmpfs mount SIZE=100M but armbian doesnt seem to occupy this log2ram size at bootup....
  8. Armbian for Amlogic S912

    Sorry - I didnt understand your question
  9. ARMBIAN for Amlogic S905 and S905X

    I did "update" from 20180212 to 20180216 with installing the following files via dpkg -i with the files from (files does show my download-time) -rw-r--r-- 1 root root 23274564 Feb 16 21:31 firmware-aml_5.41_arm64.deb -rw-r--r-- 1 root root 80668 Feb 16 21:28 linux-dtb-amlogics905x_5.41_arm64.deb -rw-r--r-- 1 root root 16948344 Feb 16 21:30 linux-image-amlogics905x_5.41_arm64.deb Was that the right way (I think yes)? System is running and does show Linux sunvell-t95kpro 3.14.29 #6 SMP PREEMPT Fri Feb 16 17:44:28 MSK 2018 aarch64 GNU/Linux Is this the only way or is there also a apt-source-repository?
  10. ARMBIAN for Amlogic S905 and S905X

    select ubuntu/stretch and desktop-variant from here:
  11. Armbian for Amlogic S802/S812

    for your S812 system did you read the notice at the bottom?: Attention !!!! On models with S802 S805 S812. Activation multi-boot is possible ONLY with SD card (activation of the USB stick is NOT WORKING). After a one-time activation procedure is multi-boot, run a variety of systems is possible from ANY storage media (SD cards and USB storage devices). When activation is done I did insert a USB-Stick with the armbian-boot-image and reboot
  12. I got 2 OPi One running latest Pi-Hole = Pi-hole Version v3.3 Web Interface Version v3.3 FTL Version v3.0 while using ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.14.18-sunxi Linux opi-one-main 4.14.18-sunxi #24 SMP Fri Feb 9 16:24:32 CET 2018 armv7l GNU/Linux Whats the special need of turning off the GPU/HDMI? less heat? less power? or more memory (while not using the GPU)? My 2 OPi One doesnt get hot and do run stable with unused but powered GPU/HDMI. The pi-hole install script curl -sSL | bash did install here the following version of dnsmasq: dnsmasq 2.76-5+deb9u1 all Small caching DNS proxy and DHCP/TFTP server dnsmasq-base 2.76-5+deb9u1 armhf Small caching DNS proxy and DHCP/TFTP server
  13. First did you start blueALSA in the backgrund with bluealsa --disable-hfp & Could you write the output of the command "devices" inside of bluetoothctl? (whats the name and id of your speaker?) Did you pair & trust your BT-speaker inside of bluetoothctl? Does BT-Speaker play the connect-sound and isnt blinking anymore? ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) seems to be the address of your USB-BT(-Dongle) Did you create a ~/.asoundrc (in the homedirectoty of your user or root if you using root) with the default-definitons of bluealsa?: defaults.bluealsa.interface "hci0" defaults.bluealsa.device "30:23:23:F4:48:2C" <==== here the id of your BT-Speaker defaults.bluealsa.profile "a2dp" defaults.bluealsa.delay 10000 (the default will only apply to this one speaker which has this id - if you want to play on another speaker/device you had to add the parameters to the commandline of the audio-command) If not you have to add the parameters for id and profile to the commandline. I have tested it today with 2 additional speakers, and the connect didnt work directly, but after starting bluealsa and then a moment later the BT-speaker will auto-connect if trusted: Device 30:21:8E:AA:4C:45 ML-28U Device 30:23:23:F4:48:2C TH-S10U Device 00:11:67:3F:9B:18 BTLS9001 If you didnt want to auto-connect or it wouldnt autoconnect you can connect to a paired&trusted BT-Speaker with the command: echo -e "connect 00:11:67:3F:9B:18\nquit" | bluetoothctl <=== here you also need to change the id to the id of your BT-Speaker Disconnect is the same: echo -e "disconnect 00:11:67:3F:9B:18\nquit" | bluetoothctl You could also change the commandline here for pairing or trusting a device like echo -e "pair 00:11:67:3F:9B:18\trust 00:11:67:3F:9B:18\nquit" | bluetoothctl Which command did you use to play a sound? (please copy the full command line)
  14. Today I did update my 2 Pi-Hole Servers (Orange Pi One with mainline kernel) to Pi-Hole V3.3 One did work fine after the update, but the other one had problems connecting to the FTL-Part of Pi-Hole. Something like "connection refused" and not showing stats - only spinning arrows. a repair via "phole -r" did not help flushing the log via gui did not help (but I wasnt sure if it does work via the gui) So I did took a look at /var/log and deleted the pi-hole logs with rm pihole* (the empty /var/log/pihole directory hasnt been deleted) Now - after a reboot - the GUI does work like before the update. Maybe its because the following info at the pi-hole-update-page:
  15. Armbian for Amlogic S802/S812

    for a S812 CPU you need the follwoing 2 files at the root of the card - aml_autoscript - from see also the wiki (use google translate in Chrome?):