On Thu, Dec 27, 2012 at 3:35 PM, Roger Luedecke wrote:

After trying the different kernels, I have tried also the i915.modeset=0 and i915.modeset=1 in grub. The former seems to cause more problems than it solves, changing from a frozen screen to a garbled one.

Garbled sounds like some hardware problem. When I had that problem with an nVidia, it was a busted (ie: burnt) RAM module. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2012-12-27 13:35 (GMT-0500) Roger Luedecke composed:

I have tried running three different kernels.

Presumably you are running some version of openSUSE, and it behaves the same with Gnome, KDE, LXDE, XFCE and every other DE? I've not noticed this regardless of kernel on any 945GM system here running TDE, KDE or KDE4, but none are Toshiba laptops. Does it help to put http://fm.no-ip.com/Tmp/Linux/Xorg/70-composite.conf in /etc/X11/xorg.conf.d/ ? What is your display's native mode? Are you using it? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/27/2012 07:35 PM, Roger Luedecke wrote:

3.4 had known intel bugs, many of which were fixed in 3.6.10, hence that install. 3.7 (from tumbleweed) was originally being tested until I read there were regressions regarding the intel drivers.

What issue actually? I backported commit 9a28977181724ebbd9bdc45291cf29da55a729ee Author: Jesse Barnes Date: Fri Oct 26 09:42:42 2012 -0700 drm/i915: TLB invalidation with MI_FLUSH_DW requires a post-sync op v3 to both master and stable yesterday.

My screen will suddenly become unresponsive, with only the mouse being able to move. Then shortly thereafter that will stop responding as well. It is not possible to drop to TTY. I have to hold the power down.

After trying the different kernels, I have tried also the i915.modeset=0 and i915.modeset=1 in grub. The former seems to cause more problems than it solves,

You need KMS to have intel driver working properly. Non-KMS support was removed long time ago.

changing from a frozen screen to a garbled one. So far the latter is proving stable, though perhaps with slightly degraded graphical performance.

modeset=1 is the default. It should change the behavior in no way. It looks like some assertion in the driver is hit. Could you try to switch to SNA? Like this in /etc/X11/xorg.conf.d/50-device.conf: Section "Device" Identifier "Default Device" Driver "intel" Option "AccelMethod" "sna" EndSection regards, - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJQ3XfNAAoJEL0lsQQGtHBJ7C0P/3/RCtMPF3y68FZ9HNt/tpbo c/V92X9UERDReof3y8g7F5Ge9kzVqxnuga4NE7B2Wp9du0RiLkfMjhzuA2FaM1M/ 2u06fmv4lnkLB8QyhO18F1sMTsJ7B4Vv42kERbSqj1bQet5R7L/XEii23h9hif2I qwjzDYJcww5bCl+r2pwEyZ/viXTy9WyMKdi7fUylPMpvxX3eX8pGMLjt3ZvQ2LQ+ uMUVIeHySJYb8E9cSbxQ7gA1jwT83PbJkSDA9cjskqbvQxqkhTGdWge2GtX9AabP wdGxx7WBYxedu6SHZ7l1Gr7Z5oHPEgRttGaaXrlxo5U5hC/cuXwgqimtoWJjLHta k/UQ9Du57WcOHFHIPhWstXaFkYFvmYU2hLyTGhoB7uN6QPWHrd9v9c04qrum7LOw a/+PmosacP7gV11zerO2FjmX7GjPU6YgLMJo9GuEMxjHPjd9x/0CKRLBY60gKmxm ZuPx5ARpeRX3yKb1cxaLlPIZB6kwm3TGfJkcyeFmVBkBmNsSnVwMd4vlCnKB3Uzw D1PpG2QLNy32nTowXoS0QWt1W+PBeU8Elf1xIIAOfsENWTD/oK09TGx9NdmCynad 6eYJAlcwgs19QMYmMd0MP+836N2NENo+JKqvqDsJZ16qGH/kmizTU7OexvvgB9vs dlSwVSe4wKHuR2ZuK5Rg =xXih -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org