One thing that continues to irk me about Linux is how pedantic it can be in terms of logging unimportant happenings especially on bootup. Like the fact that Pulse Audio Volume Control cannot interact with Bluetooth. So it spits out a lengthy explanation in a log file, along with other non-critical concerns that in reality are not concerns at all. I eventually found a fix that eliminates the issue entirely. No harm, no foul given I don't use Bluetooth technology at all.
The good news is that over time and updated versions of Linux Mint (20.3 to 21.0) I have been able to eliminate these messages one-by-one by posting them verbatim into search engines. With a little time and patience I've been able to find the right solution in terms of either making them invisible in the bootup process or even better, to stop them from being posted in the log file. All those pieces of text add up unless you routinely purge them using apps like "Stacer" to eliminate all that unnecessary recording of benign issues that the OS does automatically.
The only things now being logged are the last two mysteries to solve. Eventually I may find the right solution to make them go away, unless they involve BIOS settings I choose not to alter. From what I have googled, they appear to be "bios bugs". Non-critical, but annoying to see them systematically show up in log files. Yet given the age of my computer's motherboard, it's impractical to consider updating my BIOS. In any event I have made them invisible on bootup by simply adding "loglevel=3" in my GRUB file.
1) gkr-pam: unable to locate daemon control file
2) ACPI Error: Aborting method \ _SB.PCI0.SATO._GTF due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Presently I'm mulling over this link as a possible fix to stop item#2 from being perpetually logged. Which would be nice given this repeats itself no less than eight times in both bootup and in being recorded as an entry to the log file. Of course in adding "loglevel=3" to my GRUB file, at least it no longer shows on bootup. Making booting Linux Mint 21.0 no more than ten seconds after the BIOS information comes and goes onscreen.
Where I need to make yet another addition to the default command line of my GRUB file:
GRUB_CMDLINE_LINUX_DEFAULT="libata.noacpi=1"
Providing of course that I found the right answer:
ACPI BIOS ERROR (BUG): Could not resolve symbol [\_SB.PCIO.SATO.PRTO._GTF.DSSP] AE_NOT_FOUND (20190816/psargs-330)
Still, I'm thrilled that my perserverance has paid off over time. Having gotten these benign log entries down to a mere two items. The bad news? If you really want to tweak your Linux Distro to near-perfection, these are the sort of things you have to get your feet wet over. The good news? It's usually just a matter of using search engines to find the answers. That unlike Microsoft Windows, you really can have virtually everything your way if you really want it. Though the older your computer may be, the more likely you may have to deal with such things.
Do you absolutely have to do this sort of thing? LOL....hellno. But if you have OCD, expect yourself to do something about it until you have everything "just so". In essence, this is far more about ME than Linux. Still, for me the effort is worth it in making a ten-year old computer run like a fine, well-oiled machine. With Micro$oft completely out of the picture.