April 2010 - Radeon HD - openSUSE Mailing Lists

0x719B:0x1002:0x0602: FireMV 2250 Problem with PLL programming
by Ales Fiala 23 Apr '10

23 Apr '10

Folks, I need some help from someone who understands the PLL programming. I have a FireMV2250 with RV516 GPU. I just came across an old CRT monitor that has a mode for which I can't synthesize a pixel clock. The mode is the following: Mode "1800x1440": 299.70 MHz, 120.85 kHz, 80.0 Hz Modeline "1800x1440" 299.70 1800 1941 2133 2480 1440 1442 1449 1510 -hsync +vsync My initial problem is the following message in the log file: (II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Output: 900000 (WW) RADEONHD(0): Higher minimum PLL output detected than the default: 648000 9000000. Please contact the authors ASAP. (II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Output: 1100000 OK, one of the numbers in this message is off by a factor of 10 but that's only a problem in the print. Internally the numbers are used correctly. The message is telling me that the ATOM BIOS specifies the minimum PLL clock output to be 900 MHz. And that is higher than the default of 648 MHz. I am to contact the authors ASAP, so here it is. My second problem is that after warning me, the code then uses the clock range specified by the ATOM BIOS, the 900-1100 MHZ. It does not use the default range of 648-1100 MHz. This makes some pixel clock frequencies, like the 299.7 MHz in the above mode, not achievable. Remember that <pixel clock> = <PLL clock> / <post divisor>. I made a table of the first few post divisors and the pixel clock range they can achieve: PLL output range post divisor pixel clock range 900-1100 / 2 = 450-550 * no overlap with next range 900-1100 / 3 = 300-366 * no overlap with next range 900-1100 / 4 = 225-275 * no overlap with next range 900-1100 / 5 = 180-220 900-1100 / 6 = 150-183 900-1100 / 7 = 128-157 Note that there are gaps between the achievable pixel clock ranges. Some pixel clocks just can't be synthesized with these constraints. So should the code be fixed to ignore the ATOMBIOS specified range and use the default range? With the default range there are no gaps in the pixel clock since it is wider. Or should the range be widened only a little to make all frequencies achievable? By my calculations the range of 732-1100 would be sufficient. Thanks for your help. Ales Fiala Hewlett Packard -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

2 2

0x7244:0x18BC:0x3192: 1950 XT
by Tim 22 Apr '10

22 Apr '10

Hello, I recently updated to the current Debian Sid packages and recompiled with the latest Debian 2.6.32 kernel. Since then, my video refresh has become quite slow. For instance, when I switch between desktops, I have to watch for as much as 1 or 2 seconds for my browser window to repaint itself, rectangle by rectangle. I suppose it's possible that this issue is a problem in Xorg, but since my card still isn't recognized correctly by the radeonhd drivers, I figured this would be the most likely culprit. My card is a (X)1950 XT, but both lspci and the radeon driver initially detect it as an X1900. A number of warnings show up in the Xorg log (see attached). I believe I've submitted a request before to have this card recognized. Let me know if there's anything else I can provide to help you add it to the driver. Thanks much, tim

3 5

0x954F:0x174B:0x0E13: RV710 (Sapphire Radeon HD4350 512MB DDR2)
by co 19 Apr '10

19 Apr '10

Hi. Im using this card in a crossfire-capable motherboard. I hope this problem is not reported, so i dont make you spend time. Problem: With firmware-linux-nonfree (0.23) package intalled, screen goes black, system becomes unusable when loading X. Software versions im using: DEBIAN SID. Here are some Xorg.0.log ... X.Org X Server 1.7.6.901 (1.7.7 RC 1) Release Date: 2010-04-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-4-amd64 x86_64 Debian Current Operating System: Linux compu 2.6.32-3-amd64 #1 SMP Wed Feb 24 18:07:42 UTC 2010 x86_64 Kernel command line: root=/dev/sdc6 ro Build Date: 17 April 2010 04:48:18PM xorg-server 2:1.7.6.901-2 (Cyril Brulebois <kibi(a)debian.org>) ... (EE) RADEONHD(0): RHDDRIVersionCheck: drmOpen("radeon", "pci:0000:01:00.0") failed. (WW) RADEONHD(0): RHDDRIPreInit: Version check failed. Disabling DRI. (WW) RADEONHD(0): Falling back to ShadowFB acceleration ... but -i think- this last message is because of i dont have firmware-linux-nonfree. So, please tell me if you need more logs with this package installed (when the problem happens). Best Regards. -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

Fresh 'git pull' now radeonhd won't build - error: invalid storage class
by David C. Rankin 19 Apr '10

19 Apr '10

Matthias, all I was updating my spare drive for my laptop and I thought I would build the radeonhd driver and see if any recent changes would have helped with the blackscreen issue. I didn't even get that far and I ran into a new problem. autogen.sh --prefix /usr completed just fine, but then during make I received the following error: 01:39 alchemy:~/apps/rhd/_b> make Making all in src git_version.sh: Output is new file, creating git_version.h CC r5xx_accel.o CC r5xx_xaa.o CC r600_shader.o CC radeon_3d.o CC radeon_textured_videofuncs.o CC rhd_atombios.o CC rhd_atomcrtc.o CC rhd_atomout.o CC rhd_atompll.o CC rhd_audio.o CC rhd_biosscratch.o CC rhd_connector.o CC rhd_crtc.o CC rhd_cs.o CC rhd_cursor.o CC rhd_dac.o CC rhd_ddia.o CC rhd_dig.o CC rhd_driver.o ../../src/rhd_driver.c: In function ‘RHDPciProbe’: ../../src/rhd_driver.c:517: error: invalid storage class for function ‘RHDPreInit’ ../../src/rhd_driver.c:1097: error: invalid storage class for function ‘RHDScreenInit’ ../../src/rhd_driver.c:1339: error: invalid storage class for function ‘rhdAllIdle’ ../../src/rhd_driver.c:1365: error: invalid storage class for function ‘rhdEngineIdle’ ../../src/rhd_driver.c:1393: error: invalid storage class for function ‘RHDCloseScreen’ ../../src/rhd_driver.c:1453: error: invalid storage class for function ‘RHDFreeScreen’ ../../src/rhd_driver.c:1460: error: invalid storage class for function ‘RHDEnterVT’ ../../src/rhd_driver.c:1552: error: invalid storage class for function ‘RHDLeaveVT’ ../../src/rhd_driver.c:1578: error: invalid storage class for function ‘RHDSwitchMode’ ../../src/rhd_driver.c:1602: error: invalid storage class for function ‘RHDAdjustFrame’ ../../src/rhd_driver.c:1625: error: invalid storage class for function ‘RHDDisplayPowerManagementSet’ ../../src/rhd_driver.c:1707: error: invalid storage class for function ‘RHDLoadPalette’ ../../src/rhd_driver.c:1782: error: invalid storage class for function ‘RHDSaveScreen’ ../../src/rhd_driver.c:1839: error: invalid storage class for function ‘rhdMapMMIO’ ../../src/rhd_driver.c:1874: error: invalid storage class for function ‘rhdUnmapMMIO’ ../../src/rhd_driver.c:1892: error: invalid storage class for function ‘rhdGetVideoRamSize’ ../../src/rhd_driver.c:1922: error: invalid storage class for function ‘rhdMapFB’ ../../src/rhd_driver.c:2043: error: invalid storage class for function ‘rhdUnmapFB’ ../../src/rhd_driver.c:2065: error: invalid storage class for function ‘rhdFbOffscreenGrab’ ../../src/rhd_driver.c:2119: error: invalid storage class for function ‘rhdOutputConnectorCheck’ ../../src/rhd_driver.c:2160: error: invalid storage class for function ‘rhdModeLayoutSelect’ ../../src/rhd_driver.c:2309: error: invalid storage class for function ‘rhdModeDPISet’ ../../src/rhd_driver.c:2401: error: invalid storage class for function ‘rhdModeLayoutPrint’ ../../src/rhd_driver.c:2498: error: invalid storage class for function ‘rhdModeInit’ ../../src/rhd_driver.c:2512: error: invalid storage class for function ‘rhdSetMode’ ../../src/rhd_driver.c:2568: error: invalid storage class for function ‘rhdSave’ ../../src/rhd_driver.c:2597: error: invalid storage class for function ‘rhdRestore’ ../../src/rhd_driver.c:2742: error: invalid storage class for function ‘rhdAccelOptionsHandle’ ../../src/rhd_driver.c:2833: error: invalid storage class for function ‘rhdProcessOptions’ ../../src/rhd_driver.c:2919: error: invalid storage class for function ‘rhdDoReadPCIBios’ ../../src/rhd_driver.c:3058: error: invalid storage class for function ‘rhdGetIGPNorthBridgeInfo’ ../../src/rhd_driver.c:3082: error: invalid storage class for function ‘rhdGetCardType’ ../../src/rhd_driver.c:3141: error: expected declaration or statement at end of input make[3]: *** [radeonhd_drv_la-rhd_driver.lo] Error 1 make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 What's up? Let me know if you need anything else from the build attempt. I can always grab info off the spare drive with a usb connector. Keep up the good work and maybe once we get past this, I'll see if the blackscreen issue for the RS690M has been fixed with recent changes :-) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

