Are you sure it's a bug? Maybe try to fix it first by opening a thread on the forums?
Why does your kdm.log talks about /lib/modules/2.6.39-ARCH/kernel/drivers/ ? Have you restarted your computer after updating to linux 3 kernel?

Does your system work w/ e.g. dwm?
I'm using IBM NetVista with the same card but I'm *not* using KDE - works fine.
https://bbs.archlinux.org/viewtopic.php?pid=940330#p940330

Looking at dmesg output, the i915 driver is not loaded on your system. Did you blacklist it? I have some thinclients running with the same NetVista systems, they work fine (though I enabled ShadowFB for those).

@karol Yes, this a bug for me. I did one installation process from zero and I hope than everything work fine, otherwise something is wrong here and must be considered as a bug.

@JGC Yes you're right. I didn't blacklist it, this is a new and recent installation. When I try load the module, this message appears:

[root@myhost ~]# modprobe i915
WARNING: Error inserting i2c_core (/lib/modules/3.0-ARCH/kernel/drivers/i2c/i2c-core.ko.gz): No such device
WARNING: Error inserting agpgart (/lib/modules/3.0-ARCH/kernel/drivers/char/agp/agpgart.ko.gz): No such device
WARNING: Error inserting intel_gtt (/lib/modules/3.0-ARCH/kernel/drivers/char/agp/intel-gtt.ko.gz): No such device
WARNING: Error inserting button (/lib/modules/3.0-ARCH/kernel/drivers/acpi/button.ko.gz): No such device
WARNING: Error inserting i2c_algo_bit (/lib/modules/3.0-ARCH/kernel/drivers/i2c/algos/i2c-algo-bit.ko.gz): No such device
WARNING: Error inserting intel_agp (/lib/modules/3.0-ARCH/kernel/drivers/char/agp/intel-agp.ko.gz): No such device
WARNING: Error inserting drm (/lib/modules/3.0-ARCH/kernel/drivers/gpu/drm/drm.ko.gz): No such device
WARNING: Error inserting drm_kms_helper (/lib/modules/3.0-ARCH/kernel/drivers/gpu/drm/drm_kms_helper.ko.gz): No such device
FATAL: Error inserting i915 (/lib/modules/3.0-ARCH/kernel/drivers/gpu/drm/i915/i915.ko.gz): No such device
[root@myhost ~]#

I did search and all the files are in the file system. I can't see the logic in this. How can I fix this one?

PS: Can you back severity to Critical?. I can't work with this machine without X mode. Thanks.

Do you have 'options i915 modeset=1' in your /etc/modprobe.d/modprobe.conf ?
Post the output of 'grep -v '#' /etc/mkinitcpio.conf'.


I really think you should open a thread on the forums so we don't clutter this bug report.

@karol No, I don't have no value in /etc/modprobe.d/modprobe.conf file.

[root@myhost ~]# grep -v '#' /etc/mkinitcpio.conf
MODULES=""

BINARIES=""

FILES=""

HOOKS="base udev autodetect pata scsi sata filesystems usbinput"


[root@myhost ~]#

Thanks by your interest and fast answers.

I added the i915 module to the MODULES line in /etc/mkinitcpio.conf file, I regenerated the initramfs and I rebooted the machine and the failure still continues.

I added i915.modeset=1 to the kernel line in /boot/grub/menu.lst file and I rebooted the machine and the failure still continues.

I followed the instructions of X freeze/crash with intel driver section and I rebooted the machine and the failure still continues.

What's the output of 'lsmod | grep i915' and 'grep kernel /boot/grub/menu.lst | grep -v '#''?
What does your /etc/X11/xorg.conf.d/20-intel.conf look like?

Again, I'm not using KDE, but enabling 'Shadow' fixed any problems I had w/ the GPU:
[karol@black test]$ cat /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
Identifier "card0"
Driver "intel"
Option "Shadow" "True"
Option "DRI" "false"
EndSection

Here are the answers:

[root@myhost ~]# lsmod | grep i915
[root@myhost ~]# grep kernel /boot/grub/menu.lst | grep -v '#'
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/4d9f10b4-1f2c-447b-98c5-15882fb8150c ro i915.modeset=1
[root@myhost ~]# cat /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
Identifier "old intel stuff"
Driver "intel"
Option "Shadow" "True"
Option "DRI" "false"
EndSection
[root@myhost ~]#

I have 'options i915 modeset=1' in my /etc/modprobe.d/modprobe.conf and

[karol@black foo2]$ grep -v '#' /etc/mkinitcpio.conf
MODULES="intel_agp i915"
BINARIES=""
FILES="/etc/modprobe.d/modprobe.conf"
HOOKS="base udev autodetect pata scsi sata filesystems consolefont"
COMPRESSION="gzip"


If you try 'modprobe i915' do you still get the same errors? If so, do you have the files e.g. /lib/modules/3.0-ARCH/kernel/drivers/gpu/drm/i915/i915.ko.gz and /usr/lib/xorg/modules/drivers/intel_drv.so?

Can you post your 20-intel.conf, xorg.conf and any other config you're using to setup X?

Yes, the error still continues:

