dri-devel January 2016

dri-devel@lists.freedesktop.org

194 participants
1200 discussions

[Bug 68527] New: Planetary Annihilation Alpha: translation from TGSI failed !
by bugzilla-daemon＠freedesktop.org 04 Jul '19

04 Jul '19

https://bugs.freedesktop.org/show_bug.cgi?id=68527 Priority: medium Bug ID: 68527 Assignee: dri-devel(a)lists.freedesktop.org Summary: Planetary Annihilation Alpha: translation from TGSI failed ! Severity: normal Classification: Unclassified OS: Linux (All) Reporter: sxx.public(a)yahoo.com Hardware: x86-64 (AMD64) Status: NEW Version: 9.2 Component: Drivers/Gallium/r600 Product: Mesa I test this game on my AMD HD6950 and Intel HD3000 both using latest Mesa 9.2. Problem with sun shader only occur with R600g. I can also notice that sun shader inside game based on this demo (which is working fine with R600): https://github.com/ashima/webgl-noise OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD CAYMAN OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.0-devel OpenGL core profile shading language version string: 1.40 -- You are receiving this mail because: You are the assignee for the bug.

1 26

[Bug 37471] New: Website with information about maintainers/developers
by bugzilla-daemon＠freedesktop.org 29 May '19

29 May '19

https://bugs.freedesktop.org/show_bug.cgi?id=37471 Summary: Website with information about maintainers/developers Product: DRI Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: johannesobermayr(a)gmx.de There should be a website with information about main developers/maintainers: Product (DRM Intel, DRM Radeon, Mesa) | Component[s] (Maintainer, Core developer, Intel, R200, R300, R600, nouveau, ...) | Real Name | eMail | Name on IRC | Usual time to ask (e.g. 17 to 20 UTC) | Available on IRC channels (#dri-devel, #nouveau, ...) | Working for [Red Hat, SUSE, Linux Foundation, Ubuntu, ...] -- 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 86351] New: HDMI audio garbled output on Radeon R9 280X
by bugzilla-daemon＠bugzilla.kernel.org 23 Mar '19

23 Mar '19

https://bugzilla.kernel.org/show_bug.cgi?id=86351 Bug ID: 86351 Summary: HDMI audio garbled output on Radeon R9 280X Product: Drivers Version: 2.5 Kernel Version: 3.17 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: joker(a)netswarm.net Regression: No Created attachment 153891 --> https://bugzilla.kernel.org/attachment.cgi?id=153891&action=edit dmesg output Any sound played back over HDMI results in garbled audio output. When playing audio at 24000hz or below (19200Hz also tested) playback starts to work normaly without the constant choppyness. What also works is 44100Hz in Mono. It behaves like a data bandwith issue that kicks in above 24000hz Stereo or 44100Hz Mono. All test are done directly talking to the alsa device. This means no pulseaudio or dmix or similar processing. "plughw" had to be used because the hardware does not allow low rates like 24000. During all Test a perfectly fine and stable 1080p image is displayed over HDMI. (No dropouts at all). This hardware setup has also be successfully tested using Windows. (Incl. Multi channel PCM 6.0 for lot's of audio bandwidth) Working Audio Tests: -------------------- speaker-test -r 24000 -c2 speaker-test -r 24000 -c6 (multi channel PCM works too) mpg123 -r 24000 <file> mpg123 -m -r 44100 <file> The peer format detection is pcm 2.0 44100 or 48000 here. It appears the format link doesn't matter, only the actual data bandwidth that's being used) Garbled Audio Tests: -------------------- speaker-test -r 48000 -c2 speaker-test -r 48000 -c6 mpg123 -r 44100 <file> All passthru formats (dts, dolby d, pcm multi channel) get detected my the destination, but after a short period it loses the link and tries to resync. What previously also worked is a HD5570 in the same system which i no longer have access to though. Not sure about the kernel used back then. -- You are receiving this mail because: You are watching the assignee of the bug.

1 35

[Bug 88501] New: AMD/ATI RS690M Console blanks to white
by bugzilla-daemon＠bugzilla.kernel.org 05 Mar '19

05 Mar '19

