November 2007 - Radeon HD - openSUSE Mailing Lists

Re: [radeonhd] The X1950 GT Card has not been recognized
by Luc Verhaegen 06 Dec '07

06 Dec '07

On Wed, Nov 07, 2007 at 11:40:31PM +0300, Vsevolod Novikov wrote: > Hi Hans, > > Yes, the module compiled from the master branch was more successive, > but not enough :/ > > The two applied logs are produced with AGP aperture size 256 > (badradeon-2) and 512 (badradeon-3) Mb. This doesn't change anything sadly. > The monitor connected to the card is "FLATRON 795FT Plus" (CRT > connected through the VGA connector). > > I would be happy if this information will help you. > > Regards, > Vsevolod Please attach your VGA connected monitor to any of the radeons outputs and run rhd_conntest, and provide the full feedback. 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

2 9

How to set DPI
by Karel Podvolecky 06 Dec '07

06 Dec '07

Hi, I was wondering if there is a way how to set DPI or Panel dimensions. I have 15" 1400x1050 display and 75 DPI is too small (fonts are to small). Fglrx says it has about 150 DPI. Karel -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

2 1

[Bug 13430] New: dual-head screens always have same position
by bugzilla-daemon＠freedesktop.org 01 Dec '07

01 Dec '07

http://bugs.freedesktop.org/show_bug.cgi?id=13430 Summary: dual-head screens always have same position Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: joachim.deguara(a)amd.com QAContact: xorg-team(a)lists.x.org Perhaps I am just doing something wrong but with xrandr both of my screen always have the same position either 0x0 or 1280x0. They are both DVI TFTs at 1280x1024 made by HP. I tried xrandr --auto and xrandr --output DVI-I_2/digital --left-of DVI-I_1/digital and finally just trying to set the position of one screen with xrandr --output DVI-I_2/digital --pos 0x0. As mentioned both screens always had the same position even when I explicitly set one of them to a different position then both would change. Here are the logs associated with it. -- 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 11

Re: Re: [radeonhd] 24bit depth and asus f3jr panel
by anonymous 30 Nov '07

30 Nov '07

Hi, in my xorg log it looks like: (II) RADEONHD(0): LVDS SEQ Dig onto DE: 30 (II) RADEONHD(0): LVDS SEQ DE to BL: 250 (II) RADEONHD(0): LVDS Off Delay: 500 (II) RADEONHD(0): LVDS Duallink: 0x0 (II) RADEONHD(0): LVDS 24Bit: 0x0 (II) RADEONHD(0): LVDS FPDI: 0x480 Symptoms are noisy pictures (like old GIF pictures with reduced colors) on LVDS only. On other displays I've not seen the symptoms so far. I CONFIRM. Fri, 30 Nov 2007 17:01:13 +0100, On André-Sebastian Liebe <andre@xxxxxxxxx> wrote: Hi there, this seems to be more a generic lvds problem if you ask me. I've got the same problem here with my x1600 mobile on LVDS. Sine tag 1.0.0 there are new infos in the xorg log: (II) RADEONHD(0): LVDS SEQ Dig onto DE: 30 (II) RADEONHD(0): LVDS SEQ DE to BL: 250 (II) RADEONHD(0): LVDS Off Delay: 500 (II) RADEONHD(0): LVDS Duallink: 0x1 (II) RADEONHD(0): LVDS 24Bit: 0x0 (II) RADEONHD(0): LVDS FPDI: 0x690 In the second line from the bottom it looks to me like the driver thinks it's not a 24Bit display (0x0) but with fglrx and avivo it works correct. Symptoms are noisy pictures (like old GIF pictures with reduced colors) on LVDS only. On other displays I've not seen the symptoms so far. On 11/30/07, anonymous <dconfimrone@xxxxxxx> wrote: Hello. I have asus f3jr laptop with radeon mobility X2300 ( M64 product withconfim Chipset Supported AMD Graphics Processor (0x718A) ) For 16bit in xorg.conf everything is ok. If I set 24bit depth in xorg.conf then is a lot of noise in the video output, on the laptop panel at least. I took a screenshot and the noise does not exist there; zooming in on areas of colour reveals the noise is a constant pattern in the background. This does not happen with the fglrx driver. Fglrx says that my laptop panel is: (II) fglrx(0): SAMSUNG (II) fglrx(0): LTN154XA-L01 (II) fglrx(0): EDID (in hex): (II) fglrx(0): 00ffffffffffff004ca3454900000000 (II) fglrx(0): 00110103802115780a87f594574f8c27 (II) fglrx(0): 27505400000001010101010101010101 (II) fglrx(0): 010101010101ee1a0080502010301030 (II) fglrx(0): 13004bcf100000190000000f00000000 (II) fglrx(0): 00000000002387026401000000fe0053 (II) fglrx(0): 414d53554e470a2020202020000000fe (II) fglrx(0): 004c544e31353458412d4c30310a0041 (II) fglrx(0): End of Display1 EDID data -------------------- [drone@tyrion ../xf86-video-radeonhd/utils/conntest]$ sudo ./rhd_conntest -d 1:0:0 [sudo] password for drone: rhd_conntest: v0.0.4, git branch master, commit 8b1b8bfb Checking connectors on 0x718A, 0x1043, 0x1449 (@01:00:00): Load Detection: RHD_OUTPUT_NONE HotPlug: RHD_HPD_NONE DDC: RHD_DDC_2 LVDS Info: 18bits, single link, LDI Panel found. Power Timing: 0xF9F, 0x000, 0x03, 0x19, 0x1F4 Macro: 0x0B520407, Clock Pattern: 0x0063 [drone@tyrion ../xf86-video-radeonhd/utils/conntest]$ Greet MB

