Broken NVIDIA RandR detected, falling back to RandR 1.0.

Questions about Wine on Linux
Post Reply
jaerki
Level 1
Level 1
Posts: 8
Joined: Tue Jun 25, 2019 11:14 am

Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by jaerki » Tue Jun 25, 2019 11:49 am

I am having trouble running a game called Ragnarok. Game runs fine except there is stuttering of frames, constantly. Game requires OpenGL hardware acceleration.

I am running ubuntu 16.04 32bit with nvidia proprietary drivers.
wine 4.0.1 installed from HQ repository.

Attached is winelog with additional information. Log shows that 3D acceleration is present, however in game it is not. Please guide in correct direction.

Code: Select all

0026:err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
000d:err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
0009:err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
0009:fixme:thread:GetThreadUILanguage : stub, returning default language.
0009:fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33d8dc, (nil) 0x33d904
0009:fixme:nls:get_dummy_preferred_ui_language (0x38 0x33d8dc (nil) 0x33d904) returning a dummy value (current locale)
0009:fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33d8dc, 0x109a680 0x33d904
0009:fixme:nls:get_dummy_preferred_ui_language (0x38 0x33d8dc 0x109a680 0x33d904) returning a dummy value (current locale)
0009:fixme:wtsapi:WTSRegisterSessionNotification Stub 0x1007e 0x00000000
0009:fixme:uxtheme:BufferedPaintInit Stub ()
0009:fixme:dwmapi:DwmIsCompositionEnabled 0x33fd28
0009:fixme:shcore:SetCurrentProcessExplicitAppUserModelID L"Thor_3402319": stub
002c:fixme:win:FlashWindowEx 0x143fe18 - semi-stub
0009:fixme:wtsapi:WTSUnRegisterSessionNotification Stub 0x1007e
0009:fixme:uxtheme:BufferedPaintUnInit Stub ()
002f:err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
002f:fixme:ntdll:NtQuerySystemInformation (0x00000067,0x33e9c4,0x00000008,0x33e9cc) stub
002f:fixme:wtsapi:WTSEnumerateProcessesA Stub (nil) 0x00000000 0x00000001 0x33e9d0 0x33e9cc
002f:fixme:file:K32GetMappedFileNameA (0xffffffff, 0x3e90000, 0x33f7b8, 260): stub
002f:fixme:file:K32GetMappedFileNameA (0xffffffff, 0x6a90000, 0x33f7b8, 260): stub
002f:fixme:file:K32GetMappedFileNameA (0xffffffff, 0xa4a0000, 0x33f7b8, 260): stub
002f:fixme:win:EnumDisplayDevicesW ((null),0,0x33f294,0x00000000), stub!
002f:trace:wgl:X11DRV_WineGL_InitOpenglInfo GL version             : 3.3.0 NVIDIA 340.107.
002f:trace:wgl:X11DRV_WineGL_InitOpenglInfo GL renderer            : GeForce 8600M GT/PCIe/SSE2.
002f:trace:wgl:X11DRV_WineGL_InitOpenglInfo GLX version            : 1.4.
002f:trace:wgl:X11DRV_WineGL_InitOpenglInfo Server GLX version     : 1.4.
002f:trace:wgl:X11DRV_WineGL_InitOpenglInfo Server GLX vendor:     : NVIDIA Corporation.
002f:trace:wgl:X11DRV_WineGL_InitOpenglInfo Client GLX version     : 1.4.
002f:trace:wgl:X11DRV_WineGL_InitOpenglInfo Client GLX vendor:     : NVIDIA Corporation.
002f:trace:wgl:X11DRV_WineGL_InitOpenglInfo Direct rendering enabled: True
002f:trace:wgl:init_opengl GLX is up and running error_base = 169

User avatar
Bob Wya
Level 12
Level 12
Posts: 2778
Joined: Sat Oct 16, 2010 7:40 pm
Location: Cambridge
Contact:

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by Bob Wya » Tue Jun 25, 2019 6:31 pm

jaerki wrote:I am having trouble running a game called Ragnarok. Game runs fine except there is stuttering of frames, constantly. Game requires OpenGL hardware acceleration.
You've got the best setup you can get, given your ancient graphics card (it was released in 2007 - over 10 years ago).

