December 2007 - Radeon HD - openSUSE Mailing Lists

Re: [radeonhd] latest radeonhd crashes Xorg - Asus A8Jp, Mobility Radeon X1700
by Matthias Hopf 15 Jan '08

15 Jan '08

On Nov 27, 07 00:55:35 +0200, Kirill Belokurov wrote: > On Monday 26 November 2007, Matthias Hopf wrote: > > > > > (btw, is it OK that size is told to be "0mm x 0mm" ? the xdpyinfo > > > > > e.g. reports "380x238 millimeters") > > > > > > Got it :) Let me know if you need any help with reproducing/debugging > > > this. > > > > Fixed. Side effect of a bigger bug. > > Well, sort-of. Another user is still having issues. > > So please re-test current git master :) > > Still doesn't work for me :( Here is output from xrandr (size is still 0mm x > 0mm): You might want to try latest git - I just pushed a change upstream that could (!) fix this. However, as I don't have a panel with a fixed mode provided by AtomBIOS here, so I cannot test that. Also, it could be that AtomBIOS does not provide an EDID block at all, in that case the new code won't make a difference. CU 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 5

[Bug 13854] New: freezes when fast user switching in gnome
by bugzilla-daemon＠freedesktop.org 11 Jan '08

11 Jan '08

http://bugs.freedesktop.org/show_bug.cgi?id=13854 Summary: freezes when fast user switching in gnome Product: xorg Version: 7.3 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: prusnik(a)gmail.com QAContact: xorg-team(a)lists.x.org On a random number of switches between users there would be appear a blank screen and a switch to one of the terminals and restarting X would do. However, continuing switching between users ends in a terminal system freeze with blank screen and a cursor blinking high in the left corner and the only cure there is is a HW reset. There is nothing in the logs on the subject to look for a cause. Similar behaviour happened when I was using the fglrx driver (regardless of version). I spotted a similar problem in Ubuntu's launchpad: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+… In my case I now use radeonhd driver, v1.1.0, git updated on 28.12.2007 and the problem persists. The fglrx module is not loaded in the system and the xorg files and configurations are attached to a Bug #13853. -- 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 7

Re: [radeonhd] 0x7187:0x174b:0x3000 ?Sapphire OEM? X1550 512MB
by Luc Verhaegen 09 Jan '08

09 Jan '08

On Thu, Dec 13, 2007 at 09:24:24PM +0100, Lo?c Greni? wrote: > > 1) I don't known its id. It's an OEM card, I've a "Sapphire Inside" label > on my case and one of the stickers on the back reads > "X1550 512MB DDR2 PCI-E VGA/TVO/DVI-I". It looks nearly exactly like > the Sapphire X1550 512MB that is on Newegg, except that it has a > RoHS mention on one sticker (I'm in Europe) and the SKU# is 11093-19 > (I cannot decipher it on Newegg's photo, but it does not seem to be the > same). Don't worry too much about this atm :) > 2) The BIOS maps only 256MB of ram; it is related to: > 3) The card and driver do not seem to know whether the card has 256 or > 512MB of RAM (it prints 0xE00000000/28 as main memory, but the driver > claims 512MB somewhere else). The bios message starts with "512mb". > > This is no big deal right now... In the future it'd be nice if it > were possible > to remap the 512MB somewhere else (above the 4GB mark, because I've > 4GB of DRAM). Both are the exact same issue. The memory available on the card does not equal the memory we can access from the cpu directly. Whatever is in the non-directly-addressable part can be used by the card itself, but we currently are not doing anything that could make use of that memory anyway. > 4) There is a secondary chip with id 0x71a7. It could be another X1550 > without output registers (lspci -x below). This exists only to fool some windows version. Ignore it. > > 5) Both outputs are changed together by xrandr. I've compiled a fairly > recent version of the X server and xrandr (git of beginning of September) > and, when I act on one output with xrandr, both change together. > For instance, if I type > > xrandr --output VGA_1 --right-of DVI-I_1/digital > > both output go to (1024,0). I always get same resolution and same > position for both outputs. The outputs are not in parallel because > the EDID are different for both screens. > > That's what I've found after some tries. With a single screen it works ok. > With two it's a problem (and that's unfortunate because I'd like to make > a two-seat computer). I have no idea whether this is an RandR FAQ, a known RandR issue, or an issue that still has to be dug out. I hope that Matthias can shed some light on this one. Thanks, Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

3 10

Problem setting up multiple monitors with radeonhd and xrandr
by kzot＠gmx.net 08 Jan '08

