Error Reading Edid
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Xorg does not see my monitor EDID up vote 0 down vote favorite 1 Below is the output from my Xorg.0. X.Org X Server 1.11.3 Release Date: 2011-12-16 [ 22.311] X Protocol Version 11, Revision 0 [ 22.311] Build Operating System: Linux 2.6.42-23-generic x86_64 Ubuntu [ 22.311] Current Operating System: Linux sean-P55-USB3 3.2.0-34-generic #53-Ubuntu SMP Thu Nov 15 10:48:16 UTC 2012 x86_64 [ 22.311] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-34-generic root=UUID=0a34603e-aee9-44d1-8982-a5a5a38c3e4d ro quiet splash [ 22.311] Build Date: 29 August 2012 12:12:33AM [ 22.311] xorg-server 2:1.11.4-0ubuntu10.8 (For technical support please see http://www.ubuntu.com/support) [ 22.311] Current version of pixman: 0.24.4 [ 22.311] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 22.311] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 22.311] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Nov 17 13:20:45 2012 [ 22.311] (==) Using config file: "/etc/X11/xorg.conf" [ 22.311] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 22.311] (==) No Layout section. Using the first Screen section. [ 22.311] (==) No screen section available. Using defaults. [ 22.311] (**) |-->Screen "Default Screen Section" (0) [ 22.311] (**) | |-->Monitor "
3 posts by MasterOfSmoke » Thu Nov 06, 2014 5:45 pm made a fresh raspbian wheezy i had on my pc (2013-07-26) and now the camera works. I guess the problem is with the OctoPrint distribution... ---- SOLVED ----Hi, i'm having troubles with my rpi cam board. I hadn't used it in a while and now i've installed octopi to the rpi.. All i did was a fresh install, Code: Select allsudo rpi-update
sudo raspi-config
enabled the camera and after the reboot, the camera led is always on and i can't access http://askubuntu.com/questions/218871/xorg-does-not-see-my-monitor-edid the camera. Code: Select allpi@octopi ~ $ raspistill -v -o cam.jpg
raspistill Camera App v1.3.8
Width 2592, Height 1944, quality 85, filename cam.jpg
Time delay 5000, Raw no
Thumbnail enabled Yes, width 64, height 48, quality 35
Link to latest frame enabled no
Full resolution preview No
Capture method : Single capture
Preview Yes, Full screen Yes
Preview window 0,0,1024,768
Opacity 255
https://www.raspberrypi.org/forums/viewtopic.php?t=91002&p=636567 />Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 0, Video Stabilisation No, Exposure compensation 0
Exposure Mode 'auto', AWB Mode 'auto', Image Effect 'none'
Metering Mode 'average', Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
ROI x 0.000000, y 0.000000, w 1.000000 h 1.000000
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
mmal: camera component couldn't be enabled
mmal: main: Failed to create camera component
mmal: Failed to run camera app. Please check for firmware updates
looking at this error on the forums didn't help (tried a few things.. like this one http://www.linuxx.eu/2014/07/mmal-mmalv ... ed-to.html )but i see that people ask for this log: Code: Select allpi@octopi ~ $ sudo vcdbg log msg
000949.880: HDMI:Setting property pixel encoding to Default
000949.904: HDMI:Setting property pixel clock type to PAL
000949.928: HDMI:Setting property content type flag to No data
000949.951: HDMI:Setting property fuzzy format match to enabled
000954.939: gpioman: gpioman_get_pin_num: pin LEDS_RUNNING not defined
000954.963: gpioman: gpioman_get_pin_num: pin LEDS_NAND_ACTIVITY not defined
000954.985: gpioman: gpioman_get_pin_num: pin LEDS_USB_ACTIVITY not defined
000955.007: gpioman: gpioman_get_pin_num: pin LEDS_FATAL_ERROR not defined
000955.027: gpioman: gpioman_get_pin_num: pin LEDS_APP_OK not defined
000955.046: gpioman: gpioman_get_pin
(Extended Display Identification Data) is a technology that allows a monitor to provide information about itself to a computer. The operating system reads this information to find out what resolutions, refresh rates, and so on the monitor supports so https://delightlylinux.wordpress.com/2013/08/23/adventures-in-resolving-missing-edid-monitor-data/ it can automatically configure the display output. This is a good idea when it works, but if the OS cannot read the EDID information from the monitor for whatever reason, your spanking new high-end monitor http://john.fremlin.de/programs/linux/read-edid/old.html will be limited to a low resolution display of limited use. I encountered this situation where the EDID information was missing. Here is what I did to resolve the issue in Linux Mint 15 using error reading Radeon graphics. Update: If the monitor still gives trouble when using modelines generated by cvt or gtf, try using read-edid as described in this article. The Problem I had the chance to use a quality 1920×1080 LCD display, which had three video connections: VGA, HDMI, and DVI. Linux Mint 15 detected and configured the monitor properly when connected to the VGA or HDMI connectors, but not with the DVI. After error reading edid much trial and error, it was determined that EDID information was not being supplied when conencted to the monitor's DVI port. This happened with Ubuntu, Xubuntu, Linux Mint, Windows XP, and Windows 7. The results were consistent, and all of the operating systems detected the DVI connection as a "Generic Display" limited to 640×480, 800×600, or 1024×768 resolutions. The Solution Since Linux (Windows too, but I am resolving this using Linux Mint 15) could not find the EDID information, the solution was to force the resolution. In the end, I modified the /etc/X11/xorg.conf file with a custom Monitor section that provided a Modeline of 1920×1080. The end result looked something like this: Section "Monitor" Identifier "DVI-0" DisplaySize 1920 1080 Option "DPMS" "true" Modeline "1920x1080_60.00" 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -HSync +Vsync EndSection Xorg reads this Modeline upon X initialization and says, "Okay, the DVI port supports this resolution. Let's use it." That's it. Upon restarting X, the problematic monitor automatically switched to full screen 1920×1080 at 60Hz. Even the login GDM screen displayed at the proper resolution. Why This is just a guess, but if X cannot determine what resolutions are supported by the monitor, it limits them to the lowest possible values to
1024*768 mode of my monitor. XFree86 4 (but not version 3) integrates this functionality on some video cards, so read-edid isn't needed then. If you can't find the data to set your monitor up under XFree86, then read-edid is for you; it should auto detect all necessary info and should even provide a few modes with better refresh rates/resolutions than the standard VESA ones. As of now it won't do everything for you; you'll have to edit XF86Config yourself. This read-edid version seems to work for me on my computer, but YMMV. If it screws up your monitor, causes your rich uncle to disinherit you and/or breaks your leg, don't come running to me. Use it at your own risk. It'll only work on relatively new monitors (if your monitor says it supports DDC then there's a good chance); monitors made before 1996 probably won't work with it. Your video card needs to support VBE 2.0 with DDC extension. If read-edid doesn't work and you're sure it's the latest version, please contact me. Questions, comments, suggestions are all welcome! The specifications for the systems used by this program are kept by the VESA people, more or less locked up: access is only to members, and membership is prohibitively expensive for most open-source work. The way that I got them was by begging. A public text seems to have sneaked out since then. Instructions There are two stages: 1) getting the EDID from the hardware, 2) parsing it. Simple recipe Download read-edid.tar.gz the source tarball for x86 linux/DOS. Untar. % tar zxf read-edid-$VERSION.tar.gz Compile. % cd read-edid-$VERSION/ % make Try to read the EDID from the hardware under linux. You must be the superuser (root) because this stage interfaces directly with the hardware, a somewhat risky business. root# make read-edid If everything ran smoothly, a XF86Config style monitor description should have been printed to stdout. You could put it in your XF86Config or use the information to generate more modelines (see XF86Config(5) and the XFree86-Video-Timings-HOWTO). Trouble shooting Technical details get-edid (li