1 0

[Bug 13459] New: radeonhd driver with non-ATI PCI vendor ID
by bugzilla-daemon＠freedesktop.org 30 Nov '07

30 Nov '07

http://bugs.freedesktop.org/show_bug.cgi?id=13459 Summary: radeonhd driver with non-ATI PCI vendor ID Product: xorg Version: unspecified Platform: All OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: amwsoft(a)gmail.com QAContact: xorg-team(a)lists.x.org On my Samsung R24plusF000 laptop ATI Mobility Radeon X2300 has non-ATI PCI vendor ID. As a result X does not start with radeonhd driver. I see "No device found" in Xorg.log. Video card presented in the system as: Vendor ID: 0x0001 Device ID: 0x7188 Subsystem vendor ID: 0x144D Subsystem device ID: 0xC515 Patch below resolves this problem for me, but it is ugly for PCI_VENDOR_ID_ATI replacement. After recompiling with this patch applyed my display starts in 1280x800 resolution which is native for my panel. diff -Naur old/src/rhd_driver.c new/src/rhd_driver.c --- old/src/rhd_driver.c 2007-11-24 23:32:43.000000000 +0200 +++ new/src/rhd_driver.c 2007-11-29 22:02:14.000000000 +0200 @@ -361,7 +361,7 @@ /* PCI BUS */ if (xf86GetPciVideoInfo() ) { - numUsed = xf86MatchPciInstances(RHD_NAME, PCI_VENDOR_ATI, + numUsed = xf86MatchPciInstances(RHD_NAME, 0x0001, RHDChipsets, RHDPCIchipsets, devSections,numDevSections, drv, &usedChips); diff -Naur old/src/rhd_id.c new/src/rhd_id.c --- old/src/rhd_id.c 2007-11-24 23:32:43.000000000 +0200 +++ new/src/rhd_id.c 2007-11-29 22:01:03.000000000 +0200 @@ -460,6 +460,7 @@ /* 0x7186 : M64 : Mobility Radeon X1450 */ /* 0x7187 : RV516 : Radeon X1300/X1550 */ /* 0x7188 : M64 : Mobility Radeon X2300 */ + { 0x7188, 0xC515, 0x144D, "Samsung R25plusF000 ATI Radeon X2300", RHD_CARD_FLAG_NONE, ID_CONNECTORINFO_EMPTY }, /* 0x718A : M64 : Mobility Radeon X2300 */ /* 0x718B : M62 : Mobility Radeon X1350 */ /* 0x718C : M62 : Mobility Radeon X1350 */ -- 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

4 4

[Bug 12907] radeonhd: X crash
by bugzilla-daemon＠freedesktop.org 30 Nov '07

30 Nov '07

http://bugs.freedesktop.org/show_bug.cgi?id=12907 ------- Comment #33 from roman(a)khimov.ru 2007-11-30 09:58 PST ------- > core file if you need that (285 Mb :)). Or just one meg compressed. -- 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 0

[Bug 12907] radeonhd: X crash
by bugzilla-daemon＠freedesktop.org 30 Nov '07

30 Nov '07

http://bugs.freedesktop.org/show_bug.cgi?id=12907 ------- Comment #32 from roman(a)khimov.ru 2007-11-30 09:56 PST ------- BTW, I have core file if you need that (285 Mb :)). -- 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 0

[Bug 12907] radeonhd: X crash
by bugzilla-daemon＠freedesktop.org 30 Nov '07

30 Nov '07

http://bugs.freedesktop.org/show_bug.cgi?id=12907 roman(a)khimov.ru changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #12761|0 |1 is obsolete| | ------- Comment #31 from roman(a)khimov.ru 2007-11-30 09:55 PST ------- Created an attachment (id=12879) --> (http://bugs.freedesktop.org/attachment.cgi?id=12879&action=view) gdb log for rhd_cursor 2 This is the log for cursor crash, reproduced easily again as I've said above. Regarding SWCursor - writing this from Konqueror under X with radeonhd driver and SWCursor enabled. So far so good. Yeah, 1920x1200, missed that with 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, 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 0

[Bug 12907] radeonhd: X crash
by bugzilla-daemon＠freedesktop.org 30 Nov '07

30 Nov '07

http://bugs.freedesktop.org/show_bug.cgi?id=12907 ------- Comment #30 from roman(a)khimov.ru 2007-11-30 09:32 PST ------- > I guess you know that you can still use our driver (in between tests ;) > with the Option "SWcursor"? Hmm. Not thought of that. Thanks, I'll try. Maybe I'll be able to reproduce the crash that I've reported first. > In the stacktrace creator you have to patch a line according to #19 to > get the console lit up again. OK. -- 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 0

[Bug 12907] radeonhd: X crash
by bugzilla-daemon＠freedesktop.org 30 Nov '07

30 Nov '07

http://bugs.freedesktop.org/show_bug.cgi?id=12907 ------- Comment #29 from mhopf(a)suse.de 2007-11-30 09:12 PST ------- (In reply to comment #28) > > Also, I just found this in your xorg.conf: > Nope, you have found it in B�rre's xorg.conf. :) Mine doesn't have Xinerama > enabled. Eek. :) Sorry. > > I also updated my test git repro, could you please git-pull and run the Xserver > > afterwards with the stacktrace creator (comment #14 and comment #19)? > I'll try. Although last time I tried the system freezed hard and I couldn't > switch to console to see what's up. :) I guess you know that you can still use our driver (in between tests ;) with the Option "SWcursor"? In the stacktrace creator you have to patch a line according to #19 to get the console lit up again. -- 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

1 0