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/
⠈⠳⣄⠀⠀