Jump to content

dony71

Members
  • Posts

    128
  • Joined

  • Last visited

Everything posted by dony71

  1. still error if change card = "hw:1,0" /var/log/forked-daapd.log ----------------------------------- [2017-01-13 01:04:47] [ LOG] laudio: Invalid value for card[2017-01-13 01:04:47] [ LOG] laudio: Could not open playback device: No such file or directory [2017-01-13 01:04:47] [ LOG] player: Could not start ALSA device 'BPi-M2P' [2017-01-13 01:04:47] [ LOG] player: Could not activate ALSA device 'BPi-M2P'
  2. I have problem now playing from local audio output alsa I want to play from card 1 : snddaudio Anybody help? /etc/forked-daapd.conf ---------------------------------------------------------------------------- # Local audio output audio { # Name - used in the speaker list in Remote nickname = "BPi-M2P" # Type of the output (alsa, pulseaudio or dummy) type = "alsa" # Audio PCM device name for local audio output - ALSA only #card = "default" card = "snddaudio" # Mixer channel to use for volume control - ALSA only # If not set, PCM will be used if available, otherwise Master. # mixer = "" # Mixer device to use for volume control - ALSA only # If not set, the value for "card" will be used. # mixer_device = "" # Syncronization # If your local audio is out of sync with AirPlay, you can adjust this # value. Positive values correspond to moving local audio ahead, # negative correspond to delaying it. The unit is samples, where is # 44100 = 1 second. The offset must be between -44100 and 44100. # offset = 0 } /var/log/forked-daapd.log ---------------------------------- ..... [2017-01-13 00:45:34] [ LOG] laudio: Unknown PCM snddaudio[2017-01-13 00:45:34] [ LOG] laudio: Could not open playback device: No such file or directory [2017-01-13 00:45:34] [ LOG] player: Could not start ALSA device 'BPi-M2P' [2017-01-13 00:45:34] [ LOG] player: Could not activate ALSA device 'BPi-M2P' aplay -l ----------------------------------- **** List of PLAYBACK Hardware Devices **** card 0: audiocodec [audiocodec], device 0: SUNXI-CODEC sndcodec-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: snddaudio [snddaudio], device 0: SUNXI-TDM0 snddaudio-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: sndhdmi [sndhdmi], device 0: SUNXI-HDMIAUDIO sndhdmi-0 [] Subdevices: 0/1 Subdevice #0: subdevice #0
  3. is it possible to do autorun in systemd ?? cannot start with below /etc/systemd/system/forked-daapd.service =============================================== [unit] Description=DAAP/DACP (iTunes), RSP and MPD server, supports AirPlay and Remote After=network.target sound.target [service] ExecStart=/usr/sbin/forked-daapd -f # Restart, but not more than once every 10 minutes Restart=on-failure StartLimitBurst=2 StartLimitInterval=600 [install] WantedBy=multi-user.target
  4. Thanks, compile fine now For armbian, there is no package libgnutls-dev, instead libgnutls28-dev
  5. found issue related to --enable-chromecast my configure script : ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --enable-chromecast any idea what's missing here to enable chromecast?
  6. I have also this warning below during ./configure Not sure whether this is related to the error? configure: WARNING: *** *** The config script /usr/bin/libgcrypt-config was *** built for arm-unknown-linux-gnueabihf and thus may not match the *** used host armv7l-unknown-linux-gnueabihf. *** You may want to use the configure option --with-libgcrypt-prefix *** to specify a matching config script. *** checking for gpg-error-config... /usr/bin/gpg-error-config checking for GPG Error - version >= 1.6... yes (1.17) configure: WARNING: *** *** The config script /usr/bin/gpg-error-config was *** built for arm-unknown-linux-gnueabihf and thus may not match the *** used host armv7l-unknown-linux-gnueabihf. *** You may want to use the configure option --with-gpg-error-prefix *** to specify a matching config script or use $SYSROOT. ***
  7. compile failed ... any idea? ~/Downloads/forked-daapd$ make make all-recursive make[1]: Entering directory '/home/pi/Downloads/forked-daapd' Making all in sqlext make[2]: Entering directory '/home/pi/Downloads/forked-daapd/sqlext' /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -Wall -D_LARGEFILE_SOURCE -avoid-version -module -shared -lprotobuf-c -o forked-daapd-sqlext.la -rpath /usr/lib/forked-daapd sqlext.lo -lunistring -lpthread libtool: link: gcc -shared -fPIC -DPIC .libs/sqlext.o -lprotobuf-c -lunistring -lpthread -O2 -Wl,-soname -Wl,forked-daapd-sqlext.so -o .libs/forked-daapd-sqlext.so /usr/bin/ld: cannot find -lprotobuf-c collect2: error: ld returned 1 exit status Makefile:435: recipe for target 'forked-daapd-sqlext.la' failed make[2]: *** [forked-daapd-sqlext.la] Error 1 make[2]: Leaving directory '/home/pi/Downloads/forked-daapd/sqlext' Makefile:534: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/pi/Downloads/forked-daapd' Makefile:401: recipe for target 'all' failed make: *** [all] Error 2
  8. I run mpd on port 6680 in OPi No problem if reaching in local network (localhost:6680) Now I try to reach from internet, but verifying with http://www.yougetsignal.com/tools/open-ports/ port is still closed. I try forwarding all other port in OPi like sshd port 22 also closed I'm pretty sure I set correctly port forwarding in my router because my NAS can work with same iptables rule. It seems something wrong in OPi setting, but couldn't find out what's wrong. Anybody help? #iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination #netstat -l Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:6680 *:* LISTEN
  9. I have BPI-M2+ shutdown -P now or poweroff does not power off the board Board is just halted and fan is still spinning Anyway to power off the board completely?
  10. can you try to change "sample_resolution = 24" in script.bin see below in details under [pcm0] https://github.com/igorpecovnik/lib/blob/master/config/fex/bananapim2plus.fex
  11. RPi has this interrupt driven GPIO input detection GPIO.add_event_detect(pin_number, GPIO.BOTH, callback=callback_function) Orange Pi has already this python GPIO function https://github.com/duxingkei33/orangepi_PC_gpio_pyH3 But I see only gpio.input(pin_number) function for GPIO input detection Anybody can answer whether possible to substitute RPi interrupt driven GPIO input detection?
  12. I have armbian 5.17 and notice sometimes cron does not work after reboot To verify this, I issue "pgrep cron" and nothing comes out How cron is started in armbian? I take a look on /etc/rcx.d ... nothing start there Can somebody explain?
  13. Will you kindly let me know step by step how to install SMTube using vdpau?
  14. May I know what's max PCM rate supported in kernel? Does it support 384K like in Odroid C1/C2 ? (https://github.com/hardkernel/linux/blob/odroidc2-3.14.y/include/sound/pcm.h#L115)
  15. Some progress in bluetooth now can be seen by bluetoothctl and blueman also I can pair bluetooth mouse install blueman >>> sudo apt-get install blueman add user in bluetooth group >>> sudo usermod -a -G bluetooth $USER enable hid input device module by adding "hidp" in /etc/modules-load.d/modules.conf init bluetooth start up in boot by adding this below in /etc/rc.local /etc/init.d/bluetooth stop rfkill unblock all echo " " > /dev/ttyS1 hciattach -t 5 /dev/ttyS1 bcm43xx 1500000 hciconfig hci0 up /etc/init.d/bluetooth start still issue, cannot pair any devices which needs authentication key such as bluetooth keyboard, bluetooth PAN somehow bluetooth controller timeout authentication key very fast within a second
  16. how do you pair? i try to use bluetoothctl, but when i do pair, get authentication failure on my iphone, there is pop up message "pairing unsuccessful. pairing took too long. make sure bananapim2plus is turned on, in range, and is ready to pair" ====================================== pi@bananapim2plus:~$ sudo bluetoothctl [NEW] Controller 43:43:A0:12:1F:AC bananapim2plus [default] [NEW] Device F8:27:93:1D:AB:E3 iPhone (5S) [bluetooth]# pair F8:27:93:1D:AB:E3 Attempting to pair with F8:27:93:1D:AB:E3 [CHG] Device F8:27:93:1D:AB:E3 Connected: yes Failed to pair: org.bluez.Error.AuthenticationFailed [CHG] Device F8:27:93:1D:AB:E3 Connected: no
  17. install manually, but get error below what's wrong??? pi@bananapim2plus:~/Downloads$ sudo dpkg -i rpimonitor_latest_all.deb dpkg-deb: error: `rpimonitor_latest_all.deb' is not a debian format archive dpkg: error processing archive rpimonitor_latest_all.deb (--install): subprocess dpkg-deb --control returned error exit status 2 Errors were encountered while processing: rpimonitor_latest_all.deb
  18. Can you pair successfully with any bluetooth client devices?
  19. yes, but i don't understand why armbian build script doesn't correct this? also it seems latest armbian 5.14 still doesn't solve bluetooth yet hcitool can see BT controller, but blueman or bluetoothctl cannot also trying to pair using "hcitool cc <btaddr>" is impossible same issue found also here http://unix.stackexchange.com/questions/169931/bluetoothctl-no-default-controller-available
  20. [settings] wireless_interface = wlan0 backend = external wired_interface = eth0 wpa_driver = wext always_show_wired_interface = False use_global_dns = False global_dns_1 = None global_dns_2 = None global_dns_3 = None global_dns_dom = None global_search_dom = None auto_reconnect = True debug_mode = False wired_connect_mode = 1 signal_display_type = 0 should_verify_ap = 1 dhcp_client = 0 link_detect_tool = 0 flush_tool = 0 sudo_app = 0 prefer_wired = False show_never_connect = True
  21. i compile latest armbian 5.14 for banana pi m2+ and now wicd unable to get ip address via onboard wifi previous armbian 5.12 working well below wicd.log anybody has idea why? ---------------------------------------------------------------------------- 2016/06/09 13:31:08 :: Connecting to wireless network TRENDnet 2016/06/09 13:31:08 :: attempting to set hostname with dhclient 2016/06/09 13:31:08 :: using dhcpcd or another supported client may work better 2016/06/09 13:31:11 :: attempting to set hostname with dhclient 2016/06/09 13:31:11 :: using dhcpcd or another supported client may work better 2016/06/09 13:31:12 :: Putting interface down 2016/06/09 13:31:12 :: Releasing DHCP leases... 2016/06/09 13:31:12 :: attempting to set hostname with dhclient 2016/06/09 13:31:12 :: using dhcpcd or another supported client may work better 2016/06/09 13:31:12 :: Setting false IP... 2016/06/09 13:31:13 :: Stopping wpa_supplicant 2016/06/09 13:31:13 :: Flushing the routing table... 2016/06/09 13:31:13 :: Putting interface up... 2016/06/09 13:31:15 :: Generating psk... 2016/06/09 13:31:15 :: Attempting to authenticate... 2016/06/09 13:31:29 :: Running DHCP with hostname bananapim2plus 2016/06/09 13:31:29 :: attempting to set hostname with dhclient 2016/06/09 13:31:29 :: using dhcpcd or another supported client may work better 2016/06/09 13:31:29 :: Internet Systems Consortium DHCP Client 4.3.1 2016/06/09 13:31:29 :: Copyright 2004-2014 Internet Systems Consortium. 2016/06/09 13:31:29 :: All rights reserved. 2016/06/09 13:31:29 :: For info, please visit https://www.isc.org/software/dhcp 2016/06/09 13:31:29 :: 2016/06/09 13:31:29 :: Listening on LPF/wlan0/94:a1:a2:ca:17:d8 2016/06/09 13:31:29 :: Sending on LPF/wlan0/94:a1:a2:ca:17:d8 2016/06/09 13:31:29 :: Sending on Socket/fallback 2016/06/09 13:31:29 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interva 8 2016/06/09 13:31:37 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interva 15 2016/06/09 13:31:52 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interva 18 2016/06/09 13:32:10 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interva 20 2016/06/09 13:32:30 :: No DHCPOFFERS received. 2016/06/09 13:32:30 :: No working leases in persistent database - sleeping. 2016/06/09 13:32:30 :: DHCP connection failed 2016/06/09 13:32:30 :: exiting connection thread
  22. fex for banana pi m2+ already set to 1500000 then "hciattach /dev/ttyS1 bcm43xx 1500000" should be OK btw, I found patch in yocto linux, same like your direction to enable bluetooth in raspberry pi https://lists.yoctoproject.org/pipermail/yocto/2016-April/029425.html maybe Armbian can apply this patch also? ------------------------------------------------------------------------ [bt_para] bt_used = 1 bt_uart_id = 1 bt_uart_baud = 1500000 bt_rst_n = port:PG12<1><default><default><0> bt_wake = port:PG13<1><default><default><0> bt_host_wake = port:PG11<0><default><default><0> bt_host_wake_invert = 0
×
×
  • Create New...