dri-devel July 2014

dri-devel@lists.freedesktop.org

170 participants
1128 discussions

[Bug 53391] New: nouveau: wrong display output order
by bugzilla-daemon＠bugzilla.kernel.org 08 Dec '21

08 Dec '21

https://bugzilla.kernel.org/show_bug.cgi?id=53391 Summary: nouveau: wrong display output order Product: Drivers Version: 2.5 Kernel Version: 3.8-rc6 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: stijn+bugs(a)linux-ipv6.be Regression: No My graphics card is a Gainward GTX480 (http://www.gainward.com/main/vgapro.php?id=238). It has 2 DVI outputs, and 1 mini HDMI output. The DVI outputs are numbered on the card, with DVI 1 being the closest to the PCIe slot, then DVI 2, and finally the mini HDMI. My primary (left) monitor, is connected to DVI 1, my secondary (right) monitor to DVI 2. When I boot the computer, the BIOS initializes and uses the monitor on DVI 1. Grub is displayed on the primary monitor, and the kernel initially outputs to the primary monitor as well. However, as soon as the nouveau module is loaded, the primary monitor goes to standby and the kernel now uses the secondary monitor (on DVI 2) as primary. When X starts (no Xorg.conf file), it is also displayed on the secondary monitor. When using either efifb, vesafb or uvesafb, the monitor on DVI 1 is always the primary monitor. X with nvidia.ko also uses DVI 1 as the primary display. Finally, when booting Windows, the startup screen is also displayed on the monitor connected to DVI 1. Here comes the weird part: when I am in X, and run xrandr, it does show 3 connected devices: DVI-I-1, DVI-I-2, and HDMI-1, with DVI-I-2 being the only active one. So it seems that in X, the output order is correct, but with nouveaufb the DVI connectors are swapped. I will attach the output of dmesg here. If anything else is needed, please let me know and I'll be happy to add it. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 13

[Bug 51381] New: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo
by bugzilla-daemon＠bugzilla.kernel.org 11 May '21

11 May '21

https://bugzilla.kernel.org/show_bug.cgi?id=51381 Summary: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo Product: Drivers Version: 2.5 Kernel Version: Linux version 3.6.9-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Tue Dec 4 08:04:10 CET 2012 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: a(a)anrd.net Regression: Yes Created an attachment (id=88591) --> (https://bugzilla.kernel.org/attachment.cgi?id=88591) journald log After updating from 3.6.6 to 3.6.9 my laptop with Intel graphics and ATI HD 5650 will not resume from suspend. I use vgaswitcheroo to disable the ATI card at boot. On resume the computer almost hangs (I can press power button and wait 5 minutes for a proper shutdown, but no other interaction is possible). It logs a lot of messages saying: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D098 (len 72, WS 0, PS 0) @ 0xD0C7 Steps to reproduce: echo "OFF" > /sys/kernel/debug/vgaswitcheroo/switch [suspend and resume] Actual results: Almost freeze. Expected results: Resume and work as normal. Log is attached, but if you need anything else just ask. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 62

[Bug 78111] New: APU turbo core boost not working when radeon.dpm=1
by bugzilla-daemon＠bugzilla.kernel.org 03 Dec '20

03 Dec '20

https://bugzilla.kernel.org/show_bug.cgi?id=78111 Bug ID: 78111 Summary: APU turbo core boost not working when radeon.dpm=1 Product: Drivers Version: 2.5 Kernel Version: 3.14.6 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: bgz.marko(a)gmail.com Regression: No I am testing with A6-1450 APU on Arch Linux. If I pass radeon.dpm=1 parameter at boot and start a single core workload then turbostat will report max frequency of about 1000 MHz: Core CPU Avg_MHz Bzy_MHz TSC_MHz time - - 262 998 998 5** 0 0 12 998 998 5** 1 1 998 998 998 2 2 16 998 998 3 3 21 998 998 "cpupower frequency-info" reports that boost state support is supported, but not active: boost state support: Supported: yes Active: no However, when dynamic power management is disabled (radeon.dpm=0), turbostat reports higher frequencies for single core load, up to 1300 Mhz: Core CPU Avg_MHz Bzy_MHz TSC_MHz time - - 320 1214 998 5** 0 0 9 1226 998 5** 1 1 13 1194 998 2 2 41 1143 998 3 3 1216 1216 998 "cpupower frequency-info" confirms that boost is now active. boost state support: Supported: yes Active: yes -- You are receiving this mail because: You are watching the assignee of the bug.

1 14

[Bug 71891] New: 3.13 fails to boot with the radeon module
by bugzilla-daemon＠bugzilla.kernel.org 08 Jun '20

