From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83461] hdmi screen flicker/unusable
Date: Thu, 19 Feb 2015 20:36:02 +0000 [thread overview]
Message-ID: <bug-83461-2300-TS96mxzEFx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-83461-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=83461
Joerg Esser <jackfritt@boh.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jackfritt@boh.de
--- Comment #35 from Joerg Esser <jackfritt@boh.de> ---
I had similar problems until I used 3.18.7.
I couldn´t even boot beyond radeon load. The whole kernel crashed and my
Monitor showed no usable signal. I had to blacklist and load it manually with
option radeon.dpm=0, after turning on my Monitor . With kernel 3.18.6 I could
use the radeon option radeon.aspm=0, but still had to turn on my Monitor before
radeon module load.
Now with this kernel I only need radeon.aspm=0 and no blacklist option, either
the Monitor is turned on before or after radeon module load. Also GPU speedup
with Video output works fine.
Thx alot!!
Here´s my card info
lspci -s 01:00.0 -vv
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar
[Radeon HD 5000/6000/7350/8350 Series] (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited / Sapphire Technology Device e157
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 A routed to IRQ 33
Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at f7cc0000 (64-bit, non-prefetchable) [size=128K]
Region 4: I/O ports at d000 [size=256]
Expansion ROM at f7ca0000 [disabled] [size=128K]
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 256 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 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s L1, Exit
Latency L0s <64ns, L1 <1us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s, Width x2, TrErr- Train- SlotClk+ DLActive-
BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-,
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-,
OBFF Disabled
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB,
EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-,
LinkEqualizationRequest-
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee00000 Data: 40e2
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1
Len=010 <?>
Capabilities: [150 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt-
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Kernel driver in use: radeon
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-02-19 20:36 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 18:49 [Bug 83461] New: hdmi screen flicker/unusable bugzilla-daemon
2014-09-08 4:22 ` [Bug 83461] " bugzilla-daemon
2014-09-15 17:03 ` bugzilla-daemon
2014-09-15 18:57 ` bugzilla-daemon
2014-09-16 16:00 ` bugzilla-daemon
2014-09-17 1:10 ` bugzilla-daemon
2014-09-17 14:35 ` bugzilla-daemon
2014-10-19 19:35 ` bugzilla-daemon
2014-10-19 19:37 ` bugzilla-daemon
2014-10-20 16:20 ` bugzilla-daemon
2014-10-23 17:55 ` bugzilla-daemon
2014-10-23 18:05 ` bugzilla-daemon
2014-10-23 18:06 ` bugzilla-daemon
2014-10-24 18:00 ` bugzilla-daemon
2014-10-28 15:49 ` bugzilla-daemon
2014-11-01 19:40 ` bugzilla-daemon
2014-11-01 19:45 ` bugzilla-daemon
2014-11-01 20:01 ` bugzilla-daemon
2014-11-01 20:01 ` bugzilla-daemon
2014-11-02 11:58 ` bugzilla-daemon
2014-11-07 19:19 ` bugzilla-daemon
2014-11-17 11:44 ` bugzilla-daemon
2014-11-18 15:50 ` bugzilla-daemon
2014-11-18 15:50 ` bugzilla-daemon
2014-11-28 21:20 ` bugzilla-daemon
2014-11-29 16:30 ` bugzilla-daemon
2014-11-30 20:51 ` bugzilla-daemon
2014-12-01 11:47 ` bugzilla-daemon
2014-12-28 8:24 ` bugzilla-daemon
2014-12-28 22:11 ` bugzilla-daemon
2014-12-30 16:24 ` bugzilla-daemon
2015-01-17 8:54 ` bugzilla-daemon
2015-01-20 11:23 ` bugzilla-daemon
2015-02-09 16:09 ` bugzilla-daemon
2015-02-09 16:29 ` bugzilla-daemon
2015-02-19 20:36 ` bugzilla-daemon [this message]
2015-02-19 20:39 ` bugzilla-daemon
2015-02-19 20:49 ` bugzilla-daemon
2016-05-02 22:31 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-83461-2300-TS96mxzEFx@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.