FWTS(1)

πŸ’– FWTS(1) β€” the fwts-collect girlies' guide πŸ’–

okay so bestie, welcome to the General Commands Manual for fwts-collect, and no cap, this one is a whole mood. let's get into it 🫢


✨ NAME ✨

fwts-collect β€” collect logs for fwts bug reporting. that's the whole vibe, that's the assignment πŸ’…


🌸 SYNOPSIS 🌸

fwts-collect [FILES]

πŸ¦‹ DESCRIPTION πŸ¦‹

this manual page documents, briefly, the fwts-collect firmware test suite log collecting tool. the tea is: fwts-collect collects logs plus a bunch of system and firmware dumps into the gzip'd tar ball fwts-logs.tar.gz, and then you can just yeet that thing into your bug reports. iconic behaviour, honestly.

so what does it scoop up? it collects data from:

  • /proc/iomem
  • /proc/mtrr
  • /proc/interrupts
  • IRQ counts from /sys/firmware/acpi/interrupts
  • kernel logs

and it also invokes fwts and gathers:

  • ACPI tables
  • memorymaps
  • MultiProcessor table dumps
  • CMOS data
  • UEFI variables
  • kernel version and ACPI version information
🚨 okay important: fwts using sudo is required. like, required required. no sudo, no slay.

running fwts with no options will collect logs automatically β€” it just does it, main character energy ✨. however, you can also specify the names of additional files to be added to the gzip'd tar ball. your files, your rules, periodt.


πŸŽ€ EXAMPLES πŸŽ€

gather up logs into fwts-logs.tar.gz:

sudo fwts-collect

gather up logs and also /var/log/pm-powersave.log:

sudo fwts-collect /var/log/pm-powersave.log

πŸ‘‘ SEE ALSO πŸ‘‘

fwts(1), dmidecode(8), lspci(8)


🌈 AUTHOR 🌈

fwts-collect was written by Colin King <colin.king@canonical.com> πŸ’–

this manual page was written by Colin King <colin.king@canonical.com>, for the Ubuntu project (but may be used by others). sharing is caring fr fr 🫢


and that's the whole page bestie!! written up on 5 February, 2015 for the FWTS(1) manual, and honestly? it ate. go collect those logs πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from