Bogon kernel command line options: Difference between revisions
No edit summary |
No edit summary |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''[[Dankblog|dankblog!]] 2022-03-12, 1842 | '''[[Dankblog|dankblog!]] 2022-03-12, 1842 EST, at [[Viewpoint|the danktower]]''' | ||
i was looking at my dmesg output today, wanting to know something about [[IOMMU]], and noticed the following line: | i was looking at my dmesg output today, wanting to know something about [[IOMMU]], and noticed the following line: | ||
| Line 19: | Line 19: | ||
<ul> | <ul> | ||
<li><tt>BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2</tt> this is set by grub since | <li><tt>BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2</tt> this is set by [https://www.gnu.org/software/grub/ GRUB] since 1.91, released 2005-10-15. i'm not sure why, or who consumes it. LILO set this parameter as well, and this might have just been a compatibility thing, so it might be lost in the river of time.</li> | ||
<li><tt>mem_encrypt=off</tt> this refers to AMD's [https://en.wikichip.org/wiki/x86/sme Secure Memory Encryption] extension, allowing per-page transparent encryption. i've got this disabled in my kernel config now (<tt>CONFIG_AMD_MEM_ENCRYPT</tt>), so it's no longer recognized. i've removed it.</li> | <li><tt>mem_encrypt=off</tt> this refers to AMD's [https://en.wikichip.org/wiki/x86/sme Secure Memory Encryption] extension, allowing per-page transparent encryption. i've got this disabled in my kernel config now (<tt>CONFIG_AMD_MEM_ENCRYPT</tt>), so it's no longer recognized. i've removed it.</li> | ||
<li><tt>intel_iommu=on</tt> well duh i don't have an intel in this machine. i want <tt>iommu=pt iommu=1</tt></li> | <li><tt>intel_iommu=on</tt> well duh i don't have an intel in [[Schwarzgerat_III|this machine]]. i want <tt>iommu=pt iommu=1</tt></li> | ||
</ul> | </ul> | ||
| Line 28: | Line 28: | ||
<tt>BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2 root=UUID=939be09a-b63d-403c-996a-8b9866313fbb ro mem_encrypt=off psi=0 acpi_enforce_resources=lax intel_iommu=on</tt> | <tt>BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2 root=UUID=939be09a-b63d-403c-996a-8b9866313fbb ro mem_encrypt=off psi=0 acpi_enforce_resources=lax intel_iommu=on</tt> | ||
<tt>psi=0</tt> refers to the Pressure Stall Information feedback system introduced in 2018 by Facebook hackers, which you can read about [https://www.kernel.org/doc/html/latest/accounting/psi.html here] or [https://lwn.net/Articles/764761/ here]. | <tt>psi=0</tt> refers to the Pressure Stall Information feedback system introduced in 2018 by Facebook hackers, which you can read about [https://www.kernel.org/doc/html/latest/accounting/psi.html here] or [https://lwn.net/Articles/764761/ here]. <tt>acpi_enforce_resources=lax</tt> is sadly necessary to control my bling-ass LEDs using [https://openrgb.org/ OpenRGB]. | ||
''' | anyway, i wasn't aware of this dmesg output (added on [https://lore.kernel.org/lkml/20210511211009.42259-1-ahalaney@redhat.com/ 2021-05]), but it seems a useful bit of diagnostics. unfuck your kernel command line! | ||
the only crappy element is the low visibility. ideally, a systemd oneshot unit would deliver a potent shock to the operator when this message was detected. constant vigilance! | |||
'''previously: "[[On_the_Effectiveness_of_nonnull|on the effectiveness of nonnull]]" 2021-11-05''' | |||
[[Category:Blog]] | [[Category:Blog]] | ||