<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>AI Generated (Verified) on PSA Labs</title><link>https://psalabs.eu/tags/ai-generated-verified/</link><description>Recent content in AI Generated (Verified) on PSA Labs</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 08 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://psalabs.eu/tags/ai-generated-verified/index.xml" rel="self" type="application/rss+xml"/><item><title>proxmox: NIC issues with e1000e network adapters</title><link>https://psalabs.eu/articles/kb/proxmox-nic-issues/</link><pubDate>Sun, 08 Feb 2026 00:00:00 +0000</pubDate><guid>https://psalabs.eu/articles/kb/proxmox-nic-issues/</guid><description>&lt;h2 id="summary"&gt;Summary&lt;/h2&gt;
&lt;p&gt;Some Intel onboard NICs using the &lt;strong&gt;e1000e&lt;/strong&gt; driver can intermittently lose network connectivity on Proxmox VE and repeatedly log errors like:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;e1000e … Detected Hardware Unit Hang&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This can cascade into Linux bridge ports being disabled (VM connectivity loss) and may trigger reboot/recovery automation if present.&lt;/p&gt;
&lt;p&gt;A commonly used mitigation is to disable specific NIC offloads (especially &lt;strong&gt;TSO&lt;/strong&gt;) and disable &lt;strong&gt;EEE (Energy Efficient Ethernet)&lt;/strong&gt;, then re-apply those settings on every boot using a systemd unit.&lt;/p&gt;</description></item><item><title>macOS seamless authentication</title><link>https://psalabs.eu/articles/2026/01/macos-seamless-authentication/</link><pubDate>Wed, 21 Jan 2026 00:00:00 +0000</pubDate><guid>https://psalabs.eu/articles/2026/01/macos-seamless-authentication/</guid><description>&lt;p&gt;If you do anything admin-related on macOS, you know the drill:
a random dialog pops up, you type your password, you continue&amp;hellip; and repeat that 20 times a day.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;GUI prompts (System Settings, installers, “needs your password”, &amp;hellip;) can use Touch ID and often Apple Watch confirmation.&lt;/li&gt;
&lt;li&gt;Terminal &lt;code&gt;sudo&lt;/code&gt; can be upgraded to use Touch ID as well (so you don’t have &lt;em&gt;two&lt;/em&gt; authentication experiences).&lt;/li&gt;
&lt;/ul&gt;


 &lt;blockquote class="alert alert-note"&gt;
 &lt;p class="alert-title"&gt;Clamshell reality check:&lt;/p&gt;
 &lt;p&gt;Touch ID for &lt;code&gt;sudo&lt;/code&gt; only works when a Touch ID sensor is available. With the MacBook lid closed, the built-in Touch ID button isn’t usable — you’ll need an external Touch ID keyboard. Apple Watch can approve many GUI prompts, but it won’t replace the password prompt for &lt;code&gt;sudo&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>