[root@myhost ~]# modprobe i915
WARNING: Error inserting i2c_core (/lib/modules/3.0-ARCH/kernel/drivers/i2c/i2c-core.ko.gz): No such device
WARNING: Error inserting agpgart (/lib/modules/3.0-ARCH/kernel/drivers/char/agp/agpgart.ko.gz): No such device
WARNING: Error inserting intel_gtt (/lib/modules/3.0-ARCH/kernel/drivers/char/agp/intel-gtt.ko.gz): No such device
WARNING: Error inserting button (/lib/modules/3.0-ARCH/kernel/drivers/acpi/button.ko.gz): No such device
WARNING: Error inserting i2c_algo_bit (/lib/modules/3.0-ARCH/kernel/drivers/i2c/algos/i2c-algo-bit.ko.gz): No such device
WARNING: Error inserting intel_agp (/lib/modules/3.0-ARCH/kernel/drivers/char/agp/intel-agp.ko.gz): No such device
WARNING: Error inserting drm (/lib/modules/3.0-ARCH/kernel/drivers/gpu/drm/drm.ko.gz): No such device
WARNING: Error inserting drm_kms_helper (/lib/modules/3.0-ARCH/kernel/drivers/gpu/drm/drm_kms_helper.ko.gz): No such device
FATAL: Error inserting i915 (/lib/modules/3.0-ARCH/kernel/drivers/gpu/drm/i915/i915.ko.gz): No such device
[root@myhost ~]#

I did a search and I got this:

[root@myhost ~]# ls -l /lib/modules/3.0-ARCH/kernel/drivers/i2c/
total 40
drwxr-xr-x 2 root root 4096 Aug 30 02:37 algos
drwxr-xr-x 2 root root 4096 Aug 30 02:37 busses
-rw-r--r-- 1 root root 11970 Aug 30 02:37 i2c-core.ko.gz
-rw-r--r-- 1 root root 4396 Aug 30 02:37 i2c-dev.ko.gz
-rw-r--r-- 1 root root 1742 Aug 30 02:37 i2c-mux.ko.gz
-rw-r--r-- 1 root root 2382 Aug 30 02:37 i2c-smbus.ko.gz
drwxr-xr-x 2 root root 4096 Aug 30 02:37 muxe
[root@myhost ~]# ls -l /lib/modules/3.0-ARCH/kernel/drivers/char/agp/
total 92
-rw-r--r-- 1 root root 16064 Aug 30 02:37 agpgart.ko.gz
-rw-r--r-- 1 root root 3183 Aug 30 02:37 ali-agp.ko.gz
-rw-r--r-- 1 root root 5823 Aug 30 02:37 amd64-agp.ko.gz
-rw-r--r-- 1 root root 4242 Aug 30 02:37 amd-k7-agp.ko.gz
-rw-r--r-- 1 root root 4255 Aug 30 02:37 ati-agp.ko.gz
-rw-r--r-- 1 root root 3837 Aug 30 02:37 efficeon-agp.ko.gz
-rw-r--r-- 1 root root 5754 Aug 30 02:37 intel-agp.ko.gz
-rw-r--r-- 1 root root 8913 Aug 30 02:37 intel-gtt.ko.gz
-rw-r--r-- 1 root root 4039 Aug 30 02:37 nvidia-agp.ko.gz
-rw-r--r-- 1 root root 3705 Aug 30 02:37 sis-agp.ko.gz
-rw-r--r-- 1 root root 4459 Aug 30 02:37 sworks-agp.ko.gz
-rw-r--r-- 1 root root 4159 Aug 30 02:37 via-agp.ko.gz
[root@myhost ~]# ls -l /lib/modules/3.0-ARCH/kernel/drivers/acpi/
total 108
-rw-r--r-- 1 root root 2599 Aug 30 02:37 ac.ko.gz
-rw-r--r-- 1 root root 2767 Aug 30 02:37 acpi_ipmi.ko.gz
-rw-r--r-- 1 root root 4154 Aug 30 02:37 acpi_pad.ko.gz
drwxr-xr-x 2 root root 4096 Aug 30 02:37 apei
-rw-r--r-- 1 root root 6478 Aug 30 02:37 battery.ko.gz
-rw-r--r-- 1 root root 3469 Aug 30 02:37 button.ko.gz
-rw-r--r-- 1 root root 2047 Aug 30 02:37 container.ko.gz
-rw-r--r-- 1 root root 1500 Aug 30 02:37 custom_method.ko.gz
-rw-r--r-- 1 root root 1797 Aug 30 02:37 ec_sys.ko.gz
-rw-r--r-- 1 root root 1857 Aug 30 02:37 fan.ko.gz
-rw-r--r-- 1 root root 1447 Aug 30 02:37 hed.ko.gz
-rw-r--r-- 1 root root 3085 Aug 30 02:37 pci_slot.ko.gz
-rw-r--r-- 1 root root 16988 Aug 30 02:37 processor.ko.gz
-rw-r--r-- 1 root root 2883 Aug 30 02:37 sbshc.ko.gz
-rw-r--r-- 1 root root 6593 Aug 30 02:37 sbs.ko.gz
-rw-r--r-- 1 root root 5784 Aug 30 02:37 thermal.ko.gz
-rw-r--r-- 1 root root 8452 Aug 30 02:37 video.ko.gz
[root@myhost ~]# ls -l /lib/modules/3.0-ARCH/kernel/drivers/gpu/drm/
total 148
-rw-r--r-- 1 root root 15449 Aug 30 02:37 drm_kms_helper.ko.gz
-rw-r--r-- 1 root root 84482 Aug 30 02:37 drm.ko.gz
drwxr-xr-x 2 root root 4096 Aug 30 02:37 i2c
drwxr-xr-x 2 root root 4096 Aug 30 02:37 i915
drwxr-xr-x 2 root root 4096 Aug 30 02:37 mga
drwxr-xr-x 2 root root 4096 Aug 30 02:37 nouveau
drwxr-xr-x 2 root root 4096 Aug 30 02:37 r128
drwxr-xr-x 2 root root 4096 Aug 30 02:37 radeon
drwxr-xr-x 2 root root 4096 Aug 30 02:37 savage
drwxr-xr-x 2 root root 4096 Aug 30 02:37 sis
drwxr-xr-x 2 root root 4096 Aug 30 02:37 tdfx
drwxr-xr-x 2 root root 4096 Aug 30 02:37 ttm
drwxr-xr-x 2 root root 4096 Aug 30 02:37 via
drwxr-xr-x 2 root root 4096 Aug 30 02:37 vmwgfx
[root@myhost ~]# ls -l /lib/modules/3.0-ARCH/kernel/drivers/gpu/drm/i915/
total 260
-rw-r--r-- 1 root root 264477 Aug 30 02:37 i915.ko.gz

