9:21 p.m.
(f34; gnome (is that relevant?), NVIDIA Corporation GK106 [GeForce GTX
660], Dell U2711)
This is a dual-monitor home workstation.
This afternoon, the left monitor suddenly started displaying only dim
vertical stripes and lines and a black background, nothing else. The
right monitor still works fine. It is the same when I switch the
monitor cables on the back of the tower, at the graphics card outlets.
How do I determine whether the problem is the monitor, the graphics
card, the graphics driver, or something else?
Is there something to look for in a log file? If yes, what do I look
for, and which log file should I look in?
11:57 p.m.
On 4/2/22 19:21, home user wrote:
(f34; gnome (is that relevant?), NVIDIA Corporation GK106 [GeForce
GTX
660], Dell U2711)
This is a dual-monitor home workstation.
This afternoon, the left monitor suddenly started displaying only dim
vertical stripes and lines and a black background, nothing else. The
right monitor still works fine. It is the same when I switch the
monitor cables on the back of the tower, at the graphics card outlets.
How do I determine whether the problem is the monitor, the graphics
card, the graphics driver, or something else?
Given that switching the cables doesn't change the messed up display,
that really strongly points at the monitor failing. I assume that when
you switched the cables, the working monitor showed the other part of
the desktop. Do you have another computer to try the monitor on?
Is there something to look for in a log file? If yes, what do I look
for, and which log file should I look in?
If it's a monitor problem, then there isn't likely to be anything in the
logs.
2:13 p.m.
On 4/2/22 10:57 PM, Samuel Sieb wrote:
Thank-you, Samuel.
On 4/2/22 19:21, home user wrote:
> (f34; gnome (is that relevant?), NVIDIA Corporation GK106 [GeForce GTX
> 660], Dell U2711)
>
> This is a dual-monitor home workstation.
>
> This afternoon, the left monitor suddenly started displaying only dim
> vertical stripes and lines and a black background, nothing else. The
> right monitor still works fine. It is the same when I switch the
> monitor cables on the back of the tower, at the graphics card outlets.
> How do I determine whether the problem is the monitor, the graphics
> card, the graphics driver, or something else?
Given that switching the cables doesn't change the messed up display,
that really strongly points at the monitor failing. I assume that when
you switched the cables, the working monitor showed the other part of
the desktop. Do you have another computer to try the monitor on?
Assuming it's the monitor, is it realistically possible to replace bad
components (a cpu, memory, etc.) within the monitor, or are such
components available only to monitor manufacturers? If replacement is
possible, how can I determine which components are bad?
>> Is there something to look for in a log file? If yes, what do I look
>> for, and which log file should I look in?
>
> If it's a monitor problem, then there isn't likely to be anything in the
> logs.
2:20 p.m.
On 4/3/22 13:13, home user wrote:
Assuming it's the monitor, is it realistically possible to
replace bad
components (a cpu, memory, etc.) within the monitor, or are such
components available only to monitor manufacturers? If replacement is
possible, how can I determine which components are bad?
Assuming that the parts are available, how much time, effort and money
would it cost you to repair the monitor as compared to replacing it? Is
it really worth the effort?
2:38 p.m.
On Sun, 3 Apr 2022 at 16:20, Joe Zeff <joe(a)zeff.us> wrote:
On 4/3/22 13:13, home user wrote:
> Assuming it's the monitor, is it realistically possible to replace bad
> components (a cpu, memory, etc.) within the monitor, or are such
> components available only to monitor manufacturers? If replacement is
> possible, how can I determine which components are bad?
Assuming that the parts are available, how much time, effort and money
would it cost you to repair the monitor as compared to replacing it? Is
it really worth the effort?
If your problem turns out to be a common issue for your monitor model,
you may find repair instructions online, so you can estimate the time and
component costs. In some cases there are sources that supply
replacements for a failed circuit board with one that has been repaired for
a modest price with return of the failed board. Assuming your monitor
doesn't have a CRT and isn't one of the ultra-thin designs, swapping a
board is usually something that most people can handle given adequate
instructions (often a youtube video).
--
George N. White III
10:12 a.m.
(replying to both of George White's posts)
My e-mail service provider apparently thought both of your posts (and
several other posts Fedora users list posts to other threads) were
junk. So I did not see them until a few days later. But your attempts
to help are appreciated. The friend who gave me the used replacement
monitor told me I could not have repaired the bad monitor because it
would have needed a special tool that I don't have to open up the monitor.
Bill.
3:09 p.m.
On 4/3/22 1:20 PM, Joe Zeff wrote:
On 4/3/22 13:13, home user wrote:
> Assuming it's the monitor, is it realistically possible to replace bad
> components (a cpu, memory, etc.) within the monitor, or are such
> components available only to monitor manufacturers? If replacement is
> possible, how can I determine which components are bad?
Assuming that the parts are available, how much time, effort and money
would it cost you to repair the monitor as compared to replacing it? Is
it really worth the effort?
As best as I can determine, this monitor is no longer made. So if I
replace it, would I also have to replace the twin? If I replace it (or
both), would I also have to replace the graphics card? And then the
updating of the driver and operating system, that I dread!
What would a new monitor equivalent or better than the old one cost?
I'd be surprised if it were not "4 digits". (What is available that is
"equivalent"?)
I'm willing to put in a few hours of effort, not many. Money, I
seriously need to keep costs down as much as is practical. "Used" is
one option I'm thinking about.
3:15 p.m.
On 4/3/22 13:09, home user wrote:
On 4/3/22 1:20 PM, Joe Zeff wrote:
> On 4/3/22 13:13, home user wrote:
>> Assuming it's the monitor, is it realistically possible to replace
>> bad components (a cpu, memory, etc.) within the monitor, or are such
>> components available only to monitor manufacturers? If replacement
>> is possible, how can I determine which components are bad?
>
> Assuming that the parts are available, how much time, effort and money
> would it cost you to repair the monitor as compared to replacing it?
> Is it really worth the effort?
As best as I can determine, this monitor is no longer made. So if I
replace it, would I also have to replace the twin? If I replace it (or
both), would I also have to replace the graphics card? And then the
updating of the driver and operating system, that I dread!
Unless you need them to look the same, you don't need to replace the
working monitor. You definitely don't need to replace the video card or
anything else.
What would a new monitor equivalent or better than the old one cost?
I'd
be surprised if it were not "4 digits". (What is available that is
"equivalent"?)
You haven't said what the monitor is. It very much depends on size and
quality, but you should be able to get a reasonable monitor for
$100-$150USD. I recently bought a 24" monitor for about $150CAD.
3:35 p.m.
On 4/3/22 2:15 PM, Samuel Sieb wrote:
On 4/3/22 13:09, home user wrote:
> On 4/3/22 1:20 PM, Joe Zeff wrote:
>> On 4/3/22 13:13, home user wrote:
>>> Assuming it's the monitor, is it realistically possible to replace
>>> bad components (a cpu, memory, etc.) within the monitor, or are such
>>> components available only to monitor manufacturers? If replacement
>>> is possible, how can I determine which components are bad?
>>
>> Assuming that the parts are available, how much time, effort and
>> money would it cost you to repair the monitor as compared to
>> replacing it? Is it really worth the effort?
>
> As best as I can determine, this monitor is no longer made. So if I
> replace it, would I also have to replace the twin? If I replace it
> (or both), would I also have to replace the graphics card? And then
> the updating of the driver and operating system, that I dread!
Unless you need them to look the same, you don't need to replace the
working monitor. You definitely don't need to replace the video card or
anything else.
> What would a new monitor equivalent or better than the old one cost?
> I'd be surprised if it were not "4 digits". (What is available that
> is "equivalent"?)
You haven't said what the monitor is. It very much depends on size and
quality, but you should be able to get a reasonable monitor for
$100-$150USD. I recently bought a 24" monitor for about $150CAD.
It's a Dell Ultrasharp 2711b:
27-inch
2560x1440
16:9
6 ms
0.23 mm
60 Hz
flat, not curved
no speakers.
5:26 p.m.
On Sun, 2022-04-03 at 14:35 -0600, home user wrote:
On 4/3/22 2:15 PM, Samuel Sieb wrote:
> On 4/3/22 13:09, home user wrote:
> > On 4/3/22 1:20 PM, Joe Zeff wrote:
> > > On 4/3/22 13:13, home user wrote:
> > > > Assuming it's the monitor, is it realistically possible to
replace
> > > > bad components (a cpu, memory, etc.) within the monitor, or are such
> > > > components available only to monitor manufacturers? If replacement
> > > > is possible, how can I determine which components are bad?
> > >
> > > Assuming that the parts are available, how much time, effort and
> > > money would it cost you to repair the monitor as compared to
> > > replacing it? Is it really worth the effort?
> >
> > As best as I can determine, this monitor is no longer made. So if I
> > replace it, would I also have to replace the twin? If I replace it
> > (or both), would I also have to replace the graphics card? And then
> > the updating of the driver and operating system, that I dread!
>
> Unless you need them to look the same, you don't need to replace the
> working monitor. You definitely don't need to replace the video card or
> anything else.
>
> > What would a new monitor equivalent or better than the old one cost?
> > I'd be surprised if it were not "4 digits". (What is available
that
> > is "equivalent"?)
>
> You haven't said what the monitor is. It very much depends on size and
> quality, but you should be able to get a reasonable monitor for
> $100-$150USD. I recently bought a 24" monitor for about $150CAD.
It's a Dell Ultrasharp 2711b:
27-inch
2560x1440
16:9
6 ms
0.23 mm
60 Hz
flat, not curved
no speakers.
That monitor is probably discontinued, but Dell makes comparable monitors. You can browse
Dell's
website and select monitors that meet your size and resolution requirements. The
2560x1440
resolution you quoted is called QHD and, for example, Dell's S2721D (27" QHD)
costs $274.99 and
supports both HDMI and DisplayPort connections. I'm not recommending that one, just
saying it might
be an acceptable replacement. You should know to match the connector type on your video
card to the
connector type on the monitor, or else you will need an adapter.
3:21 p.m.
On Sun, Apr 3, 2022 at 4:10 PM home user <mattisonw(a)comcast.net> wrote:
On 4/3/22 1:20 PM, Joe Zeff wrote:
> On 4/3/22 13:13, home user wrote:
>> Assuming it's the monitor, is it realistically possible to replace bad
>> components (a cpu, memory, etc.) within the monitor, or are such
>> components available only to monitor manufacturers? If replacement is
>> possible, how can I determine which components are bad?
>
> Assuming that the parts are available, how much time, effort and money
> would it cost you to repair the monitor as compared to replacing it? Is
> it really worth the effort?
As best as I can determine, this monitor is no longer made. So if I
replace it, would I also have to replace the twin? If I replace it (or
both), would I also have to replace the graphics card? And then the
updating of the driver and operating system, that I dread!
No, if it's just the monitor, then no, you don't have
to twin the new one, or replace the GPU, and therefore
don't need to change drivers or OS. Just plug and play.
What would a new monitor equivalent or better than the old one cost?
I'd be surprised if it were not "4 digits". (What is
available that is
"equivalent"?)
This is a list of 'equivalent' monitors from my local store
(in Canadian dollars)
https://www.canadacomputers.com/index.php?cPath=22_1953_1958&sf=:3_4,...
What I asked for was 27", 2560 x 1440 resolution, and it seems that
6ms response time is obsolete now (current models are faster)
The only thing I didn't check for was 'colour accuracy'.
2:58 p.m.
On Sun, 2022-04-03 at 13:13 -0600, home user wrote:
Assuming it's the monitor, is it realistically possible to
replace
bad components (a cpu, memory, etc.) within the monitor, or are such
components available only to monitor manufacturers? If replacement
is possible, how can I determine which components are bad?
If it were standard electrical parts (such as caps and transistors in a
power supply of a dead monitor, they can be replaced). But if you're
getting erroneous behaviour that's more likely to be specialised parts
of the monitors. Such parts may be available, often only as whole
board swaps, for new and current model monitors, but not for
discontinued monitors. Pricing may be extortionate.
Often there are some generic boards available that suit a wide variety
of models, but you have to find the right ones, find someone selling
actually working ones, fit them. Again, pricing may be ridiculous.
NB: If you're coupling unearthed equipment (be that your monitor or
PC, where one or both are unearthed), you really want them all to be
fully powered off while connecting or disconnecting them. Unearthed
equipment can float at high voltages (generally not a problem for
humans) but can zap ICs directly connected to the ports. This can zap
things instantly, or can cause eventual breakdowns (equipment may fail
long after connecting them up, so you never attribute the fault to this
action). Of course, equipment does spontaneously die for no apparent
cause, but the above scenario is more common than you'd think.
--
uname -rsvp
Linux 5.11.22-100.fc32.x86_64 #1 SMP Wed May 19 18:58:25 UTC 2021 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
3:26 p.m.
On 4/3/22 1:58 PM, Tim via users wrote:
On Sun, 2022-04-03 at 13:13 -0600, home user wrote:
> Assuming it's the monitor, is it realistically possible to replace
> bad components (a cpu, memory, etc.) within the monitor, or are such
> components available only to monitor manufacturers? If replacement
> is possible, how can I determine which components are bad?
If it were standard electrical parts (such as caps and transistors in a
power supply of a dead monitor, they can be replaced). But if you're
getting erroneous behaviour that's more likely to be specialised parts
of the monitors. Such parts may be available, often only as whole
board swaps, for new and current model monitors, but not for
discontinued monitors. Pricing may be extortionate.
Often there are some generic boards available that suit a wide variety
of models, but you have to find the right ones, find someone selling
actually working ones, fit them. Again, pricing may be ridiculous.
NB: If you're coupling unearthed equipment (be that your monitor or
PC, where one or both are unearthed), you really want them all to be
fully powered off while connecting or disconnecting them. Unearthed
equipment can float at high voltages (generally not a problem for
humans) but can zap ICs directly connected to the ports. This can zap
things instantly, or can cause eventual breakdowns (equipment may fail
long after connecting them up, so you never attribute the fault to this
action). Of course, equipment does spontaneously die for no apparent
cause, but the above scenario is more common than you'd think.
"unearthed"? I know that isn't meant literally, but I don't know what
you do mean. What is "unearthed" in this context?
10:25 p.m.
On Sun, 2022-04-03 at 14:26 -0600, home user wrote:
"unearthed"? I know that isn't meant literally, but I
don't know
what you do mean. What is "unearthed" in this context?
Two-pin mains plug vs three-pin mains plug (live, neutral, earth).
--
uname -rsvp
Linux 3.10.0-1160.59.1.el7.x86_64 #1 SMP Wed Feb 23 16:47:03 UTC 2022 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
10:50 p.m.
On 4/3/22 9:25 PM, Tim via users wrote:
On Sun, 2022-04-03 at 14:26 -0600, home user wrote:
> "unearthed"? I know that isn't meant literally, but I don't know
> what you do mean. What is "unearthed" in this context?
Two-pin mains plug vs three-pin mains plug (live, neutral, earth).
aaa-Ha. Australian English vs. American English.
:)
I understand now. What you call "earth", I call "ground". What you
call "pin", I call "prong". I also haven't seen "mains"
used that way
before. When I hear "Mains", I think of a surname. (Decades ago, I had
a friend and co-worker surnamed "Mains". There was also a Christian
ministry leader named David Mains.)
Thank-you.
Bill.
7:36 a.m.
On Sat, 2 Apr 2022 at 23:21, home user <mattisonw(a)comcast.net> wrote:
(f34; gnome (is that relevant?), NVIDIA Corporation GK106 [GeForce
GTX
660], Dell U2711)
This is a dual-monitor home workstation.
This afternoon, the left monitor suddenly started displaying only dim
vertical stripes and lines and a black background, nothing else. The
right monitor still works fine. It is the same when I switch the
monitor cables on the back of the tower, at the graphics card outlets.
I assume that by "the same" you mean that the left monitor display
doesn't change. This means either a cable or monitor issue.
How do I determine whether the problem is the monitor, the graphics
card, the graphics driver, or something else?
Is there something to look for in a log file? If yes, what do I look
for, and which log file should I look in?
Try swapping the cables and connecting the left monitor to a different
computer. Modern hardware is so reproducible that the same failure
often shows up across many monitors of the same model and
similar manufacturing dates. An internet search may be helpful --
sometimes the fix is known (but may require a professional
soldering setup to replace the failed component).
--
George N. White III
5:15 p.m.
On 4/2/22 8:21 PM, home user wrote:
(f34; gnome (is that relevant?), NVIDIA Corporation GK106 [GeForce
GTX
660], Dell U2711)
This is a dual-monitor home workstation.
This afternoon, the left monitor suddenly started displaying only dim
vertical stripes and lines and a black background, nothing else. The
right monitor still works fine. It is the same when I switch the
monitor cables on the back of the tower, at the graphics card outlets.
How do I determine whether the problem is the monitor, the graphics
card, the graphics driver, or something else?
Is there something to look for in a log file? If yes, what do I look
for, and which log file should I look in?
A local friend had access to a spare Dell P2412H monitor (from a
business that shut down a local office?); he gave it to me today. It is
working. But windows and text are obviously bigger on this new monitor
than on the remaining older Dell U2711. Is there a way of making things
appear the same size on the P2412H (too big) as on the U2711 (about right)?
10:22 a.m.
On Mon, 4 Apr 2022 at 23:15, home user <mattisonw(a)comcast.net> wrote:
[... snip ...] But windows and text are obviously bigger on this new
monitor
than on the remaining older Dell U2711. Is there a way of making
things appear
the same size on the P2412H (too big) as on the U2711 (about right)?
This problem persists. I've spent a lot of time in settings tools,
"NVIDIA X Server Settings", and Fedora documentation trying to find a
solution. Nothing helped. If it matters, I upgraded to Fedoa-35 this
past Thursday (April 07). This is a dual-boot workstation, and when I
boot into windows-7, text, windows, etc. appear the same size on both
monitors.
Any suggestions?
11 a.m.
Check that both monitors are running the same resolution.
Also run "xdpyinfo" (rpm is xdpyinfo if you don't have it installed, I
don't know if this tool works on wayland or not) and see if the listed size
of the screens and dpi is similar on both monitors. I have seen some
devices that the EDID info is wrong and because of that it calculates the
DPI wrong and adjusts sizes based on that data. MIne produces output like
this:
Screen #0:
dimensions: 3840x2160 pixels (1016x571 millimeters)
resolution: 96x96 dots per inch
Mine is actually 940mm x 530mm so EDID lists my monitor as about 8% bigger
than it really is
Windows may have a monitor device table that it uses that has correct
values in it, or windows 7 may not be playing any DPI scaling games.
On Sat, Apr 9, 2022 at 10:22 AM home user <mattisonw(a)comcast.net> wrote:
On Mon, 4 Apr 2022 at 23:15, home user <mattisonw(a)comcast.net>
wrote:
> [... snip ...] But windows and text are obviously bigger on this new
monitor
> than on the remaining older Dell U2711. Is there a way of making
things appear
> the same size on the P2412H (too big) as on the U2711 (about right)?
This problem persists. I've spent a lot of time in settings tools,
"NVIDIA X Server Settings", and Fedora documentation trying to find a
solution. Nothing helped. If it matters, I upgraded to Fedoa-35 this
past Thursday (April 07). This is a dual-boot workstation, and when I
boot into windows-7, text, windows, etc. appear the same size on both
monitors.
Any suggestions?
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
11:36 a.m.
On 4/9/22 10:00 AM, Roger Heflin wrote:
Check that both monitors are running the same resolution.
How do I do that?
Also run "xdpyinfo" (rpm is xdpyinfo if you don't have
it installed, I
don't know if this tool works on wayland or not) and see if the listed
size of the screens and dpi is similar on both monitors. I have seen
some devices that the EDID info is wrong and because of that it
calculates the DPI wrong and adjusts sizes based on that data. MIne
produces output like this:
Screen #0:
dimensions: 3840x2160 pixels (1016x571 millimeters)
resolution: 96x96 dots per inch
Mine is actually 940mm x 530mm so EDID lists my monitor as about 8%
bigger than it really is
Windows may have a monitor device table that it uses that has correct
values in it, or windows 7 may not be playing any DPI scaling games.
Yeow! I get hundreds of line of output! I don't see anything in the
man page for paring this down. How do I pare down the output? The
output looks identical regardless of which monitor I run the command on.
5:20 p.m.
you need to look for the section that says Screen #0/#1 and the next few
lines will the the stuff you care about (size/dpi).
On Sat, Apr 9, 2022 at 11:37 AM home user <mattisonw(a)comcast.net> wrote:
On 4/9/22 10:00 AM, Roger Heflin wrote:
> Check that both monitors are running the same resolution.
How do I do that?
> Also run "xdpyinfo" (rpm is xdpyinfo if you don't have it installed,
I
> don't know if this tool works on wayland or not) and see if the listed
> size of the screens and dpi is similar on both monitors. I have seen
> some devices that the EDID info is wrong and because of that it
> calculates the DPI wrong and adjusts sizes based on that data. MIne
> produces output like this:
>
> Screen #0:
> dimensions: 3840x2160 pixels (1016x571 millimeters)
> resolution: 96x96 dots per inch
>
> Mine is actually 940mm x 530mm so EDID lists my monitor as about 8%
> bigger than it really is
>
> Windows may have a monitor device table that it uses that has correct
> values in it, or windows 7 may not be playing any DPI scaling games.
Yeow! I get hundreds of line of output! I don't see anything in the
man page for paring this down. How do I pare down the output? The
output looks identical regardless of which monitor I run the command on.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
7:02 p.m.
On 4/9/22 4:20 PM, Roger Heflin wrote:
you need to look for the section that says Screen #0/#1 and the next
few
lines will the the stuff you care about (size/dpi).
On Sat, Apr 9, 2022 at 11:37 AM home user <mattisonw(a)comcast.net
<mailto:mattisonw@comcast.net>> wrote:
On 4/9/22 10:00 AM, Roger Heflin wrote:
> Check that both monitors are running the same resolution.
How do I do that?
> Also run "xdpyinfo" (rpm is xdpyinfo if you don't have it
installed, I
> don't know if this tool works on wayland or not) and see if the
listed
> size of the screens and dpi is similar on both monitors. I have
seen
> some devices that the EDID info is wrong and because of that it
> calculates the DPI wrong and adjusts sizes based on that data. MIne
> produces output like this:
>
> Screen #0:
> dimensions: 3840x2160 pixels (1016x571 millimeters)
> resolution: 96x96 dots per inch
>
> Mine is actually 940mm x 530mm so EDID lists my monitor as about 8%
> bigger than it really is
>
> Windows may have a monitor device table that it uses that has
correct
> values in it, or windows 7 may not be playing any DPI scaling games.
Yeow! I get hundreds of line of output! I don't see anything in the
man page for paring this down. How do I pare down the output? The
output looks identical regardless of which monitor I run the command on.
Here we go:
-----
bash.1[~]: xdpyinfo | grep dimensions
dimensions: 4480x1440 pixels (1185x381 millimeters)
bash.2[~]: xdpyinfo | grep resolution
resolution: 96x96 dots per inch
bash.3[~]: xdpyinfo | more
name of display: :1
version number: 11.0
vendor string: The X.Org Foundation
vendor release number: 12014000
X.Org version: 1.20.14
maximum request size: 16777212 bytes
motion buffer size: 256
bitmap unit, bit order, padding: 32, LSBFirst, 32
image byte order: LSBFirst
number of supported pixmap formats: 7
supported pixmap formats:
depth 1, bits_per_pixel 1, scanline_pad 32
depth 4, bits_per_pixel 8, scanline_pad 32
depth 8, bits_per_pixel 8, scanline_pad 32
depth 15, bits_per_pixel 16, scanline_pad 32
depth 16, bits_per_pixel 16, scanline_pad 32
depth 24, bits_per_pixel 32, scanline_pad 32
depth 32, bits_per_pixel 32, scanline_pad 32
keycode range: minimum 8, maximum 255
focus: window 0x360000b, revert to Parent
number of extensions: 30
BIG-REQUESTS
Composite
DAMAGE
DOUBLE-BUFFER
DPMS
DRI2
GLX
Generic Event Extension
MIT-SCREEN-SAVER
MIT-SHM
NV-CONTROL
NV-GLX
Present
RANDR
RECORD
RENDER
SECURITY
SHAPE
SYNC
X-Resource
XC-MISC
XFIXES
XFree86-DGA
XFree86-VidModeExtension
XINERAMA
XINERAMA
XInputExtension
XKEYBOARD
XTEST
XVideo
default screen number: 0
number of screens: 1
screen #0:
dimensions: 4480x1440 pixels (1185x381 millimeters)
resolution: 96x96 dots per inch
depths (7): 24, 1, 4, 8, 15, 16, 32
root window id: 0x296
depth of root window: 24 planes
number of colormaps: minimum 1, maximum 1
default colormap: 0x20
default number of colormap cells: 256
preallocated pixels: black 0, white 16777215
options: backing-store WHEN MAPPED, save-unders NO
largest cursor: 256x256
current input event mask: 0xda0033
KeyPressMask KeyReleaseMask EnterWindowMask
LeaveWindowMask StructureNotifyMask
SubstructureNotifyMask
SubstructureRedirectMask PropertyChangeMask
ColormapChangeMask
number of visuals: 228
default visual id: 0x21
visual:
visual id: 0x21
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 11 bits
visual:
visual id: 0x22
class: DirectColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 11 bits
[... snip ...]
bash.4[~]:
-----
Any ideas?
7:28 p.m.
On Sat, 9 Apr 2022 at 21:03, home user <mattisonw(a)comcast.net> wrote:
On 4/9/22 4:20 PM, Roger Heflin wrote:
> you need to look for the section that says Screen #0/#1 and the next few
> lines will the the stuff you care about (size/dpi).
>
> On Sat, Apr 9, 2022 at 11:37 AM home user <mattisonw(a)comcast.net
> <mailto:mattisonw@comcast.net>> wrote:
>
> On 4/9/22 10:00 AM, Roger Heflin wrote:
> > Check that both monitors are running the same resolution.
>
> How do I do that?
>
> > Also run "xdpyinfo" (rpm is xdpyinfo if you don't have it
> installed, I
> > don't know if this tool works on wayland or not) and see if the
> listed
> > size of the screens and dpi is similar on both monitors. I have
> seen
> > some devices that the EDID info is wrong and because of that it
> > calculates the DPI wrong and adjusts sizes based on that data.
MIne
> > produces output like this:
> >
> > Screen #0:
> > dimensions: 3840x2160 pixels (1016x571 millimeters)
> > resolution: 96x96 dots per inch
> >
> > Mine is actually 940mm x 530mm so EDID lists my monitor as about
8%
> > bigger than it really is
> >
> > Windows may have a monitor device table that it uses that has
> correct
> > values in it, or windows 7 may not be playing any DPI scaling
games.
>
> Yeow! I get hundreds of line of output! I don't see anything in the
> man page for paring this down. How do I pare down the output? The
> output looks identical regardless of which monitor I run the command
on.
Here we go:
-----
bash.1[~]: xdpyinfo | grep dimensions
dimensions: 4480x1440 pixels (1185x381 millimeters)
bash.2[~]: xdpyinfo | grep resolution
resolution: 96x96 dots per inch
I think Xorg makes one big "window" large enough to include both monitors.
96 dpi
is the default. I've only used dual monitors on Xorg a few times, and the
monitors
were identical.
Maybe this will help:
How to get a dual monitor setup with mixed DPI working on Xorg – The
Midnight Sun (lguruprasad.in)
<https://www.lguruprasad.in/blog/2020/01/13/how-to-get-a-dual-monitor-setu...
--
George N. White III
7:59 p.m.
On 4/9/22 6:28 PM, George N. White III wrote:
On Sat, 9 Apr 2022 at 21:03, home user <mattisonw(a)comcast.net
<mailto:mattisonw@comcast.net>> wrote:
On 4/9/22 4:20 PM, Roger Heflin wrote:
> you need to look for the section that says Screen #0/#1 and the
next few
> lines will the the stuff you care about (size/dpi).
>
> On Sat, Apr 9, 2022 at 11:37 AM home user <mattisonw(a)comcast.net
<mailto:mattisonw@comcast.net>
> <mailto:mattisonw@comcast.net <mailto:mattisonw@comcast.net>>>
wrote:
>
> On 4/9/22 10:00 AM, Roger Heflin wrote:
> > Check that both monitors are running the same resolution.
>
> How do I do that?
>
> > Also run "xdpyinfo" (rpm is xdpyinfo if you don't have
it
> installed, I
> > don't know if this tool works on wayland or not) and see
if the
> listed
> > size of the screens and dpi is similar on both monitors.
I have
> seen
> > some devices that the EDID info is wrong and because of
that it
> > calculates the DPI wrong and adjusts sizes based on that
data. MIne
> > produces output like this:
> >
> > Screen #0:
> > dimensions: 3840x2160 pixels (1016x571 millimeters)
> > resolution: 96x96 dots per inch
> >
> > Mine is actually 940mm x 530mm so EDID lists my monitor as
about 8%
> > bigger than it really is
> >
> > Windows may have a monitor device table that it uses that has
> correct
> > values in it, or windows 7 may not be playing any DPI
scaling games.
>
> Yeow! I get hundreds of line of output! I don't see
anything in the
> man page for paring this down. How do I pare down the
output? The
> output looks identical regardless of which monitor I run the
command on.
Here we go:
-----
bash.1[~]: xdpyinfo | grep dimensions
dimensions: 4480x1440 pixels (1185x381 millimeters)
bash.2[~]: xdpyinfo | grep resolution
resolution: 96x96 dots per inch
I think Xorg makes one big "window" large enough to include both
monitors. 96 dpi
is the default. I've only used dual monitors on Xorg a few times, and
the monitors
were identical.
Maybe this will help:
How to get a dual monitor setup with mixed DPI working on Xorg – The
Midnight Sun (lguruprasad.in)
<https://www.lguruprasad.in/blog/2020/01/13/how-to-get-a-dual-monitor-setu...
--
George N. White III
Where does the xrandr command go? Neither the web page you reference
nor the xrandr man page gives any clue.
8:37 p.m.
On Sat, 9 Apr 2022 at 22:00, home user <mattisonw(a)comcast.net> wrote:
On 4/9/22 6:28 PM, George N. White III wrote:
>
> Maybe this will help:
> How to get a dual monitor setup with mixed DPI working on Xorg – The
> Midnight Sun (lguruprasad.in)
> <
https://www.lguruprasad.in/blog/2020/01/13/how-to-get-a-dual-monitor-setu...
>
Where does the xrandr command go? Neither the web page you reference
nor the xrandr man page gives any clue.
STARTX <https://www.x.org/releases/X11R7.6/doc/man/man1/startx.1.xhtml>
--
George N. White III
9:18 p.m.
On 4/9/22 7:37 PM, George N. White III wrote:
On Sat, 9 Apr 2022 at 22:00, home user <mattisonw(a)comcast.net
<mailto:mattisonw@comcast.net>> wrote:
On 4/9/22 6:28 PM, George N. White III wrote:
>
> Maybe this will help:
> How to get a dual monitor setup with mixed DPI working on Xorg – The
> Midnight Sun (lguruprasad.in <http://lguruprasad.in>)
>
<https://www.lguruprasad.in/blog/2020/01/13/how-to-get-a-dual-monitor-setu...
<https://www.lguruprasad.in/blog/2020/01/13/how-to-get-a-dual-monitor-setu...
Where does the xrandr command go? Neither the web page you reference
nor the xrandr man page gives any clue.
STARTX <https://www.x.org/releases/X11R7.6/doc/man/man1/startx.1.xhtml>
Some parts of the xrandr I was able to figure out quickly. Other parts,
I spent a huge amount of time on, and I've got educated guesses, but I'm
still not sure.
left monitor: 1920 x 1080.
right monitor: 2560 x 1440.
What I think the xrandr command should be:
-----
xrandr --fbmm 5920x3330 --output DP-0 --pos 3360x0 --mode 2560x1440
--scale 1x1 --primary --output HDMI-0 --pos 0x0 --mode 1920x1080 --scale
1.75x1.75
-----
But I still don't get where to put the command. It seems to me that
this should be taken care of during boot-up, before the log-in screen is
displayed. I don't see how startx helps. On my work station, I don't
see any of the files listed by the startx web page you referenced:
-----
bash.15[~]: ls -a X* x* .X* .x*
ls: cannot access 'X*': No such file or directory
ls: cannot access 'x*': No such file or directory
ls: cannot access '.X*': No such file or directory
.xfce4-session.verbose-log .xscreensaver
.xournal:
. .. recent-files
bash.16[~]: su -
Password:
-bash.1[~]: cd /usr/lib/
-bash.2[lib]: ls -a X* x* .X* .x*
ls: cannot access 'X*': No such file or directory
ls: cannot access 'x*': No such file or directory
ls: cannot access '.X*': No such file or directory
ls: cannot access '.x*': No such file or directory
-bash.3[lib]:
-----
Also, Tim's Friday night (Colorado time) post suggests none of this is
needed.
How do I proceed?
>
> --
> George N. White III
5:53 a.m.
Do you know what the max supported resolution is of both monitors?
If both are capable of the same resolution then it may simply be that the
one with the current wrong resolution needs to be changed in the display
setup to match. I think the nvidia-settings tool can also adjust the
monitor resolutions (if you are using the nvidia driver). When connecting
different monitors they seem to often pick the wrong (not max) resolution,
and I have had to go into display settings and change it.
The sub-optimal solution would be to change the higher res monitor to the
same resolution of the lower resolution monitor (ie pick a common supported
resolution for both monitors) but that would lose quite a bit of pixels.
On Mon, Apr 11, 2022 at 9:19 PM home user <mattisonw(a)comcast.net> wrote:
On 4/9/22 7:37 PM, George N. White III wrote:
> On Sat, 9 Apr 2022 at 22:00, home user <mattisonw(a)comcast.net
> <mailto:mattisonw@comcast.net>> wrote:
>
> On 4/9/22 6:28 PM, George N. White III wrote:
> >
> > Maybe this will help:
> > How to get a dual monitor setup with mixed DPI working on Xorg –
The
> > Midnight Sun (lguruprasad.in <http://lguruprasad.in>)
> >
> <
https://www.lguruprasad.in/blog/2020/01/13/how-to-get-a-dual-monitor-setu...
> <
https://www.lguruprasad.in/blog/2020/01/13/how-to-get-a-dual-monitor-setu...
>>
>
> Where does the xrandr command go? Neither the web page you reference
> nor the xrandr man page gives any clue.
>
>
> STARTX <https://www.x.org/releases/X11R7.6/doc/man/man1/startx.1.xhtml>
Some parts of the xrandr I was able to figure out quickly. Other parts,
I spent a huge amount of time on, and I've got educated guesses, but I'm
still not sure.
left monitor: 1920 x 1080.
right monitor: 2560 x 1440.
What I think the xrandr command should be:
-----
xrandr --fbmm 5920x3330 --output DP-0 --pos 3360x0 --mode 2560x1440
--scale 1x1 --primary --output HDMI-0 --pos 0x0 --mode 1920x1080 --scale
1.75x1.75
-----
But I still don't get where to put the command. It seems to me that
this should be taken care of during boot-up, before the log-in screen is
displayed. I don't see how startx helps. On my work station, I don't
see any of the files listed by the startx web page you referenced:
-----
bash.15[~]: ls -a X* x* .X* .x*
ls: cannot access 'X*': No such file or directory
ls: cannot access 'x*': No such file or directory
ls: cannot access '.X*': No such file or directory
.xfce4-session.verbose-log .xscreensaver
.xournal:
. .. recent-files
bash.16[~]: su -
Password:
-bash.1[~]: cd /usr/lib/
-bash.2[lib]: ls -a X* x* .X* .x*
ls: cannot access 'X*': No such file or directory
ls: cannot access 'x*': No such file or directory
ls: cannot access '.X*': No such file or directory
ls: cannot access '.x*': No such file or directory
-bash.3[lib]:
-----
Also, Tim's Friday night (Colorado time) post suggests none of this is
needed.
How do I proceed?
>
> --
> George N. White III
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
10:22 a.m.
On 4/12/22 4:53 AM, Roger Heflin wrote:
Do you know what the max supported resolution is of both monitors?
If both are capable of the same resolution then it may simply be that
the one with the current wrong resolution needs to be changed in the
display setup to match. I think the nvidia-settings tool can also
adjust the monitor resolutions (if you are using the nvidia driver).
When connecting different monitors they seem to often pick the wrong
(not max) resolution, and I have had to go into display settings and
change it.
The sub-optimal solution would be to change the higher res monitor to
the same resolution of the lower resolution monitor (ie pick a common
supported resolution for both monitors) but that would lose quite a bit
of pixels.
According to Dell, the max resolutions are:
- left monitor, Dell Professional P2412H, 1920 x 1080.
- right monitor, Dell Ultrasharp 2711b, 2560 x 1440.
I've attached screen-captures of the "NVIDIA X Server Settings" for the
2 monitors. Because of cabling, right and left are reversed in the GUI.
Question: What is Resolution = "Auto" actually selecting?
By the way, I almost always use gnome. The xrandr article that Geoge
referred to seemed to assume Plasma.
Bill.
On Mon, Apr 11, 2022 at 9:19 PM home user <mattisonw(a)comcast.net
<mailto:mattisonw@comcast.net>> wrote:
On 4/9/22 7:37 PM, George N. White III wrote:
> On Sat, 9 Apr 2022 at 22:00, home user <mattisonw(a)comcast.net
<mailto:mattisonw@comcast.net>
> <mailto:mattisonw@comcast.net <mailto:mattisonw@comcast.net>>>
wrote:
>
> On 4/9/22 6:28 PM, George N. White III wrote:
> >
> > Maybe this will help:
> > How to get a dual monitor setup with mixed DPI working on
Xorg – The
> > Midnight Sun (lguruprasad.in <http://lguruprasad.in>
<http://lguruprasad.in <http://lguruprasad.in>>)
> >
>
<https://www.lguruprasad.in/blog/2020/01/13/how-to-get-a-dual-monitor-setup-with-mixed-dpi-working-on-xorg/
<https://www.lguruprasad.in/blog/2020/01/13/how-to-get-a-dual-monitor-setu...
>
<https://www.lguruprasad.in/blog/2020/01/13/how-to-get-a-dual-monitor-setup-with-mixed-dpi-working-on-xorg/
<https://www.lguruprasad.in/blog/2020/01/13/how-to-get-a-dual-monitor-setu...
>
> Where does the xrandr command go? Neither the web page you
reference
> nor the xrandr man page gives any clue.
>
>
> STARTX
<https://www.x.org/releases/X11R7.6/doc/man/man1/startx.1.xhtml
<https://www.x.org/releases/X11R7.6/doc/man/man1/startx.1.xhtml>>
Some parts of the xrandr I was able to figure out quickly. Other
parts,
I spent a huge amount of time on, and I've got educated guesses, but
I'm
still not sure.
left monitor: 1920 x 1080.
right monitor: 2560 x 1440.
What I think the xrandr command should be:
-----
xrandr --fbmm 5920x3330 --output DP-0 --pos 3360x0 --mode 2560x1440
--scale 1x1 --primary --output HDMI-0 --pos 0x0 --mode 1920x1080
--scale
1.75x1.75
-----
But I still don't get where to put the command. It seems to me that
this should be taken care of during boot-up, before the log-in
screen is
displayed. I don't see how startx helps. On my work station, I don't
see any of the files listed by the startx web page you referenced:
-----
bash.15[~]: ls -a X* x* .X* .x*
ls: cannot access 'X*': No such file or directory
ls: cannot access 'x*': No such file or directory
ls: cannot access '.X*': No such file or directory
.xfce4-session.verbose-log .xscreensaver
.xournal:
. .. recent-files
bash.16[~]: su -
Password:
-bash.1[~]: cd /usr/lib/
-bash.2[lib]: ls -a X* x* .X* .x*
ls: cannot access 'X*': No such file or directory
ls: cannot access 'x*': No such file or directory
ls: cannot access '.X*': No such file or directory
ls: cannot access '.x*': No such file or directory
-bash.3[lib]:
-----
Also, Tim's Friday night (Colorado time) post suggests none of this is
needed.
How do I proceed?
>
> --
> George N. White III
11:17 p.m.
On Sat, 2022-04-09 at 21:28 -0300, George N. White III wrote:
I think Xorg makes one big "window" large enough to include
both
monitors. 96 dpi is the default. I've only used dual monitors on
Xorg a few times, and the monitors were identical.
Many years ago I ran dual monitors for a while, both were very different. They had
different pixel count, size, and aspect ratio, and I think even different frame rates. It
handled it quite well and painlessly. Though there was some peculiarities as the mouse
pointed crossed over the border between them. It didn't seem to be one large
rectangle that was carved into two, more like fitting tetris blocks together. One monitor
could even be portrait while the other wasn't.
--
uname -rsvp
Linux 3.10.0-1160.59.1.el7.x86_64 #1 SMP Wed Feb 23 16:47:03 UTC 2022 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
749
days inactive
758
days old
28 comments
8 participants
participants (8)
-
C Linus Hicks -
Fulko Hew -
George N. White III -
home user -
Joe Zeff -
Roger Heflin -
Samuel Sieb -
Tim