Bug#542004: [xserver-xorg-video-mach64] Cannot load mach64.ko
Package: xserver-xorg-video-mach64 Version: 6.8.2-1 Severity: important --- Please enter the report below this line. --- DRI will not work with this old card. While there are kernel sources with mach64 in their name, no mach64.ko is built. This driver wants to load that. I used to make this module separately but that old trunk no longer compiles and is no longer supported. This bug might belong with the 2.6.30 kernel sources. --- System information. --- Architecture: i386 Kernel: Linux 2.6.30-davidb Debian Release: squeeze/sid 990 unstablewww.debian-multimedia.org 990 unstableftp.fr.debian.org 990 unstabledebian.tagancha.org 990 unstabledebian.scribus.net 990 unstabledebian.co.il 650 testing security.debian.org 650 testing debian.co.il 500 stable security.debian.org 500 stable dl.google.com 500 stable debian.co.il 500 oldstable debian.systs.org 500 lenny kde4.debian.net 500 kernel-dists-trunk kernel-archive.buildserver.net 500 intrepidppa.launchpad.net 500 experimentalansani.it 1 experimentalftp.debian.org --- Package information. --- Depends (Version) | Installed ==-+-= libc6 (= 2.3) | 2.9-25 xserver-xorg-core (= 2:1.6.2) | 2:1.6.3-1+b1 Package's Recommends field is empty. Package's Suggests field is empty. -8---8---8---8---8---8---8---8---8-- Please attach the file: /tmp/reportbug-ng-xserver-xorg-video-mach64-jTQw4_.txt to the mail. I'd do it myself if the output wasn't too long to handle. Thank you! -8---8---8---8---8---8---8---8---8-- -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541235: xserver-xorg-video-ati: Random Lockups when DRI enabled
On Thu, 2009-08-13 at 11:01 +0200, Michel Dänzer wrote: Hmm. One thing I notice is that there's almost no EXA offscreen memory, due to your enormous Virtual directive. Normally this should only affect performance, not correctness, but it might be worth trying a smaller maximum desktop size just in case. Hello, I tried different configurations for my Virtual screen. Here are the logs (hope I've picked the right lines!): Virtual: 2944x1848 (BIG) (II) EXA(0): Offscreen pixmap area of 786432 bytes VirtuaL: NONE (II) EXA(0): Offscreen pixmap area of 11436032 bytes Virtual: 1920x1848 (VERTICAL) (II) EXA(0): Offscreen pixmap area of 12255232 bytes VirtuaL: 2944x1080 (HORIZONTAL) (II) EXA(0): Offscreen pixmap area of 14352384 bytes I thought that the configuration with most free memory would have been the second one (no virtual screen) but surprisingly to me it is not the case. Now I'm using the 2944x1080 (HORIZONTAL) Virtual screen with AGPMode 4 (default) and DRI enabled. The issues I had seem to be gone. However I cannot activate Compositing when I use my external screen since X consumes almost the 80% of the CPU when I move the windows around the screen. If I use my laptop monitor (1024x768) Compositing works quite well, although I experienced some lock-ups when I tried to modify the options of gnome-do in order to activate the Docky. Can we consider this bug closed? Can you do anything to prevent users to make the same mistakes I made? Thank you, Stefano -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542064: xserver-xorg: please include patches to fix idle time computation
Package: xserver-xorg
Version: 1:7.4+4
Severity: wishlist
Hi,
as explained in [0], gnome-power-manager 2.28 will stop including any of
the (not always working) kludges to work around the idle time
computation issues in the X server.
The author has provided supposedly correct patches to fix this behavior
to Xorg. The first patch has already been committed, and the second is
very small. It would be nice to have these fixes included in Debian
before g-p-m 2.28 is uploaded.
I’m attaching the patches.
[0]
http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/
Thanks,
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
From db568f9eabf3450d8a023597ff007df355b13ea8 Mon Sep 17 00:00:00 2001
From: Peter Hutterer peter.hutte...@who-t.net
Date: Thu, 13 Aug 2009 06:37:00 +
Subject: Xext: fix up wrong conditions for negative sync transitions.
If the counter had a value higher than the trigger value for a negative
transition, the trigger value did not get set.
The correct sequence of checks is:
if (positive transition)
if (counter value trigger value)
set up trigger
if (negative transition)
if (counter value trigger value)
set up trigger
Red Hat Bug 501601 https://bugzilla.redhat.com/show_bug.cgi?id=501601
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
diff --git a/Xext/sync.c b/Xext/sync.c
index 5f4ce56..667f8ab 100644
--- a/Xext/sync.c
+++ b/Xext/sync.c
@@ -962,28 +962,24 @@ SyncComputeBracketValues(SyncCounter *pCounter, Bool startOver)
pnewltval = psci-bracket_less;
}
}
- else if ( (pTrigger-test_type == XSyncPositiveTransition
+ else if (pTrigger-test_type == XSyncNegativeTransition
ct != XSyncCounterNeverIncreases)
- ||
- (pTrigger-test_type == XSyncNegativeTransition
+ {
+ if (XSyncValueGreaterThan(pCounter-value, pTrigger-test_value)
+ XSyncValueGreaterThan(pTrigger-test_value, psci-bracket_less))
+ {
+ psci-bracket_less = pTrigger-test_value;
+ pnewltval = psci-bracket_less;
+ }
+ }
+else if (pTrigger-test_type == XSyncPositiveTransition
ct != XSyncCounterNeverDecreases)
- )
{
- if (XSyncValueLessThan(pCounter-value, pTrigger-test_value))
+ if (XSyncValueLessThan(pCounter-value, pTrigger-test_value)
+ XSyncValueLessThan(pTrigger-test_value, psci-bracket_greater))
{
- if (XSyncValueLessThan(pTrigger-test_value,
- psci-bracket_greater))
- {
- psci-bracket_greater = pTrigger-test_value;
- pnewgtval = psci-bracket_greater;
- }
- else
- if (XSyncValueGreaterThan(pTrigger-test_value,
- psci-bracket_less))
- {
- psci-bracket_less = pTrigger-test_value;
- pnewltval = psci-bracket_less;
- }
+ psci-bracket_greater = pTrigger-test_value;
+ pnewgtval = psci-bracket_greater;
}
}
} /* end for each trigger */
--
cgit v0.8.2
From 9c5fcee00d247c5bcf8a9af3a2e332ea4416f7e8 Mon Sep 17 00:00:00 2001
From: Richard Hughes rich...@hughsie.com
Date: Mon, 17 Aug 2009 09:15:32 +0100
Subject: [PATCH 2/2] Do not reset lastDeviceEventTime when we do dixSaveScreens
When we turn off DPMS with DPMSModeOff and do dixSaveScreens, don't reset the
event time else session clients using IDLETIME will be reset.
---
dix/window.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/dix/window.c b/dix/window.c
index 32e26d9..1a645f6 100644
--- a/dix/window.c
+++ b/dix/window.c
@@ -3128,8 +3128,6 @@ dixSaveScreens(ClientPtr client, int on, int mode)
if (on == SCREEN_SAVER_FORCER)
{
- UpdateCurrentTimeIf();
- lastDeviceEventTime = currentTime;
if (mode == ScreenSaverReset)
what = SCREEN_SAVER_OFF;
else
--
1.6.2.5
signature.asc
Description: Ceci est une partie de message numériquement signée
Bug#541965: Resolved after update
after today's update dist-upgrade, the problem has disappeared. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#481529: No DRI with radeon 9200 SE: solved
Hi, I didn't notice the kernel message requesting radeon/R200_cp.bin Installing package linux-firmware solved the problem. Now DRI is enabled, Dimitri -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
