Try New Technology

While doing some PBO tuning in the BIOS I ran into an issue where X died and I forgot all about the CTRL+ALT+F1-9 option to get to a CLI which would then allow me to login and issue a correct “shutdown” command. After this hard shutdown the computer would hang at the boot up stage (the 3 dots on the screen of KDE).

Below are the steps taken to fix this (in short the boot drive needed fsck ran):

• Create a bootable Manjaro Live Image (https://manjaro.org/download/) using something like DD, Rufus, Etcher, etc. (this is why you should always have one laying around)
• Once at the USB Live desktop open a Terminal window and use the “fsck” command (ie “fsck /dev/sda1“); you may need to use “sudo fsck“. NOTE: Make sure to not access any part of the drive needing checked (otherwise you will need to unmount it first).
• You should run fsck on all the different partitions of the drive, and if you get a “Dirty Bit” error on the UEFI partition then I found it best to exit the fsck and then run “fsck -a /dev/sda1“
• Reboot and boot into the computer like normal

NOTE: You may need to use “lsblk -f” from the Terminal to figure out what the correct devices are. For example an NVME boot device UEFI partition should be something like “/dev/nvme0n1p1” and then the file storage something like “dev/nvme0n1p2”

I was getting some blocker errors when running “pamac update chirp-next” (“pamac checkupdates” didn’t show signs of issues) and then I saw “Error: sublime-text.db: sublime-text: signature from “Sublime HQ Pty Ltd support@sublimetext.com” is invalid” near the start of “sudo pacman -Syyu” was ran. A very quick search online found the fix posted on the Sublime Text forums (source linked at the bottom). Below is the fix for this when it happens for anyone:

cd /var/lib/pacman/sync && sudo rm sublime-text.db.sig

NOTE: “sudo flatpak upgrade” obviously isn’t impacted by this.

Source: Sublime-text: signature from “Sublime HQ Pty Ltd is invalid – Sublime Forum

Needing to get details and support for a Solidigm (and Intel) SSD on Manjaro Linux? Install the Solidigm Storage Tool (“…supports firmware upgrades and 4Kn sector size changes for Intel and Solidigm PCIe/NVMe/SATA NAND SSDs”):

1. Enable AUR (Arch User Repository): Add/Remove Software > (three dots/hamburger menu) > Preferences > Third Party (tab) > “Enable AUR support” and “Check for updates” > Close the Add/Remove Software
2. From CLI: pamac build solidigm-sst-storage-tool-cli

Now you have access to commands such as “sudo sst show -all -ssd” to get all the information about your Solidigm or Intel SSD.

Extras:
AUR (en) – solidigm-sst-storage-tool-cli
Solidigm Storage Tool User Guide – CLI Public – sst-cli-user-guide-public-727329-006us.pdf

I have found the snapd version of CHIRP (free, open-source tool for programming your radio) was problematic when trying to set permissions for it to access the physical interface when the radio is plugged into the computer. Further research found that this can be installed from the AUR repo’s. Below are the steps I used and at he bottom of the post will be links to the source materials I used:

1. Enable AUR (Arch User Repository): Add/Remove Software > (three dots/hamburger menu) > Preferences > Third Party (tab) > “Enable AUR support” and “Check for updates” > Close the Add/Remove Software
2. From CLI: pamac build chirp-next

Sources:
Enable Arch User Repository (AUR) in Manjaro – Linux for Devices
Chirp Radio Software – Support / Third-party Applications – Manjaro Linux Forum

For a while now (since a kernel update back when I was still on an LTS) I will randomly have apps “hang” when opening or the icon show it’s open on the taskbar while it has closed from the screen. Sometimes it happened a lot, and other times not at all. I couldn’t find any solution and all the hardware tested good.

Recently I found about out about the issue with Kernels after 6.1 experiencing stutter because of the AMD Ryzen fTPM (Bug 216989).

After turning off the fTPM in my BIOS I so far have not had any of these issues anymore!

In many causes this can be found under Security > Trusted Computing: “Security Device Support” set to Disabled will completely disable TPM. There are other options if you just want to turn of fTPM but support a hardware TPM.