NUCs have historically had issues with RHEL and OSes based on it. I know some have made it work but it is a real PITA and took a bit of hackiness to do it.
I’ve had several NUCs with freepbx distro installed and working flawlessly, this NUC11 is a pita, I don’t know if because of NVMe drive or the lack of legacy support (honestly I don’t remember if UEFI/legacy was modified in previous NUCs).
It would be nice to know what is actually happening…
What I would try is getting any Linux to install and boot up then proceed to install your distro without formatting the drive ie “alongside” the other Linux.
Perhaps Intels own Clear Linux OS should be the first install? Or, maybe a distro that uses Grub would be better.
Thanks, noapic gives different boot message but still ends in kernel panic
At least NUC is not unusable… : installing a sata M2 disk instead of NVMe disk , installation starts correctly.
Must investigate in kernel vs NVMe issue…
Finding on the net, there are a lot of “know bug, to be solved in next kernels”…
“Does it worth working on kickstart ?”
Hu? I’m pretty sure this is not an English sentence.
The Problem is that RHEL7/CentOS7, the distribution FreePBX Distro is based on is very very ancient. It was released in April 2014 and uses Kernel version 3.10 - which is from June 2013. Red Hat who updates this distribution used frankenstein-like patches to integrate support for newer hardware into this ancient kernel but there are limits to this.
Until Sangoma invests some time into upgrading the underlying distribution FreePBX Distro is based on, you cannot use modern hardware. Old NUCs should work fine. Perhaps you can get a NUC7 or NUC8 somewhere, my guess is that should be old enough for it to work.
Latest distro is working fine on any NUC supporting Legacy Bios
Also NUC10 is ok, on NUC11 they removed legacy bios, so only older sata devices are ok with installation.
If someone has an Intel NUC valid alternative (same dimensions, performance and price) I’m happy to know…