Bug#820167: syslinux-efi: Kernel does not boot on Gigabyte MP30-AR0 system (APM X-Gene 1)
Package: syslinux-efi
Version: 8.4
Severity: grave
Tags: d-i
Justification: renders package unusable
Description of problem:
The Kernel does not boot after I select applicable option in the Debian Installer Grub boot menu.
Version-Release number of selected component (if applicable):
Debian 8.4 arm64
How reproducible:
Every time.
Steps to Reproduce:
1. Download http://cdimage.debian.org/debian-cd/8.4.0/arm64/iso-cd/debian-8.4.0-arm64-netinst.iso
2. Verify checksum
3. Copy to USB drive using Windows Win32DiskImager
4. Insert drive in X-Gene system
5. Boot X-Gene system
6. Navigate to UEFI Shell
7. Enter the following command to start the Fedora installer:
FS1:\EFI\BOOT\BOOTAA64.EFI
8. In the Grub boot menu select the first menu option and hit enter
9. System hangs
The boot issue was not resolved after I restarted the system and added the following kernel parameter: console=ttyS0,115200
Actual results:
The following is displayed on the serial console:
EFI stub: Booting Linux Kernel...
L3c Cache: 8MB
Systems hangs and needs to be rebooted.
Expected results:
First screen of Debian Installer on either VGA or serial console.
Additional info:
Hardware
Gigabyte MP30-AR0 motherboard with APM X-Gene 1 processor flashed with TianoCore UEFI
Kingston KVR16LE11S8/4HB 16 GB ECC DDR3 DRAM
HGST Deskstar NAS 6 TB hard drive
Logitech USB keyboard
The standard U-Boot firmware has been replaced by TianoCore UEFI using the steps described in: https://rwmj.wordpress.com/2016/03/08/gigabyte-mp30-ar0-flashing-uefi/
Both Centos 7.2 and Debian Testing were successfully installed on this system and running stable.
-- System Information:
Debian Release: 8.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Reply to: