<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Raspberry Pi 2 on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/raspberry-pi-2/</link>
        <description>Recent content in Raspberry Pi 2 on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Wed, 28 Dec 2016 22:00:29 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/raspberry-pi-2/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>[Raspberry Pi] Warning - Kernel 4.4.38 breaks boot on RPi 1 &amp; 2</title>
            <link>https://www.nico-maas.de/posts/2016-12-28-raspberry-pi-warning-kernel-4-4-38-breaks-boot-on-rpi-1-2/</link>
            <pubDate>Wed, 28 Dec 2016 22:00:29 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2016-12-28-raspberry-pi-warning-kernel-4-4-38-breaks-boot-on-rpi-1-2/</guid>
            <description>&lt;p&gt;About 14 days ago, RPi Kernel Version 4.4.38 was published. However, something went very wrong somewhere: Raspbery Pi Models 1 and 2 do not boot anymore. As a quickfix I would recommend to download the 4.4.37 Kernel from the Github Repo (&lt;a class=&#34;link&#34; href=&#34;https://github.com/raspberrypi/firmware/&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;https://github.com/raspberrypi/firmware/&lt;/a&gt;) and replace the boot Partition on your RPi 1 or 2 SDCard with the /boot path from the 4.4.37 &lt;a class=&#34;link&#34; href=&#34;https://github.com/raspberrypi/firmware/archive/6d45dcf869688163fa1c745cb059b14baf61b8fd.zip&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;ZIP File&lt;/a&gt; - and it should boot again. If you&amp;rsquo;re RPi is still working - do not update your kernel until this problem is solved! &lt;a class=&#34;link&#34; href=&#34;https://github.com/raspberrypi/firmware/issues/704&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;Issue on Github&lt;/a&gt;.&lt;/p&gt;</description>
        </item><item>
            <title>[RaspPi] Snappy Ubuntu Core on Raspberry Pi 2</title>
            <link>https://www.nico-maas.de/posts/2015-03-04-rasppi-snappy-ubuntu-core-on-raspberry-pi-2/</link>
            <pubDate>Wed, 04 Mar 2015 12:55:09 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2015-03-04-rasppi-snappy-ubuntu-core-on-raspberry-pi-2/</guid>
            <description>&lt;p&gt;Well, I finally got my Raspberry Pi 2 and just could not hold back and wanted to test Snappy Ubuntu Core and give a little introduction and how that thing works.&lt;/p&gt;&#xA;&lt;p&gt;Ok, but short into: What is Snappy Ubuntu Core?&lt;br&gt;&#xA;Well it is meant to be a secure operating system for embedded applications.&lt;br&gt;&#xA;It is based on an transactional system-management and can even rollback upgrades of the system core.&lt;br&gt;&#xA;There are three kinds of Snappy Ubuntu Core Components:&lt;br&gt;&#xA;Snappy Ubuntu Core itself (Core), Frameworks and Apps.&lt;br&gt;&#xA;Frameworks can access the Core in certain ways and thus need to be reviewed by the Ubuntu Team.&lt;br&gt;&#xA;Apps are completly isolated from each other and have limited access to the system, therefore they don&amp;rsquo;t need special security profiles or reviews, which makes publishing easier.&lt;br&gt;&#xA;Ok, and everything is controlled via the command &amp;ldquo;snappy&amp;rdquo;.&lt;/p&gt;</description>
        </item></channel>
</rss>
