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

Hi all

First of all Ciao to all the members of this forum!!

I'm just moving from RPi to CB3, all new for me.

I've booted up with latest version of Armbian (Armbian_5.10_Cubietruck_Debian_jessie_3.4.112) with a connected SSD.

I dont' see it in fdisk -l and if I go with dmesg | grep -i sata I get

[    1.265800] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 88

[    1.610672] ata1: SATA link down (SStatus 0 SControl 300)

The cable that were inside the cubieboard package has two different power cables, one red/black and another yellow/black, and if I'm not wrong the first should go into 5v Sata connector and the yellow one in the 12v Sata connector.

Should I connect both or which one?

Should I do something else to let armbian see the SSD?

By the way I've already formatted the SSD with two ext4 primary partitions.

Thanks

Vittorio

Hello,

Me, again !!

I used pwm on Lime2 with 3.4.109 and works fine (generating sounds with 2-3 Khz)

But, with 3.4.112, I have sound up to 363 Hz. Beginning with 364 Hz ... no sound !!

I verified with an oscilloscope and I don't have rectangular waves over 364 Hz .

Did anybody experienced such a strange thing ? What can be this 364 limit ?

Thanks,

Regards,

have anyone tested the tvin yet?

there are some ported drivers from android kernel on github (sun7i_tvd).

with regards

Hi Forum,

"modprobe g_mass_storage file=/dev/sda1 removable=yes stall=0" doesn't work on 3.4.112 but works on 4.6.2.

Hello list,

a big thank you to all the developers of Armbian.

I am a newbie to arm boards, have limited experience with various linuxes and definitely not enough know-how to progam anything or to compile kernels or build images, and things like u-boots are warships for me.

Without your great software images my cubietruck would probably have been an investment into electronic scrap!

A short user-feedback:

Why does a normal consumer want to use a cubieboard?

