It really hates it.
Running "sudo get-edid | parse-edid" before trying ddccontrol looks good:
sudo get-edid -b 1 | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
Only trying 1 as per your request.
256-byte EDID successfully retrieved from i2c bus 1
Looks like i2c was successful. Have a good day.
Checksum Correct
Section "Monitor"
Identifier "KOMODO V"
ModelName "KOMODO V"
VendorName "SPT"
# Monitor Manufactured week 22 of 2005
# EDID version 1.3
# Analog Display
Option "SyncOnGreen" "true"
DisplaySize 380 300
Gamma 2.20
Option "DPMS" "true"
Horizsync 24-80
VertRefresh 50-75
# Maximum pixel clock is 140MHz
#Not giving standard mode: 1280x1024, 60Hz
#Not giving standard mode: 1280x960, 60Hz
#Not giving standard mode: 1152x864, 75Hz
#Not giving standard mode: 1024x768, 66Hz
Modeline "Mode 0" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
EndSection
and looking at it with hexdump
sudo get-edid -b 1 | hexdump -C This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 1 as per your request. 256-byte EDID successfully retrieved from i2c bus 1 Looks like i2c was successful. Have a good day. 00000000 00 ff ff ff ff ff ff 00 4e 14 2a 19 af 0a 00 00 |........N.*.....| 00000010 16 0f 01 03 6f 26 1e 78 ea 68 75 a2 5a 49 9f 23 |....o&.x.hu.ZI.#| 00000020 13 50 54 bf ef 80 81 80 81 40 71 4f 61 46 01 01 |.PT......@qOaF..| 00000030 01 01 01 01 01 01 30 2a 00 98 51 00 2a 40 30 70 |......0*..Q.*@0p| 00000040 13 00 78 2d 11 00 00 1e 00 00 00 fd 00 32 4b 18 |..x-.........2K.| 00000050 50 0e 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 |P... .....S| 00000060 63 65 70 74 72 65 20 58 39 47 2d 0a 00 00 00 fc |ceptre X9G-.....| 00000070 00 4b 4f 4d 4f 44 4f 20 56 0a 20 20 20 20 00 bc |.KOMODO V. ..| 00000080 64 00 72 10 d8 da b9 51 73 5e 10 b9 82 90 23 59 |d.r....Qs^....#Y| 00000090 3e 94 48 fc 06 73 9e 34 20 64 8e 00 20 54 0a 96 |>.H..s.4 d.. T..| 000000a0 91 15 04 11 8a 18 c9 01 26 14 81 e3 86 c1 71 18 |........&.....q.| 000000b0 19 21 54 a1 d9 69 9d 20 34 32 d2 87 b8 39 17 18 |.!T..i. 42...9..| 000000c0 9c 1a 8e 07 18 80 25 34 a1 a0 21 d0 42 93 a5 66 |......%4..!.B..f| 000000d0 90 2a 02 00 ec 48 44 b9 74 e6 98 40 61 40 26 3a |.*...HD.t..@a@&:| 000000e0 20 b6 84 8c 2a cc 06 10 68 05 44 20 40 46 09 81 | ...*...h.D @F..| 000000f0 9b f4 ab 5b 28 2c 2d 03 90 b6 36 5a 83 c8 84 93 |...[(,-...6Z....| 00000100
then if I run
sudo ddccontrol -c dev:/dev/i2c-1
I get this:
sudo ddccontrol dev:/dev/i2c-1
ddccontrol version 0.4.2
Copyright 2004-2005 Oleg I. Vdovikin (oleg@cs.msu.su)
Copyright 2004-2006 Nicolas Boichat (nicolas@boichat.ch)
This program comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of this program under the terms of the GNU General Public License.
Reading EDID and initializing DDC/CI at bus dev:/dev/i2c-1...
ioctl(): No such device or address
ioctl returned -1
Reading EDID 0x50 failed.
DDC/CI at dev:/dev/i2c-1 is unusable (-2).
If your graphics card need it, please check all the required kernel modules are loaded (i2c-dev, and your framebuffer driver).
and now the monitor won't respond to any get-edid requests:
sudo get-edid -b 1 | hexdump -C 1 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 1 as per your request. Bus 1 doesn't really have an EDID... Couldn't find an accessible EDID on this bus. 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 0x11100 "Intel(R) Sandybridge/Ivybridge 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 failed The EDID data should not be trusted as the VBE call failed Looks like VBE was successful. Have a good day. 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000080
and if I want to have the EDID working again, I must unplug and plug in the monitor to reset it. Just pressing the power button on the monitor isn't enough since I guess it still has standby power.
No comments:
Post a Comment