dri-devel February 2012

dri-devel@lists.freedesktop.org

114 participants
627 discussions

[Bug 42373] New: Radeon HD 6450 (NI CAICOS) screen corruption on boot
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=42373 Bug #: 42373 Summary: Radeon HD 6450 (NI CAICOS) screen corruption on boot Classification: Unclassified 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: kunal.gangakhedkar(a)gmail.com Depends on: 40935 Created attachment 52891 --> https://bugs.freedesktop.org/attachment.cgi?id=52891 dmesg log Bought a new Radeon HD 6450 for the new desktop I was building using PhenomII X6 1075T. Installed Kubuntu Oneiric (11.10) amd64. As soon as any FB client (e.g. plymouth splash screen) starts accessing the card after switching to KMS, the screen image gets totally corrupted. Even Xorg/KDM fail to show anything useful. I can only reset the machine using the power button soft-off. Three-finger-salute also doesn't work. However, it does work in about 1 out of 10 times - if somehow the apps trying to use FB device can be killed while the radeon driver is trying to work on the chip. If KMS is disabled, the machine boots up, but Xorg fails to start saying "KMS is needed for CAICOS". The screenshots are available at: a. KMS with plymouth splash: http://img1.UploadScreenshot.com/images/main/10/30100130871.jpg b. KMS without plymouth splash (shows init msgs with bluish tinge in the background): http://img1.UploadScreenshot.com/images/main/10/30100182712.jpg c. KMS + Xorg lockup: http://img1.UploadScreenshot.com/images/main/10/30100211337.jpg d. KMS + Xorg successful start: http://img1.UploadScreenshot.com/images/main/10/30100232928.jpg I believe this is the same as bug #40935 - however, I haven't been able to boot into the system to test suspend/resume yet. Finally, I used an old nVidia GeForce 7100 GS on the same system that I had lying around as a workaround. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 48

[Bug 41766] New: radeon lvds panel heavy flickering after opening laptop lid (Mobility Radeon HD 3650)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=41766 Summary: radeon lvds panel heavy flickering after opening laptop lid (Mobility Radeon HD 3650) Product: DRI Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: pasik(a)iki.fi I'm using a laptop with Mobility Radeon HD 3650 (HP EliteBook 8530p). Normally the laptop is in a docking station, so I'm only using the external DVI monitor. The laptop lid is closed and the laptop internal LVDS panel is disabled while in the dock. I just tried the new Fedora 16 beta liveCD on my laptop. Fedora 16 automatically enables all display outputs, which means also the internal LVDS panel gets enabled, even when my laptop lid is closed. And the gnome desktop gets extended to both the DVI monitor and internal LVDS panel. This means I need to actually open the laptop lid to see the gnome menus, because they're displayed only on the internal LVDS panel. This is a configuration/defaults issue in Fedora 16, and that's not the bug I'm reporting. While opening the laptop lid I noticed the internal LVDS display is heavily flickering, and the screen is totally unreadable. I've uploaded a video of the heavily flickering LVDS panel here: http://pasik.reaktio.net/fedora/f16/radeon/f16-beta-laptop-radeon-flicker-x… Fedora 16 beta is using Linux 3.1.0-rc6. dmesg available here: http://pasik.reaktio.net/fedora/f16/radeon/f16-beta-laptop-radeon-dmesg.txt I tried rebooting the laptop a couple of times, and it seems the flickering doesn't happen on every reboot.. but it happens on *most* reboots. Flickering starts already when kernel is booting, before Xorg is started. Any more info needed ? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 16

[Bug 41762] New: radeon default power_profile "default" makes laptop overheat (Mobility Radeon HD 3650)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=41762 Summary: radeon default power_profile "default" makes laptop overheat (Mobility Radeon HD 3650) Product: DRI Version: unspecified 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: pasik(a)iki.fi I'm using a laptop with Mobility Radeon HD 3650, and I've had overheating problems for a quite some time, with multiple kernel versions. The issue happens at least with Fedora 14, Fedora 15 and latest Fedora 16 (beta). As a default radeon power_profile "default" is being used, and it causes laptop overheating and emergency thermal shutdowns.. on a completely idle system! It seems the power management doesn't work with the opensource radeon driver on this laptop (HP EliteBook 8530p). See below for analysis and more info. When I manually switch the radeon power_profile to "low" (see below) the temperature of the laptop decreases over 10 degrees celsius, making the laptop much cooler and also the fans will immediately slow down because the temperature goes down. Any idea why the "default" power_profile doesn't automatically run the card at lower engine/memory clock speeds? Here's more information from Fedota 16 beta (x86_64) liveCD.. notice how the temperature goes down from 84C to 72C when switching to power_profile "low": # cat /etc/redhat-release Fedora release 16 (Verne) # uname -a Linux localhost.localdomain 3.1.0-0.rc6.git0.3.fc16.x86_64 #1 SMP Fri Sep 16 12:26:22 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux # lspci|grep -i vga 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3650 $ cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 600000 kHz current engine clock: 594000 kHz default memory clock: 700000 kHz current memory clock: 693000 kHz voltage: 1100 mV PCIE lanes: 16 # cat /sys/devices/virtual/thermal/thermal_zone3/device/path \_TZ_.CPUZ $ cat /sys/devices/virtual/thermal/thermal_zone3/temp 84000 # cat /sys/class/drm/card0/device/power_profile default # echo low > /sys/class/drm/card0/device/power_profile (wait for 5 mins.. and notice how fans slow down) $ cat /sys/devices/virtual/thermal/thermal_zone3/temp 72000 # cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 600000 kHz current engine clock: 334120 kHz default memory clock: 700000 kHz current memory clock: 405000 kHz voltage: 900 mV PCIE lanes: 16 dmesg for the f16beta 3.1.0-rc6 kernel available here: http://pasik.reaktio.net/fedora/f16/radeon/f16-beta-laptop-radeon-dmesg.txt -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 14

[Bug 41606] New: Heavy flickering on an Sony Vaio laptop after lid close/vblank/pm-suspend
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=41606 Summary: Heavy flickering on an Sony Vaio laptop after lid close/vblank/pm-suspend 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: bugs.xorg(a)boris64.net Created an attachment (id=52135) --> (https://bugs.freedesktop.org/attachment.cgi?id=52135) dmesg My Sony Vaio laptop sometimes suffers from flickering after resuming from lid-close/vblank/pm-suspend. I can't reproduce it everytime, but i happens way too often. Additionally, the flickering won't go away until i poweroff the laptop and wait some time until switching it on again. Please tell me what kind of logs/infos exactly you need, i'll get 'em as soon as the flickering is triggered again. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 5

[Bug 41561] New: Hotplug detect does not work for HDMI monitor on Fusion E-350 board
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 13

[Bug 41418] New: [RV350] Screen corruption with certain resolutions on LVDS (scaled)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 8

[Bug 38657] New: Redwood: power state #4 not used
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 4

[Bug 41366] New: HDMI on a Fusion board only comes up when LVDS is already enabled
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 8

[Bug 41002] New: Switching doesn't work between plymouth and xorg.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 2

[Bug 40935] New: radeon lockup on resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 10

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel February 2012