Here looks like one solution: https://bbs.archlinux.org/viewtopic.php?pid=923769#p923769 but I can't find those packages.

They should still be in the ARM http://arm.konnichi.com/search/ , but I have no idea why aren't the modules loaded. I honestly have no problems using my IBM NetVista.
I was suggesting using old versions of xorg-server and friends before I knew about 'Shadow'.

The problem is not in xf86-video-intel, but in the fact that the kernel can't load a video driver for your video chip. Could you try kernel26-lts? That kernel should support your video chip for sure.

Looking at your error output of "modprobe i915", it says "no such device" for all modules that it tries to insert. Probably it fails to insert one of those modules, resulting in failure for all of them. Could you modprobe them one by one and post which one gives you errors and which one succeeds? Attaching output of dmesg after that whould also be nice.

Another thing I noticed in your first bugreport, your BIOS is setup for 1MB of stolen memory. In some situations that can cause problems. AFAIK the BIOS of your IBM computer allows setting it to 8MB instead, which could solve your problem.

I'm experiencing the same problem. I did modprobes step by step, and it turns out that the offending module is 'button':

[root@myhost ~]# modprobe i915
WARNING: Error inserting i2c_core (/lib/modules/3.1.1-GNL/kernel/drivers/i2c/i2c-core.ko.gz): No such device
WARNING: Error inserting agpgart (/lib/modules/3.1.1-GNL/kernel/drivers/char/agp/agpgart.ko.gz): No such device
WARNING: Error inserting intel_gtt (/lib/modules/3.1.1-GNL/kernel/drivers/char/agp/intel-gtt.ko.gz): No such device
WARNING: Error inserting button (/lib/modules/3.1.1-GNL/kernel/drivers/acpi/button.ko.gz): No such device
WARNING: Error inserting i2c_algo_bit (/lib/modules/3.1.1-GNL/kernel/drivers/i2c/algos/i2c-algo-bit.ko.gz): No such device
WARNING: Error inserting intel_agp (/lib/modules/3.1.1-GNL/kernel/drivers/char/agp/intel-agp.ko.gz): No such device
WARNING: Error inserting drm (/lib/modules/3.1.1-GNL/kernel/drivers/gpu/drm/drm.ko.gz): No such device
WARNING: Error inserting drm_kms_helper (/lib/modules/3.1.1-GNL/kernel/drivers/gpu/drm/drm_kms_helper.ko.gz): No such device
FATAL: Error inserting i915 (/lib/modules/3.1.1-GNL/kernel/drivers/gpu/drm/i915/i915.ko.gz): No such device
[root@myhost ~]# modprobe i2c_core
[root@myhost ~]# modprobe agpgart
[root@myhost ~]# modprobe intel_gtt
[root@myhost ~]# modprobe button
FATAL: Error inserting button (/lib/modules/3.1.1-GNL/kernel/drivers/acpi/button.ko.gz): No such device
[root@myhost ~]# modprobe i2c_algo_bit
[root@myhost ~]# modprobe intel_agp
[root@myhost ~]# modprobe drm
[root@myhost ~]# modprobe drm_kms_helper

Button not loading could indicate disabled ACPI. I don't know why intel drivers depend on the button module, but that module needs ACPI enabled to load.

Yes, it turned out that the ACPI is disabled by default in the motherboards we use. The two solutions that worked for me were:
1) Obvious one - enable ACPI in BIOS setup.
2) Compiling the button module directly into the kernel.