Ondrej Čerman

@mckaygerhard udisks2 is not required. If udisks2 is not present or fails to detect any storage devices, hardinfo will fallback to another method to detect drives. However udisks2 is recommended...

 I have similar case. I will work on this

I have same problem. It seems that the problem is since f6a4f52868c2404f3ad58ef04e513ffe5fa090c7

hello @JGG-Apps In January 2019 my PR #330 has been merged that should fix it. There is no precompiled deb package available right now, but it should be easy to...

@mckaygerhard not it is not requirement, it is optional.

It is used as primary method for detecing storage devices , if udisks2 is not present or fails to detect any drivers, [hardinfo will use fallback methods](https://github.com/lpereira/hardinfo/blob/master/modules/devices.c#L613) to detect storage...

Nice find! What I really don't like is how i-nex is actually [matching](https://github.com/i-nex/I-Nex/blob/master/I-Nex/i-nex/.src/CPU/FCpudb.module#L94) cpu to the database entry. Also keeping the database up-to-date whould be a challenge.

Too bad that wikichip do not contain CPU name string from CPUID. That would be the easiest way how to match cpuid to database entry.

Also I have another idea: I have discovered that CPU-Z TXT report contains useful data, like CPUID family, model, stepping, name string, code name, package, tdp, instructions... We could just...

We could use https://github.com/lm-sensors/lm-sensors/tree/master/configs