Resolution Won't Change on Headless Linux Box?

 
Thread Tools Search this Thread
Top Forums UNIX for Beginners Questions & Answers Resolution Won't Change on Headless Linux Box?
# 1  
Old 04-26-2017
Resolution Won't Change on Headless Linux Box?

Hello All,

Wasn't sure if I was supposed to post this under Hardware so posting here...

Device: CuBox-i
OS: OpenSuSE 13.1
Uname: Linux CuBox-PC 3.14.14-cubox-i #1 SMP Sat Sep 13 03:48:24 UTC 2014 armv7l armv7l armv7l GNU/Linux
Window Manager: XFCE
Display Manager: lightdm (*XDM?)

I have a few of these devices in our remote branch office locations for network management and I can connect to them via SSH or VNC. I am using x11vnc for remote vnc access so I can control Screen :0 of the device.

By default the device does not have an xorg.conf file.

So without connecting a monitor to the HDMI port (*which is the only display port), it defaults to 1920x1080. After many many attempts to change the resolution via xrandr I have been unable to do so. I attempted creating new modes for just about every common resolution I can think of using "cvt" and "gtf" but each time it fails to change the resolution.

In reading a few other posts I downloaded and installed the Xorg dummy driver and created an xorg.conf file so it could use the driver. But, the largest display size that would work with this driver was 1024x768. All attempts to add new resolutions and then use them failed. I was able to add new resolutions that display in xrandr's output, but when attempting to switch to them it would fail.

Here's an Example using Default Settings (*i.e. no dummy driver and no xorg.conf file):
Code:
CuBox-PC:~ # xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
   1920x1080      60.0* 
CuBox-PC:~ #
CuBox-PC:~ # cvt 1600 900 60
# 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz
Modeline "1600x900_60.00"  118.25  1600 1696 1856 2112  900 903 908 934 -hsync +vsync
CuBox-PC:~ #
CuBox-PC:~ # xrandr --newmode "1600x900"  118.25  1600 1696 1856 2112  900 903 908 934 -hsync +vsync
xrandr: Failed to get size of gamma for output default
CuBox-PC:~ # xrandr --addmode default "1600x900"
xrandr: Failed to get size of gamma for output default
CuBox-PC:~ # 
CuBox-PC:~ # xrandr --verbose
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1600 x 900, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 (0x17a) normal (normal) 0mm x 0mm
    Identifier: 0x179
    Timestamp:  64566553
    Subpixel:   unknown
    Clones:    
    CRTC:       0
    CRTCs:      0
    Transform:  1.000000 0.000000 0.000000
                0.000000 1.000000 0.000000
                0.000000 0.000000 1.000000
               filter: 
  1920x1080 (0x17a)  124.4MHz *current
        h: width  1920 start    0 end    0 total 1920 skew    0 clock   64.8KHz
        v: height 1080 start    0 end    0 total 1080           clock   60.0Hz
  1600x900 (0x1cc)  118.2MHz -HSync +VSync
        h: width  1600 start 1696 end 1856 total 2112 skew    0 clock   56.0KHz
        v: height  900 start  903 end  908 total  934           clock   59.9Hz
CuBox-PC:~ # 
CuBox-PC:~ # xrandr --output default --mode 1600x900
xrandr: Failed to get size of gamma for output default
xrandr: Configure crtc 0 failed
CuBox-PC:~ #

I believe the default driver used is something like "mxc_hdmi". I haven't tried creating an xorg.conf file using that as the driver. But, not sure if it would make a difference if it was in a xorg.conf file if it's not working with xrandr...

If anyone has any thoughts or suggestion, it would be greatly appreciated!

Thanks in Advance,
Matt
# 2  
Old 04-26-2017
Are you missing terminal drivers or does it have a a graphics card?
Is SDB relevant or not?

SDB:Configuring graphics cards - openSUSE
# 3  
Old 04-27-2017
Hey Jim, thanks for the reply.

I would assume it has a graphics card if it has an HDMI port, right? I've been trying to figure out what the Graphics card is, but the lspci command produces no output at all. I did get output from hwinfo, but the only thing that seems relevant is the driver "mxc_hdmi".

Other then that I'm not really sure.

