Re: loss of screen resolution, part 2

2022-12-23 Thread 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

2022-12-23 Thread 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

2022-12-22 Thread 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

2022-12-21 Thread 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

2022-12-21 Thread 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

2022-12-20 Thread 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

2022-12-20 Thread 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

2022-12-20 Thread 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

2022-12-19 Thread 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

2022-12-19 Thread 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

2022-12-19 Thread 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

2022-12-07 Thread 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

2022-12-04 Thread 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

2022-12-04 Thread 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 curren

Re: loss of screen resolution

2022-12-03 Thread 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

2022-12-03 Thread 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

2022-12-03 Thread 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%2F&data=05%7C01%7Ckleenesj%40ucmail.uc.edu%7Cfb8f5bce786f42dc921308dad55c42f3%7Cf5222e6c5fc648eb8f0373db18203b63%7C1%7C0%7C638056889486652349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cEu7XkZUJn3VOTiLcdvcVEvidGKsA8RLvXd1kUf7oR8%3D&reserved=0

This and 
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpaste.debian.net%2F1262700%2F&data=05%7C01%7Ckleenesj%40ucmail.uc.edu%7Cfb8f5bce786f42dc921308dad55c42f3%7Cf5222e6c5fc648eb8f0373db18203b63%7C1%7C0%7C638056889486652349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=6zqt%2FcKItF3u%2BCd7nzEQOizl9DeiksEDaNBS6BHpUb0%3D&reserved=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

2022-12-03 Thread 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

2022-12-03 Thread 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%2F&data=05%7C01%7Ckleenesj%40ucmail.uc.edu%7Ccfc9a461f864488b9b7108dad4f5c190%7Cf5222e6c5fc648eb8f0373db18203b63%7C1%7C0%7C638056449240692027%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pQ9QP%2BuDQ2%2BjbzxZB815Oo2YL8z022xO%2BTjkzHaH1%2BE%3D&reserved=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

2022-12-02 Thread 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

2022-12-02 Thread 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-install&data=05%7C01%7Ckleenesj%40ucmail.uc.edu%7C0b895e40ae1845abc85b08dad477c4ea%7Cf5222e6c5fc648eb8f0373db18203b63%7C1%7C0%7C638055908118333462%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Od8tsIGlAhdF8HQbnDo2shuCpiPVRwr8jqATtd6vhhI%3D&reserved=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

2022-12-02 Thread 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

2022-12-02 Thread 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

2022-12-02 Thread 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

2022-12-02 Thread 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.