dri-devel May 2015

dri-devel@lists.freedesktop.org

191 participants
1132 discussions

[Bug 46866] New: Piglit:Multiple failures observed while running quick-driver.tests
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=46866 Bug #: 46866 Summary: Piglit:Multiple failures observed while running quick-driver.tests Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: hysvats(a)gmail.com Driver Stack Details: ========================= 1) Kernel-3.0.0-12-generice-pae 2) drm-2.4.31 3) Mesa-8.1-devel (git-897af1d) 4) Xorg-server-1.11.4 5) xf86-video-ati- master System Environment: =================== Asic : EG CedarPro O.S. : Ubuntu-11.10 (32 bit) Processor : AMD Athlon(tm) 64 X2 @ 1 GHz Memory : 2 GB Steps to Reproduce: =================== 1) Install piglit from git clone git://anongit.freedesktop.org/git/piglit 2) #./piglit-run.py tests/quick-driver.tests results/quick-driver.results #./piglit-summary-html.py summary/quick-driver results/quick-driver.results Observation : Multiple failures observed while running quick-driver.tests =========== -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

[Bug 28943] New: Red=cyan? Why?
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=28943 Summary: Red=cyan? Why? Product: Mesa Version: unspecified Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/MGA AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: eblanca76(a)users.sourceforge.net I'm having a strange color replacement in ubuntu 10.04. Hardware is matrox g550 agp dual head, 32 MB. Well, running silent hill 2 in wine, I have cyan blood when it should be red! Here you can read the (closed) bug: http://bugs.winehq.org/show_bug.cgi?id=17741 (there are a lot of details about the bug) I thought it was due to wine but it isn't, so it was closed as invalid. Please note, this `bug' appears since a couple of years ago and even now, with mesa 7.7.1. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 1

[Bug 80678] New: xrandr scaling / transform does not work with radeon
by bugzilla-daemon＠freedesktop.org 25 Feb '16

25 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=80678 Priority: medium Bug ID: 80678 Assignee: dri-devel(a)lists.freedesktop.org Summary: xrandr scaling / transform does not work with radeon Severity: normal Classification: Unclassified OS: Linux (All) Reporter: h.judt(a)gmx.at Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Scaling doesn't work with radeon. Screen rotation does work, though. On a laptop with intel driver, the following works fine, except the mouse pointer is confined to the mode area, but I believe that is a known xorg-server bug to which a patch is available in bug #39949: xrandr --fb 1920x1080 --output eDP1 --mode 1600x900 --scale-from 1920x1080 The same command, adapted to the radeon output device doesn't work. Same software configuration (xorg-1.15.99.903, libdrm-git, mesa-git, xf86-video-ati-git, various kernel versions (at the moment 3.15.2)). lspci -vvv: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 0b00 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 41 Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at f7e20000 (64-bit, non-prefetchable) [size=128K] Region 4: I/O ports at e000 [size=256] Expansion ROM at f7e00000 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee0100c Data: 4191 Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Kernel driver in use: radeon Is scaling not implemented in radeon? -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 76321] New: Incorrect hwmon temperature when radeon card is turned off
by bugzilla-daemon＠bugzilla.kernel.org 20 Feb '16

20 Feb '16

https://bugzilla.kernel.org/show_bug.cgi?id=76321 Bug ID: 76321 Summary: Incorrect hwmon temperature when radeon card is turned off Product: Drivers Version: 2.5 Kernel Version: 3.15-rc3 Hardware: All 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: pali.rohar(a)gmail.com Regression: No When radeon card is turned off (automatically via runpm) sensors program show totally incorrect temperature: radeon-pci-0100 Adapter: PCI adapter temp1: +511.0°C (crit = +120.0°C, hyst = +90.0°C) When some opengl program is running with DRI_PRIME=1 then sensors reports: radeon-pci-0100 Adapter: PCI adapter temp1: +46.0°C (crit = +120.0°C, hyst = +90.0°C) So kernel radeon driver should not report temperature (e.g. returns -EINVAL in hwmon) when radeon card is turned off (via vgaswitcheroo or runpm). -- You are receiving this mail because: You are watching the assignee of the bug.

1 14

[Bug 66352] New: GPU lockup in L4D2 on TURKS with HyperZ
by bugzilla-daemon＠freedesktop.org 19 Feb '16

19 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=66352 Priority: medium Bug ID: 66352 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU lockup in L4D2 on TURKS with HyperZ Severity: normal Classification: Unclassified OS: FreeBSD Reporter: russianneuromancer(a)ya.ru Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 81668 --> https://bugs.freedesktop.org/attachment.cgi?id=81668&action=edit dmesg Lockup described in bug 64220 was happen right after campaign start (in first minute) but this lockup usually happen later - in first hour of playing. This lockup is not reproducible when HyperZ is disabled, so probably (like bug 64220) is related to HyperZ. [ 2160.750951] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec [ 2160.750966] radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000002525f last fence id 0x000000000002525c) [ 2160.786068] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000174118 and cpu addr 0xffffc9000681c118 [ 2160.787147] radeon 0000:01:00.0: Saved 183 dwords of commands on ring 0. [ 2160.787166] radeon 0000:01:00.0: GPU softreset: 0x00000019 [ 2160.787175] radeon 0000:01:00.0: GRBM_STATUS = 0xE7730CA0 [ 2160.787177] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xFC000001 [ 2160.787180] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 2160.787182] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 2160.787184] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 2160.787186] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x01000000 [ 2160.787189] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x000D1000 [ 2160.787191] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00068506 [ 2160.787193] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80878647 [ 2160.787196] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 2160.787356] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B [ 2160.787410] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 [ 2160.788559] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 [ 2160.788561] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [ 2160.788563] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 2160.788565] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 2160.788568] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 2160.788570] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 2160.788572] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 2160.788574] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ 2160.788576] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [ 2160.788579] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 2160.788589] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [ 2160.793777] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). [ 2160.793895] radeon 0000:01:00.0: WB enabled [ 2160.793900] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8801fb519c00 [ 2160.793904] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8801fb519c0c [ 2160.796145] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000174118 and cpu addr 0xffffc900079b2118 [ 2160.812389] [drm] ring test on 0 succeeded in 2 usecs [ 2160.812457] [drm] ring test on 3 succeeded in 1 usecs [ 2160.987496] [drm] ring test on 5 succeeded in 1 usecs [ 2160.987512] [drm] UVD initialized successfully. [ 2161.219416] [drm] ib test on ring 0 succeeded in 0 usecs [ 2161.219497] [drm] ib test on ring 3 succeeded in 1 usecs [ 2161.370073] [drm:r600_uvd_ib_test] *ERROR* radeon: failed to get create msg (-22). [ 2161.370094] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-22). ~$ lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI BeaverCreek [Radeon HD 6620G] 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Whistler [Radeon HD 6600M/6700M/7600M Series] (DRI_PRIME is used to launch game.) Linux 3.10-rc7 libdrm 2.4.45+git20130607.a0178c00 Mesa 9.2.0~git20130627.15085b47 xserver-xorg-video-radeon 7.1.99+git20130531.bd2557ea Xserver 1.13.4~git20130508+server-1.13-branch.10c42f57 Kubuntu 13.04 x86_64 updated from Xorg Edgers PPA. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 89521] New: Radeon driver fails to set dpm power state after resume from S3
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '16

19 Feb '16

https://bugzilla.kernel.org/show_bug.cgi?id=89521 Bug ID: 89521 Summary: Radeon driver fails to set dpm power state after resume from S3 Product: Drivers Version: 2.5 Kernel Version: 3.18.0 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: anhermann(a)gmx.net Regression: No Created attachment 160341 --> https://bugzilla.kernel.org/attachment.cgi?id=160341&action=edit dmesg output from 3 resume cycles Using a Radeon R9 270X and kernel 3.18.0 I get the following error message only after resume from S3 state: [drm:si_dpm_set_power_state] *ERROR* si_set_sw_state failed I would like to notice that this also happened with older kernel versions (3.17 and 3.16 with radeon.dpm=1) and other cards. My other PC has a HD 5450 with the same problem (slightly other ERROR string as its not SI). Besides the error message, I cannot see any strange behaviour, performance is good, no freezes etc. . But it sounds like performance level switching is not working correctly? I added the dmesg output showing three resume cycles with the mentioned error message as attachment. Thanks -- You are receiving this mail because: You are watching the assignee of the bug.

1 1

[Bug 90426] [tahiti xt] fog seems broken
by bugzilla-daemon＠freedesktop.org 15 Feb '16

15 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=90426 Bug ID: 90426 Summary: [tahiti xt] fog seems broken 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: sylvain.bertrand(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Main screen from sky force anniversary (game on steam): - catalyst fog is ok - mesa git fog seems broken (radeon tahiti xt) -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 79756] New: [Radeon] Resizing Steam windows freezes Xorg
by bugzilla-daemon＠freedesktop.org 15 Feb '16

15 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=79756 Priority: medium Bug ID: 79756 Assignee: dri-devel(a)lists.freedesktop.org Summary: [Radeon] Resizing Steam windows freezes Xorg Severity: normal Classification: Unclassified OS: Linux (All) Reporter: marti(a)juffo.org Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 100572 --> https://bugs.freedesktop.org/attachment.cgi?id=100572&action=edit kernel.log The gauntlet continues... After solving bug 79325, Steam now starts, but when I try to resize any Steam windows, Xorg freezes: it does not react to keyboard input (VT switching or num lock) and killing Steam doesn't unlock it. But the mouse cursor still responds to mouse movements. There is nothing in Xorg logs after the freeze. xorg-server 1.15.1 linux 3.15-rc8 linux-firmware a4f3bc03f1e7b1f25cc52328981c2a35871e55a1 (with PITCAIRN_mc2.bin) xf86-video-ati 7.3.0 Tried ati-dri/mesa versions 10.2.0rc5 as well as 10.1.3 Tried glamor-egl git a4fbc7732a1e56de385f50b778aafbdd186e015c as well as 0.6.0 (patched with cccfea4454949e3e376be42bb230603848997195 per bug 79325) gdb dump at the time of freeze: (gdb) thread apply all bt Thread 2 (Thread 0x7f34a3efd700 (LWP 630)): #0 0x00007f34ae00cb2f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x00007f34a65679cb in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x00007f34a6567117 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x00007f34ae008124 in start_thread () from /usr/lib/libpthread.so.0 #4 0x00007f34acd374bd in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f34aeac5880 (LWP 553)): #0 0x00007f34ae00f38c in __lll_lock_wait () from /usr/lib/libpthread.so.0 #1 0x00007f34ae00ab3c in _L_lock_553 () from /usr/lib/libpthread.so.0 #2 0x00007f34ae00a91a in pthread_mutex_lock () from /usr/lib/libpthread.so.0 #3 0x00007f34aad16fae in eglCreateImageKHR () from /usr/lib/libEGL.so.1 #4 0x00007f34aaf35e21 in glamor_egl_create_textured_pixmap () from /usr/lib/xorg/modules/libglamoregl.so #5 0x00007f34a77e1ac0 in ?? () from /usr/lib/xorg/modules/drivers/radeon_drv.so #6 0x00007f34a77e1e26 in ?? () from /usr/lib/xorg/modules/drivers/radeon_drv.so #7 0x00007f34a77d8819 in ?? () from /usr/lib/xorg/modules/drivers/radeon_drv.so #8 0x00000000005554c3 in ?? () #9 0x000000000055628f in ?? () #10 0x0000000000556690 in DRI2GetBuffersWithFormat () #11 0x00007f34a7c2e661 in ?? () from /usr/lib/xorg/modules/extensions/libglx.so #12 0x00007f34a656383a in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #13 0x00007f34a656190a in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #14 0x00007f34a66baa2e in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #15 0x00007f34a66bbb98 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #16 0x00007f34a668d9c0 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #17 0x00007f34a66a19d5 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #18 0x00007f34a6676577 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #19 0x00007f34a665d74c in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #20 0x00007f34a66735d4 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #21 0x00007f34a659d403 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so #22 0x00007f34aad20fee in ?? () from /usr/lib/libEGL.so.1 #23 0x00007f34aad193c5 in eglMakeCurrent () from /usr/lib/libEGL.so.1 #24 0x00007f34aaf35c08 in glamor_egl_make_current () from /usr/lib/xorg/modules/libglamoregl.so #25 0x00007f34aa8cdc69 in glamor_block_handler () from /usr/lib/libglamor.so.0 #26 0x000000000043ad64 in _CallCallbacks () #27 0x0000000000588096 in WriteToClient () #28 0x00007f34a7c13761 in ?? () from /usr/lib/xorg/modules/extensions/libglx.so #29 0x00007f34a7c271d0 in ?? () from /usr/lib/xorg/modules/extensions/libglx.so #30 0x0000000000435c8e in ?? () #31 0x0000000000439aaa in ?? () #32 0x00007f34acc6e000 in __libc_start_main () from /usr/lib/libc.so.6 #33 0x000000000042507e in _start () -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 79504] New: LLVM error on fragment shader
by bugzilla-daemon＠freedesktop.org 12 Feb '16

12 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=79504 Priority: medium Bug ID: 79504 Assignee: dri-devel(a)lists.freedesktop.org Summary: LLVM error on fragment shader Severity: normal Classification: Unclassified OS: Linux (All) Reporter: kyle(a)klkblake.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 100230 --> https://bugs.freedesktop.org/attachment.cgi?id=100230&action=edit fragment shader After compiling the attached shader and making it current, calling glClear() causes the process to crash with this error: LLVM ERROR: Cannot select: 0x314a010: v16f32 = bitcast 0x3185250 [ORD=347] [ID=224] 0x3185250: v16i32 = BUILD_VECTOR 0x3153680, 0x3153780, 0x3153880, 0x3153980, 0x3187b70, 0x3187970, 0x3097a00, 0x3097800, 0x3097600, 0x3097400, 0x3097200, 0x3097000, 0x3096e00, 0x3096c00, 0x3185550, 0x314b520 [ORD=347] [ID=222] ... <snip> ... (full error attached) I'm using the latest git version (3fc72f2ec601cb758d69cf2933dd6268d1a80c5b). -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 89686] x1250 rs600m graphic problems / unreadable fonts in (gl?)- games
by bugzilla-daemon＠freedesktop.org 10 Feb '16

10 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=89686 Bug ID: 89686 Summary: x1250 rs600m graphic problems / unreadable fonts in (gl?)- games Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: highest Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: m.st(a)gmx.net Created attachment 114484 --> https://bugs.freedesktop.org/attachment.cgi?id=114484&action=edit Warzone The problem is viewable in my attached picture. It's the game Teeworlds for example - with corrupt font. Mint 17 Mate 64 is same as in Mint 17 Xfce 64. Problems with that notebook-graphic also on Ubuntu (and when I remember correct Debian, too) HalfLife and Warzone 2100 looks same. Distros were all fresh installed. (in Ubuntu/Unity the top taskbar has the same 'striped and defect'look directly at first startup after install) Some more informations, now Mate 17.1: dmesg | grep -i radeon [ 3.414242] [drm] radeon kernel modesetting enabled. [ 3.414339] fb: switching to radeondrmfb from EFI VGA [ 3.415143] radeon 0000:01:05.0: VRAM: 256M 0x0000000070000000 - 0x000000007FFFFFFF (256M used) [ 3.415146] radeon 0000:01:05.0: GTT: 512M 0x0000000080000000 - 0x000000009FFFFFFF [ 3.415274] [drm] radeon: 256M of VRAM memory ready [ 3.415276] [drm] radeon: 512M of GTT memory ready. [ 3.424768] [drm] radeon: 1 quad pipes, 1 z pipes initialized. [ 3.426141] radeon 0000:01:05.0: WB enabled [ 3.426146] radeon 0000:01:05.0: fence driver on ring 0 use gpu addr 0x0000000080000000 and cpu addr 0xffff880035a38000 [ 3.426166] [drm] radeon: irq initialized. [ 3.426387] [drm] radeon: ring at 0x0000000080001000 [ 3.428091] [drm] radeon atom DIG backlight initialized [ 3.428096] [drm] Radeon Display Connectors [ 4.040201] fbcon: radeondrmfb (fb0) is primary device [ 4.040282] radeon 0000:01:05.0: fb0: radeondrmfb frame buffer device [ 4.040285] radeon 0000:01:05.0: registered panic notifier [ 4.044113] [drm] Initialized radeon 2.39.0 20080528 for 0000:01:05.0 on minor 0 ------------------------------------------------------------ glxinfo | grep gl server glx vendor string: SGI server glx version string: 1.4 server glx extensions: client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_texture_sRGB, GL_NV_texture_env_combine4, GL_NV_texture_rectangle, GL_NV_vdpau_interop, ------------------------------------------------------------ I changed nomodeset at startup with shift, e - but it resulted in complete garbage - the splash-screen where I normally enter my password was completely defect, b/w and absolutely unusable. I furthermore created xorg.conf, edited it with nano at the right place and changed the line with 'Option "EXAPixmaps"' to "off", afther that it started nomal - but thats all, its also unusable. Screen corrupts in a way I've never seen before, parts were rotated completely, looked crazy. But that was not what I looked for. ------------------------------------------------------------ Any ideas? It is impossible to play games :( Thanks for any help! More, maybe useful, don´t know, with 1 or two more pics, too: https://bugs.freedesktop.org/show_bug.cgi?id=35457 -- You are receiving this mail because: You are the assignee for the bug.

1 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel May 2015