<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dzu's Blog (Einträge über debian)</title><link>https://blog.lazy-evaluation.net/</link><description></description><atom:link href="https://blog.lazy-evaluation.net/de/categories/debian.xml" rel="self" type="application/rss+xml"></atom:link><language>de</language><copyright>Contents © 2025 &lt;a href="mailto:dzu@member.fsf.org"&gt;Detlev Zundel&lt;/a&gt; </copyright><lastBuildDate>Wed, 10 Dec 2025 16:15:12 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Firmware Updates on GNU/Linux</title><link>https://blog.lazy-evaluation.net/de/posts/linux/fwupdate-linux.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;div style="text-align:center" class="imageblock" id="org3891fba"&gt;

&lt;div id="orgccb53a3" class="figure"&gt;
&lt;p&gt;&lt;img src="https://blog.lazy-evaluation.net/de/images/nvme-logo.png" alt="nvme-logo.png" title="NVMe logo" align="middle" width="250"&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;/div&gt;

&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/fwupdate-linux.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (5 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/fwupdate-linux.html</guid><pubDate>Tue, 05 Aug 2025 22:01:27 GMT</pubDate></item><item><title>Firmware Updates on GNU/Linux</title><link>https://blog.lazy-evaluation.net/de/posts/linux/linux-fwupdate.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;div style="text-align:center" class="imageblock" id="org07126e3"&gt;

&lt;div id="org301e00d" class="figure"&gt;
&lt;p&gt;&lt;img src="https://blog.lazy-evaluation.net/de/images/nvme-logo.png" alt="nvme-logo.png" title="NVMe logo" align="middle" width="250"&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;/div&gt;

&lt;p&gt;
As the NAND storage technology reaches speeds that cannot be satiated
with SATA anymore, the modern SSDs are attached over &lt;a href="https://en.wikipedia.org/wiki/PCI_Express"&gt;PCIe&lt;/a&gt;, the
descendant of the very successful
&lt;a href="https://en.wikipedia.org/wiki/Peripheral_Component_Interconnect"&gt;Peripheral Component Interconnect&lt;/a&gt; standard that allowed for many
extension cards in the IBM PC ecosystem.  But where most PCI cards
could not be software upgraded in the field, the question on how to
update firmware on attached PCI devices is not obviously standardized
(or am I missing something?).  So under Windows, the manufacturers of
NVMe modules deliver their proprietary update tool, but what do we do
in a Free Operating system like GNU/Linux?
&lt;/p&gt;

&lt;p&gt;
In this blog post I will take a quick look at how I was able to
upgrade the firmware of my &lt;b&gt;Kingston SA2000M8250G&lt;/b&gt; NVMe drive in my
desktop system.
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/linux-fwupdate.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (7 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/linux-fwupdate.html</guid><pubDate>Thu, 03 Apr 2025 22:01:27 GMT</pubDate></item><item><title>Updating NVMe Firmware on GNU/Linux</title><link>https://blog.lazy-evaluation.net/de/posts/linux/nvme-fwupdate.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;div style="text-align:center" class="imageblock" id="orgfa02f3a"&gt;

&lt;div id="org04c176d" class="figure"&gt;
&lt;p&gt;&lt;img src="https://blog.lazy-evaluation.net/de/images/nvme-logo.png" alt="nvme-logo.png" title="NVMe logo" align="middle" width="250"&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;/div&gt;

&lt;p&gt;
As the NAND storage technology reaches speeds that cannot be satiated
with SATA anymore, the modern SSDs are attached over &lt;a href="https://en.wikipedia.org/wiki/PCI_Express"&gt;PCIe&lt;/a&gt;, the
descendant of the very successful
&lt;a href="https://en.wikipedia.org/wiki/Peripheral_Component_Interconnect"&gt;Peripheral Component Interconnect&lt;/a&gt; standard that allowed for many
extension cards in the IBM PC ecosystem.  But where most PCI cards
could not be software upgraded in the field, the question on how to
update firmware on attached PCI devices is not obviously standardized
(or am I missing something?).  So under Windows, the manufacturers of
NVMe modules deliver their proprietary update tool, but what do we do
in a Free Operating system like GNU/Linux?
&lt;/p&gt;

&lt;p&gt;
In this blog post I will take a quick look at how I was able to
upgrade the firmware of my &lt;b&gt;Kingston SA2000M8250G&lt;/b&gt; NVMe drive in my
desktop system.
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/nvme-fwupdate.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (3 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/nvme-fwupdate.html</guid><pubDate>Thu, 03 Apr 2025 22:01:27 GMT</pubDate></item><item><title>Empowerment Through Free Software</title><link>https://blog.lazy-evaluation.net/de/posts/linux/free-software-empowerment.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;p&gt;
#+BEGIN_COMMENT
.. title: Empowerment Through Free Software
.. author: Detlev Zundel
.. date: 2025-04-03 23:15:39 CET
.. slug: free-software-empowerment
.. tags: debian, linux, fsf, gnome, simple-scan
.. category:
.. link:
.. description:
.. type: text
#+END_COMMENTg
&lt;/p&gt;
&lt;div style="text-align:center" class="imageblock" id="orgd81b51f"&gt;

&lt;div id="org5120d96" class="figure"&gt;
&lt;p&gt;&lt;img src="https://blog.lazy-evaluation.net/de/images/fsf-member-badge.png" alt="fsf-member-badge.png" title="FSF Member Badge" align="middle" width="250"&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;/div&gt;

&lt;p&gt;
Due to having ordered a new multi-function printer, I find myself
wanting a feature in my software stack, which seems not to be
available.  But as I use a &lt;a href="https://www.gnu.org/philosophy/free-sw.html.en"&gt;Free Software&lt;/a&gt; GNU/Linux system, it is
possible to modify and extend the software on every level, so I decide
to find out if I can fix the problem myself.
&lt;/p&gt;

&lt;p&gt;
Specifically, the new printer has a document feeder for the scanner,
so that I can feed a whole stack of documents to it without manual
intervention.  Unfortunately, it is not able to do both side scans, as
this feature is only available at a much higher price tag.  But
double-sided scanning can be done in two batches by first scanning the
front sides, and then in a second batch the back sides.  The scanned
pages then need to be reordered in a post processing step to group the
corresponding front- and back sides.  Already with my own scanner, I
am pretty happy using the default scan software from the GNOME
desktop, i.e. &lt;a href="https://gitlab.gnome.org/GNOME/simple-scan"&gt;simple-scan&lt;/a&gt;.  I used the GUI to remove pages and reorder
them manually, but I did not find such a functionality that I would
now like to use.  So the topic for today is how to make this work,
ideally before the printer arrives.
&lt;/p&gt;

&lt;p&gt;
I believe this to be a very good example of how empowering Free
Software is, and so I decided to document all my steps in order to
show how I approach this task, which is completely inaccessible for
people working with non-free software.  Actually I invite you to
reproduce the steps on your own distribution to get a feeling on how
easy (or difficult?) it is to work on an arbitrary aspect of the whole
system. 
&lt;/p&gt;

&lt;p&gt;
So fire up your terminal and follow along! Expect some transcripts!
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/free-software-empowerment.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (26 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/free-software-empowerment.html</guid><pubDate>Thu, 03 Apr 2025 21:15:39 GMT</pubDate></item><item><title>Switching on Secure Boot in Debian</title><link>https://blog.lazy-evaluation.net/de/posts/linux/switching-to-secureboot.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;div class="imageblock" id="org03e99df"&gt;
&lt;p class="float-left"&gt;
&lt;img src="https://blog.lazy-evaluation.net/de/images/open-chain-castle-close-security-padlock-1356005-pxhere.com.jpg" alt="Big lock"&gt;
&lt;/p&gt;

&lt;/div&gt;

&lt;p&gt;
My main desktop machine is an AMD Ryzen-2400G on an ASUS PRIME B350M-A
motherboard.  It came with secure boot disabled and as the first
action I installed Debian on it.  Back in early 2019, Debian 10
(i.e. Buster) was stable and based on an 4.19 kernel.  I knew that the
integrated Radeon Vega GPU of this SoC required a more recent kernel,
so I used Debian testing (to become Bullseye) right from the
beginning.  It took me a bit of fiddling until two monitors worked
correctly, but after that it became my main machine.
&lt;/p&gt;

&lt;p&gt;
I did read about enabling secure boot back then, but it seemed the
implementation for GNU/Linux systems had not been defined properly,
and so I left it disabled.  Now that I understand the process better,
I want to use that additional level of security against unwanted
software on my main desktop.  This blog post will explain not only the
basics but also follow through to the nitty-gritty of key handling.
This will be in the context of Debian that I run on my machine, but we
will also compare this to an Ubuntu laptop to get an idea on how the
distributions differ in handling of this topic
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/switching-to-secureboot.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (20 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/switching-to-secureboot.html</guid><pubDate>Wed, 09 Aug 2023 21:15:23 GMT</pubDate></item><item><title>Switching to maildir in Debian Bullseye</title><link>https://blog.lazy-evaluation.net/de/posts/linux/debian-maildir.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;div style="text-align:center" class="imageblock" id="org21f3d6e"&gt;

&lt;div id="org3c25c04" class="figure"&gt;
&lt;p&gt;&lt;img src="https://blog.lazy-evaluation.net/de/images/maildir.png" alt="maildir.png" title="GnuPG logo" align="middle" width="150"&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;/div&gt;

&lt;p&gt;
Although e-mail has lost some of its importance by the advent of
secure messaging platforms like &lt;a href="https://www.signal.org/de/"&gt;Signal&lt;/a&gt;, from time to time I still get
the itch to improve my existing setup.  Recently I wondered why I am
still using a single file &lt;a href="https://en.wikipedia.org/wiki/Mbox"&gt;mbox&lt;/a&gt; instead of the more Unixy &lt;a href="https://de.wikipedia.org/wiki/Maildir"&gt;maildir&lt;/a&gt;
format on my Debian desktop and how difficult it would to be
switch. As we will see, the transition is pretty straight forward.
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/debian-maildir.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (3 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/debian-maildir.html</guid><pubDate>Fri, 22 Oct 2021 21:23:27 GMT</pubDate></item><item><title>Excursion into LXC containers</title><link>https://blog.lazy-evaluation.net/de/posts/linux/lxc-excursion.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;div style="text-align:center" class="imageblock" id="orgb3a0228"&gt;

&lt;div id="orga25265c" class="figure"&gt;
&lt;p&gt;&lt;img src="https://blog.lazy-evaluation.net/de/images/lxc1.png" alt="lxc1.png" title="LXC logo" align="middle" width="150"&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;/div&gt;

&lt;p&gt;
As I like to live on the bleeding edge by using Debian testing
(currently Bookworm), from time to time I run into situations that are
not ease to solve from within the distribution.  For example currently
its impossible to install the &lt;a href="https://yarnpkg.com/"&gt;yarn package manager&lt;/a&gt;:
&lt;/p&gt;

&lt;pre&gt;&lt;font color="#26A269"&gt;&lt;b&gt;dzu@krikkit&lt;/b&gt;&lt;/font&gt;:&lt;font color="#12488B"&gt;&lt;b&gt;~&lt;/b&gt;&lt;/font&gt;$ sudo apt install yarnpkg
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 node-esprima : Depends: nodejs:any
&lt;font color="#C01C28"&gt;&lt;b&gt;E: &lt;/b&gt;&lt;/font&gt;Unable to correct problems, you have held broken packages.
&lt;font color="#26A269"&gt;&lt;b&gt;dzu@krikkit&lt;/b&gt;&lt;/font&gt;:&lt;font color="#12488B"&gt;&lt;b&gt;~&lt;/b&gt;&lt;/font&gt;$ 
&lt;/pre&gt;

&lt;p&gt;
As I do not see an easy way to fix this and as I am pretty sure that
this will work in Debian stable, let's try spinning up an &lt;a href="https://linuxcontainers.org/lxc/introduction/"&gt;LXC&lt;/a&gt; Debian
Bullseye container and work from there instead.  The ultimate goal for
today is to locally build and view the &lt;a href="https://gjs.guide/"&gt;GNOME Javascript guide&lt;/a&gt; from a
git clone to locally test modifications.
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/lxc-excursion.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (9 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/lxc-excursion.html</guid><pubDate>Fri, 22 Oct 2021 20:51:18 GMT</pubDate></item><item><title>Debugging GNOME GThumb</title><link>https://blog.lazy-evaluation.net/de/posts/linux/debugging-gnome-gthumb.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description></description><guid>https://blog.lazy-evaluation.net/de/posts/linux/debugging-gnome-gthumb.html</guid><pubDate>Sun, 04 Oct 2020 20:48:31 GMT</pubDate></item><item><title>Vivado 2018.3 and DocNav on Debian 10 (Buster)</title><link>https://blog.lazy-evaluation.net/de/posts/linux/vivado-2018-3-buster.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;p&gt;Late last year the ageing effects of my old GNU/Linux desktop system
became so severe that ignoring them would soon not be an option
anymore.  One of the hard disks developed problems a while ago and
although I was able to fix it so that finally the extended &lt;a class="reference external" href="https://en.wikipedia.org/wiki/S.M.A.R.T."&gt;SMART&lt;/a&gt; test passed again without
errors, it still continued to report errors in the form of "unreadable
(pending) sectors".  The on-board USB controller also complains about
one of the internal USB ports for a long time and one DDR3 ram module
had to be replaced as diagnosed by the wonderful &lt;a class="reference external" href="https://en.wikipedia.org/wiki/Memtest86"&gt;Memtest86&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;On top of all this, the &lt;a class="reference external" href="https://icecat.biz/en/p/club3d/cgax-hp136/graphics+cards-radeon+x1300pro+256mb-443229.html"&gt;Club 3D Radeon X1300PRO&lt;/a&gt;
dual DVI graphics card started to occasionally hang the whole system a
few seconds after waking up from suspend.  Or at least that is what I
suspect as the system never recorded error messages in the log files.
The display however did visibly degrade and I think I saw some drm
error message flash by at some point.&lt;/p&gt;
&lt;p&gt;Be that as it will, I was glad that I got the chance to replace the
system in time and gradually move stuff off a functioning system
instead of attaching disassembled hard disks to a new system. The &lt;a class="reference external" href="http://www.arlt.com/PC/fluesterleise-Silent-PCs/Whisper-Serie/ARLT-Mr-Whisper-AMD-Ryzen-5-8GB-SSD-Radeon-Vega-11-arlt-1.html"&gt;AMD
Ryzen 5 2400G system&lt;/a&gt;
from ARLT Computer, available without Windows, looked like very good
value for money. Together with an HDMI to DVI adapter it should also
easily power my two DVI monitor setup and so it did not take long
until one of them stood beside my desk for installation.  As the Ryzen
CPU was introduced early in 2018 and the Linux 4.9 kernel at the core
of Debian Stretch was released end of 2016, it was clear that I needed
to go for the yet unreleased Debian Buster based on Linux 4.19.&lt;/p&gt;
&lt;img alt="Buster from Toy Story" class="align-center" src="https://blog.lazy-evaluation.net/images/toy-story-buster.jpg" style="width: 200px;"&gt;
&lt;p&gt;All in all things went smoothly until I turned to the Xilinx tool
chain that already gave me minor problems described in my previous
post &lt;a class="reference external" href="https://blog.lazy-evaluation.net/posts/linux/docnav-2017-04-debian-stretch.html"&gt;Fixing DocNav 2017.04 on Debian Stretch&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/vivado-2018-3-buster.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (7 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/vivado-2018-3-buster.html</guid><pubDate>Tue, 12 Feb 2019 19:38:15 GMT</pubDate></item><item><title>Fixing DocNav 2017.04 on Debian Stretch</title><link>https://blog.lazy-evaluation.net/de/posts/linux/docnav-2017-04-debian-stretch.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;p&gt;Having installed &lt;a class="reference external" href="https://www.xilinx.com/products/design-tools/vivado.html"&gt;Vivado 2017.04&lt;/a&gt; on one of
my GNU/Linux machines that run Debian 9.3 (Stretch), I realized that
DocNav fails to start:&lt;/p&gt;
&lt;div class="code"&gt;&lt;pre class="code console"&gt;&lt;a id="rest_code_1f69995b3ba04fc58d6c0dd6821cd60c-1" name="rest_code_1f69995b3ba04fc58d6c0dd6821cd60c-1" href="https://blog.lazy-evaluation.net/de/posts/linux/docnav-2017-04-debian-stretch.html#rest_code_1f69995b3ba04fc58d6c0dd6821cd60c-1"&gt;&lt;/a&gt;&lt;span class="gp"&gt;dzu@deepthought:~$ &lt;/span&gt;.&lt;span class="w"&gt; &lt;/span&gt;/opt/Xilinx/Vivado/2017.4/settings64.sh
&lt;a id="rest_code_1f69995b3ba04fc58d6c0dd6821cd60c-2" name="rest_code_1f69995b3ba04fc58d6c0dd6821cd60c-2" href="https://blog.lazy-evaluation.net/de/posts/linux/docnav-2017-04-debian-stretch.html#rest_code_1f69995b3ba04fc58d6c0dd6821cd60c-2"&gt;&lt;/a&gt;&lt;span class="gp"&gt;dzu@deepthought:~$ &lt;/span&gt;docnav
&lt;a id="rest_code_1f69995b3ba04fc58d6c0dd6821cd60c-3" name="rest_code_1f69995b3ba04fc58d6c0dd6821cd60c-3" href="https://blog.lazy-evaluation.net/de/posts/linux/docnav-2017-04-debian-stretch.html#rest_code_1f69995b3ba04fc58d6c0dd6821cd60c-3"&gt;&lt;/a&gt;&lt;span class="go"&gt;docnav: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory&lt;/span&gt;
&lt;a id="rest_code_1f69995b3ba04fc58d6c0dd6821cd60c-4" name="rest_code_1f69995b3ba04fc58d6c0dd6821cd60c-4" href="https://blog.lazy-evaluation.net/de/posts/linux/docnav-2017-04-debian-stretch.html#rest_code_1f69995b3ba04fc58d6c0dd6821cd60c-4"&gt;&lt;/a&gt;&lt;span class="gp"&gt;dzu@deepthought:~$&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;img alt="Xilinx Logo" class="align-center" src="https://blog.lazy-evaluation.net/images/xilinx-logo.png" style="width: 150px;"&gt;
&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/docnav-2017-04-debian-stretch.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (1 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/docnav-2017-04-debian-stretch.html</guid><pubDate>Sun, 28 Jan 2018 17:38:29 GMT</pubDate></item></channel></rss>