August 2009 - Radeon HD - openSUSE Mailing Lists

0x9614:0x1849:0x9614: ASrock AOD790GX/128M Radeon HD3300
by Christian Lange 25 Aug '09

25 Aug '09

Hello, I want to use the radeonhd driver 1.25 for my onboard HD3300. I own a display with pivot function an want to rotate it using randrrotation in xorg.conf Section "ServerFlags" Option "AutoAddDevices" "false" Option "RandR" "on" EndSection Section "Device" Identifier "HD3300" Driver "radeonhd" # VideoRam 262144 Option "RandRRotation" "on" Option "AccelMethod" "exa" # Option "AddARGBGLXVisuals" "true" # Option "RenderAccel" "on" Option "UnverifiedFeatures" "on" Option "RandRRotation" "on" Option "Rotate" "left" # Option "HWCursor" "on" Option "Monitor-DVI-D_1" "L220x" EndSection But te rotation does nor work in the log file I found this: (II) Setting vga for screen 0. (**) RADEONHD(0): Depth 24, (--) framebuffer bpp 32 (**) RADEONHD(0): Option "AccelMethod" "exa" (**) RADEONHD(0): Option "DRI" "on" (**) RADEONHD(0): Option "UnverifiedFeatures" "on" (**) RADEONHD(0): Selected EXA 2D acceleration. (II) RADEONHD(0): Unknown card detected: 0x9614:0x1849:0x9614. 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: 0x9614:0x1849:0x9614: <name of board> and *please* describe the problems you are seeing in your message. (--) RADEONHD(0): Detected an RS780 on an unidentified card (II) RADEONHD(0): Mapped IO @ 0xfe9f0000 to 0x7fe7e6fe7000 (size 0x00010000) (II) RADEONHD(0): Getting BIOS copy from legacy VBIOS location (II) RADEONHD(0): ATOM BIOS Rom: SubsystemVendorID: 0x1002 SubsystemID: 0x1002 IOBaseAddress: 0xc000 Filename: ODE790GX_D2. BIOS Bootup Message: 113-B27722-X28 RS780D DDR2 200e/500m regards Christian -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

Re: [radeonhd] HPD Complaing
by Egbert Eich 25 Aug '09

25 Aug '09

Ed Martin writes: > Hi, > I have a Diamond radeonhd 3870 > (http://www.newegg.com/Product/Product.aspx?Item=N82E16814103050) and i > can't use it without the 'Option "HPD" "off"', if i comment it out xorg > reports no screens found. I atached the lspci info for the card, i don't > know if you need anything else. Could you please run rhd_conntest for the situation where you have a. no display connected b. a display connected to one connector at a time. Please also send us the logfile (perferrably generated with -logverbose 7). Cheers, Egbert. -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

Re: [radeonhd] Radeon HD 4350 and AtomBIOS initialization order
by Egbert Eich 25 Aug '09

25 Aug '09

Hans de Ruiter writes: > Hi, > I've been testing a Radeon HD 4350 card with a driver that I'm writing > that is similar to yours, and I go a black screen initially. After days > of searching for the problem, I finally found out that calling ASICInit > while the VGA output is still running results in the black screen; I > think that it hangs the memory controller, or something similar. > > In order to save you lots of frustration, the following code solved the > problem: > > rhdVGADisable(rhdDriver); > rhdAllIdle(rhdDriver); > > /* run AsicInit */ > if (!rhdAtomASICInit(rhdDriver->atomBIOSHandle)) > { > dprintf(0, "%s: AsicInit failed. Won't be able to obtain VRAM " > "FB scratch space\n",__func__); > } > > I recommend that you remove the rhdAtomASICInit() call from the AtomBIOS > initialization function, and add the code above where appropriate (the > xf86-video-ati driver puts it in EnterVT). > Hans, thanks for this hint! I expect under normal circumstances ASICInit() doesn't run. Only if a card is unPOSTed (ie. when the BIOS image has not been copied to the VGA location) it is called. I assume you are looking into a case where you have such a situation. I will take a look at this (it requires slightly more code as we should not run it unconditionally. Thanks! Cheers, Egbert. -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

Re: [radeonhd] 0x9591:0x1179:0xFF01: Mobility Radeon HD 3650
by Egbert Eich 25 Aug '09

25 Aug '09

Mehmet Giritli writes: > Hi, > > The problem I am having with the above mentioned card is with a toshiba > laptop, model Satellite A350 22Z. > > When X is started using the radeonhd driver, it gets terminated > immediately. It never manages to start up. The log file is attached for > the error messages. > > (II) RADEONHD(0): Mapped IO @ 0xbfef0000 to 0x7f2718702000 (size 0x00010000) > (II) RADEONHD(0): Mapped FB @ 0xc0000000 to 0x7f26f463e000 (size 0x20000000) > (WW) RADEONHD(0): rhdVGASaveFB: Unable to access the VGA framebuffer (0xFFFFFFFF) > (EE) RADEONHD(0): D1CRTCDisable: Failed to Unsync CRTC 1 > (EE) RADEONHD(0): rhdAllIdle: unable to stop CRTC: cannot idle MC > > Fatal server error: > AddScreen/ScreenInit failed for driver 0 > The MC appears not to be idle. Do you have the fglrx kernel module loaded? Cheers, Egbert. -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

SOLVED - 2e2e4d118e Kills RS690M (x1200) Cards [ was 0x791F:0x1179:0xFF68: ]
by David C. Rankin 25 Aug '09

25 Aug '09

Matthias, Finally! We know which patch killed the radeonhd driver for the RS690M cards. The last good/bad drivers are: Last Good Commit: 7/21/09 de3f80bc6ec2a 1.2.5 First Bad Commit: 7/21/09 2e2e4d118e497 1.2.5 I am running on the de3f80bc6ec2a commit right now and it is working fine. If I compile the 2e2e4d118e497 package -- WHAM, the driver is dead-as-a-door-nail -- nothing but dead screen. I found it, now you gotta fix it :-) All of the Xorg.[01].log[.old] files can be found: http://www.3111skyline.com/download/linux/radeonhd/crash/xorg-log4/ Let me know what else to send. Man that took a while. Especially not knowing git bisect. I finally gave up on having git bisect "next" whatever step through the commits. I just had Lynx open in tty1 to the git repository, and just copied the commit number to 'git bisect start "lotsofnumbers" 1.2.5' and kept bracketing good/bad commits and finally got there. Let me know what else I can send so you guys can get the driver repaired. It was kind of fun, thanks. -- 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

