New pinxi/inxi -G/Graphics Upgrade - Testers!

h2-1

Active Member
Joined
Mar 7, 2021
Messages
125
Reaction score
104
Credits
1,858
Any testers willing and able to bang around new pinxi graphics feature, which is closing in on ready for release to next inxi, welcome.

As with the recent CPU full rewrite, this is a full rewrite of most of the graphics logic, mainly to finally add Wayland support, at least the first major steps towards it.

Features a built in EDID parser for monitors (was using the perl module Parse::EDID but it wasn't being packaged consistently by distros, and wasn't in core modules, so I finally decided to just import all the relevant code, and extend it slightly).

If you have pinxi installed, then: pinxi -U
to update to current. If you don't, then: cd /usr/local/bin && sudo wget -O pinxi smxi.org/pinxi && sudo chmod +x pinxi

then: pinxi -Gaz

Features majorly enhanced monitor and monitor position output, much more graphics data out of display, from console or ssh, and more.

Code:
pinxi -Gaz
Graphics:
  Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: XFX Pine
    driver: radeon v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max:
    gen: 2 speed: 5 GT/s 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:
    loaded: modesetting 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

Most of this data will also show for Wayland now, with a few exceptions, because wayland does not have the concept of X 'Screen', there is no 'Screen' line.

I'm particularly interested in obscure monitors, because I have had to build an internal monitor vendor code > vendor nice name data table, and there is simply no complete online documentation of monitor vendor EDID codes, I've found some good lists, and used them, but they are not complete.

pinxi -Ga --dbg 44

will include the full debugger output data for the edid parsing, which will show the monitor code id, and if you tell me the monitor vendor, I can start matching up the names with the codes, assuming anyone has some of the more obscure monitor vendors.

This is one of my test setups for Wayland Sway:

Code:
Graphics:  Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Lenovo driver: i915 v: kernel ports:
             active: LVDS-1,VGA-1 empty: DP-1 bus-ID: 00:02.0 chip-ID: 8086:2a42 class-ID: 0300
           Device-2: Advanced Micro Devices [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] vendor: Lenovo
             driver: radeon v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports: active: none
             empty: DVI-I-1,LVDS-2,VGA-2 bus-ID: 01:00.0 chip-ID: 1002:95c4 class-ID: 0300
           Device-3: Lenovo Integrated Webcam type: USB driver: uvcvideo bus-ID: 1-6:2 chip-ID: 17ef:1004
             class-ID: 0e02 serial: SN0001
           Display: wayland server: Xwayland v: 21.1.4 compositor: sway v: 1.6.1 driver: i915 d-rect: 2560x1024
             display-ID: 1
           Monitor-1: LVDS-1 pos: right model: Lenovo 0x4031 built: 2008 res: 1280x800 hz: 60 dpi: 107 gamma: 1.2
             scale: 1 size: 304x190mm (12x7.5") diag: 358mm (14.1") ratio: 16:10 modes: 1280x800
           Monitor-2: VGA-1 pos: primary,left model: Dell E173FP serial: D542855O2H2L built: 2005 res: 1280x1024
             hz: 60 dpi: 96 gamma: 1.2 scale: 1 size: 338x270mm (13.3x10.6") diag: 433mm (17") ratio: 5:4 modes:
             max: 1280x1024 min: 720x400
           Message: Wayland GBM/EGL data currently not available.
 


Brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
2,583
Reaction score
1,721
Credits
19,379
[email protected]:~$ pinxi -Ga --dbg 44
$VAR1 = {
'EISA_ID' => 'CVT0001',
'checksum' => 137,
'detailed_timings' => [
{
'ModeLine' => '"1920x1080" 138.65 1920 1952 2016 2080 1080 1083 1089 1111 -hsync -vsync',
'ModeLine_comment' => '# Monitor preferred modeline (60.0 Hz vsync, 66.7 kHz hsync, ratio 16/9)',
'digital_composite' => 3,
'horizontal_active' => 1920,
'horizontal_blanking' => 160,
'horizontal_border' => 0,
'horizontal_image_size' => 0,
'horizontal_sync_offset' => 32,
'horizontal_sync_positive' => 0,
'horizontal_sync_pulse_width' => 64,
'interlaced' => 0,
'pixel_clock' => '138.65',
'preferred' => 1,
'stereo' => 0,
'vertical_active' => 1080,
'vertical_blanking' => 31,
'vertical_border' => 0,
'vertical_image_size' => 0,
'vertical_sync_offset' => 3,
'vertical_sync_positive' => 0,
'vertical_sync_pulse_width' => 6
},
{
'ModeLine' => '"1680x1050" 144.24 1680 1760 1912 2240 1050 1053 1059 1089 +hsync -vsync',
'ModeLine_comment' => '# Monitor supported modeline (59.1 Hz vsync, 64.4 kHz hsync, ratio 16/10)',
'digital_composite' => 3,
'horizontal_active' => 1680,
'horizontal_blanking' => 560,
'horizontal_border' => 0,
'horizontal_image_size' => 410,
'horizontal_sync_offset' => 80,
'horizontal_sync_positive' => 1,
'horizontal_sync_pulse_width' => 152,
'interlaced' => 0,
'pixel_clock' => '144.24',
'stereo' => 0,
'vertical_active' => 1050,
'vertical_blanking' => 39,
'vertical_border' => 0,
'vertical_image_size' => 256,
'vertical_sync_offset' => 3,
'vertical_sync_positive' => 0,
'vertical_sync_pulse_width' => 6
}
],
'diagonal_size' => '0',
'edid_revision' => 3,
'edid_version' => 1,
'established_timings' => [
{
'X' => 640,
'Y' => '480',
'vfreq' => 60
},
{
'X' => 640,
'Y' => '480',
'vfreq' => 72
},
{
'X' => 640,
'Y' => '480',
'vfreq' => 75
},
{
'X' => 720,
'Y' => '400',
'vfreq' => '70'
},
{
'X' => 800,
'Y' => '600',
'vfreq' => 56
},
{
'X' => 800,
'Y' => '600',
'vfreq' => 60
},
{
'X' => 800,
'Y' => '600',
'vfreq' => 72
},
{
'X' => 800,
'Y' => '600',
'vfreq' => 75
},
{
'X' => 1024,
'Y' => '768',
'vfreq' => 60
},
{
'X' => 1024,
'Y' => '768',
'vfreq' => 70
},
{
'X' => 1024,
'Y' => '768',
'vfreq' => 75
},
{
'X' => 1280,
'Y' => '1024',
'vfreq' => '75'
}
],
'extension_flag' => 0,
'feature_support' => {
'DPMS_active_off' => 0,
'DPMS_standby' => 1,
'DPMS_suspend' => 0,
'GTF_compliance' => 0,
'has_preferred_timing' => 1,
'rgb' => 0,
'sRGB_compliance' => 0
},
'gamma' => 0,
'manufacturer_name' => 'CVT',
'manufacturer_name_nice' => '',
'max_size_horizontal' => 0,
'max_size_precision' => 'mm',
'max_size_vertical' => 0,
'monitor_details' => '',
'monitor_name' => '1080A',
'product_code' => 1,
'serial_number' => 1,
'standard_timings' => [
{
'X' => 800,
'Y' => '600',
'ratio' => '4/3',
'vfreq' => 70
},
{
'X' => 1024,
'Y' => '768',
'ratio' => '4/3',
'vfreq' => 72
},
{
'X' => 1280,
'Y' => '1024',
'ratio' => '5/4',
'vfreq' => 60
},
{
'X' => 1280,
'Y' => '1024',
'ratio' => '5/4',
'vfreq' => 70
},
{
'X' => 1280,
'Y' => '720',
'ratio' => '16/9',
'vfreq' => 60
},
{
'X' => 1280,
'Y' => '960',
'ratio' => '4/3',
'vfreq' => 75
},
{
'X' => 1280,
'Y' => '720',
'ratio' => '16/9',
'vfreq' => 75
},
{
'X' => 1280,
'Y' => '960',
'ratio' => '4/3',
'vfreq' => 60
}
],
'video_input_definition' => {
'composite_sync' => 0,
'digital' => 0,
'separate_sync' => 0,
'sync_on_green' => 0,
'voltage_level' => 0
},
'week' => 29,
'year' => 2006
};
$VAR1 = {
'DP-1' => {
'drivers' => [
'i915'
],
'enabled' => 'disabled',
'monitor' => 'DP-1',
'path' => '/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1',
'status' => 'disconnected'
},
'HDMI-A-1' => {
'drivers' => [
'i915'
],
'enabled' => 'disabled',
'monitor' => 'HDMI-A-1',
'path' => '/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI-A-1',
'status' => 'disconnected'
},
'VGA-1' => {
'build-date' => 2006,
'drivers' => [
'i915'
],
'enabled' => 'enabled',
'model' => '1080A',
'modes-max' => '1920x1080',
'modes-min' => '720x400',
'monitor' => 'VGA-1',
'path' => '/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1',
'res-x' => 1920,
'res-y' => 1080,
'serial' => '1',
'status' => 'connected'
}
};
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: Hewlett-Packard driver: i915 v: kernel ports: active: VGA-1
empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0412 class-ID: 0300
Device-2: Aveo USB2.0 Camera type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 3-3:4 chip-ID: 1871:0142 class-ID: 0102
Display: x11 server: X.Org v: 1.20.13 driver: loaded: modesetting
unloaded: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: VGA-1 model: 1080A serial: 1 built: 2006 res: 1920x1080 hz: 60
dpi: 119 size: 410x256mm (16.1x10.1") modes: max: 1920x1080 min: 720x400
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2)
v: 4.5 Mesa 21.2.6 compat-v: 3.0 direct render: Yes
[email protected]:~$

