Re: Xorg crash on HD6450
Le jeudi 20 février 2014 à 08:46 -0500, Alex Deucher a écrit : > On Wed, Feb 19, 2014 at 2:18 PM, Xavier Bestel wrote: > > Le mercredi 13 novembre 2013 à 12:19 +0900, Michel Dänzer a écrit : > >> On Die, 2013-11-12 at 16:15 +0100, Xavier Bestel wrote: > >> > > >> > is the following kernel Oops expected ? > >> > >> An oops is not expected by definition. > >> > >> > >> > It happens right when starting Xorg, on a kernel 2.12-rc7 (from debian). > >> > If not I'll file a bug. > >> > >> Please try 3.12 final first. If the problem persists, it would be great > >> if you could bisect. > > > > I just tried exchanging cards again, and now the Oops is gone. > > But instead I have something really strange: audio sometimes works for a > > few seconds (but often not), and thereafter if I try something like > > aplay sound.wav it's stuck for a while and aborts saying something like > > "delay exceeded" (translated from french). > > > > Nothing in the logs, the only suspect line in the dmesg is: > > [ 31.762590] [drm:evergreen_hdmi_write_sad_regs] *ERROR* Couldn't read > > SADs: 0 > > but googling for it seems to show it's benign. > > > > Well, it's benign, but it also means your monitor doesn't provide > proper SAD information which may be why hdmi audio isn't working. In fact it's because I have a video projector on the hdmi connector and an audio amplifier on the dvi connector. I guess the driver is trying to get SAD on the videoproj, which doesn't work. When I unplug the videoproj the message disappears. > > When trying to play a video (with XBMC) everything stutters, but I guess > > it's just because of the A/V sync. > > > > > > I'm sorry I can't bisect that, this machine is quite heavily used so I'm > > back with the older HD2600 (but I would prefer the HD6450 to work, > > apparently it should have working multichannel sound through hdmi). And > > there are non-working kernels in the middle, and I wouldn't know where > > to start. > > But maybe I can try a few radeontool hacks or something. > > > Can you try with kernel 3.13? Multi-channel pcm supported for AMD hda > chips wasn't added until 3.13 IIRC. Well same problem. It worked once for a few seconds, then it blocked. And strangely enough the HD2600 doesn't work with debian's 3.13, the sound is too slow (bad sample rate), I had to go back to 3.12. Life of an AMD user isn't easy ... Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Xorg crash on HD6450
"Michel Dänzer" a écrit : >On Die, 2013-11-12 at 16:15 +0100, Xavier Bestel wrote: >> >> is the following kernel Oops expected ? > >An oops is not expected by definition. Well some are more expected than others, as in "ah, 2 connectors used on an hd64xx, yes known bug" (I made that up). That' why I ask. >> It happens right when starting Xorg, on a kernel 2.12-rc7 (from >debian). >> If not I'll file a bug. > >Please try 3.12 final first. If the problem persists, it would be great >if you could bisect. Problem is that I didn't find a kernel which work well. I'll see. Thanks, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: HDMI Audio for N/S Islands ?
On Sun, 2012-04-22 at 13:00 -0400, Alex Deucher wrote: > On Sun, Apr 22, 2012 at 8:49 AM, Jrmrch Linux wrote: > > Hi Everyone, > > > > according to this page : > > http://www.x.org/wiki/RadeonFeature#Feature_Matrix_for_Free_Radeon_Drivers > > , the HDMI Audio Output for N and S Islands are to develop. Is there anyone > > on the job ? > > > > I have a WIP patch here if someone wants to finish it up: > http://people.freedesktop.org/~agd5f/0001-WIP-port-of-hdmi-dp-audio-code-to-newer-kernel.patch Does that patch enable more than 2 channels (without resorting to A52-encoded audio) on capable chipsets ? I can't tell from the patch, the only thing I can see is int channels = r600_audio_channels(rdev); which doesn't look like there's much change. Thanks, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
HDMI audio routing (?)
Hi, apparently when starting the Xorg server (on an RV630), the HDMI audio packets are routed only on the first output with something plugged in and powered on. This causes it to route audio to the videoprojector (which has no audio output), not to the audio amplifier connected to the other DVI output. Is there any way to workaround this ? Thanks, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: fglxr ATI video driver disables USB Keyboard - fix? ; gre
Hi, On Wed, 2011-04-13 at 21:17 -0700, giovanni_re wrote: > I downloaded & apt-installed from the console the fglrx package [the > driver from the hw manufacturer] Then you're on the wrong list. This one is about the free radeon driver. Try asking for support on AMD's forums. Good luck, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: recommended ati graphic hardware
On Wed, 2011-01-26 at 14:29 +0100, Xavier Bestel wrote: > Hi, > > On Wed, 2011-01-26 at 13:03 +0100, Sebastian Niehaus wrote: > > Sorry, this may be off topic on a developers mailing list. > > > > > > I was searching if there is such a thing as a "Developer's Choice" in > > ATI Graphic hardware. > > > > I am looking for a silent card which works on Debian Squeeze > > (xserver-xorg-video-ati version 6.13.1). Performance is not an issue. > > I'm using an HD2600 under squeeze. I have updated the libdrm* packages > to the unstable version (2.4.23-0.0), I can't remember why and maybe > it's even unneeded, but otherwise I think it's all squeeze: > xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 > xserver-xorg-core 2:1.7.7-11 > libgl1-mesa-dri 7.8.2-2 > > It works well, does OpenGL sufficiently to run XBMC. Sometimes Xorg > happens to die when playing movies, but it's quite rare. Oh sorry, I realize I forgot an important component: kernel is 2.6.37-trunk-amd64 (from experimental), which probably explains why the newer libdrm, and is definitely *not* squeeze. I needed it for the newer KMS in there AFAIR. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: recommended ati graphic hardware
On Wed, 2011-01-26 at 16:03 +0100, Sebastian Niehaus wrote: > Xavier Bestel schrieb: > > No talk about the r600 driver. > > > Hm. Hm? The 3D part is handled by the r300 mesa driver for older cards (but not older than radeon 9700), and r600 for the newer ones (I can't remember the starting card). I don't know which cards are handled by the r600_dri.so bundled in squeeze. Note that I'm now speaking about things I barely know about. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: recommended ati graphic hardware
On Wed, 2011-01-26 at 15:40 +0100, Sebastian Niehaus wrote: > Jonathan Fischer Friberg schrieb: > > On Wed, Jan 26, 2011 at 1:29 PM, Xavier Bestel > <mailto:xavier.bes...@free.fr>> wrote: > > > > I was searching if there is such a thing as a "Developer's Choice" in > > > ATI Graphic hardware. > > [...] > > > > > Some kind of hardware matrix on a public web page would be /very/ cool > > > or some recommenations of currently availiable hardware. > > > > Maybe this is what you're looking for? > > http://free3d.org/ > > Thanks, this is great. If a bit outdated. No talk about the r600 driver. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: recommended ati graphic hardware
On Wed, 2011-01-26 at 15:29 +0100, Sebastian Niehaus wrote:
> Hi.
>
> Xavier Bestel schrieb:
> > On Wed, 2011-01-26 at 14:29 +0100, Xavier Bestel wrote:
>
> >>> I am looking for a silent card which works on Debian Squeeze
> >>> (xserver-xorg-video-ati version 6.13.1). Performance is not an issue.
>
> >> I'm using an HD2600 under squeeze. I have updated the libdrm* packages
> >> to the unstable version (2.4.23-0.0), I can't remember why and maybe
> >> it's even unneeded, but otherwise I think it's all squeeze:
> >> xserver-xorg-video-radeon 1:6.13.1-2+squeeze1
> >> xserver-xorg-core 2:1.7.7-11
> >> libgl1-mesa-dri 7.8.2-2
>
> > Oh sorry, I realize I forgot an important component: kernel is
> > 2.6.37-trunk-amd64 (from experimental), which probably explains why the
> > newer libdrm, and is definitely *not* squeeze. I needed it for the newer
> > KMS in there AFAIR.
>
> Yes, I read that KMS support has been added in a post-Squeeze kernel
> (2.6.34 IIRC. Squeeze has 2.6.32).
>
> At least *I* can live without KMS right now if the generic ("non-KMS")
> mode works fine.
For my part I prefer to have KMS because of the power-management of the
card. I don't know if you can live with a more recent kernel or if you
absolutely need a pure squeeze.
I may try booting into UMS mode, but that machine is heavily used a home
and rebooting isn't that easy. I'll tell you when/if I try.
> Thank you /very/ /much/ for your imput.
You're welcome :)
> Hint to ATI: I have to spend some money now. Perfomance is not an issue,
> silence is one. Money is not a big issue, open source drivers are. I
> really would appreciate an ATI solution otherwise I might consider an
> Intel mainboard and Graphic solution.
I don't think they're listening to you. The ATI guys here are just devs,
on a side-project (the main one being Catalyst). AFAICS OSS linux
support isn't a selling point (for now ?).
Xav
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: recommended ati graphic hardware
Hi, On Wed, 2011-01-26 at 13:03 +0100, Sebastian Niehaus wrote: > Sorry, this may be off topic on a developers mailing list. > > > I was searching if there is such a thing as a "Developer's Choice" in > ATI Graphic hardware. > > I am looking for a silent card which works on Debian Squeeze > (xserver-xorg-video-ati version 6.13.1). Performance is not an issue. I'm using an HD2600 under squeeze. I have updated the libdrm* packages to the unstable version (2.4.23-0.0), I can't remember why and maybe it's even unneeded, but otherwise I think it's all squeeze: xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 xserver-xorg-core 2:1.7.7-11 libgl1-mesa-dri 7.8.2-2 It works well, does OpenGL sufficiently to run XBMC. Sometimes Xorg happens to die when playing movies, but it's quite rare. > Some kind of hardware matrix on a public web page would be /very/ cool > or some recommenations of currently availiable hardware. Fully agreed ! Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: HDMI audio on HD 2600 not working
Le dimanche 09 janvier 2011 à 10:06 +0100, Xavier Bestel a écrit : > Hi, > > I've just bought an (used) HDMI audio amp (Yamaha RX-V1600) and tried to > connect it to my HTPC (pc running XBMC, debian/squeeze using > xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 + kernel 2.6.37-rc7-amd64, > with a Radeon RH 2600), via a DVI-to-HDMI cable. There are 2 cables > running from the card, one to the amp, an other one to a monitor. So now it sort-of works, but I have to boot with the monitor disconnected, then plug it afterwards. I have some "stereo mode not supported" messages in the log, but I can hear some sound. So first question: why is that, and how to make sound go to the right connector ? I tried switching the connectors, but same result. I don't switch off that machine very often, but having to unplug/replug isn't that practical. Then, I have a little problem: there's only a 2-channels mode supported. When using speaker-test from ALSA package, all other configuration result in: [r...@awak:~]$ LANG=C speaker-test -D hw:1,3 -c 5 speaker-test 1.0.23 Playback device is hw:1,3 Stream parameters are 48000Hz, S16_LE, 5 channels Using 16 octaves of pink noise Channels count (5) not available for playbacks: Invalid argument Setting of hwparams failed: Invalid argument Passthrough-mode with DTS or Dolby works, but as it causes its share of troubles I'd prefer for n-channels (with n!=2) to work. Does someone know how do to that ? Thanks, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: HDMI audio on HD 2600 not working
Le dimanche 09 janvier 2011 à 10:06 +0100, Xavier Bestel a écrit : > Hi, > > I've just bought an (used) HDMI audio amp (Yamaha RX-V1600) and tried to > connect it to my HTPC (pc running XBMC, debian/squeeze using > xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 + kernel 2.6.37-rc7-amd64, > with a Radeon RH 2600), via a DVI-to-HDMI cable. There are 2 cables > running from the card, one to the amp, an other one to a monitor. If that can help, here's a bit of log: [9.040206] [drm] radeon kernel modesetting enabled. [9.040264] radeon :01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [9.040270] radeon :01:00.0: setting latency timer to 64 [9.042764] [drm] initializing kernel modesetting (RV630 0x1002:0x9589). [9.100919] [drm] register mmio base: 0xE040 [9.100922] [drm] register mmio size: 65536 [9.101185] ATOM BIOS: GV [9.101212] radeon :01:00.0: VRAM: 512M 0x - 0x1FFF (512M used) [9.101214] radeon :01:00.0: GTT: 512M 0x2000 - 0x3FFF [9.101648] [drm] Detected VRAM RAM=512M, BAR=256M [9.101651] [drm] RAM width 128bits DDR [9.136058] [TTM] Zone kernel: Available graphics memory: 2029842 kiB. [9.136061] [TTM] Initializing pool allocator. [9.136083] [drm] radeon: 512M of VRAM memory ready [9.136085] [drm] radeon: 512M of GTT memory ready. [9.136144] radeon :01:00.0: irq 44 for MSI/MSI-X [9.136150] radeon :01:00.0: radeon: using MSI. [9.136179] [drm] radeon: irq initialized. [9.136182] [drm] GART: num cpu pages 131072, num gpu pages 131072 [9.137748] [drm] Loading RV630 Microcode [9.638417] radeon :01:00.0: WB enabled [9.670180] [drm] ring test succeeded in 1 usecs [9.670302] [drm] radeon: ib pool ready. [9.670377] [drm] ib test succeeded in 0 usecs [9.670379] [drm] Enabling audio support [9.670386] failed to evaluate ATIF got AE_BAD_PARAMETER [9.670629] [drm] Radeon Display Connectors [9.670631] [drm] Connector 0: [9.670632] [drm] DVI-I [9.670634] [drm] HPD1 [9.670636] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [9.670638] [drm] Encoders: [9.670639] [drm] DFP1: INTERNAL_KLDSCP_TMDS1 [9.670641] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [9.670643] [drm] Connector 1: [9.670644] [drm] DIN [9.670645] [drm] Encoders: [9.670647] [drm] TV1: INTERNAL_KLDSCP_DAC2 [9.670648] [drm] Connector 2: [9.670650] [drm] DVI-I [9.670651] [drm] HPD2 [9.670653] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [9.670655] [drm] Encoders: [9.670656] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [9.670658] [drm] DFP2: INTERNAL_LVTM1 ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
HDMI audio on HD 2600 not working
Hi, I've just bought an (used) HDMI audio amp (Yamaha RX-V1600) and tried to connect it to my HTPC (pc running XBMC, debian/squeeze using xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 + kernel 2.6.37-rc7-amd64, with a Radeon RH 2600), via a DVI-to-HDMI cable. There are 2 cables running from the card, one to the amp, an other one to a monitor. The problem is that I can't hear anything on the amp. Here are the outputs on the machine: [r...@awak:~]$ aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 Here's how I try to play something: [r...@awak:~]$ aplay -D hw:1,3 /usr/share/sounds/shutdown1.wav Playing WAVE '/usr/share/sounds/shutdown1.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo Warning: rate is not accurate (requested = 44100Hz, got = 48000Hz) please, try the plug plugin ... which does nothing (note that I don't fully dismiss the possibility I could have misconfigured that complex beast of an amp). I don't care too much about the wrong rate for now. When reading the apm's documentation, they say the HDMI device has to support HDCP. Could that be the problem ? Is there something to configure somewhere to have that activated ? Thanks, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Feature Request: GPU scaling
Hi, On Thu, 2010-11-25 at 23:57 +1100, Jamie Smith wrote: > Hi, > > I saw a previous post requesting this, but I've only just signed up to > the list and wasn't sure how to post a follow up. I'd also really > appreciate this feature. > > If I am not mistaken, previous versions of the driver used to force > some kind of flat (no dithering) GPU scaling when a program tried to > change to a resolution lower than the desktop, and KMS was not > enabled. This perhaps unintended behaviour allowed me to play old > games in Wine with a sharper(blocky) look which I preferred, instead > of washed out colour. With newer versions of the driver, it does not > seem to make any difference, and the programs change the resolution, > forcing my LCD monitor to use its crappy blurred scaling. Are you sure it's not just Wine taking advantage of RandR and changing resolution on the fly ? Maybe try to disable use of (X)RandR on Wine (if it's at all possible) to have it use some sort of software scaling. HTH, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Which one to buy ?
Here comes that time again: I have to buy a graphic card, I want to buy a radeon, not too long/wide (limited space in the box), reasonably recent and powerful, to be used in a debian/sid system. What do I buy if I want 3D (compiz at least) now, or at least very soon ? I guess if AMD pours money on linux support, it's because they want their stuff to be bought. But it's not clear yet when the latest gen is usable without fglrx. Thanks for your enlightened advices, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: [ANNOUNCE] xf86-video-ati 6.13.0
Hi, On Mon, 2010-04-05 at 12:18 -0400, Alex Deucher wrote: > > Major changes since the 6.12.x series > > - Add support for KMS (kernel modesetting) for r1xx-evergreen asics I think you meant r8xx-evergreen here. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#575287: Same here even with 2.6.32-4-amd64
On Thu, 2010-03-25 at 10:53 +0100, Julien Cristau wrote: > On Thu, Mar 25, 2010 at 09:47:43 +0100, Michel Dänzer wrote: > > > The above means that the X driver is using UMS whereas KMS is enabled in > > the kernel. This results in a conflict for hardware access and cannot > > work properly. > > > > It's usually caused by the radeon kernel module being loaded too late. > > > With the latest sid kernel udev should load the module on boot. dmesg > would give a clue as to why that didn't happen here. If you mean loading in the initrd, I think there's still a bug with the firmware not being present. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#515326: gdb trace
Le samedi 06 mars 2010 à 12:12 +0100, Brice Goglin a écrit : > On Thu, Mar 19, 2009 at 10:59:58AM +0100, Xavier Bestel wrote: > > Anything I could try ? > > Try a newer version, and maybe 6.12.191 with KMS ? I don't have an r300 anymore. On an r600, with 6.12.191 + KMS it's perfect. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#461153: Rotation on RV350
Le samedi 06 mars 2010 à 09:54 +0100, Brice Goglin a écrit : > On Wed, Mar 19, 2008 at 02:37:04PM +0100, Samuel Mimram wrote: > > Hi, > > > > The problem with rotation on RV350 (left of the screen not refreshed) > > does not seem to be present anymore with the > > 1:6.8.1~git20080302.a4398ac3-1 version of the ati driver. > > Xavier, are things working for you too now? Yes, rotation was working well - before I changed my RV350 for an R6xx. Sorry for not reporting it sooner. Thanks, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Radeon 9600XT for a developer
Hi, my old pc died, the new one has no AGP slot, so I have an unused radeon 9600XT AGP (it's an RV360) lying around. If a developer has a need for it, please contact me. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: HDMI Audio on
On Mon, 2009-12-07 at 16:41 +0100, Marius Gröger wrote: > Rafał Miłecki schrieb: > > I think no one is working on HDMI port to radeon. However Christian > > (author of HDMI for radeonhd) ported his work to KMS. Hopefully we > > will see this in 2.6.33-rc1. > > Well all that KMS stuff is a bit to bleeding edge for me - not that I > wouldn't trust that stuff but I rather stick with my distro kernels. > > Let me ask my original question the other way round: playing video on my > 3200HD over HDMI - would I actually benefit from using the radeon driver > (vs. the radeonhd), provided I somehow get the HDMI audio ported? > http://www.x.org/wiki/radeon says that this driver has (better) video > playback, but - without knowing any of the details - the radeonhd driver > seems to do fine so far. > > If you ask: why bother if your system is ok as it is? - well, I like to > run the "right" thing, so if there is more OSS focus on the radeon > driver I want to use it. Secondly, I like to optimize things, so if > there's a better driver I want to use it. I'm sure you know what I mean :-) Yes, of course. The "right" thing to do it to switch to KMS these days. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#515326: gdb trace
Le jeudi 19 mars 2009 à 11:00 +0100, Xavier Bestel a écrit : > Hi again, > > I could ssh to my machine during a hang. there's nothing in the log, > nothing in dmesg. I could gdb the X server and client (carousel) but the > traces make no sense to me: Xorg: (gdb) bt #0 0xb7f22424 in __kernel_vsyscall () #1 0xb7bb0b29 in ioctl () from /lib/i686/cmov/libc.so.6 #2 0xb79c0bed in drmDMA (fd=10, request=0xbff3dcfc) at ../../libdrm/xf86drm.c:1266 #3 0xb79474c7 in RADEONCPGetBuffer (pScrn=0x9a83f88) at ../../src/radeon_accel.c:594 #4 0xb7999823 in RADEONPrepareSolidCP (pPix=0x9db03d0, alu=3, pm=4294967295, fg=0) at ../../src/radeon_exa_funcs.c:92 #5 0xb777d44a in exaFillRegionSolid (pDrawable=0x9db03d0, pRegion=0x9db2448, pixel=0, planemask=4294967295, alu=) at ../../exa/exa_accel.c:1072 #6 0xb777edf2 in exaPolyFillRect (pDrawable=0x9db03d0, pGC=0x9d377d0, nrect=1, prect=0x9d4b51c) at ../../exa/exa_accel.c:751 #7 0x0817aad4 in damagePolyFillRect (pDrawable=0x9db03d0, pGC=0x9d377d0, nRects=1, pRects=0x9d4b51c) at ../../../miext/damage/damage.c:1404 #8 0x08089490 in ProcPolyFillRectangle (client=0x9d4b328) at ../../dix/dispatch.c:1769 #9 0x0808c51f in Dispatch () at ../../dix/dispatch.c:437 #10 0x080716f5 in main (argc=9, argv=0xbff3e064, envp=Cannot access memory at address 0xc0286431) at ../../dix/main.c:397 ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#515326: gdb trace
Hi again, I could ssh to my machine during a hang. there's nothing in the log, nothing in dmesg. I could gdb the X server and client (carousel) but the traces make no sense to me: carousel: (gdb) bt #0 0xb801f424 in __kernel_vsyscall () #1 0xb7cb0b59 in ioctl () from /lib/i686/cmov/libc.so.6 #2 0xb7bc6c5d in drmIoctl () from /usr/lib/libdrm.so.2 #3 0xb7bc6fab in drmCommandWrite () from /usr/lib/libdrm.so.2 #4 0xb78786de in ?? () from /usr/lib/dri/r300_dri.so #5 0x0004 in ?? () #6 0x0017 in ?? () #7 0x08df956c in ?? () #8 0x0004 in ?? () #9 0x08e014a8 in ?? () #10 0x3fda53c2 in ?? () #11 0x08df956c in ?? () #12 0xb7a798d4 in ?? () from /usr/lib/dri/r300_dri.so #13 0x08e014a8 in ?? () #14 0x08df4e08 in ?? () #15 0xbfd3d5a8 in ?? () #16 0xb78ad911 in _mesa_Finish () from /usr/lib/dri/r300_dri.so Backtrace stopped: frame did not save the PC X: (gdb) bt #0 0xb8030424 in __kernel_vsyscall () #1 0xb7cbdb59 in ioctl () from /lib/i686/cmov/libc.so.6 #2 0xb7acdc5d in drmIoctl () from /usr/lib/libdrm.so.2 #3 0xb7acdfab in drmCommandWrite () from /usr/lib/libdrm.so.2 #4 0xa76676de in ?? () from /usr/lib/dri/r300_dri.so #5 0x000b in ?? () #6 0x0017 in ?? () #7 0x0951cf64 in ?? () #8 0x0004 in ?? () #9 0x0951cf10 in ?? () #10 0x in ?? () (using xserver-xorg-video-radeon 1:6.11.0-1) Anything I could try ? Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#515326: xorg-video-radeon: OpenGL freezes on radeon 9600 XT
Le samedi 28 février 2009 à 19:26 +0100, Xavier Bestel a écrit : > I'll try bustype PCI sometime. Doesn't work: (**) RADEON(0): Forced into PCI mode (EE) RADEON(0): [pci] Out of memory (-12) (EE) RADEON(0): [pci] PCI failed to initialize. Disabling the DRI. (II) RADEON(0): [drm] removed 1 reserved context for kernel (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xf82c6000 at 0xb79fc000 (II) RADEON(0): [drm] Closed DRM master. (WW) RADEON(0): Direct rendering disabled ... and a white screen in compiz :/ Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#515326: xorg-video-radeon: OpenGL freezes on radeon 9600 XT
It happens again, even if Xorg tells: (==) RADEON(0): Using AGP 4x Curiously, playing with compiz doesn't do anything, it's just a screensaver (opengl slideshow). Maybe because transfering images to textures exercises the AGP bus too much. I'll try bustype PCI sometime. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#515326: xorg-video-radeon: OpenGL freezes on radeon 9600 XT
On Mon, 2009-02-16 at 16:19 -0500, Alex Deucher wrote: > On Mon, Feb 16, 2009 at 3:59 PM, Xavier Bestel wrote: > > Le lundi 16 février 2009 à 08:11 +0100, Michel Dänzer a écrit : > >> On Sun, 2009-02-15 at 17:40 +0100, Xavier Bestel wrote: > >> > > >> > when the screensaver runs for a while, Xorg deadlocks. > >> > Happens since latest experimental upgrade. > >> > >> Which of xserver-xorg-video-radeon, libgl1-mesa-dri or > >> linux-image-$(uname -r) were upgraded/installed from/to what versions > >> during that upgrade? Can you isolate which of them introduced the > >> problem? > > > > I upgraded them all. > > I could try to find the culprite if it's really necessary, but .. > > > >> > (==) RADEON(0): Using AGP 8x > >> > >> Does > >> > >> Option "AGPMode" "4" > > > > That was it, thanks. However, if my memory serves me good, there was a > > time when this option was needed for my card, and a version (last year) > > of xserver-xorg-video-radeon started to guess right how to configure my > > card. It seems the newest one has lost how to do it properly. > > I've added a quirk for your setup to ati git master: > 3c9e00c7f2ed494976713e8f77b729e0d76409db I had a quick look, I didn't know it was so specific ! Apparently from your commit, some 9600XT could run at mode 8 on some other chipsets. I doubt that (mine never run well at mode 8, and I changed motherboard twice). Thanks anyway, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#515326: xorg-video-radeon: OpenGL freezes on radeon 9600 XT
Le lundi 16 février 2009 à 08:11 +0100, Michel Dänzer a écrit : > On Sun, 2009-02-15 at 17:40 +0100, Xavier Bestel wrote: > > > > when the screensaver runs for a while, Xorg deadlocks. > > Happens since latest experimental upgrade. > > Which of xserver-xorg-video-radeon, libgl1-mesa-dri or > linux-image-$(uname -r) were upgraded/installed from/to what versions > during that upgrade? Can you isolate which of them introduced the > problem? I upgraded them all. I could try to find the culprite if it's really necessary, but .. > > (==) RADEON(0): Using AGP 8x > > Does > > Option "AGPMode" "4" That was it, thanks. However, if my memory serves me good, there was a time when this option was needed for my card, and a version (last year) of xserver-xorg-video-radeon started to guess right how to configure my card. It seems the newest one has lost how to do it properly. HTH, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Tearing problem at bigger overlay sizes
On Wed, 2009-01-14 at 18:47 +0200, Michel Dänzer wrote: > On Wed, 2009-01-14 at 17:35 +0100, Xavier Bestel wrote: > > On Tue, 2009-01-13 at 18:55 +0100, Matthias Hopf wrote: > > > On Jan 13, 09 18:39:10 +0100, Xavier Bestel wrote: > > > > > Because the chip might reorder memory writes, and decide for later > > > > > blocks to be pushed out first (or even pushed out to memory w/o > > > > > changing > > > > > the cache). That way you *could* see multiple tearings. > > > > > > > > I thought a cache flush acted like a barrier, i.e. even if reordered > > > > between them all writes before the flush should go. > > > > > > Yes, but the beam could already in the middle of the screen if you flush > > > only at the end of all blocks. > > > > That would mean the engine isn't way faster than the beam, which I > > thought was doubtful but after seeing the fillrate¹ of an r300 seems > > plausible: around 1 Gtex/s means an HD screen (1920*1080 = 2 Gpix) would > > take 2s to draw ... > > I must have missed something, it looks way too slow. > > Well for one, 1920 * 1080 is about two million pixels, not two > billion. :) Ahem *blushes* ... so we're down to .002s to draw an HD screen, 1/10th of a frame at 50Hz. I don't know what's the duration of a vblank with an LCD using reduced blanking, but it should fit in. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Tearing problem at bigger overlay sizes
On Tue, 2009-01-13 at 18:55 +0100, Matthias Hopf wrote: > On Jan 13, 09 18:39:10 +0100, Xavier Bestel wrote: > > > Because the chip might reorder memory writes, and decide for later > > > blocks to be pushed out first (or even pushed out to memory w/o changing > > > the cache). That way you *could* see multiple tearings. > > > > I thought a cache flush acted like a barrier, i.e. even if reordered > > between them all writes before the flush should go. > > Yes, but the beam could already in the middle of the screen if you flush > only at the end of all blocks. That would mean the engine isn't way faster than the beam, which I thought was doubtful but after seeing the fillrate¹ of an r300 seems plausible: around 1 Gtex/s means an HD screen (1920*1080 = 2 Gpix) would take 2s to draw ... I must have missed something, it looks way too slow. Xav 1. http://en.wikipedia.org/wiki/Comparison_of_ATI_Graphics_Processing_Units#Radeon_R300_.289xxx.2C_X10xx.29_series ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Tearing problem at bigger overlay sizes
On Tue, 2009-01-13 at 18:20 +0100, Matthias Hopf wrote: > On Jan 13, 09 18:07:13 +0100, Xavier Bestel wrote: > > On Tue, 2009-01-13 at 17:41 +0100, Matthias Hopf wrote: > > > > tear free. Sometimes the diagonal tear can be seen in one or more (2..4 > > > > > > > > segments out of 11) of the 100 line segments. This last point is really > > > > puzzling, this could indicate the graphics engine is just keeping up > > > > with the refresh, slightly slower or slightly faster. > > > > > > Could be a caching issue, pushing out the cache after each block might > > > help. > > > > Why not just after the last block ? > > Because the chip might reorder memory writes, and decide for later > blocks to be pushed out first (or even pushed out to memory w/o changing > the cache). That way you *could* see multiple tearings. I thought a cache flush acted like a barrier, i.e. even if reordered between them all writes before the flush should go. > Again, this is a lot of hand waving. Still, it might be an idea. As you say, it's only handwaving ... Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Tearing problem at bigger overlay sizes
On Tue, 2009-01-13 at 17:41 +0100, Matthias Hopf wrote: > > tear free. Sometimes the diagonal tear can be seen in one or more (2..4 > > segments out of 11) of the 100 line segments. This last point is really > > puzzling, this could indicate the graphics engine is just keeping up > > with the refresh, slightly slower or slightly faster. > > Could be a caching issue, pushing out the cache after each block might > help. Why not just after the last block ? ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: texturedvideo adapter truncated in fullscreen
On Mon, 2008-02-25 at 10:46 +0100, Michel Dänzer wrote: > On Mon, 2008-02-25 at 09:26 +0100, Xavier Bestel wrote: > > On Sun, 2008-02-24 at 23:53 +0100, Brice Goglin wrote: > > > Xavier Bestel wrote: > > > > Oh, and also I had to invert the adapters order (texturevideo in #0 and > > > > overlay in #1), otherwise no way to test it. But as it seems to use a > > > > bit more CPU, maybe the order should be dependant on wether composite is > > > > activated. > > > > > > > > > > mplayer -vo xv:port=74 did the trick here (xvinfo says that the textured > > > adaptor is #1 with ports 74-89). > > > > Ah, silly me ! I read the manpage too fast and tried xv:port=1 ... > > Anyway, as it's not so easy in totem and xine, and using the cmdline > > isn't so hype these days, I think it may make sense to use texturing by > > default with composite. > > Possibly, or it might be even better if the video players become > smarter, e.g. using the overlay when their window isn't redirected (say > in fullscreen mode) and a textured port otherwise (or when the overlay > isn't available). Or, if we can make both adaptors work equally well, > maybe we could merge them to a single one which automagically switches > between overlay and textured as appropriate :). One can dream... That means the player can discriminate between textured and overlay adaptors, and know if it's in a composited environment. More clientspace hackery. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: texturedvideo adapter truncated in fullscreen
On Sun, 2008-02-24 at 23:53 +0100, Brice Goglin wrote: > Xavier Bestel wrote: > > Oh, and also I had to invert the adapters order (texturevideo in #0 and > > overlay in #1), otherwise no way to test it. But as it seems to use a > > bit more CPU, maybe the order should be dependant on wether composite is > > activated. > > > > mplayer -vo xv:port=74 did the trick here (xvinfo says that the textured > adaptor is #1 with ports 74-89). Ah, silly me ! I read the manpage too fast and tried xv:port=1 ... Anyway, as it's not so easy in totem and xine, and using the cmdline isn't so hype these days, I think it may make sense to use texturing by default with composite. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
texturedvideo adapter truncated in fullscreen
Hi, I tested with joy the brand new texturedvideo adapted in git, on an r300 (radeon 9600 XT). It works ! It works under compiz ! And it wobbles and rotates on the cube, etc. Thanks :) There's a little trouble though: when I put the video fullscreen, the bottom of the video is blank. It's like the video height is limited to something like 1024 (my screen is 1920x1200). Oh, and also I had to invert the adapters order (texturevideo in #0 and overlay in #1), otherwise no way to test it. But as it seems to use a bit more CPU, maybe the order should be dependant on wether composite is activated. Thanks, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#461153: xserver-xorg-video-ati: rotation corrupts screen
On jeu, 2008-01-17 at 15:47 -0500, Alex Deucher wrote: > On Jan 17, 2008 2:48 PM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > > > > > > On jeu, 2008-01-17 at 13:00 -0500, Alex Deucher wrote: > > > On Jan 17, 2008 12:52 PM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > On jeu, 2008-01-17 at 10:50 -0500, Alex Deucher wrote: > > > > > On Jan 17, 2008 10:47 AM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > On Thu, 2008-01-17 at 10:42 -0500, Alex Deucher wrote: > > > > > > > On Jan 17, 2008 4:27 AM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > > > > > > > > On Thu, 2008-01-17 at 10:00 +0100, Michel Dänzer wrote: > > > > > > > > > On Wed, 2008-01-16 at 23:26 +0100, Xavier Bestel wrote: > > > > > > > > > > Package: xserver-xorg-video-ati > > > > > > > > > > Version: 1:6.7.198~git20080109.10e7636c-1 > > > > > > > > > > Severity: normal > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi again ... > > > > > > > > > > > > > > > > > > > > when I rotate display using > > > > > > > > > > xrandr -o 1 > > > > > > > > > > or > > > > > > > > > > xrandr --output DVI-0 --rotation left > > > > > > > > > > the display is corrupted. I can see some parts of the > > > > > > > > > > windows rotated, > > > > > > > > > > some part non-rotated, and some garbage everywhere. > > > > > > > > > > I'm using compiz. > > > > > > > > > > > > > > > > > > Then it can't work until xserver 1.5 due to previously > > > > > > > > > missing AIGLX > > > > > > > > > damage reporting. > > > > > > > > > > > > > > > > > > > > > > > > > > > > 01:00.0 VGA compatible controller: ATI Technologies Inc > > > > > > > > > > RV350 AR [Radeon 9600] > > > > > > > > > > > > > > > > > > Note that even without a GLX compositing manager, support for > > > > > > > > > accelerated rotation with R300 generation cards was only just > > > > > > > > > pushed to > > > > > > > > > the upstream Git repository. Also, AFAIK it's only working > > > > > > > > > correctly > > > > > > > > > with EXA at this point. > > > > > > > > > > > > > > > > Ok, fair enough. > > > > > > > > I've tried with metacity, and you're right it's damn slow. > > > > > > > > But the display is also corrupted. All the pixel on the right > > > > > > > > of the > > > > > > > > (non-rotated) screen are garbled, I'd say on the last fifth of > > > > > > > > the > > > > > > > > display. > > > > > > > > I took a screenshot, but on the screenshot everything is > > > > > > > > allright. So > > > > > > > > the corruption happens only on-screen. > > > > > > > > > > > > > > What version of the driver/xserver are you using? Earlier > > > > > > > version of > > > > > > > radeon had some bugs when it came to rotation. > > > > > > > > > > > > xserver 2:1.4.1~git20080105-1 > > > > > > xserver-xorg-video-ati 1:6.7.198~git20080109.10e7636c-1 > > > > > > > > > > Can you get a picture of the corruption maybe with a digital camera? > > > > > Also are you using EXA or XAA? > > > > > > > > Here are the pictures (1 from afar, 1 nearer). > > > > I hope attaching big files to a bug is ok. > > > > > > Can you post your xorg log and config? Does rotation work ok under > > > XAA? How about if you disable tiling (Option "ColorTiling" "False")? > > > Looks like an issue with damage and tiling. > > > > Disabling colortiling makes it work. > > Do I need to test something else ? > > does making your virtual area square help? > Virtual 2400 2400 Apparently yes. But now I tried the latest driver (including your rotated acceleration), and the lowest fifth of the screen isn't updated anymore (with colortiling on or off, virtual area square or rectangular). Still a damage problem apparently. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#461153: xserver-xorg-video-ati: rotation corrupts screen
On ven, 2008-01-18 at 12:28 +0100, Michel Dänzer wrote: > On Thu, 2008-01-17 at 20:48 +0100, Xavier Bestel wrote: > > > > Disabling colortiling makes it work. > > Do I need to test something else ? > > Can you try the new version in experimental, > 1:6.7.198~git20080117.6bd510a2-1? That should now accelerate the > rotation. Indeed it does, but the lowest fifth of the (non-rotated) screen is never repainted. So when I move a window, it looks like it goes 'underneath' that part. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#461153: xserver-xorg-video-ati: rotation corrupts screen
On jeu, 2008-01-17 at 13:00 -0500, Alex Deucher wrote: > On Jan 17, 2008 12:52 PM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > > > > > > On jeu, 2008-01-17 at 10:50 -0500, Alex Deucher wrote: > > > On Jan 17, 2008 10:47 AM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > > > > > > > > On Thu, 2008-01-17 at 10:42 -0500, Alex Deucher wrote: > > > > > On Jan 17, 2008 4:27 AM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > > > > > > On Thu, 2008-01-17 at 10:00 +0100, Michel Dänzer wrote: > > > > > > > On Wed, 2008-01-16 at 23:26 +0100, Xavier Bestel wrote: > > > > > > > > Package: xserver-xorg-video-ati > > > > > > > > Version: 1:6.7.198~git20080109.10e7636c-1 > > > > > > > > Severity: normal > > > > > > > > > > > > > > > > > > > > > > > > Hi again ... > > > > > > > > > > > > > > > > when I rotate display using > > > > > > > > xrandr -o 1 > > > > > > > > or > > > > > > > > xrandr --output DVI-0 --rotation left > > > > > > > > the display is corrupted. I can see some parts of the windows > > > > > > > > rotated, > > > > > > > > some part non-rotated, and some garbage everywhere. > > > > > > > > I'm using compiz. > > > > > > > > > > > > > > Then it can't work until xserver 1.5 due to previously missing > > > > > > > AIGLX > > > > > > > damage reporting. > > > > > > > > > > > > > > > > > > > > > > 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 > > > > > > > > AR [Radeon 9600] > > > > > > > > > > > > > > Note that even without a GLX compositing manager, support for > > > > > > > accelerated rotation with R300 generation cards was only just > > > > > > > pushed to > > > > > > > the upstream Git repository. Also, AFAIK it's only working > > > > > > > correctly > > > > > > > with EXA at this point. > > > > > > > > > > > > Ok, fair enough. > > > > > > I've tried with metacity, and you're right it's damn slow. > > > > > > But the display is also corrupted. All the pixel on the right of the > > > > > > (non-rotated) screen are garbled, I'd say on the last fifth of the > > > > > > display. > > > > > > I took a screenshot, but on the screenshot everything is allright. > > > > > > So > > > > > > the corruption happens only on-screen. > > > > > > > > > > What version of the driver/xserver are you using? Earlier version of > > > > > radeon had some bugs when it came to rotation. > > > > > > > > xserver 2:1.4.1~git20080105-1 > > > > xserver-xorg-video-ati 1:6.7.198~git20080109.10e7636c-1 > > > > > > Can you get a picture of the corruption maybe with a digital camera? > > > Also are you using EXA or XAA? > > > > Here are the pictures (1 from afar, 1 nearer). > > I hope attaching big files to a bug is ok. > > Can you post your xorg log and config? Does rotation work ok under > XAA? How about if you disable tiling (Option "ColorTiling" "False")? > Looks like an issue with damage and tiling. Disabling colortiling makes it work. Do I need to test something else ? Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#461153: xserver-xorg-video-ati: rotation corrupts screen
On jeu, 2008-01-17 at 13:00 -0500, Alex Deucher wrote: > On Jan 17, 2008 12:52 PM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > > > > > > On jeu, 2008-01-17 at 10:50 -0500, Alex Deucher wrote: > > > On Jan 17, 2008 10:47 AM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > > > > > > > > On Thu, 2008-01-17 at 10:42 -0500, Alex Deucher wrote: > > > > > On Jan 17, 2008 4:27 AM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > > > > > > On Thu, 2008-01-17 at 10:00 +0100, Michel Dänzer wrote: > > > > > > > On Wed, 2008-01-16 at 23:26 +0100, Xavier Bestel wrote: > > > > > > > > Package: xserver-xorg-video-ati > > > > > > > > Version: 1:6.7.198~git20080109.10e7636c-1 > > > > > > > > Severity: normal > > > > > > > > > > > > > > > > > > > > > > > > Hi again ... > > > > > > > > > > > > > > > > when I rotate display using > > > > > > > > xrandr -o 1 > > > > > > > > or > > > > > > > > xrandr --output DVI-0 --rotation left > > > > > > > > the display is corrupted. I can see some parts of the windows > > > > > > > > rotated, > > > > > > > > some part non-rotated, and some garbage everywhere. > > > > > > > > I'm using compiz. > > > > > > > > > > > > > > Then it can't work until xserver 1.5 due to previously missing > > > > > > > AIGLX > > > > > > > damage reporting. > > > > > > > > > > > > > > > > > > > > > > 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 > > > > > > > > AR [Radeon 9600] > > > > > > > > > > > > > > Note that even without a GLX compositing manager, support for > > > > > > > accelerated rotation with R300 generation cards was only just > > > > > > > pushed to > > > > > > > the upstream Git repository. Also, AFAIK it's only working > > > > > > > correctly > > > > > > > with EXA at this point. > > > > > > > > > > > > Ok, fair enough. > > > > > > I've tried with metacity, and you're right it's damn slow. > > > > > > But the display is also corrupted. All the pixel on the right of the > > > > > > (non-rotated) screen are garbled, I'd say on the last fifth of the > > > > > > display. > > > > > > I took a screenshot, but on the screenshot everything is allright. > > > > > > So > > > > > > the corruption happens only on-screen. > > > > > > > > > > What version of the driver/xserver are you using? Earlier version of > > > > > radeon had some bugs when it came to rotation. > > > > > > > > xserver 2:1.4.1~git20080105-1 > > > > xserver-xorg-video-ati 1:6.7.198~git20080109.10e7636c-1 > > > > > > Can you get a picture of the corruption maybe with a digital camera? > > > Also are you using EXA or XAA? > > > > Here are the pictures (1 from afar, 1 nearer). > > I hope attaching big files to a bug is ok. > > Can you post your xorg log and config? Does rotation work ok under > XAA? How about if you disable tiling (Option "ColorTiling" "False")? > Looks like an issue with damage and tiling. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461153 for info. I'll try colortiling. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#461153: xserver-xorg-video-ati: rotation corrupts screen
On Thu, 2008-01-17 at 10:42 -0500, Alex Deucher wrote: > On Jan 17, 2008 4:27 AM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > > On Thu, 2008-01-17 at 10:00 +0100, Michel Dänzer wrote: > > > On Wed, 2008-01-16 at 23:26 +0100, Xavier Bestel wrote: > > > > Package: xserver-xorg-video-ati > > > > Version: 1:6.7.198~git20080109.10e7636c-1 > > > > Severity: normal > > > > > > > > > > > > Hi again ... > > > > > > > > when I rotate display using > > > > xrandr -o 1 > > > > or > > > > xrandr --output DVI-0 --rotation left > > > > the display is corrupted. I can see some parts of the windows rotated, > > > > some part non-rotated, and some garbage everywhere. > > > > I'm using compiz. > > > > > > Then it can't work until xserver 1.5 due to previously missing AIGLX > > > damage reporting. > > > > > > > > > > 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AR > > > > [Radeon 9600] > > > > > > Note that even without a GLX compositing manager, support for > > > accelerated rotation with R300 generation cards was only just pushed to > > > the upstream Git repository. Also, AFAIK it's only working correctly > > > with EXA at this point. > > > > Ok, fair enough. > > I've tried with metacity, and you're right it's damn slow. > > But the display is also corrupted. All the pixel on the right of the > > (non-rotated) screen are garbled, I'd say on the last fifth of the > > display. > > I took a screenshot, but on the screenshot everything is allright. So > > the corruption happens only on-screen. > > What version of the driver/xserver are you using? Earlier version of > radeon had some bugs when it came to rotation. xserver 2:1.4.1~git20080105-1 xserver-xorg-video-ati 1:6.7.198~git20080109.10e7636c-1 Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#461153: xserver-xorg-video-ati: rotation corrupts screen
On Thu, 2008-01-17 at 10:50 -0500, Alex Deucher wrote: > On Jan 17, 2008 10:47 AM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > > > > On Thu, 2008-01-17 at 10:42 -0500, Alex Deucher wrote: > > > On Jan 17, 2008 4:27 AM, Xavier Bestel <[EMAIL PROTECTED]> wrote: > > > > On Thu, 2008-01-17 at 10:00 +0100, Michel Dänzer wrote: > > > > > On Wed, 2008-01-16 at 23:26 +0100, Xavier Bestel wrote: > > > > > > Package: xserver-xorg-video-ati > > > > > > Version: 1:6.7.198~git20080109.10e7636c-1 > > > > > > Severity: normal > > > > > > > > > > > > > > > > > > Hi again ... > > > > > > > > > > > > when I rotate display using > > > > > > xrandr -o 1 > > > > > > or > > > > > > xrandr --output DVI-0 --rotation left > > > > > > the display is corrupted. I can see some parts of the windows > > > > > > rotated, > > > > > > some part non-rotated, and some garbage everywhere. > > > > > > I'm using compiz. > > > > > > > > > > Then it can't work until xserver 1.5 due to previously missing AIGLX > > > > > damage reporting. > > > > > > > > > > > > > > > > 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AR > > > > > > [Radeon 9600] > > > > > > > > > > Note that even without a GLX compositing manager, support for > > > > > accelerated rotation with R300 generation cards was only just pushed > > > > > to > > > > > the upstream Git repository. Also, AFAIK it's only working correctly > > > > > with EXA at this point. > > > > > > > > Ok, fair enough. > > > > I've tried with metacity, and you're right it's damn slow. > > > > But the display is also corrupted. All the pixel on the right of the > > > > (non-rotated) screen are garbled, I'd say on the last fifth of the > > > > display. > > > > I took a screenshot, but on the screenshot everything is allright. So > > > > the corruption happens only on-screen. > > > > > > What version of the driver/xserver are you using? Earlier version of > > > radeon had some bugs when it came to rotation. > > > > xserver 2:1.4.1~git20080105-1 > > xserver-xorg-video-ati 1:6.7.198~git20080109.10e7636c-1 > > Can you get a picture of the corruption maybe with a digital camera? > Also are you using EXA or XAA? I'm using EXA. I'll try when I'm back home, if I remember to do it :) Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#461153: xserver-xorg-video-ati: rotation corrupts screen
On Thu, 2008-01-17 at 10:00 +0100, Michel Dänzer wrote: > On Wed, 2008-01-16 at 23:26 +0100, Xavier Bestel wrote: > > Package: xserver-xorg-video-ati > > Version: 1:6.7.198~git20080109.10e7636c-1 > > Severity: normal > > > > > > Hi again ... > > > > when I rotate display using > > xrandr -o 1 > > or > > xrandr --output DVI-0 --rotation left > > the display is corrupted. I can see some parts of the windows rotated, > > some part non-rotated, and some garbage everywhere. > > I'm using compiz. > > Then it can't work until xserver 1.5 due to previously missing AIGLX > damage reporting. > > > > 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AR [Radeon > > 9600] > > Note that even without a GLX compositing manager, support for > accelerated rotation with R300 generation cards was only just pushed to > the upstream Git repository. Also, AFAIK it's only working correctly > with EXA at this point. Ok, fair enough. I've tried with metacity, and you're right it's damn slow. But the display is also corrupted. All the pixel on the right of the (non-rotated) screen are garbled, I'd say on the last fifth of the display. I took a screenshot, but on the screenshot everything is allright. So the corruption happens only on-screen. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#459428: xserver-xorg-video-ati: "tossed event which came in late"
On sam, 2008-01-12 at 19:20 +0100, Brice Goglin wrote: > Let's wait a couple weeks and close it then if you haven't reproduced again. Great. I'm very good at procrastinating. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#459428: xserver-xorg-video-ati: "tossed event which came in late"
On dim, 2008-01-06 at 17:06 +0100, Xavier Bestel wrote: > On dim, 2008-01-06 at 16:24 +0100, Brice Goglin wrote: > > Does it happen all the time, even when idle? Or only when running > > compiz, 3d applications, anything CPU intensive that could prevent the > > server from processing events fast enough? > > I'm running compiz, nothing else extravagant. Apparently it happened at > startup, because now I'm watching the log and it doesn't happen any > more, even when moving/resizing windows. FWIW, I can't reproduce it now. Maybe the new version fixed something (but I didn't see anything in the git commits that could). Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#459428: xserver-xorg-video-ati: "tossed event which came in late"
On dim, 2008-01-06 at 16:24 +0100, Brice Goglin wrote: > Xavier Bestel wrote: > > since the very latest vesrion of this package (didn't happen in the > > previous experimental version), > > with 1:6.7.198~git20080101.f65374f5-1 ? or > 1:6.7.198~git20071223.ad3325f6-1 ? It didn't happen with 1:6.7.198~git20080101.f65374f5-1 but now it happens with 1:6.7.198~git20080102.30cab1db-1 > There are not many changes for your > hardware that could explain this behavior. Ah, I changed 1 thing in xorg.conf in-between: I uncommented Option "AGPMode" "4" (it looks like it helps with my lockups, so far so good). > > my Xorg.log is full of: > > tossed event which came in late > > mieqEnequeue: out-of-order valuator event; dropping. > > It apparently doesn't cause more harm than usual. > > > Does it happen all the time, even when idle? Or only when running > compiz, 3d applications, anything CPU intensive that could prevent the > server from processing events fast enough? I'm running compiz, nothing else extravagant. Apparently it happened at startup, because now I'm watching the log and it doesn't happen any more, even when moving/resizing windows. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
DMA IRQ ping-pong
Hi, I have an ATI radeon 9600 XT, and I'm tracking the debian experimental driver (last version is 1:6.7.198~git20080101.f65374f5-1). I still have some random lockups, but they are few and far between (say once or twice a week), so not so easy to track. On strange thing I have observed in the log is that the DMA IRQ allocated varies between the runs. Here's the diff between the last two logs: -(II) RADEON(0): [drm] dma control initialized, using IRQ 17 +(II) RADEON(0): [drm] dma control initialized, using IRQ 16 This time the version changed, but sometimes just a reboot can trigger this. It's always IRQ 16 or 17. Is that ok ? Thanks, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#457233: xserver-xorg-video-ati: freezes system after a few minutes with comiz on rv370
On mer, 2007-12-26 at 12:42 +0100, Brice Goglin wrote: > Xavier Bestel wrote: > > (BTW, I installed 1:6.7.197-1 from unstable and it's stable). > > > > You're saying that the same config (without any AGP options or so) works > with 197 while it wasn't with 6.7.197-git20071219.ce4fa1ce-1 ? Yes, I'm saying exactely that ! > There are only 4 upstream commits between these packages: > RADEON: check for xf86_crtc_clip_video_helper() in ... > Fix RN50 mode filtering. > RADEON: skip empty connectors when creating outputs > RADEON: add support for legacy radeons with DVI and ... > I am not sure anything is supposed to touch your board here... I'm not sure either, the only thing I see is that there's a new kernel: 2.6.23-2 (based on 2.6.23.10), but all changes look driver- or kvm-related. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#457233: xserver-xorg-video-ati: freezes system after a few minutes with comiz on rv370
On ven, 2007-12-21 at 10:09 +0100, Michel Dänzer wrote: > On Fri, 2007-12-21 at 10:02 +0100, Xavier Bestel wrote: > > On Fri, 2007-12-21 at 09:17 +0100, Michel Dnzer wrote: > > > On Fri, 2007-12-21 at 09:09 +0100, Xavier Bestel wrote: > > > > On Fri, 2007-12-21 at 08:53 +0100, Michel Dnzer wrote: > > > > > On Thu, 2007-12-20 at 22:18 +0100, Xavier Bestel wrote: > > > > > > > > > > > > (==) RADEON(0): Using AGP 8x > > > > > > > > > > Was the previous version (1:6.7.196-2?) using this rate as well? Does > > > > > Option "AGPMode" "4" help with the current version? > > > > > > > > The only available versions are 1:6.7.192-3 and 1:6.6.193-3, and I can't > > > > remember what 1:6.7.196-2 was setting as AGP mode. > > > > Do you want me to try one of them ? > > > > > > Do you know about http://snapshot.debian.net/ ? > > > > I keep being told about it, but I must have a bird's memory ... > > > > With 6.7.196-2 I see no interesting changes in the log, except maybe for > > that: > > -(II) RADEON(0): [drm] dma control initialized, using IRQ 16 > > +(II) RADEON(0): [drm] dma control initialized, using IRQ 17 > > > > I'll try forcing AGPmode when I get back home. > > Well, if 6.7.196-2 is still more stable, the difference isn't related to > AGPMode. In that case, it would be great if you could try isolating the > change that made things worse for you using git-bisect. You can start > the process in a checked out Git tree with > > git-bisect good 5022d006 > git-bisect bad ce4fa1ce Hi, I'm back from holidays and wanted to try that. However: [EMAIL PROTECTED]:~/git/Xorg/driver/xf86-video-ati]$ git-bisect bad ce4fa1ce fatal: Needed a single revision Do I have another mean to specify that commit ? (BTW, I installed 1:6.7.197-1 from unstable and it's stable). Thanks, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#457233: xserver-xorg-video-ati: freezes system after a few minutes with comiz on rv370
On Fri, 2007-12-21 at 09:17 +0100, Michel Dänzer wrote: > On Fri, 2007-12-21 at 09:09 +0100, Xavier Bestel wrote: > > On Fri, 2007-12-21 at 08:53 +0100, Michel Dnzer wrote: > > > On Thu, 2007-12-20 at 22:18 +0100, Xavier Bestel wrote: > > > > > > > > (==) RADEON(0): Using AGP 8x > > > > > > Was the previous version (1:6.7.196-2?) using this rate as well? Does > > > Option "AGPMode" "4" help with the current version? > > > > The only available versions are 1:6.7.192-3 and 1:6.6.193-3, and I can't > > remember what 1:6.7.196-2 was setting as AGP mode. > > Do you want me to try one of them ? > > Do you know about http://snapshot.debian.net/ ? I keep being told about it, but I must have a bird's memory ... With 6.7.196-2 I see no interesting changes in the log, except maybe for that: -(II) RADEON(0): [drm] dma control initialized, using IRQ 16 +(II) RADEON(0): [drm] dma control initialized, using IRQ 17 I'll try forcing AGPmode when I get back home. Thanks, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#457233: xserver-xorg-video-ati: freezes system after a few minutes with comiz on rv370
On Fri, 2007-12-21 at 08:53 +0100, Michel Dänzer wrote: > On Thu, 2007-12-20 at 22:18 +0100, Xavier Bestel wrote: > > > > this driver has always locked the machine randomly, but I could live > > with it. The latest experimental version though is unusable: after a few > > minutes the machine freezes (hard freeze, like a PCI bus lockup: not > > even ping works, but the keyboard leds are blinking). > > Note: the previous experimental version was more usable for me. > > > > Frankly I really don't know what I can do to help, because once frozen > > the machine is a brick. Does someone have a idea for that problem ? > > The best start is probably to try and isolate the change(s) that made > things worse for you. > > > > (==) RADEON(0): Using AGP 8x > > Was the previous version (1:6.7.196-2?) using this rate as well? Does > Option "AGPMode" "4" help with the current version? The only available versions are 1:6.7.192-3 and 1:6.6.193-3, and I can't remember what 1:6.7.196-2 was setting as AGP mode. Do you want me to try one of them ? (At present I can only access my box remotely, so I can install something else and see the log, but I can't test with compiz). Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Running xrandr on a remote client - possible?
On sam, 2007-12-15 at 00:07 +0100, Wolfgang Pfeiffer wrote: > Hi All > > Please CC me, if you respond: I'm not subscribed to this list. > > I'm looking for a way to run xrandr on a remote client after logging > in to this client via ssh, and manipulate > > * 1 the remote clients internal display > * 2 the remote clients external display (VGA/TV etc ...) You must first start the X server locally (on the remote client). Either by login in through gdm, or through ssh by stopping gdm and typing startx or something equivalent. Then you can login remotely through ssh and type; export DISPLAY=:0 and it should work. If you can't login locally on the remote client, then you'll have to know which user is logged in (often it's "gdm") and use its Xauthority credentials. IIRC something like: export XAUTHORITY=~gdm/.Xauthority but you may need to setup your permissions to be able to read this file (e.g. add yourself to the "gdm" group). Good luck, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: CTM: was Re: [radeonhd] Necessary for 3D
On Mon, 2007-10-08 at 12:35 +0200, Syren Baran wrote: > The R580 has (depending on modell) 48 processors each executing the same > command on different memory locations (though some may be sleeping, > depending on flow control). > The instruction set is very different from architectures i know. > A Sparcs RISC set is more or less a subset of x86 CISC set, but this ... > hmm, i still consider it wierd, but maybe it just takes time getting > used to. > > LLVM docs state it can produce code for Sparc and x86 (and intermediate > byte code) and mentions all kinds of optimisation strategies. > I doubt these strategies were developed with such a processor in mind. Ask Zack Rusin, he's working precisely on that: http://www.nabble.com/Vector-swizzling-and-write-masks-code-generation-t4528538.html Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: [radeonhd] Necessary for 3D
On Fri, 2007-10-05 at 18:17 +0200, Matthias Hopf wrote: > On Oct 05, 07 17:33:45 +0200, Xavier Bestel wrote: > > Now the obvious question: do you know if AMD & Novell have plans to have > > radeonhd work on new cards the day they are out, say from r8xx on ? > > We would love to have a long-term commitment, but obviously I cannot > speak for the AMD side, and I cannot comment on current negotiations. > > Sorry, this is getting too political, I think I stretched as far as I > can go in public. Oh, thanks a lot already. I was just trying to extort some (hard to find) information for a selfish buying decision. I guess the r300 driver will be good enough for a while yet. Thanks again, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: [radeonhd] Necessary for 3D
On Fri, 2007-10-05 at 15:47 +0200, Matthias Hopf wrote: > On Oct 05, 07 14:21:42 +0200, Xavier Bestel wrote: > > On Fri, 2007-10-05 at 14:15 +0200, Matthias Hopf wrote: > > > It'll be quite a while > > > until we will see 3D docs. At least that's my estimation. > > > > Does it mean buying an r6xx now is of no use ? I mean, r7xx could be out > > before the radeonhd driver can run compiz. > > It certainly will be. It's not too long until r7xx will be pushed. A 3D > driver is a complex beast, especially if done from the ground up. No, > r4xx code won't help, r6xx has a completely different engine. Now the obvious question: do you know if AMD & Novell have plans to have radeonhd work on new cards the day they are out, say from r8xx on ? Thanks, Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: [radeonhd] Necessary for 3D
On Fri, 2007-10-05 at 14:15 +0200, Matthias Hopf wrote: > It'll be quite a while > until we will see 3D docs. At least that's my estimation. Does it mean buying an r6xx now is of no use ? I mean, r7xx could be out before the radeonhd driver can run compiz. Xav ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