08 Jan '08

Hello, I have a problem setting up multiple monitors with radeonhd and xrandr. I tried to follow the how-to in http://wiki.x.org/wiki/radeonhd#head-b4abfb1970c58a8fef1a1d6d368422d5f1205b…, but it does not work for me. I am running the following setup: T60 Thinkpad Notebook with an ATI X1400 and two external monitors via docking station (DVI and VGA), i.e. I have 3 monitors. radeonhd/xrandr detects them all/correct, configure them as clones and they run (beside some small graphic glitches on monitor PANEL) well. --------------------- [root@thyone ~]# xrandr -q Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 2560 x 1400 VGA_1 connected 1280x1024+0+0 376mm x 301mm 1280x1024 60.0*+ 75.9 75.0 71.9 69.8 59.9 [...] PANEL connected 1400x1050+0+0 287mm x 215mm 1400x1050 60.0*+ DVI-D_1 connected 1280x1024+0+0 376mm x 301mm 1280x1024 60.0*+ 75.9 75.0 71.9 69.8 59.9 [...] ---------------------- As the verbose mode shows the DVI-D_1 and VGA_1 output are sharing one CRTC. ---------------------- [root@thyone ~]# xrandr -q --verbose Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 2560 x 1400 VGA_1 connected 1280x1024+0+0 (0x46) normal (normal) 376mm x 301mm [...] Clones: PANEL DVI-D_1 CRTC: 0 CRTCs: 0 1 [...] PANEL connected 1400x1050+0+0 (0x5a) normal (normal) 287mm x 215mm [...] Clones: VGA_1 DVI-D_1 CRTC: 1 CRTCs: 0 1 [...] DVI-D_1 connected 1280x1024+0+0 (0x46) normal (normal) 376mm x 301mm [...] Clones: VGA_1 PANEL CRTC: 0 CRTCs: 0 1 [...] ---------------------- What I want is to achieve is one big screen (2560x1024) over DVI-D_1 and VGA_1. PANEL is not important. Running ---------------------- [root@thyone ~]# xrandr --output VGA_1 --right-of DVI-D_1 ---------------------- results in one big screen (2560x1050) over PANEL and (DVI-D_1 | VGA_1), i.e. DVI-D_1 and VGA_1 show the same. ---------------------- [root@thyone ~]# xrandr -q Screen 0: minimum 320 x 200, current 2560 x 1050, maximum 2560 x 1400 VGA_1 connected 1280x1024+1280+0 376mm x 301mm 1280x1024 60.0*+ 75.9 75.0 71.9 69.8 59.9 [...] PANEL connected 1400x1050+0+0 287mm x 215mm 1400x1050 60.0*+ DVI-D_1 connected 1280x1024+1280+0 376mm x 301mm 1280x1024 60.0*+ 75.9 75.0 71.9 69.8 59.9 [...] ---------------------- Trying to circumvent this by switching off PANEL and giving DVI-D_1 and VGA_1 differenct CRTCs does not work either. ---------------------- [root@thyone ~]# xrandr --output PANEL --off && xrandr --output DVI-D_1 --crtc 1 && xrandr --output VGA_1 --right-of DVI-D_1 ---------------------- This results in both PANEL and DVI-D_1 being switched off. ---------------------- [root@thyone ~]# xrandr -q Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 2560 x 1400 VGA_1 connected 1280x1024+0+0 376mm x 301mm 1280x1024 60.0*+ 75.9 75.0 71.9 69.8 59.9 [...] PANEL connected 1400x1050 60.0 + DVI-D_1 connected 1280x1024 60.0 + 75.9 75.0 71.9 69.8 59.9 [...] [root@thyone ~]# xrandr -q --verbose Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 2560 x 1400 VGA_1 connected 1280x1024+0+0 (0x46) normal (normal) 376mm x 301mm [...] Clones: PANEL DVI-D_1 CRTC: 0 CRTCs: 0 1 [...] PANEL connected (normal) [...] Clones: VGA_1 DVI-D_1 CRTCs: 0 1 [...] DVI-D_1 connected (normal) [...] Clones: VGA_1 PANEL CRTCs: 0 1 [...] ---------------------- Am I missing something or is there a bug in radeonhd and/or xrandr? And if bug which component (for feeding bugzilla)? Version of involved components: x11-driver-video-radeonhd-1.0.1-0.20071214.1mdv2008.1 libxrandr2-1.2.2-1mdv2008.0 xrandr-1.2.2-1mdv2008.0 x11-server-xorg-1.4-17mdv2008.1 -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

