Error of failed request badname named color or font does not exist xrandr

Есть два монитора. 1(SAMSUNG 76E) - подключен к видеокарте через шнур vga от монитора и переходник с vga на DVI(порт в видюхе), 2(LG) - подключен на прямую через dvi кабель(с ним проблем нет с разрешением). Командой xrandr получен: Screen 0: minim...


0

0

Есть два монитора. 1(SAMSUNG 76E) — подключен к видеокарте через шнур vga от монитора и переходник с vga на DVI(порт в видюхе), 2(LG) — подключен на прямую через dvi кабель(с ним проблем нет с разрешением).

Командой

получен:

Screen 0: minimum 8 x 8, current 2560 x 1080, maximum 16384 x 16384
DVI-I-0 connected 640x480+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   640x480       59.94*+
   320x240       60.05  
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-D-0 connected primary 1920x1080+640+0 (normal left inverted right x axis y axis) 477mm x 268mm
   1920x1080     60.00*+
   1680x1050     59.95  
   1280x1024     75.02    60.02  
   1152x864      75.00  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   640x480       75.00    59.94  
  1280x1024_60.00 (0x2ca) 109.000MHz -HSync +VSync
        h: width  1280 start 1368 end 1496 total 1712 skew    0 clock  63.67KHz
        v: height 1024 start 1027 end 1034 total 1063           clock  59.89Hz
  1024x768_60.00 (0x2cb) 63.500MHz -HSync +VSync
        h: width  1024 start 1072 end 1176 total 1328 skew    0 clock  47.82KHz
        v: height  768 start  771 end  775 total  798           clock  59.92Hz

В файле xorg.conf прописано следующее:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 361.42  (buildd@lgw01-18)  Tue Apr  5 14:33:28 UTC 2016

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    # HorizSync source: xconfig, VertRefresh source: xconfig
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "CRT-0"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 650 Ti"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-2"
    Option         "metamodes" "DVI-I-0: nvidia-auto-select +0+0, DVI-D-0: nvidia-auto-select +640+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Пробовал изменить разрешение http://forum.ubuntu.ru/index.php?topic=78813.0 этим способом.

На шаге 3, при создании

xrandr --newmode "1024x768_60.00"   63.50  1024 1072 1176 1328  768 771 775 798 -hsync +vsync

, терминал ответил:

X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  16 (RRCreateMode)
  Serial number of failed request:  37
  Current serial number in output stream:  37

Прочитал, что у кого-то работало если просто проигнорировать. Попробовал шаг 4.

xrandr --addmode DVI-I-0 1024x768_60.00

, ответ:

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  18 (RRAddOutputMode)
  Serial number of failed request:  37
  Current serial number in output stream:  38

После чего,

выдал тоже самое что и в первый раз

После чего я попробовал в xorg.config поправить:

...
Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-2"
    Option         "metamodes" "DVI-I-0: 1280x1024 +0+0, DVI-D-0: nvidia-auto-select +640+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

...

В списке разрешений ничего не добавилось, и сам монитор не изменил разрешение.

Вот что удалось нарыть в гугле для монитора:

#в xorg.conf сейчас не это
Section "Monitor"
    Identifier     "Monitor0"  
    VendorName     "STN"  
    ModelName      "S/T 77E/76E"  
    HorizSync       30.0 - 85.0  
    VertRefresh     50.0 - 160.0  
    Option         "DPMS"  
EndSection 

Помогите пожалуйста настроить xorg.conf для «проблемного» монитора, чтобы ему можно было изменить разрешение на 1024х768 или 1280х1024.
Всем откликнушивмся заранее спасибо!

@xnuken

I cannot seem to make a virtual screen i am on arch running kernel 5.0.8

Creating a Virtual Screen... Error: ['xrandr', '--newmode', '1440x900_virt', '106.50', '1440', '1528', '1672', '1904', '900', '903', '909', '934', '-hsync', '+vsync'] X Error of failed request: BadName (named color or font does not exist) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 16 (RRCreateMode) Serial number of failed request: 45 Current serial number in output stream: 45

@Rafael-Martins

Same error on Manjaro:

[‘xrandr’, ‘—newmode’, ‘1367x1024_virt’, ‘115.50’, ‘1368’, ‘1448’, ‘1592’, ‘1816’, ‘1024’, ‘1027’, ‘1037’, ‘1063’, ‘-hsync’, ‘+vsync’]
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 16 (RRCreateMode)
Serial number of failed request: 37
Current serial number in output stream: 37

@xnuken

@kbumsik

Hi guys, could you tell me the desktop environment (e.g. Gnome, KDE…) you use?

@xnuken

@beiju

