[Arm-dev] Kernel problems on APM X-Gene

Thu Sep 21 10:17:00 UTC 2017
Jeremiah Rothschild <jeremiah at franz.com>

On Thu, Sep 21, 2017 at 05:09:05PM +0700, Phong Vo wrote:
> Jeremiah,
> 
> You will need to use UEFI firmware, either Gigabyte AMI BIOS or APM UEFI
> Tianocore,
> but the official version would be AMI BIOS which you should contact AMI
> for such.

I apologize because I forgot that I daisy chained U-Boot to TianoCore UEFI
already.

Here is my version:

TianoCore 1.20.03-uhp UEFI 2.4.0 Feb 22 2016 11:17:26

> -Phong
> 
> +-----Original Message-----
> +From: Arm-dev [mailto:arm-dev-bounces at centos.org] On Behalf Of Jeremiah
> +Rothschild
> +Sent: Thursday, September 21, 2017 4:32 PM
> +To: Conversations around CentOS on ARM hardware
> +Subject: Re: [Arm-dev] Kernel problems on APM X-Gene
> +
> +On Thu, Sep 21, 2017 at 04:19:55PM +0700, Phong Vo wrote:
> +> Jeremiah,
> +
> +Hi Phong, thank you for the reply.
> +
> +> Is this on Mustang board? Which version of bootloader are you using?
> +
> +Pardon me for not being more specific. This is the Gigabyte MP30-AR0
> +board.
> +
> +Using bootloader version:
> +U-Boot 2013.04-mp30ar0_sw_1.18.04 (Sep 02 2015 - 16:38:06) REV: F06b (
> +uart0 )
> +
> +> -Phong
> +>
> +> +-----Original Message-----
> +> +From: Arm-dev [mailto:arm-dev-bounces at centos.org] On Behalf Of
> +> +Jeremiah Rothschild
> +> +Sent: Thursday, September 21, 2017 1:45 PM
> +> +To: arm-dev at centos.org
> +> +Subject: [Arm-dev] Kernel problems on APM X-Gene
> +> +
> +> +Hey everyone!
> +> +
> +> +I cannot get any kernel past 4.5.0-23.el7.aarch64 to work on APM
> +> +X-Gene hardware. This includes the new (CentOS 7.4) 4.11.0-22 kernel.
> +> +
> +> +The last thing ever displayed during boot is this:
> +> +
> +> +EFI stub: Booting Linux Kernel...
> +> +EFI stub: Using DTB from configuration table EFI stub: Exiting boot
> +> +services and installing virtual address map...
> +> +L3c Cache: 8MB
> +> +
> +> +which is usual. However, nothing is logged to /var/log/messages
> +> +(presumably it isn't making it far enough in the boot process) and
> +> +I'm not sure how to further troubleshoot the issue.
> +> +
> +> +Has anyone else been successful? Are there new patches I am unaware
> +of?
> +> +Can someone please help me debug deeper?
> +> +
> +> +Thanks in advance!
> +> +
> +> +j
> +> +_______________________________________________
> +> +Arm-dev mailing list
> +> +Arm-dev at centos.org
> +> +https://lists.centos.org/mailman/listinfo/arm-dev
> +> _______________________________________________
> +> Arm-dev mailing list
> +> Arm-dev at centos.org
> +> https://lists.centos.org/mailman/listinfo/arm-dev
> +_______________________________________________
> +Arm-dev mailing list
> +Arm-dev at centos.org
> +https://lists.centos.org/mailman/listinfo/arm-dev
> _______________________________________________
> Arm-dev mailing list
> Arm-dev at centos.org
> https://lists.centos.org/mailman/listinfo/arm-dev