retitle 595103 framebuffer gone for intel i915 starting 2.6.32-21
severity 595103 grave
thanks

This is clearly a kernel issue and has nothing to do with xorg-anything.

# zegrep i915|fb|Debian dmesg.0 dmesg
dmesg.0:[ 0.000000] Linux version 2.6.32-5-686 (Debian 2.6.32-23) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-3) ) #1 SMP Sat Sep 18 02:14:45 UTC 2010
dmesg.0:[ 8.888189] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
dmesg:[ 0.000000] Linux version 2.6.32-5-686 (Debian 2.6.32-20) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Thu Aug 12 13:38:27 UTC 2010
dmesg:[ 8.208970] i915 0000:00:02.0: power state changed by ACPI to D0
dmesg:[ 8.209019] i915 0000:00:02.0: power state changed by ACPI to D0
dmesg:[ 8.209031] i915 0000:00:02.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
dmesg:[ 8.209039] i915 0000:00:02.0: setting latency timer to 64
dmesg:[ 9.349771] fb0: inteldrmfb frame buffer device
dmesg:[ 9.349915] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

However, until it is fixed, one cannot dream of running X windows. Even
just running on the console will eventually lead to a black screen, and
the need to reboot, disks having been synced or not.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 877hidi8ad.fsf@jidanni.org">http://lists.debian.org/877hidi8ad.fsf@jidanni.org

On Thu, Sep 23, 2010 at 08:59:54 +0800, jidanni@jidanni.org wrote:

> However, until it is fixed, one cannot dream of running X windows. Even
> just running on the console will eventually lead to a black screen, and
> the need to reboot, disks having been synced or not.
>
This is not true. You can get X up with vesa just fine.

Cheers,
Julien

forcemerge 595511 595103
severity 595511 grave
thanks
Even /etc/init.d/console-setup is affected I believe. Normally during
boot the console messages disappear, then reappear but now getting printed
at a smaller size. This corresponds to the point things start getting
logged in /var/log/boot. The first line wherein being
Thu Sep 23 14:51:41 2010: Activating swap...done.

Starting with kernel -21 they just all get printed at the same initial
size. I.e., the trouble starts right there X or no X.

>>>>> "JC" == Julien Cristau <jcristau@debian.org> writes:
JC> You can get X up with vesa just fine.

Not me though. And, I needn't start X at all, and before long the entire
display disappears and we need to cold reboot holding down the power
button, disks having been synced or not. Hence grave.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87sk10dezy.fsf@jidanni.org">http://lists.debian.org/87sk10dezy.fsf@jidanni.org