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 <mrma...@earthlink.net> 
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) <kleen...@ucmail.uc.edu>
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 <mrma...@earthlink.net> 
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 <b...@busby.net> 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 <maniku...@gmail.com>
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


Reply via email to