Created attachment 598216 [details] Xorg.0.log Description of problem: Always when X is started it produces a black screen with blinking cursor. It is not possible to reset the display and one has to log in via network. Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.12.2-4.fc17.x86_64 xorg-x11-drv-intel-2.19.0-5.fc17.x86_64 How reproducible: Always Steps to Reproduce: 1.Starting X via command line or xdm 2. 3. Actual results: X server starts aborts with the following error X.Org X Server 1.12.2 Release Date: 2012-05-29 X Protocol Version 11, Revision 0 Build Operating System: x86-06 2.6.32-220.17.1.el6.x86_64 Current Operating System: Linux yoda 3.4.4-5.fc17.x86_64 #1 SMP Thu Jul 5 20:20:59 UTC 2012 x86_64 Kernel command line: rd.md.uuid=2072230d:f96fabc5:5994ec5f:b36c46ae rd.lvm=0 root=UUID=7cdec3d3-0ecf-4910-be7d-9506642391a8 KEYTABLE=de-latin1-nodeadkeys SYSFONT=True rd.luks=0 LANG=en_US.UTF-8 ro rd.dm=0 selinux=0 rootfstype=ext4 i915.semaphores=1 Build Date: 26 June 2012 04:32:54AM Build ID: xorg-x11-server 1.12.2-4.fc17 Current version of pixman: 0.24.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 14 06:53:41 2012 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" X: intel_bufmgr_gem.c:2783: drm_intel_bufmgr_gem_init: Assertion `0' failed. Aborted Expected results: X server starts Additional info: Disabling kms allows to start the X server using the VESA driver. However without kms the VT terminals are black. Hardware information: Xeon E3-1275 16 GiB Ram no other graphic card mainboard Asus P8C WS
Created attachment 598217 [details] gdb output with backtrace
Created attachment 598218 [details] video ROM for the chip
Created attachment 598219 [details] opregion data
Created attachment 598222 [details] dmidecode output
The reason why the X server does not start is because libdrm does not know the Ivybridge Server (GT2), which I am using. All Xeon Ivy Bridge having the P4000 are effected by this. The following patch fixes my problem: http://cgit.freedesktop.org/mesa/drm/commit/?id=e057a56448e2e785f74bc13dbd6ead8572ebed91
After upgrading my F17 machine from kernel 3.3.4-5 to 3.4.4-5 I experienced the same problem. Boot screen messages: plymouthd: intel_bufmgr_gen.c:2783: drm_intel_bufmgr_gem_init: Assertion '0'. Cannot open font file True Then nothing further but blank screen with cursor in upper-left corner. Motherboard is Gigabyte GA-Z77X-UDH5 CPU is Xeon E3-1245v2 (Ivy Bridge) Platform is Desktop
Installing libdrm 2.4.37 from bodhi fixed the problem on my F17 machine. .
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.