2 1

xrandr resolution problems
by Thomas Wendt 08 Jan '08

08 Jan '08

Hi, I'm testing the radeonhd driver (version 1.1.0-1 from Debian) on my Radeon HD2600XT and except from starting with the wrong and not recognizing my preferred resolution everything seems to work well. The XServer starts with a 1280x800 resolution with 60 Hz. I expected something like that because my CRT monitor doesn't provide any EDID information and I commented the HorizSync and VertRefresh options in the xorg.conf. But why is it choosing a widescreen(?) resolution?! Wouldn't it be smarter to choose the 1024x768 or 800x600 resolution if no EDID information are provided and a analog monitor is connected? The xrandr -q output looks like this: Screen 0: minimum 320 x 200, current 1280 x 800, maximum 1280 x 1280 DVI-I_1/digital disconnected DVI-I_1/analog connected 1280x800+0+0 0mm x 0mm 1280x800 60.0* 1280x768 60.0 1024x768 60.0 800x600 60.3 640x480 59.9 TV_7PIN_DIN disconnected DVI-I_2/digital disconnected DVI-I_2/analog disconnected Anyway, the main problem is that after uncommenting the HorizSync and VertRefresh options and restarting the XServer nothing changed. The xrandr output is the same. Adding the following modeline and a preferred mode to the monitor section doesn't help either. Modeline "1280x1024_85.00" 159.36 1280 1376 1512 1744 1024 1025 1028 1075 -HSync +Vsync Option "PreferredMode" "1280x1024_85.00" The Xorg.0.log mentions something like this: (**) RADEONHD(0): Option "PreferredMode" "1280x1024_85.00" (WW) RADEONHD(0): Option "PreferredMode" is not used But I can get my preferred resolution with the following commands: thoemy@thoemy:~$ xrandr --newmode "1280x1024_85.00" 159.36 1280 1376 1512 1744 1024 1025 1028 1075 -HSync +Vsync thoemy@thoemy:~$ xrandr --addmode DVI-I_1/analog thoemy@thoemy:~$ xrandr --output DVI-I_1/analog --mode 1280x1024_85.00 thoemy@thoemy:~$ xrandr -q Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1280 x 1280 DVI-I_1/digital disconnected DVI-I_1/analog connected 1280x1024+0+0 0mm x 0mm 1280x800 60.0 1280x768 60.0 1024x768 60.0 800x600 60.3 640x480 59.9 1280x1024_85.00 85.0* TV_7PIN_DIN disconnected DVI-I_2/digital disconnected DVI-I_2/analog disconnected So am I doing something wrong or is it a bug in xrandr or the radeonhd driver? xrandr -v says: Server reports RandR version 1.2 Another thing is that xrandr reports a maximum resolution of 1280x1280 but I'm sure that I used 1600x1200 before. Attached is the xorg log and the xorg.conf used for testing. Thanks, Thomas

2 1

Re: [radeonhd] Unknown card detected using radeonhd driver
by Luc Verhaegen 07 Jan '08

07 Jan '08

On Thu, Nov 29, 2007 at 09:17:29PM -0500, James Slagle wrote: > > There is only 1 DVI connector and 1 VGA connector on the card. I > tried the driver from today, and X never finishes starting, it just > stays hung at a black screen. I've attached the Xorg log file. > > Thanks, > James Slagle Hrm, why would it be hanging. Since there is a 2 week gap now (my apologies for that), and there have been a decent number of fixes to the driver, can you try pulling a new git version? If our code really was looping over a broken connector table, then I do not think there was any change that could influence this, but we better start from a new baseline :) Thanks, Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

3 10

patch for new RS690 card id (Gigabyte MA69GM-S2H motherboard)
by tim hughes 07 Jan '08

07 Jan '08

