I tried updating to the driver you specified (Actually, I went to 2.10.902). I still can't start X, I get: (EE) intel(0): No kernel modesetting driver detected. (EE) Screen(s) found, but none have a usable configuration. I have checked dmesg, doesn't appear to be anything interesting there. In the interest of confirming that I have a proper configuration, I changed " Driver "Intel" " to " Driver "vesa" " temporarily, X started up (thought without decorations, I didn't really bother to look into that). I am currently using the uvesafb framebuffer driver, but as soon as the i915 module loads it enables modesetting and my display goes blank. <div class="gmail_quote">On Wed, Mar 17, 2010 at 2:15 PM, Haroldo Stenger <<a href="mailto:haroldo.stenger@gmail.com">haroldo.stenger@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Scott, Having fighted 48 hours in a row with a very similar configuration, I'd tell you my tips: At a point in the configuration-changes line , I had xf86-video-intel-2.10.0 installed , and X did not start , but show a lot of errors. I upgraded to 2.10.901 , and X started. There was an EDID checksum problem in dmesg trail , but that did not disappear, however, X started working as I said. The other problem I was fighting , was that I I attached a LCD monitor, then ctrl alt f1 gave me a "out of range" error. That was because comething in the KMS thing was not acknowledgeing any of the /etc/fb.modes settings. If I typed "fbset" to obtain info, the timings appeared all in 0. Then I discovered a very magical thing , that enabled VGA , while keeping KMS , aparently with framebuffer console (fbcon). You have to put as a boot parameter in lilo or grub an item that reads like : video="VGA-1:1024x768" I also tried video="VGA-1:1024x768@72" and then I could use the LCD monitor again. The problem wasn't one if I used a CRT monitor, since it supported the misterious horiz freq KMS was trying to render. let me know. haroldo 2010/3/17 Scott Silverman <<a href="mailto:ssilverman@simplexinvestments.com">ssilverman@simplexinvestments.com</a>>: <div><div></div><div class="h5">> The fbcon driver is built-in to my kernel, which it seems was not the case > for your issue. I have looked through the vesafb and uvesafb documentation > from the kernel, but it is not clear to me how I would use this to configure > my framebuffer. > > What I do now is pass vga=773 as a kernel arg in grub, which along with > "nomodesetting" gets me a usable console, but I can not start X with that > configuration, even disregarding my other X issues. > > 2010/3/17 Andre Müller <<a href="mailto:andremuellerster@gmail.com">andremuellerster@gmail.com</a>> >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 03/17/10 17:44, Scott Silverman wrote: >> > I have an IBM Thinkpad X30 with the Intel Corporation 82830 CGC [Chipset >> > Graphics Controller] (rev 04). >> > >> > I am trying to install X with Arch Linux (kernel 2.6.32). I have the >> > xf86-video-intel v2.10.0-1. >> > >> > First, without X installed/running, if I boot the machine normally I get >> > nothing but a blank screen. Same if I set "i915.modeset=1". >> > Alternatively, >> > if i use the "nomodesetting" kernel argument I can properly boot and use >> > the >> > console. >> > >> > Output of dmesg when booted with i915.modeset=1: >> > <a href="http://paste.pocoo.org/show/190811/" target="_blank">http://paste.pocoo.org/show/190811/</a> >> > >> > Xorg.0.log when started (via ssh) with i915.modeset=1: >> > <a href="http://paste.pocoo.org/show/190807/" target="_blank">http://paste.pocoo.org/show/190807/</a> >> > >> > >> > How can I configure my kernel/xorg so that I can boot and see my >> > console, >> > and also have the ability to start X? >> > >> It may be the problem I once had as well... >> >> You need to make shure the framebuffer is enabled and loaded as >> well (that needs the framebuffer config option but do NOT select >> any of the framebuffers). >> >> The grory details are in >> <a href="http://bugs.freedesktop.org/show_bug.cgi?id=22674" target="_blank">http://bugs.freedesktop.org/show_bug.cgi?id=22674</a> >> and somewhere on this ML. >> >> Best >> Andre >> >> > >> > >> > >> > _______________________________________________ >> > Intel-gfx mailing list >> > <a href="mailto:Intel-gfx@lists.freedesktop.org">Intel-gfx@lists.freedesktop.org</a> >> > <a href="http://lists.freedesktop.org/mailman/listinfo/intel-gfx" target="_blank">http://lists.freedesktop.org/mailman/listinfo/intel-gfx</a> >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.14 (GNU/Linux) >> Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a> >> >> iEYEARECAAYFAkuhF9kACgkQhYOgL/M0VS2DBQCeNhO3meWU7s2PwVm0vAlnTgLh >> tI8AnRRusmYC9d0xDai3OIFkjhnnUIYb >> =ZnjD >> -----END PGP SIGNATURE----- > > > _______________________________________________ > Intel-gfx mailing list > <a href="mailto:Intel-gfx@lists.freedesktop.org">Intel-gfx@lists.freedesktop.org</a> > <a href="http://lists.freedesktop.org/mailman/listinfo/intel-gfx" target="_blank">http://lists.freedesktop.org/mailman/listinfo/intel-gfx</a> > > </div></div></blockquote></div>