Re: Virtual machine affects client screen resolution

[Roy J. Tellason, Sr.]

On Friday 24 February 2023 10:03:31 pm Max Nikulin wrote:
> On 25/02/2023 00:55, Roy J. Tellason, Sr. wrote:
> > On Wednesday 22 February 2023 09:24:17 pm Max Nikulin wrote:
> >> On 19/02/2023 01:01, Roy J. Tellason, Sr. wrote:
> >>> So this got me curious,  and I tried it out.  In the terminal that's
> >>> running inside of the virtualbox instance where I'm doing emails,  it
> >>> comes back with:
> >>>
> >>> :0
> >>
> >> Have you tried to emulate multiple monitors in virtualbox?
> > 
> > I'm not sure what I need to do with the computer to make this happen.
> 
> VirtualBox can emulate multiple monitors, they may be represented as 
> several windows on the same physical device. It is convenient to test 
> behavior of applications in the configuration with multiple monitors. 
> There is an option in VM configuration UI.

I don't recall seeing that,  I'll have another look...
 
> >>> But in a terminal which is running on the host Debian system,  it comes 
> >>> back with:
> >>>
> >>> :0.0
> >>>
> >>> I wonder why the difference?
> >>
> >> My guess is that it may depend on graphics adapter and its driver.
> > 
> > It's an older machine with a VGA output being used.  I assume that I'll
> > need to get some kind of a card with an HDMI output and a cable to make
> > that happen.  No idea what the driver is,  probably nothing special.
> 
> It does not matter if it is special or not. My guess (that may be wrong) 
> that even noveau vs. nvidia may behave differently. I have never gone 
> deeper, since I do not remember any problem with setting DISPLAY=:0 when 
> it was necessary. Driver in use should appear in Xorg.0.log, e.g.
> 
> (II) modeset(0): [DRI2]   DRI driver: i965

Only thing I'm finding that resembles that is these lines:

[ 13041.620] (II) modeset(0): [DRI2]   DRI driver: i965
[ 13041.620] (II) modeset(0): [DRI2]   VDPAU driver: i965
 
> >> I have heard that a display may have several screens (it is not the same 
> >> as multiple monitors that show
> >> different regions of the same display and screen). I have never tried such 
> >> configuration.
> > 
> > Are you referring to multiple desktops?  I have that going,  for sure.
> 
> My impression is that multiple screens of a display is not the same as 
> virtual desktops (and not the same as multiple monitors). I am not 
> familiar with X11 protocol so closely. Frankly speaking, I has a hope 
> that somebody will post a proper link. My curiosity is not strong enough 
> yet to filter search engine results myself.


-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

Re: Virtual machine affects client screen resolution

[Max Nikulin]

On 25/02/2023 00:55, Roy J. Tellason, Sr. wrote:

On Wednesday 22 February 2023 09:24:17 pm Max Nikulin wrote:

On 19/02/2023 01:01, Roy J. Tellason, Sr. wrote:

So this got me curious,  and I tried it out.  In the terminal that's
running inside of the virtualbox instance where I'm doing emails,  it
comes back with:

:0


Have you tried to emulate multiple monitors in virtualbox?


I'm not sure what I need to do with the computer to make this happen.


VirtualBox can emulate multiple monitors, they may be represented as 
several windows on the same physical device. It is convenient to test 
behavior of applications in the configuration with multiple monitors. 
There is an option in VM configuration UI.



But in a terminal which is running on the host Debian system,  it comes back 
with:

:0.0

I wonder why the difference?


My guess is that it may depend on graphics adapter and its driver.


It's an older machine with a VGA output being used.  I assume that I'll
need to get some kind of a card with an HDMI output and a cable to make
that happen.  No idea what the driver is,  probably nothing special.


It does not matter if it is special or not. My guess (that may be wrong) 
that even noveau vs. nvidia may behave differently. I have never gone 
deeper, since I do not remember any problem with setting DISPLAY=:0 when 
it was necessary. Driver in use should appear in Xorg.0.log, e.g.


(II) modeset(0): [DRI2]   DRI driver: i965


I have heard that a display may have several screens (it is not the same as 
multiple monitors that show
different regions of the same display and screen). I have never tried such 
configuration.


Are you referring to multiple desktops?  I have that going,  for sure.


My impression is that multiple screens of a display is not the same as 
virtual desktops (and not the same as multiple monitors). I am not 
familiar with X11 protocol so closely. Frankly speaking, I has a hope 
that somebody will post a proper link. My curiosity is not strong enough 
yet to filter search engine results myself.

Re: Virtual machine affects client screen resolution

[Roy J. Tellason, Sr.]

On Wednesday 22 February 2023 09:24:17 pm Max Nikulin wrote:
> 
> On 19/02/2023 01:01, Roy J. Tellason, Sr. wrote:
> > On Saturday 18 February 2023 12:17:20 am Max Nikulin wrote:
> >> echo "$DISPLAY"
> > 
> > So this got me curious,  and I tried it out.  In the terminal that's
> > running inside of the virtualbox instance where I'm doing emails,  it
> > comes back with:
> > 
> > :0
> 
> Have you tried to emulate multiple monitors in virtualbox?

Not yet.  I would like to go to multiple monitors at some point,  particularly 
once I get going with some of the CAD stuff I have installed that I really 
haven't done anything much with yet.  I'm not sure what I need to do with the 
computer to make this happen.
 
> > But in a terminal which is running on the host Debian system,  it comes 
> > back with:
> > 
> > :0.0
> > 
> > I wonder why the difference?
> 
> My guess is that it may depend on graphics adapter and its driver. 

It's an older machine with a VGA output being used.  I assume that I'll need to 
get some kind of a card with an HDMI output and a cable to make that happen.  
No idea what the driver is,  probably nothing special.

> I have heard that a display may have several screens (it is not the same as 
> multiple monitors that show
> different regions of the same display and screen). I have never tried such 
> configuration.

Are you referring to multiple desktops?  I have that going,  for sure.


-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

Re: Virtual machine affects client screen resolution

[Max Nikulin]

On 19/02/2023 01:01, Roy J. Tellason, Sr. wrote:

On Saturday 18 February 2023 12:17:20 am Max Nikulin wrote:

echo "$DISPLAY"


So this got me curious,  and I tried it out.  In the terminal that's
running inside of the virtualbox instance where I'm doing emails,  it
comes back with:

:0


Have you tried to emulate multiple monitors in virtualbox?


But in a terminal which is running on the host Debian system,  it comes back 
with:

:0.0

I wonder why the difference?


My guess is that it may depend on graphics adapter and its driver. I 
have heard that a display may have several screens (it is not the same 
as multiple monitors that show different regions of the same display and 
screen). I have never tried such configuration. I am unsure which 
approach is used in nvidia's xinerama.

Re: Virtual machine affects client screen resolution

[Albert S.]

My thanks to David Wright and Max Nikulin.

That was a good wake-up call. Most of my VMs are safe, but it was 
interesting to learn what was really going on.


ForwardX11 was enabled for the ssh session. Initially I imagined 
vncviewer (to the KVM host though ssh) was the one causing the problem, 
but now it is clear that the ssh session to the VM was responsible for it.


This was the result of checking open tcp ports on the VM:
$ netstat -nlt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address State
...
tcp0  0 127.0.0.53:53   0.0.0.0:*   LISTEN
tcp0  0 127.0.0.1:6010  0.0.0.0:*   LISTEN

$ echo $DISPLAY
localhost:10.0

It was also a good opportunity to learn about XPRA and test it.

Albert


On 2/17/23 22:15, David Wright wrote:

On Fri 17 Feb 2023 at 20:57:38 (-0500), Albert S. wrote:

Running “xrandr --size 800x600” on a virtual machine affected both
monitors on my workstation. That was completely unexpected and I am
wondering how to explain that.

Below you will find the detailed description.


[ … ]


But my real concern is how a xrandr command issued on a VM which is
running on another machine could affect the video of the client
machine used to access that VM.

I would appreciate an explanation for that.


The clue is in your use of the word "client". In fact, the "video of
the machine used to access that VM" is the X /server/. The
applications that you control on this machine, and others that you
connect to, which you thought were servers, are in fact the clients.

So, for example, I'm sitting at my All-in-One, running an X server as
usual. In a room down the hall, I have a laptop that's booted up, but
hasn't been used yet. It's sitting at a VC prompt waiting for someone
to log in. There's no X server running on it.

I've connected to the laptop with ssh from an xterm here on my A-i-O,
and typed into the /laptop/:

$ xrandr --output eDP --rotate right

and immediately, my screen blanks, comes back a second later, and
everything is sideways. When I type:

$ xrandr --output eDP --rotate normal

then normality is restored.

So I ran xrandr on the laptop, but xrandr is not concerned with that
machine, but only with the X /server/, running on my A-i-O.

https://en.wikipedia.org/wiki/X_Window_System

Cheers,
David.

Re: Virtual machine affects client screen resolution

[Roy J. Tellason, Sr.]

On Saturday 18 February 2023 12:17:20 am Max Nikulin wrote:
> echo "$DISPLAY"

So this got me curious,  and I tried it out.  In the terminal that's running 
inside of the virtualbox instance where I'm doing emails,  it comes back with:

:0

But in a terminal which is running on the host Debian system,  it comes back 
with:

:0.0

I wonder why the difference?

-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

Re: Virtual machine affects client screen resolution

[Max Nikulin]

On 18/02/2023 08:57, Albert S. wrote:


If you think I issued the xrandr command on the wrong machine, that was 
not the case: history makes it clear.


Behavior depends on the DISPLAY environment value at the moment when 
xrandr was executed. Likely it was pointed not to vnc Xserver, but to 
the socket forwarded to your workstation by ssh. Try


echo "$DISPLAY"

In a local shell, in a ssh session, and from vncviewer.

Re: Virtual machine affects client screen resolution

[David Wright]

On Fri 17 Feb 2023 at 20:57:38 (-0500), Albert S. wrote:
> Running “xrandr --size 800x600” on a virtual machine affected both
> monitors on my workstation. That was completely unexpected and I am
> wondering how to explain that.
> 
> Below you will find the detailed description.

[ … ]

> But my real concern is how a xrandr command issued on a VM which is
> running on another machine could affect the video of the client
> machine used to access that VM.
> 
> I would appreciate an explanation for that.

The clue is in your use of the word "client". In fact, the "video of
the machine used to access that VM" is the X /server/. The
applications that you control on this machine, and others that you
connect to, which you thought were servers, are in fact the clients.

So, for example, I'm sitting at my All-in-One, running an X server as
usual. In a room down the hall, I have a laptop that's booted up, but
hasn't been used yet. It's sitting at a VC prompt waiting for someone
to log in. There's no X server running on it.

I've connected to the laptop with ssh from an xterm here on my A-i-O,
and typed into the /laptop/:

$ xrandr --output eDP --rotate right

and immediately, my screen blanks, comes back a second later, and
everything is sideways. When I type:

$ xrandr --output eDP --rotate normal

then normality is restored.

So I ran xrandr on the laptop, but xrandr is not concerned with that
machine, but only with the X /server/, running on my A-i-O.

https://en.wikipedia.org/wiki/X_Window_System

Cheers,
David.

Virtual machine affects client screen resolution

[Albert S.]

Running “xrandr --size 800x600” on a virtual machine affected both 
monitors on my workstation. That was completely unexpected and I am 
wondering how to explain that.


Below you will find the detailed description.

I run KVM on a Debian 11 server, which has no monitor or keyboard 
attached to it. One of the VMs running on that server is a Ubuntu 
desktop 22.04 LTS (I needed the desktop version due to the application I 
was running there). From another machine (a workstation running Debian 
11, xfce) with two monitors I access the Ubuntu VM when I need to. I use 
ssh to the server to establish a ssh tunnel, and then access the Ubuntu 
machine with the command “/usr/lib/ssvnc/vncviewer localhost:5906 &”.


A couple of weeks ago I decided to increase the Ubuntu VM resolution to 
1600x1200 to make my work easier, and that initially worked. However, 
today, after a reboot of the Debian server and all VMs, I noticed that 
the Ubuntu screen (through VNC) would still have the resolution of 
1600x1200 when displayed on my workstation, but it would display as 
black on the top and gray on the bottom, without any image. The VM 
console was dead. However, I could still access the VM through ssh. So, 
I started trying different commands to fix the problem. One of the 
commands I issued on the VM (through ssh) was “xrandr –size 800x600”.


When I issued the xrandr command, one display on my workstation turned 
off, and the other one went to 800x600 resolution. That was completely 
unexpected. I am asking myself how can a command issued on a VM which is 
running on a different machine affect the screen resolution of the 
workstation used to access that VM. Just to be clear, I was accessing 
that VM both through ssh and through vncviewer (still back and gray 
screen image) when that happened.


If you think I issued the xrandr command on the wrong machine, that was 
not the case: history makes it clear.


Just to be complete, the solution to the video problem was to make a 
change on the KVM xml file, from video type=vga to type=virtio.


But my real concern is how a xrandr command issued on a VM which is 
running on another machine could affect the video of the client machine 
used to access that VM.


I would appreciate an explanation for that.

Thanks,

Albert

Re: loss of screen resolution, part 2

[gene heskett]

On 12/21/22 03:37, to...@tuxteam.de wrote:

On Tue, Dec 20, 2022 at 05:26:06PM +, Kleene, Steven (kleenesj) wrote:

[...]


On Tuesday, December 20, 2022 10:36 AM, Max Nikulin wrote:

get-edid | parse-edid
edid-decode /sys/class/drm/card0-HDMI-A-1/edid

Thanks.  get-edid doesn't find any EDIDs, and there are no edid files under
/sys/devices.


Could it just be that the microcontroller (in the display)
responsible for providing the EDID is dead?

Cheers


That, Tomas,  depending on how old the purchase receipt is, should be 
grounds for returning it for credit against one that works.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: loss of screen resolution, part 2

[gene heskett]

On 12/20/22 12:27, Kleene, Steven (kleenesj) wrote:

On Monday, December 19, 2022 9:12 PM, I wrote:

Today I have my new desktop and did a clean install of Bullseye.  I call fvwm
with startx, and once again my screen is 1024x768.


On Monday, December 19, 2022 9:49 PM, Timothy M Butterworth wrote:

Newer Intel graphics require closed source binary blobs. Try installing
firmware-linux-nonfree.


I did that and am still stuck.  Thanks for the suggestion.

On Monday, December 19, 2022 10:29 PM, Felix Miata  
replied:

Cardinal rule of PC shopping for use with Linux, unless you are a Linux
developer:
   Make sure the major PC components are several months or more older than
   your selected distro's original release date.


I've heard that rule often but trusted a local friend who's built many Linux
machines to build mine.  I've used *ix for 40 years but never assembled the
hardware.  And here I am.


To use Bullseye, at the least you need either a backport kernel containing
Alder Lake support, or Bookworm (Testing) or Sid (Unstable).


I'll try Testing and, if that fails, maybe an add-on graphics card.  Thanks.

On Tuesday, December 20, 2022 2:47 AM, Bret Busby  wrote:

Perhaps, it would be worthwhile, to download and try a Linux Mint live iso,


Thank you.  I hope to stick with Debian but will keep this in mind.



Another possibility comes to mind because there are cheap one way cables 
out there, just waiting to snag some shekels from the relatively new 
bee.  So you might be able to get the get-edid to work with a different 
cable that is all there for 2 way traffic. There is also the possibility 
the monitor is too old to have an edid response but that is only a 
suspect if it is over a decade old.


On Tuesday, December 20, 2022 10:36 AM, Max Nikulin wrote:Or 

get-edid | parse-edid
edid-decode /sys/class/drm/card0-HDMI-A-1/edid

Thanks.  get-edid doesn't find any EDIDs, and there are no edid files under
/sys/devices.


From: Max Nikulin 
Sent: Tuesday, December 20, 2022 10:36 AM
To: debian-user@lists.debian.org
Subject: Re: loss of screen resolution, part 2

External Email: Use Caution


On 20/12/2022 09:49, Timothy M Butterworth wrote:

Newer Intel graphics require closed source binary blobs. Try installing
firmware-linux-nonfree.


In the previous thread somebody spotted an issue with fetching modes
supported by the monitor. Examples of commands to debug such problem:

get-edid | parse-edid
edid-decode /sys/class/drm/card0-HDMI-A-1/edid


.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

Re: loss of screen resolution, part 2

[Max Nikulin]

On 21/12/2022 00:26, Kleene, Steven (kleenesj) wrote:

On Tuesday, December 20, 2022 10:36 AM, Max Nikulin wrote:

get-edid | parse-edid
edid-decode /sys/class/drm/card0-HDMI-A-1/edid

Thanks.  get-edid doesn't find any EDIDs, and there are no edid files under
/sys/devices.


Have you checked "journalctl -b" (current boot only) output for messages 
related to missing firmware? It may be noticeable in "apt upgrade" 
messages when initramfs is created during installing of new kernel.


As an experiment (it is better to remove new file or restore old 
version) latest firmware files may be taken from

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree
Such changes usually requires "update-initramfs -u" (normally performed 
by scripts insides firmware .deb packages).

Re: loss of screen resolution, part 2

[Kleene, Steven (kleenesj)]

On Wednesday, December 21, 2022 3:37 AM, to...@tuxteam.de  
wrote:
> Could it just be that the microcontroller (in the display) responsible for
> providing the EDID is dead?

That might have seemed like a good explanation when I saw it with the older
desktop, but now it seems unlikely.  With the new desktop running Testing,
the monitor works and there is an edid file under /sys/devices.  Thanks.

I forgot to mention last time how impressed and grateful I am that the
developers got support for this new motherboard implemented as fast as they
did.


From: to...@tuxteam.de 
Sent: Wednesday, December 21, 2022 3:37 AM
To: debian-user@lists.debian.org
Subject: Re: loss of screen resolution, part 2

External Email: Use Caution

Re: loss of screen resolution, part 2

[tomas]

On Tue, Dec 20, 2022 at 05:26:06PM +, Kleene, Steven (kleenesj) wrote:

[...]

> On Tuesday, December 20, 2022 10:36 AM, Max Nikulin wrote:
> > get-edid | parse-edid
> > edid-decode /sys/class/drm/card0-HDMI-A-1/edid
> Thanks.  get-edid doesn't find any EDIDs, and there are no edid files under
> /sys/devices.

Could it just be that the microcontroller (in the display)
responsible for providing the EDID is dead? 

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: loss of screen resolution, part 2

[Kleene, Steven (kleenesj)]

On Monday, December 19, 2022 9:12 PM, I wrote:
>> Today I have my new desktop and did a clean install of Bullseye.  I call fvwm
>> with startx, and once again my screen is 1024x768.

On Monday, December 19, 2022 10:29 PM, Felix Miata  
replied:
> To use Bullseye, at the least you need either a backport kernel containing
> Alder Lake support, or Bookworm (Testing) or Sid (Unstable).

I did a clean install of Bookworm and am happy to report that solved the
problem.  Thank you.


From: Kleene, Steven (kleenesj) 
Sent: Tuesday, December 20, 2022 12:26 PM
To: debian-user@lists.debian.org
Subject: Re: loss of screen resolution, part 2

On Monday, December 19, 2022 9:12 PM, I wrote:
>> Today I have my new desktop and did a clean install of Bullseye.  I call fvwm
>> with startx, and once again my screen is 1024x768.

On Monday, December 19, 2022 9:49 PM, Timothy M Butterworth wrote:
> Newer Intel graphics require closed source binary blobs. Try installing
> firmware-linux-nonfree.

I did that and am still stuck.  Thanks for the suggestion.

On Monday, December 19, 2022 10:29 PM, Felix Miata  
replied:
> Cardinal rule of PC shopping for use with Linux, unless you are a Linux
> developer:
>   Make sure the major PC components are several months or more older than
>   your selected distro's original release date.

I've heard that rule often but trusted a local friend who's built many Linux
machines to build mine.  I've used *ix for 40 years but never assembled the
hardware.  And here I am.

> To use Bullseye, at the least you need either a backport kernel containing
> Alder Lake support, or Bookworm (Testing) or Sid (Unstable).

I'll try Testing and, if that fails, maybe an add-on graphics card.  Thanks.

On Tuesday, December 20, 2022 2:47 AM, Bret Busby  wrote:
> Perhaps, it would be worthwhile, to download and try a Linux Mint live iso,

Thank you.  I hope to stick with Debian but will keep this in mind.

On Tuesday, December 20, 2022 10:36 AM, Max Nikulin wrote:
> get-edid | parse-edid
> edid-decode /sys/class/drm/card0-HDMI-A-1/edid
Thanks.  get-edid doesn't find any EDIDs, and there are no edid files under
/sys/devices.


From: Max Nikulin 
Sent: Tuesday, December 20, 2022 10:36 AM
To: debian-user@lists.debian.org
Subject: Re: loss of screen resolution, part 2

External Email: Use Caution


On 20/12/2022 09:49, Timothy M Butterworth wrote:
> Newer Intel graphics require closed source binary blobs. Try installing
> firmware-linux-nonfree.

In the previous thread somebody spotted an issue with fetching modes
supported by the monitor. Examples of commands to debug such problem:

get-edid | parse-edid
edid-decode /sys/class/drm/card0-HDMI-A-1/edid

Re: loss of screen resolution, part 2

[Kleene, Steven (kleenesj)]

On Monday, December 19, 2022 9:12 PM, I wrote:
>> Today I have my new desktop and did a clean install of Bullseye.  I call fvwm
>> with startx, and once again my screen is 1024x768.

On Monday, December 19, 2022 9:49 PM, Timothy M Butterworth wrote:
> Newer Intel graphics require closed source binary blobs. Try installing
> firmware-linux-nonfree.

I did that and am still stuck.  Thanks for the suggestion.

On Monday, December 19, 2022 10:29 PM, Felix Miata  
replied:
> Cardinal rule of PC shopping for use with Linux, unless you are a Linux
> developer:
>   Make sure the major PC components are several months or more older than
>   your selected distro's original release date.

I've heard that rule often but trusted a local friend who's built many Linux
machines to build mine.  I've used *ix for 40 years but never assembled the
hardware.  And here I am.

> To use Bullseye, at the least you need either a backport kernel containing
> Alder Lake support, or Bookworm (Testing) or Sid (Unstable).

I'll try Testing and, if that fails, maybe an add-on graphics card.  Thanks.

On Tuesday, December 20, 2022 2:47 AM, Bret Busby  wrote:
> Perhaps, it would be worthwhile, to download and try a Linux Mint live iso,

Thank you.  I hope to stick with Debian but will keep this in mind.

On Tuesday, December 20, 2022 10:36 AM, Max Nikulin wrote:
> get-edid | parse-edid
> edid-decode /sys/class/drm/card0-HDMI-A-1/edid
Thanks.  get-edid doesn't find any EDIDs, and there are no edid files under
/sys/devices.


From: Max Nikulin 
Sent: Tuesday, December 20, 2022 10:36 AM
To: debian-user@lists.debian.org
Subject: Re: loss of screen resolution, part 2

External Email: Use Caution


On 20/12/2022 09:49, Timothy M Butterworth wrote:
> Newer Intel graphics require closed source binary blobs. Try installing
> firmware-linux-nonfree.

In the previous thread somebody spotted an issue with fetching modes
supported by the monitor. Examples of commands to debug such problem:

get-edid | parse-edid
edid-decode /sys/class/drm/card0-HDMI-A-1/edid

Re: loss of screen resolution, part 2

[Max Nikulin]

On 20/12/2022 09:49, Timothy M Butterworth wrote:
Newer Intel graphics require closed source binary blobs. Try installing 
firmware-linux-nonfree.


In the previous thread somebody spotted an issue with fetching modes 
supported by the monitor. Examples of commands to debug such problem:


get-edid | parse-edid
edid-decode /sys/class/drm/card0-HDMI-A-1/edid

Re: loss of screen resolution, part 2

[Felix Miata]

Kleene, Steven (kleenesj) composed on 2022-12-20 02:12 (UTC):

> Today I have my new desktop and did a clean install of Bullseye.

Cardinal rule of PC shopping for use with Linux, unless you are a Linux 
developer:

Make sure the major PC components are several months or more older than
your selected distro's original release date.

> lspci | grep VGA
> 00:02.0 VGA compatible controller: Intel Corporation Device 4692 (rev 0c)

https://pci-ids.ucw.cz/read/PC/8086/4692
https://en.wikipedia.org/wiki/Alder_Lake
"Intel officially announced 12th Gen Intel Core CPUs on October 27, 2021. Intel
officially announced 12th Gen Intel Core mobile CPUs and non-K series desktop 
CPUs
on January 4, 2022. ... Alder Lake."

>   Desktop: FVWM v: 2.6.8 vt: 1 dm: startx Distro: Debian GNU/Linux 11
> (bullseye)
> Graphics:
>   Device-1: Intel vendor: ASUSTeK driver: N/A arch: Gen-12.2
> process: Intel 10nm built: 2021-22+ bus-ID: 00:02.0 chip-ID: 8086:4692

https://en.wikipedia.org/wiki/Debian_version_history#Debian_11_(Bullseye)
"Debian 11 (Bullseye) was released on 14 August 2021.[1] It is based on the 
Linux
5.10 LTS kernel and will be supported for five years.[187]"

Your situation is backwards, distro released (2021) long before the hardware
(2022). Thus, out-of-the-box Bullseye can't be expected to support your GPU. To
use Bullseye, at the least you need either a backport kernel containing Alder 
Lake
support, or Bookworm (Testing) or Sid (Unstable).
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: loss of screen resolution, part 2

[Timothy M Butterworth]

On Mon, Dec 19, 2022 at 9:28 PM Kleene, Steven (kleenesj) <
kleen...@ucmail.uc.edu> wrote:

> On Thursday, December 1, 2022 9:41 PM, I started a thread (same title as
> this
> minus "part 2"), with:
> > Out of the blue today, my usual screen resolution (1920x1200) became
> > unavailable.
>
> Despite many helpful suggestions, the problem wasn't resolved.  Since I
> was about to get a new desktop, I figured I could give up.  This history
> may
> all be irrelevant.
>
> Today I have my new desktop and did a clean install of Bullseye.  I call
> fvwm
> with startx, and once again my screen is 1024x768.  New desktop, new cable,
> same monitor (Dell U2412Mb), now connected DVI to Display Port.  I tested
> another Dell monitor connected HDMI to HDMI and had the same problem, so I
> don't guess the problem is in the monitor.
>
> The system sees the monitor as "default" rather than VGA, DP, DVI, or HDMI.
> I was able to define a new mode 1920x1200 with xrandr, but xrandr --addmode
> fails because I can't find an "output name" that works.  At the bottom are
> some of the outputs that were requested in the previous thread.
>
> On the motherboard (ASUS - Z790M-PLUS Prime D4 Intel LGA 1700 microATX),
> the
> NIC is apparently not supported yet by Debian, and I had to put in a second
> NIC.  Do I have to add a graphics card too now to get 1920x1200?
>
> Thanks.
>
> cat /etc/debian_version
> 11.6
>
> lspci | grep VGA
> 00:02.0 VGA compatible controller: Intel Corporation Device 4692 (rev 0c)
>
> dpkg --get-selections | grep firmware
> firmware-linux-free install
>
> dpkg --get-selections | grep xserver-xorg-video-*
> xserver-xorg-video-all  install
> xserver-xorg-video-amdgpu   install
> xserver-xorg-video-ati  install
> xserver-xorg-video-fbdevinstall
> xserver-xorg-video-intelinstall
> xserver-xorg-video-nouveau  install
> xserver-xorg-video-qxl  install
> xserver-xorg-video-radeon   install
> xserver-xorg-video-vesa install
> xserver-xorg-video-vmware   install
>

Newer Intel graphics require closed source binary blobs. Try installing
firmware-linux-nonfree.


