[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-bugs
Subject:    Re: Cubieboard2 installation image boot failure
From:       Jonathan Gray <jsg () jsg ! id ! au>
Date:       2019-03-14 1:29:01
Message-ID: 20190314012901.GB589 () largo ! jsg ! id ! au
[Download RAW message or body]

On Wed, Mar 13, 2019 at 06:50:05PM +0900, UnHa Kim wrote:
> >Synopsis: cubieboard2 installation image boot failure.
> >Category: Installation
> >Environment:
>         System      : OpenBSD 6.4
>         Details     : OpenBSD 6.4 Cubieboard2 installation image.
>         Architecture: OpenBSD.armv7
> 
> (https://ftp.openbsd.org/pub/OpenBSD/6.4/armv7/miniroot-cubie-64.fs)
> 
> 
> >What works
> HDMI screen is visible.
> u-boot start EFI.
> u-boot load kernel.
> 
> >What does not works
> After kernel loading kernel, machine freezes with EHCI controller error
> message.
> 
> >Comment
> Cubieboard2 (20120909 NAND) boot fails with 'miniroot-cubie-64.fs'
> installation image.
> 
> Debian linux have been successfully installed on the specific hardware.
> So, it is not likely a hardware issue.
> 
> There are several revision in Cubieboard2.
> (http://dl.cubieboard.org/model/CubieBoard2/How To Distinguish Your
> CubieBoard2 Version.pdf)
> And, the only revision at hand is '20120909 NAND', the oldest.
> 
> > Messages on HDMI screen.
> (Transferred here with hand typing. So, expect some typos.)
> 
> < ... u-boot show no error message before kernel loading ... >
> 
> ## Starting EFI application at 42000000 ...
> >> OpenBSD/armv7 BOOTARM 1.1
> boot>
> cannot open sd0a:/etc/random.seed: No such file or directory
> booting sd0a:/bsd: 2777624+455424+8052348+448127
> [188263+107+206656+181827]=oxbbf494
> EHCI failed to shut down host controller.
> EHCI failed to shut down host controller.
> 
> < No response after EHCI related error messages. >
> 

The dtb for that system has a /chosen/stdout-path of serial.
If you want kernel output to go to a framebuffer you should change the
device tree value, otherwise use serial.

U-Boot will in some instances send output to both serial and framebuffer
at the same time.  The kernel does not have the same behaviour.

[prev in list] [next in list] [prev in thread] [next in thread]