About all you can do, additionally, is to perhaps retest with winehq-staging-4.11...
Enable wine-esync with:

Code: Select all

export WINEESYNC=1
and disable all Wine terminal output:

Code: Select all

export WINEDEBUG=-all
These measures might help a little bit.

Also you probably want to disable composting, in your Desktop Environment.


Please don't title a forum thread with:
Broken NVIDIA RandR detected, falling back to RandR 1.0.
This is totally meaningless and does not provide any description - what-so-ever - of what the thread is about. :roll:

Wine outputs this terminal message, for anyone using the Nvidia proprietary driver.
Whether they have a crappy, ancient video card or a shiny new Geforce RTX 2080 Ti !
I patch out this warning message, on my Gentoo wine ebuild's, because it is so annoying.
Nvidia doesn't fully implement newer xrandr standards, in their proprietary driver...

A more sensible forum title would be something like:
Ubuntu 16.04 + Wine 4.0.1: Ragnarok constant frame stuttering
Boom - all the information is there... At a glance.
It's also easy to re-find the thread, in the main forum thread list.

Thanks
Bob

jkfloris
Level 6
Level 6
Posts: 704
Joined: Thu Aug 14, 2014 10:10 am

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by jkfloris » Wed Jun 26, 2019 10:31 am

@Bob Wya
[Off-topic]
Wine outputs this terminal message, for anyone using the Nvidia proprietary driver.
Whether they have a crappy, ancient video card or a shiny new Geforce RTX 2080 Ti !
That is weird. I don't get that warning
:roll: Maybe I am not anyone.

Debian Sid, Wine 4.11

Code: Select all

~/.wine/drive_c/Program Files (x86)/misc$ WINEDEBUG=+xrandr,+wgl /opt/wine-devel/bin/wine wglgears.exe 
001e:trace:xrandr:X11DRV_XRandR_Init Found XRandR 1.5.
001e:trace:xrandr:xrandr12_init_modes CRTC 0: mode 0x1c0, 1920x1080+0+0.
001e:trace:xrandr:xrandr12_init_modes OUTPUT 0: name "DVI-D-0".
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1c0: 1920x1080@60.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1c1: 1680x1050@60.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1c2: 1440x900@75.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1c3: 1440x900@60.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1c4: 1280x1024@75.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1c5: 1280x1024@60.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1c6: 1280x960@60.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1c7: 1152x864@75.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1c8: 1024x768@75.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1c9: 1024x768@70.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1ca: 1024x768@60.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1cb: 800x600@75.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1cc: 800x600@60.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1cd: 800x600@56.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1ce: 640x480@75.
001e:trace:xrandr:xrandr12_init_modes Adding mode 0x1cf: 640x480@60.
001e:trace:xrandr:xrandr12_get_current_mode CRTC 0: mode 0x1c0, 1920x1080+0+0.
000d:trace:xrandr:X11DRV_XRandR_Init Found XRandR 1.5.
000d:trace:xrandr:xrandr12_init_modes CRTC 0: mode 0x1c0, 1920x1080+0+0.
000d:trace:xrandr:xrandr12_init_modes OUTPUT 0: name "DVI-D-0".
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1c0: 1920x1080@60.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1c1: 1680x1050@60.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1c2: 1440x900@75.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1c3: 1440x900@60.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1c4: 1280x1024@75.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1c5: 1280x1024@60.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1c6: 1280x960@60.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1c7: 1152x864@75.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1c8: 1024x768@75.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1c9: 1024x768@70.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1ca: 1024x768@60.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1cb: 800x600@75.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1cc: 800x600@60.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1cd: 800x600@56.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1ce: 640x480@75.
000d:trace:xrandr:xrandr12_init_modes Adding mode 0x1cf: 640x480@60.
0009:trace:xrandr:X11DRV_XRandR_Init Found XRandR 1.5.
0009:trace:xrandr:xrandr12_init_modes CRTC 0: mode 0x1c0, 1920x1080+0+0.
0009:trace:xrandr:xrandr12_init_modes OUTPUT 0: name "DVI-D-0".
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1c0: 1920x1080@60.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1c1: 1680x1050@60.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1c2: 1440x900@75.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1c3: 1440x900@60.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1c4: 1280x1024@75.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1c5: 1280x1024@60.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1c6: 1280x960@60.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1c7: 1152x864@75.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1c8: 1024x768@75.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1c9: 1024x768@70.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1ca: 1024x768@60.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1cb: 800x600@75.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1cc: 800x600@60.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1cd: 800x600@56.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1ce: 640x480@75.
0009:trace:xrandr:xrandr12_init_modes Adding mode 0x1cf: 640x480@60.
0009:trace:wgl:wglChoosePixelFormat 0x25003f 0x404068: size 40 version 1 flags 37 type 0 color 24 0,0,0,0 accum 0 depth 16 stencil 0 aux 0
0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo GL version             : 4.6.0 NVIDIA 418.74.
0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo GL renderer            : GeForce GTX 950/PCIe/SSE2.
0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo GLX version            : 1.4.
0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo Server GLX version     : 1.4.
0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo Server GLX vendor:     : NVIDIA Corporation.
0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo Client GLX version     : 1.4.
0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo Client GLX vendor:     : NVIDIA Corporation.
0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo Direct rendering enabled: True
...