> grep Driver  /var/log/Xorg.0.log | grep II
> [52.843] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
>
> inxi -GSaz
> System:
>   Kernel: 5.10.0-20-amd64 arch: x86_64 bits: 64 compiler: gcc v: 10.2.1
> parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-20-amd64
> root=UUID=82fc750d-98f2-4096-9d84-17a2690d1dcf ro quiet
>   Desktop: FVWM v: 2.6.8 vt: 1 dm: startx Distro: Debian GNU/Linux 11
> (bullseye)
> Graphics:
>   Device-1: Intel vendor: ASUSTeK driver: N/A arch: Gen-12.2
> process: Intel 10nm built: 2021-22+ bus-ID: 00:02.0 chip-ID: 8086:4692
> class-ID: 0300
>   Display: server: X.Org v: 1.20.11 driver: X: loaded: vesa
> unloaded: fbdev,modesetting dri: swrast gpu: N/A display-ID: :0
> screens: 1
>   Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm (10.67x7.99")
> s-diag: 339mm (13.33")
>   Monitor-1: default res: 1024x768 hz: 76 size: N/A modes: N/A
>   API: OpenGL v: 4.5 Mesa 20.3.5 renderer: llvmpipe (LLVM 11.0.1 256 bits)
> compat-v: 3.1 direct render: Yes
>
> cat ~/.local/share/xorg/Xorg.0.log | pastebinit
> https://paste.debian.net/1264692/
>


-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

loss of screen resolution, part 2

[Kleene, Steven (kleenesj)]

On Thursday, December 1, 2022 9:41 PM, I started a thread (same title as this
minus "part 2"), with:
> Out of the blue today, my usual screen resolution (1920x1200) became
> unavailable.

Despite many helpful suggestions, the problem wasn't resolved.  Since I
was about to get a new desktop, I figured I could give up.  This history may
all be irrelevant.

Today I have my new desktop and did a clean install of Bullseye.  I call fvwm
with startx, and once again my screen is 1024x768.  New desktop, new cable,
same monitor (Dell U2412Mb), now connected DVI to Display Port.  I tested
another Dell monitor connected HDMI to HDMI and had the same problem, so I
don't guess the problem is in the monitor.

The system sees the monitor as "default" rather than VGA, DP, DVI, or HDMI.
I was able to define a new mode 1920x1200 with xrandr, but xrandr --addmode
fails because I can't find an "output name" that works.  At the bottom are
some of the outputs that were requested in the previous thread.

On the motherboard (ASUS - Z790M-PLUS Prime D4 Intel LGA 1700 microATX), the
NIC is apparently not supported yet by Debian, and I had to put in a second
NIC.  Do I have to add a graphics card too now to get 1920x1200?

Thanks.

cat /etc/debian_version
11.6

lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Device 4692 (rev 0c)

dpkg --get-selections | grep firmware
firmware-linux-free install

dpkg --get-selections | grep xserver-xorg-video-*
xserver-xorg-video-all  install
xserver-xorg-video-amdgpu   install
xserver-xorg-video-ati  install
xserver-xorg-video-fbdevinstall
xserver-xorg-video-intelinstall
xserver-xorg-video-nouveau  install
xserver-xorg-video-qxl  install
xserver-xorg-video-radeon   install
xserver-xorg-video-vesa install
xserver-xorg-video-vmware   install

grep Driver  /var/log/Xorg.0.log | grep II
[52.843] (II) modesetting: Driver for Modesetting Kernel Drivers: kms

inxi -GSaz
System:
  Kernel: 5.10.0-20-amd64 arch: x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-20-amd64
root=UUID=82fc750d-98f2-4096-9d84-17a2690d1dcf ro quiet
  Desktop: FVWM v: 2.6.8 vt: 1 dm: startx Distro: Debian GNU/Linux 11
(bullseye)
Graphics:
  Device-1: Intel vendor: ASUSTeK driver: N/A arch: Gen-12.2
process: Intel 10nm built: 2021-22+ bus-ID: 00:02.0 chip-ID: 8086:4692
class-ID: 0300
  Display: server: X.Org v: 1.20.11 driver: X: loaded: vesa
unloaded: fbdev,modesetting dri: swrast gpu: N/A display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm (10.67x7.99")
s-diag: 339mm (13.33")
  Monitor-1: default res: 1024x768 hz: 76 size: N/A modes: N/A
  API: OpenGL v: 4.5 Mesa 20.3.5 renderer: llvmpipe (LLVM 11.0.1 256 bits)
compat-v: 3.1 direct render: Yes

cat ~/.local/share/xorg/Xorg.0.log | pastebinit
https://paste.debian.net/1264692/

Re: loss of screen resolution

[Kleene, Steven (kleenesj)]

On December 1, 2022 9:41 PM, I wrote:
>> Out of the blue today, my usual screen resolution (1920x1200) became
>> unavailable. ...

On Sunday, December 4, 2022 1:26 AM, Felix Miata 
replied:
> Do you have another VGA cable you could try? Do you have any other PCs with
> VGA output available that you could test with your display?

My cable has one end male and one female, and I don't have a spare or a
useful adapter.  I tried swapping in another monitor using the cable from the
problem build.  The resolution problem persisted.  So the cable is still
a suspect.

On Sunday, December 4, 2022 8:22 PM, Felix Miata 
replied:
> Save the following as /etc/X11/xorg.conf.d/40-vga.conf:
>
> Section "Monitor"
> Identifier "DefaultMonitor"
> VendorName  "Dell"
> ModelName   "U2412M"
> HorizSync   30-83
> VertRefresh 50-61
> Option  "PreferredMode" "1920x1200"
> EndSection

Thanks.  I tried that and was again unsuccessful.

I guess this is in software or in the cable.  I could buy another cable, but
I'm the process of getting a new desktop built anyway.  I think I'll just
live with this until I can abandon ship.

Thanks for all your efforts, Felix.  I did learn a few things.


From: Felix Miata 
Sent: Sunday, December 4, 2022 8:22 PM
To: debian-user@lists.debian.org
Subject: Re: loss of screen resolution

External Email: Use Caution


Kleene, Steven (kleenesj) composed on 2022-12-04 18:03 (UTC):

> I do have /usr/lib/xserver-xorg-video-intel.  I don't have
> /etc/X11/xorg.conf.d/ but do have /usr/share/X11/xorg.conf.d/ with the
> following:
>   10-amdgpu.conf  10-quirks.conf  10-radeon.conf  40-libinput.conf  
> 70-wacom.conf
> It wasn't obvious to me that these were relevant.

> I don't have any useful spare hardware at home, although I do at work.  I
> could steal a VGA cable to test here.

If nothing yet suggested works, a more flexible solution than a manually 
generated
& hard-coded modeline applied after X has already started is letting the server
generate one on startup based upon the formerly provided EDID basics I retrieved
from your old Xorg.0.log:

Ranges: V min: 50 V max: 61 Hz, H min: 30 H max: 83 kHz

Save the following as /etc/X11/xorg.conf.d/40-vga.conf:

Section "Monitor"
Identifier "DefaultMonitor"
VendorName  "Dell"
ModelName   "U2412M"
HorizSync   30-83
VertRefresh 50-61
Option  "PreferredMode" "1920x1200"
EndSection

This early application ought to make it behave more like it used to, unless the
problem is actually inside the display. I've had two 1920x1200s die on me, a 
Dell
made in 2005 and a Lenovo made in 2009. My 2560x1080 Dell only lasted 5 years
before refusing to power on any more. :~( The two 1920x1200 I have now are 2011
NEC and 2012 Samsung.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: loss of screen resolution

[Felix Miata]

Kleene, Steven (kleenesj) composed on 2022-12-04 18:03 (UTC):

> I do have /usr/lib/xserver-xorg-video-intel.  I don't have
> /etc/X11/xorg.conf.d/ but do have /usr/share/X11/xorg.conf.d/ with the
> following:
>   10-amdgpu.conf  10-quirks.conf  10-radeon.conf  40-libinput.conf  
> 70-wacom.conf
> It wasn't obvious to me that these were relevant.

> I don't have any useful spare hardware at home, although I do at work.  I
> could steal a VGA cable to test here.

If nothing yet suggested works, a more flexible solution than a manually 
generated
& hard-coded modeline applied after X has already started is letting the server
generate one on startup based upon the formerly provided EDID basics I retrieved
from your old Xorg.0.log:

Ranges: V min: 50 V max: 61 Hz, H min: 30 H max: 83 kHz

Save the following as /etc/X11/xorg.conf.d/40-vga.conf:

Section "Monitor"
Identifier "DefaultMonitor"
VendorName  "Dell"
ModelName   "U2412M"
HorizSync   30-83
VertRefresh 50-61
Option  "PreferredMode" "1920x1200"
EndSection

This early application ought to make it behave more like it used to, unless the
problem is actually inside the display. I've had two 1920x1200s die on me, a 
Dell
made in 2005 and a Lenovo made in 2009. My 2560x1080 Dell only lasted 5 years
before refusing to power on any more. :~( The two 1920x1200 I have now are 2011
NEC and 2012 Samsung.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: loss of screen resolution

[Kleene, Steven (kleenesj)]

On December 1, 2022 9:41 PM, I wrote:
>> Out of the blue today, my usual screen resolution (1920x1200) became
>> unavailable. ...

On December 4, 2022 1:26 AM, Felix Miata  replied:
> Your old Xorg.0.logs differ significantly from your current ones ...
> This suggests to me your EDID is currently being misread or is incomplete.
> Does your VGA cable have 15 pins on both ends, or only 14? ...

It has 14 pins.  This monitor and cable have worked fine since 2014 with this
desktop running Debian.  About a week before the problem started, I did
disconnect the VGA cable from the desktop input.  I just reseated it
carefully and even rebooted, but that didn't fix the problem.  Maybe I fried
something messing with the connection.

I can confirm that my /var/log/Xorg.0.log (Jul  3  2021) has the EDID content
while ~/.local/share/xorg/Xorg.0.log (Dec  4 11:57) does not.

> Something to try: switch display driver from modesetting to intel. If
> xserver-xorg-video-intel is not installed, it should be used automatically if
> you install it. If it's already installed, then likely there's a .conf file
> in /etc/X11/xorg.conf.d/ specifically calling it that you could switch to
> calling intel instead.

I do have /usr/lib/xserver-xorg-video-intel.  I don't have
/etc/X11/xorg.conf.d/ but do have /usr/share/X11/xorg.conf.d/ with the
following:
  10-amdgpu.conf  10-quirks.conf  10-radeon.conf  40-libinput.conf  
70-wacom.conf
It wasn't obvious to me that these were relevant.

I don't have any useful spare hardware at home, although I do at work.  I
could steal a VGA cable to test here.

Thanks again.


From: Felix Miata 
Sent: Sunday, December 4, 2022 1:26 AM
To: debian-user@lists.debian.org
Subject: Re: loss of screen resolution

External Email: Use Caution


Kleene, Steven (kleenesj) composed on 2022-12-02 02:41 (UTC):
...
Your old Xorg.0.logs differ significantly from your current ones, and my
own on a similar Intel GPU. In what follows, the current ones and the old
ones omit everything between the first and last lines:

*
[  2059.607] (II) modeset(0): EDID for output VGA-1
[  2059.607] (II) modeset(0): Manufacturer: DEL  Model: a079  Serial#: 810693964
[  2059.607] (II) modeset(0): Year: 2014  Week: 24
[  2059.607] (II) modeset(0): EDID Version: 1.3
[  2059.607] (II) modeset(0): Analog Display Input,  Input Voltage Level: 
0.700/0.300 V
[  2059.607] (II) modeset(0): Sync:  Separate  Composite  SyncOnGreen
[  2059.607] (II) modeset(0): Max Image Size [cm]: horiz.: 52  vert.: 32
[  2059.607] (II) modeset(0): Gamma: 2.20
[  2059.607] (II) modeset(0): DPMS capabilities: StandBy Suspend Off; RGB/Color 
Display
[  2059.607] (II) modeset(0): First detailed timing is preferred mode
[  2059.607] (II) modeset(0): redX: 0.640 redY: 0.330   greenX: 0.300 greenY: 
0.600
[  2059.607] (II) modeset(0): blueX: 0.150 blueY: 0.060   whiteX: 0.313 whiteY: 
0.329
[  2059.607] (II) modeset(0): Supported established timings:
[  2059.607] (II) modeset(0): 720x400@70Hz
[  2059.607] (II) modeset(0): 640x480@60Hz
[  2059.607] (II) modeset(0): 800x600@60Hz
[  2059.607] (II) modeset(0): 1024x768@60Hz
[  2059.607] (II) modeset(0): Manufacturer's mask: 0
[  2059.607] (II) modeset(0): Supported standard timings:
[  2059.607] (II) modeset(0): #0: hsize: 1280  vsize 960  refresh: 60  vid: 
16513
[  2059.607] (II) modeset(0): #1: hsize: 1280  vsize 1024  refresh: 60  vid: 
32897
[  2059.607] (II) modeset(0): #2: hsize: 1600  vsize 1200  refresh: 60  vid: 
16553
[  2059.607] (II) modeset(0): #3: hsize: 1680  vsize 1050  refresh: 60  vid: 179
[  2059.607] (II) modeset(0): #4: hsize: 1920  vsize 1080  refresh: 60  vid: 
49361
[  2059.607] (II) modeset(0): Supported detailed timing:
[  2059.607] (II) modeset(0): clock: 154.0 MHz   Image Size:  518 x 324 mm
[  2059.607] (II) modeset(0): h_active: 1920  h_sync: 1968  h_sync_end 2000 
h_blank_end 2080 h_border: 0
[  2059.607] (II) modeset(0): v_active: 1200  v_sync: 1203  v_sync_end 1209 
v_blanking: 1235 v_border: 0
[  2059.607] (II) modeset(0): Serial No: YMYH146D0R5L
[  2059.607] (II) modeset(0): Monitor name: DELL U2412M
[  2059.608] (II) modeset(0): Ranges: V min: 50 V max: 61 Hz, H min: 30 H max: 
83 kHz, PixClock max 175 MHz
[  2059.608] (II) modeset(0): EDID (in hex):
[  2059.608] (II) modeset(0):   000010ac79a04c355230
[  2059.608] (II) modeset(0):   181801030e342078eaee95a3544c9926
[  2059.608] (II) modeset(0):   0f5054a1080081408180a940b300d1c0
[  2059.608] (II) modeset(0):   010101010101283c80a070b023403020
[  2059.608] (II) modeset(0):   36000644211a00ff00594d59
[  2059.608] (II) modeset(0):   48313436443052354c0a00fc0044
[  2059.608] (II) modeset(0):   454c4c2055323431324d0a2000fd
[  2059.608] (II) modeset(0):   00323d1e5311000a2020202020200092
[  2059.608] (II) modeset(0): Printing probed modes for output VGA-1
*

This suggests to me your EDID is currently being misread or is incomple

Re: loss of screen resolution

[Felix Miata]

Kleene, Steven (kleenesj) composed on 2022-12-02 02:41 (UTC):
... 
Your old Xorg.0.logs differ significantly from your current ones, and my
own on a similar Intel GPU. In what follows, the current ones and the old
ones omit everything between the first and last lines:

*
[  2059.607] (II) modeset(0): EDID for output VGA-1
[  2059.607] (II) modeset(0): Manufacturer: DEL  Model: a079  Serial#: 810693964
[  2059.607] (II) modeset(0): Year: 2014  Week: 24
[  2059.607] (II) modeset(0): EDID Version: 1.3
[  2059.607] (II) modeset(0): Analog Display Input,  Input Voltage Level: 
0.700/0.300 V
[  2059.607] (II) modeset(0): Sync:  Separate  Composite  SyncOnGreen
[  2059.607] (II) modeset(0): Max Image Size [cm]: horiz.: 52  vert.: 32
[  2059.607] (II) modeset(0): Gamma: 2.20
[  2059.607] (II) modeset(0): DPMS capabilities: StandBy Suspend Off; RGB/Color 
Display
[  2059.607] (II) modeset(0): First detailed timing is preferred mode
[  2059.607] (II) modeset(0): redX: 0.640 redY: 0.330   greenX: 0.300 greenY: 
0.600
[  2059.607] (II) modeset(0): blueX: 0.150 blueY: 0.060   whiteX: 0.313 whiteY: 
0.329
[  2059.607] (II) modeset(0): Supported established timings:
[  2059.607] (II) modeset(0): 720x400@70Hz
[  2059.607] (II) modeset(0): 640x480@60Hz
[  2059.607] (II) modeset(0): 800x600@60Hz
[  2059.607] (II) modeset(0): 1024x768@60Hz
[  2059.607] (II) modeset(0): Manufacturer's mask: 0
[  2059.607] (II) modeset(0): Supported standard timings:
[  2059.607] (II) modeset(0): #0: hsize: 1280  vsize 960  refresh: 60  vid: 
16513
[  2059.607] (II) modeset(0): #1: hsize: 1280  vsize 1024  refresh: 60  vid: 
32897
[  2059.607] (II) modeset(0): #2: hsize: 1600  vsize 1200  refresh: 60  vid: 
16553
[  2059.607] (II) modeset(0): #3: hsize: 1680  vsize 1050  refresh: 60  vid: 179
[  2059.607] (II) modeset(0): #4: hsize: 1920  vsize 1080  refresh: 60  vid: 
49361
[  2059.607] (II) modeset(0): Supported detailed timing:
[  2059.607] (II) modeset(0): clock: 154.0 MHz   Image Size:  518 x 324 mm
[  2059.607] (II) modeset(0): h_active: 1920  h_sync: 1968  h_sync_end 2000 
h_blank_end 2080 h_border: 0
[  2059.607] (II) modeset(0): v_active: 1200  v_sync: 1203  v_sync_end 1209 
v_blanking: 1235 v_border: 0
[  2059.607] (II) modeset(0): Serial No: YMYH146D0R5L
[  2059.607] (II) modeset(0): Monitor name: DELL U2412M
[  2059.608] (II) modeset(0): Ranges: V min: 50 V max: 61 Hz, H min: 30 H max: 
83 kHz, PixClock max 175 MHz
[  2059.608] (II) modeset(0): EDID (in hex):
[  2059.608] (II) modeset(0):   000010ac79a04c355230
[  2059.608] (II) modeset(0):   181801030e342078eaee95a3544c9926
[  2059.608] (II) modeset(0):   0f5054a1080081408180a940b300d1c0
[  2059.608] (II) modeset(0):   010101010101283c80a070b023403020
[  2059.608] (II) modeset(0):   36000644211a00ff00594d59
[  2059.608] (II) modeset(0):   48313436443052354c0a00fc0044
[  2059.608] (II) modeset(0):   454c4c2055323431324d0a2000fd
[  2059.608] (II) modeset(0):   00323d1e5311000a2020202020200092
[  2059.608] (II) modeset(0): Printing probed modes for output VGA-1
*

This suggests to me your EDID is currently being misread or is incomplete.
Does your VGA cable have 15 pins on both ends, or only 14? Do you have
another VGA cable you could try? Do you have any other PCs with VGA output
available that you could test with your display? Do you have a FullHD TV
with VGA input you could test 1920x1080 with? Perhaps your cable simply
could use a removal and refitting.

Something to try: switch display driver from modesetting to intel. If
xserver-xorg-video-intel is not installed, it should be used automatically
if you install it. If it's already installed, then likely there's a .conf
file in /etc/X11/xorg.conf.d/ specifically calling it that you could switch
to calling intel instead.

The modesetting display driver is newer technology developed in large part
by Intel's driver programmers, and is responsible for the intel display
driver not having an official release in nearly a decade. Sometimes it works
better, or at least works when the modesetting driver has a bug, but the
modesetting is actually the default for AMD, Intel, NVidia and all other GPUs
for which a KMS module exists.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: loss of screen resolution

[Felix Miata]

Kleene, Steven (kleenesj) composed on 2022-12-02 02:41 (UTC):

See if adding the following file helps:
---
# cat /etc/X11/xorg.conf.d/25-intelExtra.conf
Section "Device"
Identifier  "IntelKludges"
Option  "ReprobeOutputs" "on"   # default off
EndSection
---

"(WW) VGA arbiter: cannot open kernel arbiter, no multi-card support"
from your logs puzzles me. :( Is this in a VM?
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: loss of screen resolution

[Kleene, Steven (kleenesj)]

On December 1, 2022 9:41 PM, I wrote:

>> Out of the blue today, my usual screen resolution (1920x1200) became
>> unavailable. ...

On December 3, 2022 1:23 PM, Felix Miata  wrote:

> This and http://paste.debian.net/1262700/ are the same log created Sat Jul 3
> 16:37:19 2021 using kernel 4.19.0-17-amd64. If these are from /var/log/ then
> look in ~/.local/share/xorg/ for a current one.

Sorry, I should have noticed that.  Here are the contents of
~/.local/share/xorg/Xorg.0.log, first from the console after a fresh boot:
  http://paste.debian.net/1262763/
then after calling startx and coming up 1024x768:
  http://paste.debian.net/1262764/
and finally after using xrandr to get 1920x1200:
  http://paste.debian.net/1262765/

The second and third files only differ by one line at the end.  Thanks.


From: Felix Miata 
Sent: Saturday, December 3, 2022 1:23 PM
To: debian-user@lists.debian.org
Subject: Re: loss of screen resolution

External Email: Use Caution


Kleene, Steven (kleenesj) composed on 2022-12-03 14:15 (UTC):

> For Xorg.0.log,
> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpaste.debian.net%2F1262735%2Fdata=05%7C01%7Ckleenesj%40ucmail.uc.edu%7Cfb8f5bce786f42dc921308dad55c42f3%7Cf5222e6c5fc648eb8f0373db18203b63%7C1%7C0%7C638056889486652349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=cEu7XkZUJn3VOTiLcdvcVEvidGKsA8RLvXd1kUf7oR8%3Dreserved=0

This and 
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpaste.debian.net%2F1262700%2Fdata=05%7C01%7Ckleenesj%40ucmail.uc.edu%7Cfb8f5bce786f42dc921308dad55c42f3%7Cf5222e6c5fc648eb8f0373db18203b63%7C1%7C0%7C638056889486652349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=6zqt%2FcKItF3u%2BCd7nzEQOizl9DeiksEDaNBS6BHpUb0%3Dreserved=0
 are the same log created
Sat Jul 3 16:37:19 2021 using kernel 4.19.0-17-amd64. If these are from 
/var/log/
then look in ~/.local/share/xorg/ for a current one.

Current kernel is 4.19.0-22-amd64.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: loss of screen resolution

[Felix Miata]

Kleene, Steven (kleenesj) composed on 2022-12-03 14:15 (UTC):

> For Xorg.0.log,
> http://paste.debian.net/1262735/

This and http://paste.debian.net/1262700/ are the same log created
Sat Jul 3 16:37:19 2021 using kernel 4.19.0-17-amd64. If these are from 
/var/log/
then look in ~/.local/share/xorg/ for a current one.

Current kernel is 4.19.0-22-amd64.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: loss of screen resolution

[Kleene, Steven (kleenesj)]

On December 1, 2022 9:41 PM, I wrote:
>>> Out of the blue today, my usual screen resolution (1920x1200) became
>>> unavailable. ...

On December 2, 2022 10:12 AM, Felix Miata  wrote:
>> ... run
>> inxi -U
>> to upgrade, and post here output from within an X terminal:
>> inxi -GSaz
>> ...
>> Next, give us the whole log to see:
cat /var/log/Xorg.0.log | pastebinit

And on December 3, 2022 1:14 AM, Felix Miata  added:

> Did these result after applying your xrandr workaround? If the problem
> remains in absence of the workaround, the inxi and log need to come from
> being in that condition.

I had done those after the workaround.  So I exited fvwm back to the console,
recalled fvwm via startx, and gathered the information again before doing the
workaround.
inxi ->
System:
  Kernel: 4.19.0-22-amd64 arch: x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-22-amd64
root=UUID=093750e2-4489-4550-a3fc-5e86b450320b ro quiet
  Desktop: FVWM v: 2.6.8 vt: 1 dm: startx Distro: Debian GNU/Linux 10
(buster)
Graphics:
  Device-1: Intel 82946GZ/GL Integrated Graphics driver: i915 v: kernel
arch: Gen-3.5 process: Intel 90nm built: 2005-06 ports: active: VGA-1
empty: none bus-ID: 00:02.0 chip-ID: 8086:2972 class-ID: 0300
  Display: server: X.Org v: 1.20.4 driver: X: loaded: modesetting
unloaded: fbdev,vesa dri: i965 gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 270x203mm (10.63x7.99")
s-diag: 338mm (13.3")
  Monitor-1: VGA-1 res: 1024x768 hz: 60 size: N/A modes: max: 1024x768
min: 640x480
  API: OpenGL v: 2.1 Mesa 18.3.6 renderer: Mesa DRI Intel 946GZ
direct render: Yes

This is the same as before except showing 1024x768 instead of 1920x1200.

For Xorg.0.log,
http://paste.debian.net/1262735/

Thanks again.


From: Felix Miata 
Sent: Saturday, December 3, 2022 1:14 AM
To: debian-user@lists.debian.org
Subject: Re: loss of screen resolution

External Email: Use Caution


Kleene, Steven (kleenesj) composed on 2022-12-02 02:20 (UTC):

>> Next, give us the whole log to see:
> cat /var/log/Xorg.0.log | pastebinit

> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpaste.debian.net%2F1262700%2Fdata=05%7C01%7Ckleenesj%40ucmail.uc.edu%7Ccfc9a461f864488b9b7108dad4f5c190%7Cf5222e6c5fc648eb8f0373db18203b63%7C1%7C0%7C638056449240692027%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=pQ9QP%2BuDQ2%2BjbzxZB815Oo2YL8z022xO%2BTjkzHaH1%2BE%3Dreserved=0

> That's a lot to look at.  Thank you.

I don't see anything to suggest that there's anything wrong. Did these result
after applying your xrandr workaround? If the problem remains in absence of the
workaround, the inxi and log need to come from being in that condition. I have
something similar needing no correction or workaround:

# inxi -GSaz --vs --zl --hostname
inxi 3.3.23-00 (2022-10-31)
System:
  Host: gx62b Kernel: 4.19.0-22-amd64 arch: x86_64 bits: 64 compiler: gcc
v: 8.3.0 parameters: root=LABEL= ipv6.disable=1 net.ifnames=0
biosdevname=0 plymouth.enable=0 noresume mitigations=auto consoleblank=0
  Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 10 (buster)
Graphics:
  Device-1: Intel 82945G/GZ Integrated Graphics vendor: Dell driver: i915
v: kernel arch: Gen-3.5 process: Intel 90nm built: 2005-06 ports:
active: DVI-D-1,VGA-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:2772
class-ID: 0300
  Display: x11 server: X.Org v: 1.20.4 driver: X: loaded: intel
unloaded: fbdev,modesetting,vesa dri: i915 gpu: i915 display-ID: :0
screens: 1
  Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.00x10.00")
s-diag: 803mm (31.62")
  Monitor-1: DVI-D-1 mapped: DVI1 pos: primary,left model: NEC EA243WM
serial:  built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 520x320mm (20.47x12.6") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
  Monitor-2: VGA-1 mapped: VGA1 pos: right model: Dell P2213
serial:  built: 2012 res: 1680x1050 hz: 60 dpi: 91 gamma: 1.2
size: 470x300mm (18.5x11.81") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
  API: OpenGL v: 1.4 Mesa 18.3.6 renderer: Mesa DRI Intel 945G
direct render: Yes
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: loss of screen resolution

[Felix Miata]

Kleene, Steven (kleenesj) composed on 2022-12-02 02:20 (UTC):

>> Next, give us the whole log to see:
> cat /var/log/Xorg.0.log | pastebinit

> http://paste.debian.net/1262700/

> That's a lot to look at.  Thank you.

I don't see anything to suggest that there's anything wrong. Did these result
after applying your xrandr workaround? If the problem remains in absence of the
workaround, the inxi and log need to come from being in that condition. I have
something similar needing no correction or workaround:

# inxi -GSaz --vs --zl --hostname
inxi 3.3.23-00 (2022-10-31)
System:
  Host: gx62b Kernel: 4.19.0-22-amd64 arch: x86_64 bits: 64 compiler: gcc
v: 8.3.0 parameters: root=LABEL= ipv6.disable=1 net.ifnames=0
biosdevname=0 plymouth.enable=0 noresume mitigations=auto consoleblank=0
  Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 10 (buster)
Graphics:
  Device-1: Intel 82945G/GZ Integrated Graphics vendor: Dell driver: i915
v: kernel arch: Gen-3.5 process: Intel 90nm built: 2005-06 ports:
active: DVI-D-1,VGA-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:2772
class-ID: 0300
  Display: x11 server: X.Org v: 1.20.4 driver: X: loaded: intel
unloaded: fbdev,modesetting,vesa dri: i915 gpu: i915 display-ID: :0
screens: 1
  Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.00x10.00")
s-diag: 803mm (31.62")
  Monitor-1: DVI-D-1 mapped: DVI1 pos: primary,left model: NEC EA243WM
serial:  built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 520x320mm (20.47x12.6") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
  Monitor-2: VGA-1 mapped: VGA1 pos: right model: Dell P2213
serial:  built: 2012 res: 1680x1050 hz: 60 dpi: 91 gamma: 1.2
size: 470x300mm (18.5x11.81") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
  API: OpenGL v: 1.4 Mesa 18.3.6 renderer: Mesa DRI Intel 945G
direct render: Yes
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: loss of screen resolution

[Kleene, Steven (kleenesj)]

On December 1, 2022 9:41 PM, I wrote:

>> Out of the blue today, my usual screen resolution (1920x1200) became
>> unavailable. ...

On December 2, 2022 10:12 AM, Felix Miata  wrote:

> ... run
> inxi -U
> to upgrade, and post here output from within an X terminal:
> inxi -GSaz

System:
  Kernel: 4.19.0-22-amd64 arch: x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-22-amd64
root=UUID=093750e2-4489-4550-a3fc-5e86b450320b ro quiet
  Desktop: FVWM v: 2.6.8 vt: 1 dm: startx Distro: Debian GNU/Linux 10
(buster)
Graphics:
  Device-1: Intel 82946GZ/GL Integrated Graphics driver: i915 v: kernel
arch: Gen-3.5 process: Intel 90nm built: 2005-06 ports: active: VGA-1
empty: none bus-ID: 00:02.0 chip-ID: 8086:2972 class-ID: 0300
  Display: server: X.Org v: 1.20.4 driver: X: loaded: modesetting
unloaded: fbdev,vesa dri: i965 gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 507x317mm (19.96x12.48")
s-diag: 598mm (23.54")
  Monitor-1: VGA-1 res: 1920x1200 hz: 60 size: N/A modes: max: 1024x768
min: 640x480
  API: OpenGL v: 2.1 Mesa 18.3.6 renderer: Mesa DRI Intel 946GZ
direct render: Yes

> Next, give us the whole log to see:
cat /var/log/Xorg.0.log | pastebinit

http://paste.debian.net/1262700/

That's a lot to look at.  Thank you.


From: Felix Miata 
Sent: Friday, December 2, 2022 10:12 AM
To: debian-user@lists.debian.org
Subject: Re: loss of screen resolution

External Email: Use Caution


Kleene, Steven (kleenesj) composed on 2022-12-02 13:11 (UTC):

> I'll add that I did do a weekly apt upgrade shortly before this happened,

Now let's see how all those things Dan asked for work together:

Install/Upgrade inxi. Buster's inxi is a broken antique. Best to install 
directly
from upstream. It's just a data collection and presentation script:
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsmxi.org%2Fdocs%2Finxi-installation.htm%23inxi-manual-installdata=05%7C01%7Ckleenesj%40ucmail.uc.edu%7C0b895e40ae1845abc85b08dad477c4ea%7Cf5222e6c5fc648eb8f0373db18203b63%7C1%7C0%7C638055908118333462%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=Od8tsIGlAhdF8HQbnDo2shuCpiPVRwr8jqATtd6vhhI%3Dreserved=0
To upgrade Debian's version, it's necessary to edit /etc/inxi.conf to remove the
upgrade blockage, so change B_ALLOW_UPDATE=false to B_ALLOW_UPDATE=true, then 
run

inxi -U

to upgrade, and post here output from within an X terminal:

inxi -GSaz

Next, give us the whole log to see:

cat /var/log/Xorg.0.log | pastebinit
or
cat ~/.local/share/xorg/Xorg.0.log | pastebinit

and provide the resulting URI here, or attach the file to your reply. Don't 
paste
its content into the email unless you know how to prevent line wrapping that 
makes
a mess of it.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: loss of screen resolution

[Felix Miata]

Kleene, Steven (kleenesj) composed on 2022-12-02 13:11 (UTC):

> I'll add that I did do a weekly apt upgrade shortly before this happened,

Now let's see how all those things Dan asked for work together:

Install/Upgrade inxi. Buster's inxi is a broken antique. Best to install 
directly
from upstream. It's just a data collection and presentation script:
https://smxi.org/docs/inxi-installation.htm#inxi-manual-install
To upgrade Debian's version, it's necessary to edit /etc/inxi.conf to remove the
upgrade blockage, so change B_ALLOW_UPDATE=false to B_ALLOW_UPDATE=true, then 
run

inxi -U

to upgrade, and post here output from within an X terminal:

inxi -GSaz

Next, give us the whole log to see:

cat /var/log/Xorg.0.log | pastebinit
or
cat ~/.local/share/xorg/Xorg.0.log | pastebinit

and provide the resulting URI here, or attach the file to your reply. Don't 
paste
its content into the email unless you know how to prevent line wrapping that 
makes
a mess of it.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Re: loss of screen resolution

[Kleene, Steven (kleenesj)]

On December 1, 2022 9:41 PM, I wrote:

>> Out of the blue today, my usual screen resolution (1920x1200) became
>> unavailable. ...

On December 2, 2022 7:43 AM, Dan Ritter  replied:

> I'm going to guess that this is a change in one or both of:
>
> - GPU firmware
> - X11 GPU driver
>
> Let's get the output from:
>
> cat /etc/debian_version

10.13

> lspci | grep VGA

00:02.0 VGA compatible controller: Intel Corporation 82946GZ/GL Integrated 
Graphics Controller (rev 02)

> dpkg --get-selections | grep firmware

firmware-linux-free install

> dpkg --get-selections | grep xserver-xorg-video-*

xserver-xorg-video-all  install
xserver-xorg-video-amdgpu   install
xserver-xorg-video-ati  install
xserver-xorg-video-fbdevinstall
xserver-xorg-video-intelinstall
xserver-xorg-video-nouveau  install
xserver-xorg-video-qxl  install
xserver-xorg-video-radeon   install
xserver-xorg-video-vesa install
xserver-xorg-video-vmware   install

> grep Driver  /var/log/Xorg.0.log|grep II

[  2059.194] (II) modesetting: Driver for Modesetting Kernel Drivers: kms

I'll add that I did do a weekly apt upgrade shortly before this happened, but
it's not obvious that any of the upgrades (firefox-esr grub-common grub-pc
grub-pc-bin grub2-common krb5-locales libgssapi-krb5-2 libgssapi-krb5-2:i386
libk5crypto3 libk5crypto3:i386 libkrb5-3 libkrb5-3:i386 libkrb5support0
libkrb5support0:i386 vim-common vim-tiny xxd) are relevant.

Thanks.


From: Dan Ritter 
Sent: Friday, December 2, 2022 7:43 AM
To: Kleene, Steven (kleenesj)
Cc: debian-user@lists.debian.org
Subject: Re: loss of screen resolution

External Email: Use Caution


Kleene, Steven (kleenesj) wrote:
> Out of the blue today, my usual screen resolution (1920x1200) became
> unavailable.  I booted to the console and called startx, which brings up
> fvwm.  But my default base window went way off-screen, and the type was huge.
> xrandr said I was at 1024x768 and did not list the 1920x1200 option at all.
> (It usually does.)  I was able to define and call that option in my base
> window with:
>
> xrandr --newmode "1920x1200_60.00"  193.25  1920 2056 2256 2592  1200 1203 
> 1209 1245 -hsync +vsync
> xrandr --addmode VGA-1 1920x1200_60.00
> xrandr --output VGA-1 --mode 1920x1200_60.00
>
> This gave me my usual window and font size, but there are some side issues
> (e.g. where icons go when I minimize them).
>
> In any case, I think the problem is upstream of X windows.  I boot to a
> console, and the font there was much bigger than usual.  Where is that
> controlled?  Any idea how to get this back to normal?  The monitor is set to
> an aspect ratio of 16:1.  Resetting the monitor and rebooting did not fix
> the problem.

I'm going to guess that this is a change in one or both of:

- GPU firmware
- X11 GPU driver

Let's get the output from:

cat /etc/debian_version
to find out what you're running

lspci | grep VGA
to find out what your graphics hardware is

dpkg --get-selections | grep firmware
to find out what firmware is installed

dpkg --get-selections | grep xserver-xorg-video-*
to find out whether the right video driver is installed

and finally,

grep Driver  /var/log/Xorg.0.log|grep II

or if that file is missing,

grep Driver ~/.local/share/xorg/Xorg.0.log | grep II

to find out what driver is actually being used

-dsr-

Re: loss of screen resolution

[Dan Ritter]

Kleene, Steven (kleenesj) wrote: 
> Out of the blue today, my usual screen resolution (1920x1200) became
> unavailable.  I booted to the console and called startx, which brings up
> fvwm.  But my default base window went way off-screen, and the type was huge.
> xrandr said I was at 1024x768 and did not list the 1920x1200 option at all.
> (It usually does.)  I was able to define and call that option in my base
> window with:
> 
> xrandr --newmode "1920x1200_60.00"  193.25  1920 2056 2256 2592  1200 1203 
> 1209 1245 -hsync +vsync
> xrandr --addmode VGA-1 1920x1200_60.00
> xrandr --output VGA-1 --mode 1920x1200_60.00
> 
> This gave me my usual window and font size, but there are some side issues
> (e.g. where icons go when I minimize them).
> 
> In any case, I think the problem is upstream of X windows.  I boot to a
> console, and the font there was much bigger than usual.  Where is that
> controlled?  Any idea how to get this back to normal?  The monitor is set to
> an aspect ratio of 16:1.  Resetting the monitor and rebooting did not fix
> the problem.

I'm going to guess that this is a change in one or both of:

- GPU firmware
- X11 GPU driver

Let's get the output from:

cat /etc/debian_version
to find out what you're running

lspci | grep VGA
to find out what your graphics hardware is

dpkg --get-selections | grep firmware
to find out what firmware is installed

dpkg --get-selections | grep xserver-xorg-video-*
to find out whether the right video driver is installed

and finally,

grep Driver  /var/log/Xorg.0.log|grep II

or if that file is missing,

grep Driver ~/.local/share/xorg/Xorg.0.log | grep II

to find out what driver is actually being used

-dsr-

loss of screen resolution

[Kleene, Steven (kleenesj)]

Out of the blue today, my usual screen resolution (1920x1200) became
unavailable.  I booted to the console and called startx, which brings up
fvwm.  But my default base window went way off-screen, and the type was huge.
xrandr said I was at 1024x768 and did not list the 1920x1200 option at all.
(It usually does.)  I was able to define and call that option in my base
window with:

xrandr --newmode "1920x1200_60.00"  193.25  1920 2056 2256 2592  1200 1203 1209 
1245 -hsync +vsync
xrandr --addmode VGA-1 1920x1200_60.00
xrandr --output VGA-1 --mode 1920x1200_60.00

This gave me my usual window and font size, but there are some side issues
(e.g. where icons go when I minimize them).

In any case, I think the problem is upstream of X windows.  I boot to a
console, and the font there was much bigger than usual.  Where is that
controlled?  Any idea how to get this back to normal?  The monitor is set to
an aspect ratio of 16:1.  Resetting the monitor and rebooting did not fix
the problem.

Thanks.

Re: After some effort, can't change grub screen resolution

[bridgenash...@gmail.com]

y.com/aqua+vitae) from TheFreeDictionary.com (http://www.thefreedictionary.com)

Sent from Yahoo Mail on Android

Re: Debian Live Advanced Micro Devices, Inc. [AMD/ATI] RS780 [Radeon HD 3200] screen resolution

[Richmond]

"Andrew M.A. Cater"  writes:

> On Sat, Jan 08, 2022 at 06:52:32PM +, Richmond wrote:
>> I am currently running Debian 10.
>> 
>> sudo lspci|grep VGA
>> 01:05.0 VGA compatible controller: Advanced Micro Devices,
>> Inc. [AMD/ATI] RS780 [Radeon HD 3200]
>> 
>> sudo xrandr
>> 
>> Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
>> VGA-0 connected primary 1440x900+0+0 (normal left inverted right x axis
>> y axis) 408mm x 255mm
>> 
>> 1440x900  59.89*+  74.98  
>>1280x1024 75.0260.02  
>>1024x768  75.0370.0760.00  
>>832x624   74.55  
>>800x600   72.1975.0060.3256.25  
>>640x480   75.0072.8166.6759.94  
>>720x400   70.08  
>> HDMI-0 disconnected (normal left inverted right x axis y axis)
>> 
>> So I boot the debian 11 live iso from usb and it only offers me three of
>> the lowest resolutions. I think what I need to do is tell the kernel
>> command line to install the radeon driver, or maybe copy an xorg.conf
>> file onto the live root but I cannot find any such file, no file which
>> contains 1440x900.
>> 
>> How can I get 1440x900 with the live cd?
>>
>
> You need the debian-live with non-free firmware included:
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.2.0-live+nonfree/amd64/bt-hybrid/
> and whichever desktop you want.
>
> I would very strongly suggest NOT to use debian-live images to install if
> you're not sure - as another user has found, they can install large amounts
> of extra software and would, instead, suggest installing using the non-free
> firmware netinst or the DVD:  
>
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.2.0+nonfree/amd64/iso-cd/firmware-11.2.0-amd64-netinst.iso
>
> or
>
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.2.0+nonfree/amd64/iso-dvd/firmware-11.2.0-amd64-DVD-1.iso
>
> then work through. The files you need are almost certainly in either
> firmware-linux-nonfree or firmware-misc-nonfree: it's probably worth
> installing those at some point to make sure.
>
> With every good wish, as ever,
>
> Andy cater

Thanks. The live non-free cd worked. Don't worry, I am not doing an
installation or upgrade, I just wanted to use a live cd.

Re: Debian Live Advanced Micro Devices, Inc. [AMD/ATI] RS780 [Radeon HD 3200] screen resolution

[Andrew M.A. Cater]

On Sat, Jan 08, 2022 at 06:52:32PM +, Richmond wrote:
> I am currently running Debian 10.
> 
> sudo lspci|grep VGA
> 01:05.0 VGA compatible controller: Advanced Micro Devices,
> Inc. [AMD/ATI] RS780 [Radeon HD 3200]
> 
> sudo xrandr
> 
> Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
> VGA-0 connected primary 1440x900+0+0 (normal left inverted right x axis
> y axis) 408mm x 255mm
> 
> 1440x900  59.89*+  74.98  
>1280x1024 75.0260.02  
>1024x768  75.0370.0760.00  
>832x624   74.55  
>800x600   72.1975.0060.3256.25  
>640x480   75.0072.8166.6759.94  
>720x400   70.08  
> HDMI-0 disconnected (normal left inverted right x axis y axis)
> 
> So I boot the debian 11 live iso from usb and it only offers me three of
> the lowest resolutions. I think what I need to do is tell the kernel
> command line to install the radeon driver, or maybe copy an xorg.conf
> file onto the live root but I cannot find any such file, no file which
> contains 1440x900.
> 
> How can I get 1440x900 with the live cd?
>

You need the debian-live with non-free firmware included: 
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.2.0-live+nonfree/amd64/bt-hybrid/
 and whichever desktop you want.

I would very strongly suggest NOT to use debian-live images to install if
you're not sure - as another user has found, they can install large amounts
of extra software and would, instead, suggest installing using the non-free
firmware netinst or the DVD:  

https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.2.0+nonfree/amd64/iso-cd/firmware-11.2.0-amd64-netinst.iso
 

or

https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.2.0+nonfree/amd64/iso-dvd/firmware-11.2.0-amd64-DVD-1.iso

then work through. The files you need are almost certainly in either 
firmware-linux-nonfree or firmware-misc-nonfree: it's probably worth installing 
those at some point to make sure.

With every good wish, as ever,

Andy cater

Debian Live Advanced Micro Devices, Inc. [AMD/ATI] RS780 [Radeon HD 3200] screen resolution

[Richmond]

I am currently running Debian 10.

sudo lspci|grep VGA
01:05.0 VGA compatible controller: Advanced Micro Devices,
Inc. [AMD/ATI] RS780 [Radeon HD 3200]

sudo xrandr

Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
VGA-0 connected primary 1440x900+0+0 (normal left inverted right x axis
y axis) 408mm x 255mm

1440x900  59.89*+  74.98  
   1280x1024 75.0260.02  
   1024x768  75.0370.0760.00  
   832x624   74.55  
   800x600   72.1975.0060.3256.25  
   640x480   75.0072.8166.6759.94  
   720x400   70.08  
HDMI-0 disconnected (normal left inverted right x axis y axis)

So I boot the debian 11 live iso from usb and it only offers me three of
the lowest resolutions. I think what I need to do is tell the kernel
command line to install the radeon driver, or maybe copy an xorg.conf
file onto the live root but I cannot find any such file, no file which
contains 1440x900.

How can I get 1440x900 with the live cd?

Re: Screen resolution during Stretch installation

[Étienne Mollier]

On 3/1/19 4:20 PM, Fabiano Ferronato wrote:
> I'm installing Debian in my Asus ROG GL552VW laptop (Intel and
> Nvidia video cards) and the resolution (probably 3840x2160)is
> set in a way  that the font size is so small that I have to
> almost  put my face on the monitor so I can read. And the
> windows size is also larger than the monitor area, so I can't
> see the buttons. I can complete the installation either way,
> but I want to know why this is happening and how to solve
> this.
[...]
> Where I can change the screen resolution during (or before)
> install?

Good Day,

In the Grub menu, where you are prompted to choose between
Graphical install, Install, and so on, you can hit 'e' to edit
the Grub entry and prepend the line:

set gfxpayload=keep

Then hit 'F10' to proceed to the installation.

This will conserve the resolution used by this menu, which
should be readable, contrary to the following steps.  Other
values should be possible if you want a better, still readable,
resolution:

set gfxpayload=1280x1024x32

This may answer at least the first question, hopefully.

Kind Regards,
-- 
Étienne Mollier 

All opinions are my own.

Re: Screen resolution during Stretch installation

[Pascal Hambourg]

Le 01/03/2019 à 18:30, Felix Miata a écrit :


Including either nomodeset or nouveau.modeset=0 for installation


is pointless, since the installer does not use KMS.


Another key is the i7-6700HQ provides HD 530 Intel video. Intel + NVidia 
usually equates to
"Optimus"


which makes nouveau.modeset=0 even more pointless, since only the Intel 
GPU drives the video outputs and may use KMS.

Re: Screen resolution during Stretch installation

[Felix Miata]

Fabiano Ferronato composed on 2019-03-01 16:20 (UTC+0100):

> I don't know if this is the wright place to ask, but I'm searching a lot
> trying to find a way to this problem.
> I'm installing Debian in my Asus ROG GL552VW laptop (Intel and Nvidia video
> cards) and the resolution (probably 3840x2160)is set in a way  that the
> font size is so small that I have to almost  put my face on the monitor so
> I can read. And the windows size is also larger than the monitor area, so I
> can't see the buttons. I can complete the installation either way, but I
> want to know why this is happening and how to solve this.
> After OS install, I try to follow Debian instructions to install Nvidia
> drivers. But I'm following every tutorial and ending up with a broken
> installation.

> So, my questions:
> Where I can change the screen resolution during (or before) install?
> After install, resolution is still wrong. How can I set OS resolution
> during install?

An alternative suggestion to Curt's is to utilize the kernel's KMS. Curt's 
suggestion included
disabling KMS with either the nomodeset or nouveau.modeset=0 string on the 
installer's cmdline.
Including video=2560x1440 or video=1920x1080 should increase the font sizes 
without disabling KMS.

Including either nomodeset or nouveau.modeset=0 for installation generally 
means its included in
/etc/default/grub and /boot/grub/grub.cfg on the installed system, continuing 
KMS blockage, and
making video performance suffer greatly. Both are intended as troubleshooting 
workarounds, though
traditionally, non-FOSS drivers have required disabling KMS full time.

Another key is the i7-6700HQ provides HD 530 Intel video. Intel + NVidia 
usually equates to
"Optimus", which generally means a requirement to follow special instructions 
for installing either
OS or NVidia drivers. These you can find by using Optimus, Prime and Bumblebee 
as search keywords.
Optimus instructions on https://wiki.archlinux.org/index.php/Optimus are 
reputedly very good, in
case any you find for Debian seem inadequate to task.

Note too that there are three potentially competent DDX drivers for NVidia, the 
non-FOSS from
NVidia, plus the two from Xorg, nouveau and modesetting. The newer technology 
modesetting is the
upstream default, included in the server package since 4 years ago, but most 
installations manage
to override it by installing all optional DDX drivers via virtual (meta) 
package, including
xserver-xorg-video-nouveau. BTW, upstream's name for DDX drivers takes the form
xf86-video-, helpful to know in evaluating search results.

Having the nouveau DDX installed blocks the modesetting DDX unless explicitly 
configured not to via
/etc/X11/xorg.conf*. IOW, if you purge xserver-xorg-video-nouveau, or 
explicitly configure its use,
before installing NVidia drivers, you get an opportunity to test whether you 
even need to add the
non-FOSS DDX.
-- 
Evolution as taught in public schools is religion, not science.

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

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

Re: Screen resolution during Stretch installation

[Curt]

On 2019-03-01, Fabiano Ferronato  wrote:
>
> Hi all!
>
> I don't know if this is the wright place to ask, but I'm searching a lot
> trying to find a way to this problem.
> I'm installing Debian in my Asus ROG GL552VW laptop (Intel and Nvidia video
> cards) and the resolution (probably 3840x2160)is set in a way  that the
> font size is so small that I have to almost  put my face on the monitor so
> I can read. And the windows size is also larger than the monitor area, so I
> can't see the buttons. I can complete the installation either way, but I
> want to know why this is happening and how to solve this.
> After OS install, I try to follow Debian instructions to install Nvidia
> drivers. But I'm following every tutorial and ending up with a broken
> installation.
>

This reddit thread I stumbled on seems pertinent to your case:

https://www.reddit.com/r/linuxquestions/comments/8f9slp/cant_install_any_linux_distro_on_my_asus_rog/

Apparently the key is to set the "nomodeset" boot parameter at the boot
prompt. 


-- 
“Let us again pretend that life is a solid substance, shaped like a globe,
which we turn about in our fingers. Let us pretend that we can make out a plain
and logical story, so that when one matter is despatched--love for instance--
we go on, in an orderly manner, to the next.” - Virginia Woolf, The Waves

Screen resolution during Stretch installation

[Fabiano Ferronato]

Hi all!

I don't know if this is the wright place to ask, but I'm searching a lot
trying to find a way to this problem.
I'm installing Debian in my Asus ROG GL552VW laptop (Intel and Nvidia video
cards) and the resolution (probably 3840x2160)is set in a way  that the
font size is so small that I have to almost  put my face on the monitor so
I can read. And the windows size is also larger than the monitor area, so I
can't see the buttons. I can complete the installation either way, but I
want to know why this is happening and how to solve this.
After OS install, I try to follow Debian instructions to install Nvidia
drivers. But I'm following every tutorial and ending up with a broken
installation.

So, my questions:
Where I can change the screen resolution during (or before) install?
After install, resolution is still wrong. How can I set OS resolution
during install?

I hope somebody could give some advice on where to go.

Thanks!!

Re: After some effort, can't change grub screen resolution

[Lance Simmons]

On Fri, Jun 29, 2018 at 4:34 AM Darac Marjal 
wrote:

>
> Is it BIOS (in which case you have grub-pc
> installed) or (U)EFI (in which case you have grub-efi-ia32 or
> grub-efi-amd64 installed)?
>

I have UEFI (which I just learned), but grub-pc is installed. I assume
that's because the UEFI has legacy mode turned on.

Can I move from grub-pc to grub-efi-amd64? There are a few random webpages
that suggest it's difficult; I haven't found an authoritative source that
says how to do it.

I didn't notice anything in the gnu.org help-grub archive that seemed
relevant, but I may have missed something.

-- 
Lance Simmons

Re: After some effort, can't change grub screen resolution

[Darac Marjal]

On Fri, Jun 29, 2018 at 12:49:53AM -0500, Lance Simmons wrote:

  I want to change grub screen resolution.
  Four facts:
  (1) "vbeinfo" and "videoinfo" return no result in grub.  The screen blanks 
and eventually I restart the computer.


This /probably/ means that grub doesn't know how to control your video 
device. 


  (2) "hwinfo --framebuffer" returns no result.  I would append the logfile, 
but it's 7500 lines long.
  (3) running

lspci  -v -s  $(lspci | grep ' VGA ' | cut -d" " -f 1)

  returns:
  00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics
  Controller (rev 35) (prog-if 00 [VGA controller])
  Subsystem: ASRock Incorporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller
  Flags: bus master, fast devsel, latency 0, IRQ 121
  Memory at 9000 (64-bit, non-prefetchable) [size=16M]
  Memory at 8000 (64-bit, prefetchable) [size=256M]
  I/O ports at f000 [size=64]
  [virtual] Expansion ROM at 000c [disabled] [size=128K]
  Capabilities: [d0] Power Management version 2
  Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Capabilities: [b0] Vendor Specific Information: Len=07 
  Kernel driver in use: i915
  Kernel modules: i915
  (4) So far, changing GRUB_GFXMODE (in /etc/default/grub) to several of the 
resolutions I know my monitor supports (and then
  running "sudo update-grub") has no effect.


Just as a wild stab-in-the-dark, have you tried GRUB_GFXMODE=auto ? This 
is the default when using gfxterm, though, so you've probably already 
got the best grub can do.


One thing that you don't mention, which could be potentially useful is 
how your computer boots. Is it BIOS (in which case you have grub-pc 
installed) or (U)EFI (in which case you have grub-efi-ia32 or 
grub-efi-amd64 installed)? UEFI brings easier access to higher 
resolutions, so if you have the option to switch to that, it may be 
beneficial.



  Any suggestions?
  I've been running sid for a year, but this has been a problem since I got the 
computer a couple of years ago and was running
  stable so I figure it's not sid-specific.
  --
  Lance Simmons


--
For more information, please reread.


signature.asc
Description: PGP signature

Re: After some effort, can't change grub screen resolution

[Felix Miata]

Lance Simmons composed on 2018-06-29 00:49 (UTC-0500):

> (1) "vbeinfo" and "videoinfo" return no result in grub.  The screen blanks
> and eventually I restart the computer.

Neither work at my current Grub2-efi prompt on Kaby Lake. From videoinfo, I do
get a two line output:

List of supported video modes:
Legend: mask/position=red/gree/blue/reserved
...
> (3) running

> lspci  -v -s  $(lspci | grep ' VGA ' | cut -d" " -f 1)

Give inxi -G -c0 a try.

> Any suggestions?

If you've only ever used UEFI boot mode on that Asrock, try booting a USB stick
or HD with Grub2 installed in CSM (non-UEFI/GPT) mode to see if either command
returns anything. Neither vbeinfo nor videoinfo has _ever_ worked for me. I
suspect those commands are not compatible with one of either various UEFI BIOS,
or all UEFI BIOS.

Ask on the help-grub or Grub-devel mailing lists if you can't get a Google
answer that lines up with my suspicion. and nothing useful turns up here. I only
use Grub2 on UEFI systems with GPT, always Grub Legacy with MBR disks.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

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

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

Re: After some effort, can't change grub screen resolution

[Michael Lange]

Hi,

On Fri, 29 Jun 2018 00:49:53 -0500
Lance Simmons  wrote:

(...)
> 
> (4) So far, changing GRUB_GFXMODE (in /etc/default/grub) to several of
> the resolutions I know my monitor supports (and then running "sudo
> update-grub") has no effect.
> 
> Any suggestions?

I had a similar problem some time ago; I am no expert, so I had to try a
few things, and finally came up with these lines in /etc/default/grub:

GRUB_GFXMODE=1024x768
GRUB_GFXPAYLOAD=1024x768

This works, at least here :)

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

You are an excellent tactician, Captain.  You let your second in
command attack while you sit and watch for weakness.
-- Khan Noonian Singh, "Space Seed", stardate 3141.9

After some effort, can't change grub screen resolution

[Lance Simmons]

I want to change grub screen resolution.

Four facts:

(1) "vbeinfo" and "videoinfo" return no result in grub.  The screen blanks
and eventually I restart the computer.

(2) "hwinfo --framebuffer" returns no result.  I would append the logfile,
but it's 7500 lines long.

(3) running

lspci  -v -s  $(lspci | grep ' VGA ' | cut -d" " -f 1)

returns:

00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35)
(prog-if 00 [VGA controller])
Subsystem: ASRock Incorporation Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 121
Memory at 9000 (64-bit, non-prefetchable) [size=16M]
Memory at 8000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [d0] Power Management version 2
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [b0] Vendor Specific Information: Len=07 
Kernel driver in use: i915
Kernel modules: i915

(4) So far, changing GRUB_GFXMODE (in /etc/default/grub) to several of the
resolutions I know my monitor supports (and then running "sudo
update-grub") has no effect.

Any suggestions?

I've been running sid for a year, but this has been a problem since I got
the computer a couple of years ago and was running stable so I figure it's
not sid-specific.

-- 
Lance Simmons

Re: How to fix screen resolution ( has been set to 1024 * 768 )

[Michael Fothergill]

On 12 January 2017 at 18:50, Michael Fothergill <
michael.fotherg...@gmail.com> wrote:

>
>
> On 12 January 2017 at 17:50, Cathy Gramze <rhia...@gmail.com> wrote:
>
>> And what video card/chipset do you have? I got the 1024x768 until I
>> installed firmware-Linux-nonfree to get the firmware for my integrated
>> Intel graphics. Perhaps you, too need some firmware. It's the best bet when
>> other distros Just Work, as they include non-free drivers by default, and
>> Debian doesn't.
>>
>>
>> cathy
>>
>>
> Presumably if you ran gNewSense which is a version of Debian recommended
> by the Free Software Foundation then you would have to use xorg.conf to set
> the screen resolution.
>
> Think gNewSense = orthodox ; Debian = reformed; Ubuntu =
> secular/heterodox..
>
> MF ​​
>
>
>
>>
>> On 01/12/2017 06:36 AM, Lisi Reisz wrote:
>>
>>> On Monday 09 January 2017 10:34:23 manashpal wrote:
>>>
>>>> After installing Debian latest Jessie in my system, I am getting a
>>>> 1024*768
>>>> screen resolution, but my monitor can render 1366*768. it is unlikely to
>>>> have got such a unexpected screen resolution like 1024*768. on the other
>>>> hand ubuntu, fedora, kali and many more linux distros has never
>>>> disappoint
>>>> me such a way. how can I fix it ? kindly let me know the steps I will
>>>> follow.thanks.m@n@sh..p@l
>>>>
>>> Which Desktop Environment, if any, are you using?
>>>
>>> Lisi
>>>
>>>
>>
>

Re: How to fix screen resolution ( has been set to 1024 * 768 )

[Cathy Gramze]

And what video card/chipset do you have? I got the 1024x768 until I 
installed firmware-Linux-nonfree to get the firmware for my integrated 
Intel graphics. Perhaps you, too need some firmware. It's the best bet 
when other distros Just Work, as they include non-free drivers by 
default, and Debian doesn't.



cathy


On 01/12/2017 06:36 AM, Lisi Reisz wrote:

On Monday 09 January 2017 10:34:23 manashpal wrote:

After installing Debian latest Jessie in my system, I am getting a 1024*768
screen resolution, but my monitor can render 1366*768. it is unlikely to
have got such a unexpected screen resolution like 1024*768. on the other
hand ubuntu, fedora, kali and many more linux distros has never disappoint
me such a way. how can I fix it ? kindly let me know the steps I will
follow.thanks.m@n@sh..p@l

Which Desktop Environment, if any, are you using?

Lisi

Re: How to fix screen resolution ( has been set to 1024 * 768 )

[Lisi Reisz]

On Monday 09 January 2017 10:34:23 manashpal wrote:
> After installing Debian latest Jessie in my system, I am getting a 1024*768
> screen resolution, but my monitor can render 1366*768. it is unlikely to
> have got such a unexpected screen resolution like 1024*768. on the other
> hand ubuntu, fedora, kali and many more linux distros has never disappoint
> me such a way. how can I fix it ? kindly let me know the steps I will
> follow.thanks.m@n@sh..p@l

Which Desktop Environment, if any, are you using?

Lisi

Re: How to fix screen resolution ( has been set to 1024 * 768 )

[Cathy Gramze]

  
  
We'd be happy to help. What videocard/chipset do you have? What
driver is currently in use? It really sounds like a simple driver
problem. 

cathy

On 01/09/2017 05:34 AM, manashpal
  wrote:

After installing Debian latest Jessie in my system, I
  am getting a 1024*768 screen resolution, but my monitor can render
  1366*768. it is unlikely to have got such a unexpected screen
  resolution like 1024*768. on the other hand ubuntu, fedora, kali
  and many more linux distros has never disappoint me such a way.
  how can I fix it ? kindly let me know the steps I will follow.
  
  thanks.
  
  m@n@sh..p@l


  

Re: How to fix screen resolution ( has been set to 1024 * 768 )

[Floris]

Op Mon, 09 Jan 2017 11:34:23 +0100 schreef manashpal  
<mpal2...@rediffmail.com>:


After installing Debian latest Jessie in my system, I am getting a  
1024*768 screen resolution, but my monitor can render >1366*768. it is  
unlikely to have got such a unexpected screen resolution like 1024*768.  
on the other hand ubuntu, fedora, >kali and many more linux distros has  
never disappoint me such a way. how can I fix it ? kindly let me know  
the steps I will >follow.


thanks.

m@n@sh..p@l


Is it possible to give us some more information? What is your system?
Can you post the output of:
lspci | grep VGA
and
xrandr

Floris

How to fix screen resolution ( has been set to 1024 * 768 )

[manashpal]

After installing Debian latest Jessie in my system, I am getting a 1024*768 
screen resolution, but my monitor can render 1366*768. it is unlikely to have 
got such a unexpected screen resolution like 1024*768. on the other hand 
ubuntu, fedora, kali and many more linux distros has never disappoint me such a 
way. how can I fix it ? kindly let me know the steps I will 
follow.thanks.m@n@sh..p@l

Re: Screen resolution in Jessie

[Dan Ritter]

On Wed, Apr 29, 2015 at 12:22:43PM -0700, Gary Roach wrote:
 On 04/29/2015 09:47 AM, Michael Biebl wrote:
 Am 29.04.2015 um 18:28 schrieb Gary Roach:
 I just upgraded to Jessie with no problems. I use a 24 16x9 monitor.
 With wheezy, there was a 1920 x 1080? mode that gave the correct aspect
 ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200
 mode. All of my circles are now elipses. Is there a solution to this
 problem. Is there a different driver out there. I'm using the on board
 video card  on my Intel DP55KG mother board. I am certain that I didn't
 have this problem with Wheezy.
 Does /var/log/Xorg.0.log contain any warnings or errors?
 I assume you use the intel driver? Is xserver-xorg-video-intel
 correctly installed?
 
 What does xrandr -q say?
 
 
 OK xrandr -v -q gives:
 
 xrandr program version   1.4.2
 xrandr: Failed to get size of gamma for output default
 Screen 0: minimum 640 x 480, current 1600 x 1200, maximum 1600 x 1200
 default connected 1600x1200+0+0 0mm x 0mm
1600x1200  0.00*
1280x1024  0.00
1280x960   0.00
1024x768   0.00
800x6000.00
640x4800.00
 
 No 1920 x ? shows up. I re-installed xserver-xorg-video-intel using
 Aptitude. Nothing changed.
 
 [27.140] (II) VESA(0): Total Memory: 256 64KB banks (16384kB)

You have two problems:

1. You are using the VESA driver instead of the intel driver.
Change this by creating /etc/X11/xorg.conf and specifying the
intel driver. Here's a skeleton:

Section ServerLayout
Identifier X.org Configured
Screen  0  Screen0 0 0
InputDeviceMouse0 CorePointer
InputDeviceKeyboard0 CoreKeyboard
EndSection

ection InputDevice
Identifier  Keyboard0
Driver  kbd
EndSection

Section InputDevice
Identifier  Mouse0
Driver  mouse
Option  Protocol auto
Option  Device /dev/input/mice
Option  ZAxisMapping 4 5 6 7
EndSection

Section Monitor
Identifier   Monitor0
VendorName   Monitor Vendor
ModelNameMonitor Model
EndSection

Section Device
Identifier  Card0
Driver  intel
EndSection

Section Screen
Identifier Screen0
Device Card0
MonitorMonitor0
SubSection Display
Viewport   0 0
Depth 24
EndSubSection
EndSection



2. (After you solve 1, this may go away) Your monitor's EDID
information is not being picked up or interpreted properly by
the card/driver. You should be able to override it with
something like this:

xrandr --output VGA1 --addmode 1920x1080
xrandr --output VGA1 --mode 1920x1080

-dsr-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150430124728.gc9...@randomstring.org

Re: Screen resolution in Jessie (Solved)

[Gary Roach]

On 04/30/2015 05:47 AM, Dan Ritter wrote:

On Wed, Apr 29, 2015 at 12:22:43PM -0700, Gary Roach wrote:

On 04/29/2015 09:47 AM, Michael Biebl wrote:

Am 29.04.2015 um 18:28 schrieb Gary Roach:

I just upgraded to Jessie with no problems. I use a 24 16x9 monitor.
With wheezy, there was a 1920 x 1080? mode that gave the correct aspect
ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200
mode. All of my circles are now elipses. Is there a solution to this
problem. Is there a different driver out there. I'm using the on board
video card  on my Intel DP55KG mother board. I am certain that I didn't
have this problem with Wheezy.

Does /var/log/Xorg.0.log contain any warnings or errors?
I assume you use the intel driver? Is xserver-xorg-video-intel
correctly installed?

What does xrandr -q say?



OK xrandr -v -q gives:

xrandr program version   1.4.2
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1600 x 1200, maximum 1600 x 1200
default connected 1600x1200+0+0 0mm x 0mm
1600x1200  0.00*
1280x1024  0.00
1280x960   0.00
1024x768   0.00
800x6000.00
640x4800.00

No 1920 x ? shows up. I re-installed xserver-xorg-video-intel using
Aptitude. Nothing changed.

[27.140] (II) VESA(0): Total Memory: 256 64KB banks (16384kB)

You have two problems:

1. You are using the VESA driver instead of the intel driver.
Change this by creating /etc/X11/xorg.conf and specifying the
intel driver. Here's a skeleton:

Section ServerLayout
Identifier X.org Configured
Screen  0  Screen0 0 0
InputDeviceMouse0 CorePointer
InputDeviceKeyboard0 CoreKeyboard
EndSection

ection InputDevice
Identifier  Keyboard0
Driver  kbd
EndSection

Section InputDevice
Identifier  Mouse0
Driver  mouse
Option  Protocol auto
Option  Device /dev/input/mice
Option  ZAxisMapping 4 5 6 7
EndSection

Section Monitor
Identifier   Monitor0
VendorName   Monitor Vendor
ModelNameMonitor Model
EndSection

Section Device
Identifier  Card0
Driver  intel
EndSection

Section Screen
Identifier Screen0
Device Card0
MonitorMonitor0
SubSection Display
Viewport   0 0
Depth 24
EndSubSection
EndSection



2. (After you solve 1, this may go away) Your monitor's EDID
information is not being picked up or interpreted properly by
the card/driver. You should be able to override it with
something like this:

xrandr --output VGA1 --addmode 1920x1080
xrandr --output VGA1 --mode 1920x1080

-dsr-


Thank you everyone for the help. Dan, you finally tipped me to the real 
problem. There was no xorg.conf file in my system. After further 
reading, I learned that X doesn't use a configuration file any longer 
but generates one on the fly by probing the hardware on boot up. A 
configuration file is only needed if something strange is required. So I 
rebooted  my system and watched the boot messages very carefully ( some 
way to capture these - the real early ones - would be nice). An error 
message showed up saying that a firmware package for radeon 5400 series 
chip set was missing. With more digging around I found that when l did 
an -  apt-get install firmware-linux-nonfree xserver-xorg-video-radeon - 
and reboot the system the correct driver loaded. No more problem.


My wifes computer is the same  but her 4:3 screen doesn't show the 
problem, I may fix it anyway.


I wouldn't be surprised if there a lot of users out there that have the 
same problem but haven't detected it.


Gary R.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5542c075.6080...@verizon.net

Re: Screen resolution in Jessie

[Michael Biebl]

Am 29.04.2015 um 18:28 schrieb Gary Roach:
 I just upgraded to Jessie with no problems. I use a 24 16x9 monitor.
 With wheezy, there was a 1920 x 1080? mode that gave the correct aspect
 ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200
 mode. All of my circles are now elipses. Is there a solution to this
 problem. Is there a different driver out there. I'm using the on board
 video card  on my Intel DP55KG mother board. I am certain that I didn't
 have this problem with Wheezy.

Does /var/log/Xorg.0.log contain any warnings or errors?
I assume you use the intel driver? Is xserver-xorg-video-intel
correctly installed?

What does xrandr -q say?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Screen resolution in Jessie

[Gary Roach]

I just upgraded to Jessie with no problems. I use a 24 16x9 monitor. 
With wheezy, there was a 1920 x 1080? mode that gave the correct aspect 
ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200 
mode. All of my circles are now elipses. Is there a solution to this 
problem. Is there a different driver out there. I'm using the on board 
video card  on my Intel DP55KG mother board. I am certain that I didn't 
have this problem with Wheezy.


Gary R.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/554106b6.10...@verizon.net

Re: Screen resolution in Jessie

[Frank Miles]

On Wed, 29 Apr 2015 18:30:03 +0200, Gary Roach wrote:

 I just upgraded to Jessie with no problems. I use a 24 16x9 monitor. 
 With wheezy, there was a 1920 x 1080? mode that gave the correct aspect 
 ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200 
 mode. All of my circles are now elipses. Is there a solution to this 
 problem. Is there a different driver out there. I'm using the on board 
 video card  on my Intel DP55KG mother board. I am certain that I didn't 
 have this problem with Wheezy.
 
 Gary R.

My 1920 x 1200 is working fine using the on-chip Intel video system and Jessie.
Never tried the x1080.

Can you alter the configuration using xrandr ?

HTH..


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mhr2dg$spg$1...@dont-email.me

Re: Screen resolution in Jessie

[Gary Roach]

On 04/29/2015 09:47 AM, Michael Biebl wrote:

Am 29.04.2015 um 18:28 schrieb Gary Roach:

I just upgraded to Jessie with no problems. I use a 24 16x9 monitor.
With wheezy, there was a 1920 x 1080? mode that gave the correct aspect
ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200
mode. All of my circles are now elipses. Is there a solution to this
problem. Is there a different driver out there. I'm using the on board
video card  on my Intel DP55KG mother board. I am certain that I didn't
have this problem with Wheezy.

Does /var/log/Xorg.0.log contain any warnings or errors?
I assume you use the intel driver? Is xserver-xorg-video-intel
correctly installed?

What does xrandr -q say?



OK xrandr -v -q gives:

xrandr program version   1.4.2
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1600 x 1200, maximum 1600 x 1200
default connected 1600x1200+0+0 0mm x 0mm
   1600x1200  0.00*
   1280x1024  0.00
   1280x960   0.00
   1024x768   0.00
   800x6000.00
   640x4800.00

No 1920 x ? shows up. I re-installed xserver-xorg-video-intel using 
Aptitude. Nothing changed.


There were no warnings or errors in the Xorg.0.log but I did find the 
following:

//(I noticed that it got the screen size right, 520, 320 mm)

[27.140] (II) VESA(0): Total Memory: 256 64KB banks (16384kB)
[27.140] (II) VESA(0): default monitor: Using hsync range of 
30.00-83.00 kHz
[27.140] (II) VESA(0): default monitor: Using vrefresh range of 
50.00-61.00 Hz
[27.140] (II) VESA(0): default monitor: Using maximum pixel clock 
of 175.00 MHz

[27.140] (WW) VESA(0): Unable to estimate virtual size
[27.140] (II) VESA(0): Not using built-in mode 1920x1440 (no mode 
of this name)
[27.140] (II) VESA(0): Not using built-in mode 1856x1392 (no mode 
of this name)
[27.140] (II) VESA(0): Not using built-in mode 1792x1344 (no mode 
of this name)
[27.140] (II) VESA(0): Not using built-in mode 1400x1050 (no mode 
of this name)
[27.141] (II) VESA(0): Not using built-in mode 1152x864 (no mode 
of this name)
[27.141] (II) VESA(0): Not using built-in mode 720x400 (no mode of 
this name)
[27.141] (II) VESA(0): Not using built-in mode 640x350 (no mode of 
this name)
[27.141] (II) VESA(0): Not using built-in mode 512x384 (no mode of 
this name)
[27.141] (II) VESA(0): Not using built-in mode 320x240 (no mode of 
this name)
[27.141] (II) VESA(0): Not using built-in mode 320x200 (no mode of 
this name)

[27.141] (--) VESA(0): Virtual size is 1600x1200 (pitch 1600)
[27.141] (**) VESA(0): *Built-in mode 1600x1200
[27.141] (**) VESA(0): *Built-in mode 1280x1024
[27.141] (**) VESA(0): *Built-in mode 1280x960
[27.141] (**) VESA(0): *Built-in mode 1024x768
[27.141] (**) VESA(0): *Built-in mode 800x600
[27.141] (**) VESA(0): *Built-in mode 640x480
*[27.141] (**) VESA(0): Display dimensions: (520, 320) mm*
[27.141] (**) VESA(0): DPI set to (78, 95)
[27.141] (**) VESA(0): Using Shadow Framebuffer
[27.141] (II) Loading sub module shadow
[27.141] (II) LoadModule: shadow
[27.141] (II) Loading /usr/lib/xorg/modules/libshadow.so
[27.247] (II) Module shadow: vendor=X.Org Foundation
[27.247]compiled for 1.16.4, module version = 1.1.0
[27.247]ABI class: X.Org ANSI C Emulation, version 0.4
[27.247] (II) Loading sub module fb
[27.247] (II) LoadModule: fb
[27.247] (II) Loading /usr/lib/xorg/modules/libfb.so
[27.324] (II) Module fb: vendor=X.Org Foundation
[27.324]compiled for 1.16.4, module version = 1.0.0
[27.324]ABI class: X.Org ANSI C Emulation, version 0.4
[27.324] (==) Depth 24 pixmap format is 32 bpp
[27.324] (II) Loading sub module int10
[27.324] (II) LoadModule: int10
[27.324] (II) Loading /usr/lib/xorg/modules/libint10.so
[27.324] (II) Module int10: vendor=X.Org Foundation
[27.324]compiled for 1.16.4, module version = 1.0.0
[27.324]ABI class: X.Org Video Driver, version 18.0
[27.324] (II) VESA(0): initializing int10
[27.324] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[27.324] (II) VESA(0): VESA BIOS detected
[27.324] (II) VESA(0): VESA VBE Version 3.0
[27.324] (II) VESA(0): VESA VBE Total Mem: 16384 kB
[27.324] (II) VESA(0): VESA VBE OEM: ATI ATOMBIOS
[27.324] (II) VESA(0): VESA VBE OEM Software Rev: 12.16
[27.324] (II) VESA(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI 
Technologies Inc.

[27.324] (II) VESA(0): VESA VBE OEM Product: CEDAR
[27.324] (II) VESA(0): VESA VBE OEM Product Rev: 01.00
[27.324] (II) VESA(0): virtual address = 0x7f66a9821000,
physical address = 0xe000, size = 16777216
[27.337] (II) VESA(0): Setting up VESA Mode 0x176 (1600x1200)
[27.337] (II) VESA(0): VBESetVBEMode failed, mode set without 
customized refresh.

[27.451] (==) VESA(0): Default visual is TrueColor
[27.516] (==) VESA(0): 

Re: Screen resolution in Jessie

[Michael Biebl]

Am 29.04.2015 um 21:22 schrieb Gary Roach:
 [27.621] (II) AIGLX: Screen 0 is not DRI2 capable
 [27.638] (EE) AIGLX: reverting to software rendering
 [29.297] (II) AIGLX: Loaded and initialized swrast
 [29.297] (II) GLX: Initialized DRISWRAST GL provider for screen 0

I don't see a message about the intel driver being loaded and used
successfully, only this error message.

Can you provide the full Xorg.0.log somewhere?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Re: XFCE4 screen resolution stuck too low

[Lars Noodén]

Thanks.

On 09/26/2014 01:19 AM, Chris Bannister wrote:


Maybe X isn't getting the correct resolution from the monitor. Check the
xorg log file and see if that helps.


The Xorg log file ( /var/log/Xorg.0.log ) shows no relevant errors and 
only a few items that seem to relate to the resolution.  e.g.


[   101.814] Mode: 143 (1400x1050)
...
[   101.814] Mode: 145 (1400x1050)
...
[   101.815] *Mode: 146 (1400x1050)
...

I do see one hopeful piece?

$ grep -i modeline /var/log/Xorg.0.log
[23.821] (II) VESA(0): Printing DDC gathered Modelines:
[23.821] (II) VESA(0): Modeline 1680x1050x0.0
119.00  1680 1728 1760 1840  1050 1053 1059 1080 -hsync
-vsync (64.7 kHz eP)



You may need to set a modeline config in an xorg.conf file.


The wiki ( https://wiki.debian.org/Xorg ) mentions to run

cd /etc/X11/
Xorg -configure

I've tried that with X turned off as well as from single-user mode and 
gotten only a core dump and a skeletal xorg.conf then appears in /root. 
 I suppose I add the modeline info to that.


Where would I find the official instructions about creating a proper 
modeline for the hardware I have?


#lspci |grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices,
Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series]


Have you googled this issue? i.e using monitor model linux resolution


Extensively over the last two days.

Regards,
/Lars



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5425a446.6040...@gmail.com

XFCE4 screen resolution stuck too low

[Lars Noodén]

In XFCE4, on Jessie, I am getting a display resolution of 1400x1050 
instead of 1680x1050.  If I go to the XFCE Menu - Settings - Display, 
it gives me only a single choice, that of 1400x1050, not higher or lower.


xrandr seems to be able to see the maximum resolution:

$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x 1050
default connected 1400x1050+0+0 0mm x 0mm
   1400x1050 60.00*
  1680x1050 (0x186) 146.250MHz
h: width  1680 start 1784 end 1960 total 2240 skew0 clock 
65.29KHz
v: height 1050 start 1053 end 1059 total 1089   clock 
59.95Hz



What should I be looking at to get this set in XFCE?

Regards,
/Lars


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54244c26.2040...@gmail.com

Re: XFCE4 screen resolution stuck too low

[Steve Litt]

On Thu, 25 Sep 2014 20:08:54 +0300
Lars Noodén lars.noo...@gmail.com wrote:

 In XFCE4, on Jessie, I am getting a display resolution of 1400x1050 
 instead of 1680x1050.  If I go to the XFCE Menu - Settings -
 Display, it gives me only a single choice, that of 1400x1050, not
 higher or lower.
 
 xrandr seems to be able to see the maximum resolution:
 
 $ xrandr
 xrandr: Failed to get size of gamma for output default
 Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x
 1050 default connected 1400x1050+0+0 0mm x 0mm
 1400x1050 60.00*
1680x1050 (0x186) 146.250MHz
  h: width  1680 start 1784 end 1960 total 2240 skew0
 clock 65.29KHz
  v: height 1050 start 1053 end 1059 total 1089
 clock 59.95Hz
 
 
 What should I be looking at to get this set in XFCE?
 
 Regards,
 /Lars

First, how confident are you that this is *only* in Xfce, and not in
LXDE and Openbox and who knows what other window managers? Perhaps it's
an X thing, plain and simple.

My computer does the opposite. It opens in too high a resolution, so
that the bottom of the screen is unseeable. So I created the following
command, called xraa, to switch from 1920x1200 to 1920x1080:

=
#!/bin/bash
sudo xrandr --output default --mode 1920x1080
=

In my Openbox, Shift+Ctrl+Semicolon brings up dmenu, I type xraa, and
bang, my resolution's right. Obviously, my visudo sets xrandr to run as
root for slitt, no password.

There's probably a right way to fix it, but I haven't found it yet,
so I just work around the problem.

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140925132854.410ff...@mydesq2.domain.cxm

Re: XFCE4 screen resolution stuck too low

[Lars Noodén]

On 09/25/2014 08:28 PM, Steve Litt wrote:

First, how confident are you that this is *only* in Xfce, and not in
LXDE and Openbox and who knows what other window managers? Perhaps it's
an X thing, plain and simple.


There are still some configuration options I have missed that are needed 
to try LXDE or Openbox.


However, I'm in FVWM just now and the resolution is only 1400x1050 here, 
too.


Regards,
/Lars


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5424558b.3030...@gmail.com

Re: XFCE4 screen resolution stuck too low

[Chris Bannister]

On Thu, Sep 25, 2014 at 08:48:59PM +0300, Lars Noodén wrote:
 On 09/25/2014 08:28 PM, Steve Litt wrote:
 First, how confident are you that this is *only* in Xfce, and not in
 LXDE and Openbox and who knows what other window managers? Perhaps it's
 an X thing, plain and simple.
 
 There are still some configuration options I have missed that are needed to
 try LXDE or Openbox.
 
 However, I'm in FVWM just now and the resolution is only 1400x1050 here,
 too.

Maybe X isn't getting the correct resolution from the monitor. Check the
xorg log file and see if that helps.

You may need to set a modeline config in an xorg.conf file. 

Have you googled this issue? i.e using monitor model linux resolution

-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140925221927.GH3395@tal

Re: XFCE4 screen resolution stuck too low

[Brian]

On Thu 25 Sep 2014 at 20:48:59 +0300, Lars Noodén wrote:

 On 09/25/2014 08:28 PM, Steve Litt wrote:
 First, how confident are you that this is *only* in Xfce, and not in
 LXDE and Openbox and who knows what other window managers? Perhaps it's
 an X thing, plain and simple.
 
 There are still some configuration options I have missed that are
 needed to try LXDE or Openbox.
 
 However, I'm in FVWM just now and the resolution is only 1400x1050
 here, too.

You have /var/log/Xorg.0.log to look at; it should tell you which
resolutions were detected. What card and driver are you using? Does
the monitor provide EDID information?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/25092014233347.e38702331...@desktop.copernicus.demon.co.uk

Screen resolution [was: Re: Building computer]

[Anthony Campbell]

On 02 Oct 2013, Stan Hoeppner wrote:

[snip] 
  No apology needed. You did in fact peg my age correctly; I will be 61 next
  month. And I too have known people who run less than the native resolution 
  to make the fonts bigger. When I get to that point, though, I will simply 
  increase 
  the font size so I don't get jaggies and blurry letters. Right now my eyes 
  need 
  the sharpness of the image, not a size increase. 
 
[snip] 

Increasing the size of the term font isn't a solution for the very tiny menu
fonts you get in some applications, e.g. imagemagick. For this reason,
at least on my desktop with a CRT monitor, I use 1280x1024 instead of
1600x1200. There is no obvious degradation of quality, at least to my
worsening eyes. On my laptop this doesn't work well because you get
distortion at any resolution other than the native.

AC

-- 
Anthony Campbell - a...@acampbell.org.uk 
http://www.acupuncturecourse.org.uk 
http://www.smashwords.com/profile.view/acampbell
https://itunes.apple.com/ca/artist/anthony-campbell/id73235412






-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131003074542.ga...@arcadia.home.gateway

RE: grub2 screen resolution

[Bonno Bloksma]

Hi,

 AHA, an undocumented feature. At least, it is not documented in the 
 /etc/default/grub file itself.

 You need to do:

info grub

 Bet you didn't know about that. :)

Well I knew about info but when I want to know about syntax I use mainly 
man, but there is no man page for grub.
Also the info pages start off with a lot off text before we get to the options 
in the /etc/default/grub file, that threw me of. ;-)

Bonno Bloksma


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/89d1798a7351d040b4e74e0a043c69d701094...@hglexch-01.tio.nl

Re: grub2 screen resolution

[Scott Ferguson]

On 06/04/12 16:17, Bonno Bloksma wrote:

snipped

 there is no man page for grub.

!?

grub-bin2h
grub-editenv
grub-emu
grub-install
grub-mkconfig
grub-mkdevicemap
grub-mkfont
grub-mkimage
grub-mkpasswd-pbkdf2
grub-mkrelpath
grub-mkrescue
grub-probe
grub-reboot
grub-script-check
grub-set-default
grub-setup
lb_binary_grub
lb_binary_grub2
update-grub
update-grub2

snipped


Kind regards

-- 
Iceweasel/Firefox/Chrome/Chromium/Iceape/IE extensions for finding
answers to questions about Debian:-
https://addons.mozilla.org/en-US/firefox/collections/Scott_Ferguson/debian/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f7e973e.1020...@gmail.com

RE: grub2 screen resolution

[Bonno Bloksma]

Hi,

 I do not understand the defaults build into Grub2. For instance the 
 default resolution, it is at 640x480. Which machine running Linux 
 cannot at least use 800x600? Or is Grub2 made with hendhelds as a 
 target environment as well?

 Yes - especially those squint-o-vision widescreen ratio netbooks.

Ok.

 Right now I have to add a line GRUB_GFXMODE=800x600 to the 
 /etc/default/grub file each time.

 Modify it then:-
 #update-grub

I know about update-grub, did not think I needed to mention that as it is 
needed for all changes to the grub settings.

 You might want to read /etc/default/grub first... (first line)
Like I wrote, I knew that. ;-)

Bonno Bloksma

RE: grub2 screen resolution

[Bonno Bloksma]

Hi Dom,

 Right now I have to add a line GRUB_GFXMODE=800x600 to the /etc/default/grub 
 file each time. That part I kan still understand, eventhough I think that 
 should be the default resolution.
 But I also have to change the /etc/grub.d/00_header script each time by 
 adding the line set gfxpayload=keep at the proper place.

 You should not need to change the 00_header script.

 Adding a line into /etc/default/grub, after the GRUB_GFXMODE entry with

 GRUB_GFXPAYLOAD_LINUX=keep
 
 should make grub keep the screen resolution.

AHA, an undocumented feature. At least, it is not documented in the 
/etc/default/grub file itself.

 You will need to run update-grub to regenerate and install the change 
 configuration of course.

I know abou that. ;-)

Bonno Bloksma


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/89d1798a7351d040b4e74e0a043c69d701092...@hglexch-01.tio.nl

Re: grub2 screen resolution

[Brian]

On Thu 05 Apr 2012 at 11:48:57 +, Bonno Bloksma wrote:

 AHA, an undocumented feature. At least, it is not documented in the
 /etc/default/grub file itself.

You need to do:

   info grub

Bet you didn't know about that. :)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120405132030.GC16316@desktop

grub2 screen resolution

[Bonno Bloksma]

Hi,

When I install a Squeeze machine, or when I update a Lenny machine to Squeeze, 
the first thing I do is to change the screen resolution so I can get some more 
tekst on the console when I need it. Of course most of the time I use ssh (or 
PuTTY) to go to a server and I can choose the screen size om my desktop but 
when there is a problem and I need to be at the console it is nice if there can 
be more then 80 chars on a line and 25 lines on a screen. :-(

I do not understand the defaults build into Grub2.
For instace the default resolution, it is at 640x480. Which machine running 
Linux cannot at least use 800x600? Or is Grub2 made with hendhelds as a target 
environment as well?

The second thing I don not understand it why Grub2 will not keep the screen 
resolution after the menu has gone. Why does it by default ALWAYS go back to 
640x480 even when the menu is shown at a higher resolution? I can understand 
there being a option NOT to keep the menu resolution if that may be nedded but 
by default it should keep the same resolution.

Right now I have to add a line GRUB_GFXMODE=800x600 to the /etc/default/grub 
file each time. That part I kan still understand, eventhough I think that 
should be the default resolution.
But I also have to change the /etc/grub.d/00_header script each time by adding 
the line set gfxpayload=keep at the proper place.

Is this a bug in the Grub2 system that will be resolved or does this need users 
to bug the Grub developers to change this? If the latter, how and where to I 
(and others) tell them that?

Bonno Bloksma


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/89d1798a7351d040b4e74e0a043c69d701090...@hglexch-01.tio.nl

Re: grub2 screen resolution

[Scott Ferguson]

On 04/04/12 20:37, Bonno Bloksma wrote:
 Hi,
 
 When I install a Squeeze machine, or when I update a Lenny machine
 to Squeeze, the first thing I do is to change the screen resolution
 so I can get some more tekst on the console when I need it. Of course
 most of the time I use ssh (or PuTTY) to go to a server and I can
 choose the screen size om my desktop but when there is a problem and
 I need to be at the console it is nice if there can be more then 80
 chars on a line and 25 lines on a screen. :-(
 
 I do not understand the defaults build into Grub2. For instace the 
 default resolution, it is at 640x480. Which machine running Linux 
 cannot at least use 800x600? Or is Grub2 made with hendhelds as a 
 target environment as well?

Yes - especially those squint-o-vision widescreen ratio netbooks.

 
 The second thing I don not understand it why Grub2 will not keep the 
 screen resolution after the menu has gone. Why does it by default 
 ALWAYS go back to 640x480 even when the menu is shown at a higher 
 resolution? I can understand there being a option NOT to keep the 
 menu resolution if that may be nedded but by default it should keep 
 the same resolution.
 
 Right now I have to add a line GRUB_GFXMODE=800x600 to the 
 /etc/default/grub file each time.

Modify it then:-
#update-grub

 That part I kan still understand, eventhough I think that should be
 the default resolution. But I also have to change the
 /etc/grub.d/00_header script each time by adding the line set
 gfxpayload=keep at the proper place.
 
 Is this a bug in the Grub2 system that will be resolved or does this 
 need users to bug the Grub developers to change this? If the 
 latter, how and where to I (and others) tell them that?

You might want to read /etc/default/grub first... (first line)

 
 Bonno Bloksma
 
 

Kind regards

-- 
Iceweasel/Firefox/Chrome/Chromium/Iceape/IE extensions for finding
answers to questions about Debian:-
https://addons.mozilla.org/en-US/firefox/collections/Scott_Ferguson/debian/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f7c2e7c.2040...@gmail.com

Re: grub2 screen resolution

[Dom]

On 04/04/12 11:37, Bonno Bloksma wrote:

Hi,

When I install a Squeeze machine, or when I update a Lenny machine to Squeeze, 
the first thing I do is to change the screen resolution so I can get some more 
tekst on the console when I need it. Of course most of the time I use ssh (or 
PuTTY) to go to a server and I can choose the screen size om my desktop but 
when there is a problem and I need to be at the console it is nice if there can 
be more then 80 chars on a line and 25 lines on a screen. :-(

I do not understand the defaults build into Grub2.
For instace the default resolution, it is at 640x480. Which machine running 
Linux cannot at least use 800x600? Or is Grub2 made with hendhelds as a target 
environment as well?


Some of my older, smaller laptops only display up to 800x480, for one 
example.



The second thing I don not understand it why Grub2 will not keep the screen 
resolution after the menu has gone. Why does it by default ALWAYS go back to 
640x480 even when the menu is shown at a higher resolution? I can understand 
there being a option NOT to keep the menu resolution if that may be nedded but 
by default it should keep the same resolution.

Right now I have to add a line GRUB_GFXMODE=800x600 to the /etc/default/grub 
file each time. That part I kan still understand, eventhough I think that 
should be the default resolution.
But I also have to change the /etc/grub.d/00_header script each time by adding 
the line set gfxpayload=keep at the proper place.


You should not need to change the 00_header script.

Adding a line into /etc/default/grub, after the GRUB_GFXMODE entry with

GRUB_GFXPAYLOAD_LINUX=keep

should make grub keep the screen resolution.

You will need to run update-grub to regenerate and install the change 
configuration of course.




Is this a bug in the Grub2 system that will be resolved or does this need users to 
bug the Grub developers to change this? If the latter, how and where to I 
(and others) tell them that?


It is not a bug.

--
Dom


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f7c3c18.4080...@rpdom.net

Re: grub2 screen resolution

[Jon Dowland]

On 04/04/12 11:37, Bonno Bloksma wrote:
 The second thing I don not understand it why Grub2 will not keep the 
 screen resolution after the menu has gone. Why does it by default 
 ALWAYS go back to 640x480 even when the menu is shown at a higher 
 resolution?

Grub is essentially an entirely distinct operating system from Linux.
Grub is loaded by the BIOS, it then loads the rest of itself,
and it hands over to Linux when it quits.

When you leave grub (by selecting a menu entry), control of the display
is handed over to the Linux kernel, which will default to a text-mode
display initially (in most cases).

Later in the boot sequence (in most cases) the DRM drivers are loaded
and kernel mode-setting kicks in, which alters the display to a higher
resolution.

If you want a more consistent display resolution, then grub would need
to instruct the linux kernel to initialise the video display to match
what it used.  This is (I think) not impossible: certainly, prior to
KMS, you could use a framebuffer console, and you could configure its
resolution on the kernel command line. However, I'm not sure how that
stuff interacts with the KMS stuff, so I'd advise not to bother.


-- 
Jon Dowland



signature.asc
Description: OpenPGP digital signature

Re: Screen resolution

[Andrei Popescu]

On Vi, 06 ian 12, 23:28:07, Brian wrote:
 
 I'll not bore you with why it happens but the EDID data are not passed to
 X on a couple of my machines, My xorg.conf is usually non-existent but
 in this case I have:
 
Section Monitor
Identifier   1905FP
Modeline 1280x1024  109.00  1280 1368 1496 1712  1024 1027 1034 1063 
 -hsync +vsync
HorizSync 30-81
VertRefresh   56-76
EndSection
 
Section Screen
IdentifierDefault Screen
Monitor   1905FP
DefaultDepth   16
SubSection Display
Depth  16
Modes 1280x1024
EndSubSection
EndSection
 
 Modeline is computed using 'cvt 1280 1024'.

Did you try without the Modeline? As far as I know X should be able to 
compute it based on HorizSync, VertRefresh and Modes.
Also, it might be interesting to pass DisplaySize so that DPI is 
correct.

Kind regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: Screen resolution

[Camaleón]

On Fri, 06 Jan 2012 18:37:01 +, Andrew Wood wrote:

 On 06/01/12 18:21, Camaleón wrote:
 Yup, you have to add the unexistant mode before you can use it :-)
 Steps are detailed at Adding undetected resolutions section.
 Greetings,
 
 OK, in an ideal world though shouldnt the board 'announce' that it
 supports that mode when probed?

Sure, Xorg has to handle this automatically. But of course something went 
wrong within your setup (monitor, VGA card, intel driver...) and it 
failed so you have to manually solve the issue. 

Afterwards, you can go to Debian BTS and report it to find out the 
culprit.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2012.01.07.10.40...@gmail.com

Re: Screen resolution

[Brian]

On Sat 07 Jan 2012 at 11:49:08 +0200, Andrei Popescu wrote:

 Did you try without the Modeline? As far as I know X should be able to 
 compute it based on HorizSync, VertRefresh and Modes.

X may indeed do this but, after commenting out Modeline, the best it
could offer was 1024x768.

 Also, it might be interesting to pass DisplaySize so that DPI is 
 correct.

Nothing doing here, either.

Thanks for the suggestions; they did as an incentive to review what I
did a couple of years ago but using a Modeline does appear to be my only
solution. No EDID information is available, by the way, because there is
an ancient KVM between the machines and the monitor.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120108011137.GD13969@desktop

Re: Screen resolution

[debian]

On Sun, 8 Jan 2012 01:11:37 +
Brian a...@cityscape.co.uk wrote:

 On Sat 07 Jan 2012 at 11:49:08 +0200, Andrei Popescu wrote:
 
  Did you try without the Modeline? As far as I know X should be able
  to compute it based on HorizSync, VertRefresh and Modes.
 
 X may indeed do this but, after commenting out Modeline, the best it
 could offer was 1024x768.
 
  Also, it might be interesting to pass DisplaySize so that DPI is 
  correct.
 
 Nothing doing here, either.
 
 Thanks for the suggestions; they did as an incentive to review what I
 did a couple of years ago but using a Modeline does appear to be my
 only solution. No EDID information is available, by the way, because
 there is an ancient KVM between the machines and the monitor.

Try without the ancient KVM?

I've been plagued with similar problems for years.  A couple of days
ago, in a uncharacteristic flash of clarity, I finally solved it by
switching to a shorter VGA cable.  Apparently the old cable (actually a
short cable and an extension) exceeded the allowable noise threshold.

Since switching... no more problems with monitor misconfiguration.

jeff


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120107200309.49315180@homerm12

Re: Screen resolution

[Andrei Popescu]

On Vi, 06 ian 12, 02:31:17, Andrew Wood wrote:
 Hi Kevin
 
 
 yes the xserver-xorg-video-intel package is installed. how do i
 check which driver is actually being used? one strange thing is that
 the kernel is printing out the following to the console, not sure
 what it means, could it be a fault with the controller board in the
 LCD?

I've had issues with EDID in the past when using too long monitor cable. 
Try using a short and known-good cable. If this doesn't work either you 
can try replacing/fixing the monitor (it helps if it is still under 
warranty) or just hardcode the monitor capabilities in xorg.conf (you 
will need some specs out of the user manual or the internet).

Hope this helps,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: Screen resolution

[Andrew Wood]

You can tell by looking in /var/log/Xorg.0.log.  If after looking at 
the log file, the problem isn't readily apparent, post the contents 
here, and someone should be able to figure out what's wrong.


-- Kevin



The pertinent contents of the log seem to be as follows. Im not sure how 
it works. It seems to probe the monitor to see what resolutions it 
supports. Should the controller board in the LCD therefore have a list 
of supported resolutions on it which it reports back to X?


Im using a controller board from LCDparts.net  They claim to have 
programmed it for this screen and that if it wasnt programmed correctly 
I wouldnt get any image at all and therefore its an OS problem but Im 
not convinced.


Thanks for all your help so far!

[   328.489] (==) No Layout section.  Using the first Screen section.
[   328.489] (==) No screen section available. Using defaults.
[   328.489] (**) |--Screen Default Screen Section (0)
[   328.489] (**) |   |--Monitor default monitor
[   328.491] (==) No monitor specified for screen Default Screen Section.
Using a default monitor configuration.
[   328.491] (==) Automatically adding devices
[   328.491] (==) Automatically enabling devices

[some lines cut out]


[   328.761] (II) LoadModule: fbdev
[   328.763] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[   328.815] (II) Module fbdev: vendor=X.Org Foundation
[   328.815] compiled for 1.11.0, module version = 0.4.2
[   328.815] ABI class: X.Org Video Driver, version 11.0
[   328.816] (II) intel: Driver for Intel Integrated Graphics Chipsets: 
i810,

i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server
[   328.824] (II) VESA: driver for VESA chipsets: vesa
[   328.824] (II) FBDEV: driver for framebuffer: fbdev
[   328.824] (++) using VT number 7

[   328.911] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[   328.912] (WW) Falling back to old probe method for vesa
[   328.912] (WW) Falling back to old probe method for fbdev
[   328.912] (II) Loading sub module fbdevhw
[   328.912] (II) LoadModule: fbdevhw
[   328.913] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[   329.158] (II) Module fbdevhw: vendor=X.Org Foundation
[   329.158] compiled for 1.11.2.902, module version = 0.0.2
[   329.158] ABI class: X.Org Video Driver, version 11.0
[   329.159] drmOpenDevice: node name is /dev/dri/card0
[   329.159] drmOpenDevice: open result is 9, (OK)
[   329.159] drmOpenByBusid: Searching for BusID pci::00:02.0
[   329.159] drmOpenDevice: node name is /dev/dri/card0
[   329.160] drmOpenDevice: open result is 9, (OK)
[   329.160] drmOpenByBusid: drmOpenMinor returns 9
[   329.160] drmOpenByBusid: drmGetBusid reports pci::00:02.0
[   329.160] (II) intel(0): Creating default Display subsection in 
Screen sectio

n
Default Screen Section for depth/fbbpp 24/32
[   329.160] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[   329.160] (==) intel(0): RGB weight 888
[   329.160] (==) intel(0): Default visual is TrueColor
[   329.161] (II) intel(0): Integrated Graphics Chipset: Intel(R) 945GME
[   329.161] (--) intel(0): Chipset: 945GME
[   329.161] (**) intel(0): Relaxed fencing disabled
[   329.161] (**) intel(0): Wait on SwapBuffers? enabled
[   329.161] (**) intel(0): Triple buffering? enabled
[   329.161] (**) intel(0): Framebuffer tiled
[   329.161] (**) intel(0): Pixmaps tiled
[   329.161] (**) intel(0): 3D buffers tiled
[   329.161] (**) intel(0): SwapBuffers wait enabled
[   329.162] (==) intel(0): video overlay key set to 0x101fe
[   329.230] (II) intel(0): Output VGA1 has no monitor section
[   329.247] (II) intel(0): Output DVI1 has no monitor section
[   329.610] (II) intel(0): Output TV1 has no monitor section
[   329.686] (II) intel(0): EDID for output VGA1
[   329.686] (II) intel(0): Printing probed modes for output VGA1
[   329.686] (II) intel(0): Modeline 1024x768x60.0   65.00  1024 1048 
1184 134

4  768 771 777 806 -hsync -vsync (48.4 kHz)
[   329.687] (II) intel(0): Modeline 800x600x60.3   40.00  800 840 968 
1056  6

00 601 605 628 +hsync +vsync (37.9 kHz)
[   329.687] (II) intel(0): Modeline 800x600x56.2   36.00  800 824 896 
1024  6

00 601 603 625 +hsync +vsync (35.2 kHz)
[   329.687] (II) intel(0): Modeline 848x480x60.0   33.75  848 864 976 
1088  4

80 486 494 517 +hsync +vsync (31.0 kHz)
[   329.687] (II) intel(0): Modeline 640x480x59.9   25.18  640 656 752 
800  48

0 489 492 525 -hsync -vsync (31.5 kHz)
[   

Re: Screen resolution

[Johann Klammer]

Andrew Wood wrote:

Hi Kevin


yes the xserver-xorg-video-intel package is installed. how do i check
which driver is actually being used? one strange thing is that the
kernel is printing out the following to the console, not sure what it
means, could it be a fault with the controller board in the LCD?

353.942420] i915 :00:02.0: VGA-1: EDID block 0 invalid.
[ 363.669312] Raw EDID:
[ 363.669327] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 363.669335] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 363.669343] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 363.669350] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 363.669357] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 363.669364] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 363.669371] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 363.669378] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 363.669392] i915 :00:02.0: VGA-1: EDID block 0 invalid.


On 06/01/12 00:59, Kevin Ross wrote:


EDID is the mechanism by which the display notifies the Gfx Card
of it's Capabilities(Resolution etc).
The message above may either be caused by your display not supplying 
this information, or it is querying the wrong output. VGA instead of 
DVI. In the latter case, it may not be significant at all.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f071a38.9060...@aon.at

Re: Screen resolution

[Camaleón]

On Thu, 05 Jan 2012 23:59:45 +, Andrew Wood wrote:

 Ive got an LCD screen whose native resolution is 1440x900 yet i can only
 get Wheezy to display 1024x768. No higher resolution is listed in System
 Settings. How do I enable a higher resolution please?

What's the output of xrandr?

You can try to manually add the desired resolution from there (using 
xrandr). Here is a good doc, although it can be a bit oudated, YMMV:

https://wiki.ubuntu.com/X/Config/Resolution#Adding_undetected_resolutions

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2012.01.06.16.59...@gmail.com

Re: Screen resolution

[Andrew Wood]

Thanks guys, xrandr gives:
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm

   1024x768   60.0*
   800x60060.3 56.2
   848x48060.0
   640x48059.9
DVI1 disconnected (normal left inverted right x axis y axis)
TV1 disconnected (normal left inverted right x axis y axis)


using the Ubuntu wiki instructions I then tried:

xrandr --output VGA1 --mode 1440x900

and got:

xrandr: cannot find mode 1440x900

On 06/01/12 16:59, Camaleón wrote:

On Thu, 05 Jan 2012 23:59:45 +, Andrew Wood wrote:


Ive got an LCD screen whose native resolution is 1440x900 yet i can only
get Wheezy to display 1024x768. No higher resolution is listed in System
Settings. How do I enable a higher resolution please?

What's the output of xrandr?

You can try to manually add the desired resolution from there (using
xrandr). Here is a good doc, although it can be a bit oudated, YMMV:

https://wiki.ubuntu.com/X/Config/Resolution#Adding_undetected_resolutions

Greetings,




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f07328d.2070...@me.com

Re: Screen resolution

[Camaleón]

On Fri, 06 Jan 2012 17:42:37 +, Andrew Wood wrote:

 On 06/01/12 16:59, Camaleón wrote:
 On Thu, 05 Jan 2012 23:59:45 +, Andrew Wood wrote:

 Ive got an LCD screen whose native resolution is 1440x900 yet i can
 only get Wheezy to display 1024x768. No higher resolution is listed in
 System Settings. How do I enable a higher resolution please?
 What's the output of xrandr?

 You can try to manually add the desired resolution from there (using
 xrandr). Here is a good doc, although it can be a bit oudated, YMMV:

 https://wiki.ubuntu.com/X/Config/Resolution#Adding_undetected_resolutions

 Thanks guys, xrandr gives:
 Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
 VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis)
 0mm x 0mm
 1024x768   60.0*
 800x60060.3 56.2
 848x48060.0
 640x48059.9
 DVI1 disconnected (normal left inverted right x axis y axis) TV1
 disconnected (normal left inverted right x axis y axis)
 
 
 using the Ubuntu wiki instructions I then tried:
 
 xrandr --output VGA1 --mode 1440x900
 
 and got:
 
 xrandr: cannot find mode 1440x900

Yup, you have to add the unexistant mode before you can use it :-)

Steps are detailed at Adding undetected resolutions section.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2012.01.06.18.21...@gmail.com

Re: Screen resolution

[Andrew Wood]

On 06/01/12 18:21, Camaleón wrote:
Yup, you have to add the unexistant mode before you can use it :-) 
Steps are detailed at Adding undetected resolutions section. Greetings, 


OK, in an ideal world though shouldnt the board 'announce' that it 
supports that mode when probed?



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f073f4d.8020...@me.com

Re: Screen resolution

[Jochen Spieker]

Andrew Wood:
 On 06/01/12 18:21, Camaleón wrote:
 Yup, you have to add the unexistant mode before you can use it :-)
 Steps are detailed at Adding undetected resolutions section.
 Greetings,
 
 OK, in an ideal world though shouldnt the board 'announce' that it
 supports that mode when probed?

