Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[how-to] 3d hardware acc with ati open source driver.
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 8, 9, 10 ... 27, 28, 29  Next  
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
pingufunkybeat
l33t
l33t


Joined: 01 Dec 2004
Posts: 610

PostPosted: Mon Dec 07, 2009 12:34 pm    Post subject: Reply with quote

That's a very strange glxgears output. I don't know how to understand it.

with your card, you should be getting above 1000fps, easily. (yes, I know, glxgears is not a benchmark, but it can be a quick diagnostic tool)

As for KMS, you either need to activate it in the kernel, under staging drivers, or you need to pass the modeset=1 parameter to the radeon module when loading it.
Back to top
View user's profile Send private message
bob_111
Apprentice
Apprentice


Joined: 12 Oct 2004
Posts: 155

PostPosted: Tue Dec 08, 2009 12:34 pm    Post subject: Reply with quote

Finally made the jump from the dreaded fglrx to the open source drivers!

Running a vanilla 2.6.32 kernel with libdrm, mesa and radeon drivers from the x11 overlay.
Code:
michael@localhost ~ $ glxgears
15769 frames in 5.0 seconds = 3153.769 FPS
16600 frames in 5.0 seconds = 3319.940 FPS
16600 frames in 5.0 seconds = 3319.974 FPS

My first successful acceleration test with the new drivers and two monitors :D http://i.imgur.com/PyaQx.jpg
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5387

PostPosted: Tue Dec 08, 2009 4:36 pm    Post subject: Reply with quote

I have a problem, using libdrm, mesa, xf86-video-ati from svn and gentoo-sources-2.6.32 with kms, my computer hard freezes twice a day. I've reverted to 31 with the x11-drm.
I've posted a bug in drm bugzilla...
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
earendilion
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2007
Posts: 115
Location: Meudon (92), France

PostPosted: Wed Dec 09, 2009 7:35 pm    Post subject: Reply with quote

Hi.

I tried to activate the KMS option in the kernel, and video-ati driver, but what I get is a garble screen... I can only move the cursor.

Here is my kdm.log :
Code:

X.Org X Server 1.7.3
Release Date: 2009-12-3
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32-gentoo-ithil x86_64
Current Operating System: Linux ithil 2.6.32-gentoo-ithil #5 SMP Tue Dec 8 00:02:28 CET 2009 x86_64
Kernel command line: root=/dev/sda2 video=uvesafb:ywrap,1280x800-32,mtrr
Build Date: 07 December 2009  11:57:39PM

Current version of pixman: 0.17.2
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec  9 20:04:16 2009
(==) Using default built-in configuration (30 lines)
(EE) Failed to load module "vesa" (module does not exist, 0)
(EE) Failed to load module "fbdev" (module does not exist, 0)
(II) [KMS] Kernel modesetting enabled.
Setting master
record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now..
record: http://bugs.freedesktop.org/show_bug.cgi?id=20500
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(EE) HID 0566:3108: failed to initialize for relative axes.