I found this info below, in the hwinfo output... Sorry, if its not related to what you're asking.
Code:
  P: /devices/virtual/mxc_hdmi/mxc_hdmi
  N: mxc_hdmi
  E: DEVNAME=/dev/mxc_hdmi
  E: DEVPATH=/devices/virtual/mxc_hdmi/mxc_hdmi
  E: MAJOR=247
  E: MINOR=0
  E: SUBSYSTEM=mxc_hdmi
  
  P: /devices/virtual/mxc_hdmi_cec/mxc_hdmi_cec
  N: mxc_hdmi_cec
  E: DEVNAME=/dev/mxc_hdmi_cec
  E: DEVPATH=/devices/virtual/mxc_hdmi_cec/mxc_hdmi_cec
  E: MAJOR=243
  E: MINOR=0
  E: SUBSYSTEM=mxc_hdmi_cec
  
  P: /devices/virtual/mxc_ipu/mxc_ipu
  N: mxc_ipu
  E: DEVNAME=/dev/mxc_ipu
  E: DEVPATH=/devices/virtual/mxc_ipu/mxc_ipu
  E: MAJOR=249
  E: MINOR=0
  E: SUBSYSTEM=mxc_ipu
  
  P: /devices/virtual/mxc_vpu/mxc_vpu
  N: mxc_vpu
  E: DEVNAME=/dev/mxc_vpu
  E: DEVPATH=/devices/virtual/mxc_vpu/mxc_vpu
  E: MAJOR=244
  E: MINOR=0
  E: SUBSYSTEM=mxc_vpu

  P: /devices/soc0/soc.1/120000.hdmi_core
  E: DEVPATH=/devices/soc0/soc.1/120000.hdmi_core
  E: DRIVER=mxc_hdmi_core
  E: MODALIAS=of:Nhdmi_coreT<NULL>Cfsl,imx6dl-hdmi-core
  E: OF_COMPATIBLE_0=fsl,imx6dl-hdmi-core
  E: OF_COMPATIBLE_N=1
  E: OF_FULLNAME=/soc/hdmi_core@00120000
  E: OF_NAME=hdmi_core
  E: SUBSYSTEM=platform

  P: /devices/soc0/soc.1/130000.gpu
  E: DEVPATH=/devices/soc0/soc.1/130000.gpu
  E: DRIVER=galcore
  E: MODALIAS=of:NgpuT<NULL>Cfsl,imx6dl-gpuCfsl,imx6q-gpu
  E: OF_COMPATIBLE_0=fsl,imx6dl-gpu
  E: OF_COMPATIBLE_1=fsl,imx6q-gpu
  E: OF_COMPATIBLE_N=2
  E: OF_FULLNAME=/soc/gpu@00130000
  E: OF_NAME=gpu
  E: SUBSYSTEM=platform



            galcore: /devices/soc0/soc.1/130000.gpu
         mxc_vpu: /devices/soc0/soc.1/2000000.aips-bus/2040000.vpu
        mxc_asrc: /devices/soc0/soc.1/2000000.aips-bus/2000000.spba-bus/2034000.asrc
        mxc_hdmi: /devices/soc0/soc.1/20e0000.hdmi_video
        mxc_vdoa: /devices/soc0/soc.1/2100000.aips-bus/21e4000.vdoa
         mxs-dma: /devices/soc0/soc.1/110000.dma-apbh

  platform device: name = 130000.gpu
    path = /devices/soc0/soc.1/130000.gpu
    type = "of:NgpuT<NULL>Cfsl,imx6dl-gpuCfsl,imx6q-gpu"

If you have any commands you would like me to run to get you more info, just let me know.

Thanks again for the reply, much appreciated.

-Matt

---------- Post updated at 06:07 PM ---------- Previous update was at 04:10 PM ----------

After just Googling around a bit for the "imx6dl GPU", which you can see in the hwinfo output I posted. It seems like it's part of the Vivante Graphics Card... Does that sound correct?

