OT: greenish area in new monitor

[Ralf Mardorf]

On Thu, 2 May 2019 10:33:20 +0000, Mike Marchywka wrote:
>Did you try to ask the software what it thought the monitor was?
>Curious if this is a wierd interaction of software with an as yet
>unknown hardware problem. For example, does anyone know how to use
>this? 
>
>get-edid | parse-edid

To me that are "böhmische Dörfer" (it's "double Dutch").

# get-edid | parse-edid

I'm not booted to my Ubuntu install, the output provided by my Arch
Linux install seems to be useless, at least for my LCD display, that
works well for my Ubuntu 16.04, as well as for my Arch Linux install.

The output running from my Arch Linus install is:

[root at archlinux rocketmouse]# get-edid | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
Looks like no busses have an EDID. Sorry!
Attempting to use the classical VBE interface

	Performing real mode VBE call
	Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
	Function supported
	Call successful

	VBE version 300
	VBE string at 0xc98c4 "Intel(R) HSW Mobile/Desktop Graphics Chipset Accelerated VGA BIOS"

VBE/DDC service about to be called
	Report DDC capabilities

	Performing real mode VBE call
	Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
	Function supported
	Call successful

	Monitor and video card combination does not support DDC1 transfers
	Monitor and video card combination supports DDC2 transfers
	0 seconds per 128 byte EDID block transfer
	Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
	Read EDID

	Performing real mode VBE call
	Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
	Function supported
	Call successful

EDID claims 1 more blocks left


*********** Something special has happened!
This happens a lot with TV's, and other devices
with extension blocks. If you have a TV, don't bother.
Odds are good that I2C will work for you. Try 'modprobe i2c-dev'.
Otherwise, please contact the author, Matthew Kern
E-mail: pyrophobicman at gmail.com
Please include full output from this program (especially that to stderr)



Reading next EDID block

VBE/DDC service about to be called
	Read EDID

	Performing real mode VBE call
	Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
	Function supported
	Call successful

EDID claims 1 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Looks like VBE was successful. Have a good day.
Checksum Correct

Section "Monitor"
	Identifier "EV2450"
	ModelName "EV2450"
	VendorName "ENC"
	# Monitor Manufactured week 8 of 2017
	# EDID version 1.3
	# Digital Display
	DisplaySize 530 300
	Gamma 2.20
	Option "DPMS" "true"
	Horizsync 15-68
	VertRefresh 49-61
	# Maximum pixel clock is 150MHz
	#Not giving standard mode: 1280x1024, 60Hz
	#Not giving standard mode: 1680x1050, 60Hz
	#Not giving standard mode: 1600x900, 60Hz
	#Not giving standard mode: 1280x720, 60Hz
	#Not giving standard mode: 1280x800, 60Hz

	#Extension block found. Parsing...
I only know about extension blocks of type 02h. PLEASE email me!
Something strange happened. Please contact the author,
Matthew Kern at <pyrophobicman at gmail.com>

-- 
pacman -Q linux{,-rt{-cornflower,,-pussytoes,-securityink}}|cut -d\  -f2
5.0.10.arch1-1
5.0.10_rt7-0
5.0.7_rt5-1
5.0.3_rt1-0
4.19.37_rt19-0