Decker

Hi, 3 flashing led diodes of my Banana Pi make good party atmosphere when I want to sleep. what are ways to disable led diodes on Banana Pi? Is there a way to disable them without recompiling kernel? Can it be done by editing script file in /boot? What exactly do I need to change to switch them off? Thank you very much!

Hi tkaiser, thank you for answer and explanation with wifi. I have already looked at commits before I posted this question. I saw what was changed so I suspected merge, but because there is no mention that "bananapipro" option in script is (and will be) for M1, M1+ and Pro, I was afraid that development was ended for M1 board and only PRO will be supported in the future. That is why I asked. Maybe change line 178 of configuration.sh to something like #description (M1, M1+, Pro) A20 dual core 1Gb SoC So no one gets confused.

Hi, When I start armbian script, there is no Banana Pi M1 model anymore. Was Banana Pi M1 merged with Banana Pi Pro model? I could not find any note or info about this change anywhere. Thank you!

Loaded sunxi module (modprobe sunxi), lsmod shows it, but OTG is still not powered. EDIT: Just installed 3.4 kernel and after script.bin modification OTG works OK. So it is not HW problem.

My luck is bad here Igor. port still dead. To be sure I have compiled whole own kernel too. First time with "host", second time with "otg" option in sun7i-a20-bananapi.dts (I have deleted source dir before second attempt). Nothing changes. (I have installed both new kernel and dtb .deb files) I do not know where I could make a mistake. Chrrrm. Maybe port is broken physically. I will just wait to next release and will see what is up.

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.

Yes, I see now. Sorry for posting this, I have downloaded zip from http://www.armbian.com/banana-pi/so I have could not see the warning on www.armbian.com Thank you for the answer. (And lot of new work, one can see it everywhere! )

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.

Hi, In kernel 4.1, we have dmesg spammed by: [84320.834217] clocksource hstimer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 238907555784 ns It should disappear in 4.2. If you need to repair it now, you can patch it yourself: http://permalink.gmane.org/gmane.comp.hardware.netbook.arm.sunxi/17500 D.

You are definitely right about extensive/expensive quality ensurance and selection process does not happen, but 2.0GHz@0.1V... man... that does not happen too... If voltage control would work, there would be some value where board would not run. Not even blessed board can work without voltage... And I can set voltage to whatever I want, it is still the same.

Hey kids, it is me, again! So, this time I found out (well, you maybe knew it before and I am dumbing around again) that voltage control does not work on Banana Pi (at least) mainline kernel. Well, if I am supposed to change it in linux-mainline/arch/arm/boot/dts/sun7i-a20.dtsi. I tried to reach 1248000kHz, which is, of course, unstable. So I was adding and adding voltage, until I was too afraid to continue (1650000mV ). But BananaPi was unstable the same way (freez after few minutes of FTP transfer), no more (bad charger) or no less (would still need more voltage). So after few hours of re-compiling source and listening wonderful music I tried this: 1248000(kHz)@800000(mV), which is big overclock and 100000(mV) less than default voltage for lowest available frequency (144000kHz). But again, few minutes of FTP was possible. That should not be possible with 1248000(kHz)@800000(mV) [default max is 960000(kHz)@1400000(mV)]. I do not think that this would be able to boot to X. Maybe I need to enable changing voltage somewhere, maybe it is not possible, I do not know. I only know that I am compiling/installing this the right way, because changed frequency in source file appears in scaling_available_freq later in running kernel. I am sure that changing this voltage value does not have any effect. Maybe I need to change some other value to enable voltage customization?

Well, interesting. Any way or link to "how to enable OTG in mainline"? I have not found anything useful (for OTG) in /arch/arm/boot/dts/. I enabled needed things (later also not needed things to be sure) in .config, but that is not enough. Maybe I will find something helpful in that pdf.

Haha, I am using "CUSTOM_KERNEL_CONFIG" for a while now in my edited script, but it need more testing and I need to add comments before making pull request... Simply, my script does not load default .config when CUSTOM_KERNEL_CONFIG is set to "yes" AND .config exist in kernel directory. It does not have the ability to change path to .config.

http://cateee.net/lkddb/web-lkddb/INPUT_EVBUG.html CONFIG_INPUT_EVBUG (Event debugging) Location: │ │ -> Device Drivers │ │ -> Input device support │ │ -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y]) I do not think we need it.

Well, today I was somehow unlucky with building, even with my method mentioned here before. I even tried to reinstall whole host´s Ubuntu in Czech language, later in English (everything, locales, keyboards, time, etc...), but I was still unsuccessful in building working Jessie OR Wheezy (kernel 4.0.5) image. I have not found why. Languages seemed right, no errors reported in console. But image seemed "read only". Maybe script creates damaged images? But no error was in the console during shrinking. Size in compile.sh was 2500MB... I dont know. I did not do anything special, all was default (except sd-size). Maybe I "solved" one bug, but there is another one... Sometime exported image ended up in kernel panic after u-boot. I spend many hours trying, purging and trying again, but did not find anything. I am working on some changes to your script, but I need to test them before I prepare a pull request and... I am not sure if I will be able to repair this "language bug" by the proper way... I will probably not even try since I think there are 2 bugs and I cannot solve the other one (so I cannot test my work before the pull request) :-/ For now I am using Igor's image of sdcard with my own kernel (created with compile.sh), that works OK.