jaerki
Level 1
Level 1
Posts: 8
Joined: Tue Jun 25, 2019 11:14 am

Ubuntu 16.04 + Wine 4.0.1: Ragnarok constant frame stutterin

Post by jaerki » Wed Jun 26, 2019 12:51 pm

Is this guide of use to me:
https://wiki.winehq.org/Wine_Developer% ... and_OpenGL
specially part 3.2 - It seems I can't run the script mentioned there, because my /path is different, or there are no such files in respective directories. Maybe the guide isn't up to date?

Also my video card should run this game smoothly.
Enable wine-esync with:
Code:
export WINEESYNC=1

and disable all Wine terminal output:
Code:
export WINEDEBUG=-all

These measures might help a little bit
What file to edit with these lines?

jaerki
Level 1
Level 1
Posts: 8
Joined: Tue Jun 25, 2019 11:14 am

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by jaerki » Thu Jun 27, 2019 1:55 am

I don't even have to login to game to experience stuttering, It starts at login screen.

Here is a log when I launch wine through terminal:

Code: Select all

002e:fixme:ntdll:NtQuerySystemInformation (0x00000067,0x33e9c4,0x00000008,0x33e9cc) stub
002e:fixme:wtsapi:WTSEnumerateProcessesA Stub (nil) 0x00000000 0x00000001 0x33e9d0 0x33e9cc
002e:fixme:file:K32GetMappedFileNameA (0xffffffff, 0x3e90000, 0x33f7b8, 260): stub
002e:fixme:file:K32GetMappedFileNameA (0xffffffff, 0x6a90000, 0x33f7b8, 260): stub
002e:fixme:file:K32GetMappedFileNameA (0xffffffff, 0xa4a0000, 0x33f7b8, 260): stub
002e:fixme:win:EnumDisplayDevicesW ((null),0,0x33f294,0x00000000), stub!
002e:fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}.
0039:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts.
002e:fixme:ddraw:ddraw7_WaitForVerticalBlank iface 0x1ab118, flags 0x1, event (nil) stub!
0032:fixme:wtsapi:WTSEnumerateProcessesA Stub (nil) 0x00000000 0x00000001 0x329f168 0x329f164
0032:fixme:wtsapi:WTSEnumerateProcessesA Stub (nil) 0x00000000 0x00000001 0x329f168 0x329f164
002e:err:ole:CoUninitialize Mismatched CoUninitialize
Glxinfo -B gives this outup:

Code: Select all

sPC:~/Wine/RagnarokLife_client-2019030802_full-packed$ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 8600M GT/PCIe/SSE2
OpenGL core profile version string: 3.3.0 NVIDIA 340.107
OpenGL core profile shading language version string: 3.30 NVIDIA via Cg compiler
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.3.0 NVIDIA 340.107
OpenGL shading language version string: 3.30 NVIDIA via Cg compiler
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 2.0 NVIDIA 340.107 340.107
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.00


jaerki
Level 1
Level 1
Posts: 8
Joined: Tue Jun 25, 2019 11:14 am

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by jaerki » Thu Jun 27, 2019 1:30 pm

I have just reinstalled with wine staging. Problem persists. No OpenGL support in the game.

