Hello,

Am Mittwoch, 3. Juni 2015 schrieb Ladislav Slezak:
> I have reimplemented monitor detection in hwinfo to read the data from
> /sys instead of running BIOS emulation and reading the data from the
> VESA BIOS. This should work better and should be more reliable.

> The new version prints some additional properties (monitor manufacture
> date), so there should be at least a little change in the output...
> 
> Of course, reporting success or improvements here is also appreciated
> ;-)

I installed the 13.2 package on Tumbleweed, because hwinfo 21.13 didn't 
make it into Tumbleweed yet. 

Oh, and the 21.14 package in system:install:head/hwinfo has a 0 byte 
tarball :-/


On my laptop (with an additional external monitor attached), I get

--- monitor1.log        2015-06-06 15:53:24.036726348 +0200
+++ monitor2.log        2015-06-06 15:59:25.362474177 +0200
@@ -1,6 +1,7 @@
-33: None 00.0: 10000 Monitor
-  [Created at monitor.95]
+26: None 00.0: 10000 Monitor
+  [Created at monitor.125]
   Unique ID: rdCR.+Gf2yBtn0F1
+  Parent ID: VCu0._YOiuWv5Ly7
   Hardware Class: monitor
   Model: "BenQ GL2450H"
   Vendor: BNQ 
@@ -20,6 +21,8 @@
   Resolution: 1600x900@60Hz
   Resolution: 1920x1080@60Hz
   Size: 531x298 mm
+  Year of Manufacture: 2014
+  Week of Manufacture: 33
   Detailed Timings #0:
      Resolution: 1920x1080
      Horizontal: 1920 2008 2052 2200 (+88 +132 +280) +hsync
@@ -31,19 +34,24 @@
     Hor. Sync Range: 30-83 kHz
     Bandwidth: 148 MHz
   Config Status: cfg=new, avail=yes, need=no, active=unknown
+  Attached to: #20 (VGA compatible controller)
 
-34: None 00.2: 10002 LCD Monitor
-  [Created at monitor.95]
-  Unique ID: aHB6.TXuwCXVLBM9
+27: None 01.0: 10002 LCD Monitor
+  [Created at monitor.125]
+  Unique ID: wkFv.TXuwCXVLBM9
+  Parent ID: VCu0._YOiuWv5Ly7
   Hardware Class: monitor
   Model: "X176G LCD Monitor"
   Vendor: LPL "X176G"
   Device: eisa 0x0000 
   Resolution: 1440x900@60Hz
   Size: 367x230 mm
+  Year of Manufacture: 2007
+  Week of Manufacture: 0
   Detailed Timings #0:
      Resolution: 1440x900
      Horizontal: 1440 1520 1568 1968 (+80 +128 +528) -hsync
        Vertical:  900  901  904  914 (+1 +4 +14) -vsync
     Frequencies: 108.00 MHz, 54.88 kHz, 60.04 Hz
   Config Status: cfg=new, avail=yes, need=no, active=unknown
+  Attached to: #20 (VGA compatible controller)

I'm slightly surprised that I get a different Unique ID for the laptop 
display - you should know better if this is intentional.

The full hwinfo output has some more differences. Just as an example:

 >> misc.1.2: open parallel
------ exec: "/sbin/modprobe parport " -----
+----- exec: "/sbin/rmmod lp" -----
+----- return code: ? -----
+----- exec: "/sbin/rmmod parport_pc" -----
+----- return code: ? -----
+----- exec: "/sbin/rmmod parport" -----
+  rmmod: ERROR: Module parport is in use by: ppdev
 ----- return code: ? -----

Maybe you need to rmmod ppdev first?

Needless to say that my laptop doesn't have a parport ;-)


If you are interested in the full hwinfo output (from 21.12. and 21.13), 
take a look at www.cboltz.de/tmp/dl/hwinfo-logs.tar.gz


Regards,

Christian Boltz
-- 
Also, monolithisch im Sinne von "das macht einfach alles und streichelt
auch noch die Katze", nicht im Sinne von einem großen Code Blob.
[Andreas Scherbaum über systemd auf
https://plus.google.com/117024231055768477646/posts/7tJUsZidkr6]

-- 
To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org
To contact the owner, e-mail: yast-devel+owner@opensuse.org