[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Last revisionBoth sides next revision
slackwarearm:disk_encryption_slackware_aarch64 [2022/05/13 13:57 (UTC)] – created mralk3slackwarearm:disk_encryption_slackware_aarch64 [2023/10/12 18:06 (UTC)] – [Known Issues] clarifications, knonw issue. mralk3
Line 99: Line 99:
  
 ===== Known Issues ===== ===== Known Issues =====
-  * The serial console does not display the password prompt to decrypt storage.+  * This issue has been addressed. <del>The serial console does not display the password prompt to decrypt storage.</del>
  
-The Pinebook Pro has a monitor that remedies this.  However, the RockPro64, Raspberry Pi 3/4, will require a display to be attached. This makes it difficult to use a headless system.  As a workaround, you can boot your system and decrypt the disk with a key file.  You can store the key file on the SD Card.  When you want to leave your system encrypted you can simply remove the SD card and take it with you.+<del> The Pinebook Pro has a monitor that remedies this.  However, the RockPro64, Raspberry Pi 3/4, will require a display to be attached. This makes it difficult to use a headless system.  As a workaround, you can boot your system and decrypt the disk with a key file.  You can store the key file on the SD Card.  When you want to leave your system encrypted you can simply remove the SD card and take it with you.</del>
  
-  * The Pinebook Pro does not always restart properly when the "reboot" command is used.  It is unclear if this is due to the disk being encrypted.+  * The Pinebook Pro does not always restart properly when the "reboot" command is used.  This is marked as a known issue. <del>It is unclear if this is due to the disk being encrypted.</del>
  
 A workaround is to run the "poweroff" command to completely shut down the system instead.  Then power it back up with the power button. A workaround is to run the "poweroff" command to completely shut down the system instead.  Then power it back up with the power button.

Trace: • package_management • localization • multilib • howtos • nl • building_packages_with_sbopkg • mailing_list • first_steps • slackware_automation_using_ansible

slackwarearm:disk_encryption_slackware_aarch64 ()