https://bugs.freedesktop.org/show_bug.cgi?id=41561
Summary: Hotplug detect does not work for HDMI monitor on
Fusion E-350 board
Product: DRI
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: simon.farnsworth(a)onelan.co.uk
Using airlied-drm-fixes kernel as of commit
6777a4f6898a53974ef7fe7ce09ec41fae0f32db with Alex Deucher's patch
"drm/radeon/kms: use hardcoded dig encoder to transmitter mapping for DCE4.1"
on top, I'm not seeing uevents from the kernel when I plug and unplug a HDMI
monitor.
dmesg with drm.debug=0xf shows me the following when I connect a monitor:
# dmesg -c
[15202.939581] [drm:evergreen_irq_process], r600_irq_process start: rptr 5872,
wptr 5888
[15202.939609] [drm:evergreen_irq_process], IH: HPD2
[15203.050597] [drm:radeon_atombios_connected_scratch_regs], DFP1 connected
[15203.050605] [drm:output_poll_execute], [CONNECTOR:15:HDMI-A-1] status
updated from 1 to 1
[15203.052661] [drm:output_poll_execute], [CONNECTOR:17:VGA-1] status updated
from 2 to 2
radeonreg suggests that the HPD sense bit is correctly set
# ./radeonreg regs all | grep 00006028 # DC_HPD2_INT_STATUS
00006028 ff0ff012 (-15732718)
When I remove the monitor, I get the following from dmesg and radeonreg:
# dmesg -c
[15307.075271] [drm:evergreen_irq_process], r600_irq_process start: rptr 5888,
wptr 5904
[15307.075300] [drm:evergreen_irq_process], IH: HPD2
[15307.131727] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid,
remainder is 192
[15307.131733] Raw EDID:
[15307.131738] 3f ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[15307.131742] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[15307.131745] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[15307.131749] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[15307.131752] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[15307.131756] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[15307.131759] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[15307.131763] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[15307.141965] [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but
no|invalid EDID
[15307.141975] [drm:radeon_atombios_connected_scratch_regs], DFP1 connected
[15307.141981] [drm:output_poll_execute], [CONNECTOR:15:HDMI-A-1] status
updated from 1 to 1
[15307.144028] [drm:output_poll_execute], [CONNECTOR:17:VGA-1] status updated
from 2 to 2
# ./radeonreg regs all | grep 00006028 # DC_HPD2_INT_STATUS
00006028 ff0ff000 (-15732736)
suggesting that HPD sense bits are being updated correctly by the hardware, but
that this isn't resulting in uevents following through.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=41418
Summary: [RV350] Screen corruption with certain resolutions on
LVDS (scaled)
Product: DRI
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: dev(a)karlchenofhell.org
I'm getting a screen corruption with the resolutions
1400x1050
1440x900
on a RV350, using kernel-3.0.4, libdrm-2.4.26.
A photograph of the corrupted screen under X is attached, though the corruption
also appears using tests/modetest w/o X started.
--------
# lspci -nns1:0.0
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M10 NT [FireGL
Mobility T2] [1002:4e54] (rev 80)
--------
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=38657
Summary: Redwood: power state #4 not used
Product: DRI
Version: unspecified
Platform: All
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: mkgmafbt(a)gmail.com
Created an attachment (id=48390)
--> (https://bugs.freedesktop.org/attachment.cgi?id=48390)
Part of dmesg with power states
It's a Sapphire Radeon HD5670 512MB GDDR5. DRM reports 5 power states, but low
profile won't use #4, wich is the 2D profile, nor does dynpm. All kernels with
Evergreen pm support are affected by this (possible) bug, including 3.0-rc4.
cat /sys/class/drm/card0/device/power_profile
low
cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 775000 kHz
current engine clock: 399990 kHz
default memory clock: 950000 kHz
current memory clock: 950000 kHz
voltage: 1100 mV
PCIE lanes: 16
(should be 150/300 MHz 0.9V)
lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon
HD 5670] [1002:68d8]
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=41366
Summary: HDMI on a Fusion board only comes up when LVDS is
already enabled
Product: DRI
Version: XOrg CVS
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: simon.farnsworth(a)onelan.co.uk
I'm running airlied's drm-fixes, git revision
fdfc61594e6de21c23f955818ef78bcab9bafe40, and experiencing "interesting" times
trying to get HDMI to work on a Fusion GPU (detected by X as [ 49.876] (--)
RADEON(0): Chipset: "AMD Radeon HD 6310 Graphics" (ChipID = 0x9802)).
If I run:
xrandr --output HDMI-0 --off
xrandr --output LVDS --auto
xrandr --output HDMI-0 --mode 1920x1200
the HDMI monitor comes up at 1920x1200
If I run:
xrandr --output HDMI-0 --off
xrandr --output LVDS --off
xrandr --output HDMI-0 --mode 1920x1200
the HDMI monitor immediately enters DPMS Off state, and stays there.
I've confirmed with "grep . /sys/class/drm/card0-HDMI-A-1/*" that the kernel
thinks the HDMI connector is switched on. The only difference I can see is that
HDMI works when it gets CRTC 1, but not when it gets CRTC 0.
I have captured logs from the kernel with drm.debug=0x6 during the runs, in
case that explains what's going on; I will attach them to this bug.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=41002
Summary: Switching doesn't work between plymouth and xorg.
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: fabian.deutsch(a)gmx.de
When initiating a switch to the discrete card while plymouth is running, the
switch doesn't happen completely in the small slot between the end of ply and
Xorg's start.
This happens with current Fedora 15 (all updates).
Note: Maybe this is similar to bug #32970
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=40935
Summary: radeon lockup on resume
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: hramrach(a)gmail.com
The card locked up after resume from suspend.
The resume probably happened because suspend failed and the system did not
shut down at all meaning the card was not reset to text mode.
Initializing radeon from anything but text mode fails but normally does not
lock up the card completely.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=40128
Summary: RV635 (Radeon HD 3600) failed to evaluate ATIF got
AE_BAD_PARAMETER
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: volodymyr(a)shcherbyna.com
Created an attachment (id=50258)
--> (https://bugs.freedesktop.org/attachment.cgi?id=50258)
dmesg output describing original problem
Hello,
I have HD 3600 and I am using Debian sid x86_64. I have noticed recently in my
dmesg output the following line: "failed to evaluate ATIF got AE_BAD_PARAMETER"
and I was suggested to file a bug here.
Please see attached full dmesg output of my machine.
Thank you,
V.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=39953
Summary: Flicker after waking from DPMS sleep
Product: DRI
Version: XOrg CVS
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: minor
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: curaga(a)operamail.com
Created an attachment (id=50058)
--> (https://bugs.freedesktop.org/attachment.cgi?id=50058)
lspci -vvnn
My E-350 laptop screen flickers for ~5 minutes every time after waking from
DPMS. The flicker persists through VT switches and changing the power profile
to high.
After the wait it stabilizes and picture is good again.
It looks similar to a CRT on 60Hz, but xrandr is confident the mode is right
for the lcd (60hz, not something lower).
Lenovo G575 laptop
AMD E-350
Linux 3.0.1
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.