User avatar
Bob Wya
Level 12
Level 12
Posts: 2778
Joined: Sat Oct 16, 2010 7:40 pm
Location: Cambridge
Contact:

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by Bob Wya » Thu Jun 27, 2019 2:01 pm

jkfloris wrote:@Bob Wya
[Off-topic]
Wine outputs this terminal message, for anyone using the Nvidia proprietary driver.
Whether they have a crappy, ancient video card or a shiny new Geforce RTX 2080 Ti !
That is weird. I don't get that warning
:roll: Maybe I am not anyone.

Debian Sid, Wine 4.11
...
Ah that's interesting. I dug into the Wine source code... It's because my laptop's builtin display is connected by Display Port.
The Nvidia driver only returns a single (native) display resolution, for such a device, from xrandr.
This is what actually triggers the warning message from Wine.

Bob

User avatar
Bob Wya
Level 12
Level 12
Posts: 2778
Joined: Sat Oct 16, 2010 7:40 pm
Location: Cambridge
Contact:

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by Bob Wya » Thu Jun 27, 2019 2:10 pm

@jaerki

You could try forcibly lowering the OpenGL profile Wine supports:

Code: Select all

wine reg add 'HKEY_CURRENT_USER\Software\Wine\Direct3D' /v MaxVersionGL /t REG_DWORD /d 0x30003 /f
See: WineHQ Wiki: Useful Registry Keys.

Bob

jaerki
Level 1
Level 1
Posts: 8
Joined: Tue Jun 25, 2019 11:14 am

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by jaerki » Fri Jun 28, 2019 8:22 am

After using in terminal:

Code: Select all

 wine reg add HKEY_CURRENT_USER\Software\Wine\Direct3D' /v MaxVersionGL /t REG_DWORD /d 0x30003 /f
I get following output:

Code: Select all

002f:err:winediag:wined3d_dll_init Setting maximum allowed wined3d GL version to 3.3.
002f:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
002f:fixme:ntdll:NtQuerySystemInformation (0x00000067,0x32e694,0x00000008,0x32e69c) stub
002f:fixme:wtsapi:WTSEnumerateProcessesA Stub (nil) 0x00000000 0x00000001 0x32e6a0 0x32e69c
002f:fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}.
002f:fixme:ddraw:ddraw_surface_create Application wants to create rendering target in system memory, using video memory instead
003c:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts.
002f:fixme:ddraw:ddraw7_WaitForVerticalBlank iface 0x1c5398, flags 0x1, event (nil) stub!
0033:fixme:wtsapi:WTSEnumerateProcessesA Stub (nil) 0x00000000 0x00000001 0x349f1e8 0x349f1e4
002f:err:ole:CoUninitialize Mismatched CoUninitialize
Nothing changed inside the game, however.

User avatar
Bob Wya
Level 12
Level 12
Posts: 2778
Joined: Sat Oct 16, 2010 7:40 pm
Location: Cambridge
Contact:

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by Bob Wya » Fri Jun 28, 2019 9:16 am

@jaerki

Can you log what your GPU is doing when you try to run the game?

Something like:

Code: Select all

start_log=0
echo "" > "${HOME}/nvidia_gpu_log.txt"
while ((1)); do
    sleep 10s
    if pgrep -c 'wineserver'; then
        start_log=1
    elif ((start_log)); then
        break
    else
        continue
    fi
    nvidia-smi --query >> "${HOME}/nvidia_gpu_log.txt"
done        
should do. Just run the script, before running the game...

Thanks
Bob

jaerki
Level 1
Level 1
Posts: 8
Joined: Tue Jun 25, 2019 11:14 am

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by jaerki » Fri Jun 28, 2019 10:15 am

I don't know how to attach whole log as a file, so here is sample:

Code: Select all

==============NVSMI LOG==============

Timestamp                           : Fri Jun 28 18:01:40 2019
Driver Version                      : 340.107

