Schwemmlandebene

I'm glad to give something back to Armbian.

I'm glad to give something back to Armbian.

Banana Pi M2
PS: I don't use the latest Armbian toolchain. I'm using the .ignore_changes feature.
root@m2-bare:~# uname -a Linux m2-bare 4.5.4-sunxi #2 SMP Sat Jun 11 13:05:21 CEST 2016 armv7l GNU/Linux root@m2-bare:~# cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 17: 0 0 0 0 GIC-0 29 Edge arch_timer 18: 11870 265608 31223 36550 GIC-0 30 Edge arch_timer 21: 0 0 0 0 GIC-0 50 Level sun4i_timer0 22: 0 0 0 0 GIC-0 83 Level sun5i_timer0 27: 0 0 0 0 GIC-0 82 Level 1c02000.dma-controller 28: 1653 0 0 0 GIC-0 92 Level sunxi-mmc 29: 8549 0 0 0 GIC-0 94 Level sunxi-mmc 30: 27 0 0 0 GIC-0 104 Level ehci_hcd:usb1 31: 0 0 0 0 GIC-0 105 Level ohci_hcd:usb2 40: 2251 0 0 0 GIC-0 60 Level sun4i-ts 41: 425 0 0 0 GIC-0 32 Level serial 42: 43646 0 0 0 GIC-0 114 Level eth0 48: 0 0 0 0 GIC-0 72 Level 1f00000.rtc 57: 0 0 0 0 sunxi_pio_edge 4 Edge 1c0f000.mmc cd 181: 43 0 0 0 sunxi_pio_level 0 Level brcmf_oob_intr IPI0: 0 0 0 0 CPU wakeup interrupts IPI1: 0 0 0 0 Timer broadcast interrupts IPI2: 3407 15690 13225 7318 Rescheduling interrupts IPI3: 6 8 3 6 Function call interrupts IPI4: 0 0 0 0 CPU stop interrupts IPI5: 0 0 0 0 IRQ work interrupts IPI6: 0 0 0 0 completion interrupts Err: 0 root@m2-bare:~#

I can confirm some trouble with the combination of lamabo-r1, 4.6.1 and USB.
With standard linux-sunxi-next.config my USB keyboards work.
But after disabling some I2C drivers in the kernel configuration the board doesn't get any input from the keyboards.
On one keyboard the NumLock LED lits after hitting the key, on the other it does not.
 
$ sudo lsusb
unable to initialize libusb: -99

Hallo,   this Mini-Howto describes how to change the behavior of the onboard LEDs during booting. There are many ways to do that. Two ways are shown here, a SysV style using /etc/rc.local and a systemd style using a configuration file in /etc/tmpfiles.d/. The systemd file is earlier interpreted than rc.local.   It is tested on Banana Pi M1*/M2/R1 with Debian jessie next (5.0x, 4.4.x). * partly   Which LEDs could be accessed? root@bananapim2:~# ls -1 /sys/class/leds/ bpi-m2:blue:usr bpi-m2:green:usr bpi-m2:red:usr * The Banana Pi M1 lists the blue LED but it couldn't be set via /etc/tmpfiles.d/ or /etc/rc.local.
  Which behaviors are possible? root@bananapim2:~# cat /sys/class/leds/bpi-m2\:green\:usr/trigger none rc-feedback kbd-scrollock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usb-gadget usb-host [mmc0] heartbeat cpu0 cpu1 cpu2 cpu3 default-on mmc1 rfkill0   Edit /etc/rc.local to set the behavior of the onboard LEDs root@bananapim2:~# cat /etc/rc.local #!/bin/sh -e echo "default-on" > /sys/class/leds/bpi-m2\:red\:usr/trigger echo "mmc0" > /sys/class/leds/bpi-m2\:green\:usr/trigger echo "heartbeat" > /sys/class/leds/bpi-m2\:blue\:usr/trigger exit 0 or  edit /etc/tmpfiles.d/leds.conf.
