Mailinglist Archive: radeonhd (312 mails)

[Alex Deucher <alexdeucher@xxxxxxxxx>]

On 4/9/09, Gene Heskett <gene.heskett@xxxxxxxxxxx> wrote:
> Problem:
>  -------------------------Xorg.0.log-snippets----------------
>  (--) RADEONHD(0): Detected an RV610 on an unidentified card
>  (II) RADEONHD(0): Mapped IO @ 0xfdde0000 to 0xb800e000 (size 0x00010000)
>  (II) RADEONHD(0): PCIE Card Detected
>  (II) RADEONHD(0): Getting BIOS copy from legacy VBIOS location
>  (II) RADEONHD(0): ATOM BIOS Rom:
>         SubsystemVendorID: 0x1092 SubsystemID: 0x0710
>         IOBaseAddress: 0x6c00
>         Filename: SD303VTD.I1J
>         BIOS Bootup Message:
>  DM-HD610LG2-512
>
>  (II) RADEONHD(0): Analog TV Default Mode: 1
>  (II) RADEONHD(0): Found default TV Mode NTSC
>  (II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR
>  aperture.
>  (II) RADEONHD(0): Using only 262144kB of the total 524288kB.
>  (--) RADEONHD(0): VideoRAM: 262144 kByte
>  (II) RADEONHD(0): Framebuffer space used by Firmware (kb): 16
>  (II) RADEONHD(0): Start of VRAM area used by Firmware: 0x1fffc000
>  (II) RADEONHD(0): AtomBIOS requests 16kB of VRAM scratch space
>  (II) RADEONHD(0): AtomBIOS VRAM scratch base: 0x1fffc000
>  (WW) RADEONHD(0): rhdAtomAllocateFbScratch: FW FB scratch area 536854528
>  (size: 16384) extends beyond available framebuffer size 268435456
>  (II) RADEONHD(0): Cannot get VRAM scratch space. Allocating in main memory
>  instead
>  [...]
>  (WW) RADEONHD(0): Direct rendering for R600 and up forced on - This is NOT
>  officially supported yet and may cause instability or lockups
>  (II) RADEONHD(0): Found libdri 5.4.0.
>  drmOpenDevice: node name is /dev/dri/card0
>  drmOpenDevice: open result is -1, (No such device)
>  drmOpenDevice: open result is -1, (No such device)
>  drmOpenDevice: Open failed
>  drmOpenByBusid: Searching for BusID pci:0000:03:00.0
>  drmOpenDevice: node name is /dev/dri/card0
>  drmOpenDevice: open result is -1, (No such device)
>  drmOpenDevice: open result is -1, (No such device)
>  drmOpenDevice: Open failed
>  drmOpenByBusid: drmOpenMinor returns -19
>  [...]
>  drmOpenDevice: node name is /dev/dri/card14
>  drmOpenDevice: open result is -1, (No such device)
>  drmOpenDevice: open result is -1, (No such device)
>  drmOpenDevice: Open failed
>  (EE) RADEONHD(0): RHDDRIVersionCheck: drmOpen("radeon", "pci:0000:03:00.0")
>  failed.
>  (WW) RADEONHD(0): RHDDRIPreInit: Version check failed. Disabling DRI.
>  [...]
>  -----------------------
>  The kernel is 2.6.29.1-rc2, and dri is built in.  It also fails when it is a
>  module.
>
>  And my screen scrolling is maddening slow, 2 lines of text at a time, with a
>  nearly full second of screen redraw per 2 lines scrolled.  Cap that with 
> about
>  a 100ms delay to keyboard repeat, and there have been times when a finger on
>  the up or down arrow wasn't released quick enough, and that screen was
>  unusable for a couple minutes when the scrolling finally got caught up with
>  the 100x/second keyboard repeat, which does not respond to setting it for 
> half
>  a second and 5x a second in the bios, nor in the kconfig prefs.
>
>  Many Thanks for any help you can give me on this.

There is no r6xx/r7xx drm support in 2.6.29.  You need to use 2.6.30 or
you need to compile kernel modules from the r6xx-r7xx-support branch
of the drm.  Because of this, in your case you have no acceleration enabled, so
performance will be poor.  Unless you have the drm modules, it's best
to disable the drm and exa and stick with shadowfb (the default).
Enabling acceleration when the drm is not available will fall back to
direct framebuffer access rather than shadowfb, so it will be slower.

Alex
-- 
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx