> On Jan 1, 2016, at 5:13 PM, Mark Kettenis <mark.kette...@xs4all.nl> wrote:
>
>> From: Dale Ghent <da...@elemental.org>
>> Date: Thu, 31 Dec 2015 15:02:11 -0500
>>
>>> On Dec 31, 2015, at 2:43 PM, Mark Kettenis <mark.kette...@xs4all.nl> wro
> On Jan 5, 2016, at 12:05 PM, Mark Kettenis wrote:
>
>>
>>> On Jan 1, 2016, at 5:13 PM, Mark Kettenis wrote:
>>>
>>> Thanks. This strange. I don't quite understand what's happening here
>>> as the ACPI MADT table lists the CPUs in the
> Read my message again. I'm suggesting to turn xhci off in the kernel,
> not the BIOS.
Alright, so here's an update. This Xeon-D system is able to be booted and
installed using your suggestions:
In BIOS:
CPU Configuration -> Cores Enabled -> set to 1
In UKC:
disable acpi
disable xhci
Here's
> On Dec 31, 2015, at 2:43 PM, Mark Kettenis wrote:
>
> Can you please send me a dmesg as well as the acpidump output for this
> machine? That will give me a chance at figuring out what is going
> wrong.
Here you go, Mark:
http://elemental.org/xeon-d.tar.gz
/dale
Has anyone used or otherwise been able to boot 5.8 on a Xeon-D 1540 system?
We're experimenting with a SuperMicro Xeon-D 1540 system
(http://www.supermicro.com/products/system/1U/5018/SYS-5018D-FN4T.cfm) and are,
surprisingly, not getting terribly far into the kernel boot process, with a
returned 0
>>> cpu probe won
cpu0 at mainbus0: apid 0 (application processor)
cpu0: not started
>>> probing for ioapic*
>>> ioapic probe returned 0
>>> probing for efifb0
>>> efifb probe returned 0
>>> probing for pci*
>>> pci probe returned 0
> On Dec 30, 2015, at 3:21 PM, Mark Kettenis <mark.kette...@xs4all.nl> wrote:
>
>> From: Dale Ghent <da...@elemental.org>
>> Date: Wed, 30 Dec 2015 14:49:58 -0500
>>
>> Has anyone used or otherwise been able to boot 5.8 on a Xeon-D 1540 =
>> syst