On Wed, 2009-06-03 at 21:26 +0200, Brice Goglin wrote:
Jerry,
Does this problem still happen with latest intel driver from unstable or
experimental?
I'm no longer seeing the lockups, so the recent Intel drivers must have
fixed the issue.
--
To UNSUBSCRIBE, email to
Package: xserver-xorg-video-intel
Version: 2:2.4.0-1
Followup-For: Bug #475112
Another lockup using 2.4.0 and xserver 1.4.99. This time there's a backtrace.
Here's the log:
(WW) Failed to open protocol names file /etc/X11/xserver/protocol.txt
This is a pre-release version of the X server
Package: xserver-xorg-video-intel
Version: 2:2.3.2-2
Followup-For: Bug #490159
I again saw the I830WaitLpRing crash in my Xserver. I noticed that
while the Xserver was trying to restart, the following shows up in the kernel
log:
Aug 2 22:54:09 cerberus kernel: [149895.395894] mtrr: no more
Brice Goglin wrote:
found 475112 2:2.2.99.902-1
thank you
Jerry Quinn wrote:
Also, it would be good to know whether it is EXA related. Add
Option AccelMethod XAA
do the Device section of your xorg.conf.
I've now seen the same X death with XAA enabled in 2.2.99.902-1, so
Brice Goglin wrote:
Jerry Quinn wrote:
Package: xserver-xorg-video-intel
Version: 2:2.2.1-1
Severity: important
Can you reproduce with 2:2.2.99.902-1 from experimental?
Also, it would be good to know whether it is EXA related. Add
Option AccelMethod XAA
do the Device section of your
Brice Goglin wrote:
Jerry Quinn wrote:
The lockup is random but has happened a few times in the last week for me.
This time, I hit C-w to close a icedove window when it happened. One thing
that may be useful to know is that I've opened and closed many many windows,
due to some bad calendar
Brice Goglin wrote:
Jerry Quinn wrote:
Package: compiz
Version: 0.6.3~git20071222.061ff159-1
Severity: normal
I'm trying compiz for the first time. When I start it up, all the window
borders disappear. No sign of compiz taking control appears. Also, I cannot
see what I type in any terminal
Package: compiz
Version: 0.6.3~git20071222.061ff159-1
Severity: normal
I'm trying compiz for the first time. When I start it up, all the window
borders disappear. No sign of compiz taking control appears. Also, I cannot
see what I type in any terminal window. It seems to respond to clicks to
Brice Goglin wrote:
Jerry Quinn wrote:
What's the right place to put this so it will autoload correctly in
the future?
/etc/modules should work. But you shouldn't have to do that, it should
be done automatically by the system.
Should it be automatic on each reboot? Or should the installer
Brice Goglin wrote:
Jerry Quinn wrote:
Package: xserver-xorg-video-intel
Version: 2:2.1.1-1
Severity: important
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Debian (xorg-server 2:1.3.0.0.dfsg-12)
Current
Brice Goglin wrote:
Hi,
About 8 years ago, you reported a bug to the Debian BTS regarding
xlsfonts incorrectly processing some patterns. Did you reproduce this
problem recently? With Xorg/Etch? If not, I will close this bug in the
next weeks.
This problem doesn't seem to be there any more
Package: xserver-xorg-video-ati
Version: 1:6.5.8.0-1
Severity: normal
The radeon driver can't detect the video chip on this thinkpad. lspci gives:
01:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 71c4
(prog-if 00 [VGA])
Subsystem: Lenovo Unknown device 2007
Package: xbase-clients
Version: 1:7.1.ds-2
Severity: minor
As the subject says.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux
Package: xserver-xorg-video-mga
Version: 1:1.2.1.3.dfsg.1-2
Severity: important
xorg crashes randomly but invariably within a day or so. This one happened
within glcore.
Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x89) [0x80b6849]
1: [0xe420]
2:
Package: xserver-xorg-video-mga
Version: 1:1.2.1.3.dfsg.1-2
Severity: normal
This is a continuation of bug 356558. The DVI output doesn't work under X
but console output works fine.
This problem isn't related to a particular kernel version.
-- System Information:
Debian Release:
Package: xserver-xorg
Version: 1:7.0.22
Followup-For: Bug #374576
This crash appears to happen within 24 hours. I'm now thinking that sometimes
a screensaver can trigger it.
The kernel is linux-image-2.6.16-2-k7 version 2.6.16-14
Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x88) [0x80b8d98]
Package: xserver-xorg
Version: 1:7.0.22
Followup-For: Bug #374576
The same crash (or at least the same backtrace), showed up overnight while the
machine was idle.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'),
Package: xserver-xorg
Version: 6.9.0.dfsg.1-4
Severity: normal
I have a Sceptre X20G-Naga II connected to my matrox adaptor. If I bring it
up attached to the DVI port (DVI-DVI), console works (VGA is handled
differently by the card, I assume), but I get a black screen from X.
Connecting the
Package: xserver-xfree86
Version: 4.2.1-12.1
Severity: minor
The ATI driver incorrectly detects the screen dots per inch as 75 dpi.
xdpyinfo says the panel is 474x356 mm. The actual physical dimensions
are approx 286x215 mm. This is an IBM thinkpad T30. The same error
occurs on multiple
Branden Robinson writes:
On Sat, Nov 30, 2002 at 10:09:17PM -0500, Jerry Quinn wrote:
Chris Halls writes:
I read this in Kernel Traffic #192. Could this be your problem?
Marcelo Tosatti announced 2.4.20-rc1 and included the BitKeeper summary. He
said, Several networking
Branden Robinson writes:
On Sat, Nov 30, 2002 at 10:09:17PM -0500, Jerry Quinn wrote:
Chris Halls writes:
I read this in Kernel Traffic #192. Could this be your problem?
Marcelo Tosatti announced 2.4.20-rc1 and included the BitKeeper
summary. He
said, Several
it. Also, I don't use fbdev, because I don't get a working display at
all with it.
That said, I can pull down this kernel and give it a try.
Thanks,
Jerry Quinn
--
1. Linux 2.4.20-rc1 Released
Topics: Filesystems, Framebuffer, Source Control
29 Oct - 8 Nov (8 posts) Archive
it. Also, I don't use fbdev, because I don't get a working display at
all with it.
That said, I can pull down this kernel and give it a try.
Thanks,
Jerry Quinn
--
1. Linux 2.4.20-rc1 Released
Topics: Filesystems, Framebuffer, Source Control
29 Oct - 8 Nov (8 posts) Archive
Package: xserver-xfree86
Version: 4.2.1-3
Severity: normal
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW
01:00.0 Class 0300: 1002:4c57
### BEGIN DEBCONF SECTION
# XF86Config-4 (XFree86 server configuration file) generated by dexconf, the
# Debian X Configuration
Package: xserver-xfree86
Version: 4.2.1-3
Severity: normal
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW
01:00.0 Class 0300: 1002:4c57
### BEGIN DEBCONF SECTION
# XF86Config-4 (XFree86 server configuration file) generated by dexconf, the
# Debian X Configuration
Branden Robinson writes:
On Sat, Nov 16, 2002 at 09:20:15PM -0500, Jerry Quinn wrote:
Either way, the fact that blanking and unblanking works at the console
should point to the X server doing something wrong, no?
Only if putting the card into graphics mode counts as doing something
Branden Robinson writes:
On Sat, Nov 16, 2002 at 09:20:15PM -0500, Jerry Quinn wrote:
Either way, the fact that blanking and unblanking works at the console
should point to the X server doing something wrong, no?
Only if putting the card into graphics mode counts as doing something
Michel Dänzer writes:
On Sam, 2002-11-16 at 05:50, Jerry Quinn wrote:
The machine is an IBM Thinkpad T30 with a fresh install of Debian 3.0
on it. The LCD on this laptop will blank after about 5 minutes.
If you are at the X display when it blanks, it cannot be unblanked again
and resume (close the lid, open the lid).
If you are at one of the virtual consoles, unblanking works fine.
I notice that lspci thinks the chip is an M6 Mobility, but X thinks it
is an M7 Mobility.
Jerry Quinn
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LW
01:00.0
and resume (close the lid, open the lid).
If you are at one of the virtual consoles, unblanking works fine.
I notice that lspci thinks the chip is an M6 Mobility, but X thinks it
is an M7 Mobility.
Jerry Quinn
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LW
01:00.0
30 matches
Mail list logo