Yes, that's what your broken EDID should do instead of delivering
zeroes.

J.
-- 
I start many things but I have yet to finish a single one.
[Agree]   [Disagree]
 http://www.slowlydownward.com/NODATA/data_enter2.html


signature.asc
Description: Digital signature

Re: Screen resolution

[Brian]

On Fri 06 Jan 2012 at 18:37:01 +, Andrew Wood wrote:

 OK, in an ideal world though shouldnt the board 'announce' that it  
 supports that mode when probed?

I think X can only work with what it is given. If the monitor fails for
some reason to impart information X's idea of what is possible is bound
to be incomplete. xrandr will display what it thinks it can do based on
what it knows, so, as has been pointed out, if it is lacking in knowledge
of what is possible you will have to tell it.

I'll not bore you with why it happens but the EDID data are not passed to
X on a couple of my machines, My xorg.conf is usually non-existent but
in this case I have:

   Section Monitor
   Identifier   1905FP
   Modeline 1280x1024  109.00  1280 1368 1496 1712  1024 1027 1034 1063 
-hsync +vsync
   HorizSync 30-81
   VertRefresh   56-76
   EndSection

   Section Screen
   IdentifierDefault Screen
   Monitor   1905FP
   DefaultDepth   16
   SubSection Display
   Depth  16
   Modes 1280x1024
   EndSubSection
   EndSection