https://bugzilla.kernel.org/show_bug.cgi?id=88501 Bug ID: 88501 Summary: AMD/ATI RS690M Console blanks to white Product: Drivers Version: 2.5 Kernel Version: 3.6.0-rc5 to 3.18.0-rc4 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: business.kid(a)gmail.com Regression: Yes Created attachment 158181 --> https://bugzilla.kernel.org/attachment.cgi?id=158181&action=edit Git Bisect log, & git visualise o/p Without X running, linux consoles blank after a period adjustable by setterm. Mine does not. It goes white. If I invert the screen colours, it goes whiter. Backlight? I cloned the Linus-stable git and tried it. 3.18.0-rc4 twists this slightly - The FIRST time the screen blanks, it does so correctly; every other time, it blanks to white. I'm a hardware guy, not a software expert. Git bisect gives the output below. Details of the box also attached The box is a HP 6715S, twin core Turion, 3G ram. It's running Slackware-current as of Sept 30th, 2014. LSPCI output attached. Bios Version: ATI 02/13/08,1. -- You are receiving this mail because: You are watching the assignee of the bug.

1 11

[Bug 60623] New: White Screen on boot with radeon.dpm=1
by bugzilla-daemon＠bugzilla.kernel.org 05 Mar '19

05 Mar '19

https://bugzilla.kernel.org/show_bug.cgi?id=60623 Bug ID: 60623 Summary: White Screen on boot with radeon.dpm=1 Product: Drivers Version: 2.5 Kernel Version: 3.11.0-999-generic Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: blocking Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: electrobs(a)gmail.com Regression: No Using the latest ubuntu built kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/, and enabling the boot option of radeon.dpm=1 . Results in a black screen after grub that eventually turns white gradually. Removing the option allows the laptop to function perfectly with the AMD 3650 video card. Hardware: -Lenovo T500 with AMD 3650 and a Intel 4500MHD switchable graphics off. -more info at http://support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-71785 Software: -clean install of Kubuntu 13.04 with beta ppa enabled for KDE 4.11 rc2 -xorg-edgers ppa enabled -- You are receiving this mail because: You are watching the assignee of the bug.

1 2

[Bug 91110] Textures missing iff character in specific areas in dolphin running Xenoblades Chronicles
by bugzilla-daemon＠freedesktop.org 17 Feb '19

17 Feb '19

https://bugs.freedesktop.org/show_bug.cgi?id=91110 Bug ID: 91110 Summary: Textures missing iff character in specific areas in dolphin running Xenoblades Chronicles Product: Mesa Version: git Hardware: x86-64 (AMD64) URL: https://code.google.com/p/dolphin-emu/issues/detail?id =8688 OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: christian(a)madez.de QA Contact: dri-devel(a)lists.freedesktop.org Iff a character is in specific areas some textures on him are not rendered. In the entry of colony 9 is such an area. The textures are rendered properly on the Intel GPU. There are screenshots, a fifolog and an apitrace at the end of the linked bugreport. The problem appears in Debian Jessie, Sid and mesa-git the last time checked, which was 9 days ago. I compiled mesa-git with CFLAGS = -g -O2 -Wall -std=c99 -Werror=implicit-function-declaration -Werror=missing-prototypes -fno-strict-aliasing -fno-builtin-memcmp -DDEBUG and set $ export LIBGL_DEBUG=verbose $ export MESA_DEBUG=1 $ export EGL_LOG_LEVEL=debug before running dolphin. Running dolphin with the game until the issue appears gives the following output $ dolphin-emu Gtk-Message: Failed to load module "canberra-gtk-module" libGL: screen 0 does not appear to be DRI3 capable libGL: pci id for fd 22: 1002:679a, driver radeonsi libGL: OpenDriver: trying lib/tls/radeonsi_dri.so libGL: OpenDriver: trying lib/radeonsi_dri.so libGL: Can't open configuration file /home/user/.drirc: Arquivo ou diretório não encontrado. libGL: Can't open configuration file /home/user/.drirc: Arquivo ou diretório não encontrado. libGL: Using DRI2 for screen 0 I'm sorry, I don't know how to write a simple GLUT-based test program. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 93747] Proprietary game Minecraft fails to enter fullscreen
by bugzilla-daemon＠freedesktop.org 17 Feb '19

17 Feb '19

