On 12/09/2016 19:41, Phil Endecott wrote:
The Ubuntu mini.iso installer from here:
http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-arm64/current/images/netboot/
also works, with a 4.4.0 kernel:
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 4.4.0-9136-generic
(buildd@bos01-arm64-004) (gcc version 5.4.1 20160803 (Ubuntu/Linaro
5.4.1-1ubuntu2) ) #55-Ubuntu SMP Fri Aug 26 05:58:05 UTC 2016 (Ubuntu
4.4.0-9136.55-generic 4.4.16)
[ 0.000000] Boot CPU: AArch64 Processor [500f0001]
[ 0.000000] earlycon: Early serial console at MMIO32 0x1c020000
(options '')
[ 0.000000] bootconsole [uart0] enabled
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] EFI v2.40 by American Megatrends
[ 0.000000] efi: ACPI 2.0=0x807ff43000 ESRT=0x807e161e18 SMBIOS
3.0=0x807e161c18
ACPI is disabled:
[ 0.083487] ACPI: Interpreter disabled.
It must be using the device tree and surviving whatever bugs it has.
If this seems to work I may keep this kernel and try to convert the base
filesystem from Ubuntu to Debian; that should be easy, right??!
Why try to convert? Just use a debian rootfs with that ubuntu kernel (or
a centos kernel, or a redhat kernel. or a fedora kernel) and friends.
Then, you can build your own debian kernel. Much easier.
Maybe one of you experts can guess how the Debian and Ubuntu installers
and/or kernels differ that cause the Debian ones to fail for me, despite
being newer. I was wondering if GRUB might have some influence.
As mentioned in an earlier post, the debian installer didn't work with
the AR0 board either. Debian are a bit behind the curve on these server
boards.
Mike.
--
Mike Howard
