February 2010 - Radeon HD - openSUSE Mailing Lists

[Bug 20146] New: r6xx-r7xx-support: second radeonhd card initialization failed
by bugzilla-daemon＠freedesktop.org 16 Oct '11

16 Oct '11

http://bugs.freedesktop.org/show_bug.cgi?id=20146 Summary: r6xx-r7xx-support: second radeonhd card initialization failed Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: kl(a)stat.phys.spbu.ru QAContact: xorg-team(a)lists.x.org Created an attachment (id=22995) --> (http://bugs.freedesktop.org/attachment.cgi?id=22995) Xorg.0.log I have a multiseat configuration based on two pci/e radeonhd cards (primary:RS780, secondary:rv710). Both cards are working fine with radeonhd-1.2.4, but when i try r6xx-r7xx-support radeonhd brunch to get 2D hardware acceleration only primary videocard was initialized. I try to initialize videocards separately, but this does not help also. The initialization of secondary chip(rv710) finished with the messages ===================================================================== (--) RADEONHD(0): Detected an RV710 on an unidentified card (II) RADEONHD(0): Mapped IO @ 0xfe7f0000 to 0x7fc084b5c000 (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: 0x1002 SubsystemID: 0x1002 IOBaseAddress: 0xb000 Filename: M3A78T_D_1.b BIOS Bootup Message: B27722 RS780D DDR2 200e/500m (II) RADEONHD(0): Analog TV Default Mode: 4294967040 (EE) RADEONHD(0): No Video RAM detected. (II) UnloadModule: "radeonhd" (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found ===================================================================== As i can see radeonhd driver try to use ATOM BIOS of primary videochip to boot secondary videochip. As result it did not find videoram and failed. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 5

[Bug 20593] New: radeonhd driver generates unaligned traps on Alpha
by bugzilla-daemon＠freedesktop.org 16 May '11

16 May '11

http://bugs.freedesktop.org/show_bug.cgi?id=20593 Summary: radeonhd driver generates unaligned traps on Alpha Product: xorg Version: git Platform: Alpha OS/Version: Linux (All) Status: NEW Severity: minor Priority: low Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: mcree(a)orcon.net.nz QAContact: xorg-team(a)lists.x.org CC: mcree(a)orcon.net.nz The radeonhd driver generates unaligned traps on Alpha architecture. These are not a show stopper, but do incur very inefficient memory accesses via kernel traps, and pollute the kernel logs with annoying messages. Using radeonhd at git df71658688e47614a3f660c28ac1dc77970eb491 But the version is irrelevant as the misaligned memory accesses have been there for a long time - I have been too lazy to report them until now. >From dmesg: X(2015): unaligned trap at 0000020000903088: 000002000098c5d7 28 1 X(2015): unaligned trap at 0000020000903088: 000002000098c5df 28 1 X(2015): unaligned trap at 0000020000903088: 000002000098c5e7 28 1 X(2015): unaligned trap at 0000020000903088: 0000020000989771 28 1 Connecting gdb to the running X process reveals the culprit: (gdb) list *0x0000020000903088 0x20000903088 is in GetParametersDirect32 (AtomBios/CD_Operations.c:441). 436 } 437 438 UINT32 GetParametersDirect32(PARSER_TEMP_DATA STACK_BASED * pParserTempData) 439 { 440 pParserTempData->CD_Mask.SrcAlignment=alignmentDword; 441 pParserTempData->Index=*(UINT32*)pParserTempData->pWorkingTableData->IP; 442 pParserTempData->pWorkingTableData->IP+=sizeof(UINT32); 443 return pParserTempData->Index; 444 } 445 Line 441 is a 32bit (long word) access. The address dereferenced is not aligned to a 32bit boundary for an unaligned trap to occur. The ati driver is worse. It coughs up unaligned traps from GetParametersDirect16() and GetParametersRegister() too, but I haven't seen these from radeonhd. Cheers Michael. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

3 10

[Bug 25309] New: OpenGL corruption with radeonhd on HD 4850
by bugzilla-daemon＠freedesktop.org 09 Mar '11

09 Mar '11

http://bugs.freedesktop.org/show_bug.cgi?id=25309 Summary: OpenGL corruption with radeonhd on HD 4850 Product: xorg Version: 7.5 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/radeonhd AssignedTo: eich(a)pdx.freedesktop.org ReportedBy: dawitbro(a)sbcglobal.net QAContact: xorg-team(a)lists.x.org Created an attachment (id=31493) --> (http://bugs.freedesktop.org/attachment.cgi?id=31493) xorg.conf Overview: Enabling OpenGL support in apps while using combination of radeonhd with RV770 GPU leads to massive screen corruption. It's likely that this is a very hardware-specific issue -- see reference to fdo bug #24301 in "Additional information" section below. Originally this bug was shared by radeon as well as radeonhd, but has been fixed in xf86-video-ati by Alex Deucher (commit 5f84636...), so it now is present in radeonhd only. Steps to reproduce: I've been using two apps to test OpenGL: 'prboom' and 'dosbox'. (I believe that running any app using OpenGL would result in the same massive rendering corruption.) prboom: running 'prboom -vidmode gl' enables OpenGL support, resulting in corruption. (Running 'prboom' without "-vidmode gl" option disables OpenGL, and rendering is fine.) dosbox: graphics output mode is controlled by ~/.dosboxrc, in the section called "[sdl]", and using the option "output=opengl" enables OpenGL support. (Setting this to other output modes, such as "output=overlay", disables OpenGL in DOSBox and results in perfect rendering.) Actual results: prboom: running prboom with OpenGL enabled results in massive screen corruption. The game does not crash, but all surfaces and enemies are rendered in a garbled fashion. Essentially unplayable, unless you want to take an "acid trip" without the LSD. dosbox: Running an old DOS game (I've been using Warlords 2) with OpenGL enabled results in worse corruption than with 'prboom', and is totally unusable. DOSBox is not crashed, and the game's keyboard shortcuts are working, but you cannot see anything at all except the unchanging, corrupt graphics. Both test apps spam my dmesg and kern.log files with this message when running with OpenGL enabled: [drm:r600_cp_dispatch_texture] *ERROR* Invalid destination offset Expected results: both apps should render the games without corrupting the graphics and with all of the benefits OpenGL has to offer (acceleration, superior rendering quality, etc.). System info: GPU: GIGABYTE GV-R485MC-1GI Radeon HD 4850 (RV770) 1GB VRAM, 256-bit GDDR3 PCI Express 2.0 x16 Kernel + architecture: [uname -r -m] 2.6.32-rc8-0git091120.desktop.uvesafb x86_64 Linux distribution: Debian unstable Machine: self-built MSI 790FX-GD70 motherboard socket AM3 AMD 790FX and SB750 Chipset OCZ OCZ3P1600EB4GK 2x2GB DDR3 1600 AMD Phenom II X4 955 Software versions: xf86-video-radeonhd: git commit 6387ab4..., dated 11-12-2009 Mesa-7.7-devel: git commit 37676b3..., dated 11-15-2009 libdrm: release 2.4.15 tarball XOrg Server: 1.7.0 from Debian experimental, dated 10-04-2009 prboom: v2.5.0 DOSBox: v0.72 Additional versions: radeonhd: initially was using 1.2.5 from Debian unstable; built radeon 1.3.0 from official release tarball in early November before upgrading to the version mention above on Nov. 12 Mesa: initially using Mesa-7.7-devel from tarball, dated 11-05-2009 X Server: initially using 1.6.5 from Debian unstable (Other software -- libdrm, prboom, and DOSBox -- remained unchanged.) Symptoms with OpenGL enabled did not change (on radeonhd) with any of the mentioned version changes. Additional Information: This problem was discovered in the process of experimenting with 2D/3D acceration support for my RV770 GPU. Debian did not include support for Radeon 'r600' in their Mesa-7.6 packages, so I had to build upstream versions of libdrm, Mesa-7.7-devel, and xf86-video-radeonhd to get the necessary support for 'r600'. I also have experimented with xf86-video-ati. The "xserver-xorg-video-radeon" package in Debian unstable (from xf86-video-ati) was version 6.12.3 when I began experimenting. It also produced the same graphics corruption I am seeing with "radeonhd", including the "r600_cp_dispatch_texture" error spam in my logs. However, it was discovered by Alex Deucher that a problem in the "radeon" DDX driver having to do with large amounts of VRAM was the cause of the problem with that driver. (See fdo bug #24301.) Matthias Hopf believes that the root cause of this identical corruption (and log spam) I am experiencing with "radeonhd" is not the same as for "radeon", however. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 6

[Bug 22114] New: monitor sometimes stays flashing black
by bugzilla-daemon＠freedesktop.org 21 Jan '11

21 Jan '11

http://bugs.freedesktop.org/show_bug.cgi?id=22114 Summary: monitor sometimes stays flashing black Product: xorg Version: 7.4 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: estellnb(a)gmail.com QAContact: xorg-team(a)lists.x.org Using the new xorg-x11-driver-video-radeonhd-1.2.5_20090506_4be5f71-3.1 driver with kernel2.6.30-rc5-git1-master_20090515173431_9c6d4c14-default as recommended a very strange error annoys me from time to time: The screen suddenly turns black for about a second; then it continues to view everything as usual. This happens multiple times in sequence and may not stop at all; very annoying. using a FS Scaleoview Q26W-1 1920x1200 monitor. Singleton turn-blacks have occured with previous versions but they did not annoy. Now they occur multiple times in sequence and may not stop at all. May be related with bug 21896, since it sometimes occurs more often on scrolling. Very likely related to the new radeonhd driver since the rest of the system has stayed the same; i.e. I have not updated Xorg or any other relevant component than the 2.6.30 kernel required for the new radeonhd. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 28

Re: [radeonhd] no compositing (gnome/kwin) with FireGL v5200
by Egbert Eich 31 May '10

31 May '10

Antenore Gatta writes: > Hello, > > I'm quite sure I did some mistake in the configuration, so before to > open a bug I'd be really glad if someone can help me to troubleshoot > my issue. > > I've an ATI mobility Firegl v5200 (lenovo T60p) > > I pastebin some info at http://pastebin.com/m40597c37 > > I've first moved from using the fglrx to radeonhd 1.2.4, as I was > quite happy with it (just really slow), I've upgraded to the last > versions of radeonhd (from mesa 7.7.2) and kernel 2.6.32 > > 2D works perfectly, 3D works with OpenGL applications (I tried > glxgears), but not the compositing with Gnome and/or kwin (AIGLX, glx, > dri and composite are enabled). What problems are you seeing actually? Cheers, Egbert. -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

3 3

Re: [radeonhd] AMD 690G - dual head mode at high res.
by Egbert Eich 25 Mar '10

25 Mar '10

scott.radeonhd(a)scottrix.co.uk writes: > All > > I have a gigabyte GA-MA690G-S3H motherboard with the AMD 690G chipset. > Until recently I was using the VGA output connected to a 1280x1024 CRT and > the DVI_D output connected to a 1920x1200 LCD, this worked fine. I now > have two 1920x1200 LCDs one connected to the VGA and one to the DVI_D, > however, I have been unable to get the VGA to display at 1920x1200. > Instead everything in software on the box thinks the VGA is at 1920x1200 > (xrandr, but X start up logs), however, the screen is actually at > 1600x1200. The radeon (NOT HD) driver seemed to work a little better in > that both screens were put in the same mode, however, the bottom screen in > the setup would always get corruption. I am now using the ati driver which > seems to work fine for this setup. > > I am not sure how much testing I can do since this PC is used daily by > myself and my wife and taking down X and restarting it would be a real > pain. I might be able to do some testing with a second X server running on > a different VT if people think that won't destroy my current setup. > > I thought that maybe I am doing something wrong and if not then maybe > someone on the list can test this setup and confirm it and then raise a bug > if they can. > Please provide a a verbose log file. To obtain this start X from the console with: 'X -logverbose 7' and terminate it with ctrl-alt-backspace. Cheers, Egbert. -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

4 9

Re: [radeonhd] 0x9611:0x1043:0x82EE: ASUS M3A78-CM onboard AMD780V(RS780)
by Egbert Eich 15 Mar '10

15 Mar '10

Jakob Bohm writes: > > > > > > If a video adapter must be set to the same refresh rate for VGA > > > and video output, the NTSC resulution with 60Hz Interlaced may be > > > a better choice to match 60Hz VGA signals. As always, a user > > > configured monitor overrides any compiled in defaults and may be > > > configured to override autodetection too. > > > > > Isn't this how it is working presently? User supplied modes always > > have priority, however they are not used unconditionally but verified > > against various other settings. > > > > No that is precisely NOT how it is working presently (at least in > 1.2.5): There is no known (==documented) option that makes > radeonhd believe my configured monitor over its own flawed > autodetection of "no" monitor present. There are options to tell > radeonhd that there is no monitor even if it detects one, but no > option to tell it there IS a monitor. This is correct. If no monitor is detected there is presently no way around this. But as soon as a monitor is detected as connected the user supplied modes have precedence. > > There should be NO situation in which the autodetection of > anything but the adapter itself should cause the driver to refuse > to load. The very existence of the execution path that ends by > outputting the message "(EE) RADEONHD(0): Failed to detect a > connected monitor" is a bug. The problem here is that DVI connectors can have digital or analog monitors connected. So even if we assume that something is connected we still don't know which output to enable. We could just enable both and hope for the best - the problem here is that due to the chip design it's not always possible to share a crtc between analog and digital outputs as the crtc might have to be programmed slightly differently. This is not true in all cases. We could of course add an elaborate option where the user can specify what sort of output is connected. > > The inability to identify the connected monitor should lead to > "All known modes are potentially valid" > (like in old drivers without autodetection), not to > "(WW) RADEONHD(0): Unable to find initial modes" > "(EE) RADEONHD(0): RandR: No valid modes. Disabling RandR support." > > In summary, the radeonhd code currently scheduled for inclusion in > the next Debian release seems extremely lopsided in its desire to > consider the card useless until otherwise proven. > I do agree that the monitor detection code needs to be more tolerant and at least try to fall back to probing for the presence of a monitor thru ddc if other methods fail. Cheers, Egbert. -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

4 8

0x9710:0x1462:0x7596
by Omer Uner GUCLU 05 Mar '10

05 Mar '10

Hello all, My Xorg.log contains : (II) RADEONHD: version 1.3.0, built from dist of git branch master, commit 79a0ab2f (II) Primary Device is: PCI 01@00:05:0 (EE) KMS is disabled. This is good for us, because RADEONHD conflicts with KMS. (**) RADEONHD(0): Depth 24, (--) framebuffer bpp 32 (**) RADEONHD(0): Option "DRI" "on" (**) RADEONHD(0): Selected EXA 2D acceleration. (II) RADEONHD(0): Card not in database: 0x9710:0x1462:0x7596; using generic modesetting. If - and only if - your card does not work or does not work optimally please contact radeonhd(a)opensuse.org to help rectify this. Use the subject: 0x9710:0x1462:0x7596: <name of board> and *please* describe the problems you are seeing in your message. (--) RADEONHD(0): Detected an RS880 on an unidentified card (II) RADEONHD(0): Mapped IO @ 0xfeaf0000 to 0x7fce221ea000 (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 Would you give me any advice ? -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

4 3

[Bug 22213] New: [EXA] Blur on y-axis also when only x-axis is scaled billiear
by bugzilla-daemon＠freedesktop.org 03 Mar '10

03 Mar '10

http://bugs.freedesktop.org/show_bug.cgi?id=22213 Summary: [EXA] Blur on y-axis also when only x-axis is scaled billiear Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: linuxhippy(a)gmail.com QAContact: xorg-team(a)lists.x.org Created an attachment (id=26644) --> (http://bugs.freedesktop.org/attachment.cgi?id=26644) screenshot illustrating the problem When scaling a picture in x-axis and billinear filtering is requested, the y-axis is blurred too. Seems to me like an off-one-half bug. The attached screenshot illustrates the problem. The first (top) line was rendered with pixman (NoAccel), the second line with exa on my HD3850 / Ubuntu 9.04 live cd. This causes problems with themes that cache pre-rendered elements in pixmaps and use them scaled later on. (E.g. button outline is blurred instead of sharp 1px line). -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 2

0x9613:0x1179:0xFF6A: Toshiba L300D
by Sean MacLennan 27 Feb '10

27 Feb '10

Hi, I didn't know what to put for name of board since it is a laptop (Toshiba Satellite L300D) and the video is built in ;) Here is the lspci -s1:5 -v output: 01:05.0 VGA compatible controller: ATI Technologies Inc RS780MC [Radeon HD 3100 Graphics] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device ff6a Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at e0000000 (32-bit, prefetchable) [size=256M] I/O ports at 7000 [size=256] Memory at f6300000 (32-bit, non-prefetchable) [size=64K] Memory at f6200000 (32-bit, non-prefetchable) [size=1M] Expansion ROM at <unassigned> [disabled] Capabilities: [50] Power Management version 3 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Kernel driver in use: radeon The radeon driver works (obviously, I am using it now), but I am trying to get compiz running and it needs radeonhd? I have tried both 1.2.5 and 1.3.0. With both, I just get a blank white screen. Since I got the "card not in database" error I thought I would see if this is a known problem. I am running Slackware 13.0 and the following is the complete xorg.conf file. If I don't specify radeonhd, it defaults to the radeon driver. Section "Device" Identifier "Radeon" Driver "radeonhd" EndSection I have also attached the Xorg.0.log file... I hope attachments are not a problem. Cheers, Sean

2 1