dri-devel December 2012

dri-devel@lists.freedesktop.org

121 participants
687 discussions

[Bug 46711] New: Monitor not turning on after DisplayPort re-plug in Xorg
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=46711 Bug #: 46711 Summary: Monitor not turning on after DisplayPort re-plug in Xorg Classification: Unclassified 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: tvrtko.ursulin(a)onelan.co.uk Created attachment 57747 --> https://bugs.freedesktop.org/attachment.cgi?id=57747 Kernel DRM debug log showing successful replug without, and failing with Xorg running. On a AMD G-T56N (Radeon HD 6310) box connected to the monitor via DisplayPort monitor does not come on after re-plugging the display cable but claims to be in power save. At the same time, according to xrandr it is connected and displaying. Stopping Xorg and monitor comes back up displaying the console. Re-pluging the display cable with no Xorg running is fine. Attached kernel DRM debug log. Log itself which ends after cable re-plug when Xorg is running. Which is when the display goes into power save. Before that in the same log you can find Xorg starting up and before that a successful cable re- plug when X was not running. All this is with kernel.org 3.3.0-rc4 kernel. Xorg packages are: xorg-x11-server-Xorg-1.11.3-1.fc16.x86_64 xorg-x11-drv-ati-6.14.3-8.20120209gite20284409.fc16.x86_64 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 26

[Bug 46660] New: Xorg & KMS go to black screen after linux version 2.6.39
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=46660 Bug #: 46660 Summary: Xorg & KMS go to black screen after linux version 2.6.39 Classification: Unclassified 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: vladi(a)aresgate.net Created attachment 57687 --> https://bugs.freedesktop.org/attachment.cgi?id=57687 Xorg config constant while doing the bisect. Hi, Getting an black screen after panasonic viera tc-p42x1. after doing an git bisect good v2.6.39 on git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git i come to this: fe6f0bd03d697835e76dd18d232ba476c65b8282 is the first bad commit commit fe6f0bd03d697835e76dd18d232ba476c65b8282 Author: Marek Olšák <maraeo(a)gmail.com> Date: Sat May 7 01:09:57 2011 +0200 drm/radeon/kms: add missing Evergreen texture formats to the CS parser BC6 and BC7 are described in ARB_texture_compression_bptc. No idea what FMT_32_AS_32_32_32_32 is good for. Signed-off-by: Marek Olšák <maraeo(a)gmail.com> Signed-off-by: Dave Airlie <airlied(a)redhat.com> :040000 040000 bd72080004eca34dd6c17a3111d76f1b515f5e8d ea46d48c05fb870991f72f0d9e2ebd936e4214aa M drivers -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 16

[Bug 45291] New: No video output via DisplayPort on Mobility HD 4670.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=45291 Bug #: 45291 Summary: No video output via DisplayPort on Mobility HD 4670. Classification: Unclassified Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: jonimoose(a)gmail.com Created attachment 56209 --> https://bugs.freedesktop.org/attachment.cgi?id=56209 dmesg I have a Dell Studio XPS 1610 laptop and a Dell U2312HM monitor with DisplayPort. The monitor works in the BIOS but as soon as Grub loads and Linux starts to boot it blanks and enters Powersave mode.once in X xrandr reports it as on but there is no picture and the monitors OSD just continues to report that it is in Powersave mode. Enabling and disabling the monitor via Xrandr does not error and my windows manager resizes things as if it was enabled but the monitor still shows no input. There are no errors in dmesg during this and everything is reported as working.(the warning at the end of dmesg is from a different HDMI monitor which I plugged later since the DisplayPort one wasn't working) -- 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 44549] New: "Ring buffer test failed" on Radeon 5450
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=44549 Bug #: 44549 Summary: "Ring buffer test failed" on Radeon 5450 Classification: Unclassified Product: DRI Version: XOrg CVS 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: ebischoff(a)nerim.net linux kernel : 3.2.0 libdrm-radeon1 : 2.4.29 xserver-xorg-video-radeon : 6.14.99 motherboard : ASUS M2A-VM HDMI (*no* VIA chipset) Graphics card : msi R5450 with 1 Gb onboard RAM memory size : 4 Gb Description : when booting, the message "Ring buffer test failed" appears in dmesg log. A a consequence, the software rasterizer is chosen, and after X is started, there is no 3D acceleration. Workaround : when I add "mem=3G" to the kernel parameters, the message disappears, and I get 3D acceleration. Of course, 1 Gb of RAM memory is lost for the applications. (log files will get attached to this bug report) -- 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 43835] New: System crashes when radeon firmware blob (R520_cp.bin) is installed
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=43835 Bug #: 43835 Summary: System crashes when radeon firmware blob (R520_cp.bin) is installed Classification: Unclassified Product: DRI Version: XOrg CVS Platform: Other URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=65153 2 OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: noelamac(a)gmail.com Created attachment 54426 --> https://bugs.freedesktop.org/attachment.cgi?id=54426 Logs ("dmesg" and "xorg.0.log" for kernels 3.2-rc4 and 3.1 with and without the firmware installed) 1. Steps to reproduce the problem Running Debian Wheezy, by installing the package "firmware-linux-nonfree" which contains the firmware to enable 3D acceleration for the ATI card (M56P Radeon Mobility X1600), when the system starts and user logins, the system crashes (no specific action triggers the crash, is just about time to get it). 2. Symptoms The user receives a "kernel oops" (kernel 3.1) or system hangs with a trace (kernel 3.2-rc4) and system locks. 3. Tested kernels The user has tested kernel 3.1 (Wheezy's stock kernel) and 3.2-rc4 (from Debian's experimental branch). Both kernels expose the same result when firmware is installed. On the other hand, both kernels work fine as soon as the firmware package is unistalled. 4. Additional information The crash has been tracked in Debian BTS #651532 (full link available in the URL field). 5. Attached logs (4 files): - "dmesg" and "Xorg.0.log" for kernels 3.2-rc4 and 3.1 when firmware is installed. - "dmesg" and "Xorg.0.log" for kernels 3.2-rc4 and 3.1 when firmware is not installed. 6. Other considerations Please, note that I am opening the this bug on behalf of another person who is experiencing the crash. For this reason I'm CC'ing to him. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 59