Screen brand DGM
 

Brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
2,583
Reaction score
1,721
Credits
19,379
[email protected]:~$ pinxi -Ga --dbg 44
$VAR1 = {
'EISA_ID' => 'INL000a',
'checksum' => 242,
'detailed_timings' => [
{
'ModeLine' => '"1366x768" 67.1 1366 1383 1395 1434 768 771 773 781 -hsync +vsync',
'ModeLine_comment' => '# Monitor preferred modeline (59.9 Hz vsync, 46.8 kHz hsync, ratio 16/9, 100 dpi)',
'digital_composite' => 3,
'horizontal_active' => 1366,
'horizontal_blanking' => 68,
'horizontal_border' => 0,
'horizontal_dpi' => '100.861627906977',
'horizontal_image_size' => 344,
'horizontal_sync_offset' => 17,
'horizontal_sync_positive' => 0,
'horizontal_sync_pulse_width' => 12,
'interlaced' => 0,
'pixel_clock' => '67.1',
'preferred' => 1,
'stereo' => 0,
'vertical_active' => 768,
'vertical_blanking' => 13,
'vertical_border' => 0,
'vertical_dpi' => '100.552577319588',
'vertical_image_size' => 194,
'vertical_sync_offset' => 3,
'vertical_sync_positive' => 1,
'vertical_sync_pulse_width' => 2
},
{
'ModeLine' => '"1366x768" 67.1 1366 1383 1395 1434 768 771 773 781 -hsync +vsync',
'ModeLine_comment' => '# Monitor supported modeline (59.9 Hz vsync, 46.8 kHz hsync, ratio 16/9, 100 dpi)',
'digital_composite' => 3,
'horizontal_active' => 1366,
'horizontal_blanking' => 68,
'horizontal_border' => 0,
'horizontal_dpi' => '100.861627906977',
'horizontal_image_size' => 344,
'horizontal_sync_offset' => 17,
'horizontal_sync_positive' => 0,
'horizontal_sync_pulse_width' => 12,
'interlaced' => 0,
'pixel_clock' => '67.1',
'stereo' => 0,
'vertical_active' => 768,
'vertical_blanking' => 13,
'vertical_border' => 0,
'vertical_dpi' => '100.552577319588',
'vertical_image_size' => 194,
'vertical_sync_offset' => 3,
'vertical_sync_positive' => 1,
'vertical_sync_pulse_width' => 2
}
],
'diagonal_size' => '15.5485395942567',
'edid_revision' => 3,
'edid_version' => 1,
'established_timings' => [],
'extension_flag' => 0,
'feature_support' => {
'DPMS_active_off' => 0,
'DPMS_standby' => 0,
'DPMS_suspend' => 0,
'GTF_compliance' => 0,
'has_preferred_timing' => 1,
'rgb' => 0,
'sRGB_compliance' => 0
},
'gamma' => 120,
'manufacturer_name' => 'INL',
'manufacturer_name_nice' => '',
'max_size_horizontal' => '34.4',
'max_size_precision' => 'mm',
'max_size_vertical' => '19.4',
'monitor_details' => '',
'monitor_text' => [
'1G5D3�156GW01'
],
'product_code' => 10,
'ratio' => '1.77319587628866',
'ratio_name' => '16/9',
'ratio_precision' => 'mm',
'serial_number' => 0,
'standard_timings' => [],
'video_input_definition' => {
'composite_sync' => 0,
'digital' => 1,
'separate_sync' => 0,
'sync_on_green' => 1,
'voltage_level' => 0
},
'week' => 0,
'year' => 2009
};
$VAR1 = {
'DP-1' => {
'drivers' => [
'i915'
],
'enabled' => 'disabled',
'monitor' => 'DP-1',
'path' => '/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1',
'status' => 'disconnected'
},
'LVDS-1' => {
'build-date' => 2009,
'diagonal' => '15.5',
'diagonal-m' => 395,
'dpi' => 101,
'drivers' => [
'i915'
],
'enabled' => 'enabled',
'gamma' => '1.2',
'modes-min-max' => '1366x768',
'monitor' => 'LVDS-1',
'path' => '/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1',
'ratio' => '16:9',
'res-x' => 1366,
'res-y' => 768,
'size-x' => 344,
'size-x-i' => '13.5',
'size-y' => 194,
'size-y-i' => '7.6',
'status' => 'connected'
},
'VGA-1' => {
'drivers' => [
'i915'
],
'enabled' => 'disabled',
'monitor' => 'VGA-1',
'path' => '/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1',
'status' => 'disconnected'
}
};
Graphics:
Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Dell
driver: i915 v: kernel ports: active: LVDS-1 empty: DP-1,VGA-1
bus-ID: 00:02.0 chip-ID: 8086:2a42 class-ID: 0300
Device-2: Ricoh Integrated Webcam type: USB driver: uvcvideo
bus-ID: 1-6:3 chip-ID: 05ca:180a class-ID: 0e02
Display: x11 server: X.Org v: 1.20.13 driver: loaded: modesetting
unloaded: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0")
s-diag: 414mm (16.3")
Monitor-1: LVDS-1 built: 2009 res: 1366x768 hz: 60 dpi: 101 gamma: 1.2
size: 344x194mm (13.5x7.6") diag: 395mm (15.5") ratio: 16:9 modes: 1366x768
OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express (CTG)
v: 2.1 Mesa 21.2.6 direct render: Yes
[email protected]:~$
 

craigevil

Well-Known Member
Joined
Feb 24, 2021
Messages
361
Reaction score
362
Credits
2,494
$ pinxi -Gaz
Code:
Graphics:
  Device-1: bcm2711-hdmi0 driver: vc4_hdmi v: N/A bus-ID: N/A
    chip-ID: brcm:fef00700 class-ID: hdmi
  Device-2: bcm2711-hdmi1 driver: vc4_hdmi v: N/A bus-ID: N/A
    chip-ID: brcm:fef05700 class-ID: hdmi
  Device-3: bcm2711-vc5 driver: vc4_drm v: N/A bus-ID: N/A
    chip-ID: brcm:gpu class-ID: gpu
  Display: x11 server: X.Org v: 1.21.1.3 compositor: marco v: 1.26.0
    driver: loaded: modesetting unloaded: fbdev display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
    s-diag: 582mm (22.9")
  Monitor-1: HDMI-1 mapped: HDMI-A-1 model: Sceptre T27 built: 2020
    res: 1920x1080 hz: 60 dpi: 81 gamma: 1.2 size: 600x330mm (23.6x13.0")
    diag: 685mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  OpenGL: renderer: V3D 4.2 v: 2.1 Mesa 21.3.5 direct render: Yes
 

captain-sensible

Well-Known Member
Joined
Jun 14, 2019
Messages
2,808
Reaction score
1,900
Credits
17,294
pixi -Gaz on Arch 5.16.10-arch1-1
 

Attachments

  • pinxi.txt
    840 bytes · Views: 92
OP
H

h2-1

Active Member
Joined
Mar 7, 2021
Messages
125
Reaction score
104
Credits
1,858
brickwizard, thanks, you seem to have monitors specifically designed to make the new logic fail!! ideal, great.

Code:
'manufacturer_name' => 'CVT',
'manufacturer_name_nice' => '',
'max_size_horizontal' => 0,
'max_size_precision' => 'mm',
'max_size_vertical' => 0,
'monitor_details' => '',
'monitor_name' => '1080A',

This is now updated, CVT == DGM, updated in pinxi.

Code:
'manufacturer_name' => 'INL',
'manufacturer_name_nice' => '',
'max_size_horizontal' => '34.4',
'max_size_precision' => 'mm',
'max_size_vertical' => '19.4',
'monitor_details' => '',
'monitor_text' => [
'1G5D3�156GW01'
],

What is the monitor brand there?

I'd debated trying to use the monitor_text as a fallback, but also notice it contains some non regular characters, which I've also seen before myself. I have to look at the code and see what monitor_text actually refers to, can you tell from the monitor if any part of that matches the model number/id?

captainsensible, without the --dbg 44 I can't see what happened there on yours, it got no monitor brand / vendor data. What brand is the monitor, with the --dbg 44 data I can match that to the code ID.

I can see already one thing I can enhance however, if I get a 'nice' monitor vendor name, and no model, it should still show something, so I'll fix that.

I'll see if I can dig up anything about what monitor_text actually means

The docs on edid say that monitor_name isn't supposed to be empty, but above examples show that it sometimes is
 
Last edited:

Brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
2,583
Reaction score
1,721
Credits
19,379
I thought I would send you the full reports, saves having to do it again, I still have the old zg5 to do, I have no longer got the 21 yr old travel mate
 

Brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
2,583
Reaction score
1,721
Credits
19,379
What is the monitor brand there?
The second is the dell lappy, I have no idea who makes their screens

oh, and the model number of the DGM is L-2266WD
 
Last edited:

Brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
2,583
Reaction score
1,721
Credits
19,379
I changed the OS on the ZG5 since the last test, to 32bit Debian it will not let me install pinxi, may have to try a different distro live later.
 

Brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
2,583
Reaction score
1,721
Credits
19,379
finally the full report on the acer ZG5
[email protected] ~ $ pinxi -Ga --dbg 44
$VAR1 = {
'EISA_ID' => 'AUO11c2',
'checksum' => 88,
'detailed_timings' => [
{
'ModeLine' => '"1024x600" 50.4 1024 1048 1184 1344 600 603 604 625 -hsync -vsync',
'ModeLine_comment' => '# Monitor preferred modeline (60.0 Hz vsync, 37.5 kHz hsync, ratio 1.71, 133 dpi)',
'digital_composite' => 3,
'horizontal_active' => 1024,
'horizontal_blanking' => 320,
'horizontal_border' => 0,
'horizontal_dpi' => '133.382564102564',
'horizontal_image_size' => 195,
'horizontal_sync_offset' => 24,
'horizontal_sync_positive' => 0,
'horizontal_sync_pulse_width' => 136,
'interlaced' => 0,
'pixel_clock' => '50.4',
'preferred' => 1,
'stereo' => 0,
'vertical_active' => 600,
'vertical_blanking' => 25,
'vertical_border' => 0,
'vertical_dpi' => '134.867256637168',
'vertical_image_size' => 113,
'vertical_sync_offset' => 3,
'vertical_sync_positive' => 0,
'vertical_sync_pulse_width' => 1
}
],
'diagonal_size' => '8.87304104925222',
'edid_revision' => 3,
'edid_version' => 1,
'established_timings' => [],
'extension_flag' => 0,
'feature_support' => {
'DPMS_active_off' => 0,
'DPMS_standby' => 0,
'DPMS_suspend' => 0,
'GTF_compliance' => 0,
'has_preferred_timing' => 1,
'rgb' => 0,
'sRGB_compliance' => 0
},
'gamma' => 120,
'manufacturer_name' => 'AUO',
'manufacturer_name_nice' => 'AU Optronics',
'manufacturer_specified_range_timing' => {
'horizontal_back_porch_max' => 0,
'horizontal_back_porch_min' => 0,
'horizontal_blanking_max' => 0,
'horizontal_blanking_min' => 0,
'horizontal_max' => 49,
'horizontal_sync_pulse_width_max' => 0,
'horizontal_sync_pulse_width_min' => 0,
'module_revision' => 32,
'vertical_back_porch_max' => 0,
'vertical_back_porch_min' => 0,
'vertical_blanking_max' => 0,
'vertical_blanking_min' => 0,
'vertical_max' => 82,
'vertical_sync_pulse_width_max' => 0,
'vertical_sync_pulse_width_min' => 0
},
'max_size_horizontal' => '19.5',
'max_size_precision' => 'mm',
'max_size_vertical' => '11.3',
'monitor_details' => '',
'monitor_text' => [
'AUO',
'B089AW01 V1'
],
'product_code' => 4546,
'ratio' => '1.72566371681416',
'ratio_name' => '16/9',
'ratio_precision' => 'mm',
'serial_number' => 0,
'standard_timings' => [],
'video_input_definition' => {
'composite_sync' => 0,
'digital' => 1,
'separate_sync' => 0,
'sync_on_green' => 0,
'voltage_level' => 0
},
'week' => 1,
'year' => 2008
};
$VAR1 = {
'LVDS-1' => {
'build-date' => 2008,
'diagonal' => '8.9',
'diagonal-m' => 225,
'dpi' => 133,
'drivers' => [
'i915'
],
'enabled' => 'enabled',
'gamma' => '1.2',
'modes-min-max' => '1024x600',
'monitor' => 'LVDS-1',
'path' => '/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1',
'ratio' => '16:9',
'res-x' => 1024,
'res-y' => 600,
'size-x' => 195,
'size-x-i' => '7.7',
'size-y' => 113,
'size-y-i' => '4.4',
'status' => 'connected'
},
'VGA-1' => {
'drivers' => [
'i915'
],
'enabled' => 'disabled',
'monitor' => 'VGA-1',
'path' => '/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1',
'status' => 'disconnected'
}
};
Graphics:
Device-1: Intel Mobile 945GSE Express Integrated Graphics
vendor: Acer Incorporated ALI driver: i915 v: kernel alternate: intelfb
ports: active: LVDS-1 empty: VGA-1 bus-ID: 00:02.0 chip-ID: 8086:27ae
class-ID: 0300
Device-2: Suyin Acer CrystalEye Webcam type: USB driver: uvcvideo
bus-ID: 1-5:3 chip-ID: 064e:d101 class-ID: 0e02
serial: CN0316-M608-OV01-VA-R02.00.00
Display: x11 server: X.Org v: 1.20.4 compositor: xfwm v: 4.12.5 driver:
loaded: intel unloaded: fbdev,modesetting,vesa display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1024x600 s-dpi: 96 s-size: 270x158mm (10.6x6.2")
s-diag: 313mm (12.3")
Monitor-1: LVDS1 mapped: LVDS-1 built: 2008 res: 1024x600 hz: 60 dpi: 130
gamma: 1.2 size: 200x110mm (7.9x4.3") diag: 225mm (8.9") ratio: 16:9
modes: 1024x600
OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 v: 1.4 Mesa 19.0.8
direct render: Yes
 
OP
H

h2-1

Active Member
Joined
Mar 7, 2021
Messages
125
Reaction score
104
Credits
1,858
This seems to confirm, I need to add a fallback case, while the specs said monitor_name is required field, apparently it's not being used always, so I'll add in a dual test, if name or vendor nice name, then....
monitor_text' => [
'AUO',
'B089AW01 V1'
],
That value unfortunately cannot be relied on, it seems quite random as to how it is populated, in this case, it's vendor code as item 1, probably monitor model as item 2, but I've seen others that did not use this structure, I suspect this is something that is left up to the vendor to complete, and also there's sometimes non printing ascii characters in there, so I'll have to leave that one alone as a data source.

This is in latest pinxi now, the one or both test for vendor nice name and monitor name.
 
OP
H

h2-1

Active Member
Joined
Mar 7, 2021
Messages
125
Reaction score
104
Credits
1,858
And with that, inxi 3.3.13 is out the door. It's going to have holes in it for sure, particularly around getting matching monitor vendor 3 letter codes to vendor actual names, due to there being no complete online list I could find for monitor vendors.
 

captain-sensible

Well-Known Member
Joined
Jun 14, 2019
Messages
2,808
Reaction score
1,900
Credits
17,294
For Arch i've got a simple PKGBUILD file working for pinxi which it installs it "the Arch way" which means you can easily uninstall it the Arch way if anyone wants it. It goes to
Code:
 [[email protected]:~]$ which pinxi                                          (04-01 18:10)
/usr/bin/pinxi
[[email protected]:~]$


@h2-1 pinxi has either disappeared from https://aur.archlinux.org/ or was never there in the first place- any use or interest to submit to AUR ?
 

Brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
2,583
Reaction score
1,721
Credits
19,379
This from inxi
Arch Linux: inxi is in either in the Community Repos or in AUR (it varies year to year), so just install inxi as you normally would any other package. It's usually reasonably current.
 
OP
H

h2-1

Active Member
Joined
Mar 7, 2021
Messages
125
Reaction score
104
Credits
1,858

captain-sensible

I always thought the AUR packaging of pinxi was one of the sillier exercises in pointlessness I've come across. While yes, it will be packaged 'the arch way', if you install it the 'inxi/pinxi' way, you never have depend on a flakey AUR package or packager, and it will always 'just work'. pinxi is the first thing I install on any system, vm, etc, often I don't even bother with inxi, which is the 'old' branch of pinxi in a sense, the only thing I use inxi for is to verify that I didn't do any copy/paste errors when creating next inxi from pinxi, and that the output is correct in terms of changed features and indentation levels and so on.

With this said, there is of course the advantage that if the package is correctly made, and correctly installs pinxi and the man page, and correctly always just updates to current pinxi from github, and doesn't require any packager manual intervention to update pinxi version, if all those things are done correctly, then you have automated:
Code:
sudo pinxi -U --man
which means you'll always have the current github pinxi, which does have some utility. However, to reiterate what is hopefully obvious, I don't want to get 'bug reports' from pinxi unless the person understands what pinxi is, that it might get new features, drop them, have bugs, etc, by definition, so unless you are actively following some part of pinxi development and understand what is being done, and roughly why, user feedback is not desired at all, it's a negative to me, with the exception of people actively involved in helping and testing and who understand what that means.

pinxi was definitely in AUR, it's something I found so odd that it struck me quite distinctly, so it's not something I'd forget.

For smart non script kiddie users who are active helpers however using straight git pinxi is going to be much more useful since why bother running all of the AUR package manager to update 1 or 2 files? That's kind of silly to me. Note that if the pinxi package does anything other than just grab the latest pinxi file from github every time you do an update, then it's a huge negative, and the package should be deleted because it then becomes a massive liability, the last thing in the world anyone should run is a non current pinxi, that's in the realm of counterproductive pointlessness.

Despite all this, one of my favorite things as the inxi developer is good competent users who provide good competent feedback or ideas based on running pinxi, and who are somewhat involved at some level and understand what the stuff is, how to submit debugger datasets,etc. The WORST thing I know of with inxi development is people asking for help/assistance with issues and not submitting the debugger data, that's a huge waste of my time, and for some distros, particularly but not limited to FreeBSD, I won't even talk to a user of that distro anymore if they don't supply the data, I will close the issue, that's from them having repeatedly wasted my time with stupid pointless incompetent bug or issue reports then not supplying the data I need to resolve it, expecting that I have any interest in their niche vanity project distro.

Yes, I wish I had more help, no, I don't expect to get it on any consistent basis, yes, pinxi is the tool you need to use to provide that help, and no, I do not want people who don't understand what it is to be using it.

Keep in mind the 'real' pinxi way, which is this:

Code:
cd /usr/local/bin
sudo wget -O pinxi smxi.org/pinxi
sudo chmod +x pinxi
sudo pinxi -U --man # to install the man page, if you want it, the man is also not stable
sudo chown [yourUserName]:[yourUserName] pinxi

then always, as regular user:
Code:
pinxi -U

This is what I always do, that way, when I access to a system, a vm, whatever, all I have to do is: pinxi -U to update, irrelevant the os, distro, whatever, it will always work, don't have to think what package manager it is, whatever, then I do my testing.

There's also pinxi -U 3 which is used heavily under very active development of advanced complicated features, I use that to update my server pinxi which is what -U 3 grabs, which bypasses all the throttles and limits that github imposes, and allows me to update the server file in about 1 second as I develop and test new features. -U 3 breaks a lot though when active development is ongoing since I don't do any attempt to actually have it be anything but a development tool, it will sometimes spray out debugger data I need to test or develop something, sometimes not, once -U 3 server is stable, I will send it to pinxi, and once all the features in pinxi are stable enough for next inxi, I will make next inxi, then the cycle starts all over again.

By far the best thing anyone can do is simply get to know inxi output really well, then test always with current pinxi, and report issues or failures if they find them.

Right now I'm going into 'take a break from massive inxi development' cycle, or at least, lol, I will try, and am going to rely, or try to rely, for a while, on user issues and feedback, plus of course spotting bugs and things that need fixes from online output.

Latest thing I saw was that in some rare cases, lm-sensors is failing to divide the temp by 100 so I saw a cpu temp of 6401.2 C, I'll be adding in a sensors feature that will fix obvious gross errors like that.
 
Last edited:

captain-sensible

Well-Known Member
Joined
Jun 14, 2019
Messages
2,808
Reaction score
1,900
Credits
17,294
a short no would have done it for me ...but "exercises in pointlessness" thats what i live for
 
Last edited:
OP
H

h2-1

Active Member
Joined
Mar 7, 2021
Messages
125
Reaction score
104
Credits
1,858
With all this said, I would imagine it could be kind of entertaining to watch a new feature, like the recent -G / Monitor / EDID (--edid) updates slowly, or rapidly, evolve in pinxi, until they get put into next inxi, and it all starts over again.
 
OP
H

h2-1

Active Member
Joined
Mar 7, 2021
Messages
125
Reaction score
104
Credits
1,858
No doesn't communicate any information, with something like pinxi, basically nobody who doesn't want to read an explanation like that should be really using it. Or packaging it. However, I do encourage motivated users to run it by default, because those are the best issue/bug reports I get, by far. On github, the best way for a user to get my attention is for them to have read the readme, and filed the issue using latest pinxi, that way I know they are reading the directions.

Arch users in general I don't hear from much on the organization side of things anymore, that is, the packagers, the forum mods, those people, most of the stuff I get feedback on now comes from Manjaro, Garuda, and EndeavorOS,
 
Last edited:

Brickwizard

Well-Known Member
Joined
Apr 28, 2021
Messages
2,583
Reaction score
1,721
Credits
19,379
It seems to be taking a while for the upgrades to make it into the distribution packages, the latest mint is still only on 3.0.38
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Members online


Top