Ben Hutchings writes: > We can't support two different kernel versions but we can potentially > update the DRM drivers to the versions in Linux 3.4.y. This is covered > by bug #687442 which I've marked as blocking this bug. > > Julien Cristau prepared some packages for testing before we make this > change. Here's how you would install them with APT: > > gpg --no-default-keyring --keyring > /usr/share/keyrings/debian-keyring.gpg --export 310180050905E40C | apt-key > add - > echo deb http://people.debian.org/~jcristau/wheezy-drm34/ ./ > > /etc/apt/sources.list.d/jcristau-wheezy-drm34.list > apt-get update > apt-get install linux-image-3.2.0-4.drm-amd64 # or -486, or -686-pae > > Please test and send your results (good or bad) to > 687...@bugs.debian.org
I think we have a winner. I have been running linux-image-3.2.0-4.drm-amd64 for a week now with no stability problems. None of the previous 3.2 kernels were ever likely to make it that far. As a brief summary, my experience so far with Linux kernels has been: hangs: 3.2.23 (3.2.0-3) 3.2.32 (3.2.0-4) 3.2.35 (3.2.0-4) 3.7.1 (!) (experimental) no hangs: 3.5.5 (experimental) 3.6.8 (experimental) 3.6.9 (experimental) 3.7.3 (experimental) 3.2.35 w/3.4 Intel DRM (3.2.0-4.drm) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20752.16563.100367.238...@hexadecimal.uoregon.edu
