Source: mesa
Version: 21.0.3-1
Severity: normal
Tags: patch
This patch fixes an incomplete application of an upstream fix for newer Navi22
card such as the 6700 XT resolving screen corruption issues
Upstream commit
https://gitlab.freedesktop.org/mesa/mesa/-/commit/ccc4abdbf4b889fd1467b237c7cc2d0d
Le 12/03/2020 à 18:36, Alex ARNAUD a écrit :
To compile Mesa 19 it involves the following dependencies that need to
be backported:
* meson
Meson 0.52 is now into buster-backports.
* libclc
I've contacted the OpenCL team to backport their software to
buster-backports.
I&#x
related packages
- Same for clang
Then it's mostly a matter of having rights and time to do it.
How can I help to make it progress?
Best regards,
Alex.
Le 11/03/2020 à 15:32, Alex ARNAUD a écrit :
Hello the Debian X Strike Force team,
I'd like to thank you for the work you made. I&
for those having the same issue like me?
Thanks in advance,
Alex.
for those having the same issue like me?
Thanks in advance,
Alex.
Thanks for the work you made to make Debian.
Best regards,
Alex.
Le 26/04/2018 à 16:56, Uwe Kleine-König a écrit :
The freedesktop guys are responsible for the kernel, too. So it was
addressed to the right people.
Right, but what's on Debian? Does the package xorg is relevant?
Best regards,
Alex.
shes regularly. I've spent one hour to figure out the
issue and to find this bug.
I've apply the work around to save my life but a regular user couldn't
do that.
Best regards,
Alex.
Package: Xdmx
Version: 1.19.3-2
Severity: important
Dear Maintainer,
Xdmx segfaults when starting it with Xdmx -display 192.168.102.57:0
-norender :1
I am not sure if the parameters are correct as I was setting it up, but
it should not segfault anyway.
The trace is:
(II) dmx[o0/192.168.102.57:0]
#x27;), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages xserver-xorg-video-intel depends on:
ii libc6 2.19-18+deb8u4
ii libdrm-intel1 2.4.70-1~bpo8+1
ii libdrm22.4.70-1~bpo8+1
ii libpciaccess0 0.13.2-3+b1
ii libpixman-1-0 0.32.6-3
ii libudev1 215-17+deb8u4
ii libx11-6 2:1.6.2-3
ii libx11-xcb12:1.6.2-3
ii libxcb-dri2-0 1.10-3+b1
ii libxcb-dri3-0 1.10-3+b1
ii libxcb-sync1 1.10-3+b1
ii libxcb-util0 0.3.8-3
ii libxcb11.10-3+b1
ii libxcursor11:1.1.14-1+b1
ii libxdamage11:1.1.4-2+b1
ii libxext6 2:1.3.3-1
ii libxfixes3 1:5.0.1-2+b2
ii libxinerama1 2:1.1.3-1+b1
ii libxrandr2 2:1.4.2-1+b1
ii libxrender11:0.9.8-1+b1
ii libxshmfence1 1.1-4
ii libxss11:1.2.2-1
ii libxtst6 2:1.2.2-1+b1
ii libxv1 2:1.0.10-1+b1
ii libxvmc1 2:1.0.8-2+b1
ii xserver-xorg-core [xorg-video-abi-18] 2:1.16.4-1
xserver-xorg-video-intel recommends no packages.
xserver-xorg-video-intel suggests no packages.
-- no debconf information
--
Alex ARNAUD
Visual-Impairment Project Manager
Hypra - "Humanizing technology"
ou appear to have disabled kms somehow and you are getting the vesa
driver rather than the native radeon driver.
Alex
> [18.639] (II) [KMS] drm report modesetting isn't supported.
> [18.639] (II) [KMS] drm report modesetting isn't supported.
> [18.639] (II) [KMS] dr
. Maybe Catalyst is a bit
> more forgiving or maybe there is some configuration issue here I don't
> understand.
>
> My problem is solved; there may still be a minor bug here in how the
> auto-configuration of the driver works.
The open source driver does not support YCbCr
mmand line in
grub or at runtime using xrandr (e.g., xrandr --output HDMI-0 --set
audio off). If that helps, can you try kernel 4.1?
Alex
>
> Owen Riddy
> Email: owen.ri...@gmail.com
> Mobile: 040 163 2663
>
> --
>
> On 18 May 2015 at 12:56, Michel Dänzer wrote:
>>
previous version was working correctly?
Does the problem only happen when you physically power off the
monitor? Does it come back ok when you let dpms kick in? How about
when you physically disconnect the monitor from the computer? Also,
what screensavers are you using? There may be a problema
the hw involved, this patch might help:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=66c2b84ba6256bc5399eed45582af9ebb3ba2c15
Alex
>
>Simon
>
> -- System Information:
> Debian Release: 8.0
> APT prefers testing
> APT policy: (990, 'testi
Cool, it works with the version from experimental -
2:2.99.911+git20140607-1~exp1 !
Also it seems that the source package has missing buid-deps, I had to
install these 3 package in order to build it on jessy:
libxcb-randr0-dev
libxcb-shape0-dev
libxcb-xfixes0-dev
Thanks,
Alex
On Tue, Jun 10
uot; "sna" didn't help me.
Also works fine via OpenGL.
Regards,
Alex
n't loading - only black screen. With working fglrx GNOME also
> loading
> in fallback mode. In Windows graphic card work correct.
>
Can you try a newer kernel? 3.2.0 is pretty old.
Alex
--
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/CADnq5_O0vRSrid4gB=�=cWfcD5JpD=w58vpf9pa0xdqjw...@mail.gmail.com
til the X driver is
> started.
>
> Furthermore, there's some additional initialization needed for the X
> driver itself to work, which for some reason only happens after
> starting & stopping X repeatedly.
>
>
> Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Is t
With KMS, the kernel driver inits and manages the hw so it
takes relatively longer to load and the ddx may try and access the
kernel driver before it's finished loading leading to fail.
Alex
>
> --
> Robert Millan
>
> ___
> xorg
ay want to use the driver without X, e.g., wayland, or
headless compute. Additionally, if you have the driver loaded you can
use advanced power management features and dpms which are not
available with vesa or vga mode.
Alex
>
> Cheers,
> Julien
>
> ___
wer kernel or if you are using EFI to boot, try
using the legacy bios option. Unfortunately, macs do just about
everything differently you may need some sort of mac specific quirk to
make it work properly, especially with EFI boot.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
w
On Wed, Apr 3, 2013 at 2:22 PM, Pablo Oliveira wrote:
> On Wed, Apr 3, 2013 at 3:34 PM, Alex Deucher wrote:
>>
>> On Tue, Apr 2, 2013 at 10:04 AM, Pablo Oliveira wrote:
>> > Package: xserver-xorg-video-ati
>> > Version: 1:6.14.4-8
>> > Followup-For: B
lems disappears completely.
To clarify, do you mean that after a dpms cycle both monitors work
correctly? Does a newer kernel help? 3.2 is pretty old. There were
a number of display related fixes that went into 3.7 for example.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ..
0,B1,B2,B3,B4,B5,B6,B7,B8,B9,BA,BB,BC,BD,BE,BF,C0,C1,C2,C3,C4,C5,C6,C7,C8,C9,CA,CB,CC,CD,CE,CF,D0,D1,D2,D3,D4,D5,D6,D7,D8,D9,DA,DB,DC,DD,DE,DF,E0,E1,E2,E3,E4,E5,E6,E7,E8,E9,EA,EB,EC,ED,EE,EF,F0,F1,F2,F3,F4,F5,F6,F7,F8,F9,FA,FB,FC,FD,FE,FF,ramlsfw
E: NAME="ACPI Virtual Keyboard Device"
E: P
ffer and the
compositor is responsible for updating the display buffer with the new
Xv data.
Alex
--
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/cadnq5_ovcej17kinr5uwwdedkv3rf-5mklxcmkoikso0_bl...@mail.gmail.com
o have this problem. Can anyone suggest ways in
> which I can troubleshoot/resolve it?
Can you try a newer kernel? 3.6 or 3.7? That may help with the
modesettings. As for the acceleration, corruption, you might try a
newer version of mesa.
Alex
--
To UNSUBSCRIBE, email
ack into Linux. I'm booting with grub-efi.
If apple uses the built in GPU backlight controller, it may work with
the new backlight control patches in my drm-3.7 branch:
http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.7-wip
Alex
--
To UNSUBSCRIBE, email to debian-x-req
writing from a different wheezy
> install).
Make sure you install the firmware package and that the firmware is
available in the initrd if you are using one.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm
When you switch VTs,
just the display base address is changed. The gamma is not changed.
I suspect this may affect other drivers as well so probably needs to
be fixed in common code.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsub
gt;
Also note that rendering can only be synchronized to one head at a
time to avoid tearing. If you have windows that span multiple heads,
you may get tearing on the non-synced heads.
Alex
--
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/CADnq5_PQq+-_nu+JyBMwAGsnpwL028pub1ZJE8ûHtyPv...@mail.gmail.com
Are we really sure it's a service to debian users or debian as a
distribution to simply remove compiz from wheezy based on a number of
minor(?) issues that are so obscure that they needed a fake RC bug?
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscri
On Mon, Mar 5, 2012 at 12:42 PM, Christopher Dow
wrote:
> Unfortunately, my problem is that I can't change the display modes to the
> native resolution. Even with one display disabled, I still can't set the
> native resolution. I get the same "input timing not supported" message every
> time
152x864
The xserver (not the driver) is picking 1152x864 since it's the
largest common mode supported by both monitors. You'll have to use
xrandr to choose a different mode (or specify different default modes
in your xorg.conf). Alternatively, you can start up X with one
monitor attached
b covers and more. The reason radeonfb is
still around is that it covers a few corner cases (suspend and resume
on ppc mac cards) which hasn't been ported over to radeon yet. On
x86, there is no reason to use radeonfb.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
On Sun, Jan 8, 2012 at 2:15 AM, Craig Small wrote:
> On Wed, Jan 04, 2012 at 09:48:50AM -0500, Alex Deucher wrote:
>> Is there any chance you are using a hybrid laptop with both Intel and
>> AMD GPUs in it? Based on your log this looks like it a MUX-less one
> It is definite
ernal
monitor port). We can double check by posting your dmesg output.
MUX-less systems aren't supported yet as we need a fair amount of drm
and X infrastructure to handle buffer sharing between GPUs and
decoupled display and rendering.
Alex
> - Craig
> --
> Craig Small VK2XLZ http:
On Mon, Nov 14, 2011 at 9:34 AM, Joost Kraaijeveld
wrote:
> On Mon, 2011-11-14 at 09:15 -0500, Alex Deucher wrote:
>> I would suggest using KMS rather than UMS. When you switch to KMS,
>> I'd also suggest using the r600 gallium 3D driver and removing the
>> Virtual line
appens when doing nothing with the system but when audio is
> playing. Running Gnome3 in the fallback mode works OK and no freeze happens.
>
I would suggest using KMS rather than UMS. When you switch to KMS,
I'd also suggest using the r600 gallium 3D driver and removing the
Virtual line
On Sun, Nov 13, 2011 at 1:34 PM, Iustin Pop wrote:
> On Thu, Nov 10, 2011 at 06:15:43PM +0100, Michel Dänzer wrote:
>> On Don, 2011-11-10 at 18:01 +0100, Michal Suchanek wrote:
>> > On 10 November 2011 17:46, Alex Deucher wrote:
>> > > On Wed, Nov 9, 2011
. However, it sounds
like you are using an environment that is mostly software rendering.
As such in order for the CPU to access tiled buffers, the GPU has to
copy them to a linear buffer before CPU can access it properly.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.deb
I can confirm the same activity as David. No longer segfaults.
The driver itself still seems regressed. It did work in Lenny, I cannot get a
usable screen through auto-detection with Squeeze or Wheezy.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscr
I was planning to update this machine to Wheezy, I can retest this. I still
owe the BTS another bug about the driver regression anyway, so I could
hopefully test that also.
- Original Message -
From: Daniel Kahn Gillmor
To: 605...@bugs.debian.org; 605051-submit...@bugs.debian.org
Cc:
On Mon, Aug 22, 2011 at 1:38 PM, Willian Gustavo Veiga
wrote:
> Of course I can Alex. It's attached.
> Thank you very much.
The radeon has no connectors specified in the vbios so it's muxless.
Not much we can do with it until X gets re-architected to decouple
display and
On Sun, Aug 21, 2011 at 1:13 PM, Willian Veiga wrote:
> Alex Deucher, I have an AMD Radeon HD 6470M but I can't select which
> card I want to use in the BIOS setup.
>
> How do I know if my GPU display is MUXes or MUX-less? I've tried to
> select the discrete card using
means the display
hardware is only attached to one of the GPUs and the other one is
strictly used for rendering. Unfortunately, the X server needs a lot
of work to support that scenario so it will not be supported any time
soon in the open source drivers.
Alex
--
To UNSUBSCRIBE, email to deb
scratch that; still broken on 1.10.1 in testing for laptop, just took
a while to trigger. following up in upstream bug
https://bugs.freedesktop.org/show_bug.cgi?id=26213
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@l
via patch Revert "dix: use the event mask of the grab for TryClientEvents."
http://cgit.freedesktop.org/xorg/xserver/patch/?id=1884db430a5680e37e94726dff46686e2218d525
http://lists.freedesktop.org/archives/xorg-announce/2010-July/001354.html
grabbutton would cause the input mask to be incorrectly
On Tue, May 24, 2011 at 4:00 PM, Tim Wootton wrote:
> On 22/05/11 21:49, Tim Wootton wrote:
>>
>> On 22/05/11 21:16, Alex Deucher wrote:
>>
>>>
>>> Are you using native DP or a DP to HDMI converter? If you are using a
>>> converter, is it
On Sun, May 22, 2011 at 3:37 PM, Tim Wootton wrote:
> On 22/05/11 00:06, Alex Deucher wrote:
>
>> Not a bug. Only 2 non-DP monitors are supported since there are only
>> two plls. If you want 3 or more monitors the rest have to be DP. The
>> fact that you can make it wo
nly 2 non-DP monitors are supported since there are only
two plls. If you want 3 or more monitors the rest have to be DP. The
fact that you can make it work with some fiddling is pure luck and is
completely unsupported. You end up with one of the plls driving two
monitors which only works
On Sun, May 8, 2011 at 7:13 PM, jamie wrote:
> Package: xserver-xorg-video-radeon
> Version: 1:6.14.1-1
> Severity: normal
>
>
> While actively working on my laptop, I experience no problems. However,
> when I am away from the machine for more than about 5 or 10 minutes, the
> screen either goes b
On Tue, Apr 26, 2011 at 4:41 PM, Andrew Rule wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 26/04/11 20:39, Alex Deucher wrote:
>> On Tue, Apr 26, 2011 at 3:56 AM, Andrew Rule wrote:
>> Hi,
>>
>> I also have this problem. It appeared for me w
If you want to fix UMS, you'll probably have to bisect
xf86-video-ati to find out what change caused the breakage. Your time
would be better off spend bisecting to see what caused the instability
with KMS.
Alex
>
> Please ask further questions if you need. I'm gonna try downgr
ent (gnome/kde/etc.) to decide what to do when the lid is
closed.
Alex
--
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/banlktin7bryszr++gqlwtyw0uar6p6m...@mail.gmail.com
Package: xserver-xorg-input-evdev
Version: 1:2.3.2-6
Severity: important
Tags: upstream
after a mouse is unplugged/replugged, X no longer sends any events except to
the current window; including the WM. xev running in background does not
receive motionNotify. affects both keyboard and mouse.
80
>
Since you are using gallium make sure it is built with llvm support as
that is very important for asics without vertex hardware. You can
also disable tear-free buffer swaps by adding:
Option "SwapbuffersWait" "FALSE"
to the device section of your xorg.conf. Th
On Sun, Mar 6, 2011 at 1:36 PM, Ben Hutchings wrote:
> On Sun, 2011-03-06 at 13:08 -0500, Alex Deucher wrote:
>> On Fri, Mar 4, 2011 at 8:50 PM, Ben Hutchings wrote:
>> > On Fri, 2011-03-04 at 21:01 +0200, Faidon Liambotis wrote:
>> >> severity 616301 critical
his
> applies to the X driver too.
>
With or without KMS, the userspace acceleration drivers can certainly
cause GPU hangs if the 3D engine is programmed with some combination
of commands it doesn't like.
Alex
> Ben.
>
> --
> Ben Hutchings
> Once a job is foule
> [ 21.248538] [drm] Loading RS780 Microcode
> [ 21.274940] [drm:r600_startup] *ERROR* Failed to load firmware!
Install the linux firmware package. rotation requires acceleration
and acceleration is not available without the firmware.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists
34578b
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=619efb105924d8cafa0c1dd9389e9ab506f5425d
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=a4b40d5d97f5c9ad0b7f4bf2818291ca184bb433
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif
On Mon, Feb 21, 2011 at 12:46 PM, Cyril Brulebois wrote:
> Hi!
>
> Alex Deucher (08/07/2009):
>> On Wed, Jul 8, 2009 at 8:22 AM, Jonathan Rafael
>> Ghiglia wrote:
>> > I can't mess up with this computer right now. I tried the packages
>> > from uns
On Mon, Feb 21, 2011 at 12:28 PM, Cyril Brulebois wrote:
> Hi Alberto/Alex,
>
> Alex Deucher (13/08/2007):
>> Hmmm... I didn't realize you were using an XPRESS chip. multi-head
>> is handling is not really working properly at the moment due to a
>> lack of d
Hi Cyril,
7.10-3 is the first version of Mesa which didn't freeze the machine
running Braid, and 7.10-2 did crash. I see 7.10-4 is available but I
didn't try it yet.
Alex
On 02/19/2011 12:05 PM, Cyril Brulebois wrote:
Alex Dănilă (19/02/2011):
After installing the newest
Hi,
After installing the newest Mesa, with Gallium3D enabled, I can play
Braid without crashes.
At least for me, this is fixed.
Thank you,
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.o
On Mon, Feb 14, 2011 at 4:09 PM, GSR wrote:
> Hi,
> jcris...@debian.org (2011-02-13 at 1104.39 +0100):
>> > back, the screen shows the bg (or maybe it was left from previous run)
>> > and then monitor goes into sleep immediately, ignoring kbd as original
>> > report.
>> You should probably trim yo
On Fri, Feb 11, 2011 at 5:06 PM, Gábor Melis wrote:
> GSR writes:
>
>> Hi,
>> daen...@debian.org (2011-02-11 at 1035.03 +0100):
>>> On Fre, 2011-02-11 at 05:54 +0100, GSR wrote:
>>> > Could you check MigrationHeuristic setting? And try with "greedy"?
>>> This option doesn't have any effect with c
On Fri, Dec 17, 2010 at 5:21 PM, Marcos Marado
wrote:
> Hello again,
>
> 2010/12/17 Alex Deucher :
>> 2010/12/16 Marcos Marado :
>>> 2010/12/16 Michel Dänzer :
>>>> On Mit, 2010-12-15 at 21:29 +, Marcos Marado wrote:
>>>>> After installin
100% CPU issue is gone.
> Unfortunately, the flickering issue (more often on black screens) is still
> present with kms, so for now I'm sticking with having it disabled.
>
> If you want to have doing some debugging/testing/whatever, feel free to ask...
>
Try booting with radeo
inux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=3a89b4a9ca7ce11e3b7d5119aea917b9fc29a302
Alex
--
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/aanlktikb22jt19-1ylzbdlf__xm+1jfwqotmrzgud...@mail.gmail.com
Package: libxaw7-dev
Version: 2:1.0.8-1
Apparently the dev package contains the library itself.
Unpacking libxaw7-dev (from .../libxaw7-dev_2%3a1.0.8-1_amd64.deb) ...
dpkg: error processing
/var/cache/apt/archives/libxaw7-dev_2%3a1.0.8-1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/libX
;
> I have tried every new possibly involved package when they are published in
> sid or experimental. But the issue is not solved.
>
Does booting with radeon.new_pll=0 help? Alternatively, you can try
Dave's drm-radeon-testing tree as it has some pll patches:
http://git.kernel.org/?p
work out of the box in that case.
>
> Done. Here you have both log files.
You have radeonfb loaded which is claiming the device preventing the
kms drm from loading.
Alex
>
> --
> Ivan Vilata i Balaguer -- http://ivan.lovesgazpacho.net/
>
> ___
figure out how to apply it even
>> manually. I'm using the debian linux-source-2.6.32 package, version
>> 2.6.32-23. Is there a better kernel source I could try to apply to?
>
> Probably linux-2.6's master?
Yes.
Alex
>
> Mraw,
> KiBi.
&
On Tue, Sep 7, 2010 at 6:48 AM, wrote:
> Hi,
>
>> Make sure the radeon drm is loaded before you start X.
>>
>> Alex
>>
>
> Radeon drm is loaded by xorg.conf which is loaded by X, isn't it? How can I
> get that to load before X starts?
>
For KMS, t
00 (RV250 4C66) 20090101 x86/MMX/SSE2 TCL
>> DRI2
>>
>> IMHO, that means some part of the graphical driver is loaded too late for the
>> system to detect hardware acceleration actually IS available.
>>
>> Any solutuions?
Make sure the radeon drm is loaded b
for return
> answer 1 6
> During some seconds, the main monitor get stranges color and lights intensity!
>
> It seem to be the same problem that the bug #569970 but I am not sure.
> Someone have an idea to solve this?
> Tell me if you need other logs or informations.
You need thi
On Fri, Aug 27, 2010 at 5:48 AM, Julien Cristau wrote:
> On Fri, Aug 27, 2010 at 11:14:15 +0200, janca wrote:
>
>> Kernel version (/proc/version):
>> Linux version 2.6.32-5-686 (Debian 2.6.32-20) (b...@decadent.org.uk) (gcc
>> version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Thu Aug 12 13:38:27 UTC 2010
>
Enabling KMS solved this. Please close.
Thank you for the solution,
Alex
On 08/01/2010 01:57 AM, Alex Dănilă wrote:
Hi,
thanks, I understand.
KMS is disabled on my computer because it breaks any rendering (Xorg
and virtual terminal). I guess I should first solve that...
By Javascript I
Enabling kernel modesetting solved this problem. As before, I didn't
manage to profile and see what's happening.
From my POV this bug can be closed. However, if you give me
instructions on how to profile, I'm willing to take some time and
provide the results.
Thanks,
Alex
O
On Mon, Aug 2, 2010 at 2:07 AM, Yann Dirson wrote:
> On Sun, Aug 01, 2010 at 10:12:27PM -0400, Alex Deucher wrote:
>> On Mon, Jul 26, 2010 at 3:21 PM, Yann Dirson wrote:
>> > Package: xserver-xorg-video-radeon
>> > Version: 1:6.13.1-2
>> > Severity: normal
&g
68 framebuffer and no connected outputs, and if you are
using kms and a hotplug enabled driver, you will get an event when a
monitor finally gets plugged in.
Alex
> -- Package-specific info:
> /var/lib/x11/X.roster does not exist.
>
> /var/lib/x11/X.md5sum does not exist.
>
> X ser
Hi,
thanks, I understand.
KMS is disabled on my computer because it breaks any rendering (Xorg and
virtual terminal). I guess I should first solve that...
By Javascript I meant fancy animations on the web, I can tell you, that
does work terribly without acceleration.
Alex
On 07/17/2010 01
Package: xorg
Version: 1:7.5+6
Severity: normal
After activating a screen the following symptoms happen (usually) less
than 10 seconds:
-the cursor is jerky
-moving a window or clicking does not seems to happen immediately
-shortcuts (ex. Alt+Tab) do not work, and typing is lagging.
This is no
Package: xorg
Version: 1:7.5+6
Severity: normal
Some types of acceleration are not availabe to the second simultaneous
log-in on the machine. I only say some types,
because some things work fast, others slow:
Fast:
-window resizing (both kwin and metacity)
-Opera animations, drawing, javascript
g
>> the X server, it outputs "radeonfb :00:10.0: Invalid ROM contents" there.
>
> Looks like radeonfb is preventing the radeon kernel module from working
> with kernel modesetting (KMS). Disable radeonfb or load radeon with
> modeset=0.
>
>
> P.S.
rk-s3-bios --quirk-s3-mode --quirk-dpms-suspend
> --quirk-test --quirk-radeon-off --quirk-s3-bios --quirk-s3-mode
Please try without any quirks. KMS shouldn't need them and they will
likely break things.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
wit
Package: xserver-xorg-video-intel
Version: 2:2.9.1-3
Severity: normal
I typically work for several hours, then X dies (screen goes black,) and after
a minute a GDM error comes up "Failed to start the X server". When I look at
the details, I see the "Failed to start submit batchbuffer: Input/Outp
On Sun, Apr 18, 2010 at 05:17:10PM +0200, Julien Cristau wrote:
> Please run
> /usr/share/bug/xserver-xorg/script 3>/tmp/xorg-bug-577996.txt
> and send the resulting file to this bug.
>
> Cheers,
> Julien
Attached.
--
Alex, homepage: http://www.bennee.com/~alex/
It
On Sun, Apr 18, 2010 at 01:48:40PM +0200, Julien Cristau wrote:
> On Sun, Apr 18, 2010 at 10:55:16 +0200, Alex wrote:
> > On Fri, Apr 16, 2010 at 01:11:33AM +0200, Cyril Brulebois wrote:
> > > Alex Bennee (15/04/2010):
> >
> > Seems more stable but have had it bla
On Fri, Apr 16, 2010 at 01:11:33AM +0200, Cyril Brulebois wrote:
> Hi,
>
> Alex Bennee (15/04/2010):
> > Since a recent update to sid (in the last 2 weeks) resume from
> > suspend has become unreliable.
>
>
> please upgrade your kernel from your current 2.6.32
Package: xorg
Version: 1:7.5+5
Severity: important
Tags: sid
Since a recent update to sid (in the last 2 weeks) resume from suspend has
become unreliable. Although the machine appears to resume OK I'm unable to
unlock X as the screen is blank. I've been unable to switch to console mode
(possibly d
ed to use the textured video adapter.
Alex
--
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/q2ua728f9f91004020757weda29e2t7944316194255...@mail.gmail.com
message in
> Xorg.0.conf telling:
>
> (WW) RADEON(0): Direct rendering is not supported when VGA arb is necessary
> for the device
> (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI.
I suspect you are missing the ucode needed by the chip. Make sure you
have the linu
o the kernel command line. -1 will use pci
gart rather than agp.
Alex
> - Fabian
>
>
>
> -- Package-specific info:
> /var/lib/x11/X.roster does not exist.
>
> /var/lib/x11/X.md5sum does not exist.
>
> X server symlink status:
> lrwxrwxrwx 1 root root 13 Apr 9
r maintainers.)
The fade effect done by adjusting the gamma (driver independent). The
gamma isn't changed when you switch VTs.
Alex
--
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/a728f9f91003240820x20588751y5493e69b4aa6c...@mail.gmail.com
On Fri, 2010-03-19 at 17:11 +0100, Brice Goglin wrote:
> The whole point is that glxgears reports something that is meaningless
> and we're trying to fight about it by hiding as much as possible all
> reports that show glxgears in big. Some distributions even hide the
> glxgears fps output by defau
On Fri, 2010-03-19 at 16:34 +0100, Brice Goglin wrote:
> Alex Hvostov wrote:
> > This issue happens to me, too. It is most definitely not solved.
> >
>
> There is nothing to solve in this report, glxgears is not a benchmark,
> so having a "slow glxgears" m
kernel/git/airlied/drm-2.6.git;a=commitdiff;h=7a9f0dd9c49425e2b0e39ada4757bc7a38c84873
http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=b4fe945405e477cded91772b4fec854705443dd5
Alex
>
>
> $dmesg
>
> [ 322.305400] [drm] Num pipes: 1
> [ 372.981310] ut-bin: pag
On Sat, Mar 13, 2010 at 3:57 AM, Michael Cree wrote:
> On 13/03/10 06:57, Alex Deucher wrote:
>>
>> On Fri, Mar 12, 2010 at 4:57 AM, Michael Cree wrote:
>>>
>>> On 10/03/10 08:44, Alex Deucher wrote:
>>>>>>>>
>>>
1 - 100 of 392 matches
Mail list logo
