From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-204144-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits))
(No client certificate requested)
by finch.gentoo.org (Postfix) with ESMTPS id 7C7DB1581C1
for <garchives@archives.gentoo.org>; Sun, 7 Jul 2024 00:32:59 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 0E14E2BC0AF;
Sun, 7 Jul 2024 00:32:54 +0000 (UTC)
Received: from mail-oa1-x2f.google.com (mail-oa1-x2f.google.com [IPv6:2001:4860:4864:20::2f])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 5ABB1E2B48
for <gentoo-user@lists.gentoo.org>; Sun, 7 Jul 2024 00:32:53 +0000 (UTC)
Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-25e0663de76so1332960fac.1
for <gentoo-user@lists.gentoo.org>; Sat, 06 Jul 2024 17:32:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20230601; t=1720312372; x=1720917172; darn=lists.gentoo.org;
h=content-transfer-encoding:in-reply-to:mime-version:user-agent:date
:message-id:autocrypt:from:references:to:subject:from:to:cc:subject
:date:message-id:reply-to;
bh=MQQBgPZXfNPeF+Llk0dRYlbnyhbzKe4dCQBCO2xmEG0=;
b=Xeu98wirgMhuMAG7QhJKqZSmec1hchwQTw2Sdq3dklTegsD8VwX20cI8D2HJAX5hbQ
fPOiUntW4ckCuI9GGeg9aVW8fHI2bvwaEvWsR9t/emYFciPdIV0orWGoUr7IdNQMUPk7
AnQxbvdrA7rFcRjFZKXgr5wqabenYeLODYIH/JBDPuYBos7PrPPxedpFwQCLsbmUNaJ3
IRXb2h3ZjpNhFKmicV8KHq1kdj8yg0HJiIlTgmfZ0m2/KHpENguqBhDXj8XYVFmvguAV
nANolhqH4QoYtHyN7mU255kcPhrMVZX6TKuHR5/TTIpxBcQbjS8HvxRp/l7GLAuIy9l3
T/xg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1720312372; x=1720917172;
h=content-transfer-encoding:in-reply-to:mime-version:user-agent:date
:message-id:autocrypt:from:references:to:subject:x-gm-message-state
:from:to:cc:subject:date:message-id:reply-to;
bh=MQQBgPZXfNPeF+Llk0dRYlbnyhbzKe4dCQBCO2xmEG0=;
b=ZNyVZMgfyfCLWvp95cRokqaTeTobZT8O3EodInoA+8DtU3r5lDNEOimA544F072I7E
oIVBgXF2KQkaOCGUY8D5PoStXlZqMtma0KGAxrQGMta435jlm5FOLRu+As2KUFl1QmTN
PPaqzE/iQOyQ1yNCQprIY9KUxazUAyfBYRv1Cqzlb2abYTPpGRWYnfRXyVhmvgkr32Ol
uCY/vmN31KAFRzJFZJUSU5Ch1fN7RbzZrrnoWG+w8OHPoODPCRFH3c7+d6qwO+6jlKB5
wCQjZC1tWKdkKvD36goqdd/aqlbh6219pnxpF1ikDWaJDBg5Hw3N6JqfGF0oIsias9CS
c5bA==
X-Gm-Message-State: AOJu0YzeqOywnbMCJ/ubWKhmNrfnTTk93ptVLP5t/L1BTnvvtkbYdbrA
9Bivx8XKBJJpPrv0xpttJAruPSCYdKlisSrPqFgAQw2NA/3ZV9kL
X-Google-Smtp-Source: AGHT+IEN18O/4HKs/T2f2zo9DeKpmx8nogxa6gdTmlI514phIRnOjm6YHJe9ZUdVBlr5UyJ3aUHv6w==
X-Received: by 2002:a05:6871:5214:b0:25e:14f0:62c2 with SMTP id 586e51a60fabf-25e2b8d97c1mr7374348fac.3.1720312372019;
Sat, 06 Jul 2024 17:32:52 -0700 (PDT)
Received: from [10.8.8.22] ([107.179.20.206])
by smtp.gmail.com with ESMTPSA id 586e51a60fabf-25dff4c6b61sm2395021fac.25.2024.07.06.17.32.51
(version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
Sat, 06 Jul 2024 17:32:51 -0700 (PDT)
Subject: Re: [gentoo-user] New monitor, new problem. Everything LARGE O_O
To: gentoo-user@lists.gentoo.org
References: <34ea5003-9d26-f379-35b9-aa638942d2ad@gmail.com>
<2816357.BEx9A2HvPv@rogueboard>
<f336bb35-67ae-d9ac-bad3-edc86f85caf5@gmail.com>
<1973786.PYKUYFuaPT@rogueboard>
From: Dale <rdalek1967@gmail.com>
Autocrypt: addr=rdalek1967@gmail.com; prefer-encrypt=mutual; keydata=
mQINBGFSciYBEADcEGMyJBSuavKO/XKUVvgkxck7Nl8Iuu8N2lcnRji/rSKg5c1Acix1ll9i
oW8JBCHwvn0+Xy60BvEsqcup3YSHw5STl/bR1ePEehtnYrg8FdjdS91+B805RfnKMm69rFVI
wLSBHQrSG1yxHd8CloWoEdhmVtP24buajbh114bgXd9ahtpZrCVMrWdWYUg2mEXguGV5uNAh
Rf8SWxDNc79w24JxsV34a8niMUYMjzWr0rafIbzk732X38vGjVMLo/2mMpkbp9mPp++LHoY+
0Pet8zxxdXPJSCd475kza1AD+hhSyBZXB9yknYWgyY3cZe1rGmooJSi2KX4QxO7npwLThcO1
be6KKRkd35+Fi/a1BzVOHsZMiK/gcwxEFoMd27gir4ehaeHJfFXl+65w4hj0EsOZSxrJrm2C
R50g5By2czSKP1bADEygFNpIJj51AR+wM88NImG2RPtlT2maYBzazvF05g65cdHXGp1C7W5P
wwwKU2DgABB2t7N7z5A69LnryBRw4zUYDRRYLTYlBlYgg+xILm2c0OrBdxJgLJa7JE50Eo25
d3PFwt9J0gYvqy6sPFLl9So0sDg9zm0hKQtXOP5kgropUFGrNoJI+mjwF4rYLRBVzZwNAvlO
OhEvHubBo3mEllv4x+FeptwXZxlk7gUsdqI8AxnFB8K9wi6FVQARAQABtBtEYWxlIDxyZGFs
ZWsxOTY3QGdtYWlsLmNvbT6JAk4EEwEIADgCGyMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AW
IQQSG1h01ruv/WNXc3Q3RqOgiQH1GwUCYVJy8gAKCRA3RqOgiQH1G+waEACeTZCt77jnRAmQ
AV7otKuZekDWiLi3Eig8tj5ZJiCNSYA/hIxzmexRP0GMqjitcXK1iGwWcvMzzvIq30GAjIfB
4BR38cnXbtBa6fNewiT7QaZe/Hn6yBRldXNQypzbHy+/o27bUEy+oX4rE7etUgEHQAjuw7xz
XFWg4tH1/KJvsOVY5upnWc5LdxYhsuQ3dQD4b22GsK0pOBDfb9PiirYM8eGKvrVuq4E/c75z
lDDFhINl18lNZ9D0ZFL3IkTjHsAAqFH9uhnnEB8CWdHbBewPEfRaOhBUYWZ3Q8uTkmDgZT8q
D9jlvLEdw7Nh2ApdxoepnI/4D+ql2Gr4DtH7SEPydr5gcf1Qr/2bXRb1hAYnIVcbncs/Bm3Z
bkRKPVWMfE3Fusa+p5hMzixk0YysMaTHlc7mYRYAEZGnPMXnmcCbetwARU7A0yz1M1kCMOAQ
Lsz8KH5kv3cRenMB6SFfjND2JfAK61H5TtnPq3L8noS2ZykRYxq9Nm3X64O1tJojIKBoZFr8
AwYNCvqC6puUyGMuzHPh7jPof8glfrrEKIYUvNPGMDoVX3IGetxh/9l6NcxgFA4JGoR+LS3C
zmeNrwlllAe3OEUfKoWVQ+pagpSdM+8hHolaSda4Ys66Z3fCR4ZvcTqfhTAVskpqdXa4isAk
7vTcXu3L499ttywEp7rJTbkCDQRhUnImARAAncUdVhmtRr59zqpTUppKroQYlzR0jv8oa7DG
K4gakTAT2N7evnI9wpssmzyVk8VEiLzhnFQ/Ol3FRt6hZCXDJt0clyHOyTfvz/MNFttWuZTc
mLpSvmRR6VRjAH+Tz3Eam2xUw3PGuH97BcXQ3NnX3msv1UDxtxxBu6e2YrdeOhrCUSgzokcJ
98ChUNy934cgepPybAI12lSWqVFQ1aG7jExZfiUk+333fPSDbpKoZbTW5YJLXbycmW/C1IWL
qYQyNjRWKaGoJtUWFhhmNiOQct7n90aKivNVPavmN+UQ9LlMaINtf9T6XCzLfogCFsulDCDJ
0yNQLDTurHaB4E71xoctgXmLLq9z1RQ0W2XiVAAOZQj6K3+d0AOUjDhCQ2QW8dUSq0ckkZXV
DKVJOGS8Nhf2eIWIqRnP3AcUiiaiFGqUaVUmUAZ6h/oJmgghEu/1S+pcuUKU5i69+XCZ3hH2
Jzwzbf7K+FAIkOhCfHncF8i1N1pk00pOVykNnqHTfFo3qFusHt0ZWgXVnnn4pYdXqZNoDhvF
BRE5Vm4k/k96Pw8HRx6Os6eFSRrlqGzRgqsu86FekxusXB9UGv4lJhtU/J+8MRWsh22K718s
DbQnABicGKFz1qQlWvcf59oTByhLINJCBt1WXl+TzJDXepr3QSkqmK41dO9Hob97C9dMiK8A
EQEAAYkCNgQYAQgAIAIbDBYhBBIbWHTWu6/9Y1dzdDdGo6CJAfUbBQJhUnLyAAoJEDdGo6CJ
AfUbVHIQAKSWw620vPhR3A/njU2z77F3z/Jk+HTKdE3fIyWSWdkYN7CBFL0NguOMP30WZ+qE
sJhZu7T5hf251MwQUUt27xlfnKYOmQs7CqONlXuXlGZI6WufrUjxNcVz+5gJsqvUWuuJWsgg
sDmE92IBnfG/f81fPHWQyfr/SF4wYDMyoFp5xCCQpp1zB63iuFvvrhxBkEHzmbRtVDOhl0Xp
BVEDR1w3QRACw9QJD/KM05Czv9JNQYlwinWO/OaQ9cMlUpKLgswUPg9IZ5vucxScfuAUA5uC
B1jlAQ8ZPlVukBmbEv5RGOv+lpuEbA3YDMVtEeH4YMFbjt/+vH3Cr2vTbp5JlpByLburJEH0
WXZLUawEfUsZvVwpOuJK75vaa2HYXee+Cb3iCIzwfIfctdlqzUcbGRczlRNM59hpvj4z29Gh
3kAxVHItAYq54ikxQ9l4hQ8s9sLYPbX/WtcBxNX8crBSw0FLnmzGleVEtBHyqtt5CLzQNgrj
GYWl1vKDUmRPw1CdZ1c+fMN9CY11jOM5B5ZnqZWfDeVYO2iJ5SuvTycChexCb8WYn1bdCBIo
bBtga2RBXbVt4Mh9E4owsszefn51MwfjXxB20Fc5k3GU1AVpTCMs3ayYCzo0b2pvEvdjtDcA
CYLEFPWgaFX9iQAM/CDfKvTtvgGWpqtCL2raq/mQoJEU
Message-ID: <bd9654db-9050-bdc7-447c-3e0c2e2ba6ca@gmail.com>
Date: Sat, 6 Jul 2024 19:32:49 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Firefox/91.0 SeaMonkey/2.53.18.2
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
In-Reply-To: <1973786.PYKUYFuaPT@rogueboard>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Archives-Salt: 793e0249-af98-449d-b983-b3db82660be4
X-Archives-Hash: aed124cd1941f5a377dfcb46b3fd7be4
Michael wrote:
> On Saturday, 6 July 2024 17:11:23 BST Dale wrote:
>> Michael wrote:
>>> On Saturday, 6 July 2024 10:59:30 BST Dale wrote:
>>>> Mark Knecht wrote:
>>>>> On Tue, Jul 2, 2024 at 12:44 PM Dale <rdalek1967@gmail.com
>>>>> <mailto:rdalek1967@gmail.com>> wrote:
>>>>> <SNIP>
>>>>>
>>>>>> I tried it with those options and without. Neither changed anything.
>>>>>> I
>>>>>> originally tried it with no xorg.conf at all. I was hoping maybe the
>>>>>> Nvidia GUI thing would adjust things. I may try that again. No
>>>>>> xorg.conf and use the GUI thing. That's what I use to set up my TV and
>>>>>> such anyway. Thing is, the sddm screen is HUGE too.
>>>>> <SNIP>
>>>>>
>>>>>> :-) :-)
>>>>> ???
>>>>>
>>>>> xdpyinfo | grep -B2 resolution
>>>>>
>>>>> ???
>>>> I booted my new rig up again. Dang that thing. It was HUGE again. I
>>>> started reading stuff, mainly about xorg.conf and the available
>>>> settings. I changed all sorts of stuff, including some things Micheal
>>>> suggested. I restarted DM each time. I was about ready to toss it in
>>>> the old minnow pond, that's where everything goes to die here. Lots of
>>>> CRT monitors in there. LOL Anyway, I had to install that package to
>>>> run that command. It spit out a oops when I tried to run it after a
>>>> copy and paste. I also installed it on my main rig, just to compare.
>>>> On the new rig, the DPI was a fairly large number. I thought I had the
>>>> output saved but it seems to be gone. My main rig tho showed 80x80 dots
>>>> per inch. I did a duck search, finally found how to set that. I then
>>>> restarted DM and YEPPIE!!! It was a normal size again.
>>>>
>>>> Now the monitor on my main rig is a bit older too. Maybe 6 or 7
>>>> years??? Should newer monitors be set to a higher number for DPI? Is
>>>> that normal? Why was it using such a high number by default? I want to
>>>> say one was like 200 or something. It was quite large. The reason I'm
>>>> asking, I may need to set something else to make the screen the right
>>>> size but let it use that larger dpi number, if that is what the newer
>>>> monitor prefers to use.
>>>>
>>>> Now to reboot, see if I have thoughts of that minnow pond again. :/
>>>>
>>>> Dale
>>>>
>>>> :-) :-)
>>> I'm struggling to follow your post because you do not provide specific
>>> information on the commands you input, the output you get in your terminal
>>> and the observed changes in the monitor.
>>>
>>> You also don't provide info on the changes you made in your xorg.conf, or
>>> xrandr and the corresponding changes observed each time in your
>>> Xorg.0.log.
>>>
>>> Strictly speaking, the pixel density of an on-screen digital image is
>>> referred to as Pixels Per Inch (PPI), but the term DPI which refers to a
>>> printed image of ink Dots Per Inch has stuck.
>>>
>>> In addition, there is the physical pixel density of your monitor and the
>>> rendered pixel density of the X11 image(s). Tweaking the latter allows
>>> you to scale the display and make images look larger than the native
>>> monitor resolution.
>>>
>>> You can set the DPI in your xorg.conf, or you can set it with xranrd, or
>>> you can set it on the CLI when you launch X, but usually this is not
>>> necessary and could mess up the scaling of your fonts, window decorations
>>> and symbols too (the font DPI is set differently by setting Xft.dpi: in
>>> ~/.Xresources, of the window manager's/DE font settings).
>>>
>>> A good starting point is to get the manual of your monitor and look at its
>>> published native resolution, e.g. 1920x1080 and the physical monitor size
>>> over which this resolution is displayed. Let's assume this 1920x1080
>>> native resolution belongs to a 23" monitor. A 23" diagonal would
>>> correspond to a 20" wide screen real estate. Consequently the horizontal
>>> PPI would be:
>>>
>>> PPI = 1920 pixels / 20" = 96
>>>
>>> The same resolution on a 24" wide monitor would give a PPI of:
>>>
>>> PPI = 1920 pixels / 24" = 80
>>>
>>> Obviously a physically wider 24" monitor with the same native screen
>>> resolution as a smaller 20" monitor will not look as sharp when viewed
>>> from
>>> the *same* distance.
>>>
>>> Similarly, changing the selected resolution on the same 23" monitor from
>>> say 1920 pixels wide to a lower resolution of 1280 pixels gives a PPI of
>>> 64.
>>>
>>> I leave the calculation of the vertical PPI to the reader.
>>>
>>> Usually I start with no xorg.conf and leave the card to detect what the
>>> monitor prefers, then use the Scale setting in the desktop settings to
>>> increase/decrease (zoom in/zoom out) the displayed scale. This has the
>>> effect of altering the PPI to higher or lower values to improve
>>> readability of content. The above should help you arrive at some
>>> practical resolution, but I would start with the native resolution of the
>>> monitor and work down from there if you find it difficult to read its
>>> display.
>>>
>>> NOTE: Using Qt scaling can mess up window decorations, widgets, etc. I've
>>> found it doesn't work well with some KDE applications and their menus/
>>> submenus, or pop up windows. You need to set PLASMA_USE_QT_SCALING=1 to
>>> make it follow Qt scaling and there's GTK3 too which may need tuning.
>>> This is the reason I calculate PPI before I venture into buying a new
>>> monitor, unless I can see it in person to make sure I can still read its
>>> content. ;-)
>> The reason I picked Mark's post is that I used the command he gave to
>> find out the DPI info was different from my main rig. When I first
>> booted up and started DM, I got that HUGE screen again. It worked last
>> time. I hadn't changed anything. I sometimes wonder still if it reads
>> xorg.conf each time. Anyway, when it didn't work, I started reading up
>> a bit. I tried several things including checking options you posted but
>> nothing worked. It stayed HUGE. Then I ran the command Mark gave and
>> noticed the difference in DPI between my main rig and the new rig. I
>> then found out how to set that in xorg.conf and set it the same as my
>> main rig. As soon as I restarted DM, the screen came up the correct
>> size. The HUGE part was gone. When I rebooted, it was still the normal
>> size. It also worked each time I restarted DM. The only change is
>> setting DPI. Like this:
>>
>>
>> Section "Monitor"
>> Identifier "Monitor0"
>> VendorName "Unknown"
>> ModelName "Samsung LS32B30"
>> Option "PreferredMode" "1920x1080_60.00"
>> Option "DPMS"
>> Option "DPI" "80 x 80"
>>
>>
>> I just booted the new rig again and it has a normal display. None of
>> that huge stuff. I think I've rebooted like three times now and it
>> worked every time. I think that is the most reboots with a config that
>> works since I built this rig. Usually, it works once, maybe twice, then
>> fails. Later on, it might work again. This machine is like rolling
>> dice. You never know what you going to get. Three consecutive reboots
>> with it working gives me hope on this one. I won't be surprised if when
>> I hook up a second monitor or the TV that it breaks again tho. ;-)
>>
>> My only question now, is that a good setting or is there a better way to
>> make sure this thing works, each time I reboot?
>>
>> Dale
>>
>> :-) :-)
> Is this your monitor?
>
> https://www.samsung.com/us/business/computing/monitors/flat/32--s30b-fhd-75hz-amd-freesync-monitor-ls32b300nwnxgo/#specs
>
> If the screen is 27.5" wide and 15.47 high, then at a native 1,920 x 1,080
> pixel resolution the DPI would be approx. 70x70. However, if you're happy
> with the way it looks @80x80, then that's a good setting. After all, you're
> the one looking at it! :-)
Actually, mine is a LS32B304NWN. I'm not sure what the difference is
between 300 and 304. There may just be a minor version change but
display is the same. Sorta like a bug fix. Could be one is a slightly
newer model or something. I dunno. It's hi res and a good deal. :-D
Compared to the HUGE display, yea, it looks good. The reason I was
asking if that is correct is this, maybe it should be set to, just
guessing, 128 x 128 but some other setting makes the picture the right
size, not HUGE. If 70 x 70 or 80 x 80 is a setting that the monitor is
designed for and ideal, then that is fine. I don't see a DPI setting on
the link you posted. Can it be called something else?
Monitors, even the old CRTs, have resolutions and settings they work
best at. Those are the ones I'd like to use. If for no other reason,
it just makes it easier on the monitor to handle. I read once where a
person had a monitor that had a great picture at 60Hz refresh. Even tho
it would work at 75Hz, the picture wasn't as good. It seems that
something didn't like that 75Hz setting. That person used the 60Hz
setting. Some things are picky that way. Higher isn't always better.
I may try that 70 setting. Odds are, just like the difference between
60 and 75Hz refresh rate, I likely won't be able to tell the
difference. Time will tell tho.
By the way, I booted the rig up when I went to heat up supper and was
downloading new messages. It booted to a normal screen. I think it is
at least being consistent now. Before, it was hit or miss, mostly
miss. Given how good things are at just working, I'm surprised that the
correct setting wasn't used automatically. I'd think it should be.
Maybe that is a bug????
Now to go eat supper. I hope the monitor comes in soon. I ordered a
monitor stand too. I think the stand will be here before the monitor.
I'm kinda hoping the monitor was shipped but tracking info just wasn't
uploaded yet. That would make the monitor arrive sooner. Kinda
doubtful tho. Most are pretty quick to update those.
Dale
:-) :-)