| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 27 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 46:39:01 |
| Calls: | 632 |
| Calls today: | 3 |
| Files: | 1,187 |
| D/L today: |
24 files (29,813K bytes) |
| Messages: | 176,485 |
To my surprise, delight and consternation both screens came up.
interrobang varieties
This morning my main computer (this one) came up but only one screen
was working.
The graphics card has 4 sockets. One HDMI and 3 DisplayPorts. Both my
screens use HDMI, so they have adapters. I switched everything round
and found both screens worked provided they were plugged into one
particular displayport.
Checking "Display" in system settings only shows one screen.
Just before I clocked off for the night, I thought I would boot up on
the Mint 22.1 install flashdrive.
To my surprise, delight and consternation both screens came up.
Now I need to work out where the fault lies in the software?
Suggestions please. :(
Alan
On Thu, 9/25/2025 5:14 PM, pinnerite wrote:
This morning my main computer (this one) came up but only one screen
was working.
The graphics card has 4 sockets. One HDMI and 3 DisplayPorts. Both my
screens use HDMI, so they have adapters. I switched everything round
and found both screens worked provided they were plugged into one
particular displayport.
Checking "Display" in system settings only shows one screen.
Just before I clocked off for the night, I thought I would boot up on
the Mint 22.1 install flashdrive.
To my surprise, delight and consternation both screens came up.
Now I need to work out where the fault lies in the software?
Suggestions please. :(
Alan
xrandr --query
xrandr --listactivemonitors
readedit ... | parseedid
Paul
On Thu, 9/25/2025 8:30 PM, Paul wrote:
On Thu, 9/25/2025 5:14 PM, pinnerite wrote:
This morning my main computer (this one) came up but only one screen
was working.
The graphics card has 4 sockets. One HDMI and 3 DisplayPorts. Both my
screens use HDMI, so they have adapters. I switched everything round
and found both screens worked provided they were plugged into one
particular displayport.
Checking "Display" in system settings only shows one screen.
Just before I clocked off for the night, I thought I would boot up on
the Mint 22.1 install flashdrive.
To my surprise, delight and consternation both screens came up.
Now I need to work out where the fault lies in the software?
Suggestions please. :(
Alan
xrandr --query
xrandr --listactivemonitors
readedit ... | parseedid
Paul
That should be readEDID. As the EDID serial interface on a monitor,
declares the resolution choices of that monitor, and being able
to read the EDID, proves it is connected.
Paul
This morning my main computer (this one) came up but only one screen
was working.
The graphics card has 4 sockets. One HDMI and 3 DisplayPorts. Both my
screens use HDMI, so they have adapters. I switched everything round
and found both screens worked provided they were plugged into one
particular displayport.
Checking "Display" in system settings only shows one screen.
Just before I clocked off for the night, I thought I would boot up on
the Mint 22.1 install flashdrive.
To my surprise, delight and consternation both screens came up.
Now I need to work out where the fault lies in the software?
Suggestions please. :(
Alan
----- Synchronet 3.21a-Linux NewsLink 1.2
Linux Mint 22.1 kernel version 6.8.0-84-generic Cinnamon 6.4.8
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda
On Thu, 25 Sep 2025 22:14:14 +0100
pinnerite <pinnerite@gmail.com> wrote:
This morning my main computer (this one) came up but only one screen
was working.
The graphics card has 4 sockets. One HDMI and 3 DisplayPorts. Both my
screens use HDMI, so they have adapters. I switched everything round
and found both screens worked provided they were plugged into one
particular displayport.
Checking "Display" in system settings only shows one screen.
Just before I clocked off for the night, I thought I would boot up on
the Mint 22.1 install flashdrive.
To my surprise, delight and consternation both screens came up.
Now I need to work out where the fault lies in the software?
Suggestions please. :(
Alan
Well, after a morning of faffing about, ChatGPT came up with a "successfull" result.
Here is its advice:
https://www.dropbox.com/scl/fi/7q3vu9tu9sixvpd75tvtv/Steps_for_2nd_monitor.pdf?rlkey=mitrs0uf8pih1oye8zf1gaqph&st=7c44vnss&dl=0
However!
My system has a 2TB NVMe and a 2TB hard drive.
When I rebooted what came up puzzled me.
I couldn't find the notes that I had saved prior to reboot.
The answer was it had booted off the hard-drive.
The data was intact but on the NVMe.
Several desktop icons were missing too but these things are easy to fix.
It looks like the origibal problem arose from something dodgy in an update.
Thanks for the suggestions,
Alan
--
Linux Mint 22.1 kernel version 6.8.0-84-generic Cinnamon 6.4.8
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda
I started with a Mint 22.1 system, that yesterday was running two
screens perfectly.
This morning only one was recognised.
I have spent the whole day following what seemed to be logical
instructions from ChatGPT, constantly hitting brick walls, followed by
"Ah - I can see the problem ... "
At the end of the day I can only get into the system by getting to the
Boot Menu and selecting the install flash drive but opening up in the
correct home page.
Still only one screen and that one over scanned!
The desktop icons have had to be reduced from small to smaller.
sudo modprobe -n -v amdgpu
[sudo] password for alan:
insmod /lib/modules/6.8.0-84-generic/kernel/drivers/gpu/drm/display/drm_display_helper.ko.zst
insmod /lib/modules/6.8.0-84-generic/kernel/drivers/gpu/drm/ttm/ttm.ko.zst insmod /lib/modules/6.8.0-84-generic/kernel/drivers/gpu/drm/drm_ttm_helper.ko.zst
insmod /lib/modules/6.8.0-84-generic/kernel/drivers/gpu/drm/drm_suballoc_helper.ko.zst
insmod /lib/modules/6.8.0-84-generic/kernel/drivers/gpu/drm/drm_buddy.ko.zst insmod /lib/modules/6.8.0-84-generic/kernel/drivers/gpu/drm/scheduler/gpu-sched.ko.zst
insmod /lib/modules/6.8.0-84-generic/kernel/drivers/gpu/drm/drm_exec.ko.zst insmod /lib/modules/6.8.0-84-generic/kernel/drivers/gpu/drm/amd/amdxcp/amdxcp.ko.zst
insmod /lib/modules/6.8.0-84-generic/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko.zst
exp_hw_support=1
That suggests the amdgpu modules are loaded.
The bootloader is correctly set for EFI.
I once had a charming Singaporean assistant in the days before microcomputers. We used to key in transactions and their codes which
later became converted to paper tape. This later was transported to a mainframe data centre, later returning along with a fan-folded prinout.
The problem was that he and his colleagues were forever hitting the
wrong keys and jamming the punch. I got over that by removing the
"naughty" keys and Sellotaping over the holes. Yet because of ther
amount of pounding the ke=yboard received, keys still jammed it.
My You friend said "Mr A" machine work hard very tired. Maybe should
rest.
Which is what I am going to do now.
Alan
If the monitors are really there, an XRandR command should be able
to make the monitors do things.
But first the monitors have to be list-able, as HDMI-1 and HDMI-2
or whatever.
https://wiki.archlinux.org/title/Xrandr
On Fri, 9/26/2025 5:59 PM, Paul wrote:
If the monitors are really there, an XRandR command should be able
to make the monitors do things.
But first the monitors have to be list-able, as HDMI-1 and HDMI-2
or whatever.
https://wiki.archlinux.org/title/Xrandr
And Wayland would be a different matter. (Pure Wayland needs a different tool.)
But you could be using an X11 server via XWayland compatibility interface on Wayland.
System:
Host: CHARGER Kernel: 6.8.0-84-generic arch: x86_64 bits: 64
Desktop: MATE v: 1.26.2 Distro: Linux Mint 22.2 Zara
Graphics:
Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
loaded: vmware unloaded: fbdev,modesetting,vesa dri: swrast gpu: vmwgfx
resolution: 1440x900~60Hz
bullwinkle@CHARGER:~$ xrandr --listmonitors
Monitors: 1
0: +*Virtual1 1440/381x900/238+0+0 Virtual1
Paul
On Fri, 26 Sep 2025 18:14:23 -0400
Paul <nospam@needed.invalid> wrote:
On Fri, 9/26/2025 5:59 PM, Paul wrote:xrandr --listmonitors only lists one monitor.
If the monitors are really there, an XRandR command should be able
to make the monitors do things.
But first the monitors have to be list-able, as HDMI-1 and HDMI-2
or whatever.
https://wiki.archlinux.org/title/Xrandr
And Wayland would be a different matter. (Pure Wayland needs a different tool.)
But you could be using an X11 server via XWayland compatibility interface on Wayland.
System:
Host: CHARGER Kernel: 6.8.0-84-generic arch: x86_64 bits: 64
Desktop: MATE v: 1.26.2 Distro: Linux Mint 22.2 Zara
Graphics:
Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X: >> loaded: vmware unloaded: fbdev,modesetting,vesa dri: swrast gpu: vmwgfx >> resolution: 1440x900~60Hz
bullwinkle@CHARGER:~$ xrandr --listmonitors
Monitors: 1
0: +*Virtual1 1440/381x900/238+0+0 Virtual1
Paul
Alan
On Sat, 9/27/2025 8:00 AM, pinnerite wrote:
On Fri, 26 Sep 2025 18:14:23 -0400
Paul <nospam@needed.invalid> wrote:
On Fri, 9/26/2025 5:59 PM, Paul wrote:xrandr --listmonitors only lists one monitor.
If the monitors are really there, an XRandR command should be able
to make the monitors do things.
But first the monitors have to be list-able, as HDMI-1 and HDMI-2
or whatever.
https://wiki.archlinux.org/title/Xrandr
And Wayland would be a different matter. (Pure Wayland needs a different tool.)
But you could be using an X11 server via XWayland compatibility interface on Wayland.
System:
Host: CHARGER Kernel: 6.8.0-84-generic arch: x86_64 bits: 64
Desktop: MATE v: 1.26.2 Distro: Linux Mint 22.2 Zara
Graphics:
Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X: >>> loaded: vmware unloaded: fbdev,modesetting,vesa dri: swrast gpu: vmwgfx >>> resolution: 1440x900~60Hz
bullwinkle@CHARGER:~$ xrandr --listmonitors
Monitors: 1
0: +*Virtual1 1440/381x900/238+0+0 Virtual1
Paul
Alan
This morning my main computer (this one) came up but only one screen
was working.
The graphics card has 4 sockets. One HDMI and 3 DisplayPorts. Both my
screens use HDMI, so they have adapters. I switched everything round
and found both screens worked provided they were plugged into one
particular displayport.
Checking "Display" in system settings only shows one screen.
Just before I clocked off for the night, I thought I would boot up on
the Mint 22.1 install flashdrive.
To my surprise, delight and consternation both screens came up.
Now I need to work out where the fault lies in the software?
Suggestions please. :(
Alan
On Thu, 25 Sep 2025 22:14:14 +0100
pinnerite <pinnerite@gmail.com> wrote:
This morning my main computer (this one) came up but only one screen
was working.
The graphics card has 4 sockets. One HDMI and 3 DisplayPorts. Both my
screens use HDMI, so they have adapters. I switched everything round
and found both screens worked provided they were plugged into one
particular displayport.
Checking "Display" in system settings only shows one screen.
Just before I clocked off for the night, I thought I would boot up on
the Mint 22.1 install flashdrive.
To my surprise, delight and consternation both screens came up.
Now I need to work out where the fault lies in the software?
Suggestions please. :(
Alan
By switching to the instllation kernel 6.8.8-51, the problem disappeared!
Alan
On Sat, 9/27/2025 9:59 AM, Paul wrote:
On Sat, 9/27/2025 8:00 AM, pinnerite wrote:
On Fri, 26 Sep 2025 18:14:23 -0400
Paul <nospam@needed.invalid> wrote:
On Fri, 9/26/2025 5:59 PM, Paul wrote:xrandr --listmonitors only lists one monitor.
If the monitors are really there, an XRandR command should be able
to make the monitors do things.
But first the monitors have to be list-able, as HDMI-1 and HDMI-2
or whatever.
https://wiki.archlinux.org/title/Xrandr
And Wayland would be a different matter. (Pure Wayland needs a different tool.)
But you could be using an X11 server via XWayland compatibility interface on Wayland.
System:
Host: CHARGER Kernel: 6.8.0-84-generic arch: x86_64 bits: 64
Desktop: MATE v: 1.26.2 Distro: Linux Mint 22.2 Zara
Graphics:
Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
loaded: vmware unloaded: fbdev,modesetting,vesa dri: swrast gpu: vmwgfx
resolution: 1440x900~60Hz
bullwinkle@CHARGER:~$ xrandr --listmonitors
Monitors: 1
0: +*Virtual1 1440/381x900/238+0+0 Virtual1
Paul
Alan
There is a
/var/log/gpu-manager.log
as well, shown in this one.
https://forums.linuxmint.com/viewtopic.php?t=430711
Paul
On Sat, 27 Sep 2025 10:06:39 -0400
Paul <nospam@needed.invalid> wrote:
On Sat, 9/27/2025 9:59 AM, Paul wrote:
On Sat, 9/27/2025 8:00 AM, pinnerite wrote:
On Fri, 26 Sep 2025 18:14:23 -0400
Paul <nospam@needed.invalid> wrote:
On Fri, 9/26/2025 5:59 PM, Paul wrote:xrandr --listmonitors only lists one monitor.
If the monitors are really there, an XRandR command should be able >>>> to make the monitors do things.
But first the monitors have to be list-able, as HDMI-1 and HDMI-2
or whatever.
https://wiki.archlinux.org/title/Xrandr
And Wayland would be a different matter. (Pure Wayland needs a different tool.)
But you could be using an X11 server via XWayland compatibility interface on Wayland.
System:
Host: CHARGER Kernel: 6.8.0-84-generic arch: x86_64 bits: 64
Desktop: MATE v: 1.26.2 Distro: Linux Mint 22.2 Zara
Graphics:
Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
loaded: vmware unloaded: fbdev,modesetting,vesa dri: swrast gpu: vmwgfx
resolution: 1440x900~60Hz
bullwinkle@CHARGER:~$ xrandr --listmonitors
Monitors: 1
0: +*Virtual1 1440/381x900/238+0+0 Virtual1
Paul
Alan
There is a
/var/log/gpu-manager.log
as well, shown in this one.
https://forums.linuxmint.com/viewtopic.php?t=430711
Paul
I have uninstalled and later reinstalled kernel 6.8.0-51-generic
which has brought back my second monitor.
What the other kernels didn't do was to install the kernel module
amdgpu.