Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #177429 > unrolled thread

Set resolution options without xrandr

Back to article view | Back to linux.debian.user

Contents

  Set resolution options without xrandr Tony Baldwin <tonybaldwin@gmx.com> - 2017-02-05 04:00 +0100
    Re: Set resolution options without xrandr John Hasler <jhasler@newsguy.com> - 2017-02-05 05:30 +0100
      Re: Set resolution options without xrandr Ric Moore <wayward4now@gmail.com> - 2017-02-05 06:10 +0100
    Re: Set resolution options without xrandr Felix Miata <mrmazda@earthlink.net> - 2017-02-05 06:00 +0100
      Re: Set resolution options without xrandr Tony Baldwin <tonybaldwin@gmx.com> - 2017-02-05 15:20 +0100
        Magickally Resolved?: Set resolution options without xrandr Tony Baldwin <tonybaldwin@gmx.com> - 2017-02-05 16:00 +0100
          Re: Magickally Resolved?: Set resolution options without xrandr rhkramer@gmail.com - 2017-02-05 16:30 +0100
            Re: Magickally Resolved?: Set resolution options without xrandr Steven Mainor <steve@degga.net> - 2017-02-07 01:50 +0100
          Re: Magickally Resolved?: Set resolution options without xrandr Felix Miata <mrmazda@earthlink.net> - 2017-02-05 18:20 +0100

#177429 — Set resolution options without xrandr

In the past, of course I'd have dug up /etc/X11/xorg.conf with vi, and 
edited it, but there is no such file on this system (Jessie).
I've been trying to use xrandr, but I'm clearly missing something that 
the instructions I'm finding on superuser isn't giving me.
(http://superuser.com/questions/716795/how-to-adjust-the-screen-resolution-in-debian 
)

The worst thing is that it WAS on the proper resolution, then I had a 
PSU go south, so powered everything (including the monitor) down, while 
I went out to acquire a new PSU, and, upon rebooting after installing 
said new PSU, my screen res has gone from a beautiful 1680 x1050 to 
1280x768 of some such crap, and looks awful, in my opinion.
I didn't do anything to mess with it, so have no idea why it changed., 
and now the actual default for the monitor ( the 1680 x 1050 ) appears 
unavailable to xrandr

Thanks in Advance,
Tony


-- 
http://tonybaldwin.me
all tony, all the time

[toc] | [next] | [standalone]

#177430

Tony writes:
> In the past, of course I'd have dug up /etc/X11/xorg.conf with vi, and
> edited it, but there is no such file on this system (Jessie).

Create one.  
-- 
John Hasler 
jhasler@newsguy.com
Elmwood, WI USA

[toc] | [prev] | [next] | [standalone]

#177432

On 02/04/2017 11:28 PM, John Hasler wrote:
> Tony writes:
>> In the past, of course I'd have dug up /etc/X11/xorg.conf with vi, and
>> edited it, but there is no such file on this system (Jessie).
>
> Create one.

+
...and which video card do you have?? Ric


-- 
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

[toc] | [prev] | [next] | [standalone]

#177431

Tony Baldwin composed on 2017-02-04 21:55 (UTC-0500):

> In the past, of course I'd have dug up /etc/X11/xorg.conf with vi, and
> edited it, but there is no such file on this system (Jessie).

/etc/X11/xorg.conf became an optional file many releases ago. It usually can be 
created and used to override problems with automagic configuration like you 
appear to be having.

/etc/X11/xorg.conf.d/ can also be used for the same purposes. Anything in 
/etc/X11/xorg.conf.d/ that conflicts with anything in /etc/X11/xorg.conf will 
override to the extent of conflict.

> I've been trying to use xrandr, but I'm clearly missing something that
> the instructions I'm finding on superuser isn't giving me.
> (http://superuser.com/questions/716795/how-to-adjust-the-screen-resolution-in-debian
> )

That particular URI is trying to use a sledge hammer to drive a brad. Only 
rarely are CVT or GTF heroics necessary with modern versions of Xorg and its 
video drivers. I cannot recall ever in the past decade needing CVT or GTF to 
calculate and configure a modeline. Xorg knows how to and does do that 
automatically based on EDID, or if the display has defective EDID, any 
overriding HorizSync and VertRefresh specifications along with PreferredMode 
configured section Monitor in /etc/X11/xorg.conf* for Xorg to calculate them 
automatically.

> The worst thing is that it WAS on the proper resolution, then I had a
> PSU go south, so powered everything (including the monitor) down, while
> I went out to acquire a new PSU, and, upon rebooting after installing

It's entirely possible creating a mode with xrandr could override some sort of 
filesystem corruption that resulted from the powerdown. Have you tried forcing 
fsck on the / filesystem since the power failure was cured?

> said new PSU, my screen res has gone from a beautiful 1680 x1050 to
> 1280x768 of some such crap, and looks awful, in my opinion.
> I didn't do anything to mess with it, so have no idea why it changed.,
> and now the actual default for the monitor ( the 1680 x 1050 ) appears
> unavailable to xrandr

Something must have become corrupted to cause what is happening to you. Jessie 
should automatically use 1680x1050 on a display whose native resolution is 
1680x1050.

I currently have host big31 connected to a native 1680x1050 LCD booted to Jessie 
with no xrandr commands configured and no /etc/X11/xorg.conf* configured to 
affect display output, and its running TDE @1680x1050.

What follows are things you can try that should work, once you've examined 
/var/log/Xorg.0.log to determine:

	A-which driver is in use
	B-which video device is connected to your display

If you cannot determine these on your own by examining Xorg.0.log, post it to 
http://paste.debian.net/ so someone here can. Also post output from 'lspci -nnk 
| grep -A6 VGA', and/or 'inxi -c0 -v6 | head -n20'. Include output of 'cat 
/proc/cmdline' in your reply.

The video driver in use should not be FBDEV(0) or VESA(0). Neither support any 
widescreen modes. What you want to see are lots of lines containing intel(0), 
nouveau(0) or radeon(0), according to which gfxchip you have, or modeset(0) or 
modesetting(0) without regard to which gfxchip you have. Something you can try 
if your gfxchip is neither ancient nor newer than Jessie is forcing use of the 
modesetting driver by ensuring xserver-xorg-video-modesetting is installed, and 
purging the xserver-xorg-video-[ati,intel,nouveau] driver matching your gfxchip.

To configure your display manually:

1-create a script in /etc/X11/Xsession.d/ containing the xrandr command you wish 
applied when X starts. http://fm.no-ip.com/Share/setup contains a long list of 
xrandr commands that have worked for me with various hardware at various times; or

2-create /etc/X11/xorg.conf.
http://fm.no-ip.com/Share/Linux/xorg.conf-1680x1050x108-mini can be used as a 
starting skeleton. Comment or remove the DisplaySize line if you don't wish DPI 
forced to 108. If your gfxcard has multiple outputs, xorg.conf may require an 
uncommented line in the device section similar one of those contained in:
http://fm.no-ip.com/Share/Linux/50-device.conf , e.g.:
	Option	"monitor-VGA-0"	"DefaultMonitor"
You shouldn't need to specify the driver to use, but if 1680x1050 continues to 
fail to result you can try putting one in the device section, e.g.:
	'Driver "nouveau"'.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#177448

On 02/04/2017 11:59 PM, Felix Miata wrote:
> 'lspci -nnk | grep -A6 VGA', and/or 'inxi -c0 -v6 | head -n20

This just gave me errors, however,
lspci | grep -i VGA gave me:
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] BeaverCreek [Radeon HD 6530D]
Xorg log pasted to http://paste.debian.net/912902/


Thanks,
Tony

-- 
http://tonybaldwin.me
all tony, all the time

[toc] | [prev] | [next] | [standalone]

#177450 — Magickally Resolved?: Set resolution options without xrandr

Oddly, a reboot with no other action on my part... (Ok, I DID C-A-F5 to 
a tty and did Xorg -configure a couple of times, but each time produced 
errors nothing seemingly encouraging at all)
seems to have returned me to my original, beautiful 1680x1050 resolution.
TL;DR: A reboot fixed me...I almost feel I've been jettisoned into 
Windows-Land?!

Tony

On 02/05/2017 09:15 AM, Tony Baldwin wrote:
>
>
> On 02/04/2017 11:59 PM, Felix Miata wrote:
>> 'lspci -nnk | grep -A6 VGA', and/or 'inxi -c0 -v6 | head -n20
>
> This just gave me errors, however,
> lspci | grep -i VGA gave me:
> 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc.
> [AMD/ATI] BeaverCreek [Radeon HD 6530D]
> Xorg log pasted to http://paste.debian.net/912902/
>
>
> Thanks,
> Tony
>

-- 
http://tonybaldwin.me
all tony, all the time

[toc] | [prev] | [next] | [standalone]

#177452 — Re: Magickally Resolved?: Set resolution options without xrandr

On Sunday, February 05, 2017 09:55:14 AM Tony Baldwin wrote:
> TL;DR: A reboot fixed me...I almost feel I've been jettisoned into
> Windows-Land?!

Just for me, what was so long that you didn't read?

[toc] | [prev] | [next] | [standalone]

#177514 — Re: Magickally Resolved?: Set resolution options without xrandr

I think he just meant 'In case you didn't want to read my previous
paragraph, a reboot fixed it.'



On Sun, 2017-02-05 at 10:26 -0500, rhkramer@gmail.com wrote:
> On Sunday, February 05, 2017 09:55:14 AM Tony Baldwin wrote:
> > TL;DR: A reboot fixed me...I almost feel I've been jettisoned into
> > Windows-Land?!
> 
> Just for me, what was so long that you didn't read?
> 

[toc] | [prev] | [next] | [standalone]

#177460 — Re: Magickally Resolved?: Set resolution options without xrandr

Tony Baldwin composed on 2017-02-05 09:55 (UTC-0500):

> Oddly, a reboot with no other action on my part... (Ok, I DID C-A-F5 to
> a tty and did Xorg -configure a couple of times, but each time produced
> errors nothing seemingly encouraging at all)

Xorg -configure is obsolete. Nothing in the xorg.conf.new it produces is 
anything running Xorg normally won't do automatically, other than writing 
useless config info to the file xorg.conf.new.

> seems to have returned me to my original, beautiful 1680x1050 resolution.

Your log showed Xorg was using the VESA driver, which is incapable of using your 
Asus VW224's native 1680x1050 resolution. Obviously something happened to result 
in either the ati or the modesetting Xorg driver being used by your Radeon HD 
6530D instead of VESA.

> TL;DR: A reboot fixed me...I almost feel I've been jettisoned into
> Windows-Land?!

It can happen. Maybe some automatic dpkg reconfiguration process that never 
finished was triggered to be finished by a reboot.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web