Testers for inxi/pinxi redone -C CPU logic... huge internal changes

fourtysixandtwo · 02-17-2022, 02:10 PM

Glad I posted the slackbuild then. I was waffling on whether or not to do it, but just goes to show you never know how sharing something useful will spark another idea or pique someones interest to send them down a fruitful path...No matter how small that bit of information was.

It sure makes sense to include it with a script like yours.

h2-1 · 02-17-2022, 03:36 PM

So am I, thanks. I actually hadn't even considered looking at the code before, but your packaging script kind of crammed home the point that I was breaking an inxi rule, to require a non core perl module to do standard functions, so after taking a look at the code, and realizing it was license compatible, and 'just worked', with basically no extra work or modifications beyond wrapping it in a class/package, I figured, why not?

There's 2 methods I'm not using, not a lot of lines of code, but if I don't end up using them, I could remove them for another 34 lines since inxi won't need them. One of them might be worth keeping, check_parsed_edid, but it doesn't do that much of interest.

Based on the cpan Parse::EDID changelog, I'd hazard a guess that when inxi ships with this, the userbase of ParseEDID will jump exponentially, probably. I'll email the maintainer just to let him know.

h2-1 · 02-22-2022, 07:43 PM

And with a faint bang, 3.3.13 is out the door, whew!! hopefully that's the last major feature full refactor/redo for a while now.

Code:

pinxi -Gaz
Graphics:
  Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: XFX Pine
    driver: radeon v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16 ports:
    active: DVI-I-1,VGA-1 empty: HDMI-A-1 bus-ID: 0a:00.0 chip-ID: 1002:68f9
    class-ID: 0300
  Display: x11 server: X.Org v: 1.20.13 compositor: xfwm v: 4.16.1 driver:
    X: loaded: modesetting gpu: radeon display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2560x1024 s-dpi: 96 s-size: 677x270mm (26.7x10.6")
    s-diag: 729mm (28.7")
  Monitor-1: DVI-I-1 pos: primary,left model: Samsung SyncMaster
    serial: <filter> built: 2004 res: 1280x1024 hz: 60 dpi: 96 gamma: 1.2
    size: 338x270mm (13.3x10.6") diag: 433mm (17") ratio: 5:4 modes:
    max: 1280x1024 min: 720x400
  Monitor-2: VGA-1 pos: right model: Dell 1908FP serial: <filter>
    built: 2008 res: 1280x1024 hz: 60 dpi: 86 gamma: 1.4
    size: 376x301mm (14.8x11.9") diag: 482mm (19") ratio: 5:4 modes:
    max: 1280x1024 min: 720x400
  OpenGL:
    renderer: AMD CEDAR (DRM 2.50.0 / 5.14.0-18.1-liquorix-amd64 LLVM 12.0.1)
    v: 3.3 Mesa 21.2.6 compat-v: 3.1 direct render: Yes

The import of Parse::EDID seems to have gone fine, it's been extended to include vendor 'nice' names, but there is no actual single place I could find that matches those 3 letter vendor codes to the vendor name, all the lists I found are incomplete. But it's not bad from what I can see, tested to make sure no regressions on tinycore, on openbsd, ongoing on wayland fedora gnome and manjaro sway, and it seems ok.

mlangdn · 02-23-2022, 05:20 AM

Looks good to me.

Code:

pinxi -Gaz
Graphics:
  Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: PNY driver: nvidia
    v: 510.54 alternate: nvidiafb,nouveau,nvidia_drm pcie: gen: 2 speed: 5 GT/s
    lanes: 4 ports: active: none off: DVI-D-1 empty: HDMI-A-1 bus-ID: 01:00.0
    chip-ID: 10de:1d01 class-ID: 0300
  Display: x11 server: X.Org v: 1.20.14 compositor: kwin_x11 driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 95 s-size: 513x292mm (20.2x11.5")
    s-diag: 590mm (23.2")
  Monitor-1: DVI-D-0 res: 1920x1080 hz: 60 dpi: 96
    size: 510x287mm (20.1x11.3") diag: 585mm (23")
  OpenGL: renderer: NVIDIA GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 510.54
    direct render: Yes

h2-1 · 02-23-2022, 02:07 PM

That looks like it completely failed to get any /sys/class/drm monitor data to me. What is:

ls /sys/class/drm

anything?

And:

inxi -Gaz --dbg 44

which will output anything it found, but to me it looks like no drm data was there. What kind of monitor is it?

To me it looks like you had xrandr installed, which did get some basic monitor info, like the dimensions and hz, and all the /sys based monitor data tests failed.

DVI-D-0 looks like an Xorg monitor ID, changed from a kernel ID of DVI-D-1 (kernel stuff seems consistent and well done, numbering starts at 1, always follows same rules for the id construction). The internal mapping rules should have matched those, unless there's an error in the regex.

mlangdn · 02-24-2022, 04:33 AM

Code:

ls /sys/class/drm
card0  card0-DVI-D-1  card0-HDMI-A-1  renderD128  version

Code:

inxi -Gaz --dbg 44
Graphics:
  Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: PNY driver: nvidia
    v: 510.54 alternate: nvidiafb,nouveau,nvidia_drm bus-ID: 01:00.0
    chip-ID: 10de:1d01 class-ID: 0300
  Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver:
    loaded: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 95 s-size: 513x292mm (20.2x11.5")
    s-diag: 590mm (23.2")
  Monitor-1: DVI-D-0 res: 1920x1080 hz: 60 dpi: 96
    size: 510x287mm (20.1x11.3") diag: 585mm (23")
  OpenGL: renderer: NVIDIA GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 510.54
    direct render: Yes

The monitor is a 23" Samsung SyncMaster 1920x1080

h2-1 · 02-24-2022, 02:29 PM

Oh, you're using inxi, I missed that. pinxi is the one you want, or you can use inxi -U because the changes went live 2 days ago in master branch.

mlangdn · 02-24-2022, 08:19 PM

inxi upgrade in today's changelog.

h2-1 · 02-24-2022, 08:51 PM

Just FYI, there's going to be a 3.3.14 reasonably soon, as soon as I see where the display/monitors stuff is failing, already getting random failures from online posts of inxi -Ga data. This was kind of my plan because I could tell I'd exhausted the variations for monitor stuff more or less among testers and my own stuff, this was immediately confirmed on the first outputs posted yesterday and day before. A few corner cases already handled in pinxi, probably within a few days most will be handled I think. Though there's one I'm going to have to try to get data from the guy, his system simply did not find any monitor data at all, that was an amd radeon apu setup, which I'd wondered about in terms of how they show in the system. Still needs more data though. APU showed as Device-1, so it wasn't that, but don't know what the issue there was.

Still missing any complete source for monitor vendor 3 character code IDs, which means any of the less common monitor code > vendor name matches will have to be done empirically, by the person telling me the brand on their monitor, and the manufacturer_name code id they see in -Ga --dbg 44 output. I think to be complete, somewhat, about 20 more will need to be added, after that it gets really obscure. 10 would probably handle most of the more standard ones people actually use that are still missing.

Redoing the ParseEDID stuff, will contact the guy once I have it more or less done and see if he wants any of the changes.