Skygod

I have Banana M1+ and a spare 16Gb SD card, so am willing to test anything if required.

Apart from the ongoing wireless / no wireless (just keep shutting down and / or rebooting until it comes back) issues, the board has been performing really well. I'm now just doing some basic housekeeping to check everything is okay and noticed that I'm getting a lot of entries in /var/log/syslog like this.... Jan 29 19:17:01 jukebox rsyslogd-2007: action 'action 17' suspended, next retry is Fri Jan 29 19:18:31 2016 [try http://www.rsyslog.com/e/2007 ] (There's around 15 of these every hour) I've seen a 'fix' posted in in respect of Raspbian about this, but wondered if this is something that should be incorporated as part of the distro or is it something users need to discover and fix themselves? http://blog.cagedmonster.net/node/6

What I've been doing for remote storage is to connect to an nbd-server and I then mount the device with nbd-client and copy files to the filesystem then disconnect the client. Not sure if this a particularly good solution, but it's been working for me.

The python script I have is : #!/usr/bin/env python3 # -*- coding:utf8 -*- import logging import pif import pygodaddy logging.basicConfig(filename='godaddy.log', format='%(asctime)s %(message)s', level=logging.INFO) GODADDY_USERNAME="xxxxxx" GODADDY_PASSWORD="xxxxxx" client = pygodaddy.GoDaddyClient() client.login(GODADDY_USERNAME, GODADDY_PASSWORD) logging.debug("Started: before 'for'") for domain in client.find_domains(): dns_records = client.find_dns_records(domain) # Old ip.. old_ip = list(dns_records)[0].value # 'New' ip! public_ip = pif.get_public_ip() # Some loggings and printing logging.debug("Domain '{0}' DNS records: {1}".format(domain, old_ip)) print("Domain '{0}' DNS records: {1}".format(domain, old_ip)) if public_ip != old_ip: if client.update_dns_record(domain, public_ip): logging.info("Domain '{0}' public IP set to '{1}'".format(domain, public_ip)) print ("Domain '{0}' public IP set to '{1}'".format(domain, public_ip)) else: pass # What to do here? .. else: logging.info("No update needed.") print ("No update needed.") (Can't remember where I got it from though. Sorry about that) EDIT : Found the original author and updater # Original Source: # https://saschpe.wordpress.com/2013/11/12/godaddy-dyndns-for-the-poor/ # https://github.com/observerss/pygodaddy # # Modified by Jeremy Sears (https://stackoverflow.com/users/1240482/jsears) This updates the @ A record and I have a CNAME record for the hostname directing to @

I registered a domain at Godaddy and have a python script that runs every ten minutes and updates my A record if my dynamic IP has changed. I can supply details if this is of interest.

+1 in support of this initiative

Probably a $300+ project by the end, so too rich for me at the moment. :-(

You've lost me. How can I connect this to my incoming ADSL2+ presentation?

fiber? In the boonies of N.E.Thailand? :lol:

"There is no CPU governor (yet?), so I assume it's running full speed (1.6Ghz) all the time." Interesting to see on their website..... There will be overclocking options too in the future to 1.8ghz/2.0ghz with newer DDR devices - but this is not public for now. From a quick read of their website, it would appear that this is what the Banana R1 should have been. If I could find a mini pcie ADSL2+ modem, this could be an interesting all-in-one gateway device project EDIT : Actually, thinking about it, exposing the motherboard to the telecomms network might not be such a good idea, as I've already had a modem/router fried during a heavy storm.

A productive couple of days! A couple of modifications made to the supplied bin file (bin2fex and fex2bin) and I'm now using the onboard 3.5mm analog audio with no crackles and using a standard TRS cable as well as the SATA drive on the SATA port instead of via USB. [sata_para] [sata_para] sata_used = 1 sata_power_en = port:PB08<1><default><default><0> [audio_para] [audio_para] audio_used = 1 capture_used = 1 audio_pa_ctrl = port:PH15<1><default><default><0> audio_lr_change = 0 playback_used = 1 capture_used = 1 So, I now have a system running without any USB devices attached and MPD is outputting everything through the analog port. Just have to resolve the issue of the Wireless sometimes failing at boot. (Often a simple 'reboot' brings it back to life)

"Bananian will not boot on your Banana Pi M1, M1+, Pro and R1 any longer " Ouch!

LOL! (Been there, done that)

Cheers for the solution! I saw this behaviour a couple of times on my Banana Pi M1+ and it caused issues with a few scripts such as the python script for setting the GoDaddy DNS Zone to my public IP address. (Learning more every day!)

It's only 55 mins to the New Year here, so let me wish you (and the Armbian gnomes) a good New Year! I've got a system that is providing all the basics of what I wanted to achieve. Just a few 'gotchas' that I hadn't expected, but I knew that the manufacturer wasn't going to be providing much in the way of support, so compared to the stories that I read of people now using their SBC's as paperweights, I've done well to accomplish what I wanted so far. (Think it's time to clone the SD card and just start 'tinkering' with a fall back position)

Cheers for that matteopb, I'll give that a go tomorrow, as I'd almost given up on ever seeing output from the HDMI port.

Cheers Igor. I do apologise for the moaning, but it's just been a few bad days. I accept that the M1+ isn't directly supported, unlike the Pro. (Definately an issue with the sunxi-tools not being in the 3.4.110 upgrade though)

Well, the SATA drive works okay in my Desktop PC and also when installed in a USB / SATA enclosure connected to the Banana Pi M1+, so there's a problem with either the supplied SATA data/power cable or the SATA connectors on the board. [ 0.687636] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 88 [ 1.009622] ata1: SATA link down (SStatus 0 SControl 300) I've now effectively lost both the USB ports, as the onboard sound through the 3.5mm jack keeps sending a 'heartbeat' pulse every couple of seconds which has meant using a USB soundcard and now the SATA connectivity is not functioning, so the brand new 240Gb SSD has to go through USB. Combined with the failed Armbian upgrade and issues rolling back to 3.4.109, the last few days of testing have not been too good.

I remembered this thread about disabling the onboard audio, but the tools have disappeared during the upgrade lrwxrwxrwx 1 root root 82 Dec 28 18:52 fex2bin -> /root/output/debs/jessie/linux-jessie-root-bananapi_4.81_armhf/usr/sbin/sunxi-fexc It would appear that it's now necessary to install sunxi-tools

Still not working on Banana Pi M1+ I've also found that my USB audio is no longer working with MPD and doesn't show in the available soundcards in alsamixer anymore, only the sunxi-CODEC, so my MPD Server service is useless at the moment. I've relinked /boot/zImage to 3.4.109-banana # ls -al /boot total 16988 drwxr-xr-x 3 root root 4096 Dec 30 22:27 . drwxr-xr-x 25 root root 4096 Dec 21 17:02 .. drwxr-xr-x 2 root root 4096 Dec 30 12:00 bin -rw-r--r-- 1 root root 6944 Oct 12 15:52 boot.bmp -rw-r--r-- 1 root root 1698 Dec 30 22:14 boot.cmd -rw-r--r-- 1 root root 1698 Dec 30 22:14 boot.cmd.backup -rw-r--r-- 1 root root 1770 Dec 30 22:14 boot.scr -rw-r--r-- 1 root root 96350 Dec 28 17:49 config-3.4.110-sun7i -rw-r--r-- 1 root root 4032124 Dec 30 12:00 initrd.img-3.4.110-sun7i lrwxrwxrwx 1 root root 25 Dec 7 19:11 script.bin -> /boot/bin/bananapipro.bin -rw-r--r-- 1 root root 2006492 Dec 28 17:49 System.map-3.4.110-sun7i -rwxr-xr-x 1 root root 5607544 Sep 30 19:21 vmlinuz-3.4.109-banana -rwxr-xr-x 1 root root 5607856 Dec 28 17:49 vmlinuz-3.4.110-sun7i lrwxrwxrwx 1 root root 28 Dec 30 22:27 zImage -> /boot/vmlinuz-3.4.109-banana After a reboot, my WiFi was not been restored. [ 30.051564] [ap6210] Succeed to set the gpio ap6210_wl_regon to 0 [ 30.280245] [ap6210] WLAN placed in RESET [ 30.284019] [ap6210] dhd_open: failed with code -5 [ 98.313775] [ap6210] Dongle Host Driver, version 1.28.23.3 (r). [ 98.345840] [ap6210] Compiled in drivers/net/wireless/ap6210 on Sep 30 2015 at 14:15:34. [ 98.393991] [ap6210] Succeed to set the gpio ap6210_wl_regon to 1 [ 99.264185] [ap6210] WLAN going back to live [ 99.542319] [ap6210] dhd_bus_devreset: WLAN ON [ 99.555648] [ap6210] Final fw_path=/lib/firmware/ap6210/fw_bcm40181a2.bin [ 99.562273] [ap6210] Final nv_path=/lib/firmware/ap6210/nvram_ap6210.txt [ 99.570399] [ap6210] download firmware /lib/firmware/ap6210/fw_bcm40181a2.bin [ 99.872092] [ap6210] bcmsdh_set_irq Flag = 1 [ 99.883177] [ap6210] dhd_bus_devreset: WLAN ON DONE [ 101.904228] [ap6210] dhdcdc_query_ioctl: dhdcdc_msg failed w/status -5 [ 101.910619] [ap6210] dhd_preinit_ioctls: can't get MAC address , error=-5 [ 103.930875] [ap6210] dhdcdc_set_ioctl: dhdcdc_msg failed w/status -110 [ 103.937925] [ap6210] dhd_check_hang: Event HANG send up due to re=0 te=2 e=-110 s=2 [ 103.955334] [ap6210] bcmsdh_set_irq Flag = 0 [ 103.972734] [ap6210] dhd_bus_devreset: WLAN OFF DONE [ 103.990423] [ap6210] Succeed to set the gpio ap6210_wl_regon to 0 [ 104.371258] [ap6210] WLAN placed in RESET [ 104.375668] [ap6210] dhd_open: failed with code -14 [ 104.395402] [ap6210] In : chip crash eventing [ 104.455132] Modules linked in: cpufreq_userspace wifi_gpio snd_usb_audio sg snd_hwdep snd_usbmidi_lib snd_rawmidi snd_seq_device nbd spidev ap6210 a20_tp 8021q garp stp llc sunxi_ir hidp rfcomm hci_uart bluetooth ppdev lp parport [ 104.649135] [<c06f2848>] (cfg80211_disconnected+0xc0/0xc4) from [<bf105200>] (wl_cfg80211_hang+0x44/0x7c [ap6210]) [ 104.723126] [<bf105200>] (wl_cfg80211_hang+0x44/0x7c [ap6210]) from [<c004d18c>] (process_one_work+0x12c/0x3b0) [ 105.214911] [ap6210] reg_notifier for intiator:0 not supported After a 2nd reboot though the WiFi came up fine even though no other devices had been connected or disconnected. [ 6.138454] [ap6210] Succeed to set the gpio ap6210_wl_regon to 0 [ 6.951165] [ap6210] WLAN placed in RESET [ 7.032236] bcmdhd: exports duplicate symbol bcmsdh_probe (owned by ap6210) [ 7.052995] bcmdhd: exports duplicate symbol bcmsdh_probe (owned by ap6210) [ 7.102658] bcm4330: exports duplicate symbol bcmsdh_probe (owned by ap6210) [ 7.110036] bcm4330: exports duplicate symbol bcmsdh_probe (owned by ap6210) [ 26.081445] [ap6210] dhd_device_event: bus not ready, exit [ 26.095983] [ap6210] Dongle Host Driver, version 1.28.23.3 (r). [ 26.103103] [ap6210] Compiled in drivers/net/wireless/ap6210 on Sep 30 2015 at 14:15:34. [ 26.108188] [ap6210] Succeed to set the gpio ap6210_wl_regon to 1 [ 26.331527] [ap6210] WLAN going back to live [ 26.572343] [ap6210] dhd_bus_devreset: WLAN ON [ 26.578394] [ap6210] Final fw_path=/lib/firmware/ap6210/fw_bcm40181a2.bin [ 26.584075] [ap6210] Final nv_path=/lib/firmware/ap6210/nvram_ap6210.txt [ 26.590678] [ap6210] download firmware /lib/firmware/ap6210/fw_bcm40181a2.bin [ 26.874086] [ap6210] Dongle ready, protocol version 4 [ 26.878999] [ap6210] Dongle ready, protocol version 4 [ 26.891192] [ap6210] Firmware up: op_mode=0x0002, Broadcom Dongle Host Driver mac=02:1a:11:f3:10:44 [ 26.907026] [ap6210] Firmware version = wl0: Apr 22 2013 14:50:00 version 5.90.195.89.6 FWID 01-b30a427d [ 26.910023] [ap6210] Chip: a962 Rev 1 Pkg 9 [ 41.064538] [ap6210] netdev_ifidx(5), chan_type(1) target channel(5) [ 41.556113] [ap6210] No WPSIE in beacon [ 41.559026] [ap6210] No WPSIE in beacon Another reboot without the USB Soundcard installed brought up the WiFi once again, and I then plugged in the Soundcard, but there's a problem in that it's no longer recognised in the way it was before starting the upgrade process. I copied the backup of /boot/bin/bananapipro.bin that I had and rebooted yet again, but the soundcard is no longer working as before. I've tried disconnecting and reconnecting it to no avail. [ 212.112649] cannot create card instance 0 [ 212.117789] snd-usb-audio: probe of 4-1:1.0 failed with error -5 [ 212.132955] input: USB PnP Sound Device as /devices/platform/sw-ohci.2/usb4/4-1/4-1:1.3/input/input3 [ 212.144592] generic-usb 0003:0D8C:013C.0002: input,hidraw0: USB HID v1.00 Device [USB PnP Sound Device] on usb-sw-ohci-1/input3 [ 396.897950] usb 4-1: USB disconnect, device number 4 [ 396.903161] ehci_irq: port change detect [ 397.033202] ehci_irq: port change detect [ 397.322679] usb 4-1: new full-speed USB device number 5 using sw-ohci [ 397.514219] usb 4-1: can't set config #1, error -62 [ 397.519555] usb 4-1: USB disconnect, device number 5 [ 399.682993] ehci_irq: port change detect [ 399.856737] ehci_irq: port change detect [ 399.911759] The port change to OHCI now! [ 400.196220] usb 4-1: new full-speed USB device number 6 using sw-ohci [ 400.396483] cannot find the slot for index 0 (range 0-0), error: -16 [ 400.399532] cannot create card instance 0 [ 400.404574] snd-usb-audio: probe of 4-1:1.0 failed with error -5 [ 400.419881] input: USB PnP Sound Device as /devices/platform/sw-ohci.2/usb4/4-1/4-1:1.3/input/input4 [ 400.431924] generic-usb 0003:0D8C:013C.0003: input,hidraw0: USB HID v1.00 Device [USB PnP Sound Device] on usb-sw-ohci-1/input3 (Not the best of days!) EDIT 31/12 : Sound to USB Soundcard eventually restored after reinstalling sunxi-tools and fex2bin the older /boot/bananapupro.fex that I'd created to disable the onboard sound output.

Have just run an apt-get update & upgrade and see I'm now on 3.4.110 # uname -a Linux <my fqdn> 3.4.110-sun7i #10 SMP PREEMPT Mon Dec 28 11:48:43 CET 2015 armv7l GNU/Linux script.bin is still linked to /boot/bin/bananapipro.bin lrwxrwxrwx 1 root root 25 Dec 7 19:11 script.bin -> /boot/bin/bananapipro.bin No WiFi now though :-( Output of dmesg | grep ap6210 [ 5.727940] [ap6210] parse wifi_used failed in script.fex. [ 5.732266] [ap6210] bluetooth is disable in script.fex. [ 5.741335] [ap6210] No wifi type selected, please check your config. [ 5.934401] [ap6210] WLAN placed in POWER ON [ 7.936360] [ap6210] failed to power up wifi chip, retry again After 4 retries it simply gives up trying I have also just connected a brand new 240Gb SATA SSD to the device, but it's not being recognised. I'll have to hook it up to my desktop to check the disk works and if so, then check I've actually got power being supplied by the SATA connector on the Banana Pi M1+

tkaiser, I now know that :-) I've seen a few threads that have gotten quite emotive about the issue as systems that previously worked fine simply stopped booting. It took me a couple of days to determine the problem, but I won't get bitten twice with this one. I'm really pleased with this Armbian distro for my little Banana Pi M1+ so far. I've got so much running on this device now and it handles everything I've thrown at it so far. Connecting a tablet / smartphone using MPDroid to the MPD server is working really well, but one guy simply wanted to stream the audio from his Windows laptop to the audio output on the Banana and he's now able to do it through TuneBlade by connecting his sound output to the Shairport service that I've installed. I'm still working my way through the ID3 tagging of c.30k tracks which I'm doing on my Windows desktop and then using using Robocopy to update the files on the Banana through a Samba share that I have created. The best $70 I've spent on hardware I reckon (including heatsink, case, fan, PSU, Micro SD) plus an initial donation to Armbian for making it all possible on a hardware platform that I'd no previous experience with.

I had disconnected the attached hard drive and it seems that Debian Jessie won't boot if there's an entry in /etc/fstab referencing a non-existent device.

Okay daft question time! I set up the Banana Pi as a Shairport server and all was working really well, but when I rebooted, I've lost any way of connecting, as the SSH server isn't starting. I have network connectivity, as I ping the IP address from another machine on the network. Thinking I could check the boot sequence, I hooked the Banana Pi up to the TV HDMI input, but that simply says "Unrecognised Signal", so any tips on how to gain access?

@indus, I've decided to go this route rather than bananian, as I'm looking for a distro that provides some 'commonality' across a number of SBC boards. For my current project a Banana Pi M1+ provides the hardware I require. I have plans for another SBC deployment within my (small) network, where a Raspberry Pi may be suitable and another where a Cubie may be best suited. Having a common distro across all these boards is why I chose this route.