And after learning Vivante might be the Graphics card, I checked the hwinfo output again and found:
Code:
  P: /devices/platform/Vivante GCCore/drm/card0
  N: dri/card0
  E: DEVNAME=/dev/dri/card0
  E: DEVPATH=/devices/platform/Vivante GCCore/drm/card0
  E: DEVTYPE=drm_minor
  E: ID_FOR_SEAT=drm-platform-Vivante_GCCore
  E: ID_PATH=platform-Vivante GCCore
  E: ID_PATH_TAG=platform-Vivante_GCCore
  E: MAJOR=226
  E: MINOR=0
  E: SUBSYSTEM=drm
  E: TAGS=:seat:uaccess:
  E: USEC_INITIALIZED=135504

I've been racking my brain trying to find the command I used yesterday, but I cannot seem to find what it was. But I remember running a command yesterday and in the output was "GC880", which in Googling it, its a Vivante imx6 GPU...

-Matt

---------- Post updated at 07:13 PM ---------- Previous update was at 06:07 PM ----------

***UPDATE***

I think I might have figured out a solution..! I'll post back tomorrow with what I did and hopefully someone can tell me if it would/could cause any issues going forward...

Thanks,
Matt

---------- Post updated 04-27-17 at 03:46 PM ---------- Previous update was 04-26-17 at 07:13 PM ----------

So in looking at the Xorg.0.log file I noticed X was looking for display drivers in the directory /usr/lib/xorg/modules/drivers/.

Code:
CuBox-PC:~ # cat /var/log/Xorg.0.log | grep -i ModulePath
# cat /var/log/Xorg.0.log | grep -i ModulePath
[ 87517.193] (==) ModulePath set to "/usr/lib/xorg/modules/updates,/usr/lib/xorg/modules"

I decided to try the driver located in this directory called fbdev_drv.so in my xorg.conf file. Stopped and Started the Xserver again and this time it now allows me to change the Screen size to almost whatever I want...

Here's my xorg.conf file containing a bunch of Modelines for different resolutions.
*Modelines from the "cvt" command...
Code:
Section "Monitor"
    Identifier    "Monitor0"
    VertRefresh    50.0 - 70.0
    HorizSync    31.0 - 69.0
    # 1920x1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 MHz
    Modeline "1920x1080"  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync
    # 1680x1050 59.95 Hz (CVT 1.76MA) hsync: 65.29 kHz; pclk: 146.25 MHz
    Modeline "1680x1050"  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync
    # 1600x1200 59.87 Hz (CVT 1.92M3) hsync: 74.54 kHz; pclk: 161.00 MHz
    #Modeline "1600x1200"  161.00  1600 1712 1880 2160  1200 1203 1207 1245 -hsync +vsync
    # 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz
    Modeline "1600x900"  118.25  1600 1696 1856 2112  900 903 908 934 -hsync +vsync
    # 1440x900 59.89 Hz (CVT 1.30MA) hsync: 55.93 kHz; pclk: 106.50 MHz
    Modeline "1440x900"  106.50  1440 1528 1672 1904  900 903 909 934 -hsync +vsync
    # 1400x1050 59.98 Hz (CVT 1.47M3) hsync: 65.32 kHz; pclk: 121.75 MHz
    Modeline "1400x1050"  121.75  1400 1488 1632 1864  1050 1053 1057 1089 -hsync +vsync
    # 1280x1024 59.89 Hz (CVT 1.31M4) hsync: 63.67 kHz; pclk: 109.00 MHz
    Modeline "1280x1024"  109.00  1280 1368 1496 1712  1024 1027 1034 1063 -hsync +vsync
    # 1280x960 59.94 Hz (CVT 1.23M3) hsync: 59.70 kHz; pclk: 101.25 MHz
    Modeline "1280x960"  101.25  1280 1360 1488 1696  960 963 967 996 -hsync +vsync
    # 1280x720 59.86 Hz (CVT 0.92M9) hsync: 44.77 kHz; pclk: 74.50 MHz
    Modeline "1280x720"   74.50  1280 1344 1472 1664  720 723 728 748 -hsync +vsync
    # 1024x768 59.92 Hz (CVT 0.79M3) hsync: 47.82 kHz; pclk: 63.50 MHz
    Modeline "1024x768"   63.50  1024 1072 1176 1328  768 771 775 798 -hsync +vsync
    # 800x600 59.86 Hz (CVT 0.48M3) hsync: 37.35 kHz; pclk: 38.25 MHz
    Modeline "800x600"   38.25  800 832 912 1024  600 603 607 624 -hsync +vsync
    # 640x480 59.38 Hz (CVT 0.31M3) hsync: 29.69 kHz; pclk: 23.75 MHz
    Modeline "640x480"   23.75  640 664 720 800  480 483 487 500 -hsync +vsync
