"sudo Xorg -configure" fails on my ThinkPad T510 with error: (EE) intel(0): No kernel modesetting driver detected. So I cannot generate working xorg.conf for further tuning. Although, Xorg works just fine without config file, I think that "Xorg -configure" should work also. It's strange, because i915 module is loaded. I tried to regenerate initramfs with intel_agp and i915 modules included (http://wiki.archlinux.org/index.php/Intel), but it didn't help KMS is enabled in my kernel by default and working. Environment: archlinux i686 current xorg-server 1.8.1.902 xf86-video-intel 2.12.0 intel-dri 7.8.2 kernel26 2.6.34.3 Attached files: * Detailed output of "sudo Xorg -configure" is in xorg_configure.txt * i915 module has been loaded before "Xorg -configure" (see lsmod_grep_i915.txt) * "sudo lspci -vv -nn" output is in lspci_vv_nn.txt * Log of running Xorg (without xorg.conf) is in Xorg.0.log * Parameters passed to my kernel is in menu.lst * kernel info is in uname_a.txt
Created attachment 37911 [details] "lsmod | grep i915" output
Created attachment 37912 [details] "sudo lspci -vv -nn" output
Created attachment 37913 [details] "sudo Xorg -configure" output
Created attachment 37914 [details] Xorg.0.log
Created attachment 37915 [details] menu.lst
Created attachment 37916 [details] "uname -a" output
Have just updated kernel to 2.6.35.2 - didn't help.
commit 8b04b350a983b89eb2d741f55baa297a933ac6ea Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Aug 19 20:05:08 2010 +0100 Open-code DRICreatePCIBusID() During -configure we would attempt to query the availablility of KMS before the DRI module was loaded, thus we were unable to create a valid bus identifier and so the query failed and we disowned the device. Fixes: Bug 29611 - Xorg -configure fails https://bugs.freedesktop.org/show_bug.cgi?id=29611 Reported-by: Sergey Samokhin <prikrutil@gmail.com> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.