I’m having the same error using Gnome. Some Google suggested that, for some reason, it’s caused by an underscore in the mode name. Sure enough, running xrandr --newmode "1368x1024_virt" 115.50 1368 1448 1592 1816 1024 1027 1037 1063 -hsync +vsync (the same command VirtScreen runs) fails, while running xrandr --newmode "1368x1024-virt" 115.50 1368 1448 1592 1816 1024 1027 1037 1063 -hsync +vsync (same thing but with the _ replaced with -) worked fine.

@penguinbing

Thank for your great job first, and I wonder is there any progress about this, I have the same mistake on ubuntu 18.04. @kbumsik

@aTosser

xrandr does not like the name for the mode, reran the exact command in terminal just replacing the name and it runs fine.

@Josempita

Any chance you could change the suffix VIRT_SCREEN_SUFFIX = «_virt» to VIRT_SCREEN_SUFFIX = «-virt» ? in xrandr.py

@tiengtinh

I also got the same problem on ubuntu 18.04

@EriKWDev

Ping! Same on Ubuntu 20.04, Gnome 3.36

ashishpatel1992, EriKWDev, sloorush, matsura8, syt0438, Sciroccogti, thetek42, jaimindevstree, AsadJivani, gwokudasam, and 2 more reacted with thumbs up emoji
itsshreyarora and jeong242 reacted with confused emoji

@ashishpatel1992

Same issue on Ubuntu 20.04 no solution yet!

@BenHall-1

Any solution for this?

Curently same error on pop_os 20.10

@zhouguannan

@Viper702

Hey,

Y’all might want to check ~/.profile of your user account —uid 1000 for something like this:

xrandr —newmode «1920x1080_60.00» 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync
xrandr —addmode LVDS-1 1920x1080_60.00
xrandr —output LVDS-1 —mode «1920x1080_60.00»

Comment all three of those out or remove from .profile and add to .xprofile instead if not already there. I duplicated the problem the other day while force setting my resolution on my laptop and stumbled across your forum while looking for the cause of that same annoying error message.

Hope this helps.

@LeKing233

Всем привет. Я решил познакомиться с Линуксом и столкнулся с проблемой: не получается выставить адекватное разрешение

Максимальное, которое могу поставить 1024 на 768, тогда как монитор 1920х1080

Видеокарта ДжиФорс 650 ТиАй, дрова стоят
Пробовал согласно инстркциям делать все через xrendr, но почему-то не работает. Ругается, какие-то ошибки выдает. Попробовал из репы поставить драйвера.
304 драйвер — полный абзац. Все крашится, раб стол отваливается
340 и 367. Ничего не меняется, кроме того что появляется приложение от Nvidea
Какой-то не Н-Видевский драйвер — разрешение падает до 640 на 480

В Нвидевском приложении пробовал насильно выставить нужное разрешение. Выставляется, но в итоге в левом верхнем углу рабочий стол с разрешением 1024 на 768, а все остальная область — черная.

Пожалуйста, направьте, подскажите… Кубунта очень приглянулась!!

При возможности пишите как можно проще, т.к. я с Линуксом и познакомиться толком не успел =(

P.S. При попытке добавить через консоль вот что получается

я:~$ xrandr

Screen 0: minimum 8 x 8, current 1024 x 768, maximum 16384 x 16384
VGA-0 connected primary 1024×768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1024×768 60.00*+
1360×768 59.96 59.80
1152×864 60.00
800×600 72.19 60.32 56.25
680×384 59.96 59.80
640×480 59.94
512×384 60.00
400×300 72.19
320×240 60.05
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)
DVI-D-1 disconnected (normal left inverted right x axis y axis)

я:~$ cvt 1920 1080 60

# 1920×1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 MHz
Modeline «1920x1080_60.00» 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync

я:~$ xrandr —newmode «1920x1080_60.00» 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync

X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 16 (RRCreateMode)
Serial number of failed request: 35
Current serial number in output stream: 35

я:~$ xrandr —addmode VGA-0 1920x1080_60.00

X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 18 (RRAddOutputMode)
Serial number of failed request: 35
Current serial number in output stream: 36

я:~$ xrandr —output VGA-0 —mode 1920x1080_60.00

xrandr: cannot find mode 1920x1080_60.00
[email protected]:~$

  • Печать

Страницы: [1] 2  Все   Вниз

