Package: libgl1-mesa-dri
Followup-For: Bug #949980
This bug is still present with the libgl1-mesa-dri in unstable
(currently 19.3.3-1), but upgrading the following set of packages
to the version in experimental (currently 20.0.0-1) fixes it for me:
libegl-mesa0
libgbm1
libgl1-mesa-dri
libglapi-me
On Mon, Sep 22, 2014 at 12:08 PM, Sven Joachim wrote:
> I don't see those, but then I don't use gdm or a compositing window
> manager. Does it help to turn off the "PageFlip" option in xorg.conf
> (see nouveau(4))?
Those error messages are gone again with kernel 3.16.3-2, but the
screen still do
Also, with nouveau.nofbaccel=1 the dead screen does not prevent a clean reboot.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/CAKCAbMh+VQi2+OjHC-8FKd_ouWuPE45c3Pzybfwk
Sorry for the delay getting back to you. nouveau.nofbaccel=1
eliminates the kernel-level errors, but the screen still does not turn
back on. /var/log/messages shows some new errors instead:
Sep 21 13:37:42 moxana gdm-Xorg-:0[781]: (WW) NOUVEAU(0):
nouveau_dri2_flip_event_handler: Pageflip has im
Package: xserver-xorg-video-nouveau
Version: 1:1.0.11-1
Severity: important
After resume from S3, the monitor does not turn back on and there are
floods of "PGRAPH" error messages in the kernel log. The OS is otherwise
functional (one can ssh in, for instance) but an attempt to reboot hangs
indef
Once again y'all have delayed doing anything about an X server bug so
long that I no longer have the hardware that was causing the problem.
:-(
zw
On Mon, Feb 21, 2011 at 9:33 AM, Cyril Brulebois wrote:
> Hi Zack,
>
> Zack Weinberg (06/03/2010):
>> That computer is off r
On Sun, Jan 30, 2011 at 11:37 AM, Julien Cristau wrote:
> On Sun, Jan 30, 2011 at 08:18:14 +0100, Cyril Brulebois wrote:
>> I'd welcome your forwarding/discussing your patch to/with upstream
>> directly:
>> http://www.x.org/wiki/Development/Documentation/SubmittingPatches
>> http://bugs.freede
On Wed, Jan 5, 2011 at 10:40 AM, Zack Weinberg wrote:
>
> Will try updating xserver-xorg-video-nouveau to the latest upstream
> sources next.
Didn't help. Filed https://bugs.freedesktop.org/show_bug.cgi?id=32855
with upstream.
--
To UNSUBSCRIBE, email to debian-x-requ...@li
On Thu, Dec 23, 2010 at 8:05 AM, Zack Weinberg wrote:
> On Thu, Dec 23, 2010 at 3:34 AM, Julien Cristau wrote:
>> On Wed, Dec 22, 2010 at 18:14:05 -0800, Zack Weinberg wrote:
>>
>>> * screen doesn't turn back on after suspend-to-ram with 2.6.36 from
>>>
On Thu, Dec 23, 2010 at 3:34 AM, Julien Cristau wrote:
> On Wed, Dec 22, 2010 at 18:14:05 -0800, Zack Weinberg wrote:
>
>> * screen doesn't turn back on after suspend-to-ram with 2.6.36 from
>> experimental
>>
> experimental has 2.6.37-rc5, did you check that?
No
On Thu, Dec 23, 2010 at 12:37 AM, Sven Joachim wrote:
> On 2010-12-23 03:14 +0100, Zack Weinberg wrote:
>> * bad image stretching with RENDER (see
>> https://bugzilla.mozilla.org/show_bug.cgi?id=468496 )
>
> Does this happen in Iceweasel 3.5 as well?
No, 3.5 does not
I'm investigating a couple of bugs which appear to be in the Nouveau
driver currently in 'experimental' (1:0.0.16+git20100825+390f1c8-1):
* bad image stretching with RENDER (see
https://bugzilla.mozilla.org/show_bug.cgi?id=468496 )
* screen doesn't turn back on after suspend-to-ram with 2.6.36 fro
On Sun, Mar 7, 2010 at 4:40 AM, Brice Goglin wrote:
>> The upstream bug[1] has been closed because DRI is supposed to work
>> fine. I just uploaded radeon 6.10.99.0 to experimental, and we have
>> mesa 7.3 there as well. It would be nice if you test all this.
>
> Still no luck with latest X packag
On Sat, Mar 6, 2010 at 1:45 AM, Brice Goglin wrote:
>
> Still problems with all this on radeon 6.12.5 or 6.12.191?
That computer is off right now, so I'm not sure exactly what version
of the driver I have on it - whatever's current in unstable. Anyway,
I haven't seen most of the problems in some
On Wed, Jan 27, 2010 at 8:03 AM, Brice Goglin wrote:
> Zack Weinberg wrote:
>> Since this morning, gnome-power-manager has put an alert in my notification
>> area with this text:
>>
>> Session active, not inhibited, screen idle.
>> If you can see this text,
On Tue, Sep 30, 2008 at 9:12 PM, Alex Deucher <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 30, 2008 at 2:12 PM, Florian Weimer <[EMAIL PROTECTED]> wrote:
>>
>> Hmm. Unfortuantely, it's not much faster with EXA. 8-(
>>
>
> How big is your screen (including both heads if you are using
> dualhead)? The
On Tue, Sep 30, 2008 at 11:12 AM, Florian Weimer <[EMAIL PROTECTED]> wrote:
> * Alex Deucher:
>
>> This is a known bug. If you put a rotation in your config, you get a
>> crash because acceleration is not set up when the rotation is
>> initialized. When the ordering was changed to fix this, it le
On Wed, Sep 17, 2008 at 9:27 AM, Michel Dänzer <[EMAIL PROTECTED]> wrote:
> As Alex pointed out, the flicker is likely due to the two display
> controllers and the accelerator fighting for memory bandwidth. You could
> try playing with Option "DisplayPriority".
Results in the other bug.
zw
On Wed, Sep 17, 2008 at 11:15 AM, Zack Weinberg <[EMAIL PROTECTED]> wrote:
> So I had to work a little harder than I'd have liked to disable one of
> the monitors (disconnect the DVI cable *and* comment out everything
> related to it in xorg.conf, including the Virtual line) bu
On Wed, Sep 17, 2008 at 7:36 AM, Alex Deucher <[EMAIL PROTECTED]> wrote:
> This is very likely related to multiple monitors. Please try EXA with
> one monitor and see if you still have the same problem.
So I had to work a little harder than I'd have liked to disable one of
the monitors (disconnec
On Wed, Sep 17, 2008 at 7:36 AM, Alex Deucher <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 16, 2008 at 8:25 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote:
>>
>> With EXA enabled on a Radeon R580 (or possibly an X1900, ATI's numbering
>> conventions confuse me)
On Wed, Sep 17, 2008 at 7:41 AM, Alex Deucher <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 16, 2008 at 8:52 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote:
>> Per the bug I just filed, XAA is painfully slow at drawing a rotated display
>> on the hardware I've got, so I t
On Tue, Sep 16, 2008 at 9:56 PM, Brice Goglin <[EMAIL PROTECTED]> wrote:
> Zack Weinberg wrote:
>> (II) RADEON(0): Generation 2 PCI interface, using max accessible memory
>> (II) RADEON(0): Detected total video RAM=524288K, accessible=262144K
>> (PCI BAR=262144K)
>>
On Tue, Sep 16, 2008 at 9:46 PM, Brice Goglin <[EMAIL PROTECTED]> wrote:
>
> I might be the Xserver core choosing the same resolution at startup (so
> that the login screen appears in the middle of both monitors instead of
> risking of having it outside one of them).
>
> You should be able to work
On Fri, Aug 8, 2008 at 1:55 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote:
>> * 6.9.0+git20080802-1 = latest upstream git, in experimental, for
>> Xserver 1.4.99 in experimental
Same phenomenon, slightly different diagnostics:
(II) RADEON(0): Generation 2 PCI interface, us
I need to correct myself - I've now observed flickering around the
mouse pointer with XAA in use, but not any of the other phenomena.
However, with XAA it's both less frequent and less prominent.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EM
Package: xserver-xorg-video-radeon
Version: 1:6.9.0+git20080826.a3cc1d7a-1
Severity: normal
Per the bug I just filed, XAA is painfully slow at drawing a rotated display
on the hardware I've got, so I tried EXA - but then the X server crashes on
startup. I'll paste the relevant bit of the server l
On Sat, Aug 2, 2008 at 3:56 PM, Brice Goglin <[EMAIL PROTECTED]> wrote:
>> I have no accelerated GL on a Radeon X1900 card. glxinfo says
>
> Don't you need a very recent mesa for 3d on r500? You might want to try
> libgl1-mesa-dri from experimental for direct rendering. And add
> xserver-xorg-core
FYI, the radeon driver has done well by me this past month or so
(although I *am* about to go file three more bugs on it) so I'm not
planning to pursue this bug any further. Feel free to close it.
zw
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Conta
Package: xserver-xorg-video-intel
Version: 2:2.3.2-2+lenny4
Followup-For: Bug #491871
Unlike a lot of people, I have had no problems whatsoever with the intel
drivers at their default settings ... until the 2.3.2-2+lenny4 version,
when several web sites I visit regularly started showing distorted
Package: xvfb
Version: 2:1.4.2-3
Severity: wishlist
File: /usr/bin/xvfb-run
Tags: patch
For e.g. automated testing of desktop applications, it would be nice
to have an xvfb-run mode that makes an effort to isolate the processes
it spawns from the user's normal environment. Specifically, it should
On Sat, Aug 2, 2008 at 4:19 PM, Brice Goglin <[EMAIL PROTECTED]> wrote:
> I just uploaded 2 newer radeon/ati:
> * 6.9.0-1+lenny2 = 6.9.0 + many backports of fixes, in unstable, for
> Xserver 1.4
Same with this one.
> * 6.9.0+git20080802-1 = latest upstream git, in experimental, for
> Xserver
On Sat, Aug 2, 2008 at 3:59 PM, Brice Goglin <[EMAIL PROTECTED]> wrote:
> You might want to try upstream git radeonhd since 1.2.1 is pretty old.
>
> That said, if radeon works fine, why not just forget about radeonhd? :)
I had been under the impression that radeon didn't support this card
at all,
On Sun, Jun 15, 2008 at 6:53 AM, Brice Goglin <[EMAIL PROTECTED]> wrote:
> Hello Zack,
> Now that 6.8.191 is in unstable, how's your Xpress working?
I'm moving; that computer is currently on a truck somewhere. I'll try
to remember, but if you don't hear from me in a couple weeks, please
ping agai
On Sat, Mar 22, 2008 at 6:31 AM, Brice Goglin
<[EMAIL PROTECTED]> wrote:
> All of you reported problems with the ati driver on Xpress chips. Alex
> Deucher called for testing of the latest ati git on
> http://www.botchco.com/agd5f/?p=25
With the very latest unstable kernel (linux-image-2.6.24-
On Wed, Feb 13, 2008 at 10:39 AM, Zack Weinberg <[EMAIL PROTECTED]> wrote:
> On Wed, Feb 13, 2008 at 6:33 AM, Brice Goglin <[EMAIL PROTECTED]> wrote:
> > Can you try the one in experimental? Can you look at /var/log/aptitude
> > or /var/log/dpkg.log to find out
On Wed, Feb 13, 2008 at 6:33 AM, Brice Goglin <[EMAIL PROTECTED]> wrote:
> Which xserver-xorg-video-ati driver are you using?
1:6.7.197-1.
> Can you try the one in experimental? Can you look at /var/log/aptitude
> or /var/log/dpkg.log to find out which driver you had before upgrading?
This br
On Wed, Feb 13, 2008 at 6:35 AM, Michel Dänzer <[EMAIL PROTECTED]> wrote:
>
> Could be https://bugs.freedesktop.org/show_bug.cgi?id=12744 .
The image attached to that bug does look very similar to the effect I'm seeing.
zw
On Dec 24, 2007 8:40 AM, Alex Deucher <[EMAIL PROTECTED]> wrote:
> Unfortunately, 3D isn't yet stable on most XPRESS chips. that's why
> it's disabled by default. I do plan to look into this when I get the
> time.
Please let me know if I can help with testing.
zw
--
To UNSUBSCRIBE, email t
On Dec 24, 2007 12:22 AM, Brice Goglin <[EMAIL PROTECTED]> wrote:
> Zack Weinberg wrote:
> > Sadly, with kernel 2.6.23 it's back to the black screen of death.
>
> I guess that was still when forcing DRI on, right?
Yes. Note that being able to reboot with alt-sysrq
On 8/10/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
> >> If you are still interested in fixing this problem, I would appreciate
> >> if you could send an updated patch. But please do not prepare it against
> >> Mesa 6.5.1 in Etch (such a change won't be accepted in Etch anyway). You
> >> should pre
On 8/12/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
> Now he wants you to do
> echo 1 > /sys/modules/drm/parameters/debug
> before starting X, then start X and send the output of dmesg.
Nothing in here looks obviously like a failure, but here it is ...
[drm] Initialized drm 1.1.0 20060810
NET
Package: xserver-xorg
Version: 1:7.2-5
Severity: wishlist
If there is no xorg.conf at all, X automatically deduces default settings
that work in a lot of cases (including my own). However, if there *is* an
xorg.conf, but it does not contain ServerLayout, Device, or Screen sections,
X refuses to s
On 7/10/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
Zack Weinberg wrote:
> 1) xrandr.out.1600x1200 is the output of this command when run under X
> with an xorg.conf forcing the max to be 1600x1200.
> 2) xrandr.out.1920x1200 is the output of this command when run under X
> wi
On 6/19/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
About 2 years ago, you reported a bug to the Debian BTS regarding a
lockup of the computer when using ati drivers on a R9100 board. Did you
reproduce this problem recently? With Xorg/Etch? With latest
xserver-xorg-core and drivers? If not, I wil
On 4/26/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
Zack Weinberg wrote:
> This is probably related to #418377, but the situation is slightly
> different. I have a flat-panel monitor which is not designed for
> resolutions higher than 1600x1200, and says so in its DDC reado
Package: xserver-xorg-core
Version: 2:1.3.0.0.dfsg-2
Severity: normal
This is probably related to #418377, but the situation is slightly
different. I have a flat-panel monitor which is not designed for
resolutions higher than 1600x1200, and says so in its DDC readout.
(Unfortunately my computer d
It has been quite some time since there was any activity on this bug.
Meanwhile the X 6.9 packages have hit unstable. Is there any reason
to believe that the bug might have been fixed in that version? I am
willing to turn DRI back on and see what happens, but not if there's
no chance the bug has
title 324717 ATI R9100 DRI drivers lock up computer to hardware reset
thanks
since it now seems to be clearly an ATI DRI issue, let's have a more useful
bug title.
zw
Anthony Callegaro said:
> It seems that I have the exact same issue. Since 6.8.2.dfsg.1-5 my PC
> was constantly crashing and needed an hardware reboot. I wasn't using
> DRI so I deactivated the nvidia drivers and the glx module in the
> xorg.conf and it seems that deactivating HW acceleration inde
Michel Dänzer said:
>> > First of all, does disabling the DRI work around the problem?
>>
>> I'll try that, but as I have no reliable way to reproduce the problem, I
>> will only be able to provide a guess, and that only after several days.
>> GL wasn't ever in use at the time of the crashes, thou
Michel Dänzer said:
> On Mon, 2005-08-22 at 20:47 -0700, Zack Weinberg wrote:
>> [...] since it was happening on a twice-daily basis
>> using the 6.8.2.dfsg.1-5 packages, and only happens once every few days
>> since I backed down to -4, that is where my suspicions lie
Several times now I've experienced a total freeze of my computer while X
is active. The machine is unresponsive to keyboard and network, and even
to the ATX soft-power button. It requires me to unplug its power cable
and reset the CMOS before it will boot again. I do not know for sure that
this
Package: libglu1-xorg
Version: 6.8.2.dfsg.1-3
Severity: wishlist
Tags: patch
The X.org implementation of libGLU is coded in C++, but it is intended
to expose only C interfaces. At present, many of the internal
interfaces are visible in the dynamic symbol table of the shared library,
which means t
Package: xfree86
Version: unavailable; reported 2003-03-01
Severity: wishlist
Tags: patch
As requested I'm re-transmitting this as a wishlist bug.
I edited the change to debian/xfree86-common.README.Debian so that it
now says "4.3.0-1" instead of "4.2.1-6". 4.2.1-6 is already out the
door, and I
Package: xfree86
Version: unavailable; reported 2003-03-01
Severity: wishlist
Tags: patch
As requested I'm re-transmitting this as a wishlist bug.
I edited the change to debian/xfree86-common.README.Debian so that it
now says "4.3.0-1" instead of "4.2.1-6". 4.2.1-6 is already out the
door, and I
This patch moves the UNIX domain sockets created by the X server, the
font server, and XIM input methods from various .subdirs of /tmp to
/var/run/X11, which directory is created at boot time by the existing
xfree86-common init script.
This change naturally has backward compatibility implications
This patch moves the UNIX domain sockets created by the X server, the
font server, and XIM input methods from various .subdirs of /tmp to
/var/run/X11, which directory is created at boot time by the existing
xfree86-common init script.
This change naturally has backward compatibility implications
The configuration for xserver-xfree86 wants to use a hardware-
detection program called discover. I can't find this program in any
package. Where do I get it? I'm using unstable.
zw
The configuration for xserver-xfree86 wants to use a hardware-
detection program called discover. I can't find this program in any
package. Where do I get it? I'm using unstable.
zw
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE
On Wed, Nov 22, 2000 at 12:11:34PM -0700, Marc Aurele La France wrote:
> On Fri, 3 Nov 2000, Zack Weinberg wrote:
>
> > I've just upgraded to XFree86 4.0.1 (thanks for the packages,
> > Branden!) and have encountered a bug in video mode detection with the
> > Mach6
On Wed, Nov 22, 2000 at 12:11:34PM -0700, Marc Aurele La France wrote:
> On Fri, 3 Nov 2000, Zack Weinberg wrote:
>
> > I've just upgraded to XFree86 4.0.1 (thanks for the packages,
> > Branden!) and have encountered a bug in video mode detection with the
> > Mach6
I've just upgraded to XFree86 4.0.1 (thanks for the packages,
Branden!) and have encountered a bug in video mode detection with the
Mach64 drivers.
Consider this XF86Config fragment:
Section "Monitor"
Identifier "ViewSonic E771"
HorizSync 30-70
VertRefresh 50-120
Modeline "102
I've just upgraded to XFree86 4.0.1 (thanks for the packages,
Branden!) and have encountered a bug in video mode detection with the
Mach64 drivers.
Consider this XF86Config fragment:
Section "Monitor"
Identifier "ViewSonic E771"
HorizSync 30-70
VertRefresh 50-120
Modeline "10
64 matches
Mail list logo
