<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Hi!<br>
</p>
<p><br>
</p>
<p>I am struggling for days now trying to get a custom (or newer) kernel to boot on a amd64 (Atom) board (or in Virtual Box).<br>
</p>
<p>Currently the board is running the infamous <a href="https://people.canonical.com/~mvo/all-snaps/amd64-all-snap.img.xz">https://people.canonical.com/~mvo/all-snaps/amd64-all-snap.img.xz</a> image.<br>
</p>
<p><br>
</p>
<p>Today I stopped trying to get one of my kernel.snaps to work and downloaded a provided kernel.snap: <a href="http://cdimage.ubuntu.com/ubuntu-core/daily-preinstalled/current/xenial-preinstalled-core-amd64.kernel.snap">http://cdimage.ubuntu.com/ubuntu-core/daily-preinstalled/current/xenial-preinstalled-core-amd64.kernel.snap</a><br>
</p>
<p><br>
</p>
<p>I could not install this one using sideloading: <br>
</p>
<p><br>
</p>
<div>ubuntu@localhost:~$ sudo snappy install xenial-preinstalled-core-amd64.kernel.snap </div>
<div>Installing xenial-preinstalled-core-amd64.kernel.snap</div>
<div>xenial-preinstalled-core-amd64.kernel.snap failed to install: package "canonical-pc-linux" is already installed with origin "canonical" your origin is "sideload"</div>
<div><br>
<br>
So I unpacked it with unsquasfh:<br>
</div>
<div>unsquashfs ../xenial-preinstalled-core-amd64.kernel.snap<br>
</div>
<div><br>
</div>
<div>Changed the name in meta/snapcraft.yaml<br>
</div>
<div><br>
</div>
<div>and compressed it again<span style="font-size: 12pt;">:</span></div>
<div>mksquashfs squashfs-root test1.snap -noappend -comp xz -no-xattrs<br>
</div>
<div><br>
</div>
<div><br>
I am installing the kernel.snap:<br>
</div>
<div>
<div>sudo snappy install test1.snap </div>
<div>Installing test1.snap</div>
<div><br>
</div>
<div>Name Date Version Developer </div>
<div>canonical-pc 2016-02-02 3.0 canonical </div>
<div>canonical-pc-linux 2016-03-21 4.4.0-14-1 canonical </div>
<div>custom-pc-linux-trion 2016-04-14 LWNSFLbcjhSj sideload </div>
<div>trionet 2016-04-06 LVdChFfSWTRn sideload </div>
<div>ubuntu-core 2016-03-08 16.04.0-24 canonical </div>
<div>Reboot to use custom-pc-linux-trion version LWNSFLbcjhSj.</div>
<div><br>
<br>
</div>
But after the reboot I seem to be stuck in the initrd:<br>
</div>
<div>grep: /proc/device-tree/model: No such file or directory<br>
</div>
<div><br>
</div>
<div>After some time <br>
</div>
<div>findfs: unable to resolve 'LABEL=writeable'<br>
</div>
<div><br>
</div>
<div>cannot find 'writable' partition<br>
</div>
<div><br>
</div>
<div>BusyBox ...<br>
</div>
<div>(initramfs)<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>This is not board specific as I can reproduce the same behaviour in VirtualBox.<br>
</div>
<div><br>
Thanks for your help.<br>
</div>
<div><br>
</div>
<div>Bye Gunther<br>
</div>
<div><br>
</div>
<div>PS: The recovery function works good. The next reboot always find its way back to the default working kernel.<br>
</div>
</body>
</html>