radeonhd bug report

Tobias Koeck

9 Mar 2010 9 Mar '10

03:03

(II) RADEONHD: version 1.3.0, built from dist of git branch master, commit 8cbff7bf (II) Primary Device is: PCI 01@00:00:0 (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support (**) RADEONHD(0): Depth 24, (--) framebuffer bpp 32 (**) RADEONHD(0): Option "DRI" (**) RADEONHD(0): Selected EXA 2D acceleration. (II) RADEONHD(0): Card not in database: 0x9505:0x0000:0x0000; using generic modesetti ng. If - and only if - your card does not work or does not work optimally please contact radeonhd@opensuse.org to help rectify this. Use the subject: 0x9505:0x0000:0x0000: <name of board> and *please* describe the problems you are seeing in your message. (--) RADEONHD(0): Detected an RV670 on an unidentified card (II) RADEONHD(0): Mapped IO @ 0xfbce0000 to 0xb7ad5000 (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: 0x0000 SubsystemID: 0x0000 IOBaseAddress: 0xb000 Filename: 38504067.42H BIOS Bootup Message: ATI RADEON HD3850 I'm using a Radeon HD3850 HD 01:00.0 VGA compatible controller: ATI Technologies Inc RV670PRO [Radeon HD 3850] --- and the 2d acceleration doesn't work ... greetings tobias -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Show replies by date

maddox

10 Mar 10 Mar

02:27

New subject: No 2D acceleration on r5xx

Hi, I have problem with radeonhd driver. 2D acceleration doesn't work. (II) RADEONHD: version 1.3.0, built from git branch master, commit 79a0ab2f (II) Primary Device is: PCI 01@00:00:0 (EE) KMS is disabled. This is good for us, because RADEONHD conflicts with KMS. (II) RADEONHD(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 (==) RADEONHD(0): Depth 24, (--) framebuffer bpp 32 (**) RADEONHD(0): Option "AccelMethod" "EXA" (**) RADEONHD(0): Option "DRI" "true" (**) RADEONHD(0): Option "UseAtomBIOS" "true" (**) RADEONHD(0): Selected EXA 2D acceleration. (II) RADEONHD(0): Card not in database: 0x715F:0x1462:0x0680; using generic modesetting. If - and only if - your card does not work or does not work optimally please contact radeonhd@opensuse.org to help rectify this. Use the subject: 0x715F:0x1462:0x0680: <name of board> and *please* describe the problems you are seeing in your message. (--) RADEONHD(0): Detected an RV505 on an unidentified card (II) RADEONHD(0): Mapped IO @ 0xfdef0000 to 0x7f1334f66000 (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: 0x1462 SubsystemID: 0x0680 IOBaseAddress: 0xde00 Filename: SR25954.bin BIOS Bootup Message: 113-MSITV068MS.120 RV505CE SAMSUNG 32MX16 256MB (II) RADEONHD(0): Analog TV Default Mode: 1 (II) RADEONHD(0): Found default TV Mode NTSC (--) RADEONHD(0): VideoRAM: 262144 kByte (II) RADEONHD(0): Framebuffer space used by Firmware (kb): 20 (II) RADEONHD(0): Start of VRAM area used by Firmware: 0xfffb000 (II) RADEONHD(0): AtomBIOS requests 20kB of VRAM scratch space (II) RADEONHD(0): AtomBIOS VRAM scratch base: 0xfffb000 (II) RADEONHD(0): Default Engine Clock: 350000 (II) RADEONHD(0): Default Memory Clock: 400000 (II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Output: 1100000 (II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Output: 0 (II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Input: 13500 (II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Input: 1000 (II) RADEONHD(0): Maximum Pixel Clock: 400000 (II) RADEONHD(0): Reference Clock: 27000 (II) RADEONHD(0): Found libdri 5.4.0. drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: Open failed drmOpenByBusid: Searching for BusID pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 9, (OK) drmOpenByBusid: drmOpenMinor returns 9 drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 (II) RADEONHD(0): Found libdrm 1.3.0. (II) RADEONHD(0): Found radeon drm 2.0.0. (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Module "i2c" already built-in (II) RADEONHD(0): Default Engine Clock: 350000 (II) RADEONHD(0): GPIO_I2C_Clk_Mask: 0x1f90 (II) RADEONHD(0): GPIO_I2C_Clk_Mask_Shift: 0x0 (II) RADEONHD(0): GPIO_I2C_Data_Mask: 0x1f90 (II) RADEONHD(0): GPIO_I2C_Data_Mask_Shift: 0x8 (II) RADEONHD(0): I2C bus "RHD I2C line 0" initialized. (II) RADEONHD(0): GPIO_I2C_Clk_Mask: 0x1f94 (II) RADEONHD(0): GPIO_I2C_Clk_Mask_Shift: 0x0 (II) RADEONHD(0): GPIO_I2C_Data_Mask: 0x1f94 (II) RADEONHD(0): GPIO_I2C_Data_Mask_Shift: 0x8 (II) RADEONHD(0): I2C bus "RHD I2C line 1" initialized. (II) RADEONHD(0): GPIO_I2C_Clk_Mask: 0x1f98 (II) RADEONHD(0): GPIO_I2C_Data_Mask_Shift: 0x8 (II) RADEONHD(0): I2C bus "RHD I2C line 2" initialized. (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Module "ddc" already built-in (II) RADEONHD(0): Detected VGA mode. (**) RADEONHD(0): Using AtomBIOS for Crtcs (**) RADEONHD(0): Using AtomBIOS for PLLs (II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Output: 0 (II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Output: 1100000 (II) RADEONHD(0): Maximum Pixel Clock: 400000 (II) RADEONHD(0): Reference Clock: 27000 (II) RADEONHD(0): rhdAtomSetPixelClockVersion returned version 2 for index 0xc (II) RADEONHD(0): rhdAtomSetPixelClockVersion returned version 2 for index 0xc (II) RADEONHD(0): FB: Allocated Cursor Image at offset 0x00000000 (size = 0x00004000) (II) RADEONHD(0): FB: Allocated Cursor Image at offset 0x00004000 (size = 0x00004000) (II) RADEONHD(0): FirmwareInfo Revision 0103 (II) RADEONHD(0): Unused attribute: ul3DAccelerationEngineClock 0 (II) RADEONHD(0): Unused attribute: ulDriverTargetEngineClock 600000 (II) RADEONHD(0): Unused attribute: ulDriverTargetMemoryClock 600000 (II) RADEONHD(0): Unused attribute: ucASICMaxTemperature 0 (II) RADEONHD(0): Scary bits: Estimated MinEngineClock 250000 kHz (II) RADEONHD(0): Scary bits: Estimated MinMemoryClock 250000 kHz (II) RADEONHD(0): No VoltageObjectInfo table (II) RADEONHD(0): Default Engine Clock: 350000 (II) RADEONHD(0): Default Memory Clock: 400000 (II) RADEONHD(0): Current Engine Clock: 344250 (II) RADEONHD(0): Current Memory Clock: 396000 (WW) RADEONHD(0): Not supporting SetVoltage V1 yet (II) RADEONHD(0): Unused attribute: SET_VOLTAGE_GET_MAX_VOLTAGE: type 6 mode 1 index 0 (II) RADEONHD(0): Power Management: used engine clock / memory clock / core (VDDC) voltage (0: ignore) (II) RADEONHD(0): Power Management: Raw Ranges (II) RADEONHD(0): Minimum 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Maximum 562000 kHz / 362500 kHz / 0.000 V (II) RADEONHD(0): Default 350000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): PowerPlayInfo Revision 0000 (EE) RADEONHD(0): Unusupported PowerPlayInfo Revision (II) RADEONHD(0): Query for Get Chip Configs: not implemented (EE) RADEONHD(0): Power Management: Cannot get known good chip configurations (II) RADEONHD(0): Power Management: Validated Ranges (II) RADEONHD(0): Minimum 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Maximum 562000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Default 350000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Power Management: Final Levels (II) RADEONHD(0): Off 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Idle 350000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Slow2D 350000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Fast2D 350000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Slow3D 350000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Fast3D 350000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Max3D 562000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): User 350000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Connector[0] {RHD_CONNECTOR_DVI, "DVI-I DFP1 CRT1", RHD_DDC_0, RHD_HPD_0, { RHD_OUTPUT_TMDSA, RHD_OUTPUT_DACA } } (II) RADEONHD(0): Connector[1] {RHD_CONNECTOR_TV, "SVIDEO TV1", RHD_DDC_NONE, RHD_HPD_NONE, { RHD_OUTPUT_DACB, RHD_OUTPUT_NONE } } (**) RADEONHD(0): Using AtomBIOS for Outputs (II) RADEONHD(0): rhdAtomEncoderControlVersion(TMDSAEncoderControl) returned version 3 for index 0x1e (II) RADEONHD(0): rhdAtomSelectCrtcSourceVersion returned version 1 for index 0x2a (--) RADEONHD(0): Attaching Output AtomOutputTMDSA to Connector DVI-I 1 (**) RADEONHD(0): Using AtomBIOS for Outputs (II) RADEONHD(0): rhdAtomSelectCrtcSourceVersion returned version 1 for index 0x2a (--) RADEONHD(0): Attaching Output AtomOutputDACA to Connector DVI-I 1 (**) RADEONHD(0): Using AtomBIOS for Outputs (II) RADEONHD(0): rhdAtomSelectCrtcSourceVersion returned version 1 for index 0x2a (--) RADEONHD(0): Attaching Output AtomOutputDACB to Connector TV SVIDEO (II) RADEONHD(0): RandR: Adding RRoutput DVI-I_1/digital for Output AtomOutputTMDSA (II) RADEONHD(0): RandR: Adding RRoutput DVI-I_1/analog for Output AtomOutputDACA (II) RADEONHD(0): RandR: Adding RRoutput TV_SVIDEO for Output AtomOutputDACB (II) RADEONHD(0): Output DVI-I_1/digital has no monitor section (II) RADEONHD(0): Output DVI-I_1/digital has no monitor section (II) RADEONHD(0): Output DVI-I_1/analog has no monitor section (II) RADEONHD(0): Output TV_SVIDEO has no monitor section (II) RADEONHD(0): Calling DAC_LoadDetection (II) RADEONHD(0): DAC_LoadDetection Successful (II) RADEONHD(0): Setting AtomOutputTMDSA to incoherent (II) RADEONHD(0): I2C device "RHD I2C line 0:ddc2" registered at address 0xA0. (II) RADEONHD(0): I2C device "RHD I2C line 0:DDC control interface" registered at address 0x6E. ... (II) RADEONHD(0): FB: Allocated Offscreen Buffer at offset 0x01C28000 (size = 0x01998000) (II) RADEONHD(0): FB: Allocated DRI Back Buffer at offset 0x035C0000 (size = 0x01C20000) (II) RADEONHD(0): FB: Allocated DRI Depth Buffer at offset 0x051E0000 (size = 0x01C20000) (II) RADEONHD(0): FB: Allocated GART table at offset 0x0FFF8000 (size = 0x00008000, end of FB) (II) RADEONHD(0): FB: Allocated DRI Textures at offset 0x06E00000 (size = 0x09000000) (II) RADEONHD(0): Using 16 MB GART aperture (II) RADEONHD(0): Using 2 MB for the ring buffer (II) RADEONHD(0): Using 2 MB for vertex/indirect buffers (II) RADEONHD(0): Using 12 MB for GART textures (--) Depth 24 pixmap format is 32 bpp (II) RADEONHD(0): Mapped IO @ 0xfdef0000 to 0x7f1334f66000 (size 0x00010000) (II) RADEONHD(0): Mapped FB @ 0xd0000000 to 0x7f1320bd2000 (size 0x10000000) (II) RADEONHD(0): Attempting to enable power management (II) RADEONHD(0): Attempting to enable clock gating (II) RADEONHD(0): Current Engine Clock: 344250 (II) RADEONHD(0): Current Memory Clock: 396000 (WW) RADEONHD(0): Not supporting SetVoltage V1 yet (II) RADEONHD(0): Unused attribute: SET_VOLTAGE_GET_MAX_VOLTAGE: type 6 mode 1 index 0 (II) RADEONHD(0): Calling EnableCRTC (II) RADEONHD(0): EnableCRTC Successful (II) RADEONHD(0): Calling EnableCRTCMemReq (II) RADEONHD(0): EnableCRTCMemReq Successful (II) RADEONHD(0): Calling EnableCRTC (II) RADEONHD(0): EnableCRTC Successful (II) RADEONHD(0): Calling EnableCRTCMemReq (II) RADEONHD(0): EnableCRTCMemReq Successful drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 9, (OK) drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 9, (OK) drmOpenByBusid: Searching for BusID pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 9, (OK) drmOpenByBusid: drmOpenMinor returns 9 drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 (II) [drm] DRM interface version 1.3 (II) [drm] DRM open master succeeded. (II) RADEONHD(0): [drm] Using the DRM lock SAREA also for drawables. (II) RADEONHD(0): [drm] framebuffer handle = 0xd0000000 (II) RADEONHD(0): [drm] added 1 reserved context for kernel (II) RADEONHD(0): X context handle = 0x1 (II) RADEONHD(0): [drm] installed DRM signal handler (II) RADEONHD(0): [pci] 16384 kB allocated with handle 0x122ea900 (II) RADEONHD(0): [pci] ring handle = 0x2b800000 (II) RADEONHD(0): [pci] Ring mapped at 0x7f13209d1000 (II) RADEONHD(0): [pci] Ring contents 0x00000000 (II) RADEONHD(0): [pci] ring read ptr handle = 0x1b7fe000 (II) RADEONHD(0): [pci] Ring read ptr mapped at 0x7f1334f63000 (II) RADEONHD(0): [pci] Ring read ptr contents 0x00000000 (II) RADEONHD(0): [pci] vertex/indirect buffers handle = 0x2b7fe000 (II) RADEONHD(0): [pci] Vertex/indirect buffers mapped at 0x7f13207d1000 (II) RADEONHD(0): [pci] Vertex/indirect buffers contents 0x00000000 (II) RADEONHD(0): [pci] GART texture map handle = 0x2b801000 (II) RADEONHD(0): [pci] GART Texture map mapped at 0x7f131fc11000 (II) RADEONHD(0): [drm] register handle = 0xfdef0000 (II) RADEONHD(0): [dri] Visual configs initialized (WW) RADEONHD(0): [drm] failed to enable new memory map (II) RADEONHD(0): [drm] removed 1 reserved context for kernel (II) RADEONHD(0): [drm] unmapping 8192 bytes of SAREA 0x2b7ff000 at 0x7f1334f64000 (II) RADEONHD(0): [drm] Closed DRM master. (II) RADEONHD(0): Attempting to set Engine Clock to 350000 (II) RADEONHD(0): Current Engine Clock: 344250 (II) RADEONHD(0): Current Memory Clock: 396000 (WW) RADEONHD(0): Not supporting SetVoltage V1 yet (II) RADEONHD(0): Unused attribute: SET_VOLTAGE_GET_MAX_VOLTAGE: type 6 mode 1 index 0 (II) RADEONHD(0): Using MMIO Command Submission for acceleration. (II) EXA(0): Offscreen pixmap area of 26836992 bytes (II) EXA(0): Driver registered support for the following operations: (II) Solid (II) Copy (II) UploadToScreen (II) DownloadFromScreen (==) RADEONHD(0): Backing store disabled (==) RADEONHD(0): Silken mouse enabled (II) RADEONHD(0): RandR 1.2 enabled, ignore the following RandR disabled message. (II) RADEONHD(0): Calling BlankCRTC (II) RADEONHD(0): BlankCRTC Successful (II) RADEONHD(0): Calling BlankCRTC (II) RADEONHD(0): BlankCRTC Successful (II) RADEONHD(0): Calling BlankCRTC (II) RADEONHD(0): BlankCRTC Successful (II) RADEONHD(0): Calling BlankCRTC (II) RADEONHD(0): BlankCRTC Successful (II) RADEONHD(0): Calling BlankCRTC (II) RADEONHD(0): BlankCRTC Successful (II) RADEONHD(0): Calling BlankCRTC (II) RADEONHD(0): BlankCRTC Successful (II) RADEONHD(0): Calling TMDSAOutputControl (II) RADEONHD(0): TMDSAOutputControl Successful (II) RADEONHD(0): Calling TMDSAEncoderControl (II) RADEONHD(0): TMDSAEncoderControl Successful (II) RADEONHD(0): Calling DAC1OutputControl (II) RADEONHD(0): DAC1OutputControl Successful (II) RADEONHD(0): Calling DACAEncoderControl (II) RADEONHD(0): DACAEncoderControl Successful (II) RADEONHD(0): Calling DAC2OutputControl (II) RADEONHD(0): DAC2OutputControl Successful (II) RADEONHD(0): Calling DACBEncoderControl (II) RADEONHD(0): DACBEncoderControl Successful (II) RADEONHD(0): Calling EnableCRTC (II) RADEONHD(0): EnableCRTC Successful (II) RADEONHD(0): Calling EnableCRTCMemReq (II) RADEONHD(0): EnableCRTCMemReq Successful (II) RADEONHD(0): Calling EnableCRTC (II) RADEONHD(0): EnableCRTC Successful (II) RADEONHD(0): Calling EnableCRTCMemReq (II) RADEONHD(0): EnableCRTCMemReq Successful (II) RADEONHD(0): Calling TMDSAOutputControl (II) RADEONHD(0): TMDSAOutputControl Successful (II) RADEONHD(0): Calling EnableCRTC (II) RADEONHD(0): EnableCRTC Successful (II) RADEONHD(0): Calling EnableCRTCMemReq (II) RADEONHD(0): EnableCRTCMemReq Successful (II) RADEONHD(0): On Crtc 0 Setting 59.9 Hz Mode: Modeline "1680x1050" 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (II) RADEONHD(0): Calling SetCRTC_Timing (II) RADEONHD(0): SetCRTC_Timing Successful (II) RADEONHD(0): CallingSetCRTC_OverScan (II) RADEONHD(0): Set CRTC_OverScan Successful (II) RADEONHD(0): Calling EnableScaler (II) RADEONHD(0): EnableScaler Successful (II) RADEONHD(0): Calling SetPixelClock (II) RADEONHD(0): SetPixelClock Successful (II) RADEONHD(0): Calling SelectCRTCSource (II) RADEONHD(0): SelectCRTCSource Successful (II) RADEONHD(0): Calling EnableCRTCMemReq (II) RADEONHD(0): EnableCRTCMemReq Successful (II) RADEONHD(0): Calling EnableCRTC (II) RADEONHD(0): EnableCRTC Successful (II) RADEONHD(0): Calling TMDSAEncoderControl (II) RADEONHD(0): TMDSAEncoderControl Successful (II) RADEONHD(0): Calling TMDSAOutputControl (II) RADEONHD(0): TMDSAOutputControl Successful (II) RADEONHD(0): Calling DAC1OutputControl (II) RADEONHD(0): DAC1OutputControl Successful (II) RADEONHD(0): Calling DACAEncoderControl (II) RADEONHD(0): DACAEncoderControl Successful (II) RADEONHD(0): Calling DAC2OutputControl (II) RADEONHD(0): DAC2OutputControl Successful (II) RADEONHD(0): Calling DACBEncoderControl (II) RADEONHD(0): DACBEncoderControl Successful (II) RADEONHD(0): Calling EnableCRTC (II) RADEONHD(0): EnableCRTC Successful (II) RADEONHD(0): Calling EnableCRTCMemReq (II) RADEONHD(0): EnableCRTCMemReq Successful (==) RADEONHD(0): DPMS enabled (II) RADEONHD(0): Xv: No Textured Video possible without the Command Processor. Card : 01:00.0 VGA compatible controller: ATI Technologies Inc RV505 CE [Radeon X1550 64-bit] Regards Jan -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Matthias Hopf

11 Mar 11 Mar

16:23

New subject: No 2D acceleration on r5xx

On Mar 10, 10 03:27:40 +0100, maddox wrote:

...

I have problem with radeonhd driver. 2D acceleration doesn't work.

Please *always* provide a full log file. I have an idea, but the required information isn't included in the attached snippet. Matthias -- Matthias Hopf __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

maddox

18:38

New subject: No 2D acceleration on r5xx

On 03/11/2010 05:23 PM, Matthias Hopf wrote:

...

On Mar 10, 10 03:27:40 +0100, maddox wrote:

...
I have problem with radeonhd driver. 2D acceleration doesn't work.

Please *always* provide a full log file. I have an idea, but the required information isn't included in the attached snippet.

Matthias

I'm sorry... Full log file attached... Jan

Matthias Hopf

12 Mar 12 Mar

12:56

New subject: No 2D acceleration on r5xx

On Mar 11, 10 19:38:45 +0100, maddox wrote:

...

On 03/11/2010 05:23 PM, Matthias Hopf wrote:

...
On Mar 10, 10 03:27:40 +0100, maddox wrote:

...
I have problem with radeonhd driver. 2D acceleration doesn't work.

(WW) RADEONHD(0): [drm] failed to enable new memory map Hm. It has not been the amount of available memory (that's big enough), which I initially thought. You have to check your kernel version and the libdrm version. If both are the newest possible version (kernel 2.6.32 should suffice), then maybe the interface has changed in a backwards incompatible way?!? Matthias -- Matthias Hopf __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

maddox

20:26

New subject: No 2D acceleration on r5xx

On 03/12/2010 01:56 PM, Matthias Hopf wrote:

...

On Mar 11, 10 19:38:45 +0100, maddox wrote:

...
On 03/11/2010 05:23 PM, Matthias Hopf wrote:

...
On Mar 10, 10 03:27:40 +0100, maddox wrote:

...
I have problem with radeonhd driver. 2D acceleration doesn't work.

(WW) RADEONHD(0): [drm] failed to enable new memory map

Hm. It has not been the amount of available memory (that's big enough), which I initially thought. You have to check your kernel version and the libdrm version. If both are the newest possible version (kernel 2.6.32 should suffice), then maybe the interface has changed in a backwards incompatible way?!?

Matthias

I use Debian GNU/Linux squeeze/sid. libdrm 2.4.18-2 (from original Debian package) kernel 2.6.33 with Con Kolivas patches I tested kernel 2.6.32-7 from kernel.org and same problem. Any ideas? Jan -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

maddox

21:16

New subject: No 2D acceleration on r5xx

On 03/12/2010 09:26 PM, maddox wrote:

...

On 03/12/2010 01:56 PM, Matthias Hopf wrote:

...
On Mar 11, 10 19:38:45 +0100, maddox wrote:

...
On 03/11/2010 05:23 PM, Matthias Hopf wrote:

...
On Mar 10, 10 03:27:40 +0100, maddox wrote:

...
I have problem with radeonhd driver. 2D acceleration doesn't work. (WW) RADEONHD(0): [drm] failed to enable new memory map

Hm. It has not been the amount of available memory (that's big enough), which I initially thought. You have to check your kernel version and the libdrm version. If both are the newest possible version (kernel 2.6.32 should suffice), then maybe the interface has changed in a backwards incompatible way?!?

Matthias

I use Debian GNU/Linux squeeze/sid. libdrm 2.4.18-2 (from original Debian package) kernel 2.6.33 with Con Kolivas patches

I tested kernel 2.6.32-7 from kernel.org and same problem.

Any ideas?

Jan

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. Thanks for help and many thanks for developing radeonhd driver. Ragards Jan -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Jesse Yan

13 Mar 13 Mar

13:29

New subject: No 2D acceleration on r5xx

On 3/13/10, maddox 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.

Thanks for help and many thanks for developing radeonhd driver.

Ragards

Jan

(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? Jesse -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Matthias Hopf

15 Mar 15 Mar

15:59

New subject: No 2D acceleration on r5xx

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

...

On 3/13/10, maddox 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 -- Matthias Hopf __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

maddox

24 Mar 24 Mar

02:30

New subject: No 2D acceleration on r5xx

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 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 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

Alex Deucher

07:29

New subject: No 2D acceleration on r5xx

On Tue, Mar 23, 2010 at 10:30 PM, maddox 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 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@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

maddox

13:44

New subject: No 2D acceleration on r5xx

On Wed, 24 Mar 2010 03:29:01 -0400, Alex Deucher wrote

...

On Tue, Mar 23, 2010 at 10:30 PM, maddox 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

I know that radeonhd doesn't work with KMS but when I tested radeon driver with KMS I forget to disable KMS when moving back to radeonhd driver. In both X.org logs (as attachments in previous mail) are lines where radeonhd driver write message that KMS is disabled but its not true. KMS is enabled in scenario 2 but you can found message about disabled KMS in X.org log. It is little bit confusing. Jan

...

...
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 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@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

---------------------------------------- Freehosting PIPNI - http://www.pipni.cz/

---------------------------------------- Freehosting PIPNI - http://www.pipni.cz/ -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Matthias Hopf

15:09

New subject: No 2D acceleration on r5xx

On Mar 24, 10 13:44:42 +0000, maddox wrote:

...

In both X.org logs (as attachments in previous mail) are lines where radeonhd driver write message that KMS is disabled but its not true. KMS is enabled in scenario 2 but you can found message about disabled KMS in X.org log. It is little bit confusing.

It's very much possible that the test is not working correctly. Matthias -- Matthias Hopf __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

5153

Age (days ago)

5168

Last active (days ago)

List overview

Download

12 comments

6 participants

participants (6)

Alex Deucher
Jesse Yan
maddox
maddox
Matthias Hopf
Tobias Koeck