MX Linux Forum

Note, pinxi 3.0.38-11 has a test case for video/tv/television card detection, I believe those are coming in as multimedia type, but multimedia is always as far as I know audio, but it is not always video, so I can't use that one, most sound cards are type 0400 for example, but adding the string dete...

lspci -knnv then locate the block that is the video device, and paste it here. inxi checks for type [03..] for video / graphic card by default. pinxi -G --dbg 4 will show what it believes each pci device to be, that's the first item in each set of values. This is the most surefire way to see if supp...

Well, since I have time on my hands, and because of a recent github inxi issues filed, I've discovered that inxi has been using the wrong, sometimes, Xorg.0.log file, or not finding one at all, depending on the system. The main change, which I was not aware of, was moving /var/log/Xorg.0.log to ~/.l...

Yes, looks like it, I added a detection rule for that specific instance since i've seen it now more than once. Probably because I never tested the 'family' item in smartctl before, which has slightly different syntaxes than the model items. I've just put up a revised version, it includes non handled...

Oh, that explains it: Seagate Samsung SpinPoint M8 (AF) The vendor grabber strips out the first found vendor, samsung in this case, then exits the loop, since they are very expensive tests, and it found it. I'll add that case to the cleaner though. I didn't know seagate and samsung had any kind of a...

Hmm, that's odd, it should have stripped out the redundant 'seagate' in the model family: Can you post the --dbg 12 part, it looks like your values there are worth looking at. I still don't have a great sense of when pinxi/inxi should show users Old-Age or Pre-fail info items, that looks like it wil...

Good examples, thanks. I'm still tweaking the thresholds for when to show items, I'm varying between THRESHOLD being 25% to 60% of VALUE, depending on the data I'm seeing in various drives. The goal is to show the items before they are at the failed state re VALUE <= THRESHOLD, but it's a learning c...

Your case and I think nvme in general should be handled now in 3.0.37-25 - tested on other nvme's by trimming off the n1 and they worked fine. Added more error cases, most of interest is actually failing drives. Much improved Pre-Fail handlers, and may add a generalized pre-fail test as a fallback f...

Oh, I wonder if your m2 nvme is the difference there, that's strange, I'll have to test trimming off the n1 on others and see what happens.

Can you show the results for: smartctl -AHi /dev/nvme0

that's the command pinxi is using internally.

Hmm, the first exception, that didn't take long. So far the other nvme I have tested on gave their report with nvme0n1 type ID. I'll have to test them to see if they keep giving it if I trim off the n1 ending. I've modified the Old-Age and Pre-Fail outputs to be more coherent, was using the raw valu...