dri-devel July 2015

dri-devel@lists.freedesktop.org

180 participants
1178 discussions

[Bug 89241] A8-6410 APU with integrated R5 Mullins + dedicated R5 M240 Hainan graphics switching not working
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89241 Bug ID: 89241 Summary: A8-6410 APU with integrated R5 Mullins + dedicated R5 M240 Hainan graphics switching not working Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: linux5(a)secure-mail.biz Switching graphics between the A8-6410 APU with integrated R5 Mullins + dedicated R5 M240 Hainan is not working(HP 355 G2 notebook). I think it's because the dedicated gpu for some reason can just not be activated, because "/sys/kernel/debug/vgaswitcheroo/switch" and the Radeon Profile tool show two gpus, but changing the gpu state from "off" to something else within Radeon Profile doesn't work for the dedicated one. I tried the gearsongallium livecd with very recent drivers/Xorg/etc. Versions included in the gearsongallium livedvd i tested: Mesa-git – 10.5_git2015.02.04 Kernel – 3.19-rc6 libdrm – 2.4.99_git2015.01.22 Mesa-demos – 9.1.0_git2014.07.06 xorg-server – 1.16.99.9 xf86-video-ati – 7.99.99_2015.01.15 I also tried in Kubuntu 14.10 to switch with DRI_PRIME=1. If i do that i get corrupt window and lower fps than with integrated gpu with es2gears. However "DRI_PRIME=1 glxinfo" says it's using the dedicated gpu. In gearsongallium i get the same output with or without "DRI_PRIME=1 glxinfo" so it seems to not switch at all with recent drivers/Xorg/etc. I can also post Xorg log and dmesg output, but i couldn't spot anything unusual there looking quickly through it. However "dmesg|grep -i vga" might be important: $ dmesg |grep -i vga [ 1.069056] vgaarb: setting as boot device: PCI:0000:00:01.0 [ 1.069061] vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=io+mem,locks=none [ 1.069077] vgaarb: loaded [ 1.069080] vgaarb: bridge control possible 0000:00:01.0 [ 1.763179] fb0: EFI VGA frame buffer device [ 2.029145] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) [ 2.115398] VGA switcheroo: detected switching method \_SB_.PCI0.VGA_.ATPX handle [ 2.191102] ACPI: Video Device [VGA1] (multi-head: yes rom: no post: no) [ 2.255714] fb: switching to radeondrmfb from EFI VGA [ 2.440405] [drm] VGA-1 [ 2.527423] vga_switcheroo: enabled -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 89155] Dual monitor setup does not initialize
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=89155 Bug ID: 89155 Summary: Dual monitor setup does not initialize Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: adam.reichold(a)t-online.de Created attachment 113508 --> https://bugs.freedesktop.org/attachment.cgi?id=113508&action=edit journalctl -b | grep "\[drm" I am running Arch Linux on an AMD A6-3500 with Radeon HD 6530D graphics on an Gigabyte A55M-S2V mainboard. I just received updated X server to version 1.17.1 together with a rebuilt version 7.5.0 of the XFree86 ATI driver with the kernel staying at 3.18.6. I do have two Samsung monitors connected to the system, one via DVI and one via VGA. This setup always initialized unreliably and I had to manually add modes for the VGA-connected monitor using xrandr --newmode "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync xrandr --addmode VGA-0 "1680x1050_60.00" xrandr --output VGA-0 --mode "1680x1050_60.00" for it to work at all. But after the update described above, the two monitors never initialize properly anymore. Before the update, I sometimes had to power-cycle (meaning switch off power not just a reboot) but it did eventually work after two or three tries. The reason I am reporting this as a Radeon DRM issue instead of an X server problem is that my system log contains errors from the DRM driver about "channel eq" and "clock recovery". I attached those logs grepped for "[drm". Thank for your help and please tell me if I can provide any further information to help diagnose this. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 88891] Errors upon/resuming hibernation.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=88891 Bug ID: 88891 Summary: Errors upon/resuming hibernation. 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: bogy2004(a)abv.bg I'm facing some errors which currently aren't making any problems (not that I know of at least). Still, I'm concerned what do they mean and should I worry. Here's what I get upon entering hibernation state: http://sprunge.us/MZIb And after resuming, I get this: http://sprunge.us/USQb These are both cut from dmesg. Here's my current hardware for more info: OS: Archlinux x86_64 GPU: ATI Mobility Radeon 5145 (today known as 4570). CPU: i3 M350 Mesa version: 10.4.3 Kernel version: 3.18.4 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 88464] booting with radeon.test=1 with radeon3850hd and lockdep validation causes lock-up
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=88464 Bug ID: 88464 Summary: booting with radeon.test=1 with radeon3850hd and lockdep validation causes lock-up Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: arthur.marsh(a)internode.on.net I tried booting with radeon.test=1 Full dmesg output attached. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 88364] Xorg hangs after videocard switching
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=88364 Bug ID: 88364 Summary: Xorg hangs after videocard switching Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: lissamour(a)gmail.com Created attachment 112158 --> https://bugs.freedesktop.org/attachment.cgi?id=112158&action=edit dmesg log steps to reproduce: 1. launch anything through discrete videocard e. g. DRI_PRIME=1 glxgears I expected that program will run through discrete videocard, but after little time xorg hanged. Ubuntu 14.10 64-bit, kernel 3.18.1, lastest mesa and drivers from oibaf ppa. 0a:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun LE [Radeon HD 8550M / R5 M230] (rev ff) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD:+:Pwr:0000:00:02.0 1:DIS: :DynOff:0000:0a:00.0 -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 88183] radeonsi: R9 280X hangs with SuperTuxKart
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=88183 Bug ID: 88183 Summary: radeonsi: R9 280X hangs with SuperTuxKart 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: alexandre.f.demers(a)gmail.com In SuperTuxKart, upon loading the first track of the story mode, the display freezes. The GPU resets but when it comes back everything is messed up and it keeps resetting continuously. I'm using latest kernel 3.19-rc3 with the "drm/radeon: fix VM flush..." patches (also tested without it), latest mesa from git, latest drm from git. I'll see a journald dump outputs something interesting. -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 87796] radeonsi 120Hz graphic glitches
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=87796 Bug ID: 87796 Summary: radeonsi 120Hz graphic glitches Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: magolobel(a)yahoo.com.br Created attachment 111427 --> https://bugs.freedesktop.org/attachment.cgi?id=111427&action=edit video screenshot of the glitch When I enable 120Hz refresh rate in the Radeon R9 290 card, with my Benq XL2420T monitor, I get horizontal glitches in the image. That happens in KDE, Unity, XFCE (all with or without compositing), and games. Without compositing, the windows decorations in KDE show artifacts in 60 and 120Hz. 60Hz refresh rate works okay. Fglx proprietary driver works okay with 120Hz. I also have a Radeon HD 6970 with the radeon OSS driver and it also works okay in 120Hz in my system. Currently I am using Kubuntu 14.10, kernel 3.19RC1 and Mesa git from this PPA: https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa The card is a Sapphire Radeon R9 290 4GB Tri-X. This bug is happening since I got this card, in September. I cant get a direct screenshot nor taking photos (with a smartphone) of the glitch happening, so I take a video of it with a phone and then take a screenshot. -- You are receiving this mail because: You are the assignee for the bug.

1 34

[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

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2015