<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TLEer's Blog</title><link>https://ac2.ac.cn/en/</link><description>Recent content on TLEer's Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 26 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ac2.ac.cn/en/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting up NVIDIA Drivers on systemd-boot Fedora</title><link>https://ac2.ac.cn/en/posts/systemd-nvidia/</link><pubDate>Sun, 26 Jul 2026 00:00:00 +0000</pubDate><guid>https://ac2.ac.cn/en/posts/systemd-nvidia/</guid><description>&lt;h1 id="0-before-we-begin"&gt;0. Before we begin&lt;a class="heading-anchor" href="#0-before-we-begin" aria-label="Link to this section"&gt;#&lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;I carried out installation on my Dell Precision 5570 laptop, steps to enroll db keys may vary depending on your PC.&lt;/p&gt;
&lt;p&gt;There are two separate trust operations:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;EFI signing: firmware &lt;code&gt;db&lt;/code&gt; trusts systemd-boot and your UKI.&lt;/li&gt;
&lt;li&gt;Kernel-module signing: the NVIDIA modules are signed by a key the kernel trusts.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;No MOK is needed when booting directly through systemd-boot, provided the module certificate is in firmware &lt;code&gt;db&lt;/code&gt; and Fedora imports that key into a keyring accepted for module verification. The tutorials online are mainly about grub+shim and will often require you to enroll a MOK key.&lt;/p&gt;</description></item><item><title>Delete CF Pages Deployments</title><link>https://ac2.ac.cn/en/posts/cf-too-many-deploy/</link><pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate><guid>https://ac2.ac.cn/en/posts/cf-too-many-deploy/</guid><description>&lt;p&gt;You may encounter the error &lt;code&gt;Your project has too many deployments to be deleted, follow this guide to delete them: https://cfl.re/3CXesln&lt;/code&gt; when trying to delete a pages project which has more than approx. 100 deployments(each construction is considered as one build, like you updated an entry in your blog)&lt;/p&gt;
&lt;p&gt;&lt;img src="https://ac2.ac.cn/images/20260725_143129.png" alt="Screenshot"&gt;&lt;/p&gt;
&lt;p&gt;So I tell the big fat fish(Deepseek) to write a python script for me to automatically delete the deployments so that I can delete the project afterwards. The repo &lt;a href="https://github.com/RamaAditya49/cloudflare-bulk-delete"&gt;cloudflare-buik-delete&lt;/a&gt; is broken as the records per page of the pages api query is limited at 25, while the tool send queries with 100 records per page, causing HTTP 400 error&lt;/p&gt;</description></item><item><title>Signing systemd-boot files and enroll PK for secure boot</title><link>https://ac2.ac.cn/en/posts/systemd-secureboot/</link><pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate><guid>https://ac2.ac.cn/en/posts/systemd-secureboot/</guid><description>&lt;h1 id="0-before-we-begin"&gt;0. Before we begin&lt;a class="heading-anchor" href="#0-before-we-begin" aria-label="Link to this section"&gt;#&lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;Lately I tried to install Fedora to replace Ubuntu to get rid of the snap s**t. And I got an idea from nowhere deciding to give systemd-boot a try, so that&amp;rsquo;s how the nightmare begins.&lt;/p&gt;
&lt;p&gt;There are two separate trust operations:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;EFI signing: firmware &lt;code&gt;db&lt;/code&gt; trusts systemd-boot and your UKI.&lt;/li&gt;
&lt;li&gt;Kernel-module signing: the NVIDIA modules are signed by a key the kernel trusts.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;No MOK is needed when booting directly through systemd-boot, provided the module certificate is in firmware &lt;code&gt;db&lt;/code&gt; and Fedora imports that key into a keyring accepted for module verification. The tutorials online are mainly about grub+shim and will often require you to enroll a MOK key.&lt;/p&gt;</description></item></channel></rss>