Modeline is computed using 'cvt 1280 1024'.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120106232806.GB13969@desktop

Screen resolution

[Andrew Wood]

Ive got an LCD screen whose native resolution is 1440x900 yet i can only 
get Wheezy to display 1024x768. No higher resolution is listed in System 
Settings. How do I enable a higher resolution please?



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f063971.2020...@me.com

Re: Screen resolution

[Bob Proulx]

Andrew Wood wrote:
 Ive got an LCD screen whose native resolution is 1440x900 yet i can
 only get Wheezy to display 1024x768. No higher resolution is listed
 in System Settings. How do I enable a higher resolution please?

This is probably an issue of your graphics card rather than the
display itself.  Please furnish information about what graphics card
is in your system.  You can use the output of the lspci command to
find this.

On my system, for example:

  $ lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03)

Bob


signature.asc
Description: Digital signature

Re: Screen resolution

[Andrew Wood]

Sorry. should also have added the graphics chipset is an intel gma 950 
integrated onto an atom itx motherboard.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f063da3.6010...@me.com

Re: Screen resolution

[Andrew Wood]

Hi Bob

lspci gives:

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME 
Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller (rev 03)




On 06/01/12 00:23, Bob Proulx wrote:

Andrew Wood wrote:

Ive got an LCD screen whose native resolution is 1440x900 yet i can
only get Wheezy to display 1024x768. No higher resolution is listed
in System Settings. How do I enable a higher resolution please?

