Bug#461649: Follow-Up with pictures of black flickering bands
On Thu, Mar 20, 2008 at 4:35 PM, Stephen Benoit (Linux)
> Hi, Alex. Thanks for your reply.
> >> If you can think of any options I could try, including kernel modules
> >> (buggy intel_agp or radeonfb?), please let me know!
> > Does adjusting the DisplayPriority option help (see radeon man page)?
> > Some other options to try:
> > Option "BusType" "PCI"
> > Option "AGPMode" "X" where X is 1,2,4, or 8 (depending on your chipset)
> > Option "DRI" "False"
> At first, I thought DisplayPriority "HIGH" gave an improvement, but it
> did not last. BusType as "PCI" or "AGP" did not change the shaking.
> Turning off DRI made everything slower, of course, but I still have the
> problem. AGPMode 1, 2 and 4 have no noticeable change, 8 was rejected.
None of the other DisplayPriority options helped?
> BTW, I am using the drm module from the stock kernel 220.127.116.11. Are
> these versions current/appropriate? These are some exerpts from the
> kernel log:
> [ 23.896522] Linux agpgart interface v0.102
> [ 24.179208] agpgart: Detected an Intel 865 Chipset.
> [ 24.186347] agpgart: AGP aperture is 128M @ 0xf0000000
> [ 205.364257] [drm] Initialized drm 1.1.0 20060810
> [ 205.369473] [drm] Initialized radeon 1.28.0 20060524 on minor 0
> [ 207.225469] agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
> [ 207.225490] agpgart: Device is in legacy mode, falling back to 2.x
> [ 207.225501] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
> [ 207.225541] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
> [ 207.909309] [drm] Setting GART location based on new memory map
> [ 207.909364] [drm] writeback test succeeded in 1 usecs
> Thanks for looking into this! Any help is welcome.
Can you attach your X log and config?