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.
https://bugs.freedesktop.org/show_bug.cgi?id=39267
Summary: Dynamic power management does not work on HD5870
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: darkbasic4(a)gmail.com
I recently switched from an HD3870 to an HD5870, before dynpm did work
flawlessly (expect of a bit o flickering), but now it doesn't work anymore (it
keeps 'high' and does not switch to the lower power states). Instead 'low'
power profile does work even better than the 3870, it goes from 70 to 45°C
instead of 55°C.
linux-3.0.0-rc3, mesa git master, libdrm git master, fx86-video-ati git master,
xorg-server 1.10.3
Let me know which kind of information do you need.
--
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=39063
Summary: RV630: Sapphire HD 2600 XT power management doesnt
work.
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: vladkuzm(a)gmail.com
Created an attachment (id=48885)
--> (https://bugs.freedesktop.org/attachment.cgi?id=48885)
dmesg
On opensource drivers power managment dont work at all on my Sapphire HD 2600
XT. I tried every state - nothing happens, even dynpm doesnt works. Tested on
Ubuntu 11.04 amd64 and gentoo amd64-2.6.38.
/sys/kernel/debug/dri/0/radeon_pm_info always same:
default engine clock: 800000 kHz
current engine clock: 796500 kHz
default memory clock: 700000 kHz
current memory clock: 693000 kHz
voltage: 1200 mV
PCIE lanes: 16
sensors:
radeon-pci-0200
Adapter: PCI adapter
temp1: +82.0 C
On fglrx everything works fine.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.