Attached GPUs                       : 1
GPU 0000:01:00.0
    Product Name                    : GeForce 8600M GT
    Product Brand                   : GeForce
    Display Mode                    : N/A
    Display Active                  : N/A
    Persistence Mode                : Disabled
    Accounting Mode                 : N/A
    Accounting Mode Buffer Size     : N/A
    Driver Model
        Current                     : N/A
        Pending                     : N/A
    Serial Number                   : N/A
    GPU UUID                        : GPU-018
    Minor Number                    : 0
    VBIOS Version                   : 60.84.50.00.01
    MultiGPU Board                  : N/A
    Board ID                        : N/A
    Inforom Version
        Image Version               : N/A
        OEM Object                  : N/A
        ECC Object                  : N/A
        Power Management Object     : N/A
    GPU Operation Mode
        Current                     : N/A
        Pending                     : N/A
    PCI
        Bus                         : 0x01
        Device                      : 0x00
        Domain                      : 0x0000
        Device Id                   : 0x000000DE
        Bus Id                      : 0000:01:00.0
        Sub System Id               : 0x01F00000
        GPU Link Info
            PCIe Generation
                Max                 : N/A
                Current             : N/A
            Link Width
                Max                 : N/A
                Current             : N/A
        Bridge Chip
            Type                    : N/A
            Firmware                : N/A
    Fan Speed                       : 100 %
    Performance State               : P0
    Clocks Throttle Reasons         : N/A
    FB Memory Usage
        Total                       : 255 MiB
        Used                        : 159 MiB
        Free                        : 96 MiB
    BAR1 Memory Usage
        Total                       : N/A
        Used                        : N/A
        Free                        : N/A
    Compute Mode                    : Default
    Utilization
        Gpu                         : N/A
All following lines are also : N/A

User avatar
Bob Wya
Level 12
Level 12
Posts: 2778
Joined: Sat Oct 16, 2010 7:40 pm
Location: Cambridge
Contact:

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by Bob Wya » Sat Jun 29, 2019 5:48 pm

jaerki wrote:I don't know how to attach whole log as a file, so here is sample:
...
You can put the log anywhere. Github Gist's are quite robust.
Don't bother trying to attach anything to a forum post - it's a real pain (and the max file size limit is only ⩽ 200 Kbytes)... :lol:

Maybe retry with:

Code: Select all

nvidia-smi -l 60 --format=csv --query-gpu=timestamp,pstate,memory.used,memory.free,memory.total,utilization.gpu,utilization.memory
That should be less verbose...
  • What CPU are you using? E.g.:

    Code: Select all

    sudo apt-get install inxi
    inxi -C
  • Also, is one of your CPU cores being pegged by the wineserver process?

Thanks
Bob

jaerki
Level 1
Level 1
Posts: 8
Joined: Tue Jun 25, 2019 11:14 am

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by jaerki » Mon Jul 01, 2019 10:07 am

CPU: Dual core Intel Pentium Dual T2390 (-MCP-) cache: 1024 KB
clock speeds: max: 1867 MHz 1: 1323 MHz 2: 1221 MHz

After this:
nvidia-smi -l 60 --format=csv --query-gpu=timestamp,pstate,memory.used,memory.free,memory.total,utilization.gpu,utilization.memory
I get this:

Code: Select all

2019/07/01 17:52:52.122, P0, 176 MiB, 79 MiB, 255 MiB, [Not Supported], [Not Supported]
2019/07/01 17:53:52.123, P0, 136 MiB, 119 MiB, 255 MiB, [Not Supported], [Not Supported]
2019/07/01 17:54:52.124, P0, 149 MiB, 106 MiB, 255 MiB, [Not Supported], [Not Supported]
Also, is one of your CPU cores being pegged by the wineserver process?
Does this mean its a problem on hardware level? That certainly could be a thing, because I disassembled to clean from dust recently.

User avatar
Bob Wya
Level 12
Level 12
Posts: 2778
Joined: Sat Oct 16, 2010 7:40 pm
Location: Cambridge
Contact:

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by Bob Wya » Mon Jul 01, 2019 4:16 pm

jaerki wrote:

Code: Select all

CPU:       Dual core Intel Pentium Dual T2390 (-MCP-) cache: 1024 KB 
           clock speeds: max: 1867 MHz 1: 1323 MHz 2: 1221 MHz
Also, is one of your CPU cores being pegged by the wineserver process?
Does this mean its a problem on hardware level? That certainly could be a thing, because I disassembled to clean from dust recently.
No... Pegging a CPU core simply means means maxing that core at 100%.
The origins of this expression are probably related to: Etymology of a “pegged CPU”. It's quite a common expression.

