dri-devel January 2016

dri-devel@lists.freedesktop.org

194 participants
1200 discussions

[Bug 28000] New: [Mobile GM965/GL96][Wine][3D] Display and textures corrupted in Warhammer 40k Soulstorm
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=28000 Summary: [Mobile GM965/GL96][Wine][3D] Display and textures corrupted in Warhammer 40k Soulstorm Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: fdelente(a)mail.cpod.fr Created an attachment (id=35465) --> (https://bugs.freedesktop.org/attachment.cgi?id=35465) Xorg.0.log $ lspci 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) $ uname -m i686 $ uname -a Linux slick 2.6.32.3-smp #7 SMP PREEMPT Tue Apr 6 19:10:03 CEST 2010 i686 Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz GenuineIntel GNU/Linux -- xf86-video-intel/xserver/mesa/libdrm version: xf86-video-intel-2.11.0-i386-1 xorg-server-1.8.0-i386-1 Mesa-7.8.1-i386-1 libdrm-2.4.20-i386-1 -- kernel version: ("uname -r") 2.6.32.3-smp -- Linux distribution: Slackware 13.0 initially, but I recompiled many packages from source -- Machine or mobo model: Packard Bell BG46 fr -- Display connector: (e.g. VGA, DVI, HDMI, S-video, ...) VGA? LCD panel 3) Reproduce steps. Probability if not 100% reproducible. 100% reproducible: when starting Soulstorm, some bitmaps and 3D textures are corrupted. The same game works flawlessly on another computer with an Nvidia card. 4) Attachment: -- Xorg.0.log -- dmesg output (better with boot option "drm.debug=0x06") -- xorg.conf (if you changed any default options) No change there -- screenshot or photo (optional, a picture is worth a thousand words) -- output of "xrandr --verbose" for display mode issue -- intel_reg_dumper output (see the guide) for display issue. -- for GPU hang, get the last batch buffer (see the guide). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 12

[Bug 76559] New: screen corruption after going from VT to X
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=76559 Priority: medium Bug ID: 76559 Assignee: dri-devel(a)lists.freedesktop.org Summary: screen corruption after going from VT to X Severity: normal Classification: Unclassified OS: Linux (All) Reporter: fabio.ped(a)libero.it Hardware: x86 (IA32) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI I have a MacBook Pro with a RV530 with an external Philips 22" monitor connected (the notebook screen is disabled in X). After switching to VT and then coming back to X the screen is corrupted (like if every odd line has an offset). The same happens after suspend. A screenshot doesn't show the problem. I then usually change resolution with the Ubuntu tool (selecting a different resolution and then reapplying the previous one) and that restore the screen. Attached dmesg and Xorg log after the X -> VT -> X cycle. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 89871] nouveau diver in kernel 3.5.7 - 4.0.0-rc6 on PPC broken
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=89871 Bug ID: 89871 Summary: nouveau diver in kernel 3.5.7 - 4.0.0-rc6 on PPC broken Product: DRI Version: XOrg git Hardware: PowerPC OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/other Assignee: dri-devel(a)lists.freedesktop.org Reporter: marvin(a)mydatex.cz Created attachment 114825 --> https://bugs.freedesktop.org/attachment.cgi?id=114825&action=edit dmesg output 3.19.3 I have PowerMac G5 machine with dual PPC. On Debian wheezy Xserver works. I upgrade to jessie with kernel 3.16 and Xserver stop working. I tested these kernels: vmlinux-3.4.106 vmlinux-3.5.7 vmlinux-3.7.9 vmlinux-3.8.13 vmlinux-3.14.37 vmlinux-3.17.8 vmlinux-3.18.10 vmlinux-3.19.3 vmlinux-4.0.0-rc6 It looks like that between 3.5.7 and 3.8.13 something change and DRM part of nouveau diver and driver stop working: I tested above kernels and problem is the same this dmesg output is from 3.19.3 [drm] Initialized drm 1.1.0 20060810 [ 10.548060] checking generic (98020000 10e000) vs hw (98000000 8000000) [ 10.548066] fb: switching to nouveaufb from OFfb NVDA,Displ [ 10.555299] Console: switching to colour dummy device 80x25 [ 10.557295] nouveau [ DEVICE][0000:0a:00.0] BOOT0 : 0x043200a4 [ 10.557310] nouveau [ DEVICE][0000:0a:00.0] Chipset: NV43 (NV43) [ 10.557316] nouveau [ DEVICE][0000:0a:00.0] Family : NV40 [ 10.557567] nouveau ![ VBIOS][0000:0a:00.0] unable to locate usable image [ 10.557575] nouveau E[ DEVICE][0000:0a:00.0] failed to create 0x10000001, -22 [ 10.557584] nouveau E[ DRM] failed to create 0x00000080, -22 [ 10.558138] nouveau: probe of 0000:0a:00.0 failed with error -22 With older kernel < 3.7.9 nouveau kernel part works but newer Xorg from jessie doesn't detect videocard. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 90079] drmSetMaster and drmDropMaster need root privileges
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=90079 Bug ID: 90079 Summary: drmSetMaster and drmDropMaster need root privileges Product: DRI Version: unspecified Hardware: All OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: libdrm Assignee: dri-devel(a)lists.freedesktop.org Reporter: g1938560(a)trbvm.com I run a small, user-space program that renders images in my virtual console with drmModeSetCRTC and family. I also support virtual terminal switching with ioctl() on stuff from linux/vt.h and some basic signal handling. Switching back to X server, however, just renders... nothing. Apparently I'm supposed to call drmDropMaster so that X server can pick up from there. I get -1 and errno is set to Permission Denied. When run as root, it works as expected. Is there any reason why these functions require root privileges? More importantly, is there any workaround for this so that my user space program can let X server draw its stuff once user switches back to X's virtual terminal? -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 80683] New: EDID valid check ignores errors in CEA blocks
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=80683 Priority: medium Bug ID: 80683 Assignee: dri-devel(a)lists.freedesktop.org Summary: EDID valid check ignores errors in CEA blocks Severity: normal Classification: Unclassified OS: All Reporter: stefan.bruens(a)rwth-aachen.de Hardware: Other Status: NEW Version: DRI CVS Component: DRM/other Product: DRI in linux/drivers/gpu/drm/drm_edid.c: bool drm_edid_block_valid(u8 *raw_edid, int block, bool print_bad_edid) { ... if (csum) { if (print_bad_edid) { DRM_ERROR("EDID checksum is invalid, remainder is %d\n", csum); } /* allow CEA to slide through, switches mangle this */ if (raw_edid[0] != 0x02) goto bad; } ... return true; --- i.e. CEA blocks are always reported as valid. This occurs frequently for me with a Radeon 7750 and a Dell U2713HM connected via DisplayPort, the I2C-over-AUX seems to be buggy and swallows single bytes. If I change the "return true;" to "return !csum;" bad transfers are retried. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 73624] New: AST2300 KMS EDID issue on C2750D4I
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=73624 Priority: medium Bug ID: 73624 Assignee: dri-devel(a)lists.freedesktop.org Summary: AST2300 KMS EDID issue on C2750D4I Severity: normal Classification: Unclassified OS: All Reporter: johannesobermayr(a)gmx.de Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/other Product: DRI Created attachment 92079 --> https://bugs.freedesktop.org/attachment.cgi?id=92079&action=edit EDID issue with KMS AST2300 doesn't fetch right EDID data ... [ 10.599714] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 73 [ 10.599718] Raw EDID: [ 10.599721] 00 ff ff ff ff ff ff 00 09 d1 0b 79 45 54 00 00 [ 10.599723] 29 12 01 03 0e 2f 1a 78 2e 35 85 a6 56 48 9a 24 [ 10.599725] 12 50 54 a5 6b ba 71 00 81 0d 00 00 00 00 00 00 [ 10.599727] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 10.599729] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 10.599731] 00 00 00 00 00 00 00 00 00 00 00 00 02 01 ff ff [ 10.599733] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.599734] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 89549] DisplayLink (udl) Linux kernel memory fault on USB hot unplug, proposed patch
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=89549 Bug ID: 89549 Summary: DisplayLink (udl) Linux kernel memory fault on USB hot unplug, proposed patch Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/other Assignee: dri-devel(a)lists.freedesktop.org Reporter: adam_richter2004(a)yahoo.com Created attachment 114235 --> https://bugs.freedesktop.org/attachment.cgi?id=114235&action=edit Add ".get_vblank_counter = drm_vblank_count," to DisplayLink drm_driver functions [This is an edit of an email that I sent yesterday to linux-fbdev at vger.kernel.org and the Linux kernel udlfb maintainer.] In Linux-4.0-rc3, the DisplayLink driver gets a kernel memory fault when its USB device is unplugged, specifically when vblank_disable_and_save in linux-4.0-rc3/drivers/gpu/drm/drm_irq.c attempts to call the NULL function pointer dev->driver_get_vblank_counter. linux-4.0-rc3/Documentation/DocBook/drm.tmpl says of that field, "Otherwise drivers can use the drm_vblank_count helper function to handle this operation." Trying that seems to have eliminated the oops when I unplug the device, although I do see these lines in the console log at device driver initialization time that I think are probably fine, but which I should mention in case the indicate that I did the wrong the thing: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] No driver support for vblank timestamp query. If that doesn't look like a problem, then please apply the attached patch and push it upstream. The patch just adds one line that appears in six other framebuffer drivers to initialize the driver_get_vblank_counter drm_driver function. Thanks in advance for your attention to this problem. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 28841] New: Heavy text corruption in virtual consoles using DRI
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=28841 Summary: Heavy text corruption in virtual consoles using DRI Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: eblanca76(a)users.sourceforge.net I have a clean install of latest ubuntu lucid lynx, I added framebuffer support for g550 (matroxfb) and text in virtual consoles appears corrupted, it is made of random pixels appearing far away from the expected prompt. I can get back to clean text if I switch to xorg (ctrl+f7) then back to the virtual console, but if I type in new text, it appears ugly as usual. The only workaround for this is to disable DRI, then the text appears perfect and no switch is needed. Of course, this way the system cannot support any game. I attach my actual xorg.conf. My config: ubuntu 10.04 (Lucid) 2.6.32-22-generic i686 GNU/Linux with gnome 2.30.2 and xorg X server 1.7.6. -- 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 48215] New: [NV11] Display constantly switches on and off roughly every 10 seconds.
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=48215 Bug #: 48215 Summary: [NV11] Display constantly switches on and off roughly every 10 seconds. Classification: Unclassified Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/other AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: alex.buell(a)munted.org.uk Display constantly switches on and off roughly every 10 seconds on my NV11 machine. This started happening with 3.2.0. Checking backwards, 3.1.0 works just fine. I am currently trying a bisect to find the problem. -- 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 52560] New: Xorg -configure creats useless xorg.conf for tdfx
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=52560 Bug #: 52560 Summary: Xorg -configure creats useless xorg.conf for tdfx Classification: Unclassified Product: DRI Version: XOrg CVS Platform: All OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/other AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: tuxracer(a)hispeed.ch Had want to install my old Voodoo3/2000 PCI that 2 or 3 years ago perfectly work. Now on actual xorg-server at least 1.10 1.11 1.12 I really unable to configure a working 3D. If i use the driver without any xorg.conf I can use at least Software-Rendering. But if i create a xorg.conf using Xorg -configure it gives no 3D. On old xorg-servers the only thing i had to do for 3D on this card was to set the resolution to 1024x768 at 16bit colordepth and it worked. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2016