Search the Community

Good Morning, I'm using the 5" LCD of LeMaker designed for Banana Pi. For some reason I changed from legacy Kernel to vanilla kernel. But now in the vanilla kernel touch screen driver isn't available anymore. In legacy kernel it the ft5x_ts module. Is there an other way to make my Display working with touch again? Displays: http://wiki.lemaker.org/BananaPro/Pi:LCD_Module Martin

Hi guys, I'm running Armbian on my BananaPi for almost a year now and it has always run seamlessly, since the latest upgrade to Arabian 5.20 (Kernel 4.7.3) I've started to experience problems with the stability of the daemons. Monit is doing an hard job lately restarting many times a day almost all the processes I'm running as damons, the most affected by the Killing are Python 2.7 (running Sickrage) and Deluge daemon. In particular Deluge being killed so many times a day is quite annoying since I have to recheck the integrity of many files almost every time I get the service up again. I didn't install any additional software that could have created this instability apart the new version of Armbian so I'm asking: Is there the possibility that the Out Of Memory Killer has become too aggressive on the latest Arabian? Is that a common issue or something I can do to solve? Thanks a lot. Giulio

I am working on a new project which uses the Banana Pi to capture USB output destined for a printer in order to log the output from a system. The BananaPi will need to be a simple plugin which sits between the machine and a connected USB printer - so we want to: a ) Mimic the connected USB printer (so that the machine thinks it still has the original printer attached) b ) Capture the output from the machine c ) Send the captured output onwards to the printer. The BananaPi seemed the obvious choice as it has the built in USB OTG port and we would use the gadget printer to mimic the attached printer. Unfortunately, the Bananian images do not support the gadget printer at all (even after configuring them for Banana Pi + OTG, the command modprobe g_printer returns an error. We therefore installed the Vanilla flavour of Jessie from Armbian, and modprobe g_printer now seems to work. However, there is no /dev/g_printer which we expected to see - is this now stored in a different place, or maybe we have missed something?

I'm sorry if I come across as incompetent but I have limited skills in linux and I really dont know where else to turn to. I recently bought a DVB-S reciever to plug into my SBC (banana Pi M1) to use with tvheadend, as opposed to getting a dedicated chinese box. I just cant seem to get it to work! This is the Tuner I bought: https://www.linuxtv.org/wiki/index.php/Geniatech_HD_Star_DVB-S2_USB2.0 Apparently I have revision 3 of the board: http://imgur.com/3IhpuGG This is the comparison between the lsusb in the wiki, and my board: http://imgur.com/iHN3R5R This is the output of dmesg: [ 7.847279] sun4i-ss 1c15000.crypto-engine: Die ID 0 [ 7.911683] dw2102: su3000_identify_state [ 7.911711] dvb-usb: found a 'SU3000HD DVB-S USB2.0' in warm state. [ 7.911733] dw2102: su3000_power_ctrl: 1, initialized 0 [ 7.919512] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 7.920151] DVB: registering new adapter (SU3000HD DVB-S USB2.0) [ 7.931083] dvb-usb: MAC address: 00:af:78:66:2b:cf [ 8.002739] Registered IR keymap rc-empty [ 8.003442] input: sunxi-ir as /devices/platform/soc@01c00000/1c21800.ir/rc/rc0/input1 [ 8.003487] rc rc0: sunxi-ir as /devices/platform/soc@01c00000/1c21800.ir/rc/rc0 [ 8.021047] sunxi-ir 1c21800.ir: initialized sunXi IR driver [ 8.025796] lirc_dev: IR Remote Control driver registered, major 246 [ 8.034635] rc rc0: lirc_dev: driver ir-lirc-codec (sunxi-ir) registered at minor = 0 [ 8.034663] IR LIRC bridge handler initialized [ 8.084644] sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec mapping ok [ 8.300174] DS3000 chip version: 0.208 attached. [ 8.456265] ts2020 2-0060: Montage Technology TS2022 successfully identified [ 8.456359] dw2102: Attached DS3000/TS2020! [ 8.456387] usb 1-1: DVB: registering adapter 0 frontend 0 (Montage Technology DS3000)... [ 8.457379] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro [ 8.523385] Registered IR keymap rc-su3000 [ 8.523992] input: IR-receiver inside an USB DVB receiver as /devices/platform/soc@01c00000/1c14000.usb/usb1/1-1/rc/rc1/input2 [ 8.524650] rc rc1: IR-receiver inside an USB DVB receiver as /devices/platform/soc@01c00000/1c14000.usb/usb1/1-1/rc/rc1 [ 8.524674] dvb-usb: schedule remote query interval to 150 msecs. [ 8.524691] dw2102: su3000_power_ctrl: 0, initialized 1 [ 8.524700] dvb-usb: SU3000HD DVB-S USB2.0 successfully initialized and connected. [ 8.524875] usbcore: registered new interface driver dw2102 [ 8.790118] Adding 131068k swap on /var/swap. Priority:-1 extents:1 across:131068k SSFS [ 10.156341] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 10.371942] systemd-journald[233]: Received request to flush runtime journal from PID 1 [ 10.919515] RX IPC Checksum Offload disabled [ 10.919550] No MAC Management Counters available [ 10.919937] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 13.225766] random: nonblocking pool is initialized [ 13.851099] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 13.852131] NFSD: starting 90-second grace period (net c0e92c80) [ 16.903720] sun7i-dwmac 1c50000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 16.903812] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 18.533280] dw2102: su3000_power_ctrl: 1, initialized 1 [ 18.553986] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)... [ 18.557242] ds3000_firmware_ondemand: Waiting for firmware upload(2)... [ 19.645835] usb 1-1: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000) [ 19.649659] dw2102: su3000_power_ctrl: 0, initialized 1 [ 19.654783] dw2102: su3000_power_ctrl: 1, initialized 1 [ 19.674284] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)... [ 19.674555] ds3000_firmware_ondemand: Waiting for firmware upload(2)... This is the output of lsusb: bpi@bananapitv:~/DVB-S_FW$ lsusb -s 002 -v Bus 001 Device 002: ID 1f4d:3000 G-Tek Electronics Group Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x1f4d G-Tek Electronics Group idProduct 0x3000 bcdDevice 0.00 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 219 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 1 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 3 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x13f2 3x 1010 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 2 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 3 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x12d6 3x 726 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 3 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 3 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x12ae 3x 686 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 4 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 3 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x03ca 1x 970 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 5 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 3 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x02ac 1x 684 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 6 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 3 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x03ac 1x 940 bytes bInterval 1 I even downloaded the firmwares and placed them in /lib/firmware : bpi@bananapitv:~/DVB-S_FW$ ls /lib/firmware/ | grep "dvb" dvb-demod-mn88472-02.fw dvb-fe-ds3000.fw dvb-fe-xc4000-1.4.1.fw dvb-fe-xc5000-1.6.114.fw dvb-fe-xc5000c-4.1.30.7.fw dvb-usb-dib0700-1.20.fw dvb-usb-dw2102.fw dvb-usb-it9135-01.fw dvb-usb-it9135-02.fw dvb-usb-tbs5520.fw dvb-usb-terratec-h5-drxk.fw dvb_nova_12mhz.inp dvb_nova_12mhz_b0.inp sms1xxx-hcw-55xxx-dvbt-02.fw sms1xxx-nova-a-dvbt-01.fw sms1xxx-nova-b-dvbt-01.fw sms1xxx-stellar-dvbt-01.fw What happens is that I login to the web interface, set up a mux, enable the receiver, and associlate it with the mux I made, but it never seems to work? All my scans fail. Im fairly sure that my line is alright since the cheap chinese box I had beforehand picked up the signals perfectly fine. I went to the great and glorious google to try to look for an answer, I found out that for my revision of the tuner, a patch has been developed: https://gist.github.com/pdp7/cafd7e32fc3ec9e7a268 Link: https://github.com/Outernet-Project/orx-rpi/commit/4b336a8940604c91187ea7680a3e991d3c28ce37#diff-8b56063fa57e24b219cc9aba37202653 I've read that you need to recompile the kernel to patch it. This is the current kernel I am on: bpi@bananapitv:~$ cat /proc/version Linux version 4.6.3-sunxi (root@pluton) (gcc version 5.3.1 20160413 (Ubuntu/Linaro 5.3.1-14ubuntu2) ) #7 SMP Tue Jul 5 16:23:41 CEST 2016 bpi@bananapitv:~$ uname -a Linux bananapitv 4.6.3-sunxi #7 SMP Tue Jul 5 16:23:41 CEST 2016 armv7l GNU/Linux I edited /etc/apt/sources.list and uncommented "deb-src" and then did apt-get update and tried: bpi@bananapitv:/media/bpiDrive/KERNEL$ sudo apt-get source linux-image-$(uname -r) Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for linux-image-4.6.3-sunxi Soooo now I'm stuck. I dunno what to do ): This is waaaay above my current skillset. Since I cant get it done myself, I really don't mind paying somebody who will has the skills to be able to do it. I dont see anything wrong with compensating them for their time/expertise. How much would be reasonable for a kernel patching/recompile? USD10? USD20? I really have no idea what the going rate is, so I'm sorry if anybody takes offence to my offers. Anyways, thanks for all your time and reading my drivel. I tried to be as detailed as I could, and include any important details.

Hello, is the last BPi Vanilla wheezy image somewhere still available for download? I want to run it with Open Media Vault, which still needs wheezy. Thanks a lot. Michael

For a lark I wanted to see if a BPi would do as a softsynth. I started with the very nice 2.9 Jessie image* and 4.x kernel, but noticed only then that there's no sound, so I installed the 3.4 packages. After booting, ALSA seems to be working fine wrt line sound output and mixer. I could also play MIDI files with fluidsynth fine and hear clear audio on headphones. Connecting a USB MIDI keyboard also gets detected and its ports show up. Now, fluidsynth as a server won't start and neither does jackd. Both seem to complain about missing /dev/snd/seq. So I'm wondering if there's a kernel module or option missing or if it's an artifact of there being no actual MIDI synth chip available. But it looks like neither fluidsynth nor jack can register themselves for routing MIDI at all. There might of course be some unrelated problem that I haven't noticed. The device is not in reach now so I don't have exact output, but I thought I'd throw this topic up for a start. * Thank you for the effort put into these! It's great to have ongoing development on these boards. Firstboot on 2.9 didn't work unless I resized the partition first to make some free space. I imagine this is probably fixed in a later image as the brokenness note on the page is gone.

I am trying to connect a SNBC receipt printer to my Banana Pi - model number: BTP-r580(II) However, dmesg shows that whilst it is identified as a USB device, it is not identified as a printer (probably not helped by the fact that all of their receipt printers appear to have idVendor = 0x154f and idProduct = 0x154f Whilst their website (http://www.newbeiyang.com) has downloads for linux drivers, once connected there is no /dev/usb nor a dev/ttyUSB0 directory (in case it is recognised as a serial device). The linux drivers appear to be used for CUPs which is not installed, so I have not downloaded them. Someone else has the same problem on the Raspberry Pi with a differernt printer from this manufacturer - https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=119253 Where should I go from here?

Hi Folks, I installed armbian Jessie with Desktop and Kernel 4.6.3 on my Banana Pi. I'm glad to see, that most of modules I need are installed and working properly. Good job, thanks! But there is one little problem I've got with the kernel. I need pwm (Pin PB2) to control the backlight of my LCD. With Bananian I used sunxi-pwm modul. Worked fine, but isn't installed in the kernel 4.6.3. I know there are ways to build it into the kernel. But befor I'll build an own kernel, I'm hoping of an other way to make pwm for backlight working again. I saw an pwm folder at /sys/class/pwm and also pwm-sun4i modul can be loaded. Unfortunately /sys/class/pwm is empty and stays empty even when I load pwm-sun4i. In the devicetree I can see a pwm device: /sys/firmware/devicetree/base/soc@01c00000/pwm@01c20e00. Has anyone an Idea how I can pwm make working with this System? Yours Martin

Hi, I updated my image for BananPi from v5.00 (Wheezy) to the latest one (v5.16). Everything works fine, but if I run "apt-get upgrade" I get the message that the package "linux-whezzy-root-bananapi" is reserved (will not be installed). hardware-info says 6 packages to update, but I can't... Is this correct? Do I need this package to be on the latest version? What to do? Thanks. Steffen

I know Banana pi had issues in the past connecting at gigabit speeds. I thought that was a fixed problem, though. I did a fresh Jessie server install today and it still connects at 100 megabit. Is there a user action that must be taken? According to http://linux-sunxi.org/LeMaker_Banana_Pi the GMAC wasn't supported in the community kernel but should be in later kernels. Is this still an issue? How does one set GMAC_TX_DELAY to 3? Is that a config file thing or a patch that needs to be applied? Are other Banana Pi owners just living with 100 megabit speeds? A bit of system information: ~> uname -a Linux bananapi 4.6.3-sunxi #7 SMP Tue Jul 5 16:23:41 CEST 2016 armv7l GNU/Linux ~> dmesg | grep Link [ 22.504469] sun7i-dwmac 1c50000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx ~> sudo ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: external Auto-negotiation: on Supports Wake-on: d Wake-on: d Current message level: 0x0000003f (63) drv probe link timer ifdown ifup Link detected: yes

Hey there, I have managed to compile your great image. How ever I dont receive any HDMI signal on boot. During the first boot I got atleast some picture. but after loading kernel all went black. See log: https://sprunge.us/YjQd I used a] HDMI to VGA converter b] a direct HDMI connection. Both screens usually work. See log: https://sprunge.us/YjQd I will continue to install the system via SSH, however I would like to use HDMI lateron e.g. in emergency cases. Greetings!

Hello! Is there any hope to acquire a r3p2 or a newer Mali driver support in an armbian kernel for Banana Pi?

Hi All! Legacy kernel says: "Enabled audio devices: analog, 8 channel HDMI, spdif and I2S (if wired and enabled in HW configuration)" But there is no multi channel device listed in aplay -L , like surround51, surround71, etc. With "speaker-test -D default:sunxisndhdmi -c 6 -t wav", We got a downmixed stereo result. Receiver device is a BEM-182 Broadcast Monitor on its HDMI input - only 2 VU-meter band appears. Other test setup is the same receiver in SDI input mode with an HDMI to SDI converter. Specs of this adapter declares that it supports 8 channel, and this time 8 VU-meter band appears on the monitor so device is ready to receive multi-channel audio, but the 6-8CH audio transmission is still downmixed to stereo... Are there anything that should be switched manually / reconfigured on the BPi transmitter side? Or is it an incompatibility situation? Best regards, Peter

Hi! I have Banana PI and LVDS 5" with touch screen. I installed latest image and folow procedure to enable it: and modify /etc/module to support touch screen, But I find out there is no bananapilcd5.bin in /boot/bin folder. Then I had downloaded banana_pi_5lcd.bin from lemakaer page (https://github.com/LeMaker/fex_configuration/tree/master/bin), and execute above line again (first rename it and put into bin folder). LCD Screen is now working but I have no touch screem Am I missing something ?

Hello Forum, please excuse my bad English. I try setting up a stratum1-server. Based on GPS. For this I use the Banana Pi with kernel 4.6.2 and the Adafruit GPS. The GPS is connected to GPIO J12 and works. RX/TX is not the problem. The problem is the right pin for the PPS-signal. dmesg|grep pps* [ 0.001207] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000) [ 0.067281] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 4 [ 3.260009] pps_core: LinuxPPS API ver. 1 registered [ 3.260018] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 3.260048] PTP clock support registered [ 3.322715] simple-framebuffer 7fe79000.framebuffer: framebuffer at 0x7fe79000, 0x178e00 bytes, mapped to 0xf0900000 [ 3.987818] 8021q: 802.1Q VLAN Support v1.8 [ 4.023716] mmc0: host does not support reading read-only switch, assuming write-enable [ 4.122304] No HW DMA feature register supported [ 4.122317] TX Checksum insertion supported [ 4.298551] usb_phy_generic.0.auto supply vcc not found, using dummy regulator [ 6.863909] pps_gpio: unknown parameter 'gpio_pin' ignored [ 7.002898] systemd[1]: Starting Apply Kernel Variables... [ 7.989677] sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec mapping ok lsmod | grep pps pps_gpio 2655 0 My question: How do I specify that (maybe) PIN 18 is for PPS. I tried /etc/modprobe.d/pps-gpio.conf with options pps-gpio gpio_pin=18 But in dmesg appears [ 6.863909] pps_gpio: unknown parameter 'gpio_pin' ignored Probably it is not a major problem, but I'm stuck at this point. Greetings from Berlin

I had working Banana Pi -> I compiled latest kernel (all config were default) and installed it -> Banana Pi did not boot, it was stucked on "Raising network interfaces" -> I downloaded latest image (Debian Jessie) and flashed it on SD card -> Banana Pi still stucked on "Raising network interfaces". Banana Pi is connected via normal cable directly to the router with DHCP. I have also tested cable and router and tried to use different cable. I have not changed anything else.

Hy everyone, I am trying to get armbian running on my bananapi. The problem is if i write the raw file to the sdcard (following the instructions) no boot partition is created. The bananapi does panic while booting and restarts after a few seconds... Any ideas? Thanks!

Hi, Since latest update just a few days ago (Linux bananapi 4.5.5-sunxi) , the bananpi keeps telling me this: [ 5 updates to install: apt-get upgrade] . When i try to upgrade there arent anything to upgrade. In did apt-get update and apt-get upgrade and nothing to upgrade. I manually execute /etc/update-motd/40-updates and its true that it says that there are 5 updates. So there must be something there that its not chaning. Any tips on this? EDIT: ok i just fixed this by manually editing the file /var/cache/apt/archives/updates.number and setting it to 0 but i think this should be automatic and it wasn't working for some reason. (seemed like the script wasn't updating that file).