08 Jun '20

https://bugzilla.kernel.org/show_bug.cgi?id=71891 Bug ID: 71891 Summary: 3.13 fails to boot with the radeon module Product: Drivers Version: 2.5 Kernel Version: 3.13.6-1-ARCH Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: sh.siddhartha(a)gmail.com Regression: No $ lspci -k | grep -A3 VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96 [Mobility Radeon HD 4650/5165] Subsystem: Dell Device 0447 Kernel driver in use: fglrx_pci Kernel modules: radeon, fglrx Dell Inspiron N5010 (BIOS) Legacy catalyst works properly. Using the open source radeon driver either boots to tty login with above errors, or boots to a locked up black screen. drm syslog: [drm] Initialized drm 1.1.0 20060810 [drm] radeon kernel modesetting enabled. fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver [drm] initializing kernel modesetting (RV730 0x1002:0x9480 0x1028:0x0447). [drm] register mmio base: 0xFBE20000 [drm] register mmio size: 65536 [drm] Detected VRAM RAM=1024M, BAR=256M [drm] RAM width 128bits DDR [drm] radeon: 1024M of VRAM memory ready [drm] radeon: 1024M of GTT memory ready. [drm] GART: num cpu pages 262144, num gpu pages 262144 [drm] Loading RV730 Microcode [drm] PCIE GART of 1024M enabled (table at 0x000000000025D000). [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] Driver supports precise vblank timestamp query. [drm] radeon: irq initialized. [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 1 usecs [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!! [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!! [drm:rv770_startup] *ERROR* radeon: failed initializing UVD (-1). [drm] Enabling audio 0 support [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs [drm] radeon atom DIG backlight initialized [drm] Radeon Display Connectors [drm] Connector 0: [drm] VGA-1 [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [drm] Encoders: [drm] CRT1: INTERNAL_KLDSCP_DAC1 [drm] Connector 1: [drm] HDMI-A-1 [drm] HPD1 [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [drm] Encoders: [drm] DFP1: INTERNAL_UNIPHY [drm] Connector 2: [drm] LVDS-1 [drm] DDC: 0x7f68 0x7f68 0x7f6c 0x7f6c 0x7f70 0x7f70 0x7f74 0x7f74 [drm] Encoders: [drm] LCD1: INTERNAL_UNIPHY2 [drm] Internal thermal controller with fan control [drm] radeon: dpm initialized [drm] fb mappable at 0xC045E000 [drm] vram apper at 0xC0000000 [drm] size 4325376 [drm] fb depth is 24 [drm] pitch is 5632 fbcon: radeondrmfb (fb0) is primary device [drm:rv770_dpm_set_power_state] *ERROR* rv770_restrict_performance_levels_before_switch failed radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device [drm] Initialized radeon 2.36.0 20080528 for 0000:01:00.0 on minor 0 -- You are receiving this mail because: You are watching the assignee of the bug.

1 51

[Bug 58981] New: Bisected regression; boot failure with Radeon 9250 PCI 256MB + KMS
by bugzilla-daemon＠bugzilla.kernel.org 28 Jan '20

28 Jan '20

https://bugzilla.kernel.org/show_bug.cgi?id=58981 Summary: Bisected regression; boot failure with Radeon 9250 PCI 256MB + KMS Product: Drivers Version: 2.5 Kernel Version: 2.6.35,3.2.45,3.10-rc2 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: jdietrch(a)fastmail.fm Regression: Yes I have a Radeon 9250 PCI 256MB video card in my machine. I discovered that this machine would not boot with 3.2.45 when KMS was enabled by default in the kernel config. Immediately after the grub menu, the screen would go black and nothing more would happen. Or sometimes columns of character-sized "marks" would appear on the screen. In either case, though, the machine would not boot. So I went back to 2.6.33 and found that booting with KMS did work just fine there. So I used git bisect to find where the problem arose, and that pointed to this commit which was merged for 2.6.35: commit 6b8b1786a8c29ce6e32298b93ac8d4a18a2b11c4 Author: Jerome Glisse <jglisse(a)redhat.com> Date: Wed Apr 7 10:21:31 2010 +0000 drm/radeon/kms: enable use of unmappable VRAM V2 I confirmed this result of git bisect by checking out 2.6.35 final and reverting that one commit, and the resulting kernel booted fine with KMS enabled by default. I also tried 3.10-rc2 and that booted fine when I added radeon.modeset=0 to the kernel commandline. I will attach files with dmesg output and lspci. Please let me know if there is anything else I can do. I'll be happy to test a proposed fix if that would be helpful. Thank you, James Dietrich -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 6