Hello all, I've added a patch to recognise my (microATX) 690G motherboard; according to the xorg.log file, it looks like my mb uses the same atom bios as the -S3H mother board (the ATX version of my motherboard), so I don't know whether the code should be quite so specific about what it has identified; what do you think? Let me know if there's anything I can do to help. Tim Here's a snippet of the xorg.log after the patch: (--) RADEONHD(0): Detected an RS690 on a Gigabyte MA69GM-S2H (II) RADEONHD(0): Mapped IO at 0x2b4ff49ce000 (size 0x00010000) (II) RADEONHD(0): Getting BIOS copy from legacy VBIOS location (II) RADEONHD(0): ATOM BIOS Rom: SubsystemVendorID: 0x1002 SubsystemID: 0x791e IOBaseAddress: 0xee00 Filename: 69G_S3_4.bin BIOS Bootup Message: ATI Radeon Xpress for GBTMA69G-S3 and a diff: cb306d3f212df57be652d83ca04fda6376269a97 src/rhd_id.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/src/rhd_id.c b/src/rhd_id.c index 027fbb8..cd10016 100644 --- a/src/rhd_id.c +++ b/src/rhd_id.c @@ -553,6 +553,7 @@ rhdCards[] = /* 0x7297 : RV560 : RV560 */ /* 0x791E : RS690 : Radeon X1200 */ { 0x791E, 0x1043, 0x826D, "Asus M2A-VM", RHD_CARD_FLAG_NONE, ID_CONNECTORINFO_EMPTY }, + { 0x791E, 0x1458, 0xD001, "Gigabyte MA69GM-S2H", RHD_CARD_FLAG_NONE, ID_CONNECTORINFO_EMPTY }, /* 0x791F : RS690 : Radeon X1200 */ { 0x791F, 0x103C, 0x30C2, "HP/Compaq 6715b", RHD_CARD_FLAG_NONE, ID_CONNECTORINFO_EMPTY }, /* 0x793F : RS600 : Radeon Xpress 1200 */ -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

2 2

Small HD 2600 gamma question
by Marcel de Boer 06 Jan '08

06 Jan '08

Hi! I've been looking around a bit for a new video card, and the HD 2600 Pro (AGP) seems like a good choice, especially with the reported support from ATI for open-source drivers. I'm not (yet) interested in much acceleration, but I do want to use the card for photo editing, so before I make a final decision, I'd like to know if this card has support for independent gamma tables for each display of a dual-head setup (so I can use the tuned calibrations for both of my monitors.) E.g. what happens if you give the following two commands: xgamma -s 0 -gamma 2 xgamma -s 1 -gamma 0.5 Does the first screen become lighter and the second one darker or does something else happen? This list may not be the right place to ask this, but this information is almost impossible to find anywhere, so the driver developers are probably the only people who know. Thank you very much in advance! Gtnx Marcel de Boer -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

3 3

[Bug 13793] New: Latest git driver results in no screen display
by bugzilla-daemon＠freedesktop.org 02 Jan '08

02 Jan '08

http://bugs.freedesktop.org/show_bug.cgi?id=13793 Summary: Latest git driver results in no screen display Product: xorg Version: unspecified Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: ade(a)beth2.org QAContact: xorg-team(a)lists.x.org I tried to bump to 1.1.0 from cad8539ca12249a2c16b177e2364b77395a0dcab but this shows no screen at all. After doing a git-bisect it seems that e5f9b2d2f646ae93552eaccbd1193778fc772c8b causes the problem. Hardware is HP 8510w with FireGL 5600, 1920x1200 panel. Xorg logs to follow for before and after the commit -- 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 7

[Bug 13831] New: Misc. code cleanups suggested by Paulo de Andrade
by bugzilla-daemon＠freedesktop.org 31 Dec '07

31 Dec '07

http://bugs.freedesktop.org/show_bug.cgi?id=13831 Summary: Misc. code cleanups suggested by Paulo de Andrade Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: awilliamson(a)mandriva.com QAContact: xorg-team(a)lists.x.org CC: pcpa(a)mandriva.com.br Hi, guys. Trying to build radeonhd 1.1.0 on Mandriva I ran into a build error. This resulted in a rapid stream of suggestions for code cleanups by pcpa (our resident X code guy), about 25% of which I understand at all. :) I am therefore doing an unedited copy / paste dump on to you guys on the hope that you understand 'em better than I do! Thanks. <pcpa> AdamW: I was going to ask you what error messages, but just tried to compile it. Just patch it to not include "xf86_ansic.h". It is some conflicting defintions with glibc headers and xf86libcwrapper, but libcwrapper isn't supported anymore in upstream. <pcpa> AdamW: This basically will cause libc calls to not be wrapped. It has been broken for very long also, but just commenting it is enough to fix the problem. <pcpa> AdamW: you also need change calls to xf86snprintf to snprintf and xf86strdup to strdup (those were wrappers, and should not be called directly...) <pcpa> yes, in xorg git upstream libcwrapper has been removed almost one month ago. You can submit a bug report I think If any of this is unclear, please ask pcpa about it. I'll try and CC him on this bug. -- 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 10