Cannot get native 1024×600 resolution with xrandr etc.

[Member anti-ewaste]

Hi,

Just installed 19.2 full and I’m stuck at 800×600, checked the Screen Layout Editor, tried cvt and xrandr with the following:

$ cvt 1024 600
# 1024×600 59.85 Hz (CVT) hsync: 37.35 kHz; pclk: 49.00 MHz
Modeline “1024x600_60.00” 49.00 1024 1072 1168 1312 600 603 613 624 -hsync +vsync

$ xrandr –newmode “1024x600_60.00” 49.00 1024 1072 1168 1312 600 603 613 624 -hsync +vsync
xrandr: Failed to get size of gamma for output default

$ xrandr –addmode “1024x600_60.00” 49.00 1024 1072 1168 1312 600 603 613 624 -hsync +vsync
xrandr: unrecognized option ‘1024’
Try ‘xrandr –help’ for more information.

Is it a driver issue? I’m on the ASUS Eee PC 1000HD and I understand it is an Intel Integrated GMA 900 with WSVGA.

• This topic was modified 2 years, 8 months ago by anti-ewaste.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Use arandr in the control centre.
It might work better.
If not, then you’re probably out of luck with a buster based distro and you need an earlier version.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member anti-ewaste]

Helpful

Up

0

::

Yeah I tried that first.. 1024×600 is not listed.

Does this matter/help:
———
$ inxi -F
Graphics:
Device-1: Intel Mobile 915GM/GMS/910GML Express Graphics driver: N/A
Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 800×600~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6

$ glxinfo | grep vendor
server glx vendor string: SGI
client glx vendor string: Mesa Project and SGI
OpenGL vendor string: VMware, Inc.

$ glxinfo | grep render
direct rendering: Yes
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_query_renderer,
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth,
GL_MESA_ycbcr_texture, GL_NV_conditional_render, GL_NV_depth_clamp,
GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth,
GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_fog_distance,
GL_OES_element_index_uint, GL_OES_fbo_render_mipmap,

• This reply was modified 2 years, 8 months ago by anticapitalista.
• This reply was modified 2 years, 8 months ago by anti-ewaste.
• This reply was modified 2 years, 8 months ago by anti-ewaste.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Seems like the latest org in buster (antiX-19) no longer supports your video driver.
It falls back to vesa.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member anti-ewaste]

Helpful

Up

0

::

Ahh thanks, I think I can live with 800×600 in favor of a less preferrable distro. 🙂

EDIT: Downloading 17.4.1

• This reply was modified 2 years, 8 months ago by anti-ewaste.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Can you try antiX-17.4.1 (stretch-based, supported for another 3 years)? Just to see if that works better.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member anti-ewaste]

Helpful

Up

0

::

Yep 17.4.1 works straight from the live disk. Can we assume they won’t bother to support this driver going forward?

[Member cyrilus31]

Helpful

Up

0

::

A bit late, and maybe a no-go but addmode syntax is the following :

xrandr –addmode OUTPUT (VGA or LVDS or whatever your output) NAME (1024x600_60.00 in your case)

[Author]

Posts