From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Giuseppe Bilotta" Subject: Re: [Linux-fbdev-devel] [PATCH] nvidiafb: allow ignoring EDID info Date: Sun, 4 Feb 2007 22:17:08 +0100 Message-ID: References: <20070128160831.fb51347f.akpm@osdl.org> <21d7e9970701281612q56b694edp6efd1a5556dea3fe@mail.gmail.com> <20070128162907.370f5476.akpm@osdl.org> <21d7e9970701281639w57edc2efw4ba620d4c1bdcee7@mail.gmail.com> <20070130203301.GA15067@dreamland.darkstar.lan> <20070204201713.GA12867@dreamland.darkstar.lan> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070204201713.GA12867@dreamland.darkstar.lan> Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-Id: Cc: linux-fbdev-devel@lists.sourceforge.net, Andrew Morton , Dave Airlie , linux-kernel@vger.kernel.org On 2/4/07, Luca Tettamanti wrote: > Giuseppe, can you send me the EDID block of your monitor? I'd gladly do it, if I knew how to retrieve it ... because apparently, get-edid doesn't work, even though both the nv driver for X and nvidiafb manage to retrieve it. This is the output from get-edid """ get-edid: get-edid version 1.4.1 Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 Function supported Call successful VBE version 300 VBE string at 0x11110 "NVidia" 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 does not support 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 Error: output block unchanged """ Anything else I can try? -- Giuseppe "Oblomov" Bilotta