I tried with or without xorg.conf, and I get the same result :(
_________________
Laptop : XPS M1330/Core2 T9300 - 2.50Ghz/2Go Ram - DDR2/250Go 7200TPM/nVidia 9200GS/Led Screen
-----
Desktop : Gygabyte EX58-UD3R/Core i7 920 2.67Ghz/3Go Ram - DDR3/WD 1To - 7200TPM - 32Mo Cache/ATI HD4850 - 1Go Ram
Back to top
View user's profile Send private message
snipe
n00b
n00b


Joined: 12 Nov 2009
Posts: 6

PostPosted: Mon Dec 14, 2009 8:50 pm    Post subject: Reply with quote

Using KMS all i get is a black screen.
But without it, it runs really smooth except for some tearing here and there but nothing thats annoying.
Using 2.6.32-zen1 and radeonhd. (tried xf86-video-ati but still only gets all black on both monitors).
When modprobing with modeset why does it revert from 80x25 to framebuffer? doesnt even have framebuffer enabled in kernel.

Edit: nvm about the tearing part...
Back to top
View user's profile Send private message
pingufunkybeat
l33t
l33t


Joined: 01 Dec 2004
Posts: 610

PostPosted: Mon Dec 14, 2009 10:32 pm    Post subject: Reply with quote

With KMS, you get a framebuffer console in your monitor's native resolution. That enables fast VT switching because you don't have to change resolutions.

When does your screen go blank? When activating xdm or before? Is there any output? Do you have the firmware in the correct place?

I prefer to build drm+firmware into the kernel to avoid all sorts of strange problems people have with loading modules in the right order. Also, using radeon instead of radeonhd can save you trouble these days. there shouldn't be much difference in theory, but radeonhd seems to be falling behind, and most ati developers are using radeon.
Back to top
View user's profile Send private message
snipe
n00b
n00b


Joined: 12 Nov 2009
Posts: 6

PostPosted: Tue Dec 15, 2009 7:54 am    Post subject: Reply with quote

My screen goes all blank when entering X. When I'm killing X I can see it fails to unload radeon drivers because its still in effect.
I'm not using xdm going straight to console. Makes no difference using radeon or radeonhd.
I have DRM+Firmware being built in kernel.
Back to top
View user's profile Send private message
pingufunkybeat
l33t
l33t


Joined: 01 Dec 2004
Posts: 610

PostPosted: Tue Dec 15, 2009 11:12 am    Post subject: Reply with quote

Anything in dmesg? Xorg.log?

Also, which mesa and libdrm? Which version of radeon/radeonhd?
Back to top
View user's profile Send private message
snipe
n00b
n00b


Joined: 12 Nov 2009
Posts: 6

PostPosted: Tue Dec 15, 2009 5:29 pm    Post subject: Reply with quote

Ok here goes:
Version:
Radeonhd 1.3.0 from git branch master
radeon-9999 from x11-overlay
mesa-9999 from x11-overlay
libdrm-9999 from x11-overlay

This is the messages log after a modprobe radeon modeset=1
------------------------------SNIP------------------------------
Dec 15 18:07:25 chaos kernel: [ 274.452911] [drm] radeon kernel modesetting enabled.
Dec 15 18:07:25 chaos kernel: [ 274.453381] ACPI: PCI Interrupt Link [LNEB] enabled at IRQ 19
Dec 15 18:07:25 chaos kernel: [ 274.453387] radeon 0000:02:00.0: PCI INT A -> Link[LNEB] -> GSI 19 (level, low) -> IRQ 19
Dec 15 18:07:25 chaos kernel: [ 274.453392] radeon 0000:02:00.0: setting latency timer to 64
Dec 15 18:07:25 chaos kernel: [ 274.455855] [drm] radeon: Initializing kernel modesetting.
Dec 15 18:07:25 chaos kernel: [ 274.455903] [drm] register mmio base: 0xDFFF0000
Dec 15 18:07:25 chaos kernel: [ 274.455904] [drm] register mmio size: 65536
Dec 15 18:07:25 chaos kernel: [ 274.459791] ATOM BIOS: 954F.11.12.0.2.AS01
Dec 15 18:07:25 chaos kernel: [ 274.459797] [drm] Clocks initialized !
Dec 15 18:07:25 chaos kernel: [ 274.459990] [drm] Detected VRAM RAM=256M, BAR=256M
Dec 15 18:07:25 chaos kernel: [ 274.459993] [drm] RAM width 64bits DDR
Dec 15 18:07:25 chaos kernel: [ 274.460075] [TTM] Zone kernel: Available graphics memory: 2030796 kiB.
Dec 15 18:07:25 chaos kernel: [ 274.460094] [drm] radeon: 256M of VRAM memory ready
Dec 15 18:07:25 chaos kernel: [ 274.460096] [drm] radeon: 512M of GTT memory ready.
Dec 15 18:07:25 chaos kernel: [ 274.460145] [drm] Loading RV710 CP Microcode
Dec 15 18:07:25 chaos kernel: [ 274.460147] platform radeon_cp.0: firmware: requesting radeon/RV710_pfp.bin
Dec 15 18:07:25 chaos kernel: [ 274.489451] platform radeon_cp.0: firmware: requesting radeon/RV710_me.bin
Dec 15 18:07:25 chaos kernel: [ 274.507576] [drm] GART: num cpu pages 131072, num gpu pages 131072
Dec 15 18:07:25 chaos kernel: [ 274.541227] [drm] ring test succeeded in 1 usecs
Dec 15 18:07:25 chaos kernel: [ 274.541339] [drm] radeon: ib pool ready.
Dec 15 18:07:25 chaos kernel: [ 274.541413] [drm] ib test succeeded in 0 usecs
Dec 15 18:07:25 chaos kernel: [ 274.541626] [drm] Radeon Display Connectors
Dec 15 18:07:25 chaos kernel: [ 274.541628] [drm] Connector 0:
Dec 15 18:07:25 chaos kernel: [ 274.541629] [drm] HDMI-A
Dec 15 18:07:25 chaos kernel: [ 274.541631] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
Dec 15 18:07:25 chaos kernel: [ 274.541633] [drm] Encoders:
Dec 15 18:07:25 chaos kernel: [ 274.541634] [drm] DFP1: INTERNAL_UNIPHY
Dec 15 18:07:25 chaos kernel: [ 274.541636] [drm] Connector 1:
Dec 15 18:07:25 chaos kernel: [ 274.541637] [drm] VGA
Dec 15 18:07:25 chaos kernel: [ 274.541639] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
Dec 15 18:07:25 chaos kernel: [ 274.541640] [drm] Encoders:
Dec 15 18:07:25 chaos kernel: [ 274.541641] [drm] CRT2: INTERNAL_KLDSCP_DAC2
Dec 15 18:07:25 chaos kernel: [ 274.541643] [drm] Connector 2:
Dec 15 18:07:25 chaos kernel: [ 274.541644] [drm] DVI-I
Dec 15 18:07:25 chaos kernel: [ 274.541646] [drm] DDC: 0x7f10 0x7f10 0x7f14 0x7f14 0x7f18 0x7f18 0x7f1c 0x7f1c
Dec 15 18:07:25 chaos kernel: [ 274.541647] [drm] Encoders:
Dec 15 18:07:25 chaos kernel: [ 274.541648] [drm] CRT1: INTERNAL_KLDSCP_DAC1
Dec 15 18:07:25 chaos kernel: [ 274.541650] [drm] DFP2: INTERNAL_UNIPHY2
Dec 15 18:07:25 chaos kernel: [ 274.756980] [drm] fb mappable at 0xC0141000
Dec 15 18:07:25 chaos kernel: [ 274.756982] [drm] vram apper at 0xC0000000
Dec 15 18:07:25 chaos kernel: [ 274.756984] [drm] size 7257600
Dec 15 18:07:25 chaos kernel: [ 274.756985] [drm] fb depth is 24
Dec 15 18:07:25 chaos kernel: [ 274.756986] [drm] pitch is 6912
Dec 15 18:07:25 chaos kernel: [ 274.777222] executing set pll
Dec 15 18:07:25 chaos kernel: [ 274.782015] executing set crtc timing
Dec 15 18:07:25 chaos kernel: [ 274.782043] [drm] TV-11: set mode 1280x1024 30
Dec 15 18:07:25 chaos kernel: [ 274.797219] executing set pll
Dec 15 18:07:25 chaos kernel: [ 274.802015] executing set crtc timing
Dec 15 18:07:25 chaos kernel: [ 274.802040] [drm] TMDS-15: set mode 1680x1050 31
Dec 15 18:07:25 chaos kernel: [ 274.827019] Console: switching to colour frame buffer device 160x64
Dec 15 18:07:25 chaos kernel: [ 274.831867] fb0: radeondrmfb frame buffer device
Dec 15 18:07:25 chaos kernel: [ 274.831868] registered panic notifier
Dec 15 18:07:25 chaos kernel: [ 274.831872] [drm] Initialized radeon 2.0.0 20080528 for 0000:02:00.0 on minor 0
------------------------------SNIP------------------------------

xorg.log:
snipped from RADEONHD loading part

------------------------------SNIP------------------------------
(II) RADEONHD: X driver for the following AMD GPG (ATI) graphics devices:
RV505 : Radeon X1550, X1550 64bit.
RV515 : Radeon X1300, X1550, X1600; FireGL V3300, V3350.
RV516 : Radeon X1300, X1550, X1550 64-bit, X1600; FireMV 2250.
R520 : Radeon X1800; FireGL V5300, V7200, V7300, V7350.
RV530 : Radeon X1300 XT, X1600, X1600 Pro, X1650; FireGL V3400, V5200.
RV535 : Radeon X1300, X1650.
RV550 : Radeon X2300 HD.
RV560 : Radeon X1650.
RV570 : Radeon X1950, X1950 GT; FireGL V7400.
R580 : Radeon X1900, X1950; AMD Stream Processor.
R600 : Radeon HD 2900 GT/Pro/XT; FireGL V7600/V8600/V8650.
RV610 : Radeon HD 2350, HD 2400 Pro/XT, HD 2400 Pro AGP; FireGL V4000.
RV620 : Radeon HD 3450, HD 3470.
RV630 : Radeon HD 2600 LE/Pro/XT, HD 2600 Pro/XT AGP; Gemini RV630;
FireGL V3600/V5600.
RV635 : Radeon HD 3650, HD 3670.
RV670 : Radeon HD 3690, 3850, HD 3870, FireGL V7700, FireStream 9170.
R680 : Radeon HD 3870 X2.
M52 : Mobility Radeon X1300.
M54 : Mobility Radeon X1400; M54-GL.
M56 : Mobility Radeon X1600; Mobility FireGL V5200.
M58 : Mobility Radeon X1800, X1800 XT; Mobility FireGL V7100, V7200.
M62 : Mobility Radeon X1350.
M64 : Mobility Radeon X1450, X2300.
M66 : Mobility Radeon X1700, X1700 XT; FireGL V5250.
M68 : Mobility Radeon X1900.
M71 : Mobility Radeon HD 2300.
M72 : Mobility Radeon HD 2400; Radeon E2400.
M74 : Mobility Radeon HD 2400 XT.
M76 : Mobility Radeon HD 2600;
(Gemini ATI) Mobility Radeon HD 2600 XT.
M82 : Mobility Radeon HD 3400.
M86 : Mobility Radeon HD 3650, HD 3670, Mobility FireGL V5700.
M88 : Mobility Radeon HD 3850, HD 3850 X2, HD 3870, HD3870 X2.
RS600 : Radeon Xpress 1200, Xpress 1250.
RS690 : Radeon X1200, X1250, X1270.
RS740 : RS740, RS740M.
RS780 : Radeon HD 3100/3200/3300 Series.
R700 : Radeon R700.
RV710 : Radeon HD4570, HD4350.
RV730 : Radeon HD4670, HD4650.
RV740 : Radeon HD4770. EXPERIMENTAL AND UNTESTED.
RV770 : Radeon HD 4800 Series; Everest, K2, Denali ATI FirePro.
RV790 : Radeon HD 4890.
M92 : Mobility Radeon HD4330, HD4530, HD4570. EXPERIMENTAL.
M93 : Mobility Radeon M93. EXPERIMENTAL AND UNTESTED.
M96 : Mobility Radeon HD4600.
M97 : Mobility Radeon HD4860. EXPERIMENTAL AND UNTESTED.
M98 : Mobility Radeon HD4850, HD4870.

(II) RADEONHD: version 1.3.0, built from dist of git branch master, commit 8cbff7bf

(II) Primary Device is: PCI 02@00:00:0
(**) RADEONHD(0): Depth 24, (--) framebuffer bpp 32
(**) RADEONHD(0): Option "AccelMethod" "EXA"
(**) RADEONHD(0): Selected EXA 2D acceleration.
(II) RADEONHD(0): Card not in database: 0x954F:0x1043:0x0274; 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: 0x954F:0x1043:0x0274: <name of board>
and *please* describe the problems you are seeing
in your message.
(--) RADEONHD(0): Detected an RV710 on an unidentified card
(II) RADEONHD(0): Mapped IO @ 0xdfff0000 to 0x7f5338a26000 (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: 0x1043 SubsystemID: 0x0274
IOBaseAddress: 0xe800
Filename: SV30348a.bin
BIOS Bootup Message:
954F.11.12.0.2.AS01

(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): 20
(II) RADEONHD(0): Start of VRAM area used by Firmware: 0x7ffec
(II) RADEONHD(0): AtomBIOS requests 20kB of VRAM scratch space
(II) RADEONHD(0): AtomBIOS VRAM scratch base: 0x7ffec
(WW) RADEONHD(0): rhdAtomAllocateFbScratch: FW FB scratch area not located at the end of VRAM. Scratch End: 0x84fec VRAM End: 0x10000000
(II) RADEONHD(0): Cannot get VRAM scratch space. Allocating in main memory instead
(II) RADEONHD(0): Default Engine Clock: 600000
(II) RADEONHD(0): Default Memory Clock: 400000
(II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Output: 1200000
(II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Output: 0
(II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Input: 16000
(II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Input: 6000
(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 7, (OK)
drmOpenByBusid: Searching for BusID pci:0000:02:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci:0000:02: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): Reference Clock: 27000
(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_Clk_Mask_Shift: 0x0
(II) RADEONHD(0): GPIO_I2C_Data_Mask: 0x1f98
(II) RADEONHD(0): GPIO_I2C_Data_Mask_Shift: 0x8
(II) RADEONHD(0): I2C bus "RHD I2C line 2" initialized.
(II) RADEONHD(0): GPIO_I2C_Clk_Mask: 0x1f88
(II) RADEONHD(0): GPIO_I2C_Clk_Mask_Shift: 0x0
(II) RADEONHD(0): GPIO_I2C_Data_Mask: 0x1f88
(II) RADEONHD(0): GPIO_I2C_Data_Mask_Shift: 0x8
(II) RADEONHD(0): I2C bus "RHD I2C line 3" initialized.
(II) RADEONHD(0): GPIO_I2C_Clk_Mask: 0x1fc4
(II) RADEONHD(0): GPIO_I2C_Clk_Mask_Shift: 0x0
(II) RADEONHD(0): GPIO_I2C_Data_Mask: 0x1fc4
(II) RADEONHD(0): GPIO_I2C_Data_Mask_Shift: 0x8
(II) RADEONHD(0): I2C bus "RHD I2C line 4" initialized.
(II) RADEONHD(0): GPIO_I2C_Clk_Mask: 0x1fe8
(II) RADEONHD(0): GPIO_I2C_Clk_Mask_Shift: 0x0
(II) RADEONHD(0): GPIO_I2C_Data_Mask: 0x1fe8
(II) RADEONHD(0): GPIO_I2C_Data_Mask_Shift: 0x8
(II) RADEONHD(0): I2C bus "RHD I2C line 5" 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: 1200000
(II) RADEONHD(0): Maximum Pixel Clock: 400000
(II) RADEONHD(0): Reference Clock: 27000
(II) RADEONHD(0): rhdAtomSetPixelClockVersion returned version 3 for index 0xc
(II) RADEONHD(0): rhdAtomSetPixelClockVersion returned version 3 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 0104
(II) RADEONHD(0): Unused attribute: ul3DAccelerationEngineClock 0
(II) RADEONHD(0): Unused attribute: ulDriverTargetEngineClock 0
(II) RADEONHD(0): Unused attribute: ulDriverTargetMemoryClock 0
(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): Default Engine Clock: 600000
(II) RADEONHD(0): Default Memory Clock: 400000
(II) RADEONHD(0): Current Engine Clock: 599060
(II) RADEONHD(0): Current Memory Clock: 396000
(II) RADEONHD(0): Current Chip Voltage: 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.900 V
(II) RADEONHD(0): Maximum 750000 kHz / 600000 kHz / 1.100 V
(II) RADEONHD(0): Default 600000 kHz / 400000 kHz / 1.100 V
(II) RADEONHD(0): PowerPlayInfo Revision 0401
(II) RADEONHD(0): Power Management: Validated Ranges
(II) RADEONHD(0): Minimum 110000 kHz / 250000 kHz / 0.900 V
(II) RADEONHD(0): Maximum 750000 kHz / 600000 kHz / 1.100 V
(II) RADEONHD(0): Default 600000 kHz / 400000 kHz / 1.100 V
(II) RADEONHD(0): Power Management: Known Good Configurations
(II) RADEONHD(0): 1 600000 kHz / 400000 kHz / 1.100 V
(II) RADEONHD(0): 2 110000 kHz / 250000 kHz / 0.900 V
(II) RADEONHD(0): 3 300000 kHz / 400000 kHz / 1.000 V
(II) RADEONHD(0): 4 600000 kHz / 400000 kHz / 1.100 V
(II) RADEONHD(0): 5 600000 kHz / 400000 kHz / 1.100 V
(II) RADEONHD(0): 6 600000 kHz / 400000 kHz / 1.100 V
(II) RADEONHD(0): 7 600000 kHz / 400000 kHz / 1.100 V
(II) RADEONHD(0): 8 110000 kHz / 400000 kHz / 0.900 V
(II) RADEONHD(0): 9 300000 kHz / 400000 kHz / 1.000 V
(II) RADEONHD(0): Power Management: Final Levels
(II) RADEONHD(0): Off 110000 kHz / 250000 kHz / 0.900 V
(II) RADEONHD(0): Idle 600000 kHz / 400000 kHz / 1.100 V
(II) RADEONHD(0): Slow2D 600000 kHz / 400000 kHz / 1.100 V
(II) RADEONHD(0): Fast2D 600000 kHz / 400000 kHz / 1.100 V
(II) RADEONHD(0): Slow3D 600000 kHz / 400000 kHz / 1.100 V
(II) RADEONHD(0): Fast3D 600000 kHz / 400000 kHz / 1.100 V
(II) RADEONHD(0): Max3D 750000 kHz / 600000 kHz / 1.100 V
(II) RADEONHD(0): User 600000 kHz / 400000 kHz / 1.100 V
(II) RADEONHD(0): Connector[0] {RHD_CONNECTOR_DVI_SINGLE, "HDMI_TYPE_A DFP1", RHD_DDC_1, RHD_HPD_0, { RHD_OUTPUT_UNIPHYA, RHD_OUTPUT_NONE } }
(II) RADEONHD(0): Connector[1] {RHD_CONNECTOR_VGA, "VGA CRT2", RHD_DDC_0, RHD_HPD_NONE, { RHD_OUTPUT_DACB, RHD_OUTPUT_NONE } }
(II) RADEONHD(0): Connector[2] {RHD_CONNECTOR_DVI, "DUAL_LINK_DVI_I CRT1 DFP2", RHD_DDC_4, RHD_HPD_3, { RHD_OUTPUT_UNIPHYE, RHD_OUTPUT_DACA } }
(**) RADEONHD(0): Using AtomBIOS for Outputs
(II) RADEONHD(0): rhdAtomSelectCrtcSourceVersion returned version 2 for index 0x2a
(--) RADEONHD(0): Attaching Output AtomOutputUniphyA to Connector DVI-D 1
(**) RADEONHD(0): Using AtomBIOS for Outputs
(II) RADEONHD(0): rhdAtomSelectCrtcSourceVersion returned version 2 for index 0x2a
(--) RADEONHD(0): Attaching Output AtomOutputDACB to Connector VGA 1
(**) RADEONHD(0): Using AtomBIOS for Outputs
(EE) RADEONHD(0): RHDHdmiInit: unknown HDMI output type
(II) RADEONHD(0): rhdAtomSelectCrtcSourceVersion returned version 2 for index 0x2a
(--) RADEONHD(0): Attaching Output AtomOutputUniphyE to Connector DVI-I 2
(**) RADEONHD(0): Using AtomBIOS for Outputs
(II) RADEONHD(0): rhdAtomSelectCrtcSourceVersion returned version 2 for index 0x2a
(--) RADEONHD(0): Attaching Output AtomOutputDACA to Connector DVI-I 2
(II) RADEONHD(0): RandR: Adding RRoutput DVI-D_1 for Output AtomOutputUniphyA
(II) RADEONHD(0): RandR: Adding RRoutput VGA_1 for Output AtomOutputDACB
(II) RADEONHD(0): RandR: Adding RRoutput DVI-I_2/digital for Output AtomOutputUniphyE
(II) RADEONHD(0): RandR: Adding RRoutput DVI-I_2/analog for Output AtomOutputDACA
(II) RADEONHD(0): Output DVI-D_1 using monitor section DFP-2
(II) RADEONHD(0): Output DVI-D_1 has no monitor section
(II) RADEONHD(0): Output VGA_1 using monitor section DFP-1
(**) RADEONHD(0): Option "RightOf" "DFP-2"
(II) RADEONHD(0): Output DVI-I_2/digital using monitor section DFP-2
(II) RADEONHD(0): Output DVI-I_2/analog has no monitor section
(II) RADEONHD(0): Calling DAC_LoadDetection
(II) RADEONHD(0): DAC_LoadDetection Successful
(II) RADEONHD(0): AtomOutputDACB: Sensed Output: VGA
(II) RADEONHD(0): Setting AtomOutputDACB to incoherent
(II) RADEONHD(0): I2C device "RHD I2C line 0:ddc2" registered at address 0xA0.
(II) RADEONHD(0): EDID data for DELL E171FP
(II) RADEONHD(0): Manufacturer: DEL Model: 300f Serial#: 1095059021
(II) RADEONHD(0): Year: 2003 Week: 20
(II) RADEONHD(0): EDID Version: 1.3
(II) RADEONHD(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
(II) RADEONHD(0): Sync: Separate
(II) RADEONHD(0): Max Image Size [cm]: horiz.: 34 vert.: 27
(II) RADEONHD(0): Gamma: 2.20
(II) RADEONHD(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) RADEONHD(0): Default color space is primary color space
(II) RADEONHD(0): First detailed timing is preferred mode
(II) RADEONHD(0): redX: 0.631 redY: 0.354 greenX: 0.294 greenY: 0.596
(II) RADEONHD(0): blueX: 0.143 blueY: 0.087 whiteX: 0.315 whiteY: 0.330
(II) RADEONHD(0): Supported established timings:
(II) RADEONHD(0): 720x400@70Hz
(II) RADEONHD(0): 640x480@60Hz
(II) RADEONHD(0): 640x480@75Hz
(II) RADEONHD(0): 800x600@60Hz
(II) RADEONHD(0): 800x600@75Hz
(II) RADEONHD(0): 1024x768@60Hz
(II) RADEONHD(0): 1024x768@75Hz
(II) RADEONHD(0): 1280x1024@75Hz
(II) RADEONHD(0): Manufacturer's mask: 0
(II) RADEONHD(0): Supported standard timings:
(II) RADEONHD(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) RADEONHD(0): #1: hsize: 1152 vsize 864 refresh: 75 vid: 20337
(II) RADEONHD(0): Supported detailed timing:
(II) RADEONHD(0): clock: 108.0 MHz Image Size: 338 x 270 mm
(II) RADEONHD(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
(II) RADEONHD(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
(II) RADEONHD(0): Serial No: 7R41535CAEFM
(II) RADEONHD(0): Monitor name: DELL E171FP
(II) RADEONHD(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 80 kHz, PixClock max 140 MHz
(II) RADEONHD(0): EDID (in hex):
(II) RADEONHD(0): 00ffffffffffff0010ac0f304d464541
(II) RADEONHD(0): 140d010368221b78eea69ea15a4b9824
(II) RADEONHD(0): 165054a54b008180714f010101010101
(II) RADEONHD(0): 010101010101302a009851002a403070
(II) RADEONHD(0): 1300520e1100001e000000ff00375234
(II) RADEONHD(0): 31353335434145464d0a000000fc0044
(II) RADEONHD(0): 454c4c204531373146500a20000000fd
(II) RADEONHD(0): 00384c1e500e000a2020202020200084
(II) RADEONHD(0): Calling DAC_LoadDetection
(II) RADEONHD(0): DAC_LoadDetection Successful
(II) RADEONHD(0): Setting AtomOutputUniphyE to incoherent
(II) RADEONHD(0): I2C device "RHD I2C line 4:ddc2" registered at address 0xA0.
(II) RADEONHD(0): I2C device "RHD I2C line 4:DDC control interface" registered at address 0x6E.
(II) RADEONHD(0): EDID data for SyncMaster
(II) RADEONHD(0): Manufacturer: SAM Model: 30f Serial#: 1296380466
(II) RADEONHD(0): Year: 2007 Week: 32
(II) RADEONHD(0): EDID Version: 1.3
(II) RADEONHD(0): Digital Display Input
(II) RADEONHD(0): Max Image Size [cm]: horiz.: 47 vert.: 30
(II) RADEONHD(0): Gamma: 2.20
(II) RADEONHD(0): DPMS capabilities: Off
(II) RADEONHD(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) RADEONHD(0): First detailed timing is preferred mode
(II) RADEONHD(0): redX: 0.662 redY: 0.329 greenX: 0.205 greenY: 0.684
(II) RADEONHD(0): blueX: 0.146 blueY: 0.077 whiteX: 0.313 whiteY: 0.329
(II) RADEONHD(0): Supported established timings:
(II) RADEONHD(0): 720x400@70Hz
(II) RADEONHD(0): 640x480@60Hz
(II) RADEONHD(0): 640x480@67Hz
(II) RADEONHD(0): 640x480@72Hz
(II) RADEONHD(0): 640x480@75Hz
(II) RADEONHD(0): 800x600@56Hz
(II) RADEONHD(0): 800x600@60Hz
(II) RADEONHD(0): 800x600@72Hz
(II) RADEONHD(0): 800x600@75Hz
(II) RADEONHD(0): 832x624@75Hz
(II) RADEONHD(0): 1024x768@60Hz
(II) RADEONHD(0): 1024x768@70Hz
(II) RADEONHD(0): 1024x768@75Hz
(II) RADEONHD(0): 1280x1024@75Hz
(II) RADEONHD(0): 1152x864@75Hz
(II) RADEONHD(0): Manufacturer's mask: 0
(II) RADEONHD(0): Supported standard timings:
(II) RADEONHD(0): #0: hsize: 1680 vsize 1050 refresh: 60 vid: 179
(II) RADEONHD(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) RADEONHD(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
(II) RADEONHD(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
(II) RADEONHD(0): Supported detailed timing:
(II) RADEONHD(0): clock: 119.0 MHz Image Size: 474 x 296 mm
(II) RADEONHD(0): h_active: 1680 h_sync: 1728 h_sync_end 1760 h_blank_end 1840 h_border: 0
(II) RADEONHD(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1080 v_border: 0
(II) RADEONHD(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz
(II) RADEONHD(0): Monitor name: SyncMaster
(II) RADEONHD(0): Serial No: HSDP816146
(II) RADEONHD(0): EDID (in hex):
(II) RADEONHD(0): 00ffffffffffff004c2d0f033232454d
(II) RADEONHD(0): 20110103802f1e782a9875a95434af25
(II) RADEONHD(0): 135054bfef80b30081808140714f0101
(II) RADEONHD(0): 0101010101017c2e90a0601a1e403020
(II) RADEONHD(0): 3600da281100001a000000fd00384b1e
(II) RADEONHD(0): 510e000a202020202020000000fc0053
(II) RADEONHD(0): 796e634d61737465720a2020000000ff
(II) RADEONHD(0): 00485344503831363134360a20200080
(II) RADEONHD(0): Calling DAC_LoadDetection
(II) RADEONHD(0): DAC_LoadDetection Successful
(II) RADEONHD(0): Output DVI-D_1 disconnected
(II) RADEONHD(0): Output VGA_1 connected
(II) RADEONHD(0): Output DVI-I_2/digital connected
(II) RADEONHD(0): Output DVI-I_2/analog disconnected
(II) RADEONHD(0): Using user preference for initial modes
(II) RADEONHD(0): Output VGA_1 using initial mode 1280x1024
(II) RADEONHD(0): Output DVI-I_2/digital using initial mode 1680x1050
(II) RADEONHD(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
(II) RADEONHD(0): RandR 1.2 support enabled
(==) RADEONHD(0): RGB weight 888
(==) RADEONHD(0): Default visual is TrueColor
(II) RADEONHD(0): Using 2960x1050 Framebuffer with 3008 pitch
(II) RADEONHD(0): FB: Allocated ScanoutBuffer at offset 0x00008000 (size = 0x00C0D000)
(==) RADEONHD(0): DPI set to (96, 96)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib64/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.7.1, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) Loading sub module "exa"
(II) LoadModule: "exa"
(II) Loading /usr/lib64/xorg/modules/libexa.so
(II) Module exa: vendor="X.Org Foundation"
compiled for 1.7.1, module version = 2.5.0
ABI class: X.Org Video Driver, version 6.0
(II) RADEONHD(0): FB: Allocated Offscreen Buffer at offset 0x00C15000 (size = 0x0199A000)
(II) RADEONHD(0): FB: Allocated DRI Back Buffer at offset 0x025AF000 (size = 0x00C0D000)
(II) RADEONHD(0): FB: Allocated DRI Depth Buffer at offset 0x031BC000 (size = 0x00C1E000)
(II) RADEONHD(0): FB: Allocated GART table at offset 0x0FFF0000 (size = 0x00010000, end of FB)
(II) RADEONHD(0): FB: Allocated DRI Textures at offset 0x03DDA000 (size = 0x0C000000)
(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 @ 0xdfff0000 to 0x7f5338a26000 (size 0x00010000)
(II) RADEONHD(0): Mapped FB @ 0xc0000000 to 0x7f5323f48000 (size 0x10000000)
(II) RADEONHD(0): Attempting to enable power management
(II) RADEONHD(0): Current Engine Clock: 599060
(II) RADEONHD(0): Current Memory Clock: 396000
(II) RADEONHD(0): Current Chip Voltage: 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 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: Searching for BusID pci:0000:02:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci:0000:02: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 = 0xc0000000
(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 0x121ea900
(II) RADEONHD(0): [pci] ring handle = 0x2b800000
(II) RADEONHD(0): [pci] Ring mapped at 0x7f5323d47000
(II) RADEONHD(0): [pci] Ring contents 0x00000000
(II) RADEONHD(0): [pci] ring read ptr handle = 0x1b7ff000
(II) RADEONHD(0): [pci] Ring read ptr mapped at 0x7f5338a48000
(II) RADEONHD(0): [pci] Ring read ptr contents 0x00000000
(II) RADEONHD(0): [pci] vertex/indirect buffers handle = 0x2b801000
(II) RADEONHD(0): [pci] Vertex/indirect buffers mapped at 0x7f5323b47000
(II) RADEONHD(0): [pci] Vertex/indirect buffers contents 0x00000000
(II) RADEONHD(0): [pci] GART texture map handle = 0x2b7fe000
(II) RADEONHD(0): [pci] GART Texture map mapped at 0x7f5322f87000
(II) RADEONHD(0): [drm] register handle = 0xdfff0000
(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 0x7f5338a49000
(II) RADEONHD(0): [drm] Closed DRM master.
(II) RADEONHD(0): Attempting to set Engine Clock to 600000
(II) RADEONHD(0): Current Engine Clock: 599060
(II) RADEONHD(0): Current Memory Clock: 396000
(II) RADEONHD(0): Current Chip Voltage: 0
(WW) RADEONHD(0): RHDCSInit: CS for R600 requires DRI.
(WW) RADEONHD(0): Failed to initalize EXA; disabling acceleration.
(**) RADEONHD(0): Option "BackingStore" "on"
(**) RADEONHD(0): Backing store enabled
(==) 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 DAC2OutputControl
(II) RADEONHD(0): DAC2OutputControl Successful
(II) RADEONHD(0): Calling DACBEncoderControl
(II) RADEONHD(0): DACBEncoderControl 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 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 DAC2OutputControl
(II) RADEONHD(0): DAC2OutputControl 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 60.0 Hz Mode: Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +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 DACBEncoderControl
(II) RADEONHD(0): DACBEncoderControl Successful
(II) RADEONHD(0): Calling DAC2OutputControl
(II) RADEONHD(0): DAC2OutputControl Successful
(II) RADEONHD(0): Mapping DIG1 encoder to KLDSKP_UNIPHYE
(II) RADEONHD(0): Calling UNIPHYTransmitterControl
(II) RADEONHD(0): UNIPHYTransmitterControl 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 1 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 UNIPHYTransmitterControl
(II) RADEONHD(0): UNIPHYTransmitterControl Successful
(II) RADEONHD(0): Calling UNIPHYTransmitterControl
(II) RADEONHD(0): UNIPHYTransmitterControl 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 DIG1EncoderControl
(II) RADEONHD(0): DIG1EncoderControl Successful
(II) RADEONHD(0): Calling UNIPHYTransmitterControl
(II) RADEONHD(0): UNIPHYTransmitterControl Successful
(II) RADEONHD(0): Calling UNIPHYTransmitterControl
(II) RADEONHD(0): UNIPHYTransmitterControl Successful
(II) RADEONHD(0): Calling DAC1OutputControl
(II) RADEONHD(0): DAC1OutputControl Successful
(II) RADEONHD(0): Calling DACAEncoderControl
(II) RADEONHD(0): DACAEncoderControl Successful
(II) RADEONHD(0): RHDAudioSetSupported: config 0x60040 codec 0x1
(==) RADEONHD(0): DPMS enabled
(--) RandR disabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now..
record: http://bugs.freedesktop.org/show_bug.cgi?id=20500
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib64/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(II) RADEONHD(0): Setting screen physical size to 783 x 277 <----------------------------------------------------Why?
(**) Option "CoreKeyboard"
(**) Keyboard0: always reports core events
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "se"
(**) Keyboard0: XkbLayout: "se"
(**) Option "XkbVariant" "nodeadkeys"
(**) Keyboard0: XkbVariant: "nodeadkeys"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(**) Option "Protocol" "ImPS/2"
(**) Configured Mouse: Device: "/dev/input/mice"
(**) Configured Mouse: Protocol: "ImPS/2"
(**) Option "CorePointer"
(**) Configured Mouse: always reports core events
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "true"
(**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Configured Mouse: Buttons: 9
(**) Configured Mouse: Sensitivity: 1
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(**) Configured Mouse: (accel) keeping acceleration scheme 1
(**) Configured Mouse: (accel) acceleration profile 0
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) RADEONHD(0): Calling BlankCRTC
(II) RADEONHD(0): BlankCRTC Successful
(II) RADEONHD(0): Calling BlankCRTC
(II) RADEONHD(0): BlankCRTC Successful
------------------------------SNIP------------------------------

And lastly from where it is all blank screens.
Exiting xorg.log:
Dec 15 18:11:28 chaos kernel: [ 517.034483] mtrr: base(0xc0000000) is not aligned on a size(0xfff0000) boundary
Dec 15 18:11:28 chaos kernel: [ 517.045801] [drm:radeon_cp_setparam_kms] *ERROR* invalid ioctl with kms radeon_cp_setparam_kms
Dec 15 18:11:28 chaos kernel: [ 517.045813] [drm:radeon_cp_init_kms] *ERROR* invalid ioctl with kms radeon_cp_init_kms

------------------------------SNIP------------------------------

After this part keyboard may or may not be responsive.
Back to top
View user's profile Send private message
pingufunkybeat
l33t
l33t


Joined: 01 Dec 2004
Posts: 610

PostPosted: Tue Dec 15, 2009 9:21 pm    Post subject: Reply with quote

Looks strange. Have you tried it with a recent vanilla kernel?
Back to top
View user's profile Send private message
Herring42
Guru
Guru


Joined: 10 Mar 2004
Posts: 373
Location: Buckinghamshire

PostPosted: Tue Dec 15, 2009 9:38 pm    Post subject: Reply with quote

snipe wrote:

Dec 15 18:11:28 chaos kernel: [ 517.045801] [drm:radeon_cp_setparam_kms] *ERROR* invalid ioctl with kms radeon_cp_setparam_kms
Dec 15 18:11:28 chaos kernel: [ 517.045813] [drm:radeon_cp_init_kms] *ERROR* invalid ioctl with kms radeon_cp_init_kms


I get those errors (and a blank screen) when I try and use KMS.

Hopefully it'll be fixed soon.
_________________
"The problem with quotes on the internet is that it is difficult
to determine whether or not they are genuine." -- Abraham Lincoln
Back to top
View user's profile Send private message
smorg
n00b
n00b


Joined: 03 Apr 2006
Posts: 40
Location: Germany

PostPosted: Wed Dec 16, 2009 3:09 am    Post subject: Reply with quote

Yay, working OpenGL and KMS :-)

Yesterday I noticed mesa-7.7_rc2 and and libdrm-2.4.16 hitting the tree. So I tried to enable KMS and DRI2/OpenGL-support for my radeon 4830. Without the x11 overlay only KMS was working, but I could not start X. Then I emerged xf86-video-ati-9999 from the x11 overlay, now everything is working :-) There seems to be no need for mesa-9999 or libdrm-9999 anymore.

I am a happy user now :-D
Back to top
View user's profile Send private message
Herring42
Guru
Guru


Joined: 10 Mar 2004
Posts: 373
Location: Buckinghamshire

PostPosted: Wed Dec 16, 2009 7:54 am    Post subject: Reply with quote

Some success:

KMS and ati-9999 is working, but the console is just blank until X starts.
I think this:
Code:
[    0.803948] Console: switching to colour frame buffer device 240x67                                             
[    0.810004] fb0: radeondrmfb frame buffer device                                                               

Indicates it is trying to open the screen at too low a resolution for my monitor (1920x1080)

Anyone know how to set the console up properly?

Also, running glxgears, I get this error:
Code:
do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
Try adjusting the vblank_mode configuration parameter.
8118 frames in 5.0 seconds = 1623.456 FPS
8310 frames in 5.0 seconds = 1661.910 FPS
8567 frames in 5.0 seconds = 1713.256 FPS

What's up with my IRQs?

The card is an Asus HD 4350 (RV710)
_________________
"The problem with quotes on the internet is that it is difficult
to determine whether or not they are genuine." -- Abraham Lincoln
Back to top
View user's profile Send private message
iss
Tux's lil' helper
Tux's lil' helper


Joined: 30 Oct 2006
Posts: 134
Location: Poland/Bydgoszcz

PostPosted: Wed Dec 16, 2009 10:49 am    Post subject: Reply with quote

Just want to post some success (mainly) story.

I'm using libdrm-9999 xf86-video-ati-9999 mesa-9999 and x11-base/xorg-server-1.7.3.901 (1.7.3 and 1.7.1 was ok too).
My integrated HD 3300 (RS780) works ok with gentoo-sources-2.6.32 without KMS.

There is sometimes flickering. GoogleEarth with compositing flickers as hell. Without compositing is ok. Generally compositing works ok (cube, wobbly windows, etc.) but sometimes interferes with some programs.
Glxgears works with same speed with and without compositing (700-800 fps). With fglrx I was getting 750 fps with compositing and 1500 fps without (or 1500 and 3000 - I'm not sure now).
With KMS enabled is a bit worse - more flickering and wobbly glxgears is not smooth.

Yesterday I've tried git-sources-2.6.32-git11 with IRQ enabled firmware.
There is no flickering with KMS. Everything is smooth. Yet it is unusable beacause of lots of artifacts. Graphics are mainly ok, but fonts are unreadable.

Console works ok (1280x1024 DVI) with KMS in all cases.
Back to top
View user's profile Send private message
snipe
n00b
n00b


Joined: 12 Nov 2009
Posts: 6

PostPosted: Wed Dec 16, 2009 2:10 pm    Post subject: Reply with quote

Quote:
The card is an Asus HD 4350 (RV710)


Im also using the HD4350 card
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5387

PostPosted: Wed Dec 16, 2009 2:28 pm    Post subject: Reply with quote

iss wrote:
Just want to post some success (mainly) story.

I'm using libdrm-9999 xf86-video-ati-9999 mesa-9999 and x11-base/xorg-server-1.7.3.901 (1.7.3 and 1.7.1 was ok too).
My integrated HD 3300 (RS780) works ok with gentoo-sources-2.6.32 without KMS.

There is sometimes flickering. GoogleEarth with compositing flickers as hell. Without compositing is ok. Generally compositing works ok (cube, wobbly windows, etc.) but sometimes interferes with some programs.
Glxgears works with same speed with and without compositing (700-800 fps). With fglrx I was getting 750 fps with compositing and 1500 fps without (or 1500 and 3000 - I'm not sure now).
With KMS enabled is a bit worse - more flickering and wobbly glxgears is not smooth.

Yesterday I've tried git-sources-2.6.32-git11 with IRQ enabled firmware.
There is no flickering with KMS. Everything is smooth. Yet it is unusable beacause of lots of artifacts. Graphics are mainly ok, but fonts are unreadable.

Console works ok (1280x1024 DVI) with KMS in all cases.

is it possible to patch gentoo-sources with that patch? I get constant kernel crashes in gentoo-sources based kernels with drm and kms enabled.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
nephros
Advocate
Advocate


Joined: 07 Feb 2003
Posts: 2139
Location: Graz, Austria (Europe - no kangaroos.)

PostPosted: Wed Dec 16, 2009 6:10 pm    Post subject: Reply with quote

Not sure if it mas mentioned already in this thread, but for me the missing puzzle in getting KMS to work was

  • building drm/dri/radeon non-modular (I don't use initrds)
  • disabling anything related to framebuffers in kernel config
  • adding video=1024x768-32@60 radeon.modeset=1 to the kernel command line <= no video=radeonfb: or video=vesafb:, just the mode!
  • building the firmware for the card in question into the kernel using CONFIG_FIRMWARE_IN_KERNEL and CONFIG_EXTRA_FIRMWARE="radeon/R300_cp.bin" <= this is important!


My hardware is a vintage Radeon Xpress 200m a.k.a. RS400, adjust the relevant firmware file for yours.

HTH someone.
_________________
Please put [SOLVED] in your topic if you are a moron.
Back to top
View user's profile Send private message
iss
Tux's lil' helper
Tux's lil' helper


Joined: 30 Oct 2006
Posts: 134
Location: Poland/Bydgoszcz

PostPosted: Wed Dec 16, 2009 10:17 pm    Post subject: Reply with quote

DaggyStyle wrote:
iss wrote:
Just want to post some success (mainly) story.

I'm using libdrm-9999 xf86-video-ati-9999 mesa-9999 and x11-base/xorg-server-1.7.3.901 (1.7.3 and 1.7.1 was ok too).
My integrated HD 3300 (RS780) works ok with gentoo-sources-2.6.32 without KMS.

There is sometimes flickering. GoogleEarth with compositing flickers as hell. Without compositing is ok. Generally compositing works ok (cube, wobbly windows, etc.) but sometimes interferes with some programs.
Glxgears works with same speed with and without compositing (700-800 fps). With fglrx I was getting 750 fps with compositing and 1500 fps without (or 1500 and 3000 - I'm not sure now).
With KMS enabled is a bit worse - more flickering and wobbly glxgears is not smooth.

Yesterday I've tried git-sources-2.6.32-git11 with IRQ enabled firmware.
There is no flickering with KMS. Everything is smooth. Yet it is unusable beacause of lots of artifacts. Graphics are mainly ok, but fonts are unreadable.

Console works ok (1280x1024 DVI) with KMS in all cases.

is it possible to patch gentoo-sources with that patch? I get constant kernel crashes in gentoo-sources based kernels with drm and kms enabled.


I think IRQ handling is introduced in git7 sources. If as "that patch" you mean new firmware I've just put two files (R600_rlc.bin and R700_rlc.bin) to /lib/firmware/radeon. Without this firmware acceleration was disabled with KMS and sources git7 and above.
BTW There is advice to disable any framebuffer modules.
Don't forget to make firmware_install.

And contrary to what nephros said I had to build DRM/Radeon as module.
Back to top
View user's profile Send private message
pingufunkybeat
l33t
l33t


Joined: 01 Dec 2004
Posts: 610

PostPosted: Thu Dec 17, 2009 12:22 pm    Post subject: Reply with quote

Herring42 wrote:
KMS and ati-9999 is working, but the console is just blank until X starts.

Make sure to disable all framebuffer console stuff as it can interfere with the KMS console. I think that it uses fbcon, you should disable radeon-specific framebuffers and such.

Quote:

Also, running glxgears, I get this error:
Code:
do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
Try adjusting the vblank_mode configuration parameter.
8118 frames in 5.0 seconds = 1623.456 FPS
8310 frames in 5.0 seconds = 1661.910 FPS
8567 frames in 5.0 seconds = 1713.256 FPS

What's up with my IRQs?

Interrupt support was pushed recently, you'll need the latest stuff from git to enable them. Not much stuff is using them ATM, but they are a prerequisite for sync-to-blank and dynamic power management.
Back to top
View user's profile Send private message
Herring42
Guru
Guru


Joined: 10 Mar 2004
Posts: 373
Location: Buckinghamshire

PostPosted: Fri Dec 18, 2009 10:51 am    Post subject: Reply with quote

pingufunkybeat wrote:
Herring42 wrote:
KMS and ati-9999 is working, but the console is just blank until X starts.

Make sure to disable all framebuffer console stuff as it can interfere with the KMS console. I think that it uses fbcon, you should disable radeon-specific framebuffers and such.


All disabled, but still no joy. Takes an age to display X if the screen goes into power save too.

Quote:


Quote:

Also, running glxgears, I get this error:
Code:
do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
Try adjusting the vblank_mode configuration parameter.
8118 frames in 5.0 seconds = 1623.456 FPS
8310 frames in 5.0 seconds = 1661.910 FPS
8567 frames in 5.0 seconds = 1713.256 FPS

What's up with my IRQs?

Interrupt support was pushed recently, you'll need the latest stuff from git to enable them. Not much stuff is using them ATM, but they are a prerequisite for sync-to-blank and dynamic power management.


Ahh. Just have to wait a bit then.
_________________
"The problem with quotes on the internet is that it is difficult
to determine whether or not they are genuine." -- Abraham Lincoln
Back to top
View user's profile Send private message
VinzC
Watchman
Watchman


Joined: 17 Apr 2004
Posts: 5021
Location: Dark side of the mood

PostPosted: Fri Dec 18, 2009 3:59 pm    Post subject: Reply with quote

Hi all.

I've just --sync'ed yesterday and have tried to switch to 2.6.32. KMS works perfectly for consoles but I also get a garbled screen when X starts. I can switching back to consoles, they're not altered. just that X screen is garbled with lines, as is the mouse pointer.

I guess I have to upgrade one component. Can you guys tell me which one? If this error message (from X log is enough, just in case):
Code:
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch.
[dri] radeon kernel module version is 2.0.0 but version 1.17.0 or newer is needed.
--
(EE) RADEON(0): Acceleration initialization failed
(II) RADEON(0): acceleration disabled

Is libdrm enough or should I also pull down the latest xf86-video-ati?

(I have a Radeon RV636, aka Mobility HD3670)
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!


Last edited by VinzC on Sat Jan 16, 2010 6:22 pm; edited 1 time in total
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5387

PostPosted: Fri Dec 18, 2009 4:28 pm    Post subject: Reply with quote

VinzC wrote:
Hi all.

I've just --sync'ed yesterday and have tried to switch to 2.6.32. KMS works perfectly for consoles but I also get a garbled screen when X starts. I can switching back to consoles, they're not altered. just that X screen is garbled with lines, as is the mouse pointer.

I guess I have to upgrade one component. Can you guys tell me which one? If this error message (from X log is enough, just in case):
[code](EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch.
[dri] radeon kernel module version is 2.0.0 but version 1.17.0 or newer is needed.
--
(EE) RADEON(0): Acceleration initialization failed
(II) RADEON(0): acceleration disabled[code]
Is libdrm enough or should I also pull down the latest xf86-video-ati?

(I have a Radeon RV636, aka Mobility HD3670)

to be sure, get kernel 2.6.32(from the tree), libdrm, mesa and xf86-video-ati all from svn
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
pingufunkybeat
l33t
l33t


Joined: 01 Dec 2004
Posts: 610

PostPosted: Fri Dec 18, 2009 5:30 pm    Post subject: Reply with quote

xf86-video-ati must be configured with --radeon-experimental-api to use KMS

I'm not sure if the stable releases have this. It's best to get a git radeon driver and make sure that it is configured properly by looking into the ebuild.
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5387

PostPosted: Fri Dec 18, 2009 6:56 pm    Post subject: Reply with quote

pingufunkybeat wrote:
xf86-video-ati must be configured with --radeon-experimental-api to use KMS

I'm not sure if the stable releases have this. It's best to get a git radeon driver and make sure that it is configured properly by looking into the ebuild.

are you sure? I'm using the svn version and I'm pretty sure that I don't use that feature and I've got vanilla sources with drm and kms working
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
VinzC
Watchman
Watchman


Joined: 17 Apr 2004
Posts: 5021
Location: Dark side of the mood

PostPosted: Fri Dec 18, 2009 7:36 pm    Post subject: Reply with quote

DaggyStyle wrote:
to be sure, get kernel 2.6.32(from the tree), libdrm, mesa and xf86-video-ati all from svn

Thanks, man. Are these the ebuilds you posted at the beginning of this thread?
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3 ... 8, 9, 10 ... 27, 28, 29  Next
Page 9 of 29

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum