June 2008 - Radeon HD - openSUSE Mailing Lists

[Bug 15995] New: Screen garbles after close/open laptop lid with radeonhd
by bugzilla-daemon＠freedesktop.org 01 Nov '08

01 Nov '08

http://bugs.freedesktop.org/show_bug.cgi?id=15995 Summary: Screen garbles after close/open laptop lid with radeonhd Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: steven(a)silverorange.com QAContact: xorg-team(a)lists.x.org I have my Thinkpad T60 (ATI X1400) setup to not go to sleep when closing the lid. It does turn off the screen when it closes (as it should). However, with radeonhd, when I re-open the laptop lid, the screen is garbled (hard to describe - mostly black, a few weird colors/characters - looks like a broken command line). I'm running a stock install of Fedora 9. Let me know if any more information would be helpful. -- 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 10

Re: [radeonhd] DRI support hit master
by Matthias Hopf 14 Oct '08

14 Oct '08

On May 29, 08 11:47:26 -0700, Adam Williamson wrote: > > We want to be able to compile the driver against older Xservers for some > > of our distributions. Eventually, we'll get rid of it as well. > > OK, got it. Will poke you again if it breaks in future :) Yes, please do that! These issues typically linger around too long, so that nobody knows anymore what triggered them ;-) Matthias -- Matthias Hopf <mhopf(a)suse.de> __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat(a)mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

2 6

[Bug 13415] New: machine locks after suspend/resume
by bugzilla-daemon＠freedesktop.org 19 Sep '08

19 Sep '08

http://bugs.freedesktop.org/show_bug.cgi?id=13415 Summary: machine locks after suspend/resume Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: mads(a)kiilerich.com QAContact: xorg-team(a)lists.x.org When I try to resume with radeonhd the machine locks up. The machine is so dead that capslock toggling doesn't work - but the screen gets some kind of signal; it wakes up but shows no signal. Is this a known problem? Is it related to the graphics driver at all? Is it a kernel bug? Is a hal quirk needed? Running Fedora 8 with 2.6.23.1-49.fc8 on Dell Optiplex 745 with RV516 X1300 pro and homebuilt driver from 20071123git f5ffe41a6c1ffa9418782b7059b075da06e7c496 Suspend/resume works fine with the motherboards intel graphic card. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. _______________________________________________ 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 16

[Bug 16232] New: Screen scrambles when laptop undocked or redocked
by bugzilla-daemon＠freedesktop.org 17 Sep '08

17 Sep '08

http://bugs.freedesktop.org/show_bug.cgi?id=16232 Summary: Screen scrambles when laptop undocked or redocked Product: xorg Version: unspecified Platform: Other URL: https://bugzilla.redhat.com/show_bug.cgi?id=450018 OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: hun(a)n-dimensional.de QAContact: xorg-team(a)lists.x.org This has been reported as https://bugzilla.redhat.com/show_bug.cgi?id=450018 On docking and undocking the laptop, the top third of the screen is scrambled. http://www.youtube.com/v/84rxcRSYrUY xorg-x11-drv-radeonhd-1.2.1-1.1.20080429git.fc9.i386 corresponds to xf86-video-radeonhd commit 45fdec79 plus cherry-picked 71ec0c90. The reporter has an "ATI Technologies Inc M64-S [Mobility Radeon X2300] and the laptop is an HP 6910p". On IRC, "marcheu" suspected an SMI "playing with the card", and "yangman" remembers some docking weirdness like hard freezes with his M52 (mobility X1300) on a Thinkpad T60. I cannot remember any docking issues with my Thinkpad T60 with Mobility X1400. The Fedora bug also has an Xorg.0.log attached. -- 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 4

[Bug 16516] New: When cursor move between heads on dual-head configuration picture "shakes"
by bugzilla-daemon＠freedesktop.org 02 Sep '08

02 Sep '08

http://bugs.freedesktop.org/show_bug.cgi?id=16516 Summary: When cursor move between heads on dual-head configuration picture "shakes" Product: xorg Version: 7.3 Platform: x86 (IA32) OS/Version: FreeBSD Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: vova(a)fbsd.ru QAContact: xorg-team(a)lists.x.org Created an attachment (id=17372) --> (http://bugs.freedesktop.org/attachment.cgi?id=17372) xorg.conf Setup - I have notebook LCD panel (primary monitor, 1440x1050) and external LCD monitor with panel 1600x1200 connected via DVI to dock-station. "shakes" - like some reset occurs in hardware There was no such glitch when second head was VGA monitor with lesser resolution (probably bug is related to bug #16513). Sometimes effect is lesser, sometimes harder. Sometimes just scrolling window entirely on primary head leads to such effect xrandr --off and then configure again for second head helps a bit. $ xrandr Screen 0: minimum 320 x 200, current 3000 x 1200, maximum 3040 x 1200 PANEL connected 1400x1050+0+0 305mm x 228mm 1400x1050 60.0*+ 74.8 60.0 1920x1200Scaled 60.4 1920x1080Scaled 60.5 1600x1200 85.0 75.0 70.0 65.0 60.0 1600x1200Scaled 60.4 1680x1050Scaled 60.3 1600x1024 60.0 1400x1050Scaled 60.3 1440x960Scaled 60.4 1280x1024 85.0 75.0 60.0 1280x1024Scaled 60.5 1280x960 85.0 60.0 1280x960Scaled 60.4 1280x854Scaled 60.4 1152x864 75.0 1280x720Scaled 60.4 1152x768 54.8 1152x768Scaled 60.3 1024x768 85.0 75.0 70.1 60.0 43.5 1024x768Scaled 60.4 832x624 74.6 800x600 85.1 72.2 75.0 60.3 56.2 800x600Scaled 60.3 768x576Scaled 60.4 854x480Scaled 59.8 720x480Scaled 59.8 640x480 85.0 72.8 75.0 59.9 640x480Scaled 60.1 720x400 85.0 640x400 85.1 640x350 85.1 320x240Scaled 57.6 320x200Scaled 55.7 VGA_1 disconnected DVI-D_1 connected 1600x1200+1400+0 408mm x 306mm 1600x1200 60.0*+ 59.9 1280x1024 75.0 59.9 1280x960 59.9 1152x864 75.0 74.9 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 75.0 72.8 66.7 60.0 720x400 70.1 -- 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 3

[Bug 16400] New: Gamma of white+grey is wrong (all seems like white)
by bugzilla-daemon＠freedesktop.org 29 Aug '08

29 Aug '08

http://bugs.freedesktop.org/show_bug.cgi?id=16400 Summary: Gamma of white+grey is wrong (all seems like white) Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: patrick.matthaei(a)web.de QAContact: xorg-team(a)lists.x.org Hello, as explained in IRC I've got problems with my Sapphire X1650Pro card. I'm using the latest git master and this problem doesn't occur on my laptop (X1250). The "color" grey seems like white so on I can't figure out many things correctly on my TFT. I attached a screenshot (if I take a screenshot of it there it's all normal) and marked some points with comments. I hope it will be enough if I quote the irc log here: <the-me> libv, hm no, I try to explain it :) on my desktop (it doesnt occur on my notebook) with my x1650 pro from sapphire the white has a very big brightness, also grey, too. now for example at kde I can't see any differences between white and grey "colors". I would like to show you it but if I took a screenshot it seems normal again. with my tft setup everything is fine and I also tried to tune it so that it looks normal again :( <the-me> both setups are based on debian sid with radeonhd git master <libv> the-me: have you played with xgamma? <the-me> hmm never played with. at the moment every value eq 1.000 <the-me> ah: if I start it with fglrx for example everything is fine again (or vesa) - it just occurs with radeonhd <libv> the-me: can you play with xgamma, and if this doesn't fully solve the issue file a bug? <the-me> libv, hm okay also not very usefull (like tuning my tft itself). I created a screenshot on the box and added some comments on it - would be nice if you would have a look first on it (not so easy to explain it in english *grml*) ;) <the-me> libv, ok here is the screenshot: (***SEE ATTACHMENT***) to the comment numbers: #1: the font is just an little little bit grey, nearly unreadable. #2: the color of the lower and upper arrow are nearly the same (white). #3: unable to see this grey breaking line #4: same like #2 and #3 but there I can see an little little difference between both :) <libv> the-me: is this on tmds or on the dac? <libv> the-me: is this a digitally connected monitor, or is it connected to analog? <the-me> ah. this graphic board just has two digitally connector. there's such a digital -> analog plug after that and then the tft is plugged about a vga cable to it <libv> right, so a dac <libv> find out which dac from the log, DACA or DACB <the-me> libv, http://nopaste.linux-dev.org/?615 Okay right now here are the results: Is it DACA or DACB?: ==================== # grep -i dac /var/log/Xorg.0.log (II) RADEONHD(0): Connector[0] {RHD_CONNECTOR_DVI, "DVI-I CRT1 DFP3", RHD_DDC_0, RHD_HPD_1, { RHD_OUTPUT_DACA, RHD_OUTPUT_LVTMA } } (II) RADEONHD(0): Connector[1] {RHD_CONNECTOR_TV, "SVIDEO TV1", RHD_DDC_NONE, RHD_HPD_NONE, { RHD_OUTPUT_DACB, RHD_OUTPUT_NONE } } (II) RADEONHD(0): Connector[2] {RHD_CONNECTOR_DVI, "DVI-I DFP1 CRT2", RHD_DDC_1, RHD_HPD_0, { RHD_OUTPUT_TMDSA, RHD_OUTPUT_DACB } } (--) RADEONHD(0): Attaching Output DAC A to Connector DVI-I 1 (--) RADEONHD(0): Attaching Output DAC B to Connector TV SVIDEO (--) RADEONHD(0): Attaching Output DAC B to Connector DVI-I 2 (II) RADEONHD(0): RandR: Adding RRoutput DVI-I_1/analog for Output DAC A (II) RADEONHD(0): RandR: Adding RRoutput TV_SVIDEO for Output DAC B (II) RADEONHD(0): RandR: Adding RRoutput DVI-I_2/analog for Output DAC B (II) RADEONHD(0): DAC B: Sensed Output: VGA (II) Loading sub module "ramdac" (II) LoadModule: "ramdac"(II) Module "ramdac" already built-in (WW) RADEONHD(0): RandR: While switching off TV_SVIDEO: output DAC B is also used by DVI-I_2/analog - ignoring (WW) RADEONHD(0): RandR: While switching off TV_SVIDEO: output DAC B is also used by DVI-I_2/analog - ignoring (WW) RADEONHD(0): RandR: While switching off TV_SVIDEO: output DAC B is also used by DVI-I_2/analog - ignoring (WW) RADEONHD(0): RandR: While switching off TV_SVIDEO: output DAC B is also used by DVI-I_2/analog - ignoring rhd_dump output with radeonhd: ============================== exez:/usr/src/xf86-video-radeonhd/utils/conntest# ./rhd_dump -r 7A00,7A70 05:00.0 rhd_dump: v1.2.1, git branch master, commit 1f65f354 0x7A00: 0x00000001 0x7A04: 0x00000000 0x7A08: 0x00000000 0x7A0C: 0x00000000 0x7A10: 0x3FFFFFFF 0x7A14: 0x0000003F 0x7A18: 0x3FFFFFFF 0x7A1C: 0x0000003F 0x7A20: 0x00000000 0x7A24: 0x00000000 0x7A28: 0x00070000 0x7A2C: 0x0000000B 0x7A30: 0x00000000 0x7A34: 0x02020200 0x7A38: 0x00000000 0x7A3C: 0x00000000 0x7A40: 0x00000000 0x7A44: 0x00000000 0x7A48: 0x00000000 0x7A4C: 0x00000000 0x7A50: 0x00000000 0x7A54: 0x00050602 0x7A58: 0x00000000 0x7A5C: 0x00000000 0x7A60: 0x00000000 0x7A64: 0x00000000 0x7A68: 0x00000002 0x7A6C: 0x00000000 0x7A70: 0x00000000 rhd_dump output with vesa: ========================== exez:/usr/src/xf86-video-radeonhd/utils/conntest# ./rhd_dump -r 7A00,7A70 05:00.0 rhd_dump: v1.2.1, git branch master, commit 1f65f354 0x7A00: 0x00000001 0x7A04: 0x00000000 0x7A08: 0x00000000 0x7A0C: 0x00000000 0x7A10: 0x3FFFFFFF 0x7A14: 0x0000003F 0x7A18: 0x3FFFFFFF 0x7A1C: 0x0000003F 0x7A20: 0x00000000 0x7A24: 0x00000000 0x7A28: 0x00070000 0x7A2C: 0x0000000B 0x7A30: 0x00000000 0x7A34: 0x02020200 0x7A38: 0x00000000 0x7A3C: 0x00000000 0x7A40: 0x00000000 0x7A44: 0x00000000 0x7A48: 0x00000000 0x7A4C: 0x00000000 0x7A50: 0x00000000 0x7A54: 0x00051002 0x7A58: 0x00000000 0x7A5C: 0x00000000 0x7A60: 0x00000000 0x7A64: 0x00000000 0x7A68: 0x00000002 0x7A6C: 0x00000000 0x7A70: 0x00000000 How you can see, the only option which is different from vesa is 0x7A54 => 0x00050602 (radeonhd) vs. 0x00051002 (vesa). :) -- 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 10

[Bug 15989] New: Using RanrR radeonhd driver passes wrong resolution information to applications
by bugzilla-daemon＠freedesktop.org 13 Aug '08

13 Aug '08

http://bugs.freedesktop.org/show_bug.cgi?id=15989 Summary: Using RanrR radeonhd driver passes wrong resolution information to applications Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: marcelo.magallon(a)gmail.com QAContact: xorg-team(a)lists.x.org Created an attachment (id=16600) --> (http://bugs.freedesktop.org/attachment.cgi?id=16600) Xorg.log file without a configuration file If I configure the radeon driver to use RandR, some applications like GDM and the GNOME panel don't occupy the full screen but a fraction of it. Looking at the log file I see: (II) RADEONHD(0): Output VGA_1 disconnected (II) RADEONHD(0): Output TV_SVIDEO disconnected (II) RADEONHD(0): Output DVI-D_1 connected (II) RADEONHD(0): Output DVI-D_2 connected (II) RADEONHD(0): Output DVI-D_1 using initial mode 1280x800 (II) RADEONHD(0): Output DVI-D_2 using initial mode 1680x1050 It's a RS690 as the log says. It's integrated in the motherboard. Physically the motherboard has two display connectors, one VGA, one DVI. The monitor is connected to the DVI output. The monitor resolution, as seen in the log file is 1680x1050. Problem: GDM behaves as if the display resolution was set to 1280x800. Furthermore, the output of xdpyinfo says the display resolution is in fact 1680x1050, but xrandr reports only up to 1280x800. Initially the GNOME panels are only 1280 pixels wide and the lower one is located at the "edge" of the 800 pixel tall display, but I can drag it to the lower edge of the monitor and it will expand to occupy the full 1680 pixels. If I disable RandR using the NoRandR option, everything behaves ok. Is this a problem in the radeonhd driver or a problem in GNOME? The problem is easy to reproduce for me, I can provide more information on request. -- 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 19

[Bug 14487] New: no DVI on Gigabyte GA-MA69GM-S2H
by bugzilla-daemon＠freedesktop.org 03 Aug '08

03 Aug '08

http://bugs.freedesktop.org/show_bug.cgi?id=14487 Summary: no DVI on Gigabyte GA-MA69GM-S2H Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: bunk(a)stusta.de QAContact: xorg-team(a)lists.x.org Created an attachment (id=14296) --> (http://bugs.freedesktop.org/attachment.cgi?id=14296) Xorg.0.log Analog output works fine with the onboard 690G, but DVI output isn't working. When starting X with the monitor connected through the DVI cable I'm _sometimes_ seeing something like a quarter of my X background picture fullscreen for half a second, but there's never any usable picture and the monitor tells me that it doesn't get any input. Tested with both the 1.1.0 package from Debian unstable and current -git. -- 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 27

[Bug 15612] New: [rhd 1.2] undeterminstic system freezes on RV530 [ Radeon X1600]
by bugzilla-daemon＠freedesktop.org 02 Aug '08

02 Aug '08

http://bugs.freedesktop.org/show_bug.cgi?id=15612 Summary: [rhd 1.2] undeterminstic system freezes on RV530 [Radeon X1600] Product: xorg Version: git Platform: Other URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476309 OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: brice.goglin(a)ens-lyon.org QAContact: xorg-team(a)lists.x.org Roland Lezuo reported on the Debian BTS that radeonhd 1.2.0 (and latest upstream git) causes random freezes on his RV530. He says: "I could reliable trigger the bug by activating the screensaver. The hack running is a python based gnome-screensaver plugin written by me. The freeze occured after the screen faded out, at or shortly after the the first few seconds of the hack running." The config and log is available at http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;bug=476309 Driver 1.1.0 didn't have any problem. He bisected and is rather confident that the first bad commit is: commit af0c64d897f7f2288419b6e43468850e1037bb59 Author: Luc Verhaegen <libv(a)skynet.be> Date: Mon Jan 28 13:09:55 2008 +0100 R5xx accel: Add XAA support. MMIO path only, no CP support yet. -- 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 13

[Bug 15105] New: Unable to get modes from device connected via HDMI
by bugzilla-daemon＠freedesktop.org 31 Jul '08

31 Jul '08

http://bugs.freedesktop.org/show_bug.cgi?id=15105 Summary: Unable to get modes from device connected via HDMI Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: patrick-voigt(a)web.de QAContact: xorg-team(a)lists.x.org Created an attachment (id=15250) --> (http://bugs.freedesktop.org/attachment.cgi?id=15250) Xorg.log The driver is unable to get the modes from the projector (Panasonic PT-AX200E) connected to the HDMI port.The projector was the only device connected to the graphics card. I already posted this on the mailing list, but it might have been overlooked. Patrick -- 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 46