This is the output after booting (not working):
Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 16384 x 16384
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm
2560x1440 59.95*+
1920x1200 59.88
1920x1080 60.00 50.00 59.94
1680x1050 59.95
1600x900 60.00
1280x1024 75.02 60.02
1440x900 59.89
1280x720 60.00 50.00 59.94
1024x768 75.03 60.00
800x600 75.00 60.32
720x576 50.00
720x480 60.00 59.94
640x480 75.00 60.00 59.94
720x400 70.08
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
This is the output, after I replugged the second monitor (working):
Screen 0: minimum 320 x 200, current 3640 x 1920, maximum 16384 x 16384
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 connected primary 2560x1440+0+337 (normal left inverted right x axis y axis) 597mm x 336mm
2560x1440 59.95*+
1920x1200 59.88
1920x1080 60.00 50.00 59.94
1680x1050 59.95
1600x900 60.00
1280x1024 75.02 60.02
1440x900 59.89
1280x720 60.00 50.00 59.94
1024x768 75.03 60.00
800x600 75.00 60.32
720x576 50.00
720x480 60.00 59.94
640x480 75.00 60.00 59.94
720x400 70.08
DisplayPort-2 connected 1080x1920+2560+0 right (normal left inverted right x axis y axis) 598mm x 336mm
1920x1080 60.00*+ 50.00 59.94
1680x1050 59.88
1600x900 60.00
1280x1024 75.02 60.02
1440x900 59.90
1280x800 59.91
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
720x576 50.00
720x480 60.00 59.94
640x480 75.00 72.81 66.67 60.00 59.94
720x400 70.08
Today after locking and unlocking the screen it kept working.
I know the cables could be expensive, and you may not have another around, but have you tried using a different cable?
Check the cable you connect to your second monitor for breaks, creases and attempt to switch it with the first monitor cable.
This really sounds like a wiring issue. Where bumping the table shifts the cable just enough to be detected/undetected.
I was sure to have this confirmed to myself and tried the following a few minutes ago:
- Booting to Zorin: Second screen not recognized.
- Booting to Windows (no cables touched): Second screen is recognized.
- Booting to Zorin: Second screen not recognized.
- Booting to Windows (no cables touched): Second screen is recognized.
- Booting to Zorin: Second screen not recognized.
- Switched to another cable: Second screen is recognized.
- Booting to Zorin: Second screen not recognized.
- Switched to a third cable while shut down: Second screen not recognized.
IMHO this rules out any issue with the cable, because windows (on the same hardware) has no problems and different cables only help so much when replugged.
I don't think it's a ZORIN specific issue, as my Windows-Laptop behaves exactly the same. TBH I'm surprised my desktop running windows doesn't have this problem.
I'm open for any suggestions. I'll try some other distros from a USB-drive this weekend and try to contact the screen manufacturer too.
1 Like
This makes me wonder if the Monitor power draw is too high for the notebook computers.
In case of the notebook (or the desktop) no power should be drawn.
The main monitor (fujitsu) has a (for my understanding strong) power supply and is able to charge the notebook.
1 Like
Yes, I crossed topics,here, sorry. I was just reading about Tablet Monitors and my brain did not catch up with reality before I posted.
I've heard back from the displays manufacturer: In his word no linux-distro are ever to be supported by fujistu.
He gave me the tip to try to accomplish the following windows-settings:
- Öffnen Sie die Systemsteuerung
- Suchen Sie nach Energieoptionen
- Energiesparplaneinstellungen ändern
- Erweiterte Energieeinstellungen ändern
- Erweitern Sie den Reiter PCI Express
- Erweitern Sie Link State Power management
- Wählen Sie sowohl unter Akku und Netzbetrieb – Aus
- Klicken Sie übernehmen
Roughly translated to:
1st Open system control panel
2nd Search for energy options
3rd Change plan settings
4th Change advanced power settings
5th Expand tab PCI Express
6th Expand tab Link State Power management
7th Choose Off
8th Click Apply
Does anyone know if there are similar PCIe power settings in ZORIN OS or any kind of Linux?
Actually, there is such an application, though it doesn't come with Zorin OOB. Tlp is what you need to make these modifications. Directions to install it are here.
Be careful in what you change.
2 Likes
I could install tlp and tlp-rdw via apt-get, but it didn't finde tlpui.
But I found it in the Zorin Software Store.
The required setting as far as I can tell would be in the tab PCIe:
PCIE_ASPM_ON_AC set to "off", as I couldn't find "off" I guess "performance" has to be the right one.
I also set PCIE_ASPM_ON_BAT to "off"
I'm gonna report back if this solved it.
EDIT: This didn't help!
I checked my BIOS too and the PICE ASPM level is set to disabled there as well.
This was the only software that I'm aware of that modified these settings. You may be able to manually change it, though I'm not aware of what available options are for that setting.
Performance would assign the PCIe preference and more voltage, keeping it active more. If conservative or on-demand are options, you may want to choose one of them.
I will see if I can find a solution for this, but I warn not to expect one, as not all Linux issues have resolutions until kernel updates allow for them.
Edit: i understand now, my mistake. You don't want to disable power for a PCIe slot, you don't want it to be managed or shut off.
You can disable gnome's automatic power saving. There may be a way to disable power saving globally in tlp as well.
Forgive my mistake.
According to 20.04 - Disabling Power Saving features via command line - Ask Ubuntu, you can disable auto suspend (which may help) with the following:
To disable automatic suspend:
gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'
gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend'
I'm not sure if that was a shot in the right direction but neverteless tried to disable automatic suspend.
Unfortunately it didn't work.
Edit: I'm starting to question the setting the Fujitsu-dude told me.
Neither the windows-notebook he was talking about nor my PC use a discrete GPU.
Maybe I'm to tired right now, but does setting PCIe power management even affect integrted graphics?
Integrated graphics are a part of the cpu, meaning it doesn't require a high speed path to the processor, as it is a part of it. That is the point of PCIe. Direct, fast, path directly to the processor.
If anything, you would want to disable power management of the processor, or set it to performance.
After many e-mails back and forth between FUJITSU, SAMSUNG and GIGABYTE it seems like the DP to HDMI adapter is the problem.
Just to conclude:
Setup A: Desktop PC Win 10 - DP <-> DP - FUJITSU Monitor - DP <-> DP-HDMI-Converter <-> HDMI SAMSUNG Monitor --> flawless
Setup B: Desktop PC Zorin/Ubunutu/Mint - DP <-> DP - FUJITSU Monitor - DP <-> DP-HDMI-Converter <-> HDMI SAMSUNG Monitor --> only working after un- and replugging
Setup C: DELL Notebook Win 10 - DP <-> DP - FUJITSU Monitor - DP <-> DP-HDMI-Converter <-> HDMI SAMSUNG Monitor --> only working after un- and replugging
Setup D: Desktop PC Zorin/Ubunutu/Mint - DP <-> DP - FUJITSU Monitor - DP <-> DP DELL Monitor --> flawless
Setup E: DELL Notebook Win 10 - DP <-> DP - FUJITSU Monitor - DP <-> DP DELL Monitor --> flawless
It seems like the DP-HDMI converter is only working with my Windows-Desktop system but I have no clue why this cloud be.
Another possiblity could (?) be to un- and replug the SAMSUNG Monitor in Software. Does anybody have a idea how I cloud do this in Zorin?
A converter is a separately produced and independent component by a manufacturer. That manufacturer likely only flashed the converter device with Windows OS drivers. This is not unusual.
I ran into similar issues with a converter from HDMI to DP and I solved it by buying a normal Display Port Cable. In another circumstance, I purchased a Linux Compatible HDMI to DP cable on Amazon and that one worked properly.
You can use lshw to list your hardware, if the monitors are detected, you can get their IDs and block/unblock them. They will be listed as /dev/ and then whatever the id is.
lshw only gives me my display controller:
*-display
Beschreibung: VGA compatible controller
Produkt: Renoir
Hersteller: Advanced Micro Devices, Inc. [AMD/ATI]
Physische ID: 0
Bus-Informationen: pci@0000:05:00.0
Version: d9
Breite: 64 bits
Takt: 33MHz
Fähigkeiten: pm pciexpress msi msix vga_controller bus_master cap_list rom
Konfiguration: driver=amdgpu latency=0
Ressourcen: irq:29 memory:d0000000-dfffffff memory:e0000000-e01fffff ioport:e000(Größe=256) memory:fcc00000-fcc7ffff memory:c0000-dffff
even wiht xrandr I only see the working monitor:
DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm
2560x1440 59.95*+
1920x1200 59.88
1920x1080 60.00 50.00 59.94
1680x1050 59.95
1600x900 60.00
1280x1024 75.02 60.02
1440x900 59.89
1280x720 60.00 50.00 59.94
1024x768 75.03 60.00
800x600 75.00 60.32
720x576 50.00
720x480 60.00 59.94
640x480 75.00 60.00 59.94
720x400 70.08
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
@Aravisian
I didn't even know these things require drivers.
I'd clearly prefer to just use a DP-DP cable but my secondary monitor only supports HDMI or VGA input.
Do you maybe happen to rember wich linux compatible DP->HDMI cable you bought?
I will try searching Amazon history - but it was quite a while ago and a bunch of Christmas shopping has happened since...
Almost all hardware comes with its own Operating System.
While many Operating Systems are quite basic and simple, they are still self-regulated.
Your Computer has its own - BIOS. Your user interface Operating System, be it Zorin OS or Windows OS, must communicate with the BIOS Operating System rather than govern it.
Your GPU has its own operating system, as do network cards, etc.
Drivers are used as a communication protocol to talk to these self-regulated devices.
Programming - or installing - the Operating System onto a hardware device is commonly called "flashing" the device.
Hello everyone.
I'm just trying to ak again if anyone has any idea how to solve this.
My main staring points are still:
1st Trying to make the secondary display work as if it had a real DisplayPort port (any kind of converter)
@Aravisian: Did you happen to find the adapter you used?
2nd "Unplugging and replugging" the secondary display without phisically touching it.
Yes, sorry had to ask my son - it is just labeled Amazon Basics. 
1 Like