EndSection

Section "Device"
    Identifier    "Card0"
    Driver        "fbdev"
EndSection

Section "Screen"
    DefaultDepth    24
    Identifier    "Screen0"
    Device        "Card0"
    Monitor        "Monitor0"
    SubSection "Display"
        Depth    24
        Modes    "1920x1080" "1680x1050" "1600x1200" "1600x900" "1440x900" "1400x1050" "1280x1024" "1280x960" "1280x720" "1024x768" "800x600" "640x480"
    EndSubSection
EndSection

Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

Change AIX display resolution ?

Hello, Running X on AIX local display - want to change resolution. On Linux for example I used xrandr. ? thanks Vilius (1 Reply)
Discussion started by: vilius
1 Replies

2. Linux

How to change screen Resolution?

Dear all I install Cent OS 5.5 ( Linux OS), with bshell and also Windows OS on the my laptop (ASUA) maximum screen resolution in Windows OS is 1024*760 but in Cent OS 5.5 is 800 *600, I have a program that is necessary to install on Cent OS and I have problem with other Linux distributions... (2 Replies)
Discussion started by: mkhorami76
2 Replies

3. UNIX and Linux Applications

Exceptions while running application on headless linux

I want to install executable file(Demo.bin) on vMA4.0 virtual machine using ssh. Same can be installed on all other Linux/Unix box. but when I am trying to run it on vMA,I am getting the following error-- Could you please advise me how to approch this problem and how to resolve it? (4 Replies)
Discussion started by: smartgupta
4 Replies

4. Debian

Change resolution problem

Hi gurus I have notebook with connected external monitor. output of my xrandr looks like Screen 0: minimum 320 x 200, current 2960 x 1050, maximum 2960 x 1050 VGA connected 1680x1050+1280+0 (normal left inverted right x axis y axis) 478mm x 300mm 1680x1050 60.0*+ 1280x1024 ... (2 Replies)
Discussion started by: wakatana
2 Replies

5. UNIX for Dummies Questions & Answers

SuSE Linux 9.0 resolution change

Hello, We have a Suse Linux 9.0 box at work and I need to change the video resolution on it. We have command line interface only. Can someone please tell me how to go about doing so? Thanks, (0 Replies)
Discussion started by: mojoman
0 Replies

6. UNIX for Dummies Questions & Answers

Cannot change my display to high resolution

Hi all, i am one of the newbies with linux. i just install the Enterprise AS on my ibm z60t. I am trying to change the color setting to hight resolution, unfortunately, it does not work. it works only with the 256 color setting. It seems the widescreen or the vga card of my notebook does not... (3 Replies)
Discussion started by: sanlen
3 Replies

7. UNIX for Dummies Questions & Answers

How to change display resolution in UnixV4.0D

I would like to know how to change the display resolution in UnixV4.0D. Can anyone please help me. Regards, Avgust (1 Reply)
Discussion started by: avgust
1 Replies

8. Solaris

How to change CDE screen resolution?

I searched and found something about kdmconfig, but it's not installed. Isn't there an easy way to change the screen resolution in the CDE by right clicking or anything like that (like in Linux's KDE)? (1 Reply)
Discussion started by: lyonsd
1 Replies

9. Solaris

How to change display resolution

Hi, I would like to know how to change the display resolution in solaris on sparc. Can anyone please help me. Regards, Raja (3 Replies)
Discussion started by: RajaRC
3 Replies

10. UNIX Desktop Questions & Answers

change CRT resolution

Hello I want change my CRT resolution from 1152x900x** to 1280x1024x75 on a Solaris platform but I try "/usr/sbin/m64config" and "/usr/sbin/ffbconfig" command, the both commands failed :-( In the /dev/fbs/ directory there is juste one file : cgsix0 have you got a solution to my customer... (1 Reply)
Discussion started by: ggenevrier
1 Replies
Login or Register to Ask a Question