LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page Adding a resolution when using xorg-vesa.conf
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-24-2020, 01:41 PM   #1
Twigster
Member
 
Registered: Oct 2019
Location: France
Distribution: Slackware64 14.2
Posts: 58

Rep: Reputation: Disabled
Adding a resolution when using xorg-vesa.conf

Hi,

because of reasons, I need to use the vesa driver.

So I copy the file /etc/X11/xorg.conf-vesa to /etc/X11/xorg.conf.d/myfile.conf and add my resolution to 24 and 32 bit depth modes

like so (dont mind the wrong tabs) :

Code:
Subsection "Display"
        Depth       24
        Modes  "1280x800 ""1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       32
        Modes "1280x800" "1024x768" "800x600" "640x480"
    EndSubsection
then I restart X (ctrl alt bcksp and i'm instantly back to the login screen, probably due to my runlevel), log in and in the display settings i only have 1024x768, 800x600 and 640x480.

here is a snippet of Xorg.0.log (no other EE tags):
Code:
[  1702.082] (II) VESA(0): Setting up VESA Mode 0x118 (1024x768)
[  1702.109] (==) VESA(0): Default visual is TrueColor
[  1702.109] (==) VESA(0): Backing store enabled
[  1702.109] (==) VESA(0): DPMS enabled
[  1702.109] (==) RandR enabled
[  1702.109] (II) AIGLX: Screen 0 is not DRI2 capable
[  1702.109] (EE) AIGLX: reverting to software rendering
[  1702.215] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[  1702.216] (II) AIGLX: Loaded and initialized swrast
Here is xrandr :

Code:
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 1024x768+0+0 0mm x 0mm
   1024x768      61.00* 
   800x600       73.00  
   640x480       86.00
and here is xdpyinfo :
Code:
xdpyinfo 
name of display:    :0.0
version number:    11.0
vendor string:    The X.Org Foundation
vendor release number:    11803000
X.Org version: 1.18.3
maximum request size:  16777212 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    7
supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 4, bits_per_pixel 8, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
    depth 15, bits_per_pixel 16, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
    depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  window 0x4800005, revert to Parent
number of extensions:    27
    BIG-REQUESTS
    Composite
    DAMAGE
    DOUBLE-BUFFER
    DPMS
    DRI2
    GLX
    Generic Event Extension
    MIT-SCREEN-SAVER
    MIT-SHM
    Present
    RANDR
    RECORD
    RENDER
    SGI-GLX
    SHAPE
    SYNC
    X-Resource
    XC-MISC
    XFIXES
    XFree86-DGA
    XFree86-VidModeExtension
    XINERAMA
    XInputExtension
    XKEYBOARD
    XTEST
    XVideo
default screen number:    0
number of screens:    1

screen #0:
  dimensions:    1024x768 pixels (302x191 millimeters)
  resolution:    86x102 dots per inch
  depths (7):    24, 1, 4, 8, 15, 16, 32
  root window id:    0x25d
  depth of root window:    24 planes
  number of colormaps:    minimum 1, maximum 1
  default colormap:    0x20
  default number of colormap cells:    256
  preallocated pixels:    black 0, white 16777215
  options:    backing-store WHEN MAPPED, save-unders NO
  largest cursor:    1024x768
  current input event mask:    0xfac03f
    KeyPressMask             KeyReleaseMask           ButtonPressMask          
    ButtonReleaseMask        EnterWindowMask          LeaveWindowMask          
    KeymapStateMask          ExposureMask             StructureNotifyMask      
    SubstructureNotifyMask   SubstructureRedirectMask FocusChangeMask          
    PropertyChangeMask       ColormapChangeMask       
  number of visuals:    240
  default visual id:  0x21
  visual:
    visual id:    0x21
    class:    TrueColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
Here is the full configuration file : https://pastebin.com/kFj0i2Ji

I would like some help on how to make the additional resolution work please
Last edited by Twigster; 04-28-2020 at 08:44 PM.
 
Old 04-24-2020, 02:16 PM   #2
IlyaK
Member
 
Registered: Jun 2017
Location: The Netherlands
Distribution: Debian
Posts: 118

Rep: Reputation: 72
Please provide full ``Xorg.0.log`` it could be that vesa reports some more info.

Also, try the following:
* Remove everything except "1280x800" from your modes section
* Comment out "sync" sections in "Monitor"
* Run your server
* Check ``Xorg.0.log`` again: it should have some clues about why "1280x800" can't be ussed
 
Old 04-24-2020, 08:48 PM   #3
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,784

Rep: Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434
I'd like to suggest researching and using as much specific monitor capability as you can muster as well as the quality/validity of it's EDID. I'm think this due to the lines you're getting

Code:
   
[1702.109] (II) AIGLX: Screen 0 is not DRI2 capable
[  1702.109] (EE) AIGLX: reverting to software rendering
that indicate Xorg may need more specific direction. That also indicates that while a good idea to eliminate any modelines you don't actually prefer, you really need to be booting to runlevel 3 if you're not already.
 
Old 04-24-2020, 09:44 PM   #4
Twigster
Member
 
Registered: Oct 2019
Location: France
Distribution: Slackware64 14.2
Posts: 58

Original Poster
Rep: Reputation: Disabled
edit mistake.
Last edited by Twigster; 04-24-2020 at 09:51 PM.
 
Old 04-24-2020, 09:51 PM   #5
Twigster
Member
 
Registered: Oct 2019
Location: France
Distribution: Slackware64 14.2
Posts: 58

Original Poster
Rep: Reputation: Disabled
@IlyaK :
the file has only one HorizSync line and one vertrefresh one in the Monitor section. Following Xorg.log is with the changes you requested :

https://pastebin.com/Grf76E36

it now says :
Code:
[ 30897.439] (II) VESA(0): Not using mode "1280x800" (no mode of this name)
I also attach the file in case I made a mistake :
https://pastebin.com/Jg8T8CL3

@enorbet : I use the runlevel 4. I tried init 3 > login as root > startx and i still only had 1024x768 listed in Settings > display of xfce. Therefore I do not see what it changes or how it is important.
 
Old 04-24-2020, 11:18 PM   #6
IlyaK
Member
 
Registered: Jun 2017
Location: The Netherlands
Distribution: Debian
Posts: 118

Rep: Reputation: 72
I am not Xorg expert. Experts are or here: https://lists.x.org/mailman/listinfo/xorg .You should ask them, they know better than me.
But here is what I see from your log:

Code:
[ 30897.412] (II) VESA(0): Printing DDC gathered Modelines:
[ 30897.412] (II) VESA(0): Modeline "1280x800"x0.0   71.11  1280 1328 1360 1440  800 803 809 823 -hsync -vsync (49.4 kHz eP)
[ 30897.412] (II) VESA(0): Modeline "1280x800"x0.0   59.26  1280 1328 1360 1440  800 803 809 823 -hsync -vsync (41.2 kHz e)
Xorg asked your Monitor about supported resolutions via DDC (a small bus that connects monitor and video card).
Monitor returned EDID: data structure with information about resolutions and refresh rates.
Monitor said that it likes "1280x800". So far, so good.

But then Xorg asked your videocard about supported resolutions:
Code:
[ 30897.412] (II) VESA(0): Searching for matching VESA mode(s):
[ 30897.412] Mode: 160 (0x0)
// 0x0 means "not supported"
[ 30897.413] Mode: 161 (0x0)
// Not supported again!
[ 30897.431] Mode: 105 (1024x768)
// The first supported resolution
So, Xorg (vesa driver actually) selected this one.

Your card doesn't have to support all resolutions in VESA mode:
https://en.wikipedia.org/wiki/VESA_B...efined_by_VESA
You see? Only resolutions up to 1024 are standard. All other are optional.

Your card may support them, but only with driver, not with generic VESA api.

Things to try: https://wiki.ubuntu.com/X/Config/Res...ed_video_cards
1. Add "VideoRam 10000", although "VESA VBE Total Mem: 7872 kB" (from your log) should be enough for 1200x800 ((1200*800*4)/1024 == 3750, which is less than 7872), so I do not believe it would help.

2. Use ``cvt`` to calculate modeline and add it explicitly via ``xrandr --newmode``:
https://wiki.ubuntu.com/X/Config/Res...ed_resolutions
But this must fix broken EDID, but your EDID contains information about 1200x800, so again: this one should not help (but still worth trying).
Effect should be similar to providing modelines (refresh rates and resolutions) in "Monitor" sections. Nobody does it today because Xog uses DDC/EDID to fetch this information from monitor.

3. I see that you are using framebuffer, so kernel configures video mode for console:
Code:
[ 30897.372] (**) |   |-->Device "VESA Framebuffer"
.
Please, boot into console (runlevel 3) and provide output of "fbset" to see which mode are you using in console.
If mode is correct, you can try to use framebuffer X driver:
https://www.x.org/releases/current/d.../fbdev.4.xhtml
But it seems that vesafb (kernel driver) doesn't support resolutions more than 1024:
http://lxr.linux.no/linux+v3.4.4/Doc.../fb/vesafb.txt
So, it probably would not help(

4. You can try to disable framebuffer in your kernel by passing following params to the kernel (via lilo.conf)

Code:
vga=normal
nofb
nomodeset
video=vesafb:off
In this case, Xorg/vesa will control your videocard (kernel would not even touch it). It may help, but I am not sure.
---
It could be that you video card can't support other resolutions using vesa driver. In this case you only have to use native driver.
Last edited by IlyaK; 04-24-2020 at 11:24 PM.
 
Old 04-25-2020, 07:25 PM   #7
Twigster
Member
 
Registered: Oct 2019
Location: France
Distribution: Slackware64 14.2
Posts: 58

Original Poster
Rep: Reputation: Disabled
Hi,

When the log says "searching for matching VESA mode", where can I see all the modes it goes through?


1 - I tried adding VideoRam 1000 to the Device section (the line was there and commented in slackware supplied file). It Didn't change anything. Besides the resulting Xorg.log still said VESA VBE Total Mem: 7872. I wonder if I edited the file correctly.

2 - I followed the steps you provided to add a new mode. Upon using the --mode option, xrandr says "configure crtc 0 failed". I checked the field CRTC using xrandr --verbose, and the field is indeed at 0.

3 - I do not know how to use 'fbset'. From my X session I did init 3 > fbset and it said /dev/fb0 does not exist. I do not have anything named "fb*" in /dev either. Can you help me there?

4 - I tried your options on my append line. Not sure of what should be different.

PS : All my xrandr commands always say : "fauled to get size of gamma for output default". Maybe it's important, I dont know.

Thanks for your help so far
 
Old 04-25-2020, 09:54 PM   #8
IlyaK
Member
 
Registered: Jun 2017
Location: The Netherlands
Distribution: Debian
Posts: 118

Rep: Reputation: 72
> /dev/fb0 does not exist.
oops, that means framebuffer is not used by kernel, so step "4" was useless anyway..

Have you tried https://lists.x.org/mailman/listinfo/xorg ?
 
Old 04-26-2020, 07:02 AM   #9
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,784

Rep: Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434
Quote:
Originally Posted by Twigster View Post
@enorbet : I use the runlevel 4. I tried init 3 > login as root > startx and i still only had 1024x768 listed in Settings > display of xfce. Therefore I do not see what it changes or how it is important.
Hi Twigster. The point of runlevel 3 is simply a "base of operations", a place from where you can try adjustments without black-screening and having to reboot. I sincerely hoipe all your efforts reward you with ultimate success.
 
Old 04-26-2020, 12:43 PM   #10
Twigster
Member
 
Registered: Oct 2019
Location: France
Distribution: Slackware64 14.2
Posts: 58

Original Poster
Rep: Reputation: Disabled
@IlyaK I haven't tried yet, will do now.

Hi enorbet, thanks for the wish, I remember you from the first thread I posted here, you were very helpful
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
xorg.conf-fbdev or xorg.conf-vesa? stf92 Slackware 1 05-14-2014 02:08 AM
CRT VGA monitor only works with Vesa. Need xorg.conf to work with GPU. Aquitain3 Linux - Newbie 3 03-19-2009 08:38 AM
Slackware 12.0 default vesa xorg.conf - blank screen send Slackware 30 10-28-2007 06:23 PM
xorg.conf and VESA modes Dark_Helmet Linux - General 2 12-28-2004 10:16 PM
In Disk on Chip VESA support Kernel - VESA frambuffer Device is not Created - jebaanandhan LinuxQuestions.org Member Success Stories 0 05-23-2004 08:31 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:25 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration