Shailesh, For what it's worth, I have the same system running Fedora 31 with an older bios (12/17/2018). You might try adding *nomodeset* to your kernel commandline parameters as this has fixed some kernel call traces issues I had on my other Intel Nuks. On 3/9/20 1:23 PM, Pandey, Shailesh wrote:
Hi All,
Good Morning,
Please find attached the crash log images for StarlingX 3.0 on *Intel Haydes Canynon NUC* running on nvme.
I have *managed to* *flash Ubunttu 18.04 on this NUC on nvme*.
I have *managed to flash CentOS 7.0 using USB bootable USB and than booted CentOS and managed to Burned in Hard drive i.e nvme in this case*.
I have amended kernel commandline paramteter : *boot_device*=nvme0n1 *rootfs_device*=nvme0n1
StarlingX 3.0 boot_image.iso used :
http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outpu...
Please let me know if you have tried above image on Intel *NUC8i7HVK/NUC8iHVB.*
Please help me out what can I do here.
Regards,
Shailesh
Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-- Jack Morgan