similar to: [Bug 95334] New: GM107 with 2560x1440 display on HDMI selects suboptimal resolution 1920x1080

Hi, I've been try to get sound in wine (20040121) working on my machine for while now. As you've probably guessed I've got a SiS 7012 (which uses the intel i8x0 modules) and alsa (either natively or OSS emulation.) google came up with a few hits about this not working in the past, namely: http://www.winehq.org/hypermail/wine-devel/2002/12/0281.html But I'm not sure if this is

Hi, I've managed to get Skype running under Debian with the latest Debian release of wine. The sound is perfect, and there are no connection problems, but I noticed the following: 1) Sound from my microphone disappears ONLY when I start some other application or switch to another application. I can only vouch for this in KDE, and it happens whenever anything accesses the soundcard, so

Hi, Distribution: openSUSE 42.2 Beta, Kernel: 4.4. The box is a Dell Precision T7500 with an nVidia Quadro 4000 card and a displayport connected iiyama B2783QSU 2560x1440 monitor identified as DP-1. Problem: The monitor is detected as 1920x1080 and not 2560x1440. See Xorg log file at http://rogerprice.org/Xorg.0.log . There is no file /etc/X11/xorg.conf and in the directory

Hello list, I successfully installed Morrowind. Unfortunately, the game won't start. It issues a small popup saying a debugger has been detected, and that the debugger needs to be closed for the game to run. Is there any way I can avoid programs to see Wine as a debugger? Thanks! _________________________________________________________________ MSN Messenger : discutez en direct avec vos

These patches are adding support for outputting 2560x1440 at 56 over HDMI. This needs a pixel clock of 225 MHz which was not supported before. This was tested in a dual monitor setup with a GF114 (GTX 560 TI) and one HDMI monitor running with 2560x1440 at 56 and one DVI monitor running with 1920x1200 at 60. This still needs testing on other graphics cards and with dual link DVI. There is no

These patches are adding support for outputting 2560x1440 at 56 over HDMI. This needs a pixel clock of 225 MHz which was not supported before. This was tested in a dual monitor setup with a GF114 (GTX 560 TI) and one HDMI monitor running with 2560x1440 at 56 and one DVI monitor running with 1920x1200 at 60. This still needs testing on other graphics cards and with dual link DVI. There is no

I think you want the reduced blanking modeline: $ cvt -r 2560 1440 # 2560x1440 59.95 Hz (CVT 3.69M9-R) hsync: 88.79 kHz; pclk: 241.50 MHz Modeline "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync This matches your monitor's detailed timings: [ 55.220] (II) NOUVEAU(0): Supported detailed timing: [ 55.220] (II) NOUVEAU(0): clock: 241.5 MHz Image

Spotted by coccinelle: drivers/gpu/drm/nouveau/core/subdev/fuse/gm107.c:50:5-8: WARNING: end returns can be simpified Signed-off-by: Martin Peres <martin.peres at free.fr> --- drm/nouveau/nvkm/subdev/fuse/gm107.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drm/nouveau/nvkm/subdev/fuse/gm107.c b/drm/nouveau/nvkm/subdev/fuse/gm107.c index ba19158..0b256aa 100644

besides wine is there no other package thats can be used ----- Original Message ----- From: <wine-users-request@winehq.org> To: <wine-users@winehq.org> Sent: Friday, April 30, 2004 5:20 PM Subject: wine-users digest, Vol 1 #1756 - 15 msgs > Send wine-users mailing list submissions to > wine-users@winehq.org > > To subscribe or unsubscribe via the World Wide Web, visit

Patch "ltc/gm107: use nvkm_mask to set cbc_ctrl1" sets the 3rd bit of the CTRL1 register instead of writing it entirely in gm107_ltc_cbc_clear(). As a counterpart, gm107_ltc_cbc_wait() must also be modified to wait on that single bit only, otherwise a timeout may occur if some other bit of that register is set. This happened at least on GM206 when running glmark2-drm. While we are at

We get 1 warning when build kernel with W=1: drivers/gpu/drm/nouveau/nvkm/engine/gr/gm107.c:312:1: warning: no previous prototype for 'gm107_gr_init' [-Wmissing-prototypes] In fact, this function is only used in the file in which it is declared and don't need a declaration, but can be made static. so this patch marks this function with 'static'. Signed-off-by: Baoyou Xie

Signed-off-by: Karol Herbst <nouveau at karolherbst.de> --- drm/nouveau/nvkm/subdev/fb/gm107.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/subdev/fb/gm107.c b/drm/nouveau/nvkm/subdev/fb/gm107.c index 2a91df8..9cc7e61 100644 --- a/drm/nouveau/nvkm/subdev/fb/gm107.c +++ b/drm/nouveau/nvkm/subdev/fb/gm107.c @@ -29,7 +29,7 @@ gm107_fb = { .dtor =

Unfortunately there's no sure-fire way to distinguish a sched "op" from regular ones. They happen purely based on position. So for disassembly, use the byte position in the file to determine whether the current op should be decoded as sched or as regular. For assembly, we go back to using a shared table. Ideally we would pick out which one to use based on the position in the

https://bugs.freedesktop.org/show_bug.cgi?id=98391 Bug ID: 98391 Summary: [GM107] priv: HUB0: 614900 00800000 (1d408200) Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=103409 Bug ID: 103409 Summary: [GM107] reboot/suspend/lspci hang with nouveau Product: Mesa Version: 17.2 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=106662 Bug ID: 106662 Summary: nouveau DPMS poblem with DRI3 (GM107) Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=90054 Bug ID: 90054 Summary: white screen reboot on gm107 with multiple monitors Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=106132 Bug ID: 106132 Summary: bar.sync encoding incorrect for GM107 Product: Mesa Version: git Hardware: All OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

There is no dedicated instruction for this, so just combine it with the constant offset. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: "10.3" <mesa-stable at lists.freedesktop.org> --- This fixes the spec/glsl-1.50/execution/geometry/dynamic_input_array_index piglit test. src/gallium/drivers/nouveau/codegen/nv50_ir_lowering_gm107.cpp | 5 ++++- 1 file changed,

Hello, The method we previously used on Fermi and Kepler (0x142c) to flush the VBO cache before draw appears to be gone on Maxwell. Is there a replacement method we should use? (Or perhaps that method was never meant for VBO cache flush and instead flushed something related to the vertex quarantine area defined by 0x17bc/0x17c0/0x17c4, which in turn is gone on Maxwell?) Thanks for any light you