xpra icon
Bug tracker and wiki

Opened 6 years ago

Closed 6 years ago

Last modified 5 years ago

#682 closed defect (invalid)

opengl disabled, texture too small

Reported by: pyther Owned by: pyther
Priority: minor Milestone:
Component: client Version: trunk
Keywords: Cc:

Description

Fedora 20
Gnome 3.12

eDP1 is a high resolution display (retina)

2014-09-14 13:01:27,261 OpenGL_accelerate module loaded
2014-09-14 13:01:27,261 Using accelerated ArrayDatatype
2014-09-14 13:01:27,262 OpenGL support could not be enabled:
2014-09-14 13:01:27,262  The texture size is too small: 8192
2014-09-14 13:01:27,340 detected keyboard: rules=evdev, model=pc104, layout=us
2014-09-14 13:01:27,342 desktop size is 5680x1440 with 1 screen(s):
2014-09-14 13:01:27,342   ':0.0' (1503x381 mm) workarea: 5680x1413 at 0x27
2014-09-14 13:01:27,342     eDP1 2560x1440 (310x174 mm)
2014-09-14 13:01:27,342     DP3 1680x1050 at 2560x0 (474x296 mm)
2014-09-14 13:01:27,342     DP4 1440x900 at 4240x0 (408x255 mm)

Let me know what additional information I can provide. My opengl knowledge is weak.

Change History (4)

comment:1 Changed 6 years ago by Antoine Martin

Owner: changed from Antoine Martin to pyther

Since 8192 is enough for your screen size (5680), it must be the rectangle size (GL_MAX_RECTANGLE_TEXTURE_SIZE) that is not big enough, some older graphics cards are limited to 4k. The warning message isn't very helpful, r7610 fixes that.

opengl should be enabled on this system if you keep your total screen size below that limit. (and you should.. opengl makes things a lot faster).
Or get a new graphics card.

Apart from that, this doesn't look like a bug to me!

comment:2 Changed 6 years ago by pyther

This is a brand new laptop with a haswell chip. Getting a newer graphic card is not an option. :-)

With 3 displays active, glxgears can generate about 60FPS.

$ glxgears 
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
339 frames in 5.0 seconds = 67.764 FPS
300 frames in 5.0 seconds = 59.883 FPS
300 frames in 5.0 seconds = 59.882 FPS
300 frames in 5.0 seconds = 59.884 FPS
300 frames in 5.0 seconds = 59.884 FPS
300 frames in 5.0 seconds = 59.884 FPS

It my understanding glxgears uses opengl.

comment:3 Changed 6 years ago by Antoine Martin

Resolution: invalid
Status: newclosed

I'm not sure if glxgears uses textures, but if it did, you would not be able to make its window bigger than 4k. Good to know that some haswell chips have this limit.

Feel free to attach the gl_check.py output to this ticket.

Closing this ticket as 'invalid' because we should not enable opengl if there is a risk we might have windows we cannot display. The code is working as expected.

comment:4 Changed 5 years ago by Antoine Martin

New developments in this area: #942, #976

Note: See TracTickets for help on using tickets.