Igor

You need to use rt-patched hostapd: hostapd-rt /etc/hostapd.conf-rt

I agree. I also dumped BTSync from usage some time ago but haven't adjust the build script yet. Currently I am developing the backup / restore part which hanged somewhere in the middle. All general services are open / free to change. I don't prefer any - it must work / suit the purpose.

I manage to build but with different config. Yours was not working - kernel crash / panic (tested only briefly on Hummingboard i2ex). Small config is anyway not an option for me. I need to support all possible hw at once. ... but i bump into one bug very quickly. From no apparent reason one CPU core goes to 100% and stays there. Anyway, it's a progress and amazingly audio is here, mSata is working, i got HDMI now, ... I made a new build for old kernel too: http://www.igorpecovnik.com/2014/08/19/cubox-i-hummingboard-debian-sd-image/ v2.8 / 6.6.2015 Added iMx irqbalance service (Wheezy & Jessie) Added kernel 4.x for testing, unstable Added / fix binary repository for Wheezy and Trusty Added 256Mb emergency swap Ubuntu and jessie install errors fixed, removed busybox-syslogd and changed to default logger due to problems in Jessie and Ubuntu, apt-get upgrade fixed, console font fix, PGP signed archives, documentations update Build script rework – image size shrink to actual size, possible to have fat boot partition on SD card, everything packed as DEB apt-get upgrade ready but not enabled yet, serial console fixed, fixed hostapd under jessie, easy kernel switching, latest patched hostapd for best performance – normal and for realtek adaptors, auto IO scheduler script

It's not necessary that it's on the extension port. http://docs.cubieboard.org/cubieboard1_and_cubieboard2_gpio_pin

Yes. On kernel 4.x we have yet another driver brcmfmac and script.bin is not relevant any more. We have dtb (/boot/dtb/bananapi.dtb). You might need to rename / copy bananapipro.dtb to bananapi.dtb that everything will work.

Thanks. If this is so than I need to take a closer look. How are your script.bin settings? Note that this is just an example, not proper settings. [twi0_para] twi0_used = 1 twi0_scl = port:PB00<2><default><default><default> twi0_sda = port:PB01<2><default><default><default> [twi1_para] twi1_used = 1 twi1_scl = port:PB18<2><default><default><default> twi1_sda = port:PB19<2><default><default><default> [twi2_para] twi2_used = 1 twi2_scl = port:PB20<2><default><default><default> twi2_sda = port:PB21<2><default><default><default> [twi3_para] twi3_used = 1 twi3_scl = port:PI00<3><default><default><default> twi3_sda = port:PI01<3><default><default><default> Do you have things enabled and are you checking correct port?

I had no problems booting even from USB drive on kernel 4.x ... with latest kernel configuration updates of course. My pre-build images are not fixed yet! (I think only OrangePi)

Did you format the partition? mkfs.ext4 /dev/your-device

FAQ. That's really strange. I thought you had a problem with one particular browser. This part is anyway about to change since I am moving content to www.armbian.com when ready. The content is auto generated from here: https://github.com/igorpecovnik/lib/blob/next/documentation/general-faq.md (possible to contribute) Thanks.

Hi. I just checked the blog and everything is operational. FAQ is working and there you can find all basic questions. 1. My time is already super limited and it will get worse For problems you have comments and now forum. I think it's updated good enough (web) - there will be changes in this matter too. 2. https://github.com/ssvb/xf86-video-fbturbo is a project from someone else - you have install info in the wiki. I can't really comment desktop acceleration since I don't use it and it's out of my focus. 4.x has only basic graphics support - no acceleration in any way. 3. With minor adaptations for some boards, yes. Banana R1, a lot has been written, tested and done. We are trying to get better performance but I guess we are hitting the design limit BTW: compare only RAW data transfer without encryption. You got extra two cores on the other side and different kernel with possible encryption support(?) vs none ...

Huh, take one image back. I know that last build is problematic but it must work!

Nice! Yes, it's some unknown hardware problem, hopefully solvable. Banana should work just fine. Hard to say how stable is kernel 4.x since it's new stuff ... people report stability but also some crashes.

This "nologin / false login" occurred in last Jessie build. Since I haven't change anything in this section it's one of unfixed Jessie issue(s). If you can ping than this is a good sign which means Ethernet was initialized properly. There is also a bug in recent u-boot (2015.4) and eth0 will sometimes fail to init. Workaround is u-boot downgrade to one version back (check archive) and will be fixed within next update. Actually you only need to wait for reboot. If you have fairly decent internet connection you have to wait few minutes until apt-get update is finished and the board automatically reboots.

Yes, I assumed that I already fixed dependencies ... but haven't U-boot is also necessary to change - with old one you might have only one CPU core. Note that last version might be broken ... so U-boot one version back - check archive. If u-boot and dtb packets are not installed automatic, install them too: dpkg -i linux-u-boot*.deb dpkg -i linux-dtb*.deb BTW: My Orange PI is hard crashing without any report of error ... with any known kernel. Longest up-time was around one week. Currently clueless.

Yes, thanks for reporting this. I managed to patch & compile but have got no HDMI out. Is this normal?

Current U-boot 2015.4 is broken. Ethernet fails to init also on Lime. I only changed u-boot for the latest archived and it worked. This is temporally solution so working on permanent.

setenv bootargs console=tty1 root=/dev/mmcblk0p1 rootwait consoleblank=0 This is probably due too kernel parameter "console". It should be set to tty1 to see the output while booting. This is valid for serial console too - on the new kernel. You need to change u-boot too. For wifi ... check if firmware is there. Is there anything in the log?

Yes, there are problems with latest build. I am working on it.

Actually it hangs only sometimes - I think the problem is in Eth initialization. Cut the power and try again. (reset won't help). Stick to Wheezy and Trusty.

What is the most proper way to calculate battery discharge ratio? I am trying to add this here: Load: 0.10, 0.50, 0.38 - Memory: 974Mb - Battery discharging: 30% AXP209 gives me: http://linux-sunxi.org/AXP209 - voltage - charge / discharge current Battery capacity should be the only parameter I want to set. Is there any advanced calculation script or simply, but not so accurate, direct connection between voltage and percentage?

Jessie is problematic in general but if you don't get net ... there is/was lately some troubles with u-boot Ethernet controller initialization. Until things are not fully fixed, power off/on helps. If you made an upgrade from older image you need to check boot scripts if they are the same: https://github.com/igorpecovnik/lib/blob/next/documentation/general-faq.md#optional-steps-if-you-update-kernel-to-older-sd-image

Sata install works now on all 4.x but I only rebuild Orange kernel ... which covers all Allwinner boards. Just the name is "orange". Huh. It's stable but it's lack of some functionality and it's hard to say if it's 100% reliable. I haven't used it that much.

Oh, thanks Yes, Orange kernel is good for Banana too. http://forum.armbian.com/index.php/topic/38-config-usb-storage-debugy-on-debian-jessie-404/?p=143

Yes, kernel is the same.

Which kernel are you using? I am not sure if it's working well on newer (4.x) but it must work well within 3.4.107 - I am using some I2C modules by myself. Jessie is also not advisable. For less troubles also rather use Wheezy or Ubuntu trusty.