[Bug 64721] New: Radeon HD6450 fails on all distro's out of box.
by bugzilla-daemon＠bugzilla.kernel.org 02 Dec '19

02 Dec '19

https://bugzilla.kernel.org/show_bug.cgi?id=64721 Bug ID: 64721 Summary: Radeon HD6450 fails on all distro's out of box. Product: Drivers Version: 2.5 Kernel Version: Linux 3.2.04-amd64 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: ichapman(a)videotron.ca Regression: No I think I'm at the right place to report video card frustrations. Radeon HD450 fails to work out of the box with any Linux. With Debian Wheezy I need to edit the grub line starting with linux and add vga=791 to do anything. vga=771 fails With Knoppix 7.0 I need vga=771 and that's okay, but vga=791 the left half of screen is on right and right on left. The cursor moves to right falls off the screen and re-appears on left side. Very strange. With DebianMint I need vga=771 or 791 to get it to work. On my Acer Aspire laptop with a Radeon HD6310 I do not need any of this vga= stuff. I am sure that this is not a driver problem. All the vga=xxx does is kick it somewhere so that I loads the driver. My Motherboard is M2V-Mx from Asus and once the /etc/default/grub is fixed with GRUB_CMDLINE_LINUX="vga=791" or 771 it's okay. (sudo update-grub of course) I recently junked my Nvidia 8500GT video because the driver for that became sick, the worst feature was not being able to display the layout of the pcb tool unless I disabled the driver and used cpu sw rendering on the video but that's an other story. Ian. -- You are receiving this mail because: You are watching the assignee of the bug.

1 5

[Bug 80684] New: I2C-over-AUX drops single bytes
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=80684 Priority: medium Bug ID: 80684 Assignee: dri-devel(a)lists.freedesktop.org Summary: I2C-over-AUX drops single bytes Severity: normal Classification: Unclassified OS: All Reporter: stefan.bruens(a)rwth-aachen.de Hardware: Other Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI I get frequent errors for the EDID checksum, obviously single bytes are dropped from the EDID. Good EDID: Raw EDID: 02 03 1d f1 50 90 05 04 03 02 07 16 01 06 11 12 15 13 14 1f 20 23 09 7f 07 83 01 00 00 02 3a 80 18 71 38 2d 40 58 2c 25 00 55 50 21 00 00 1e 01 1d 80 18 71 1c 16 20 58 2c 25 00 55 50 21 00 00 <-- 9e 01 1d 00 72 51 d0 1e 20 6e 28 55 00 55 50 21 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 55 50 21 00 00 18 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5d Bad EDID example: Raw EDID: 02 03 1d f1 50 90 05 04 03 02 07 16 01 06 11 12 15 13 14 1f 20 23 09 7f 07 83 01 00 00 02 3a 80 18 71 38 2d 40 58 2c 25 00 55 50 21 00 00 1e 01 1d 80 18 1c 16 20 58 2c 25 00 55 50 21 00 00 9e <-- 0x71 is missing 01 1d 00 72 51 d0 1e 20 6e 28 55 00 55 50 21 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 55 50 21 00 00 18 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5d 00 The position of the dropped byte changes, sometimes the EDID is complete, sometimes several bytes are dropped. The bad EDIDs are *often* accompanied with [drm:radeon_process_aux_ch] dp_aux_ch flags not zero messages. Most probably the common i2c-over-aux code drops the byte, as it starts the transfer again in case of -EBUSY. If I change radeon_process_aux_ch to return -EIO in case of (ReplyStatus == 2), I no longer have any bad checksums. Hardware is Radeon 7750 + Dell U2713HM, connected via DP. Same monitor with Intel Haswell and different cable works without any errors. Kernel is 3.15.1, i.e. without the i2c bus mutex, dont know if this fixes the problems as well. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[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 80531] New: 3.16-rc2 hdmi output resolution out of range Cape Verde PRO [Radeon HD 7750]
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=80531 Priority: medium Bug ID: 80531 Assignee: dri-devel(a)lists.freedesktop.org Summary: 3.16-rc2 hdmi output resolution out of range Cape Verde PRO [Radeon HD 7750] Severity: normal Classification: Unclassified OS: Linux (All) Reporter: fredrik(a)obra.se Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 101759 --> https://bugs.freedesktop.org/attachment.cgi?id=101759&action=edit dmesg with drm.debug=1 With 3.16-rc2 my tripple screen setup breaks. DisplayPort-0 connected 1920x1200 <- ok HDMI-0 connected 1920x1080 <- (tv) resolution out of range DVI-0 connected 1680x1050 <- ok All screens work during bootup before X starts. ddx driver 7.3.0. -- You are receiving this mail because: You are the assignee for the bug.

1 14

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2014