root@bananapim2:~# cat /etc/tmpfiles.d/leds.conf w /sys/class/leds/bpi-m2:red:usr/trigger - - - - default-on w /sys/class/leds/bpi-m2:green:usr/trigger - - - - mmc0 w /sys/class/leds/bpi-m2:blue:usr/trigger - - - - heartbeat /etc/rc.local can be executed on the console, /etc/tmpfiles.d/leds.conf needs a reboot.
  A third way may be to create systemd rules. But it doesn't work for me. root@bananapim2:~# udevadm info -a -p /sys/class/leds/bpi-m2\:red\:usr [snip]   looking at device '/devices/platform/leds/leds/bpi-m2:red:usr':     KERNEL=="bpi-m2:red:usr"     SUBSYSTEM=="leds"     DRIVER==""     ATTR{brightness}=="255"     ATTR{max_brightness}=="255"     ATTR{trigger}=="none rc-feedback kbd-scrollock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usb-gadget usb-host mmc0 heartbeat cpu0 cpu1 cpu2 cpu3 [default-on] mmc1 rfkill0 " [snip]   root@bananapim2:~#nano /etc/udev/rules.d/10-leds.rules   For setting the LEDs via dts files, have a look at this discussion: http://forum.armbian.com/index.php/topic/691-banana-pro-testers-wanted-sata-drive-not-working-on-some-boards/page-4#entry5641   Regards, Steve

Hallo,   this Mini-Howto describes how to change the behavior of the onboard LEDs during booting. There are many ways to do that. Two ways are shown here, a SysV style using /etc/rc.local and a systemd style using a configuration file in /etc/tmpfiles.d/. The systemd file is earlier interpreted than rc.local.   It is tested on Banana Pi M1*/M2/R1 with Debian jessie next (5.0x, 4.4.x). * partly   Which LEDs could be accessed? root@bananapim2:~# ls -1 /sys/class/leds/ bpi-m2:blue:usr bpi-m2:green:usr bpi-m2:red:usr * The Banana Pi M1 lists the blue LED but it couldn't be set via /etc/tmpfiles.d/ or /etc/rc.local.
  Which behaviors are possible? root@bananapim2:~# cat /sys/class/leds/bpi-m2\:green\:usr/trigger none rc-feedback kbd-scrollock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usb-gadget usb-host [mmc0] heartbeat cpu0 cpu1 cpu2 cpu3 default-on mmc1 rfkill0   Edit /etc/rc.local to set the behavior of the onboard LEDs root@bananapim2:~# cat /etc/rc.local #!/bin/sh -e echo "default-on" > /sys/class/leds/bpi-m2\:red\:usr/trigger echo "mmc0" > /sys/class/leds/bpi-m2\:green\:usr/trigger echo "heartbeat" > /sys/class/leds/bpi-m2\:blue\:usr/trigger exit 0 or  edit /etc/tmpfiles.d/leds.conf.
root@bananapim2:~# cat /etc/tmpfiles.d/leds.conf w /sys/class/leds/bpi-m2:red:usr/trigger - - - - default-on w /sys/class/leds/bpi-m2:green:usr/trigger - - - - mmc0 w /sys/class/leds/bpi-m2:blue:usr/trigger - - - - heartbeat /etc/rc.local can be executed on the console, /etc/tmpfiles.d/leds.conf needs a reboot.
  A third way may be to create systemd rules. But it doesn't work for me. root@bananapim2:~# udevadm info -a -p /sys/class/leds/bpi-m2\:red\:usr [snip]   looking at device '/devices/platform/leds/leds/bpi-m2:red:usr':     KERNEL=="bpi-m2:red:usr"     SUBSYSTEM=="leds"     DRIVER==""     ATTR{brightness}=="255"     ATTR{max_brightness}=="255"     ATTR{trigger}=="none rc-feedback kbd-scrollock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usb-gadget usb-host mmc0 heartbeat cpu0 cpu1 cpu2 cpu3 [default-on] mmc1 rfkill0 " [snip]   root@bananapim2:~#nano /etc/udev/rules.d/10-leds.rules   For setting the LEDs via dts files, have a look at this discussion: http://forum.armbian.com/index.php/topic/691-banana-pro-testers-wanted-sata-drive-not-working-on-some-boards/page-4#entry5641   Regards, Steve

[update] zador.blood.stained, thanks for your help.
Until Sunday afternoon I could build different images with sudo. Suddenly this was broken.
Your advice to run compile.sh as root worked.
Than I added a new user with sudo rights and started from scratch, git clone https://github.com/igorpecovnik/libetc.
and run "sudo compile.sh" successfully.
Now I only use the new user and everything works (kernel patches, customize-image.sh).
Greetings,
Steve