To use my favorite .mp3-player attached via SPDIF to his stereo equipment, play music from a harddisk and control it via VNC-Client from a tablet (because I don't want to use an 80 W TV to control a 6 W computer).

My first experience is great: Thanks to your software (jessie desktop, legacy) I succeded immediately to get the cubietruck running and to get sound from the SPDIF-jack to my stereo equipment.

To my surprise the volume control and the mixer of the desktop version do nothing (which is very welcome because the pure PCM audio it delivers is the best input for the stereo equipment).

My next steps:

Try to get my favorite player running (banshee, which I prefer because of it's unique community extension mirage (a really inteligent auto-DJ)). As it is not available in jessie for armhf the nextsteps will either try installing it from sid or to use the ubuntu image, upgrade it to xfce (for ubuntu armhf the player is available) and install the player under ubuntu.

I hope one of the ways will work sooner or later (the first trial of both did not because my maloperation of apt-get).

Really great what you are doing!

Images with up-to-date software for people ho are not software engineers seem to be rare outside the raspi world. Hope it's not too trivial for the software cracks what people are doing with their work.

Regards,

Christian

Hi,

today I want to tell you, that I am very much upset about the result of the latest ARMBIAN Update!

After updating I figured out, that the latest update erased my bash.bashrc.custom, which took me a long time to set it right!

Unfortunate I did not have a backup!

I am very much upset, that an armbian update erases configuration files WITHOUT any further notices!!!

Regards, Ireng

I'm thinking of getting a 128GB microSDXC card (Samsung EVO) for my Cubietruck. Is this likely to work or is 64GB a hard limit?

Of course, I intend to put a sane filesystem on it, like ext4.

Dear Forum,

First of all thank you for being a member here.

Second is that I would need some help on selecting an image for my present CT board.

I need the followings:

1. hostapd with dnsmasq

2. g_mass_storage

3. sata

4.spidev or equivalent

Preferably:

3. I would need free up SD card slot, so nand or SATA boot would be preferred.

Which image is the best for me even if I need to recompile it?

Thank you in advance.

Hello !

I recently reimaged my BPi M1 with the vanilla headless Debian Jessie from Armbian. But I have two problems:

Main problem (the worst): I have a RAID SATA to USB enclosure (this one: BS-EHD-35/DUALB). After some times and randomly, the drives stops spinning and the enclosure stops itself. I've disabled any power management on hard drive, setup a cron job to write a file every 5 min, disabled autosuspend in usb core...

I didn't have this problem with the legacy kernel. I cannot downgrade to it, because I'm using BTRFS with some non-compatible extensions. Note: this is a server with apache, Deluge, Plex and Sonarr.

Side problems (I can live with if the first is OK): Also, if the drive isn't connected, the BPi won't boot, and after the enclosure stops, the BPi hang and need a force reset to remount the drive and restart services. Tried a udev rule to automate it, but no luck.

Don't understand why the enclosure stops itself, it's not really documented, and tried everything I could think.

Thank you,

Arno

i run a cubietruck on armbian with 4.6.2 kernel. it starts with the software on mmcblk0p1 (with kernel 4.6.2 and the /lib dir on the sd) but uses as root a partition of the ssd. 

when i upgrade now, i see that the upgrade process produces a new initrd.img-4.6.3 and removes the old 4.6.2.

(diagnosis: the system runs, but the keyboard/mouse connected to the usb is not functional - desktop over net works!)

i assume that there is something wrong with the boot.cmd -  but i do not see exactly how to fix it. the upgrade process uses the ssd .../lib directory and removes 4.6.2 there. if i would mount the /boot directory with the running system (in fstab) - would this help? then the upgrade process would write the initram on the sd.

thank you for the very reliable system!

andrew

my boot.cmd says:

if ext4load mmc 0 0x00000000 /boot/.verbose
then
setenv verbosity 7
else
setenv verbosity 1
fi
setenv bootargs "console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 cgroup_enable=memory swapaccount=1 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=${verbosity}"
#--------------------------------------------------------------------------------------------------------------------------------
# Boot loader script to boot with different boot methods for old and new kernel
#--------------------------------------------------------------------------------------------------------------------------------
if ext4load mmc 0 0x00000000 /boot/.next || fatload mmc 0 0x00000000 .next || ext4load mmc 0 0x00000000 .next
then
# sunxi mainline kernel
#--------------------------------------------------------------------------------------------------------------------------------
ext4load mmc 0 0x49000000 /boot/dtb/${fdtfile} || fatload mmc 0 0x49000000 /dtb/${fdtfile} || ext4load mmc 0 0x49000000 /dtb/${fdtfile}
ext4load mmc 0 0x42000000 /boot/uInitrd || fatload mmc 0 0x42000000 uInitrd || ext4load mmc 0 0x42000000 uInitrd
ext4load mmc 0 0x46000000 /boot/zImage || fatload mmc 0 0x46000000 zImage || ext4load mmc 0 0x46000000 zImage
bootz 0x46000000 0x42000000 0x49000000
#bootz 0x46000000 - 0x49000000
#--------------------------------------------------------------------------------------------------------------------------------
else
# sunxi android kernel
#--------------------------------------------------------------------------------------------------------------------------------
ext4load mmc 0 0x43000000 /boot/script.bin || fatload mmc 0 0x43000000 script.bin || ext4load mmc 0 0x43000000 script.bin
ext4load mmc 0 0x42000000 /boot/uInitrd || fatload mmc 0 0x42000000 uInitrd || ext4load mmc 0 0x42000000 uInitrd
ext4load mmc 0 0x48000000 /boot/zImage || fatload mmc 0 0x48000000 zImage || ext4load mmc 0 0x48000000 zImage
bootz 0x48000000 0x42000000
#bootz 0x48000000
#--------------------------------------------------------------------------------------------------------------------------------
fi
# Recompile with:
# mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
 

Hey everyone. I have an MK802 II stick, which has the A10 s.o.c, so i use the Olinuxino Lime a10 image on it. 

Everything works pretty much fine, except one little thing. 

This machine has worked fine with non-standard resolutions, like 1440x900, or 1280x1024. 

Now, when i turn it on, the U-boot screen appears correctly, it even shows that it set the resolution to 1440x900, and after that, the monitor says "signal out of range".

Of course, it works well with a 1080p monitor, but i wanted to use this one too.

Thanks!

Hello,

with the update to the new kernel (4.6.3-sunxi) I get some problems on my banana pro.

First, while the system starts I get sometimes a kernel panic. In the most cases the kernel will boot on the second or third try.

But the second one will be contantly and can't be avoided by a system reboot.

The network interfaces don't be worked. The will be initialized during the system start process, get there IPv4 addresses

from the router per DHCP and ifconfig shown them with the state "up". Everything looks ok.

But if I try to connect another system, the connection will be failed.

Any ping, as exsample to the router (default gateway), fails.

The ping to the own address will be worked without any issues (192.168.178.10 (eth0) and 192.168.178.52 (WLAN)).

Maybe the network layer optimized it internally and used the loopback interface.

Pls, have anybody an idea and can help me to fixed the issue.

Or give me some hint how I can make a fallback to the previous kernal 4.5.5-sunxi which works fine.

(sorry, linux is new for me, I'm a developer which like to move from QNX and the windows system layer to the IoT world)

Thanks in advance

dkl

Hi!
I love this Linux distribution, I have tried some months ago and had worked very well.

Now, I want install armbian in a pdduino3b, I go to "downloads" select pcduino3, and I have two options:

Xenial_server_vanilla and Xenial_server_legacy.

I want hardware acceleration and most options of drivers and compatibility possible, so, I go for legacy option.

But I realize that the two images have not a desktop environment, this is true?

If yes, where can I download the full newer armbian version with legacy kernel and desktop ready?

I try install xcfe over legacy image, but I have found for errors like "screen not found" and others...

Regards.

I'm using vanilla Ubuntu Xenial 16.04 from http://www.armbian.com/lamobo-r1/

When I follow the forum posts for copying everything to the SATA drive and updating /etc/fstab and /boot/boot.cmd the system boots as expected to the SATA drive. 

The problem I have is I get prompted to upgrade it on boot using apt-get upgrade. This also upgrades the kernel version from 4.6.2 to 4.6.3.

Because I have moved the system from the SD card to the SATA drive the new kernel doesn't load, only the old kernel with missing modules which causes problems.

When the kernel updates it updates the SATA drive /boot directory but the device uses the sd card /boot directory so things get screwed up.

I followed and read all the forum posts I could find on booting from the SATA drive and couldn't any reference to this so I'm not sure I missed something.

Anyway my solution was to remove the /boot directory from the SATA drive and symlink it from the /boot directory on the SD card and it all appears to work and the new kernel now shows up when I run uname -r . The correct modules now load with the updated kernel too.

Get the drive assignments

fdisk -l

Change below to match drives

SDCARD='mmcblk0p1'
SATA='sda1'

Create the temp directories

mkdir /tmp/1 /tmp/target
mount /dev/$SDCARD /tmp/1
mount /dev/$SATA /tmp/target

Modify the fstab and bootcmd files to match

sed -i -e "s/$SDCARD/$SATA/g" /tmp/1/etc/fstab
sed -i -e "s/$SDCARD/$SATA/g" /tmp/1/boot/boot.cmd
mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

Set the sdcard to auto mount in /tmp/boot

echo "/dev/$SDCARD /tmp/boot/ ext4 defaults 0 1" >> /tmp/1/etc/fstab

Copy all the files across to the sata drive

(cd /tmp/1; tar --backup -c *) |tar -C /tmp/target -xv

Remove the boot directory from the sata drive and symlink it to the sdcard boot directory

rm -Rf /tmp/target/boot
ln -s /tmp/boot/boot/ /tmp/target/boot
sync

Then reboot

reboot

Hi!

I just installed a fresh Armbian_5.14_Lamobo-r1_Debian_jessie_3.4.112 image to my R1.

While booting, the system first shows about a page of boot-messages on the Display and then changes to a Out-of-Range Display.

Changing console by <Ctrl><Alt><F1>, ...F2,... Fn doesn't help. Accessing the system with PUTTY/ssh works fine. apt-get update/upgrade/reboot won't help.

The display does 1280x1024 resolution maximum.

Just before I used banian without any problems.

What should I do?

Hi!

I need some help in order to install Node-RED over Armbian Wheezy on Cubieboard1

can anyone give me help?

I've installed Armbian_5.14_Cubieboard_Debian_jessie_3.4.112_desktop.7z and It initially worked.  I tested video files playback (I think it was mpv player) and it worked smoothly, no video lag. After 4 or 5 boot-ups, I'm no longer able to start armbian. I just see u-boot starting and then (when the kernel is going to be loaded  (message: "Starting kernel ...")) I see mess on screen and cubieboard is powered off (red power light goes down, also networking leds). I use HDMI output (unfortunately I do not have serial cable to try debug it maybe further).

What I tried so far, without success:
-changing SD card for another one (8GB cat4 for 8GB cat10)
-replacing power supply (original 5V, 2A replaced for 5.3V, 2A)
-boot without any connected device (no network cable, no usb keyboard or any other usb device)

So I reinstaled system and also tried following images (without success, same shutdown problem):
-Armbian_4.5_Cubieboard_Ubuntu_trusty_3.4.109_desktop.zip
-Armbian_5.04_Cubieboard_Ubuntu_trusty_3.4.110_desktop.zip
-Armbian_5.14_Cubieboard_Debian_jessie_3.4.112.7z

Vanilla kernels worked (I tried latest ones, no shutdowns, but I would like to have accelerated video, which is not possible under vanilla kernels AFAIK):
-Armbian_5.14_Cubieboard_Debian_jessie_3.4.112.7z
-Armbian_5.14_Cubieboard_Debian_jessie_4.6.2_desktop.7z

I also tried Lakka (OpenELEC based) Retroarch distribution and with its default kernel 3.4.91 it works (link: http://mirror.lakka.tv/nightly/a10.arm/Lakka-a10.arm-devel-20160602232347-r21463-g9531662.img.gz)
Nevertheless ffmpeg Retroarch core was unable to play video files smoothly. Therefore I would like to use Armbian (with hw accelerated graphics) and compile Retroarch on it. But I have this strange shutdown problem...
Do you have any ideas what could be wrong?

P.S. On #linux-sunxi user TheLinuxBug tried to help me and booted on his Cubieboard latest Armbian Jessie desktop and it was running ok. Do not know , but maybe it looks like the bug emerges after using Armbian for a while?..... or my cubie has some weird hardware issue (but why then some distros are OK on it).

Hi all,

Creating a DietPi image for BPi Pro based on ARMbian. I finally got a chance to test do_expand_rootfs() from /etc/init.d/firstrun. Now works with multiple partitions, thanks for doing that

Having an issue with the onboard WiFi on the BPi Pro (Lemaker). It appears to be enable, active and ready for use, however, I can not get it to scan/connect to a SSID, or even work in AP mode.

Built the image using your excellent build tools:

[ o.k. ] Building [ Armbian 5.17 Bananapipro Debian jessie default ]

root@DietPi:~# iwlist wlan0 scan
wlan0     No scan results

Fails to set country code. Always returns 00.

root@DietPi:~# iw reg set GB
root@DietPi:~# iw reg get
country 00: DFS-UNSET
        (2402 - 2472 @ 40), (6, 20), (N/A)
        (2457 - 2482 @ 40), (6, 20), (N/A), NO-IR
        (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, NO-IR
        (5170 - 5250 @ 40), (6, 20), (N/A), NO-IR
        (5735 - 5835 @ 40), (6, 20), (N/A), NO-IR

root@DietPi:~# uname -a
Linux DietPi 3.4.112-sun7i #1 SMP PREEMPT Mon Jul 11 11:51:44 BST 2016 armv7l GNU/Linux

root@DietPi:~# lsmod
Module                  Size  Used by
ap6211                624694  0
brcmfmac               96753  0
brcmutil                4804  1 brcmfmac
spidev                  6366  0
a20_tp                  3333  0
8021q                  18601  0
garp                    6068  1 8021q
stp                     2028  1 garp
llc                     5357  2 stp,garp
sunxi_ir                4013  0

root@DietPi:~# modprobe cfg80211
root@DietPi:~# lsmod
Module                  Size  Used by
spidev                  6366  0
ap6211                624694  0
a20_tp                  3333  0
8021q                  18601  0
garp                    6068  1 8021q
stp                     2028  1 garp
llc                     5357  2 stp,garp
sunxi_ir                4013  0

root@DietPi:~# dmesg | grep ap6211
[  451.514454] [ap6211] --->The Drive has been modified for BananaPro by LeMaker team<---
[  451.517353] [ap6211] select wifi ap6211
[  451.520712] [ap6211] Initializing ap6211.
[  451.525891] [ap6211] Succeed to set the gpio ap6211_wl_vdd_en to 0
[  451.531355] [ap6211] Succeed to set the gpio ap6211_wl_regon to 1
[  451.734606] [ap6211] WLAN placed in POWER ON
[  451.926840] [ap6211] Linux Kernel SDIO/MMC Driver
[  451.943795] [ap6211] Broadcom Dongle Host Driver: register interface [wlan0] MAC: 00:90:4c:11:22:33
[  451.950442] [ap6211] Succeed to set the gpio ap6211_wl_regon to 0
[  452.030664] ap6210: exports duplicate symbol bcmsdh_probe (owned by ap6211)
[  452.040690] ap6210: exports duplicate symbol bcmsdh_probe (owned by ap6211)
[  452.181233] [ap6211] WLAN placed in RESET
[  504.259810] [ap6211] Dongle Host Driver, version 1.28.23.3 (r).
[  504.266857] [ap6211] Compiled in drivers/net/wireless/ap6211 on Jul 11 2016 at 11:49:23.
[  504.271955] [ap6211] Succeed to set the gpio ap6211_wl_regon to 1
[  504.475418] [ap6211] WLAN going back to live
[  504.704716] [ap6211] dhd_bus_devreset: WLAN ON
[  504.710694] [ap6211] Final fw_path=/lib/firmware/ap6210/fw_bcm40181a2.bin
[  504.716351] [ap6211] Final nv_path=/lib/firmware/ap6210/nvram_ap6210.txt
[  504.722860] [ap6211] download firmware /lib/firmware/ap6210/fw_bcm40181a2.bin
[  504.995352] [ap6211] Dongle ready, protocol version 4
[  505.000034] [ap6211] Dongle ready, protocol version 4
[  505.010310] [ap6211] Firmware up: op_mode=0x0001, Broadcom Dongle Host Driver mac=e0:76:d0:03:54:f4
[  505.027629] [ap6211] Firmware version = wl0: Apr 22 2013 14:50:00 version 5.90.195.89.6 FWID 01-b30a427d
[  505.030627] [ap6211] Chip: a962 Rev 1 Pkg 9
[  512.519653] [ap6211]  Escan set error (-16)
[  512.521861] [ap6211] error (-16)
[  512.525283] [ap6211] Scan err = (-16), busy?-16
[  512.527963] [ap6211] scan error (-16)
[  581.110543] [ap6211] scan is not ready

root@DietPi:~# ifconfig -a
bond0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0      Link encap:Ethernet  HWaddr 02:8e:02:c2:64:56
          inet addr:192.168.0.133  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::8e:2ff:fec2:6456/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:821 errors:0 dropped:0 overruns:0 frame:0
          TX packets:586 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:80449 (78.5 KiB)  TX bytes:85245 (83.2 KiB)
          Interrupt:117

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:136 errors:0 dropped:0 overruns:0 frame:0
          TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11472 (11.2 KiB)  TX bytes:11472 (11.2 KiB)

tunl0     Link encap:IPIP Tunnel  HWaddr
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr e0:76:d0:03:54:f4
          inet6 addr: fe80::e276:d0ff:fe03:54f4/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:3260 (3.1 KiB) 

# Local
auto lo
iface lo inet loopback

# Ethernet
allow-hotplug eth0
iface eth0 inet dhcp
metric 0
address 192.168.0.100
netmask 255.255.255.0
gateway 192.168.0.1
#dns-nameservers 8.8.8.8 8.8.4.4

# Wifi
allow-hotplug wlan0
iface wlan0 inet dhcp
metric 1
address 192.168.0.100
netmask 255.255.255.0
gateway 192.168.0.1
wireless-essid FuzonWifi
wireless-key xxxxxxxxxxxxxxxxxxxxxxxx
wireless-mode Managed
wireless-power off
wpa-ssid FuzonWifi
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxx
#dns-nameservers 8.8.8.8 8.8.4.4

Hello.
Some facts:
1. Boot with image based on legacy kernel cause shutdown after some (less than 10) seconds after power on.
2. Boot with image based on vanilla kernel always ok.
3. If i try to boot without SD card, than power off Cubie with button, then insert SD and switch on with button - it will boot OK with lagacy kernel!

Which logs can help to find the problem? I ought to use legacy kernel - i need internal soundcard and both USB.
And I see that it is not my own problem - http://forum.armbian.com/index.php/topic/1593-armbian-cubieboard1a10-desktop-with-legacy-kernel-wont-boot-just-shuts-off-cubieboard/- i think we can help to find the bug.