dri-devel March 2012

dri-devel@lists.freedesktop.org

114 participants
646 discussions

[Bug 32556] New: screen flickers all the time with desktop image appearing only briefly
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32556 Summary: screen flickers all the time with desktop image appearing only briefly Product: DRI Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: critical Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: 3ntr0p13(a)gmail.com Created an attachment (id=41344) --> (https://bugs.freedesktop.org/attachment.cgi?id=41344) dmesg Machine is the same as in bug report 28331 although with different software components: Acer Aspire L5100 with an AMD Athlon 64 X2 Dual Core Processor 4000+, this time running a 64 bits debian squeeze. The machine is a small factor desktop machine designed around laptop components, so the graphic card is an integrated radeon x1200. When running a linux vanilla kernel 2.6.37-rc6, the screen flickers all the time making the machine unusable, while with debian kernel 2.6.32-5 such "flick to black" event occur from time to time, making it annoying but usable. While booting with radeon.modeset=0 the problem doesn't exhibits itself The following packages version from debian squeeze are installed: xserver-xorg 1:7.5+8 xserver-xorg-core 2:1.7.7-10 xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 Please find attached Xorg.0.log, dmesg, register dumps for ums and kms for that machine (when booted on 2.6.37-rc6). Regards, Gildas -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 38

[Bug 32422] New: Large images displayed in Firefox appear corrupted
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32422 Summary: Large images displayed in Firefox appear corrupted 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: da_fox(a)mad.scientist.com Created an attachment (id=41150) --> (https://bugs.freedesktop.org/attachment.cgi?id=41150) Picture describing a thousand words. "A picture says more than a thousand words" (aka see attachment) This is what happens when I try to view the XKCD "Online Communities 2" map (http://xkcd.com/802_large/) or other large images in firefox. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 21

[Bug 47708] New: LVDS panel does not turns off in stand-by mode
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=47708 Bug #: 47708 Summary: LVDS panel does not turns off in stand-by mode 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: eugene.shalygin(a)gmail.com Created attachment 58858 --> https://bugs.freedesktop.org/attachment.cgi?id=58858 dmesg When video goes into sleep mode, LVDS panel starts to show screens filled with b/w gradients and RGB colours in a cycle. In the same time a screen, connected via Display-Port goes into sleep mode correctly. This happens with and without X running. Ati drivers do not show such a behaviour. Hardware: Acer Aspire 8942g with Mobility Radeon HD 5850. Linux version 3.3 (but this happens starting with version 2.6.2x of 2.6.3x when I've tried KMS for the first time). -- 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 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2012