From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: meta-intel stuck on bootup #yocto To: yocto@lists.yoctoproject.org From: "Dan O'Donovan" X-Originating-Location: Limerick, Munster, IE (87.198.177.202) X-Originating-Platform: Windows Chrome 78 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Thu, 12 Dec 2019 03:13:59 -0800 References: <3uWx.1576070177005275968.UQCr@lists.yoctoproject.org> In-Reply-To: <3uWx.1576070177005275968.UQCr@lists.yoctoproject.org> Message-ID: <14786.1576149239150344420@lists.yoctoproject.org> Content-Type: multipart/alternative; boundary="NwaEe0bFSu9ORsNvg7E0" --NwaEe0bFSu9ORsNvg7E0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable If you are using the meta-intel layer, you could also change your MACHINE t= o 'intel-corei7-64' instead of 'genericx86-64'.=C2=A0 I'm not sure if it wi= ll fix your specific issue but it will at least allow you to benefit from s= ome of the additional features and patches and other tweaks that the meta-i= ntel layer provides. --NwaEe0bFSu9ORsNvg7E0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable If you are using the meta-intel layer, you could also change your MACHINE t= o 'intel-corei7-64' instead of 'genericx86-64'.  I'm not sure if it wi= ll fix your specific issue but it will at least allow you to benefit from s= ome of the additional features and patches and other tweaks that the meta-i= ntel layer provides. --NwaEe0bFSu9ORsNvg7E0--