Created attachment 26151 [details] Xorg.0.log after a failed start System environment: -- chipset: G965 -- system architecture: x86_64 -- xf86-video-intel: 2.7.1 -- xserver: Server 1.6.1.901 -- mesa: 7.5_rc2 -- libdrm: 2.4.11 -- kernel: 2.6.29-gentoo-r4 -- Linux distribution: Gentoo -- Machine or mobo model: Intel DG965SS -- Display connector: VGA/DE-15 When using KMS, X will start. When deactivating KMS in the Kernel (CONFIG_DRM_I915_KMS=n) and leaving everything else as is, X does not start. I tried to bisect this one, but with my current configuration I did not find a working state.
Created attachment 26152 [details] xorg.conf
Created attachment 26153 [details] dmesg
Created attachment 26154 [details] Xorg.0.log after the second failed start The content of Xorg.0.log changes slightly with the second try (but does not change any more after the second try).
Looks like your non-KMS kernel config is missing AGP support somehow. Try removing FB_INTEL from your config and looking into the AGP failure.
Any update here?
I just made some tests without KMS and current master of xf86-video-intel: 1. boot 2. load intelfb 3. run X does not work, AGP failure 1. boot 2. run X works fine 1. boot 2. run X 3. stop X 4. load intelfb 5. run X does not work, AGP failure 1. boot 2. run X 3. load intelfb bad crash of X 1. boot 2. load intelfb 3. unload intelfb 4. run X does not work, AGP failure So the problem occurs if and only if intelfb has been loaded before or is being loaded while X is running. It does not matter if intelfb will be unloaded again. Where exactly do I find more useful information?
Yeah, don't load intelfb. It's a special purpose driver that won't work in most cases. It's also superceded by the i915 KMS driver (and if you're not using that vesafb is probably a better way to get a fb console anyway). Again, don't ever load intelfb. Just disable it in your config. I'll send a patch to make it conflict with the i915 driver since they should never be used together.
(In reply to comment #7) > Yeah, don't load intelfb. It's a special purpose driver that won't work in > most cases. It's also superceded by the i915 KMS driver (and if you're not > using that vesafb is probably a better way to get a fb console anyway). The reason that I used intelfb in the first place was that I thought it is mandatory for using KMS. I was not aware of the fact that the KMS driver itself makes all the fb stuff (actually it is pretty obvious, but I am stupid :)). > Again, don't ever load intelfb. Just disable it in your config. I'll send a > patch to make it conflict with the i915 driver since they should never be used > together. Could also be good enough for marking as FIXED. Anyway, there is one aspect remaining: unloading intelfb does not help using the KMS driver. Is there a way to make this possible? Or is a reboot the only way?
Yeah, I'm not sure how intelfb's unload works; it may be that you have to reboot to clear up the conflicts...
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.