Red Hat Bugzilla – Bug 861803
Unable to start xorg with gma500/intel gma3600
Last modified: 2014-05-28 05:41:46 EDT
Description of problem:
Hello, startx and telinit 5 will not start a graphical environment with my "Intel Graphics Media Accelerator 3600"-based netbook (Gateway LT4004u). This is Fedora 18, fully updated.
If I run startx, I can see a backtrace.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Attempt graphical boot or run startx from a terminal
Blank screen for booting into xorg, and a stack trace for startx.
Framebuffer console works properly. The delightful fbida package properly displays images, etc.
00:02.0 VGA compatible controller : Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be1] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device [1025:0624]
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at 46000000 (32-bit, non-prefetchable) [size=1M]
I/O ports at 50d0 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: [d0] Power Management version 2
Capabilities: [b0] Vendor Specific Information: Len=07 <?>
Capabilities:  MSI: Enable+ Count=1/1 Maskable- 64bit-
Kernel driver in use: gma500
Also attaching logs.
Created attachment 619510 [details]
cat dmesg startx Xorg.0.log > combined
Original submission didn't like my pasted logs, attaching instead.
As a quick update, I've updated kernel and xorg packages through the course of F18 to no avail. Nightlie ISO's also don't start xorg.
Some good news: I can now run Fedora 17 fully updated on the same hardware. I may have been bitten by this bug, which is resolved for F17: https://bugzilla.redhat.com/show_bug.cgi?id=849475
It appears xorg-x11-drv-intel-2.20.14-1.fc18.x86_64 may fix my issue. I booted from the live destop beta and updated the package which then allowed me to start xorg. Currently trying xorg-x11-drv-intel-2.20.16-1.fc18.x86_64.
xorg-x11-drv-intel-2.20.16-1.fc18.x86_64 appears fine. Looks like more current versions of the package fix the issue.
Newer versions of the driver fix the issue. Closing.