Hi, I'm fairly new to linux and I've been trying to get my banana pi OTG port to act as a HID device when plugged in. I've been looking to do it using configfs and usb_gadget but I have no idea how to get this working. Do I need to compile the kernel with additional options to get this working? I've googled for days now and tried various different solutions but not got far with it. Any help is much appreciated.

Hello, I am facing an issue regarding audio playback using the vanilla kernel( v4.5.2 ) for Banana Pi. There is no sound via the analog audio jack. aplay -l does show my playback device though. Here are some screenshots of my current config: speaker-test is throwing error: Should I need to configure anything else?

Hi! Anyone use display? GND: Shared VCC: Power supply SDA: Bus Information SCL: clock data bus From site: https://github.com/vvromanov/cb_i2c_lcd https://github.com/vvromanov/cb_i2c_lcd/blob/master/i2c_lcd.c#L28 But how to right connect display?

I have downloaded http://mirror.igorpecovnik.com/test/Armbian_5.00_Bananapi_Debian_jessie_4.4.0-rc5.zip and tried OTG, as I though that it´s support was added in kernel 4.3, but it is not wokring. Is there a way to enable it? I am missing this feature, yet I do not want to go back to legacy kernel. I tried various usb peripherals and hubs, but OTG port is not powered. Thank you.

Hi, I am using Armbian_jessie_4.5 with kernel 4.3.x on a Banana pi. When entering any systemctl related command, I get the following error: Failed to get D-Bus connection: Unknown error -1 Any idea on what the problem might be? It's a fresh install.