Skip to content

Finding components that support feature X: filter on log file output #3

@davidovitch

Description

@davidovitch

I am interested to known which components support, under Linux, a specific hardware feature. Some concrete examples are:

  • What kind of ASPM is supported under Linux for a given component (PCIe ports on a MB, etc)?
  • List/filter all components that support a specific power state ASPM level (L1, L0s)
  • Which notebook batteries support setting the charging start/end thresholds?
  • What level of temperature/fan control is present?
  • etc

Such information is quite valuable when you're on the market for hardware and you have a list of specific Linux support requirements. Unfortunately, the hardware vendors don't really document this so you're left guessing what is possible under Linux and what is not. From the Linux kernel documentation it is also not straight forward to find out the level of hardware support for a given component.

For some of the above examples the information is contained in the lspci_all and upower outputs, but I don't have the impression that this data is indexed so searching for it would require you to first do some scraping of lots of log files of different components to get some kind of an overview.

Happy to help building something here. However, that would only work with some level of buy-in from you @linuxhw since I am not planning to start scraping and parsing the many log files into a searchable database directly from https://linux-hardware.org/. If interested, do you have any idea's on how to collaborate around this? One idea I have is to parse specific items from the log files into some sort of a database/table so you can use that to search/filter as you like. I assume you already do something similar to build the Trends and SMART reports . The simplest workable product I could imagine here is a dumb spreadsheet with filters on the columns. The compute requirements for building such a database are minimum, but it would require fast access to a (local copy) of a (partial) dump of the database and the log files of the corresponding probes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions