Jump to content

Bernie_O

Members
  • Posts

    45
  • Joined

  • Last visited

Everything posted by Bernie_O

  1. apt-get update && apt-get dist-upgrade should be enough
  2. Which kernel-version are you running? There was a bug in kernel 4.7/4.8: https://encrypted.google.com/search?hl=de&q=oom-killer kernel bug 4.7 There is also a memory-parameter that configures how much % of memory is used before the oom-killer is invoked. That might help you until the kernel-bug is fixed. Look for vm.overcommit_ratio in the last post here: http://serverfault.com/questions/362589/effects-of-configuring-vm-overcommit-memory
  3. I think the developer (E.Jurgensen) might be willing to help. So I would suggest to ask him directly in this thread: https://www.raspberrypi.org/forums/viewtopic.php?t=49928 I know this is a Raspberry-Pi Forum, but regarding sound-card configuration there should be no difference. Maybe he has an idea, or another user has a similar setup to yours. If you can solve your problem it would be nice to post the solution here as well. Best wishes, Bernie_O
  4. This looks like forked-daapd is trying to access the correct device, but there is another service/application running which accesses and thus blocks the audio device - or another application was running which used the audio device and didn't free the access again after using that audio-device. Do you have an idea what that could be? Try to disable it (or maybe reboot) and then try again with forked-daapd. I think we found the correct card and mixer. But with the "device or resource busy" problem I can't help any further. This you need to figure out yourself. Good luck :-)
  5. This doesn't work? card = "hw:1" mixer = "I2s Or Pcm Audio Mode Select format"
  6. I took the according name from the output of amixer and it works on my Banana Pi running Armbian Debian Jessie. As example: Excerpt from output of command "amixer": Simple mixer control 'Power Amplifier',0 Capabilities: pvolume pvolume-joined Playback channels: Mono Limits: Playback 0 - 63 Mono: Playback 40 [63%] [-23.00dB]Excerpt of my forked-daapd.conf: # Localaudio output audio { # Name - used in the speaker list in Remote nickname = "My Nickname" # Audio device name for local audio output # card = "default" # Mixer channel to use for volume control - ALSA/Linux only # If not set, PCM will be used if available, otherwise Master. mixer = "Power Amplifier" }Hope that works for you as well.Cheers. Edit: forked-daapd from official debian-jessie-repo (installed with: "apt-get install forked-daapd", version 22.0-2)
  7. Is there a reason for you to compile it yourself? I've been using the version from the official packages for quite a while now. I remember there were problems long time ago with version 0.19. But since Espen Jurgensen took over the development (from forked-daapd >= 0.20) this works very reliable. Installation from the official repos is really easy... Debian: https://packages.debian.org/forked-daapd Ubuntu: http://packages.ubuntu.com/forked-daapd
  8. I found a solution: There seems to be a voltage difference between ground on AV jack and actual ground on Banana Pro which is responsible for that noise: http://forum.lemaker.org/forum.php?mod=viewthread&tid=23054&page=1#pid91781 My device is a Banana Pi, but I suspected that there is a similar voltage difference. By connecting a cable from ground pin on AV jack and GPIO-ground (PIN 9) the noise is gone :-) Cheers, Bernie_O
  9. Hi, meantime I switched to mainline kernel (4.6.3) and audio output via 3,5mm jack works. However: when I stop playing music, there is quite some noise coming out of the speakers which is not the case with legacy kernel. Muting the devices and turning volume to zero (like the default-setting right after armbian-installation) doesn't help. Is this a known issue? Cheers, Bernie_O.
  10. Hi, currently I have armbian installed on an SD-Card with kernel 3.4.112-sun7i on Banana Pi. I'd like to test how armbian works installed on SATA with vanilla-kernel. Therefore I would install armbian (Vanilla) on SATA. Switching between both systems would then require a shutdown, exchange of SD-Card and startup the system again. Since i am a lazy person I'd like to know whether it is possible to use the SD-Card with 3.4.112 and just exchange the folder /boot with the one from the SD-Card I installed armbian-Vanilla on SATA (to avoid standing up, walking to the banana pi which is located in another room, exchanging the SD-Card, rebooting, walking back and sitting down again...)? The idea behind is to easily switch between both systems just by exchanging the /boot folder and then rebooting the system (without having to walk around...). Would there be any problems with this procedure? Best, Bernie_O
  11. It looks like there are problems with the new official AptRepository of tvheadend at bintray. When I do an apt-get update I get the following error: Error: http://dl.bintray.com jessie/release armhf Packages 403 Forbidden [IP: 5.153.35.248 80] I think they are working on it. Don't know when it will be fixed...
  12. For the record: it is not a good idea to have the SD-card unmounted, when doing an armbian-upgrade. Because during an armbian-upgrade there need to be files written in the folder /boot on the SD-card.
  13. No problem, just thought I'd mention it here if anybody else runs in this issue. Thanks for fixing even before I reported it and keep up the good work
  14. Hi all, yesterday I updated my system (Banana Pi) to the latest version (5.15, legacy-kernel) with apt-get update && apt-get upgradeAfter the upgrade the fixed-IP for the device was gone. It looks like the link /etc/network/interfaces has been overwritten with a new file during the upgrade - so I had to set up fixed IP again in /etc/network/interfaces like described here: http://docs.armbian.com/User-Guide_Getting-Started/#how-to-set-fixed-ip For the future I suggest changing the the upgrade-script so that the fixed IP is not overwritten. Additionally I think it would be good to write a short note in the changelog that the setting might be gone after the upgrade to 5.15. Cheers, Bernie_O
  15. Hm - maybe I misconfigured something somewhere, but I am using minidlna on my banana pi via VPN when I am not at home for quite a while now without any problems. IPsec VPN is not setup on the banana pi, but on my Router (it is a fritz.box 7390).Service-discovery works only when I am at home in my LAN but once the client (I use iPhone and iPad with an app called nPlayer) is configured - I can access my media files via dlna when I am physically not at home but connected via VPN. I don't think I did anything special in configuring minidlna and I am willing to share the settings of my /etc/mindlna.conf if someone is interested...
  16. Thank you very much for the answer and for armbian in general :-)
  17. Would it even be possible to unmount SD, when system (on HDD) has finished booting?
  18. Hi, idea: 1. move the commands for manipulating gpio to a script owned by www-data outside the webroot with chmod 100 (only executable, not readable nor writeable by www-data). 2. remove general sudo-privileges for www-data by deleting this (in the 1st post added) line from /etc/sudoers: www-data ALL=NOPASSWD: ALL 3. grant sudo privileges for www-data only for that script by adding this line to /etc/sudoers: www-data localhost = NOPASSWD: /path/outside-webroot/gpio-script.sh 4. in PHP just call the new script via shell_exec: shell_exec("sudo /path/outside-webroot/gpio-script.sh"); The script could be written in a way that different parameters could be passed to it, to have the ability to do different gpio-commands with it. Would that raise security to an acceptable level? Best, Bernie_O Edit: 1. I am not absolutely sure, but I think with my approach it is not necessary to link gpio to web-directory (ln -s /sys/class/gpio /var/www/html/gpio). 2. It might be better to use a relative path in the PHP-command shell_exec();
  19. Thank you very much for clarifying this for me. I will wait for an Armbian-release with Kernel 4.5 for my switch to mainline-kernel then. Cheers, Bernie_O.
  20. Hi, I'd quite like to switch from legacy to mainline due to various improvements I read about. I need adio-output via the 3,5mm-audio-jack though. Do I understand this thread correctly that audio will work with Mainline-Kernel 4.4 (once it is released) on Banana-Pi 3,5mm-audio-jack? Cheers, Bernie_O.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines