Ubuntu Lucid Alpha - xterm screen corruption

[John Stoffel]

Hi all,

I'm running Ubuntu Lucid Alpha (I know, bleeding edge) on a x86_64 AMD
box with 4Gb of RAM and PCIe X1600 (RV535) card, using the VGA output
to an old HP monitor.  I'm using kernel 2.6.32-9-generic from Ubuntu,
since I'm also using KVM as well.

I'm also using the xorg-edgers PPA as well:

  deb http://ppa.launchpad.net/xorg-edgers/ubuntu lucid main 
  deb-src http://ppa.launchpad.net/xorg-edgers/ubuntu lucid main 

Here's what I have installed for Mesa and xserver:

    sail:~> apt-show-versions | grep radeon
    libdrm-radeon1/lucid uptodate 2.4.17+git20091230.c5c503b5-0ubuntu0sarvatt3
    libdrm-radeon1-dbg/lucid uptodate 2.4.17+git20091230.c5c503b5-0ubuntu0sarvatt3
    xserver-xorg-video-radeon/lucid uptodate 1:6.12.99+git20100104.48aa5064-0ubuntu0sarvatt
    xserver-xorg-video-radeon-dbg/lucid uptodate 1:6.12.99+git20100104.48aa5064-0ubuntu0sarvatt

    sail:~> apt-show-versions | grep mesa
    libgl1-mesa-dev/lucid upgradeable from 7.8.0~git20100107.d699b672-0ubuntu0sarvatt to 7.8.0~git20100113.50ae9c60-0ubuntu0sarvatt
    libgl1-mesa-dri/lucid upgradeable from 7.8.0~git20100107.d699b672-0ubuntu0sarvatt to 7.8.0~git20100113.50ae9c60-0ubuntu0sarvatt
    libgl1-mesa-glx/lucid upgradeable from 7.8.0~git20100107.d699b672-0ubuntu0sarvatt to 7.8.0~git20100113.50ae9c60-0ubuntu0sarvatt
    libglu1-mesa/lucid upgradeable from 7.8.0~git20100107.d699b672-0ubuntu0sarvatt to 7.8.0~git20100113.50ae9c60-0ubuntu0sarvatt
    libglu1-mesa-dev/lucid upgradeable from 7.8.0~git20100107.d699b672-0ubuntu0sarvatt to 7.8.0~git20100113.50ae9c60-0ubuntu0sarvatt
    mesa-common-dev/lucid upgradeable from 7.8.0~git20100107.d699b672-0ubuntu0sarvatt to 7.8.0~git20100113.50ae9c60-0ubuntu0sarvatt
    mesa-utils/lucid upgradeable from 7.8.0~git20100107.d699b672-0ubuntu0sarvatt to 7.8.0~git20100113.50ae9c60-0ubuntu0sarvatt

    > apt-show-versions |grep drm
    libdrm-intel1/lucid uptodate 2.4.17+git20091230.c5c503b5-0ubuntu0sarvatt3
    libdrm-nouveau1/lucid uptodate 2.4.17+git20091230.c5c503b5-0ubuntu0sarvatt3
    libdrm-radeon1/lucid uptodate 2.4.17+git20091230.c5c503b5-0ubuntu0sarvatt3
    libdrm-radeon1-dbg/lucid uptodate 2.4.17+git20091230.c5c503b5-0ubuntu0sarvatt3
    libdrm2/lucid uptodate 2.4.17+git20091230.c5c503b5-0ubuntu0sarvatt3

I will try upgrading later tonight to the absolute latest versions.  

The system runs fine, except that when I expand an xterm to the full
size of the screen (1280x1024), there's corruption on the lower 3-4
lines of the xterm.  I can still use it, and if I re-size things so
that I raise the bottom up about 20 lines (hard to know exactly and I
can measure since I'm not in front of the machine right now) the
corruption goes away.

Would a screen shot be helpful to show the issue?

My xorg.conf has the following section:

    Section "Device"
	    Identifier      "ATI Technologies Inc ATI Default Card"
	    Boardname       "VESA driver (generic)"
	    Busid           "PCI:3:0:0"
	    Driver          "radeon"
	    Screen  0
    EndSection
 
and my dmesg from bootup looks like this:

    [    2.542792] [drm] Initialized drm 1.1.0 20060810
    ...
    [    2.573541] ACPI: PCI Interrupt Link [APC6] enabled at IRQ 16
    [    2.573589] pci 0000:03:00.0: PCI INT A -> Link[APC6] -> GSI 16
    (level, low) -> IRQ 16
    [    2.573635] pci 0000:03:00.0: setting latency timer to 64
    [    2.573813] [drm] Initialized radeon 1.31.0 20080528 for
    0000:03:00.0 on minor 0
    [    2.575998] vga16fb: initializing
    [    2.576001] vga16fb: mapped to 0xffff8800000a0000
    [    2.576125] fb0: VGA16 VGA frame buffer device
    ...
    [   33.275014] [drm] Setting GART location based on new memory map
    [   33.275459] [drm] Loading R500 Microcode
    [   33.275463] platform radeon_cp.0: firmware: requesting
    radeon/R520_cp.bin
    [   33.282575] svc: failed to register lockdv1 RPC service (errno 97).
    [   33.288547] [drm] Num pipes: 1
    [   33.288554] [drm] writeback test succeeded in 1 usecs


Which makes me think I'm not using the proper DRM stuff, but who
knows.

Please let me know if there's any more information I can provide, or
tests I can run.

Thanks,
John