https://bugs.freedesktop.org/show_bug.cgi?id=93747 Bug ID: 93747 Summary: Proprietary game Minecraft fails to enter fullscreen Product: Mesa Version: unspecified 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: andre35822(a)yahoo.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 121095 --> https://bugs.freedesktop.org/attachment.cgi?id=121095&action=edit dmesg output when opening the game and trying to set it in fullscreen I am on Arch Linux with Mesa 11.1, Kernel 4.3.3, llvm 3.7.1-1 and have an AMD 7950. The issue that is occurring is that Minecraft is failing to enter fullscreen with multiple DEs (Openbox, XFCE, and Cinnamon are the ones that I have tried, and all do not properly enter fullscreen). When I hit the fullscreen option in the game, the window sort of turns completely transparent or sometimes the theme of my desktop environment but I can not see anything. I can hear sounds from the game and clicking/pressing keyboard buttons are actually working in the game so it is as if the game is working fine just it is not rendering the window correctly. (I can hear myself breaking blocks). If I quit the game in this state and re-open it, the game will launch in fullscreen, but if I alt-tab or set it back to window mode and try to enter fullscreen mode, the same that I stated above occurs. I would like to note that I am using OpenJRE and not Sun Java's though someone with an AMD GPU and Sun java stated they experience the same issue. So I really think it is down to a mesa bug or something? I am not sure how it works. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[BUG/REGRESSION] Radeon HDMI casuses oops on Acube Sam460ex amcc 460ex power board
by Julian Margetson 03 Jan '19

03 Jan '19

Kernels 4.03 and 4.04 oops with HDMI connection on Acube Sam460ex amcc 460ex powerpc board. 016a255b7835ee7e49a3eba3c14ba0bc0221a4f8 is the first bad commit commit 016a255b7835ee7e49a3eba3c14ba0bc0221a4f8 Author: Alex Deucher <alexander.deucher(a)amd.com> Date: Tue Apr 7 09:52:42 2015 -0400 drm/radeon: only mark audio as connected if the monitor supports it (v3) commit 0f55db36d49d45b80eff0c0a2a498766016f458b upstream. Otherwise the driver may try and send audio which may confuse the monitor. v2: set pin to NULL if no audio v3: avoid crash with analog encoders Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> :040000 040000 de0366a6790f5c91d175bcb89cb34956bbe72b26 bbdb5734961f824558152c7c34a840c78bc3a9a9 M drivers [ 2.587570] Linux agpgart interface v0.103 [ 2.591997] [drm] Initialized drm 1.1.0 20060810 [ 2.596892] [drm] radeon kernel modesetting enabled. [ 2.602989] [drm] initializing kernel modesetting (VERDE 0x1002:0x683F 0x1545:0x7750). [ 2.611161] [drm] register mmio base: 0xe90000000 [ 2.615935] [drm] register mmio size: 262144 [ 2.952043] ATOM BIOS: C44501 [ 2.955323] radeon 0001:81:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used) [ 2.964253] radeon 0001:81:00.0: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF [ 2.971938] [drm] Detected VRAM RAM=1024M, BAR=256M [ 2.976840] [drm] RAM width 128bits DDR [ 2.980898] [TTM] Zone kernel: Available graphics memory: 379358 kiB [ 2.987383] [TTM] Zone highmem: Available graphics memory: 1034718 kiB [ 2.993934] [TTM] Initializing pool allocator [ 2.998331] [TTM] Initializing DMA pool allocator [ 3.003153] [drm] radeon: 1024M of VRAM memory ready [ 3.008162] [drm] radeon: 1024M of GTT memory ready. [ 3.013203] [drm] Loading verde Microcode [ 3.017266] [drm] Internal thermal controller with fan control [ 3.023437] [drm] probing gen 2 caps for device aaa1:bed1 = 18cc41/0 [ 3.077284] [drm] radeon: dpm initialized [ 3.081503] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 3.093142] [drm] probing gen 2 caps for device aaa1:bed1 = 18cc41/0 [ 3.125984] [drm] PCIE GART of 1024M enabled (table at 0x0000000000277000). [ 3.133327] radeon 0001:81:00.0: WB enabled [ 3.137565] radeon 0001:81:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffc01c00 [ 3.147697] radeon 0001:81:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffc01c04 [ 3.157827] radeon 0001:81:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffc01c08 [ 3.167957] radeon 0001:81:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffc01c0c [ 3.178078] radeon 0001:81:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffc01c10 [ 3.209673] radeon 0001:81:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xf90b5a18 [ 3.219822] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 3.226457] [drm] Driver supports precise vblank timestamp query. [ 3.232584] radeon 0001:81:00.0: radeon: MSI limited to 32-bit [ 3.238466] ppc4xx_setup_msi_irqs: fail allocating msi interrupt [ 3.244586] [drm] radeon: irq initialized. [ 4.006339] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD) [ 4.015198] radeon 0001:81:00.0: disabling GPU acceleration [ 4.220071] [drm] Radeon Display Connectors [ 4.224651] [drm] Connector 0: [ 4.227787] [drm] HDMI-A-1 [ 4.230754] [drm] HPD4 [ 4.233328] [drm] DDC: 0x6570 0x6570 0x6574 0x6574 0x6578 0x6578 0x657c 0x657c [ 4.240806] [drm] Encoders: [ 4.243815] [drm] DFP1: INTERNAL_UNIPHY2 [ 4.248131] [drm] Connector 1: [ 4.251227] [drm] DVI-I-1 [ 4.254051] [drm] HPD2 [ 4.256608] [drm] DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 0x656c [ 4.264034] [drm] Encoders: [ 4.267021] [drm] DFP2: INTERNAL_UNIPHY [ 4.271223] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 4.390562] [drm] fb mappable at 0x80478000 [ 4.394789] [drm] vram apper at 0x80000000 [ 4.398905] [drm] size 8294400 [ 4.401978] [drm] fb depth is 24 [ 4.405225] [drm] pitch is 7680 [ 4.700581] Console: switching to colour frame buffer device 240x67 [ 4.779669] radeon 0001:81:00.0: fb0: radeondrmfb frame buffer device [ 4.786489] radeon 0001:81:00.0: registered panic notifier [ 4.796803] [drm] Initialized radeon 2.41.0 20080528 for 0001:81:00.0 on minor 0 [ 31.191562] Unable to handle kernel paging request for data at address 0x00000008 [ 31.258832] Faulting instruction address: 0xc04a51bc [ 34.049506] Oops: Kernel access of bad area, sig: 11 [#1] [ 34.055246] PREEMPT Canyonlands [ 34.058586] Modules linked in: [ 34.061830] CPU: 0 PID: 1998 Comm: Xorg Not tainted 4.0.3-Sam460ex #2 [ 34.068633] task: edee4c60 ti: ede8a000 task.ti: ede8a000 [ 34.074334] NIP: c04a51bc LR: c04a546c CTR: c03e5050 [ 34.079578] REGS: ede8bc30 TRAP: 0300 Not tainted (4.0.3-Sam460ex) [ 34.086381] MSR: 00029000 <CE,EE,ME> CR: 20004422 XER: 00000000 [ 34.092944] DEAR: 00000008 ESR: 00000000 GPR00: c04a5438 ede8bce0 edee4c60 eea84000 00000000 00000000 c0710000 00000000 GPR08: 00000000 00000000 eeac0400 ede8bce0 20004444 b7a55afc b80efab0 b80ee530 GPR16: 00000000 ffffffff 6f23c730 ede8be18 c03add44 eeac0578 00000001 00004000 GPR24: 00004000 c0719b98 fffffff2 00000001 eeb61200 eea84000 eea8df00 00000000 [ 34.127485] NIP [c04a51bc] radeon_audio_enable+0x4/0x18 [ 34.133000] LR [c04a546c] radeon_audio_detect+0xd4/0x104 [ 34.138604] Call Trace: [ 34.141185] [ede8bce0] [c04a5438] radeon_audio_detect+0xa0/0x104 (unreliable) [ 34.148771] [ede8bd00] [c03e6958] radeon_dvi_detect+0x390/0x3b4 [ 34.155046] [ede8bd30] [c0391cec] drm_helper_probe_single_connector_modes_merge_bits+0xf4/0x448 [ 34.164253] [ede8bd70] [c03ade28] drm_mode_getconnector+0xe4/0x334 [ 34.170796] [ede8be10] [c03a0be8] drm_ioctl+0x348/0x464 [ 34.176343] [ede8bed0] [c00ce2e8] do_vfs_ioctl+0x52c/0x6e8 [ 34.182158] [ede8bf20] [c00ce4e4] SyS_ioctl+0x40/0x68 [ 34.187515] [ede8bf40] [c000ab1c] ret_from_syscall+0x0/0x3c [ 34.193417] --- interrupt: c01 at 0x6fb001dc [ 34.193417] LR = 0x6fb00100 [ 34.201216] Instruction dump: [ 34.204368] 8129012c 806a0018 2f890000 419e0018 81290004 2f890000 419e000c 7d2903a6 [ 34.212674] 4e800420 38600000 4e800020 81231cd8 <81290008> 2f890000 4d9e0020 7d2903a6 [ 34.376219] ---[ end trace 803e15e46b991816 ]--- [ 34.380843] * Starting Mount filesystems on boot[ OK ] *

6 26

[Bug 105111] New: amdgpu 0000:00:01.0: Invalid ROM contents (with A8-7600)
by bugzilla-daemon＠bugzilla.kernel.org 05 Dec '18

05 Dec '18

https://bugzilla.kernel.org/show_bug.cgi?id=105111 Bug ID: 105111 Summary: amdgpu 0000:00:01.0: Invalid ROM contents (with A8-7600) Product: Drivers Version: 2.5 Kernel Version: 4.3.0-rc3 Hardware: IA-64 OS: Linux Tree: Mainline Status: NEW Severity: blocking Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: fin4478(a)hotmail.com Regression: No Created attachment 188721 --> https://bugzilla.kernel.org/attachment.cgi?id=188721&action=edit dmesg output amdgpu fails to find bios rom in Amd A8-7600 system. The following is a dmesg capture after booting to linux rescue mode: [ 1.629958] [drm] amdgpu kernel modesetting enabled. [ 1.630360] [drm] initializing kernel modesetting (KAVERI 0x1002:0x1313 0x1043:0x85CB 0x00). [ 1.630410] [drm] register mmio base: 0xFEB00000 [ 1.630445] [drm] register mmio size: 262144 [ 1.630487] [drm] doorbell mmio base: 0xF0000000 [ 1.630523] [drm] doorbell mmio size: 8388608 [ 1.630582] amdgpu 0000:00:01.0: Invalid ROM contents [ 1.630652] [drm:amdgpu_get_bios [amdgpu]] *ERROR* Unable to locate a BIOS ROM [ 1.630695] amdgpu 0000:00:01.0: Fatal error during GPU init [ 1.630732] [drm] amdgpu: finishing device. [ 1.630767] [TTM] Memory type 2 has not been initialized [ 1.632024] amdgpu: probe of 0000:00:01.0 failed with error -22 Problematic code is in the file: drivers/gpu/drm/amd/amdgpu/amdgpu_bios.c -- You are receiving this mail because: You are watching the assignee of the bug.

1 9

[Bug 85791] New: nouveau: errors on boot, can't use discrete gpu
by bugzilla-daemon＠bugzilla.kernel.org 03 Dec '18

03 Dec '18

https://bugzilla.kernel.org/show_bug.cgi?id=85791 Bug ID: 85791 Summary: nouveau: errors on boot, can't use discrete gpu Product: Drivers Version: 2.5 Kernel Version: 3.16.4, 3.14.20 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: mezin.alexander(a)gmail.com Regression: No Created attachment 152791 --> https://bugzilla.kernel.org/attachment.cgi?id=152791&action=edit dmesg On boot I see these errors: [ 18.929898] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000002 FAULT at 0x4188ac [ IBUS ] [ 18.931250] nouveau E[ DRM] Pointer to TMDS table invalid [ 18.932395] nouveau E[ DRM] Pointer to flat panel table invalid [ 22.798349] nouveau E[ PGRAPH][0000:01:00.0] HUB_INIT timed out [ 22.798360] nouveau E[ PGRAPH][0000:01:00.0] 409000 - done 0x00000220 [ 22.798373] nouveau E[ PGRAPH][0000:01:00.0] 409000 - stat 0x00000000 0x00000000 0x00000000 0x00000000 [ 22.798384] nouveau E[ PGRAPH][0000:01:00.0] 409000 - stat 0x00000000 0x00000000 0x00000006 0x00000001 [ 22.798389] nouveau E[ PGRAPH][0000:01:00.0] 502000 - done 0x00000300 [ 22.798397] nouveau E[ PGRAPH][0000:01:00.0] 502000 - stat 0x00000000 0x00008c00 0x00000000 0x00000000 [ 22.798404] nouveau E[ PGRAPH][0000:01:00.0] 502000 - stat 0x00000000 0x00000000 0x00000000 0x00000000 [ 22.798406] nouveau E[ PGRAPH][0000:01:00.0] init failed, -16 Full dmesg is attached. When I try to use discrete gpu with DRI_PRIME=1 (after xrandr --setprovideroffloadsink), X crashes. Hardware: 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 01:00.0 3D controller: NVIDIA Corporation GK107M [GeForce GT 750M] (rev a1) Acer Aspire V5-573G If I remember correctly, some time ago everything worked. -- You are receiving this mail because: You are watching the assignee of the bug.

1 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2016