1 0

Re: [radeonhd] slightly confused about PowerManagement logging
by Mark Struberg 24 Aug '09

24 Aug '09

Thanks Matthias! >From the electronical point, I'd say that not running 256MB of DDR3 graphics memory on max speed of 800 MHz may easily bring 2 to 4 Watt (which is a lot on a notebook). I'm not sure about the ATI hardware, but usually the memory management in the GC also runs with 800MHz then, isn't? But you are perfectly right, switching off unused parts of the hardware will probably give us much even power benefits. I'lllook at the ForceLowPower code but I don't believe that I'm deep enough into radeonhd to disable PEs myself. txs and LieGrue, strub ----- Original Message ---- > From: Matthias Hopf <mhopf(a)suse.de> > To: Mark Struberg <struberg(a)yahoo.de> > Cc: radeonhd(a)opensuse.org > Sent: Thursday, August 20, 2009 2:01:08 PM > Subject: Re: [radeonhd] slightly confused about PowerManagement logging > > On Aug 18, 09 17:45:48 +0000, Mark Struberg wrote: > > Also, my notebook gets a lot hotter than with fglrx (with kernel 2.6.28) and > bat lifetime is reduced from 3:40 to 2:30. > > I doubt that you can get to such low levels by reducing clocks alone. I > still assume there is some yet unknown mechanism to switch off parts of > the hardware that are not used. > > Maybe reducing the number of active PEs could help? The documentation is > available... > > Matthias -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

HPD Complaing
by Ed Martin 23 Aug '09

23 Aug '09

Hi, I have a Diamond radeonhd 3870 (http://www.newegg.com/Product/Product.aspx?Item=N82E16814103050) and i can't use it without the 'Option "HPD" "off"', if i comment it out xorg reports no screens found. I atached the lspci info for the card, i don't know if you need anything else. 05:00.1 Audio device: ATI Technologies Inc Radeon HD 3870 Audio device Subsystem: Diamond Multimedia Systems Device aa18 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin B routed to IRQ 17 Region 0: Memory at da510000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #8, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [100] Vendor Specific Information <?> Kernel driver in use: HDA Intel -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

0x9591:0x103C:0x30E7: ATI Mobility Radeon HD 3650
by Marek Wiącek 22 Aug '09

22 Aug '09

Greetings, I am attempting to set up the radeonhd driver (1.2.5 - 20090714git) on Fedora 11 running on my HP EliteBook 8530p laptop. The laptop panel works correctly, but an external screen only works over an VGA link (HDMI does not work). Note that hardware issues are not likely because the same setup works correctly in Windows XP running on the same laptop. For start, the HDMI connection is not detected at all until the HPD option is set to "swap". Now that the option has been set up xrandr correctly reports a connection and is able to retrieve a list of supported resolutions. When I set a display mode with xrandr, the tool reports that it has been successfully enabled (asterisk is shown next to the selected mode), but the monitor remains in idle mode (this is not the same as "no signal" error, because the panel reports that problem in a different way when the HDMI cable is disconnected). The UseATOMBIOS option does not seem to have any effect on this issue. Output from lspci | grep -i radeonhd: 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3650 01:00.1 Audio device: ATI Technologies Inc RV635 Audio device [Radeon HD 3600 Series] -- Regards, Marek Wiącek -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

Radeon HD 4350 and AtomBIOS initialization order
by Hans de Ruiter 21 Aug '09

21 Aug '09

Hi, I've been testing a Radeon HD 4350 card with a driver that I'm writing that is similar to yours, and I go a black screen initially. After days of searching for the problem, I finally found out that calling ASICInit while the VGA output is still running results in the black screen; I think that it hangs the memory controller, or something similar. In order to save you lots of frustration, the following code solved the problem: rhdVGADisable(rhdDriver); rhdAllIdle(rhdDriver); /* run AsicInit */ if (!rhdAtomASICInit(rhdDriver->atomBIOSHandle)) { dprintf(0, "%s: AsicInit failed. Won't be able to obtain VRAM " "FB scratch space\n",__func__); } I recommend that you remove the rhdAtomASICInit() call from the AtomBIOS initialization function, and add the code above where appropriate (the xf86-video-ati driver puts it in EnterVT). regards, Hans -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

slightly confused about PowerManagement logging
by Mark Struberg 20 Aug '09

20 Aug '09

Hi! I'm using a HD3470 w 256MB dedicated RAM on my notebook and updated my kernel to 2.6.30 today to get DRI running for radeonhd (which worked like a charm after a recompile). I tried to enable PowerManagement with the following section in my xorg.conf: > Driver "radeonhd" > Option "DRI" > Option "ForceLowPowerMode" "yes" > Option "LowPowerModeEngineClock" "110000" The log shows that the power mode settings get scanned and used: >(**) RADEONHD(0): Option "DRI" >(**) RADEONHD(0): Option "ForceLowPowerMode" "yes" >(**) RADEONHD(0): Option "LowPowerModeEngineClock" "110000" ... >(II) RADEONHD(0): Power Management: used engine clock / memory clock / core (VDDC) voltage (0: ignore) >(II) RADEONHD(0): Power Management: Raw Ranges >(II) RADEONHD(0): Minimum 250000 kHz / 250000 kHz / 0.950 V >(II) RADEONHD(0): Maximum 0 kHz / 0 kHz / 1.200 V >(II) RADEONHD(0): Default 680000 kHz / 800000 kHz / 1.200 V >(II) RADEONHD(0): PowerPlayInfo Revision 0401 >(II) RADEONHD(0): Power Management: Validated Ranges >(II) RADEONHD(0): Minimum 110000 kHz / 250000 kHz / 0.950 V >(II) RADEONHD(0): Maximum 680000 kHz / 800000 kHz / 1.200 V >(II) RADEONHD(0): Default 680000 kHz / 800000 kHz / 1.200 V >(II) RADEONHD(0): Power Management: Known Good Configurations >(II) RADEONHD(0): 1 680000 kHz / 800000 kHz / 1.200 V >(II) RADEONHD(0): 2 110000 kHz / 405000 kHz / 0.950 V >(II) RADEONHD(0): 3 300000 kHz / 405000 kHz / 0.950 V >(II) RADEONHD(0): 4 680000 kHz / 800000 kHz / 1.200 V >(II) RADEONHD(0): 5 110000 kHz / 405000 kHz / 0.950 V >(II) RADEONHD(0): 6 110000 kHz / 405000 kHz / 0.950 V >(II) RADEONHD(0): 7 300000 kHz / 405000 kHz / 0.950 V >(II) RADEONHD(0): 8 300000 kHz / 405000 kHz / 1.200 V >(II) RADEONHD(0): 9 550000 kHz / 700000 kHz / 1.200 V >(II) RADEONHD(0): 10 550000 kHz / 700000 kHz / 1.200 V >(II) RADEONHD(0): 11 300000 kHz / 800000 kHz / 1.200 V >(II) RADEONHD(0): 12 300000 kHz / 800000 kHz / 1.200 V >(II) RADEONHD(0): 13 680000 kHz / 800000 kHz / 1.200 V >(II) RADEONHD(0): 14 300000 kHz / 405000 kHz / 0.950 V >(II) RADEONHD(0): 15 300000 kHz / 405000 kHz / 0.950 V >(II) RADEONHD(0): ForceLowPowerMode: forced engine clock at 110000kHz >(II) RADEONHD(0): ForceLowPowerMode: calculated memory clock at 400000kHz >(II) RADEONHD(0): Power Management: Final Levels >(II) RADEONHD(0): Off 110000 kHz / 250000 kHz / 0.950 V >(II) RADEONHD(0): Idle 110000 kHz / 400000 kHz / 1.200 V But further down the log it seems that those settings will not be used: >(II) RADEONHD(0): Attempting to enable power management >(II) RADEONHD(0): Current Engine Clock: 675000 >(II) RADEONHD(0): Current Memory Clock: 792000 >(II) RADEONHD(0): Current Chip Voltage: 0 Also, my notebook gets a lot hotter than with fglrx (with kernel 2.6.28) and bat lifetime is reduced from 3:40 to 2:30. Is there anything I may try in the xorg.conf or in the code? Find my full xorg.log attached txs and LieGrue, strub

3 4