2 2

xf86-video-radeonhd:master: 1 commit(s)
by mhopf＠kemper.freedesktop.org 19 Apr '10

19 Apr '10

Reporting from xf86-video-radeonhd: Radeon HD video driver Please visit: http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-radeonhd Or get your own copy by using: git-clone git://anongit.freedesktop.org/xorg/driver/xf86-video-radeonhd Commit against master at 97d82522...: commit 4abbce4498f9a5eaff728f48710d8abe9ee9c012 Author: Matthias Hopf <mhopf(a)suse.de> Date: Mon Apr 19 12:37:53 2010 +0200 Fix compilation in non-DRI case (invalid storage class errors). diffstat: src/rhd_driver.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) gitweb url: http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-radeonhd;a=commit;h… -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

0x7146:0x17AF:0x2158: (unknown card)
by Michael Koch 14 Apr '10

14 Apr '10

Hi! I have tested the latest GIT version of the radeonhd driver on my Ubuntu 9.10 box. The card only detects my monitor which is connected to digital DVI if I set the option HPD to off. The driver reports that my card with ID 0x7146:0x17AF:0x2158 is not in the database. Unfortunately I do not know the brand and name of the graphics card since I only have the board and no documentation. There is no identification on the board itself besides a sticker which says ATI RV515 [Radeon X1300]. I've attached the Xorg.0.log and my xorg.conf. Here is the info of lspci -v for the graphics card: 01:00.0 VGA compatible controller: ATI Technologies Inc RV515 [Radeon X1300] Subsystem: Hightech Information System Ltd. Device 2158 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11 Memory at b0000000 (32-bit, prefetchable) [size=256M] I/O ports at a800 [size=256] Memory at cfef0000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at cfec0000 [disabled] [size=128K] Capabilities: [50] Power Management version 2 Capabilities: [58] AGP version 2.0 Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Kernel modules: radeon 01:00.1 Display controller: ATI Technologies Inc RV515 [Radeon X1300] (Secondary) Subsystem: Hightech Information System Ltd. Device 2159 Flags: bus master, 66MHz, medium devsel, latency 64 Memory at cfee0000 (32-bit, non-prefetchable) [size=64K] Capabilities: [50] Power Management version 2 Is there anything I can do to help with the HPD detection? Cheers Michael Koch Section "Device" Identifier "Device0" Driver "radeonhd" Option "HPD" "off" EndSection

1 0

0x954F:0x174B:0xE106: ATI Technologies Inc RV710 [Radeon HD 4350] (Sapphire Radeon HD)
by Wolfram Nyaa~ 14 Apr '10

14 Apr '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. I tried radeonhd driver and it's not working properly. So, I'm writing this letter as suggested by radeonhd entries in X log. After "startx" screen became blank, system halts and don't react for any input except alt+sysrq. But it's still possible to login via ssh and reboot. Killing X doesn't help. Linux core 2.6.33-gentoo-05 #1 SMP PREEMPT Sat Mar 27 12:47:42 NOVT 2010 x86_64 Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz GenuineIntel GNU/Linux I'm using the following xorg.conf: Section "Files" EndSection Section "Module" #Load "dbe" Load "dri" Load "glx" Load "drm" EndSection Section "Monitor" Identifier "Samsung F2380" Option "DPMS" "true" Option "Enable" "true" Option "Primary" "true" EndSection Section "Monitor" Identifier "Samsung 172T" Option "DPMS" "true" Option "Enable" "true" Option "LeftOf" "Samsung F2380" EndSection Section "Device" Identifier "primary-radeon" Driver "radeon" BusID "PCI:1:0:0" Option "Monitor-HDMI-0" "Samsung F2380" Option "Monitor-DVI-0" "Samsung 172T" EndSection Section "Device" Identifier "secondary-radeon" Driver "radeonhd" BusID "PCI:6:0:0" EndSection Section "Screen" Identifier "Screen F2380" Device "primary-radeon" Monitor "Samsung F2380" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1920x1080" EndSubSection EndSection Section "Screen" Identifier "Screen 172T" Device "primary-radeon" Monitor "Samsung 172T" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x1024" EndSubSection EndSection Section "ServerLayout" Identifier "MainLayout" Screen 0 "Screen F2380" 0 0 Screen 1 "Screen 172T" RightOf "Screen F2380" # DualHead means two monitors #Option "DualHead" "True" EndSection Section "DRI" Mode 0666 EndSection Section "ServerFlags" Option "DRI2" "true" EndSection Section "InputClass" Driver "evdev" Identifier "Generic Devices" Option "XkbModel" "evdev" MatchTag "generic" EndSection Section "InputClass" Identifier "Garbage" Option "ignore" "true" MatchTag "garbage" EndSection -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLxcj3AAoJEN9tENx5d7sAtggIAJjro6dtEzZmzJ3gRwY/tRlH Z636dflKqao6ddK1DI7+8jv+aGVFTNgfBnhPAXlUG6o4pdLjJisclAqvchlal24A lmnzlk4+9zcVtNdtJm8px/qLG+gwdkfmoySi8XroBmPVgW/NGftnnwW56LKjzds5 Tsk7IHvx4+2Tu2VIDVJtC70t+dy1TVEjaZTTMIiBUWSoGof1zznKfHwPSkeiDcnW sc4fKmPJR4qJxCHEoNsFY5P01HeHXovJ71OH24wJji1K5OaJBozd4y4FgrcIYAQe nsTNLzs95KQU6wNN7WTiS4j39svnMQo8+RFDGkUBTOTxDDnfP6kmCaOonYnQ3KQ= =hbGK -----END PGP SIGNATURE-----

1 0

0x71C5:0x1558:0x0571: Radeon Mobility X1600
by Brian Bergstrom 13 Apr '10

13 Apr '10

X halts on startup. The screen goes blank and freezes the system. I cannot even ctrl-alt-fn to another tty. [brian@defiant ~]$ uname -a Linux defiant 2.6.32-ARCH #1 SMP PREEMPT Mon Mar 15 20:08:25 UTC 2010 i686 Genuine Intel(R) CPU T2400 @ 1.83GHz GenuineIntel GNU/Linux [brian@defiant ~]$ lspci |grep VGA 01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon Mobility X1600] [brian@defiant ~]$

2 1

0x9710:0x1565:0x1704 ATI Technologies Inc RS880 [Radeon HD 4200]
by current resident 13 Apr '10

13 Apr '10

hi, new biostar motherboard: TA785G3HD AM3 AMD 785G HDMI Micro ATX AMD Xorg.0.log has these errors: (EE) RADEONHD(0): [dri] CP_INIT failed (EE) RADEONHD(0): RHDDRIFinishScreenInit: RHDDRIKernelInit Failed. also Xorg.0.log includes: --) RADEONHD(0): Detected an RS880 on an unidentified card (II) RADEONHD(0): Mapped IO @ 0xfeaf0000 to 0xb71cb000 (size 0x00010000) (II) RADEONHD(0): Getting BIOS copy from legacy VBIOS location (II) RADEONHD(0): ATOM BIOS Rom: SubsystemVendorID: 0x1002 SubsystemID: 0x1002 IOBaseAddress: 0xd000 Filename: 13B43106.004 BIOS Bootup Message: 113-B43106-004 RS880 DDR2 200e/500m (II) RADEONHD(0): Analog TV Default Mode: 0 (II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture. (II) RADEONHD(0): Using only 262144kB of the total 393216kB. (--) 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: 0x17ffb000 (II) RADEONHD(0): AtomBIOS requests 20kB of VRAM scratch space (II) RADEONHD(0): AtomBIOS VRAM scratch base: 0x17ffb000 (WW) RADEONHD(0): rhdAtomAllocateFbScratch: FW FB scratch area 402632704 (size: 20480) extends beyond available framebuffer size 268435456 (II) RADEONHD(0): Cannot get VRAM scratch space. Allocating in main memory instead (II) RADEONHD(0): Default Engine Clock: 500000 (II) RADEONHD(0): Default Memory Clock: 533000 (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: 13500 (II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Input: 1000 (II) RADEONHD(0): Maximum Pixel Clock: 400000 (II) RADEONHD(0): Reference Clock: 14320 (II) RADEONHD(0): Found libdri 5.4.0. moving windows in fluxbox is very slow and gkrellm shows 100% CPU usage during the time it takes for the window to move to a new spot. hope this info is helpful to you in your efforts; thanks for contributing to open source software; resident(a)cfl.rr.com -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

2 1

0x9480:0x103C:0x3628: HP Mobility Radeon HD 4650 [dv6-1190en]
by Philippe De Muyter 10 Apr '10

10 Apr '10

Hello radeon expert, I have installe opensuse 11.3 milestone 4 on a HP laptop equipped with a : 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M96 [Mobility Radeon HD 4650] [1002:9480] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company ATI Mobility Radeon HD 4650 [dv6-1190en] [103c:3628] Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at c0000000 (32-bit, prefetchable) [size=256M] I/O ports at 7000 [size=256] Memory at da000000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at da020000 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> In graphic mode, the driver seems to work well so far, but the problem is that switching to text mode does not work : screen is merely black, without any text. I attach /var/log/Xorg.0.log Philippe

3 7