Mailinglist Archive: radeonhd (93 mails)

< Previous Next >
Re: [radeonhd] No 2D acceleration on r5xx
  • From: Alex Deucher <alexdeucher@xxxxxxxxx>
  • Date: Wed, 24 Mar 2010 03:29:01 -0400
  • Message-id: <a728f9f91003240029m71d2bc1fk8e2e974dd10b1d5c@xxxxxxxxxxxxxx>
On Tue, Mar 23, 2010 at 10:30 PM, maddox <maddox@xxxxxxxxxxxxx> wrote:
Hi,

I make test with two scenarios :

* scenario 1 - without KMS - 2D acceleration working
kernel : 2.6.33 with Con Kolivas BFS patch
$ cat /etc/modprobe.d/radeon.conf
options radeon modeset=0
X log : Xorg.0.log-scenario1

Lines from dmesg output :
[drm] Initialized drm 1.1.0 20060810
pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:01:00.0: setting latency timer to 64
[drm] Initialized radeon 1.32.0 20080528 for 0000:01:00.0 on minor 0


*scenario 2 - with KMS - 2D acceleration not working
kernel : 2.6.33 with Con Kolivas BFS patch
$ cat /etc/modprobe.d/radeon.conf
options radeon modeset=1
X log : Xorg.0.log-scenario2

radeonhd does not work with kms. If you want to use kms, you need to
use radeon (xf86-video-ati).

Alex


Lines from dmesg output :
[drm] Initialized drm 1.1.0 20060810
[drm] radeon kernel modesetting enabled.
radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
radeon 0000:01:00.0: setting latency timer to 64
[drm] radeon: Initializing kernel modesetting.
[drm] register mmio base: 0xFDEF0000
[drm] register mmio size: 65536
ATOM BIOS: 113
[drm] GPU reset succeed (RBBM_STATUS=0x10000140)
[drm] Generation 2 PCI interface, using max accessible memory
[drm] radeon: VRAM 256M
[drm] radeon: VRAM from 0x00000000 to 0x0FFFFFFF
[drm] radeon: GTT 512M
[drm] radeon: GTT from 0x20000000 to 0x3FFFFFFF
 alloc irq_desc for 26 on node -1
 alloc kstat_irqs on node -1
radeon 0000:01:00.0: irq 26 for MSI/MSI-X
[drm] radeon: using MSI.
[drm] radeon: irq initialized.
[drm] Detected VRAM RAM=256M, BAR=256M
[drm] RAM width 64bits DDR
[TTM] Zone  kernel: Available graphics memory: 2031302 kiB.
[drm] radeon: 256M of VRAM memory ready
[drm] radeon: 512M of GTT memory ready.
[drm] GART: num cpu pages 131072, num gpu pages 131072
[drm] RB2D reset succeed (RBBM_STATUS=0x10000140)
[drm] radeon: 1 quad pipes, 1 z pipes initialized.
[drm] PCIE GART of 512M enabled (table at 0x00040000).
[drm] radeon: cp idle (0x10000C03)
[drm] Loading R500 Microcode
platform radeon_cp.0: firmware: requesting radeon/R520_cp.bin
[drm] radeon: ring at 0x0000000020000000
[drm] ring test succeeded in 12 usecs
[drm] radeon: ib pool ready.
[drm] ib test succeeded in 0 usecs
[drm] Default TV standard: NTSC
[drm] Radeon Display Connectors
[drm] Connector 0:
[drm]   DVI-I
[drm]   HPD1
[drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[drm]   Encoders:
[drm]     CRT1: INTERNAL_KLDSCP_DAC1
[drm]     DFP1: INTERNAL_KLDSCP_TMDS1
[drm] Connector 1:
[drm]   S-video
[drm]   Encoders:
[drm]     TV1: INTERNAL_KLDSCP_DAC2
[drm] fb mappable at 0xD00C0000
[drm] vram apper at 0xD0000000
[drm] size 9216000
[drm] fb depth is 24
[drm]    pitch is 7680
Console: switching to colour frame buffer device 240x75
fb0: radeondrmfb frame buffer device
registered panic notifier
[drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0
mtrr: base(0xd0000000) is not aligned on a size(0xfff8000) boundary
[drm:radeon_cp_setparam_kms] *ERROR* invalid ioctl with kms
radeon_cp_setparam_kms
[drm:radeon_cp_init_kms] *ERROR* invalid ioctl with kms radeon_cp_init_kms


Maybe is not problem in radeonhd driver but in drm or radeon kernel driver.

Jan

On 03/15/2010 04:59 PM, Matthias Hopf wrote:

On Mar 14, 10 02:29:46 +1300, Jesse Yan wrote:


On 3/13/10, maddox<maddox@xxxxxxxxxxxxx>  wrote:


 I got it.
 I enable KMS for radeon driver test, but I have some problem with them.
 I revert back to radeonhd driver but I miss to disable KMS when radeon
kernel module is loaded.


(EE) KMS is disabled. This is good for us, because RADEONHD conflicts
with KMS.

I would've thought it was KMS conflicting with radeonhd, but the above
message was there in the Xorg.0.log. Wouldn't that rule KMS out, or is
there some other way of enabling KMS while still triggering that
message in radeonhd?


Either wrong log file, or the test isn't working as it should.

I guess.

Matthias



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

< Previous Next >
Follow Ups