wineserver is single-threaded - so has a lot of potential to become a bottleneck when gaming with Wine (especially on machines with low single-threaded performance).

Are we talking about this game: Ragnarok Online ?
Because then you've got the added complication of how Wine (+ your CPU) handles the games netcode...

Referring to: WineHQ Wiki: Performance...

It might be worth profiling Wine+Ragnarok:

Code: Select all

perf record wine ...
by installing the Ubuntu package: linux-tools-common

This will leave a profile log in the same directory, as you ran the command, called (by default): perf.data

You can visualise / display the data, in the this log file, with the command:

Code: Select all

perf report --input="${HOME}/perf.data"
(changing the location of the perf.data file - as required!)

So if you could try recording a performance trace; running Ragnarok, with Wine...
Then post a compressed version of the perf.data log file, somewhere like Google Drive or Mega (sites that will host large file).
Also, if you use firefox, then Firefox Send - would probably be quite effective!
Please do compress the log file first - before posting it online - with xz!

Thanks
Bob

jaerki
Level 1
Level 1
Posts: 8
Joined: Tue Jun 25, 2019 11:14 am

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by jaerki » Tue Jul 02, 2019 3:06 am

Bob Wya wrote:
jaerki wrote:

Code: Select all

CPU:       Dual core Intel Pentium Dual T2390 (-MCP-) cache: 1024 KB 
           clock speeds: max: 1867 MHz 1: 1323 MHz 2: 1221 MHz
Also, is one of your CPU cores being pegged by the wineserver process?
Does this mean its a problem on hardware level? That certainly could be a thing, because I disassembled to clean from dust recently.
No... Pegging a CPU core simply means means maxing that core at 100%.
The origins of this expression are probably related to: Etymology of a “pegged CPU”. It's quite a common expression.

wineserver is single-threaded - so has a lot of potential to become a bottleneck when gaming with Wine (especially on machines with low single-threaded performance).

Are we talking about this game: Ragnarok Online ?
Because then you've got the added complication of how Wine (+ your CPU) handles the games netcode...

Referring to: WineHQ Wiki: Performance...

It might be worth profiling Wine+Ragnarok:

Code: Select all

perf record wine ...
by installing the Ubuntu package: linux-tools-common

This will leave a profile log in the same directory, as you ran the command, called (by default): perf.data

You can visualise / display the data, in the this log file, with the command:

Code: Select all

perf report --input="${HOME}/perf.data"
(changing the location of the perf.data file - as required!)

So if you could try recording a performance trace; running Ragnarok, with Wine...
Then post a compressed version of the perf.data log file, somewhere like Google Drive or Mega (sites that will host large file).
Also, if you use firefox, then Firefox Send - would probably be quite effective!
Please do compress the log file first - before posting it online - with xz!

Thanks
Bob
https://send.firefox.com/download/cd554 ... xAkvxVUjQg

User avatar
Bob Wya
Level 12
Level 12
Posts: 2778
Joined: Sat Oct 16, 2010 7:40 pm
Location: Cambridge
Contact:

Re: Broken NVIDIA RandR detected, falling back to RandR 1.0.

Post by Bob Wya » Thu Jul 04, 2019 10:43 am

@jaerki

Code: Select all

perf report --sort=comm --stdio

# To display the perf.data header info, please use --header/--header-only options.
#
#
# Total Lost Samples: 0
#
# Samples: 24K of event 'cycles'
# Event count (approx.): 8437872948
#
# Overhead  Command        
# ........  ...............
#
    25.49%  winemenubuilder
    22.25%  wineserver     
    18.09%  explorer.exe   
    16.28%  Life.exe       
     6.25%  wineboot.exe   
     5.19%  winedevice.exe 
     2.82%  wine           
     1.67%  services.exe   
     1.16%  rolife.exe     
     0.75%  plugplay.exe   
     0.05%  wine-preloader 
     0.00%  perf           
Your game is (rather bizarrely) spending a lot of time in winemenubuilder??!!
So you could try to disable this.
See: WineHQ FAQ: 6.6.4 How can I prevent Wine from changing the filetype associations on my system or adding unwanted menu entries/desktop links?

Bob

Post Reply