This is probably an issue of your graphics card rather than the
display itself.  Please furnish information about what graphics card
is in your system.  You can use the output of the lspci command to
find this.

On my system, for example:

   $ lspci | grep VGA
   00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03)

Bob



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f0640ad.8020...@me.com

Re: Screen resolution

[Andrew Wood]

Hi Bob

lspci gives:

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME 
Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller (rev 03)




On 06/01/12 00:23, Bob Proulx wrote:

Andrew Wood wrote:

Ive got an LCD screen whose native resolution is 1440x900 yet i can
only get Wheezy to display 1024x768. No higher resolution is listed
in System Settings. How do I enable a higher resolution please?

This is probably an issue of your graphics card rather than the
display itself.  Please furnish information about what graphics card
is in your system.  You can use the output of the lspci command to
find this.

On my system, for example:

   $ lspci | grep VGA
   00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03)

Bob



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f0640d5.6040...@me.com

Re: Screen resolution

[Andrew Wood]

Hi Bob

lspci gives:

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME 
Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller (rev 03)




On 06/01/12 00:23, Bob Proulx wrote:

Andrew Wood wrote:

Ive got an LCD screen whose native resolution is 1440x900 yet i can
only get Wheezy to display 1024x768. No higher resolution is listed
in System Settings. How do I enable a higher resolution please?

