No, let it disabled? I only read that, when it is enabled, it could cause an Issue like this.
what does that mean? Before i try this i have to know it,cause i dont wanna do anything wrong:
flip@flip-NUC7i7DNHE:~$ sudo update-grub
Sourcing file /etc/default/grub' Sourcing file /etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/zorin/theme.txt
Found linux image: /boot/vmlinuz-6.8.0-90-generic
Found initrd image: /boot/initrd.img-6.8.0-90-generic
Found linux image: /boot/vmlinuz-6.8.0-88-generic
Found initrd image: /boot/initrd.img-6.8.0-88-generic
Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
With that, You set up a GRUB Parameter. So, the Power Saving Feature of the Intel iGPU will be disabled.
That, you have to do after You have added the GRUB Parameter. The Command make the Change affect. Without it, it wouldn't work even when You change it.
If You should be afraid of the os-prober Waring at the End, this isn't a Problem when only Zorin is installed. This os-prober searches for other installed Systems, which would be important when You wold have a Dual-Boot System.
Leon,thank you. I installed the update and rebooted.I will see if there is a positive change in the next few sessions. I will let you know.
1 Like
Hi Leon,today I tried another monitor—a BenQ from 2023—and it was no different: slow and unpredictable “opening times.”
The problem is probably more profound.The problem probably lies deeper and is somewhere between Intel and Linux/Zorin i believe.
Perhaps you have connections to Zorin/Linux IT specialists that you can utilize.
However, only if it is not a problem for you.
Thanks Leon
Have you done a
systemd-analyze blame
When your system is booted up fully? Perhaps something there is causing a lot longer boot times than should be normal?
1 Like
21.955s fstrim.service
5.973s NetworkManager-wait-online.service
2.354s apt-daily-upgrade.service
763ms fwupd.service
622ms snapd.seeded.service
544ms snapd.service
482ms networkd-dispatcher.service
457ms dev-sda2.device
416ms dev-loop3.device
404ms dev-loop4.device
402ms dev-loop2.device
399ms dev-loop5.device
396ms dev-loop7.device
378ms dev-loop1.device
371ms dev-loop0.device
369ms dev-loop6.device
268ms accounts-daemon.service
230ms udisks2.service
175ms systemd-resolved.service
157ms power-profiles-daemon.service
150ms NetworkManager.service
146ms avahi-daemon.service
lines 1-23 175ms systemd-resolved.service
157ms power-profiles-daemon.service
150ms NetworkManager.service
146ms avahi-daemon.service
144ms bluetooth.service
144ms boot-efi.mount
142ms ModemManager.service
139ms polkit.service
133ms e2scrub_reap.service
132ms systemd-udev-trigger.service
123ms thermald.service
122ms user@1000.service
118ms switcheroo-control.service
109ms systemd-logind.service
107ms wpa_supplicant.service
107ms systemd-timesyncd.service
175ms systemd-resolved.service
157ms power-profiles-daemon.service
150ms NetworkManager.service
146ms avahi-daemon.service
144ms bluetooth.service
144ms boot-efi.mount
142ms ModemManager.service
139ms polkit.service
133ms e2scrub_reap.service
132ms systemd-udev-trigger.service
123ms thermald.service
122ms user@1000.service
118ms switcheroo-control.service
109ms systemd-logind.service
107ms wpa_supplicant.service
107ms systemd-timesyncd.service
118ms switcheroo-control.service
109ms systemd-logind.service
107ms wpa_supplicant.service
107ms systemd-timesyncd.service
91ms systemd-oomd.service
88ms keyboard-setup.service
88ms cups.service
87ms gpu-manager.service
83ms gdm.service
80ms apparmor.service
77ms systemd-journal-flush.service
76ms secureboot-db.service
74ms grub-common.service
74ms systemd-udevd.service
72ms systemd-journald.service
67ms colord.service
67ms update-notifier-download.service
57ms upower.service
50ms systemd-modules-load.service
47ms systemd-fsck@dev-disk-by\x2duuid-2A40\x2d0980.service
42ms systemd-tmpfiles-setup.service
39ms systemd-remount-fs.service
lines 31-53
...and some more...
Hi,What is and isn't needed for a smooth start?
If so, can a simple user like me make the correct settings?
From that list of bootup, it doesn't seem like the system took overly long to come up. On that boot, did the monitor still take 15 minutes to show up, or was it more like a minute that it showed up?
Hi,it takes 5 to 15 minutes.
Are there no Zorin developers here who deal with user problems?
If the startup program is so overloaded that it takes minutes for the monitor to be recognized, then it can't be left up to the user to solve the problem. The user did not set the startup program, and if you're not an IT specialist, it's almost impossible to change it without precise instructions.
By the way, I still have an old HP PC with Zorin OS 17.3 that works perfectly with my 10-year-old TV as a monitor.
I don't use it, but I always keep it up to date.
Hi Leon,today I tried another monitor—a BenQ from 2023—and it was no different: slow and unpredictable “opening times.”
The problem is probably more profound.The problem probably lies deeper and is somewhere between Intel and Linux/Zorin i believe.
As this is the Community User Forum, this delegates the ZorinGroup to focus on troubleshooting received bug reports and help requests as well as continued development of Zorin OS and ZorinGrid.
After reading your entire thread, several factors become clear:
Multiple monitors show this.
Using Different cables showed this, as well as assigning the correct port.
Another system does not show this.
And what it is showing is a clear race condition between NUC7I7DNB and i915
The system tries to get the EDID from the monitor, PLL fails to lock, and the process repeats until the race condition halts, and the message from the monitor is finally received.
Which leads to: Is Your computer BIOS out of date?
Has the BIOS been updated?
This would be your first step because most likely, this is the cause.
While in your BIOS Settings, check these three things:
- Disable Display Power Saving / Deep S4/S5 (if present)
- Set Primary Display = Auto or External
- Disable legacy video / CSM if enabled
Hi,thank you.
BIOS update: I don't know and didn't know that I had to do it?
Of course, I will follow your advice if you can describe how I can update the BIOS.
Thank you for your help.
BIOS (EFI on modern systems) is an Operating System, just as Zorin OS or Windows OS is.
It is not much of a User Interface Operating System... But it is the operating system that your computer motherboard operates on.
Zorin OS or Windows OS communicate with it, they do not govern it. They are distinct and are supposed to cooperate. But neither can order the other around.
As such, that operating system needs patches, updates just as Zorin Or Windows does.
In Zorin OS, you can communicate and check. In terminal run
sudo dmidecode -s bios-version
and also
sudo dmidecode -s bios-release-date
And relay that output here. This is to check if yours is out of date.
IF it is, we can take the next complicated step of updating it - since it is a distinct O.S., that part cannot be done through Zorin OS and must be done from Intel.
DNKBLi7v.86A.0066.2019.0710.1150
flip@flip-NUC7i7DNHE:~$ sudo dmidecode -s bios-release-date
07/10/2019
Yeah... PSR boot parameter would not likely help this.
Here is where you can find the packages you need:
https://www.asus.com/supportonly/nuc7i7dnb/helpdesk_bios
You may need to switch that to the German website.
The latest is at the top.
Background information:
This page is actually very good; it explains a lot so that you are not guessing and helps improve understanding.
Your Current BIOS edition was released before multiple Intel display firmware fixes and improved DPLL locking logic, so the issue you are having with the monitor makes a lot of sense looking at this.
Installing the BIOS Update should be as easy as:
Downloading the .bio file - transferring it to a clean USB stick
Booting the computer up with that USB stick inserted and tapping the appropriate key (Usually F7 - but this can depend on manufacturer) to pull the BIOS Update Menu up.
Selecting the .bio file from the USB stick in the menu - and confirming it.
Use this thread if you have any trouble or something is changed and does not seem to work.
This is a zip-file. Do I have to unzip it or upload like it is to the USB stick?I haven't unzipped a zip file on Zorin yet. How do I do it if necessary?
Thank you for your patience.