Тема: Низкое разрешение в ubuntu 20.04  (Прочитано 2460 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
artem_2237

При очередном запуске компьютера вдруг сбросилось разрешение, монитор 1920х1080, но в настройках пишет «Неизвестный дисплей» и доступно только одно разрешение — 640х480.
Нашёл в интернете команды:
cvt 1920 1080 60

xrandr —newmode 1920x1080_60.00 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync

xrandr —addmode VGA-1-1 1920x1080_60.00

xrandr —output VGA-1-1 —mode 1920x1080_60.00.

Когда ввожу команду «xrandr —newmode 1920x1080_60.00 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync», получаю такую ошибку:

xrandr: Failed to get size of gamma for output default
X Error of failed request: BadName (named color or font does not exist)
  Major opcode of failed request: 140 (RANDR)
  Minor opcode of failed request: 16 (RRCreateMode)
  Serial number of failed request: 19
  Current serial number in output stream: 19

« Последнее редактирование: 11 Ноября 2021, 21:15:18 от Aleksandru »


Оффлайн
Pilot6

Нашёл в интернете команды:

Надо не команды в интернете искать, а понять что случилось с драйвером наверное

Я в личке не консультирую. Вопросы задавайте на форуме.


Оффлайн
artem_2237


Оффлайн
Pilot6

Ну я просто загуглил свою проблему

Это вы думаете что свою проблемы. У меня у папы тоже драйвер слетел. А он нагугил как панели на место в xfce вернуть.

Я в личке не консультирую. Вопросы задавайте на форуме.


Оффлайн
andytux

«Вдруг бывает только пук.»

При очередном запуске компьютера вдруг…

Вероятно было обновление. Или кто-то «пошалил».

xrandr —output VGA-1-1 —mode 1920x1080_60.00.

Откуда взял «VGA-1-1»? У тебя монитор подключен к VGA?
Запусти xrandr без параметров. Если в выводе нет ничего про «VGA-1-1», то и бесполезно лепить все остальные команды.

xrandr: Failed to get size of gamma for output default

Обычно ошибка возникает когда запущен «nomodeset-драйвер». Никаких других видеовходов и разрешений он не знает.


Оффлайн
Ro_112

Я прям исстрадался за это дело…спасибо что задали такой вопрос! :police:

Ноутбук Aspire E5-532 на борту Ubuntu Mate 21.04 LTS
2 Gb оперативы, карта NVidia, драйвер 390, 500 Gb HDD Toshiba


Оффлайн
andytux

Ro_112, что страдать. Этот вопрос обсуждался бесчетное количесво раз. Оглянись по сторонам, поищи.
Чтоб не скучать, загляни в эту тему. Она конечно совсем о другом, но о том-же самом.


Оффлайн
artem_2237

Откуда взял «VGA-1-1»? У тебя монитор подключен к VGA?

Я до этого шага ещё не доходил, у меня ошибка после этой команды — «xrandr —newmode 1920x1080_60.00 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync»

Обычно ошибка возникает когда запущен «nomodeset-драйвер»

Ввёл команду «sudo gedit /etc/default/grub». У меня есть там такая строка «GRUB_CMDLINE_LINUX_DEFAULT=»quiet splash», я так понимаю что nomodeset отключен, если я правильно понял что это

« Последнее редактирование: 13 Ноября 2021, 13:09:49 от artem_2237 »


Оффлайн
andytux

до этого шага ещё не доходил, у меня ошибка после этой команды — «xrandr —newmode

И это рано. Где вывод пустой xrandr? Выполнил-бы, увидел что он вообще понимает.

так понимаю что nomodeset отключен

Правильно понимаешь. Но если-бы почитал по ссылке в «Ответ 6», то увидел, что если никакие другие драйвера-режимы не работают, то система сама постарается загрузиться хотя-бы в этом режиме.


Оффлайн
artem_2237

Где вывод пустой xrandr?

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected primary 1024×768+0+0 0mm x 0mm
   1024×768       0.00*
   800×600        0.00 
   640×480        0.00 


Оффлайн
andytux

Ну вот он, красавец «nomodeset». И никакие другие режимы или видеовыходы применить ты его не заставишь.
Как видишь, нет никаких VGA. А к какому выходу у тебя подключен монитор ты так и не узнал. Мне он не нужен, но хоть ты сам узнаешь, что искать. Видеокарта какая?

« Последнее редактирование: 13 Ноября 2021, 14:39:13 от andytux »


Оффлайн
artem_2237

А к какому выходу у тебя подключен монитор ты так и не узнал. Мне он не нужен, но хоть ты сам узнаешь, что искать. Видеокарта какая?

Моник подключен через hdmi, видеокарта gtx 1650 4gb


Оффлайн
andytux

Вот если понадобится то hdmi и подставлять в хrandr, предварительно тамже посмотрев, как точно он обзывает этот видеовыход.
Драйвер какой был: nouveau или «проприетарный»? По драйверу и ищи на форуме, как восстановить его работу. По nVidia не подскажу.


Оффлайн
jurganov

xrandr —output VGA-1-1 —mode 1920x1080_60.00.

всё правильно!!
У автора инструкции  — VGA-1-1
Значит и тебе так же писать надо…


Оффлайн
andytux

«…чукча писатель.»
jurganov, прочитай хотя-бы «Ответ 9».
Опять-же, совет не для «писателя», поищи на форуме фразу: «Failed to get size of gamma».


  • Печать

Страницы: [1] 2  Все   Вверх

Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

LeV73_

Level 1
Level 1
Posts: 1
Joined: Fri Feb 21, 2020 2:27 am

Error of failed request: BadName (named color or font does not exist)

I have a problem setting up monitor resolution.
When i use

Code: Select all

xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync;

the error is showing up:

Code: Select all

Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  16 (RRCreateMode)
  Serial number of failed request:  31
  Current serial number in output stream:  31;

I used cvt command for resolution settings.
Monitor;Acer S243HL connected via VGA and DVI connector
Graphics Card:nVidia GeForce GTS 450 with latest recommended drivers

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.

Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

expedia

Level 1
Level 1
Posts: 2
Joined: Wed Apr 24, 2019 12:58 am

Re: Error of failed request: BadName (named color or font does not exist)

Post

by expedia » Mon Mar 28, 2022 1:23 pm

Hi roblm! Ihave same problem trying to set up HP 20kd
xrandr —newmode «1440x900_60.00» 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync

Here is output of inxi -SMCGx:

Code: Select all

System:    Host: Hotel Kernel: 5.4.0-105-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 
           Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic 
Machine:   Type: Desktop Mobo: Gigabyte model: P43T-ES3G serial: <root required> BIOS: Award v: F7 date: 08/20/2010 
CPU:       Topology: Dual Core model: Intel Core2 Duo E8400 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 6144 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 11999 
           Speed: 2000 MHz min/max: 2000/3000 MHz Core speeds (MHz): 1: 2000 2: 2000 
Graphics:  Device-1: NVIDIA GF116 [GeForce GTX 550 Ti] vendor: ZOTAC driver: nvidia v: 390.144 bus ID: 01:00.0 
           Display: x11 server: X.Org 1.19.6 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa 
           resolution: 1400x900~60Hz 
           OpenGL: renderer: GeForce GTX 550 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 390.144 direct render: Yes 

and xrandr —verbose:

Code: Select all

Screen 0: minimum 8 x 8, current 1400 x 900, maximum 16384 x 16384
DVI-I-0 connected primary 1400x900+0+0 (0x27f) normal (normal left inverted right x axis y axis) 0mm x 0mm
	Identifier: 0x27c
	Timestamp:  1921430
	Subpixel:   unknown
	Gamma:      1.0:1.0:1.0
	Brightness: 1.0
	Clones:    
	CRTC:       0
	CRTCs:      0 1
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: VGA 
		supported: VGA
	ConnectorType: DVI-I 
	ConnectorNumber: 0 
	_ConnectorLocation: 0 
  1024x768 (0x27d) 65.000MHz -HSync -VSync +preferred
        h: width  1024 start 1048 end 1184 total 1344 skew    0 clock  48.36KHz
        v: height  768 start  771 end  777 total  806           clock  60.00Hz
  1600x900 (0x27e) 97.500MHz +HSync -VSync
        h: width  1600 start 1648 end 1680 total 1760 skew    0 clock  55.40KHz
        v: height  900 start  903 end  908 total  926           clock  59.82Hz
  1400x900 (0x27f) 86.500MHz +HSync -VSync *current
        h: width  1400 start 1448 end 1480 total 1560 skew    0 clock  55.45KHz
        v: height  900 start  903 end  913 total  926           clock  59.88Hz
  1368x768 (0x280) 85.250MHz -HSync +VSync
        h: width  1368 start 1440 end 1576 total 1784 skew    0 clock  47.79KHz
        v: height  768 start  771 end  781 total  798           clock  59.88Hz
  1368x768 (0x281) 72.250MHz +HSync -VSync
        h: width  1368 start 1416 end 1448 total 1528 skew    0 clock  47.28KHz
        v: height  768 start  771 end  781 total  790           clock  59.85Hz
  1360x768 (0x282) 72.000MHz +HSync -VSync
        h: width  1360 start 1408 end 1440 total 1520 skew    0 clock  47.37KHz
        v: height  768 start  771 end  781 total  790           clock  59.96Hz
  1360x768 (0x283) 84.750MHz -HSync +VSync
        h: width  1360 start 1432 end 1568 total 1776 skew    0 clock  47.72KHz
        v: height  768 start  771 end  781 total  798           clock  59.80Hz
  1280x800 (0x284) 71.000MHz +HSync -VSync
        h: width  1280 start 1328 end 1360 total 1440 skew    0 clock  49.31KHz
        v: height  800 start  803 end  809 total  823           clock  59.91Hz
  1280x800 (0x285) 83.500MHz -HSync +VSync
        h: width  1280 start 1352 end 1480 total 1680 skew    0 clock  49.70KHz
        v: height  800 start  803 end  809 total  831           clock  59.81Hz
  1280x720 (0x286) 74.500MHz -HSync +VSync
        h: width  1280 start 1344 end 1472 total 1664 skew    0 clock  44.77KHz
        v: height  720 start  723 end  728 total  748           clock  59.86Hz
  1280x720 (0x287) 63.750MHz +HSync -VSync
        h: width  1280 start 1328 end 1360 total 1440 skew    0 clock  44.27KHz
        v: height  720 start  723 end  728 total  741           clock  59.74Hz
  1152x864 (0x288) 81.620MHz -HSync +VSync
        h: width  1152 start 1216 end 1336 total 1520 skew    0 clock  53.70KHz
        v: height  864 start  865 end  868 total  895           clock  60.00Hz
  1024x576 (0x289) 46.500MHz -HSync +VSync
        h: width  1024 start 1064 end 1160 total 1296 skew    0 clock  35.88KHz
        v: height  576 start  579 end  584 total  599           clock  59.90Hz
  1024x576 (0x28a) 42.000MHz +HSync -VSync
        h: width  1024 start 1072 end 1104 total 1184 skew    0 clock  35.47KHz
        v: height  576 start  579 end  584 total  593           clock  59.82Hz
  960x540 (0x28b) 37.250MHz +HSync -VSync
        h: width   960 start 1008 end 1040 total 1120 skew    0 clock  33.26KHz
        v: height  540 start  543 end  548 total  556           clock  59.82Hz
  960x540 (0x28c) 40.750MHz -HSync +VSync
        h: width   960 start  992 end 1088 total 1216 skew    0 clock  33.51KHz
        v: height  540 start  543 end  548 total  562           clock  59.63Hz
  864x486 (0x28d) 32.500MHz -HSync +VSync
        h: width   864 start  888 end  968 total 1072 skew    0 clock  30.32KHz
        v: height  486 start  489 end  494 total  506           clock  59.92Hz
  864x486 (0x28e) 30.500MHz +HSync -VSync
        h: width   864 start  912 end  944 total 1024 skew    0 clock  29.79KHz
        v: height  486 start  489 end  494 total  500           clock  59.57Hz
  800x600 (0x28f) 50.000MHz +HSync +VSync
        h: width   800 start  856 end  976 total 1040 skew    0 clock  48.08KHz
        v: height  600 start  637 end  643 total  666           clock  72.19Hz
  800x600 (0x290) 40.000MHz +HSync +VSync
        h: width   800 start  840 end  968 total 1056 skew    0 clock  37.88KHz
        v: height  600 start  601 end  605 total  628           clock  60.32Hz
  800x600 (0x291) 36.000MHz +HSync +VSync
        h: width   800 start  824 end  896 total 1024 skew    0 clock  35.16KHz
        v: height  600 start  601 end  603 total  625           clock  56.25Hz
  800x450 (0x292) 48.750MHz +HSync -VSync DoubleScan
        h: width   800 start  824 end  840 total  880 skew    0 clock  55.40KHz
        v: height  450 start  451 end  454 total  463           clock  59.82Hz
  700x450 (0x293) 43.250MHz +HSync -VSync DoubleScan
        h: width   700 start  724 end  740 total  780 skew    0 clock  55.45KHz
        v: height  450 start  451 end  456 total  463           clock  59.88Hz
  684x384 (0x294) 42.625MHz -HSync +VSync DoubleScan
        h: width   684 start  720 end  788 total  892 skew    0 clock  47.79KHz
        v: height  384 start  385 end  390 total  399           clock  59.88Hz
  684x384 (0x295) 36.125MHz +HSync -VSync DoubleScan
        h: width   684 start  708 end  724 total  764 skew    0 clock  47.28KHz
        v: height  384 start  385 end  390 total  395           clock  59.85Hz
  680x384 (0x296) 36.000MHz +HSync -VSync DoubleScan
        h: width   680 start  704 end  720 total  760 skew    0 clock  47.37KHz
        v: height  384 start  385 end  390 total  395           clock  59.96Hz
  680x384 (0x297) 42.375MHz -HSync +VSync DoubleScan
        h: width   680 start  716 end  784 total  888 skew    0 clock  47.72KHz
        v: height  384 start  385 end  390 total  399           clock  59.80Hz
  640x480 (0x298) 25.175MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.47KHz
        v: height  480 start  490 end  492 total  525           clock  59.94Hz
  640x400 (0x299) 35.500MHz +HSync -VSync DoubleScan
        h: width   640 start  664 end  680 total  720 skew    0 clock  49.31KHz
        v: height  400 start  401 end  404 total  411           clock  59.98Hz
  640x400 (0x29a) 41.750MHz -HSync +VSync DoubleScan
        h: width   640 start  676 end  740 total  840 skew    0 clock  49.70KHz
        v: height  400 start  401 end  404 total  415           clock  59.88Hz
  640x360 (0x29b) 37.250MHz -HSync +VSync DoubleScan
        h: width   640 start  672 end  736 total  832 skew    0 clock  44.77KHz
        v: height  360 start  361 end  364 total  374           clock  59.86Hz
  640x360 (0x29c) 31.875MHz +HSync -VSync DoubleScan
        h: width   640 start  664 end  680 total  720 skew    0 clock  44.27KHz
        v: height  360 start  361 end  364 total  370           clock  59.83Hz
  512x384 (0x29d) 32.500MHz -HSync -VSync DoubleScan
        h: width   512 start  524 end  592 total  672 skew    0 clock  48.36KHz
        v: height  384 start  385 end  388 total  403           clock  60.00Hz
  512x288 (0x29e) 23.250MHz -HSync +VSync DoubleScan
        h: width   512 start  532 end  580 total  648 skew    0 clock  35.88KHz
        v: height  288 start  289 end  292 total  299           clock  60.00Hz
  512x288 (0x29f) 21.000MHz +HSync -VSync DoubleScan
        h: width   512 start  536 end  552 total  592 skew    0 clock  35.47KHz
        v: height  288 start  289 end  292 total  296           clock  59.92Hz
  480x270 (0x2a0) 18.625MHz +HSync -VSync DoubleScan
        h: width   480 start  504 end  520 total  560 skew    0 clock  33.26KHz
        v: height  270 start  271 end  274 total  278           clock  59.82Hz
  480x270 (0x2a1) 20.375MHz -HSync +VSync DoubleScan
        h: width   480 start  496 end  544 total  608 skew    0 clock  33.51KHz
        v: height  270 start  271 end  274 total  281           clock  59.63Hz
  432x243 (0x2a2) 16.250MHz -HSync +VSync DoubleScan
        h: width   432 start  444 end  484 total  536 skew    0 clock  30.32KHz
        v: height  243 start  244 end  247 total  253           clock  59.92Hz
  432x243 (0x2a3) 15.250MHz +HSync -VSync DoubleScan
        h: width   432 start  456 end  472 total  512 skew    0 clock  29.79KHz
        v: height  243 start  244 end  247 total  250           clock  59.57Hz
  400x300 (0x2a4) 25.000MHz +HSync +VSync DoubleScan
        h: width   400 start  428 end  488 total  520 skew    0 clock  48.08KHz
        v: height  300 start  318 end  321 total  333           clock  72.19Hz
  320x240 (0x2a5) 12.587MHz -HSync -VSync DoubleScan
        h: width   320 start  328 end  376 total  400 skew    0 clock  31.47KHz
        v: height  240 start  245 end  246 total  262           clock  60.05Hz
DVI-I-1 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x2a6
	Timestamp:  1921430
	Subpixel:   unknown
	Clones:    
	CRTCs:      0 1
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: VGA 
		supported: VGA
	ConnectorType: DVI-I 
	ConnectorNumber: 1 
	_ConnectorLocation: 1 
DVI-I-2 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x2a7
	Timestamp:  1921430
	Subpixel:   unknown
	Clones:    
	CRTCs:      0 1
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: TMDS 
		supported: TMDS
	ConnectorType: DVI-I 
	ConnectorNumber: 0 
	_ConnectorLocation: 0 
HDMI-0 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x2a8
	Timestamp:  1921430
	Subpixel:   unknown
	Clones:    
	CRTCs:      0 1
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: TMDS 
		supported: TMDS
	ConnectorType: HDMI 
	ConnectorNumber: 2 
	_ConnectorLocation: 2 
DP-0 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x2a9
	Timestamp:  1921430
	Subpixel:   unknown
	Clones:    
	CRTCs:      0 1
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: TMDS 
		supported: TMDS
	ConnectorType: DisplayPort 
	ConnectorNumber: 3 
	_ConnectorLocation: 3 
DVI-I-3 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x2aa
	Timestamp:  1921430
	Subpixel:   unknown
	Clones:    
	CRTCs:      0 1
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: TMDS 
		supported: TMDS
	ConnectorType: DVI-I 
	ConnectorNumber: 1 
	_ConnectorLocation: 1 
DP-1 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x2ab
	Timestamp:  1921430
	Subpixel:   unknown
	Clones:    
	CRTCs:      0 1
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: DisplayPort 
		supported: DisplayPort
	ConnectorType: DisplayPort 
	ConnectorNumber: 3 
	_ConnectorLocation: 3 
  1440x900_60.00 (0x2da) 106.500MHz -HSync +VSync
        h: width  1440 start 1528 end 1672 total 1904 skew    0 clock  55.93KHz
        v: height  900 start  903 end  909 total  934           clock  59.89Hz

Thank you in advance for your assistance!

  • Index
  • » Newbie Corner
  • » [SOLVED] Correcting overscan with xrandr… [SOLVED]

#1 2012-07-17 02:02:24

HalJordan
Member
Registered: 2010-11-17
Posts: 64

[SOLVED] Correcting overscan with xrandr… [SOLVED]

I am with Linus on hating Nvidia…..
Before the 300 series driver, the overscan compensation worked perfectly. I set it to 76, whatever that translated to on the border sizes, and saw my entire desktop.
I have searched high and low, and the only solutions that I’ve seen worked for other people either were undocumented (ie they said «I fixed it with xrandr» and nothing else), or I get errors. I’ve been stuck not being able to see whats on the edges of my screen, including my panel, and half my my awn dock.

So far this is what I’ve tried. PLEASE tell me there’s something I’ve missed, or something I’ve misspelled…

hal@oa ~ >  xrandr --output HDMI-0 --set underscan on
X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  153 (RANDR)
  Minor opcode of failed request:  11 (RRQueryOutputProperty)
  Serial number of failed request:  33
  Current serial number in output stream:  33
hal@oa ~ >  xrandr --output HDMI-0 --set underscan off
X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  153 (RANDR)
  Minor opcode of failed request:  11 (RRQueryOutputProperty)
  Serial number of failed request:  33
  Current serial number in output stream:  33
hal@oa ~ >  xrandr --output HDMI-0 --fb 1920x1080 --mode 1920x1080 --panning 1900x1060+10+10
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  153 (RANDR)
  Minor opcode of failed request:  29 (RRSetPanning)
  Serial number of failed request:  33
  Current serial number in output stream:  33

Last edited by HalJordan (2012-07-18 00:30:02)

#2 2012-07-17 08:51:06

Minsc
Member
Registered: 2012-07-16
Posts: 95

Re: [SOLVED] Correcting overscan with xrandr… [SOLVED]

Is HDMI-0 listed in

Check your device listing as I suspect you’ve got the name of it wrong.

You might also want to check this, specifically the section on —fb, which you don’t need.

Last edited by Minsc (2012-07-17 08:51:42)

#3 2012-07-17 23:36:03

HalJordan
Member
Registered: 2010-11-17
Posts: 64

Re: [SOLVED] Correcting overscan with xrandr… [SOLVED]

You mean here?

hal@oa ~ > xrandr -q 
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
DVI-I-2 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 700mm x 390mm
   1280x720       60.0 +   59.9     50.0  
   1920x1080      59.9*    50.0     30.0     25.0     24.0     30.0     30.0     25.0  
   1024x768       60.0  
   800x600        60.3  
   720x576        50.0     25.0  
   720x480        60.0     59.9     30.0  
DVI-I-3 disconnected (normal left inverted right x axis y axis)

And this might explain why the underscan on/off didn’t work. _Nothing_ is listed as a property under HDMI-0, or anything else for that matter…

hal@oa ~ > xrandr --props
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
DVI-I-2 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 700mm x 390mm
	EDID:
		00ffffffffffff003683010be9030000
		01120103804627780a1990a755469824
		10494b01080001010101010101010101
		010101010101011d007251d01e206e28
		5500c48e2100001e011d8018711c1620
		582c2500c48e2100009e000000fc004d
		544332365434320a20202020000000fd
		0016500e5b10000a202020202020019a
		020322724d0384050710129314161f20
		212223097f078301000067030c001000
		98298f0ad08a20e02d10103e9600c48e
		21000018011d00bc52d01e20b8285540
		c48e2100001e011d80d0721c1620102c
		2580c48e2100009e8c0ad09020403120
		0c405500c48e210000188c0ad08a20e0
		2d10103e9600c48e2100001800000037
   1280x720       60.0 +   59.9     50.0  
   1920x1080      59.9*    50.0     30.0     25.0     24.0     30.0     30.0     25.0  
   1024x768       60.0  
   800x600        60.3  
   720x576        50.0     25.0  
   720x480        60.0     59.9     30.0  
DVI-I-3 disconnected (normal left inverted right x axis y axis)

Not to mention, he’s going for making the screen bigger than his monitor, I’m on a tv with fuggly overscan, and now way to turn it off.(That’s what I get for buying one on sale…) I want to shrink what is shown, and keep it centered. According to nvidia’s readme, they removed the overscan compensation because the xrandr implementation was easier and better…. HOW is this easier than moving a slider left and right till it’s fixed??

Last edited by HalJordan (2012-07-17 23:41:44)

#4 2012-07-17 23:45:16

Gusar
Member
Registered: 2009-08-25
Posts: 3,605

Re: [SOLVED] Correcting overscan with xrandr… [SOLVED]

You should play with MetaModes, in particular with ViewPortIn and ViewPortOut. There were cool examples on how to use them for overscan compensation at the nvnews.net forums, but the Linux section there is locked currently. Don’t ask why, let me just say the nvnews.net owner is <continuing this sentence would put me in violation of the Arch Forum Etiquette>

Where exactly did the documentation say the new way is easier, though? All I recall it saying is that it’s more flexible. Which is true, the ViewPortIn/Out stuff is extremely flexible. And they plan very much to add simpler controls to nvidia-settings, they just didn’t get to it yet.

Also, be mad at your TV. I can tell mine what kind of output it’s receiving, and I simply told it it’s a computer, so it knows not to do stupid things to the picture. And finally, Nvidia also provides a long-lived branch (295) if the 3xx series is too bleeding-edge for you.

Last edited by Gusar (2012-07-17 23:51:59)

#5 2012-07-17 23:49:18

HalJordan
Member
Registered: 2010-11-17
Posts: 64

Re: [SOLVED] Correcting overscan with xrandr… [SOLVED]

WOW that was quick…(observation, not a complaint…)

Gusar wrote:

You should play with MetaModes, in particular with ViewPortIn and ViewPortOut. There were cool examples on how to use them for overscan compensation at the nvnews.net forums, but the Linux section there is locked currently. Don’t ask why, let me just say the nvnews.net owner is <continuing this sentence would put me in violation of the Arch Forum Etiquette>

Yeah a good handfull of _really_ usefull looking articles I saw on google were on there, and thus out of reach. They had another breach like the one to their store, and decided to pull the plug till they could clean it up. I hope its not gonna take as long as kernel.org took…

And can the ViewportIn/Out be set in Nvidia settings, or does it have to be done in xorg.conf.d-or-xorg.conf? It’s gonna be a pita to go through and fiddle with the numbers, then restart X and hope it worked, rinse/repeat…

#6 2012-07-17 23:58:30

Gusar
Member
Registered: 2009-08-25
Posts: 3,605

Re: [SOLVED] Correcting overscan with xrandr… [SOLVED]

HalJordan wrote:

And can the ViewportIn/Out be set in Nvidia settings, or does it have to be done in xorg.conf.d-or-xorg.conf? It’s gonna be a pita to go through and fiddle with the numbers, then restart X and hope it worked, rinse/repeat…

It can be done with nvidia-settings. Not the GUI, but on the command-line, and the option takes effect immediately, no need to restart X. If I could only remember how exactly. The Nvidia devs for sure explained it… at the currently locked nvnews.net forums…

Edit: Google Cache to the rescue, I found it:

nvidia-settings --assign CurrentMetaMode="DFP-0: 1920x1200 { ViewPortIn=1280x1024, ViewPortOut=1500x1200+210+0}"

Fiddle with the numbers accordingly. This might be helpful: http://askubuntu.com/questions/130088/o … ts-upgrade

Last edited by Gusar (2012-07-18 00:03:40)

#7 2012-07-18 00:29:34

HalJordan
Member
Registered: 2010-11-17
Posts: 64

Re: [SOLVED] Correcting overscan with xrandr… [SOLVED]

Thanks fiddling now, I just went with sudo leafpad /etc/X11/xorg.conf & sudo systemctl restart slim.service.
Lost most of my panel the first time, just copy/pasted the one near the end, I didnt notice the +1600+0 he uses for the second monitor that I don’t have.

#8 2014-10-21 06:53:26

kokoko3k
Member
Registered: 2008-11-14
Posts: 2,343

Re: [SOLVED] Correcting overscan with xrandr… [SOLVED]

i don’t know if this answer your question, but:

xrandr --output VGA-1 --mode 1920x1080 --panning 2880x1620

…would create a desktop bigger than the monitor resolution. It will pan when the mouse reaches the borders.
(change VGA-1 to match your setup)

EDIT-
Ops, didn’t see the thread was SOLVED, sorry.

Last edited by kokoko3k (2014-10-21 07:06:32)


Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !

#9 2014-10-21 12:41:52

HalJordan
Member
Registered: 2010-11-17
Posts: 64

Re: [SOLVED] Correcting overscan with xrandr… [SOLVED]

That was over two years ago. I’ve since replaced that tv with a proper monitor. No fiddling necessary. No stretched view, and fonts are much more readable. Won’t make the mistake of using a TV for a monitor ever again.

#10 2014-10-21 13:03:43

fsckd
Forum Fellow
Registered: 2009-06-15
Posts: 4,173

Re: [SOLVED] Correcting overscan with xrandr… [SOLVED]

Not just solved, double solved! big_smile

Closing to prevent further bumps, as per our policy.


aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies

Понравилась статья? Поделить с друзьями:
  • Error of command sending rcpt to
  • Error of acquiring bank or network
  • Error occurs on ace components
  • Error occurs in the template of component logincomponent
  • Error occurs in the template of component appcomponent