This is probably an issue of your graphics card rather than the
display itself.  Please furnish information about what graphics card
is in your system.  You can use the output of the lspci command to
find this.

On my system, for example:

   $ lspci | grep VGA
   00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03)

Bob



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f06410c.4080...@me.com

Re: Screen resolution

[Andrew Wood]

Hi Bob

lspci gives:

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME 
Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller (rev 03)




On 06/01/12 00:23, Bob Proulx wrote:

Andrew Wood wrote:

Ive got an LCD screen whose native resolution is 1440x900 yet i can
only get Wheezy to display 1024x768. No higher resolution is listed
in System Settings. How do I enable a higher resolution please?

This is probably an issue of your graphics card rather than the
display itself.  Please furnish information about what graphics card
is in your system.  You can use the output of the lspci command to
find this.

On my system, for example:

   $ lspci | grep VGA
   00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03)

Bob



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f064176.4070...@me.com

Re: Screen resolution

[Kevin Ross]

On 01/05/2012 04:30 PM, Andrew Wood wrote:

Hi Bob

lspci gives:

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME 
Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller (rev 03)





I also have an Intel 945GM graphics chip in my laptop.  Works fine for 
me on Wheezy.  Sounds like you're running the VESA (generic) graphics 
driver instead of the Intel one.  Do you have xserver-xorg-video-intel 
installed?  Also, if you have an /etc/X11/xorg.conf file, rename it to 
something else, and try restarting X.


Hope this helps!
-- Kevin


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f06478c.1060...@familyross.net

Re: Screen resolution

[Andrew Wood]

Hi Kevin


yes the xserver-xorg-video-intel package is installed. how do i check 
which driver is actually being used? one strange thing is that the 
kernel is printing out the following to the console, not sure what it 
means, could it be a fault with the controller board in the LCD?


 353.942420] i915 :00:02.0: VGA-1: EDID block 0 invalid.
[  363.669312] Raw EDID:
[  363.669327]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669335]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669343]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669350]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669357]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669364]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669371]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669378]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669392] i915 :00:02.0: VGA-1: EDID block 0 invalid.


On 06/01/12 00:59, Kevin Ross wrote:


I also have an Intel 945GM graphics chip in my laptop.  Works fine for 
me on Wheezy.  Sounds like you're running the VESA (generic) graphics 
driver instead of the Intel one.  Do you have xserver-xorg-video-intel 
installed?  Also, if you have an /etc/X11/xorg.conf file, rename it to 
something else, and try restarting X.


Hope this helps!
-- Kevin





--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f065cf5.3020...@me.com

Re: Screen resolution

[Kevin Ross]

On 01/05/2012 06:31 PM, Andrew Wood wrote:

Hi Kevin


yes the xserver-xorg-video-intel package is installed. how do i check 
which driver is actually being used? one strange thing is that the 
kernel is printing out the following to the console, not sure what it 
means, could it be a fault with the controller board in the LCD?


 353.942420] i915 :00:02.0: VGA-1: EDID block 0 invalid.
[  363.669312] Raw EDID:
[  363.669327]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669335]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669343]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669350]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669357]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669364]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669371]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669378]  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  363.669392] i915 :00:02.0: VGA-1: EDID block 0 invalid.



You can tell by looking in /var/log/Xorg.0.log.  If after looking at the 
log file, the problem isn't readily apparent, post the contents here, 
and someone should be able to figure out what's wrong.


-- Kevin



On 06/01/12 00:59, Kevin Ross wrote:


I also have an Intel 945GM graphics chip in my laptop.  Works fine 
for me on Wheezy.  Sounds like you're running the VESA (generic) 
graphics driver instead of the Intel one.  Do you have 
xserver-xorg-video-intel installed?  Also, if you have an 
/etc/X11/xorg.conf file, rename it to something else, and try 
restarting X.


Hope this helps!
-- Kevin








--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f066c47.7070...@familyross.net