> I see you're running 2.6.37, and it looks like there were some more
> backlight fixes lately, so you might want to try latest 2.6.38-rc from
> experimental.
Thanks, I've just now looked at the shortlog entry related to the
backlight. However, my backlight is fine: It turns off upon suspend and
I haven't seen the GPU hang recently (running testing/unstable).
Instead when it crashes after S3 resume, the screen is off but the
backlight is on (and the GPU s otherwise working fine). See Bug#525619.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscri
> could we please get an update, with either squeeze or higher?
Alas, yes: I still see the problem. It happens every couple days where
the screen is blank (but the backlight is on). A few days ago I had
started filling out a new Debian bug report, but then got the hang
again, rebooted, and lost
Downgrading xserver-xorg-video-intel to 2.13.0-3 solved the same problem
for me (Thinkpad T60 with Intel 945GM graphics). I suspected that it
would work based on the Debian Changelog entry for 2.13.0-4:
* Fail intel_pci_probe if we don't have a kernel mode setting driver.
This allows the X serv
Package: xserver-xorg-video-intel
Version: 2:2.12.0+shadow-2
Severity: normal
This is the same problem I saw in
: Upon waking up from S3
sleep, the screen came back very close to black (with just enough
brightness that I could make out where my Emacs window was). I'm
running vanilla 2.6.36. The
> Not sure it's going to help, but well, having an updated bug status
> would be nice.
For a week or so I've been running xserver-xorg-video-intel
2.12.0+shadow-2 (and shadow-1 for a week before that). Good news: The
problem has not reappeared.
--
To UNSUBSCRIBE, email to debian-x-requ...@lis
> Is this reproducible with 2.12.0 from experimental?
I am trying 2.12.0 now. But I get several problems:
1. One time it wouldn't resume from S3 sleep.
2. Regularly the mouse does not work.
I'll try some more tests and see what I can reproduce and capture in the
log and be back in touch in a c
> Is this reproducible with 2.12.0 from experimental?
I will try that.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1obvpv-0001cn...@approx.mit.edu
>> In both cases, the backlight was still on, but the screen was blank.
>> And switching back to vt1 or any other non-X vt, then back to vt7,
>> did not solve it. However, putting the laptop into S3 sleep and then
>> resuming solved the problem.
> can you still reproduce this with latest intel dr
I've been running current kernels and libdrm (2.4.18 from unstable) and
haven't seen the problem recur.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1nlt5e-gf...@
> At least the flickering and 'screen turns to pink' issues are a kernel
> bug (or multiple kernel bugs). Adding i915.powersave=0 to the kernel
> command line should work around that.
Thanks. That fixed the pink screen and the flickering (and the 'tearing').
--
To UNSUBSCRIBE, email to debia
Package: xserver-xorg-video-intel
Version: 2:2.9.1-2
Severity: grave
The flickering in #56 has returned since I upgraded the X server
and kernel a couple days ago (I'm tracking 'unstable'). Now it
flickers a once or twice per minute.
In addition, one of the Firefox windows often gets shifted
Julien Cristau wrote:
> It's quite likely that this is fixed with newer libdrm and/or
> xserver-xorg-video-intel. Can you confirm?
I'm now using libdrm 2.4.15-1 and xserver-xorg-video-intel 2.9.1-1, and
I just retested the .mp4 files on my system (not sure which .mp4 file I
had used back in Apr
The flickering seems absent since this morning, when I installed and
rebooted with the latest and greatest 2.6.30 kernel package
(linux-image-2.6.30-1-686 version 2.6.30-5).
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas..
> Please send your config and log.
=== /etc/X11/xorg.conf =
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the
The screen flickering has returned after aptitude upgrading a few days
ago. It happens every few minutes.
The upgrade switched to these xserver-xorg packages:
xserver-xorg-core 2:1.6.3-1
xserver-xorg-video-intel 2:2.8.0-2
The hardware is a TP T60 with Intel graphics. From lspci:
00:02.1 D
I haven't rebooted since the server crash (and won't unless I have to
because of another crash). So I can reproduce the console problem any
time, and can run lspci or any other diagnostics that might help track
it down.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subje
I'm using the intel driver from unstable (2.7.1), and I have not noticed
the problem.
2.7.1 also fixed other hangs I often noticed with 2.7.0. The fix was
probably this change:
* Fix multiplication error when computing required batch space.
This could fix any number of cases where the
Package: xserver-xorg
Version: 1:7.4+1
Severity: normal
When running mplayer on an .mp4 file, it complained about LIRC
something or other, then the X server crashed. In /var/log/xdm.log
there were these lines including an assertion failure:
I830PMEvent: Capability change
I830PMEvent: Capability
> Don't use make install. Just copy src/.libs/intel.so into
> /usr/lib/xorg/modules/drivers/ (after having moved the old intel.so
> from there).
Great, that's a much simpler recipe. I did that and restarted the X
server (with just one server), and got this in the log
(II) LoadModule: "intel"
(II
> I'm using the intel driver from the experimental repo on a system
> otherwise using unstable without any ill effects. The problem is that
> even the experimental version is too old (2.6.1). Upstream has had a
> large number of bug fixes since then (most importantly to me - XV
> tearing fixes and
> I'm pretty certain that what you're seeing is already reported upstream:
> https://bugs.freedesktop.org/show_bug.cgi?id=17805
I just read through that thread. It looks similar but I'm not too sure.
The reports there were of the whole display blanking for a (short)
while. Mine doesn't go blank.
Package: xserver-xorg
Version: 1:7.3+16
Severity: normal
After about a day of uptime, the X server suddenly crashed; xdm tried
to restart it but the server kept crashing. Restarting xdm didn't
help, but rebooting did.
The machine is a Thinkpad T60 with Intel integrated graphics.
Here is the xdm
I just ran into this problem as well, and was about to report the same
workaround (changing /usr/bin/X11/xdm to /usr/bin/xdm in /etc/init.d/xdm
and /etc/X11/default-display-manager). But I'm still not sure which X
server to use in /etc/X11/xdm/Xservers. There's
-rwxr-xr-x 1 root root 1878204 200
24 matches
Mail list logo
