dri-devel March 2015

dri-devel@lists.freedesktop.org

196 participants
1117 discussions

[Bug 87291] Broken dpm for HD6670 since kernel 3.15
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=87291 Bug ID: 87291 Summary: Broken dpm for HD6670 since kernel 3.15 Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: e.edgar.frank(a)gmail.com Hello there, I'd like to report that since kernel 3.15 its nearly impossible to boot past the grub screen because post grub, during X init my monitor starts to endlessly power down/ power on. The only way to boot is to play around with the restart button, in arround 10 restarts, ~once I would get X to initialize properly. The other way is to put radeon.dpm=0 in the kernel-line. This way no errors occur, but I am left without dynamic power managemenent for the GPU. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 87126] Fragment shader value lock up rv635 device
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=87126 Bug ID: 87126 Summary: Fragment shader value lock up rv635 device Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: pavol(a)klacansky.com Created attachment 110596 --> https://bugs.freedesktop.org/attachment.cgi?id=110596&action=edit apitrace Changing output variable from vec4(1.0) to vec4(0.9) locks the gpu. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 85638] New: system crash randomly with no errors
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=85638 Bug ID: 85638 Summary: system crash randomly with no errors Product: DRI Version: XOrg CVS Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: marcoboffo.waves(a)gmail.com Created attachment 108676 --> https://bugs.freedesktop.org/attachment.cgi?id=108676&action=edit Picture of my screen Everyday, my system crashes randomly and shows random colors on my screens. (Yes, dual monitor) I can't reproduce the bug but it seems to happen on large screen update or little gnome3 transitions. complete dmesg: http://pastebin.com/szzwGKx2 uname -r: 3.17.1-1-ARCH The Xorg.log is untouched since the beginning of this month, so I don't think it can be relevant for the bugfix. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 85469] New: Brightness too high on internal AMD/ATI graphics device, but fine with external AMD/ATI graphics card
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=85469 Bug ID: 85469 Summary: Brightness too high on internal AMD/ATI graphics device, but fine with external AMD/ATI graphics card Product: DRI Version: XOrg CVS Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: paulepanter(a)users.sourceforge.net Created attachment 108433 --> https://bugs.freedesktop.org/attachment.cgi?id=108433&action=edit output of `radeonreg regs dce4` built from radeontool-1.6.3-10-g6b5e7c6 As reported on the list dri-devel [1], the brightness of the internal graphics card is too high on the ASRock E350M1 [2]. Please find the output of `radeonreg regs dce4` attached and I’ll attach the Linux kernel 3.16.5 messages and the Video BIOS too. [1] Brightness too high on internal AMD/ATI graphics device, but fine with external AMD/ATI graphics card http://lists.freedesktop.org/archives/dri-devel/2014-July/thread.html#63006 [2] http://www.asrock.com/mb/amd/e350m1/ -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 85180] New: [drm:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=85180 Bug ID: 85180 Summary: [drm:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD) Product: DRI Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: wrgcpp(a)gmail.com Created attachment 108036 --> https://bugs.freedesktop.org/attachment.cgi?id=108036&action=edit dmesg I'm using Debian Jessie, kernel 3.16.3, my graphic card is 01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] System is booting normally, but GPU acceleration can't start. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 84500] New: [radeonsi] radeon 0000:01:00.0: Packet0 not allowed!
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=84500 Priority: medium Bug ID: 84500 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi] radeon 0000:01:00.0: Packet0 not allowed! Severity: normal Classification: Unclassified OS: All Reporter: alexandre.f.demers(a)gmail.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI On a 7950, I keep getting this error from time to time in dmesg: radeon 0000:01:00.0: Packet0 not allowed! I have associated this error with playing either html5 or flash videos. It may happen when playing offline movies, but I can't tell since I haven't tested it. When the error happens, there is a slight "stuttering" (from a fraction of second to a few seconds). And then it continues. There is nothing in Xorg.0.log about it, and no other message than "radeon 0000:01:00.0: Packet0 not allowed!" in dmesg. -- You are receiving this mail because: You are the assignee for the bug.

1 56

[Bug 84106] New: GPU faults with Xonotic 0.7
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=84106 Priority: medium Bug ID: 84106 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU faults with Xonotic 0.7 Severity: normal Classification: Unclassified OS: All Reporter: darkbasic(a)linuxsystems.it Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 106566 --> https://bugs.freedesktop.org/attachment.cgi?id=106566&action=edit dmesg I have an HD 7950 with latest graphic stack from git, including LLVM 3.6 git from today. kernel is drm-next-3.18-wip from today (3.17.0-rc5-drm-next-3.18-wip). I was running some benchmarks (http://openbenchmarking.org/result/1409197-SO-1407298SO78) while I noticed sometimes the picture froze and then after a second or two it kept running the benchmark ultra fast. when the benchmark finished I noticed lots of GPU faults in dmesg: https://paste.lugons.org/show/5981/ -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 84017] New: HD 4670 only works with MSI disabled
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=84017 Priority: medium Bug ID: 84017 Assignee: dri-devel(a)lists.freedesktop.org Summary: HD 4670 only works with MSI disabled Severity: normal Classification: Unclassified OS: All Reporter: egore(a)gmx.de Hardware: Other Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI Created attachment 106459 --> https://bugs.freedesktop.org/attachment.cgi?id=106459&action=edit dmesg of bootup using radeon.msi=-1 As mentioned on the dri-devel mailing list [1] the HD 4670 in one of my older systems is only capable of doing any 3D when booting with "radeon.msi=0". Find the dmesg of a and lspci output attached. [1] http://lists.freedesktop.org/archives/dri-devel/2014-September/067758.html -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 83800] New: 3DMark2003 crashes radeon with wine 1.7.26 + gallium nine
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=83800 Priority: medium Bug ID: 83800 Assignee: dri-devel(a)lists.freedesktop.org Summary: 3DMark2003 crashes radeon with wine 1.7.26 + gallium nine Severity: normal Classification: Unclassified OS: All Reporter: darkbasic(a)linuxsystems.it Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI HD 7950 Linux 3.17.0-rc2-core-avx-i-drm-next-3.18 20140912 llvm 3.6 git xorg-server 1.15.1 + glamor git mesa git + gallium nine wine 1.7.26 + gallium nine -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 83792] New: Kernel hangs on boot without nomodeset option
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=83792 Priority: medium Bug ID: 83792 Assignee: dri-devel(a)lists.freedesktop.org Summary: Kernel hangs on boot without nomodeset option Severity: normal Classification: Unclassified OS: All Reporter: wayland(a)wayland.id.au Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Hi all. I have a Radeon FireMV 2400. I'm attempting to upgrade from Fedora 13 (kernel 2.6.33) to Fedora 20. More recent kernels have not worked for me; I recently discovered that if I use the nomodeset option, then I can book, but xorg no longer functions. Since it seems that using the nomodeset option is no longer going to be supported, I need to make this work without the nomodeset option. Unfortunately, the computer hangs (no ping via network) during boot. I tried to give it the netconsole option, but this did not seem to produce any results. What else can I try to help resolve this problem? Thanks, -- You are receiving this mail because: You are the assignee for the bug.

1 15

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2015