<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.2.2">Jekyll</generator><link href="/myblog/feed.xml" rel="self" type="application/atom+xml" /><link href="/myblog/" rel="alternate" type="text/html" /><updated>2022-10-07T17:13:27+00:00</updated><id>/myblog/feed.xml</id><title type="html">Your awesome title</title><subtitle>Write an awesome description for your new site here. You can edit this line in _config.yml. It will appear in your document head meta (for Google search results) and in your feed.xml site description.</subtitle><entry><title type="html">Welcome to Jekyll!</title><link href="/myblog/jekyll/update/2022/10/04/welcome-to-jekyll.html" rel="alternate" type="text/html" title="Welcome to Jekyll!" /><published>2022-10-04T11:02:13+00:00</published><updated>2022-10-04T11:02:13+00:00</updated><id>/myblog/jekyll/update/2022/10/04/welcome-to-jekyll</id><content type="html" xml:base="/myblog/jekyll/update/2022/10/04/welcome-to-jekyll.html"><![CDATA[<p>You’ll find this post in your <code class="language-plaintext highlighter-rouge">_posts</code> directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run <code class="language-plaintext highlighter-rouge">jekyll serve</code>, which launches a web server and auto-regenerates your site when a file is updated.</p>

<p>Jekyll requires blog post files to be named according to the following format:</p>

<p><code class="language-plaintext highlighter-rouge">YEAR-MONTH-DAY-title.MARKUP</code></p>

<p>Where <code class="language-plaintext highlighter-rouge">YEAR</code> is a four-digit number, <code class="language-plaintext highlighter-rouge">MONTH</code> and <code class="language-plaintext highlighter-rouge">DAY</code> are both two-digit numbers, and <code class="language-plaintext highlighter-rouge">MARKUP</code> is the file extension representing the format used in the file. After that, include the necessary front matter. Take a look at the source for this post to get an idea about how it works.</p>

<p>Jekyll also offers powerful support for code snippets:</p>

<figure class="highlight"><pre><code class="language-ruby" data-lang="ruby"><span class="k">def</span> <span class="nf">print_hi</span><span class="p">(</span><span class="nb">name</span><span class="p">)</span>
  <span class="nb">puts</span> <span class="s2">"Hi, </span><span class="si">#{</span><span class="nb">name</span><span class="si">}</span><span class="s2">"</span>
<span class="k">end</span>
<span class="n">print_hi</span><span class="p">(</span><span class="s1">'Tom'</span><span class="p">)</span>
<span class="c1">#=&gt; prints 'Hi, Tom' to STDOUT.</span></code></pre></figure>

<p>Check out the <a href="https://jekyllrb.com/docs/home">Jekyll docs</a> for more info on how to get the most out of Jekyll. File all bugs/feature requests at <a href="https://github.com/jekyll/jekyll">Jekyll’s GitHub repo</a>. If you have questions, you can ask them on <a href="https://talk.jekyllrb.com/">Jekyll Talk</a>.</p>]]></content><author><name></name></author><category term="jekyll" /><category term="update" /><summary type="html"><![CDATA[You’ll find this post in your _posts directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run jekyll serve, which launches a web server and auto-regenerates your site when a file is updated.]]></summary></entry><entry><title type="html">Adventures with Headless RPi</title><link href="/myblog/2022/10/04/headless-rpi.html" rel="alternate" type="text/html" title="Adventures with Headless RPi" /><published>2022-10-04T00:00:00+00:00</published><updated>2022-10-04T00:00:00+00:00</updated><id>/myblog/2022/10/04/headless-rpi</id><content type="html" xml:base="/myblog/2022/10/04/headless-rpi.html"><![CDATA[<h1 id="the-goal">The goal</h1>

<p>Run a tk-inter app from Docker on a headless Raspberry Pi</p>

<h1 id="the-tools">The tools</h1>

<ul>
  <li>Raspberry Pi 4</li>
  <li><a href="https://downloads.raspberrypi.org/raspios_lite_arm64/images/">Raspberry Pi OS Lite 64bit</a></li>
  <li>4” HDMI screen</li>
  <li>Docker</li>
</ul>

<p>Install Portainer agent</p>
<div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code>docker run <span class="nt">-d</span> <span class="se">\</span>
	<span class="nt">-p</span> 9001:9001 <span class="se">\</span>
	<span class="nt">--name</span> portainer_agent <span class="se">\</span>
	<span class="nt">--restart</span><span class="o">=</span>always <span class="se">\</span>
	<span class="nt">-v</span> /var/run/docker.sock:/var/run/docker.sock <span class="se">\</span>
	<span class="nt">-v</span> /var/lib/docker/volumes:/var/lib/docker/volumes portainer/agent:latest
</code></pre></div></div>

<h1 id="install-xorg">Install xorg</h1>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>sudo apt install 
</code></pre></div></div>

<h1 id="issue-1-lcd-isnt-full-screen">Issue 1: LCD isn’t full screen</h1>
<p>https://www.raspberrypi.com/documentation/computers/config_txt.html#hdmi-mode</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>nano /boot/config.txt
</code></pre></div></div>

<p>Settings that seems to work for the console:</p>

<ul>
  <li>overscan_right=48</li>
  <li>hdmi_force_hotplug=1</li>
  <li>hdmi_group=2</li>
  <li>hdmi_mode=14</li>
  <li>hdmi_drive=2</li>
  <li>config_hdmi_boost=4</li>
  <li>sdtv_mode=2</li>
</ul>

<p>Get current screen config:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>startx
xrandr
</code></pre></div></div>

<p>Errors generated in log file:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>sudo startx
X -configure
nano /var/log/Xorg.1.log
</code></pre></div></div>

<p>The answer may be in this <a href="../assets/logs/Xorg.1.log">log file</a>.</p>]]></content><author><name></name></author><summary type="html"><![CDATA[The goal]]></summary></entry></feed>