Changelog has changed
in [Slackware]
|
Prev: Slack 12.2 - gnuplot and wxt
Next: radeon kms
From: Ewald Pfau on 3 Mar 2010 16:51 [myself just a minute ago]: > Having installed fresh new X, for me this has broken access to X via Intel > driver. This is for hardware with 915GM. Looking around, I can see, this problem ist reported elsewhere as well. Just found it for debian and archlinux. http://www.vdr-portal.de/board/archive/93467/thread.html http://bbs.archlinux.org/viewtopic.php?pid=710093 When trying to cure it by explicitely loading module i915 or the previous versions of intel driver from extra deposit, I encountered compatibility problems, which looks like a different problem.
From: Nikolay Korotkiy on 6 Mar 2010 11:04 On Mar 3, 4:31 pm, Ewald Pfau <ander...(a)gmx.net> wrote: > Richard Herbert <rherb...(a)sympatico.ca>: > > > On Tue, 02 Mar 2010 05:54:25 +0000, Robby Workman wrote: > > >> Patience, grasshopper. :-) > > > I'll wait for 13.1. > > ----------- > > Take a look at /var/log/Xorg.0.log --> > > | X.Org X Server 1.7.5 > | Release Date: 2010-02-16 > | X Protocol Version 11, Revision 0 > | Build Operating System: Slackware 13.1 Slackware Linux Project > > ----------- > > Having installed fresh new X, for me this has broken access to X via Intel > driver. This is for hardware with 915GM. > > Before, I made use of old versions which are below 'extra', but those won't > load anymore. > > <modprobe i915> throws back: > WARNING: Error inserting button > (/lib/modules/2.6.33-smp/kernel/drivers/acpi/button.ko): Invalid module format > WARNING: Error inserting i2c_algo_bit > (/lib/modules/2.6.33-smp/kernel/drivers/i2c/algos/i2c-algo-bit.ko): Invalid module format > WARNING: Error inserting agpgart > (/lib/modules/2.6.33-smp/kernel/drivers/char/agp/agpgart.ko): Invalid module format > WARNING: Error inserting drm > (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/drm.ko): Invalid module format > WARNING: Error inserting drm_kms_helper > (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/drm_kms_helper.ko): Invalid module format > FATAL: Error inserting i915 > (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/i915/i915.ko): Invalid module format > > Results are similar when configuring 'intel' in xorg.conf. It just won't > start. There is an xorgsetup program. This will freeze access to the machine > perfectly (background jobs seem to continue). > > This is bizarre. > > So I went along configuring 'vesa' in xorg.conf, instead of 'intel'. > > Seems I have to wait. Or find some other trick. Or enough time, to find out, > what to recompile on my own, in order to access X via 1600x1200 again, > instead of lousy 1024x768 - vesa won't give me more than that. I have same problem.
From: Robby Workman on 7 Mar 2010 01:46 On 2010-03-06, Nikolay Korotkiy <sikmir(a)gmail.com> wrote: > On Mar 3, 4:31 pm, Ewald Pfau <ander...(a)gmx.net> wrote: >> Richard Herbert <rherb...(a)sympatico.ca>: >> >> > On Tue, 02 Mar 2010 05:54:25 +0000, Robby Workman wrote: >> >> >> Patience, grasshopper. :-) >> >> > I'll wait for 13.1. >> >> ----------- >> >> Take a look at /var/log/Xorg.0.log --> >> >> | X.Org X Server 1.7.5 >> | Release Date: 2010-02-16 >> | X Protocol Version 11, Revision 0 >> | Build Operating System: Slackware 13.1 Slackware Linux Project >> >> ----------- >> >> Having installed fresh new X, for me this has broken access to X via Intel >> driver. This is for hardware with 915GM. >> >> Before, I made use of old versions which are below 'extra', but those won't >> load anymore. >> >> <modprobe i915> throws back: >> WARNING: Error inserting button >> (/lib/modules/2.6.33-smp/kernel/drivers/acpi/button.ko): Invalid module format >> WARNING: Error inserting i2c_algo_bit >> (/lib/modules/2.6.33-smp/kernel/drivers/i2c/algos/i2c-algo-bit.ko): Invalid module format >> WARNING: Error inserting agpgart >> (/lib/modules/2.6.33-smp/kernel/drivers/char/agp/agpgart.ko): Invalid module format >> WARNING: Error inserting drm >> (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/drm.ko): Invalid module format >> WARNING: Error inserting drm_kms_helper >> (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/drm_kms_helper.ko): Invalid module format >> FATAL: Error inserting i915 >> (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/i915/i915.ko): Invalid module format >> >> Results are similar when configuring 'intel' in xorg.conf. It just won't >> start. There is an xorgsetup program. This will freeze access to the machine >> perfectly (background jobs seem to continue). >> >> This is bizarre. >> >> So I went along configuring 'vesa' in xorg.conf, instead of 'intel'. >> >> Seems I have to wait. Or find some other trick. Or enough time, to find out, >> what to recompile on my own, in order to access X via 1600x1200 again, >> instead of lousy 1024x768 - vesa won't give me more than that. > > I have same problem. We think we've got this one figured out too, but time will tell. Patience, grasshopper :) -RW
From: Ewald Pfau on 7 Mar 2010 15:05
[ >> FATAL: Error inserting i915 >> (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/i915/i915.ko): >> Invalid module format ...] Nikolay Korotkiy <sikmir(a)gmail.com>: > I have same problem. Cannot offer a cure the correct (analytical) way, but for me it works now, after I recurred to a previous .config for fresh compilation of kernel 2.6.33, via 'make oldconfig' (plus 'make menuconfig'). When compiling from distribution .config, somehow I fell into the trap of losing new way of access to ATA harddrive as /dev/sdax, so I did not look around for much configuration inside this version, after I had a fall-back version available. For kernel configuration of module i915, the extra tick has to be applied (in .config: 'CONFIG_DRM_I915_KMS=y'). Now module i915 could be loaded and in consequence I could configure 'intel' in xorg.conf, this looks good now. Re-arranged the items in xorg.conf a bit, as well, after reading in manpage, so to have two screens (laptop interal plus external) configured in two different blocks now. |