Hello, I followed this topic in December when Celejar was having difficulty, but that solution doesn't help me. I recently bought a motherboard w/ H67 chip-set and i5 processor. I managed to purchase it 8 hours before the Intel recall was announced - lucky me.
Xorg seems determined to load/run the vesa driver no matter what I do. I gen'd a kernel with i915 DRM support and added i915 to modules to force loading. Here are the DRM entries in config: CONFIG_DRM=m CONFIG_DRM_KMS_HELPER=m CONFIG_DRM_TTM=m CONFIG_DRM_TDFX=m CONFIG_DRM_R128=m CONFIG_DRM_RADEON=m CONFIG_DRM_RADEON_KMS=y CONFIG_DRM_I810=m CONFIG_DRM_I830=m CONFIG_DRM_I915=m CONFIG_DRM_I915_KMS=y CONFIG_DRM_MGA=m CONFIG_DRM_SIS=m CONFIG_DRM_VIA=m CONFIG_DRM_SAVAGE=m # CONFIG_DRM_VMWGFX is not set CONFIG_DRM_NOUVEAU=m CONFIG_DRM_NOUVEAU_BACKLIGHT=y # CONFIG_DRM_NOUVEAU_DEBUG is not set CONFIG_DRM_I2C_CH7006=m This kernel produces these boot messages ('grep agp|drm'), but my reading suggests I should see more: [ 0.728270] Linux agpgart interface v0.103 [ 7.258235] [drm] Initialized drm 1.1.0 20060810 The vesa driver works fine. I've since removed it and fbdev trying to force the intel choice. Here's the resulting X.log: (II) LoadModule: "dri2" (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so (II) Module dri2: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.1.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DRI2 (==) Matched intel as autoconfigured driver 0 (==) Matched vesa as autoconfigured driver 1 (==) Matched fbdev as autoconfigured driver 2 (==) Assigned the driver to the xf86ConfigLayout (II) LoadModule: "intel" (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so (II) Module intel: vendor="X.Org Foundation" compiled for 1.7.7, module version = 2.13.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: "vesa" (WW) Warning, couldn't open module vesa (II) UnloadModule: "vesa" (EE) Failed to load module "vesa" (module does not exist, 0) (II) LoadModule: "fbdev" (WW) Warning, couldn't open module fbdev (II) UnloadModule: "fbdev" (EE) Failed to load module "fbdev" (module does not exist, 0) (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge (II) Primary Device is: PCI 00@00:02:0 (EE) No devices detected. Fatal server error: no screens found Any advice? I've got 4 CPU's with nowhere to go. Steve -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201102261312.41072.newsdeb...@jetcity.org