• Announcements

    • 1. Check power supply, check SD card and check other people experiences

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

Cubieboard 2 does not start after Armbian 5.35 in headless mode
1 1

20 posts in this topic

Recommended Posts

Hi all! Kinda "mayday-mayday"

I recently upgraded Armbian to 5.35 and after reboot it gone. 

After long investigation i figured out, that it boots ONLY when HDMI cable connected to even standby tv.

This is my home server and it works nonstop in headless mode..

I am on kernel 4.13.16-sunxi, rootfs on sata SSD.

I guess something cannot be detected with uboot. How can I fix this ?

Share this post


Link to post
Share on other sites

Unfortunately, board is far from me and I visit this place no so often, as I want :(. Due to emergency went there today...

 

That's what I have now:

 

zno@armbox:~$ dpkg -l | grep u-boot
ii  linux-u-boot-cubieboard2-next      5.35                                 armhf        Uboot loader 2017.09
ii  u-boot-tools                       2014.10+dfsg1-5                      armhf        companion tools for Das U-Boot bootloader
 

 

Is there any option to force e.g. 720p mode for U-boot or downgrade/upgrade to some other version ? 

And by the way, when TV is standby mode - it detected like this:

 

zno@armbox:~$ dmesg | grep -i hdmi
[    0.000000] Kernel command line: console=ttyS0,115200 console=tty1 root=/dev/sda1 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=7

 

Currently board is placed near TV and kinda working. But may be something else to try ? Assuming no log here in reasonable amount of time....

 

May be 5.36 will help ? Just upgraded different hardware to it remotely (OpiPC) and it booted... Same u-boot, but legacy kernel.

Share this post


Link to post
Share on other sites

Well, 5.36 did not helped.

I rolled back to 5.32 (as last known good for me and it was in my apt cache). It required to remove armbian-config package also...

Boot is back to normal, I have frozen kernel/uboot updates just in case (this will motivate me to invest into Odroid as a new home server).

As an assumption.. May be I had to go via whole 5.33->5.34->5.35->5.36 ? 

Whatever, issue is not investigated =(, but server is back to normal and this is not a hardware issue.

Share this post


Link to post
Share on other sites

Hi, same problem here. Cubieboard 2 with Armbian in headless mode as Nextcloud and VPN server with an external harddisk attached (but booting from SD card).
After an upgrade yesterday to 5.36, mine won't boot either.

After finding this thread, I inserted an HDMI cable into a TV in stand by and it boots again. Thanks, znoxx, for finding this out!

 

Here is the the full dmesg with HDMI cable and TV in stand-by:

https://igel.mooo.com/nextcloud/s/7auVF2IfVXECk4X

 

Obviously, I don't have one where it doesn't boot as I don't have means to access it. But happy to help if you tell me how to. I also have restricted access to the board, but should be able to provide additional info during CET evenings.

Share this post


Link to post
Share on other sites
8 hours ago, Igor said:

no problems.

 

Same as on orangepi pc with same uboot and armbian version.... Still boots without any issues.

That's weird. I will try to install from scratch on "unsupported android stick" which actually close to cubie2, and see, what will happen, but not in reasonable amount of time, and without serial console access.

Anyway, thanks for paying attention for this and I'm feeling, that I am not alone :).

 

Oh, Igor, almost forgot it. I succeeded with rolling back since I had packages in apt-cache. What if I'm reinstalling from scratch and fail ? Where and how I can get 5.32 packages for example ?

Thanks in advance for answer. Hope it will be possible.

Share this post


Link to post
Share on other sites

Igor, can it be installed on 5.32 image ? And will it be possible to roll back to previous kernel (let's say one from 5.32)

If yes, I can try by the end of the week... May be someone can do earlier ?

 

Share this post


Link to post
Share on other sites

Hi,
I try armbian with my cubieboard. And it is not working. I try latest desktop version. But latest server version, is working fine.

Desktop console output is here. 

Spoiler


U-Boot SPL 2017.09-armbian (Nov 22 2017 - 14:17:40)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1


U-Boot 2017.09-armbian (Nov 22 2017 - 14:17:40 +0100) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Cubietech Cubieboard2
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

HDMI connected: Setting up a 1920x1080 dvi console (overscan 0x0)
Error: no valid bmp image at 66000000
In:    serial
Out:   vga
Err:   vga
SCSI:  SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   eth0: ethernet@01c50000
230454 bytes read in 202 ms (1.1 MiB/s)
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3708 bytes read in 207 ms (16.6 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
192 bytes read in 158 ms (1000 Bytes/s)
5074120 bytes read in 559 ms (8.7 MiB/s)
5594808 bytes read in 605 ms (8.8 MiB/s)
Found legacy kernel configuration
46320 bytes read in 318 ms (141.6 KiB/s)
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5074056 Bytes = 4.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
EHCI failed to shut down host controller.
   Loading Ramdisk to 49b29000, end 49fffc88 ... OK

Starting kernel ...

<6>Booting Linux on physical CPU 0
<6>Initializing cgroup subsys cpuset
<6>Initializing cgroup subsys cpu
<5>Linux version 3.4.113-sun7i (root@armbian) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #3 SMP PREEMPT Wed Nov 22 13:23:42 CET 2017
CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: sun7i
<6>Memory Reserved:
<6>     SYS  : 0x43000000 - 0x4300ffff  (  64 kB)
<6>     G2D  : 0x50000000 - 0x50ffffff  (  16 MB)
<6>     LCD  : 0x51000000 - 0x52ffffff  (  32 MB)
<6>cma: CMA: reserved 96 MiB at 43800000
Memory policy: ECC disabled, Data cache writealloc
<6>sunxi: Allwinner A20 (AW1651/sun7i) detected.
<7>On node 0 totalpages: 262144
<7>free_area_init_node: node 0, pgdat c0a83300, node_mem_map d3000000
<7>  DMA zone: 512 pages used for memmap
<7>  DMA zone: 0 pages reserved
<7>  DMA zone: 65024 pages, LIFO batch:15
<7>  Normal zone: 1008 pages used for memmap
<7>  Normal zone: 128016 pages, LIFO batch:31
<7>  HighMem zone: 528 pages used for memmap
<7>  HighMem zone: 67056 pages, LIFO batch:15
<6>PERCPU: Embedded 8 pages/cpu @d3808000 s8256 r8192 d16320 u32768
<7>pcpu-alloc: s8256 r8192 d16320 u32768 alloc=8*4096<c>
<7>pcpu-alloc: <c>[0] <c>0 <c>[0] <c>1 <c>
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260096
<5>Kernel command line: root=UUID=a950ec32-5451-4cf9-9101-69fdaea17396 rootwait rootfstype=ext4 console=tty1 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=89eed6b0-01 ubootsource=mmc usb-storage.quirks= cma=96M  cgroup_enable=memory swapaccount=1
<6>PID hash table entries: 4096 (order: 2, 16384 bytes)
<6>Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
<6>Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>allocated 2097152 bytes of page_cgroup
<6>please try 'cgroup_disable=memory' option if you don't want memory cgroups
<6>Memory: 1024MB = 1024MB total
<5>Memory: 872092k/872092k available, 176484k reserved, 270336K highmem
<5>Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
    lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc09dad5c   (10060 kB)
      .init : 0xc09db000 - 0xc0a13040   ( 225 kB)
      .data : 0xc0a14000 - 0xc0a8bf30   ( 480 kB)
       .bss : 0xc0a8bf54 - 0xc0c61130   (1877 kB)
<6>SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
<6>Preemptible hierarchical RCU implementation.
<6>     RCU dyntick-idle grace-period acceleration is enabled.
<6>     Additional per-CPU info printed with stalls.
<6>NR_IRQS:192
<6>Architected local timer running at 24.00MHz.
<6>sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
<2>start_kernel(): bug: interrupts were enabled early
<6>Console: colour dummy device 80x30
<6>console [tty1] enabled
<6>Calibrating delay loop... <c>1816.98 BogoMIPS (lpj=9084928)
<6>pid_max: default: 32768 minimum: 301
<6>Mount-cache hash table entries: 512
<6>Initializing cgroup subsys cpuacct
<6>Initializing cgroup subsys memory
<6>Initializing cgroup subsys devices
<6>Initializing cgroup subsys freezer
<6>Initializing cgroup subsys blkio
<6>Initializing cgroup subsys perf_event
<6>CPU: Testing write buffer coherency: ok
<6>CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
<6>hw perfevents: enabled with ARMv7 Cortex-A7 PMU driver, 5 counters available
<6>Setting up static identity map for 0x40720708 - 0x40720760
CPU1: Booted secondary processor
<6>CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
<6>Brought up 2 CPUs
<6>SMP: Total of 2 processors activated (3640.52 BogoMIPS).
<6>devtmpfs: initialized
<6>dummy:
<6>NET: Registered protocol family 16
<6>DMA: preallocated 256 KiB pool for atomic coherent allocations
<6>hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
<6>hw-breakpoint: maximum watchpoint size is 8 bytes.
<6>[ccu-inf] aw clock manager init
<6>[ccu-inf] aw_ccu_init
<6>[ccu-inf] script config pll3 to 297MHz
<6>[ccu-inf] script config pll4 to 300MHz
<6>[ccu-inf] script config pll6 to 600MHz
<6>[ccu-inf] script config pll7 to 297MHz
<6>[ccu-inf] script config pll8 to 336MHz
<6>Init eGon pin module V2.0
<6>bio: create slab <bio-0> at 0
<6>sunxi_gpio driver init ver 1.3
<6>gpiochip_add: registered GPIOs 1 to 2 on device: A1X_GPIO
<5>SCSI subsystem initialized
<7>libata version 3.00 loaded.
<6>usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
<6>Linux media interface: v0.10
<6>Linux video capture interface: v2.00
<6>Advanced Linux Sound Architecture Driver Version 1.0.25.
<6>cfg80211: Calling CRDA to update world regulatory domain
<6>Switching to clocksource arch_sys_counter
<5>FS-Cache: Loaded
<6>CacheFiles: Loaded
[usb_manager]: CONFIG_USB_SW_SUNXI_USB0_OTG
[sw_hcd0]: usb host driver initialize........
[sw_hcd0]: open_usb_clock
[sw_hcd0]: host_init_state = 1
[sw_hcd0]: platform is usb host
[sw_hcd0]: sw_hcd_host0: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx (X), HB-ISO Tx (X), SoftConn)
[sw_hcd0]: sw_hcd_init_controller: sw_hcd_host0: USB Host mode controller at f1c13000 using PIO, IRQ 70
<6>sw_hcd_host0 sw_hcd_host0: sw_hcd host driver
<6>sw_hcd_host0 sw_hcd_host0: new USB bus registered, assigned bus number 1
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 1 port detected
wrn: hcd is not enable, need not start hcd
[sw_hcd0]: sw_usb_host0_disable start
-------sw_hcd0_soft_disconnect---------
is_on = 0, hcd0_set_vbus_cnt = 0
[sw_hcd_host0]: Set USB Power Off
wrn: hcd is not enable, need not stop hcd
[sw_hcd0]: close_usb_clock
[sw_hcd0]: sw_usb_host0_disable end
[sw_udc]: udc_init: version 20080411
<6>NET: Registered protocol family 2
<6>IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
<6>TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
<6>TCP: Hash tables configured (established 131072 bind 65536)
<6>TCP: reno registered
<6>UDP hash table entries: 512 (order: 2, 16384 bytes)
<6>UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
<6>NET: Registered protocol family 1
<6>RPC: Registered named UNIX socket transport module.
<6>RPC: Registered udp transport module.
<6>RPC: Registered tcp transport module.
<6>RPC: Registered tcp NFSv4.1 backchannel transport module.
<6>Trying to unpack rootfs image as initramfs...
<6>Freeing initrd memory: 4952K
<6>audit: initializing netlink socket (disabled)
<5>type=2000 audit(0.990:1): initialized
highmem bounce pool size: 64 pages
<5>VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
<6>squashfs: version 4.0 (2009/01/31) Phillip Lougher
<5>NFS: Registering the id_resolver key type
<6>NTFS driver 2.1.30 [Flags: R/W].
<6>fuse init (API version 7.18)
<6>JFS: nTxBlock = 7619, nTxLock = 60959
<6>SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
<6>Btrfs loaded
<6>msgmni has been set to 1376
<6>alg: No test for stdrng (krng)
<6>Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
<6>io scheduler noop registered
<6>io scheduler deadline registered
<6>io scheduler cfq registered (default)
<6>sunxi disp driver loaded (/dev/disp api 1.0)
<6>Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
<6>[uart]: used uart info.: 0x01
<6>[uart]: serial probe 0 irq 33 mapbase 0x01c28000
<6>sunxi-uart.0: ttyS0 at MMIO 0x1c28000 (irq = 33) is a U6_16550A
<6>console [ttyS0] enabled
<7>G2D: drv_g2d_init
<6>G2D: g2dmem: g2d_start=50000000, g2d_size=1000000
<6>G2D: head:d0000000,tail:d1000000
<6>G2D: Module initialized.major:250
<6>brd: module loaded
<6>loop: module loaded
[NAND] nand driver version: 0x2 0x9
<4>Dev Sunxi softw311 nand magic does not match for MBR 1: ▒▒▒▒▒▒▒▒
<4>Dev Sunxi softw311 nand magic does not match for MBR 2: ▒▒▒▒▒▒▒▒
<4>Dev Sunxi softw311 nand magic does not match for MBR 3: ▒▒▒▒▒▒▒▒
<4>Dev Sunxi softw311 nand magic does not match for MBR 4: ▒▒▒▒▒▒▒▒
<4>Dev Sunxi softw311 nand header bad for all MBR copies, MBR corrupted or not present.
<4>Dev Sunxi softw411 nand magic does not match for MBR 1: ▒▒▒▒▒▒▒▒
<4>Dev Sunxi softw411 nand magic does not match for MBR 2: ▒▒▒▒▒▒▒▒
<4>Dev Sunxi softw411 nand magic does not match for MBR 3: ▒▒▒▒▒▒▒▒
<4>Dev Sunxi softw411 nand magic does not match for MBR 4: ▒▒▒▒▒▒▒▒
<4>Dev Sunxi softw411 nand header bad for all MBR copies, MBR corrupted or not present.
<6> nand: unknown partition table
[NAND]nand driver, ok.
pwm-sunxi: pwm0 configured - period: 20, duty_percent: 50, duty: 10
<6>sw_ahci sw_ahci.0: controller can't do PMP, turning off CAP_PMP
<6>ahci: SSS flag set, parallel bus scan disabled
<6>sw_ahci sw_ahci.0: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl platform mode
<6>sw_ahci sw_ahci.0: flags: ncq sntf stag pm led clo only pio slum part ccc
<6>scsi0 : sw_ahci_platform
<6>ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 88
<3>[spi-err] Get spi devices number failed
<3>[spi-err] register spi devices board info failed
<4>spi: cannot find any using configuration for                     all 4 spi controllers, return directly!
<6>bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
<6>Fixed MDIO Bus: probed
<6>sunxi_emac Using mii phy on PortA
<6>sunxi_emac Using MAC from SID: 02:90:07:83:5e:aa<4>emac_init fetch emac using configuration failed
<6>gmac driver is disabled
<6>PPP generic driver version 2.4.2
<6>PPP BSD Compression module registered
<6>PPP Deflate Compression module registered
<6>PPP MPPE Compression module registered
<6>NET: Registered protocol family 24
<6>ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
<6>ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[sw-ehci1]: open clock
[sw-ehci1]: Set USB Power ON
<6>sw-ehci sw-ehci.1: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver
<6>sw-ehci sw-ehci.1: new USB bus registered, assigned bus number 2
<6>sw-ehci sw-ehci.1: irq 71, io mem 0x01c14000
<6>sw-ehci sw-ehci.1: USB 2.0 started, EHCI 1.00
<6>hub 2-0:1.0: USB hub found
<6>hub 2-0:1.0: 1 port detected
[sw-ohci1]: open clock
<6>sw-ohci sw-ohci.1: SW USB2.0 'Open' Host Controller (OHCI) Driver
<6>sw-ohci sw-ohci.1: new USB bus registered, assigned bus number 3
<6>sw-ohci sw-ohci.1: irq 96, io mem 0x01c14400
<6>hub 3-0:1.0: USB hub found
<6>hub 3-0:1.0: 1 port detected
[sw-ehci2]: open clock
[sw-ehci2]: Set USB Power ON
<6>sw-ehci sw-ehci.2: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver
<6>sw-ehci sw-ehci.2: new USB bus registered, assigned bus number 4
<6>sw-ehci sw-ehci.2: irq 72, io mem 0x01c1c000
<6>sw-ehci sw-ehci.2: USB 2.0 started, EHCI 1.00
<6>hub 4-0:1.0: USB hub found
<6>hub 4-0:1.0: 1 port detected
[sw-ohci2]: open clock
<6>ata1: SATA link down (SStatus 0 SControl 300)
<6>sw-ohci sw-ohci.2: SW USB2.0 'Open' Host Controller (OHCI) Driver
<6>sw-ohci sw-ohci.2: new USB bus registered, assigned bus number 5
<6>sw-ohci sw-ohci.2: irq 97, io mem 0x01c1c400
<6>hub 5-0:1.0: USB hub found
<6>hub 5-0:1.0: 1 port detected
<6>Initializing USB Mass Storage driver...
<6>usbcore: registered new interface driver usb-storage
<6>USB Mass Storage support registered.
<6>usbcore: registered new interface driver ums-alauda
<6>usbcore: registered new interface driver ums-cypress
<6>usbcore: registered new interface driver ums-datafab
<6>usbcore: registered new interface driver ums_eneub6250
<6>usbcore: registered new interface driver ums-freecom
<6>usbcore: registered new interface driver ums-isd200
<6>usbcore: registered new interface driver ums-jumpshot
<6>usbcore: registered new interface driver ums-karma
<6>usbcore: registered new interface driver ums-onetouch
<6>usbcore: registered new interface driver ums-realtek
<6>usbcore: registered new interface driver ums-sddr09
<6>usbcore: registered new interface driver ums-sddr55
<6>usbcore: registered new interface driver ums-usbat
<6>mousedev: PS/2 mouse device common for all mice
===========================hv_keypad_init=====================
========HV Inital ===================
<3>tkey_fetch_sysconfig_para: tkey_unused.
hv_keypad_init: after fetch_sysconfig_para:  normal_i2c: 0x0. normal_i2c[1]: 0x0
<3>sunxi-rtc sunxi-rtc: Error: Set LOSC to external failed.
<3>sunxi-rtc sunxi-rtc: Warning: RTC time will be wrong!
<6>sunxi-rtc sunxi-rtc: rtc core: registered rtc as rtc0
<6>i2c /dev entries driver
config i2c gpio with gpio_config api
<6>axp_mfd 0-0034: AXP (CHIP ID: 0x41) detected
<6>axp_mfd 0-0034: AXP internal temperature monitoring enabled
<4>i2c i2c-0: Invalid probe address 0x00
<6>I2C: i2c-0: AW16XX I2C adapter
[cedar dev]: install start!!!
[cedar dev]: install end!!!
[tt]----- avs_dev driver load... ----
[tt]-----      register iomem      ----
[tt]--- avs_dev driver load ok!! -----
[ace_drv] start!!!
[ace_drv] init end!!!
[pa_drv] start!!!
[pa_drv] init end!!!
<6>axp20_ldo1: 1300 mV
<6>axp20_ldo2: 1800 <--> 3300 mV at 3000 mV

 

 

Share this post


Link to post
Share on other sites

Igor, I will give the 4.14.y kernel a try tonight.
 

Just to make sure:

- Copy the files to the cubieboard

- dpkg -i for both files

- restart and hope for the best

Correct?

Share this post


Link to post
Share on other sites

I tested with the 4.14.3 kernel and device tree provided by Igor.
The issue still exists with exactly the same behavior: CB2 won't boot without HDMI cable and TV attached at boot time. If a cable/TV is attached, it will again boot just fine.

 

armbianmonitor -u output with HDMI attached:

http://sprunge.us/fTOX

 

Contents of armbianEnv.txt

verbosity=7
console=both
disp_mode=1920x1080p60
rootdev=UUID=16d0ef66-77a0-4af0-8b91-96dbe7c237dd
rootfstype=ext4

 

I am really wild guessing here, but could this have been introduced by the recent HDMI CEC commit to the 4.14 kernel? I'm not fully clear if this actually happened for A20 boards. On http://linux-sunxi.org/Linux_mainlining_effort the status matrix says so, the individual section for the 4.14 doesn't mention it for A20 specifically. But obviously, there is a lot going on around HDMI for those boards, also for 4.15.

 

My personal workaround for the time being:

Boot with HDMI/TV attached. There seems to be no issue if you remove the HDMI cable after the boot sequence.

Share this post


Link to post
Share on other sites

Success!
With u-boot from 5.31, the CB2 boots without any HDMI/TV attached.

I am running the 4.14.3 kernel which you provided earlier.

 

Anything I can provide to solve the (to me) mystery?

 

Thanks, Igor!
And not just for this solution, but for Armbian in general!

Share this post


Link to post
Share on other sites

You can also give me some time and all you need to do will be to update and upgrade. A small bugfix release is planned ASAP and this can be fixed on the way. I'll repack u-boot with 2017.07 since I couldn't find the cause of the problem in current one.

Share this post


Link to post
Share on other sites
6 hours ago, Igor said:

I'll repack u-boot with 2017.07 since I couldn't find the cause of the problem in current one.

Igor, thanks!

No rush at all, my goal is to follow "usual update", not to try something special, since my cubie is acting like a server in, well, production mode.

Please take your time :). Currently it's working and the last thing I want - visiting the location where it placed and connecting HDMI in case of failure :)

Thanks in advance for your efforts.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

1 1

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.