[Bug 43481] New: DVI-0 with unknown connection but available modes
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=43481 Bug #: 43481 Summary: DVI-0 with unknown connection but available modes Classification: Unclassified Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: h.judt(a)gmx.at This might not be a bug, but a few kernel revisions ago, DVI-0 became active: xrandr: Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192 DVI-0 unknown connection (normal left inverted right x axis y axis) 1024x768 60.0 800x600 60.3 640x480 59.9 512x384 120.0 400x300 120.6 320x240 120.1 LVDS connected 1440x900+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1440x900 60.0*+ 1280x854 59.9 1280x800 59.8 1280x720 59.9 1152x768 59.8 1024x768 59.9 800x600 59.9 848x480 59.7 720x480 59.7 640x480 59.4 VGA-0 disconnected (normal left inverted right x axis y axis) Hardware: Lenovo Thinkpad T400 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3400 Series What's this DVI-0? LVDS and VGA-0 (when connected) work fine, and DVI-0 does not hurt, but still I thought I'd report this here in case this shouldn't be as it is now ;-) -- 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 43278] New: System hangs after suspend to ram or disk cause radeon firmware cannot be loaded.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=43278 Bug #: 43278 Summary: System hangs after suspend to ram or disk cause radeon firmware cannot be loaded. Classification: Unclassified Product: DRI Version: XOrg 6.7.0 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: hubba(a)online.de Hi, since a couple of months I have the problem with my notebook that the system hangs after doing a suspend to ram or disk. I reported the problem to the Debian team and to Bugzilla kernel team (find links below). Some tests last week by Debian (please watch the debian bug report link for further details) showed that the problem is caused by the Radeon module. The following error message occurrs when loading the radeon module: [ 270.715016] radeon_cp: Failed to load firmware "radeon/R300_cp.bin" [ 270.715045] [drm: r100_cp.init] *ERROR* Failed to load firmware! [ 270.715061] radeon 0000:01:05:0: failed initializing CP (-2) . [ 270.715072] radeon 0000:01:05:0:Disabling GPU acceleration The firmware and especially the file R300_cp.bin exists in /lib/firmware/radeon . The current version of xserver-xorg-video-radeon package is 6.14.3-1 . Please let me know if you need further information or if I can do something else. Thanks and regards Rolf http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600846 https://bugzilla.kernel.org/show_bug.cgi?id=22022 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 17

[Bug 42997] New: [R600] Corruption after resume from suspend to ram
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=42997 Bug #: 42997 Summary: [R600] Corruption after resume from suspend to ram Classification: Unclassified Product: DRI Version: XOrg CVS 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: thoemy(a)gmail.com Created attachment 53605 --> https://bugs.freedesktop.org/attachment.cgi?id=53605 Xorg log showing start, suspend and resume After resuming from suspend to ram I experience corruptions on the whole screen. I'm using a compositing desktop with gnome-shell but the corruption is also visible in the text consoles. I can recover from the corruption and continue work normally if I change the resolution or screen orientation. This bug is present in the kernel versions 3.0 - 3.2rc2 and I think also in some releases before them. The graphics card is a HD3870, X.Org X Server 1.11.1.902 The radeon module is loaded with dynclks=1 audio=1 Attached are pictures of the corruption and a my Xorg.log. Any other information I can provide? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

[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

← Newer
1
2
3
4
5
6
7
...
69
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel December 2012