Your message dated Sat, 15 Feb 2014 10:56:53 +0100 with message-id <CAGnkunfOT=UFhXG=v5ez_uo18g4lnbzjy8+en_7m9gefyxg...@mail.gmail.com> and subject line read-edid: get-edid gets stuck in an infinite loop has caused the Debian Bug report #79900, regarding read-edid: get-edid gets stuck in an infinite loop to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 79900: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=79900 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: read-edid Version: 1.4.0-2 Severity: normal get-edid does the following on my computer: (this goes on forever, just prints more and more information like this, and it prevents xserver-xfree86 from installing) My monitor is Belinea 10 30 40, videocard Riva TNT2 32MB get-edid: get-edid version 1.4.0 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 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 EDID claims 18 more blocks left *********** Something special has happened! Please contact the author, John Fremlin E-mail: one of [email protected],[email protected],[email protected] 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=0x10000 Function supported Call successful EDID claims 38 more blocks left *********** Something special has happened! Please contact the author, John Fremlin E-mail: one of [email protected],[email protected],[email protected] 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=0x10000 Function supported Call successful 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=0x10000 Function supported Call successful 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=0x10000 Function supported Call successful EDID claims 240 more blocks left *********** Something special has happened! Please contact the author, John Fremlin E-mail: one of [email protected],[email protected],[email protected] 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=0x10000 Function supported Call successful 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=0x10000 Function supported Call successful EDID claims 240 more blocks left EDID keeps on claiming same number of blocks left. Corruption? 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=0x10000 Function supported Call successful 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=0x10000 Function supported Call successful 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=0x10000 Function supported Call successful 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=0x10000 Function supported Call successful 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=0x10000 Function supported Call successful 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=0x10000 Function supported Call successful 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=0x10000 Function supported Call successful 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=0x10000 Function supported Call successful 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=0x10000 -- System Information Debian Release: woody Kernel Version: Linux atlas13 2.4.0-test12 #7 Tue Dec 12 16:29:57 CET 2000 i686 unknown Versions of the packages read-edid depends on: ii libc6 2.2-5 GNU C Library: Shared libraries and Timezone
--- End Message ---
--- Begin Message ---This bug is not longer present in 3.X branch, due to the new I2C interface, please update. -- Pozdrawiam, Dariusz Dwornikowski, Assistant Institute of Computing Science, Poznań University of Technology www.cs.put.poznan.pl/ddwornikowski/ room 2.7.2 BTiCW | tel. +48 61 665 29 41
--- End Message ---
