Acer laptop doesn't see second monitor [SOLVED]

Post by **SMG** » Sat Nov 27, 2021 6:14 pm

krauster wrote: ⤴Sat Nov 27, 2021 3:05 pmI'm noticing something. When I try to use the settings button on the rear panel of the Phillips monitor when i have it plugged in and connected to Linux that single joystick style button doesn't work correctly. When I boot to Wndows that button is working as described in the user guide for the monitor. It definitely isn't playing well with Linux. Maybe there's some sort of driver I need to install with Linux for this monitor. Its a Phillips 276E8VJSB. But I'm not seeing any linux drivers for this.

There is no Linux driver for monitors. The ports are managed by the graphics drivers. The monitor sends its EDID information to the computer and the graphic driver does the necessary interpretation.

I looked at the xrandr --verbose output again and realized it only shows the laptop screen. When I run that command on my laptop, it gives me information about all the possible connections even though I do not have an external monitor attached. There seems to be information missing. That might be why that button is not working; it seems the port is not even being seen.

Looking at the Xorg log output, it is also missing references to any external ports. Even when not used, they would show up in the Xorg log.

However, that should not cause the Nvidia driver not to load (which is what is in the gpu-manager.log).

Code: Select all

can't access /run/u-d-c-nvidia-was-loaded file
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is nvidia kernel module available? no

krauster wrote: ⤴Fri Nov 26, 2021 4:38 pmWhen I try to change to another one I get a message saying to run
Code: Select all
dpkg --configure -a
.
I tried that last night and I thought it ran and gave me the option to select the other choices but that didn't help, and today I am still getting that message to run dpgkg so I don't know what's going on there.

It is possible there is an issue related to this. We may want to start again with the Nvidia driver.

Xorg is probing both GPUs (2nd and 3rd lines), but only the Intel (card0) is being used because the Nvidia GPU is not seeing power (as per lines in the gpu-manager.log). I do not know if that is somehow related to Secure Boot or to the dpkg message.

Code: Select all

[    94.888] (II) xfree86: Adding drm device (/dev/dri/card0)
[    94.902] (--) PCI:*(0@0:2:0) 8086:9bc4:1025:143f rev 5, Mem @ 0x6012000000/16777216, 0x4000000000/268435456, I/O @ 0x00005000/64, BIOS @ 0x????????/131072
[    94.902] (--) PCI: (1@0:0:0) 10de:1f95:1025:1440 rev 161, Mem @ 0xa0000000/16777216, 0x6000000000/268435456, 0x6010000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288

What is the output of lsusb?

krauster · Post by **krauster** » Sat Nov 27, 2021 9:31 pm

Here's the output of lsusb

Code: Select all

stev@stev-Nitro-AN517-52:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing
Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 001 Device 005: ID 8087:0026 Intel Corp. 
Bus 001 Device 002: ID 17ef:6019 Lenovo Lenovo Optical USB Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The odd thing is that I did have it in a state where it was able to recognize the external monitor a while back. It was causing the problems where I needed to unplug and replug it to get it but it did show up, sometimes.

Post by **SMG** » Sat Nov 27, 2021 10:58 pm

krauster wrote: ⤴Sat Nov 27, 2021 9:31 pm Here's the output of lsusb
Code: Select all
stev@stev-Nitro-AN517-52:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing
Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 001 Device 005: ID 8087:0026 Intel Corp. 
Bus 001 Device 002: ID 17ef:6019 Lenovo Lenovo Optical USB Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The odd thing is that I did have it in a state where it was able to recognize the external monitor a while back. It was causing the problems where I needed to unplug and replug it to get it but it did show up, sometimes.

Yes, I reviewed the entire thread today and did notice that.

If you booted your laptop with the monitor attached the last time you booted the computer, please run the following in a terminal:
journalctl -b | nc termbin.com 9999
It will return with a url address that you should post in your next reply.

That command prints the journal log information of the current boot cycle and sends it to termbin. I'm hoping there might be some errors or messages which give us a clue as to what is happening.

krauster · Post by **krauster** » Sat Nov 27, 2021 11:43 pm

I can't post that output at the website because it is over the 60,000 char limit for these code posts. It's way over that. 275,023 char

Here's the link to it: https://termbin.com/mix9

krauster · Post by **krauster** » Sun Nov 28, 2021 8:45 am

I notice that the top line of the huge log says:

-- Logs begin at Mon 2021-11-15 15:13:40 EST, end at Sat 2021-11-27 22:33:15 EST. -- (actually that's new I just made with a later end time).

Maybe I want to get a log that is just from the latest boot? Although that long log may indicate where the changes to the new kernel happen and flipping back and forth between different graphics drivers. As mentioned there was a period maybe back a week ago when I was able to inconsistently get it to see the second monitor. It took replugging it in every time but it was being recognized eventually. Something I did changed that I think. Not sure if it was the BIOS, kernel or other changes. But it wasn't working well before that so I am in no worse shape really and very appreciative of the help I am getting and what i am learning.

If all else fails I'll wipe the partition as clean as possible and restart. Certainly getting it to a point where it doesn't take 1 min 45 secs from power on to login will be worth it. It used to boot in under 10 seconds it seemed.

Post by **SMG** » Sun Nov 28, 2021 12:36 pm

krauster wrote: ⤴Sun Nov 28, 2021 8:45 am I notice that the top line of the huge log says:

-- Logs begin at Mon 2021-11-15 15:13:40 EST, end at Sat 2021-11-27 22:33:15 EST. -- (actually that's new I just made with a later end time).

Maybe I want to get a log that is just from the latest boot?

The command I gave you gets the information only from the current boot cycle. Because of the size limit in termbin (which I do know about) the ending part would be cut off, but I wanted to see the startup information which happens at the beginning so it is okay that not all the information was transferred.

The line you posted above indicates the time span from which one could get logs and not the actual timespan of the specifically requested log.

krauster wrote: ⤴Sun Nov 28, 2021 8:45 amIf all else fails I'll wipe the partition as clean as possible and restart. Certainly getting it to a point where it doesn't take 1 min 45 secs from power on to login will be worth it. It used to boot in under 10 seconds it seemed.

I found the slow down. Notice the time difference between the first line and the very next line below.

Code: Select all

Nov 27 15:18:33 stev-Nitro-AN517-52 systemd[1]: systemd-rfkill.service: Succeeded.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: dev-disk-by\x2duuid-8481\x2d1F3B.device: Job dev-disk-by\x2duuid-8481\x2d1F3B.device/start timed out.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: Timed out waiting for device /dev/disk/by-uuid/8481-1F3B.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/8481-1F3B.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: Dependency failed for /boot/efi.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: Dependency failed for Local File Systems.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: Dependency failed for Clean up any mess left by 0dns-up.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: dns-clean.service: Job dns-clean.service/start failed with result 'dependency'.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: boot-efi.mount: Job boot-efi.mount/start failed with result 'dependency'.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: systemd-fsck@dev-disk-by\x2duuid-8481\x2d1F3B.service: Job systemd-fsck@dev-disk-by\x2duuid-8481\x2d1F3B.service/start failed with result 'dependency'.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: dev-disk-by\x2duuid-8481\x2d1F3B.device: Job dev-disk-by\x2duuid-8481\x2d1F3B.device/start failed with result 'timeout'.

I would have to see the output of cat /etc/fstab to get an idea of what that device might be.

krauster wrote: ⤴Sun Nov 28, 2021 8:45 amAlthough that long log may indicate where the changes to the new kernel happen and flipping back and forth between different graphics drivers. As mentioned there was a period maybe back a week ago when I was able to inconsistently get it to see the second monitor. It took replugging it in every time but it was being recognized eventually. Something I did changed that I think. Not sure if it was the BIOS, kernel or other changes.

Do you recall if you tried using the 5.11 kernel?

I found the following lines early in the log.

Code: Select all

Nov 27 15:18:27 stev-Nitro-AN517-52 kernel: acpi LNXPOWER:09: Turning OFF
Nov 27 15:18:27 stev-Nitro-AN517-52 kernel: acpi LNXPOWER:08: Turning OFF

Which might be a match for the message in gpu-manager.log which indicated it could not find power for the Nvidia GPU.

I searched on the message and found this bug report Bug 214035 - acpi_turn_off_unused_power_resources() may take down necessary hardware which sounds like it may have started in the 5.13 mainline kernel. (And does not appear to have been fixed until the 5.15 kernel). That means perhaps the 5.11 kernel might work.

I also saw the below in the log which could be why sometimes your monitor worked and sometimes it didn't? I do not know for sure.

Code: Select all

Nov 27 15:18:27 stev-Nitro-AN517-52 kernel: usb: port power management may be unreliable

These lines also indicate your system may be in RAID mode rather than ACHI. I thought that setting was something which showed in the inxi output, but I do not see reference to it in what you posted.

Code: Select all

Nov 27 15:18:27 stev-Nitro-AN517-52 kernel: ahci 0000:00:17.0: version 3.0
Nov 27 15:18:27 stev-Nitro-AN517-52 kernel: ahci 0000:00:17.0: Found 1 remapped NVMe devices.
Nov 27 15:18:27 stev-Nitro-AN517-52 kernel: ahci 0000:00:17.0: Switch your BIOS from RAID to AHCI mode to use them.
Nov 27 15:18:27 stev-Nitro-AN517-52 kernel: ahci 0000:00:17.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl RAID mode

So summary would be to check BIOS for RAID mode, try the 5.11 kernel, and provide the contents of the fstab file.

krauster · Post by **krauster** » Sun Nov 28, 2021 2:41 pm

Okay, some real progress with the 5.11.0-40 kernel.

I did get the error message asking me to run the dpkg --configure -a command ...

Code: Select all

stev@stev-Nitro-AN517-52:~$ sudo dpkg --configure -a
[sudo] password for stev:         
Setting up libxcb-dri3-0:i386 (1.14-2) ...
Setting up nvidia-dkms-470 (470.82.00-0ubuntu0.20.04.1) ...
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
Removing old nvidia-470.82.00 DKMS files...

-------- Uninstall Beginning --------
Module:  nvidia
Version: 470.82.00
Kernel:  5.13.0-21-generic (x86_64)
-------------------------------------

Status: This module version was INACTIVE for this kernel.
depmod....

DKMS: uninstall completed.

------------------------------
Deleting module version: 470.82.00
completely from the DKMS tree.
------------------------------
Done.
Loading new nvidia-470.82.00 DKMS files...
Building for 5.13.0-21-generic
Building for architecture x86_64
Building initial module for 5.13.0-21-generic
Secure Boot not enabled on this system.
Done.

nvidia.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.13.0-21-generic/kernel/drivers/char/drm/

nvidia-modeset.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.13.0-21-generic/kernel/drivers/char/drm/

nvidia-drm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.13.0-21-generic/kernel/drivers/char/drm/

nvidia-uvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.13.0-21-generic/kernel/drivers/char/drm/

nvidia-peermem.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.13.0-21-generic/kernel/drivers/char/drm/

depmod...

DKMS: install completed.
Setting up libxcb-sync1:i386 (1.14-2) ...
Setting up libllvm12:i386 (1:12.0.0-3ubuntu1~20.04.4) ...
Setting up libnvidia-encode-470:amd64 (470.82.00-0ubuntu0.20.04.1) ...
Setting up libxcb-dri2-0:i386 (1.14-2) ...
Setting up libxcb-randr0:i386 (1.14-2) ...
Setting up libx11-6:i386 (2:1.6.9-2ubuntu1.2) ...
Setting up mesa-vulkan-drivers:i386 (21.0.3-0ubuntu0.3~20.04.4) ...
Setting up libgl1-mesa-dri:i386 (21.0.3-0ubuntu0.3~20.04.4) ...
Setting up libxext6:i386 (2:1.3.4-0ubuntu1) ...
Setting up libxxf86vm1:i386 (1:1.1.4-1build1) ...
Setting up libxfixes3:i386 (1:5.0.3-2) ...
Setting up nvidia-driver-470 (470.82.00-0ubuntu0.20.04.1) ...
Setting up libnvidia-gl-470:i386 (470.82.00-0ubuntu0.20.04.1) ...
Setting up libnvidia-decode-470:i386 (470.82.00-0ubuntu0.20.04.1) ...
Setting up libglx-mesa0:i386 (21.0.3-0ubuntu0.3~20.04.4) ...
Setting up libglx0:i386 (1.3.2-1~ubuntu0.20.04.1) ...
Setting up libgl1:i386 (1.3.2-1~ubuntu0.20.04.1) ...
Setting up libnvidia-encode-470:i386 (470.82.00-0ubuntu0.20.04.1) ...
Setting up libnvidia-ifr1-470:i386 (470.82.00-0ubuntu0.20.04.1) ...
Setting up libnvidia-fbc1-470:i386 (470.82.00-0ubuntu0.20.04.1) ...
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu2) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for desktop-file-utils (0.24+linuxmint1) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for initramfs-tools (0.136ubuntu6.6) ...
update-initramfs: Generating /boot/initrd.img-5.13.0-21-generic
W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for libc-bin (2.31-0ubuntu9.2) ...
Processing triggers for man-db (2.9.1-1) ...
stev@stev-Nitro-AN517-52:~$

when I selected it to install.
But it did finish up. I did a reboot and it get this out of whack login in screen

but I can login.

Then I was finally able to see the external monitor called out in the layout window of Display but it took some messing around with it to finally get any image on to it. I can't accurately describe the process of selecting resolutions and refresh settings and other settings but I seem to have tricked it to show icons and the cursor on the external monitor. And then I was able to make it the main monitor. Everything was tiny with it set to 3840x2160 and the user interface scale settings and fractional scaling were not acting friendly and independently between the two screens. So I selected 1920x1080 and it is a good setting that works for both monitors.

I have rebooted a couple times and it seems to be holding the setting, although the login is not in the right place and scale.

Here is the output from the fstab to find what might be waiting for 1.5 minutes at boot.

Code: Select all

stev@stev-Nitro-AN517-52:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda4 during installation
UUID=0e7208d4-e8a8-480f-bd20-498ab9ae0b07 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=8481-1F3B  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0

I'll check the RAID setting in the BIOS in a bit. I remember getting pretty messed up with the original stuff I needed to do to keep Windows on one SSD and install Linux on the other SSD. It's a two SSD system that I bought used with only windows on it.

Post by **SMG** » Sun Nov 28, 2021 3:21 pm

You are not the first person I've seen who had some issues with the 5.13 kernel, but the 5.11 worked. Given the info on the bug I found, we will have to see what might be the best option for your situation once 5.11 goes end of life in February. Hopefully, there will be a fix by then and it will be backported.

krauster wrote: ⤴Sun Nov 28, 2021 2:41 pmI did a reboot and it get this out of whack login in screen

There are some adjustments which can be done for that. Check the Login Window app on the Settings tab to see which screen is the default and which HiDPI support is listed. I believe the default for both is "Auto".

krauster wrote: ⤴Sun Nov 28, 2021 2:41 pmI have rebooted a couple times and it seems to be holding the setting, although the login is not in the right place and scale.

I believe the settings in the Display app may not take place until after you log in. Check the settings in the Login Window app to see if adjustments there help.

What is the output of inxi -SMCGx and is your nvidia-prime-applet still showing it is in On-Demand mode?

krauster wrote: ⤴Sun Nov 28, 2021 2:41 pmI'll check the RAID setting in the BIOS in a bit. I remember getting pretty messed up with the original stuff I needed to do to keep Windows on one SSD and install Linux on the other SSD. It's a two SSD system that I bought used with only windows on it.

This may or may not relate to the timeout message.

From my prior post:
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: Timed out waiting for device /dev/disk/by-uuid/.8481-1F3B

which is your computer's efi partition.
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=8481-1F3B /boot/efi vfat umask=0077 0 1

Do you have separate efi partitions for Mint and Windows or are they sharing one?

krauster · Post by **krauster** » Sun Nov 28, 2021 5:17 pm

Apparently I tricked myself. When I check I see that I am actually not in the 5.11.0-40 kernel. I thought it loaded when after I completed the dpkg command and selected the kernel. I did not get an error message from selecting that kernel and I thought it said it completed the install. And I started seeing the external monitor. But it seems the 5.11 didn't load. I am using the 5.13.

Code: Select all

stev@stev-Nitro-AN517-52:~$ inxi -SMCGx
System:
  Host: stev-Nitro-AN517-52 Kernel: 5.13.0-21-generic x86_64 bits: 64 
  compiler: N/A Desktop: Cinnamon 5.0.7 Distro: Linux Mint 20.2 Uma 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: Acer product: Nitro AN517-52 v: V2.06 
  serial: <superuser/root required> 
  Mobo: CML model: Karoq_CMS v: V2.06 serial: <superuser/root required> 
  UEFI: Insyde v: 2.06 date: 08/19/2021 
CPU:
  Topology: Quad Core model: Intel Core i5-10300H bits: 64 type: MT MCP 
  arch: N/A L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 39999 
  Speed: 800 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 800 6: 869 7: 897 8: 805 
Graphics:
  Device-1: Intel UHD Graphics vendor: Acer Incorporated ALI driver: i915 
  v: kernel bus ID: 00:02.0 
  Device-2: NVIDIA vendor: Acer Incorporated ALI driver: nvidia v: 470.82.00 
  bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.11 driver: modesetting,nvidia 
  unloaded: fbdev,nouveau,vesa resolution: 1920x1080~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 21.0.3 
  direct render: Yes

as for the Login Window app, no combination of HiDPI support (Auto, Enable, Disable) and monitor (Auto, HDMI-1-0, eDP-1) makes any difference. They all put the login into the bottom left corner when I boot from a Restart.

I'll look in the BIOS and try to figure out how I have it set up next.

krauster · Post by **krauster** » Sun Nov 28, 2021 5:27 pm

another thing: I seem to not be getting the grub choice of whether to load linux or windows anymore. I wonder how that went away. Of course I change the boot order in the BIOS but I used to have the grub menu.

As mentioned I did update the BIOS in the last couple days but I thought I used grub since then, but I can't say for sure.

EDIT: I am sure I booted through grub to windows in the last day. Not sure how the grub menu has disappeared at power on.

Post by **SMG** » Sun Nov 28, 2021 5:33 pm

krauster wrote: ⤴Sun Nov 28, 2021 5:17 pm Apparently I tricked myself. When I check I see that I am actually not in the 5.11.0-40 kernel. I thought it loaded when after I completed the dpkg command and selected the kernel. I did not get an error message from selecting that kernel and I thought it said it completed the install.

That means we know it works with the 5.13 kernel.

Mint automatically boots to the highest number installed kernel. If you did not go to the grub menu, select Advanced Options, and select the 5.11 kernel, then you would boot automatically with the 5.13 kernel. The only way to boot with an older installed kernel is to go through grub's Advanced Options.

This looks good. This is what you want to see for On-Demand mode.
Graphics:
Device-1: Intel UHD Graphics vendor: Acer Incorporated ALI driver: i915
v: kernel bus ID: 00:02.0
Device-2: NVIDIA vendor: Acer Incorporated ALI driver: nvidia v: 470.82.00
bus ID: 01:00.0
Display: x11 server: X.Org 1.20.11 driver: modesetting,nvidia
unloaded: fbdev,nouveau,vesa resolution: 1920x1080~60Hz, 1920x1080~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 21.0.3
direct render: Yes

krauster wrote: ⤴Sun Nov 28, 2021 5:27 pm another thing: I seem to not be getting the grub choice of whether to load linux or windows anymore. I wonder how that went away. Of course I change the boot order in the BIOS but I used to have the grub menu.

This observation might relate to the message about the efi partition that is slowing the boot.

krauster · Post by **krauster** » Sun Nov 28, 2021 7:52 pm

Figuring things are working good enough for the two monitor setup I'd like to figure out the RAID and EFI partition stuff. Do I change it from the BIOS? I don't see how to do that. I see this:

and it mentions Optain with RAID.
But I don't see any options for that here:

Or here:

I am searching around and trying to find info about changing RAID in the BIOS and I don't see much specific to the Acer BIOS. Is the changes I need to do done in the BIOS or is it done in Linux?

Post by **SMG** » Sun Nov 28, 2021 9:30 pm

krauster wrote: ⤴Sun Nov 28, 2021 7:52 pm Figuring things are working good enough for the two monitor setup I'd like to figure out the RAID and EFI partition stuff. Do I change it from the BIOS?

It is my understanding the RAID stuff is set in BIOS/UEFI.

The EFI partition is something that is set up on the disk, usually during install and relates to grub.

These are really separate questions from your original question and not ones I normally help troubleshoot. I suggest you create new topics for them in the Installation & Boot section of the forum.

krauster · Post by **krauster** » Sun Nov 28, 2021 9:55 pm

I understand. And very much appreciate the very patient help you've given me regarding this external monitor hookup. It is working for now. I'm still confused why it was working at one point, then wasn't, and then now is, as it doesn't seem to be the kernel. I've learned some good stuff from this exchange but can't say that I understand enough to trouble shoot it on my own now (not in the least), but it has been interesting the whole way. Thank you. I don't know if I should mark this [SOLVED]?

I will look into the boot issues by researching Installation and Boot subforum and maybe open another topic of the RAID and the problems. It's interesting what you saw using journalctl to see the 1.5min timeout:

dev-disk-by\x2duuid-8481\x2d1F3B.device: Job dev-disk-by\x2duuid-8481\x2d1F3B.device/start timed out.

Can you explain what you think this might be or should I ask this question in "Installation and Boot"?

Post by **SMG** » Sun Nov 28, 2021 10:25 pm

krauster wrote: ⤴Sun Nov 28, 2021 9:55 pm I understand. And very much appreciate the very patient help you've given me regarding this external monitor hookup. It is working for now. I'm still confused why it was working at one point, then wasn't, and then now is, as it doesn't seem to be the kernel. I've learned some good stuff from this exchange but can't say that I understand enough to trouble shoot it on my own now (not in the least), but it has been interesting the whole way. Thank you. I don't know if I should mark this [SOLVED]?

I think getting the Nvidia driver re-installed fixed the issue. Something wasn't quite right in what/how the modules built.

It is your topic, so it is up to you if you want to mark it SOLVED, or give it some more time to take care of the other issues to make sure the graphics are working properly.

krauster wrote: ⤴Sun Nov 28, 2021 9:55 pm I will look into the boot issues by researching Installation and Boot subforum and maybe open another topic of the RAID and the problems. It's interesting what you saw using journalctl to see the 1.5min timeout:

dev-disk-by\x2duuid-8481\x2d1F3B.device: Job dev-disk-by\x2duuid-8481\x2d1F3B.device/start timed out.

Can you explain what you think this might be or should I ask this question in "Installation and Boot"?

I would suggest posting that entire section of messages and then also post the output of fstab. So include both of the below and mention that grub is no longer showing when it had in the past.

Code: Select all

Nov 27 15:18:33 stev-Nitro-AN517-52 systemd[1]: systemd-rfkill.service: Succeeded.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: dev-disk-by\x2duuid-8481\x2d1F3B.device: Job dev-disk-by\x2duuid-8481\x2d1F3B.device/start timed out.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: Timed out waiting for device /dev/disk/by-uuid/8481-1F3B.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/8481-1F3B.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: Dependency failed for /boot/efi.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: Dependency failed for Local File Systems.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: Dependency failed for Clean up any mess left by 0dns-up.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: dns-clean.service: Job dns-clean.service/start failed with result 'dependency'.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: boot-efi.mount: Job boot-efi.mount/start failed with result 'dependency'.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: systemd-fsck@dev-disk-by\x2duuid-8481\x2d1F3B.service: Job systemd-fsck@dev-disk-by\x2duuid-8481\x2d1F3B.service/start failed with result 'dependency'.
Nov 27 15:19:57 stev-Nitro-AN517-52 systemd[1]: dev-disk-by\x2duuid-8481\x2d1F3B.device: Job dev-disk-by\x2duuid-8481\x2d1F3B.device/start failed with result 'timeout'.

Code: Select all

stev@stev-Nitro-AN517-52:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda4 during installation
UUID=0e7208d4-e8a8-480f-bd20-498ab9ae0b07 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=8481-1F3B  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0

And then for the RAID issue, ask what the following might mean. Maybe a remapped device is not an issue? It just sounded odd to me.

Code: Select all

Nov 27 15:18:27 stev-Nitro-AN517-52 kernel: ahci 0000:00:17.0: version 3.0
Nov 27 15:18:27 stev-Nitro-AN517-52 kernel: ahci 0000:00:17.0: Found 1 remapped NVMe devices.
Nov 27 15:18:27 stev-Nitro-AN517-52 kernel: ahci 0000:00:17.0: Switch your BIOS from RAID to AHCI mode to use them.
Nov 27 15:18:27 stev-Nitro-AN517-52 kernel: ahci 0000:00:17.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl RAID mode

krauster · Post by **krauster** » Mon Nov 29, 2021 8:42 am

If it was the nvidia drivers getting reinstalled, would that happen from dpkg command? or from installing the 5.11 kernel, even though it is running the 5.13 kernel? Knowing very little I'd assume the nvidia drivers are not within the downloaded and installed 5.11 kernel.

As for marking this topic solved I'll wait a few weeks and do so if I don't see the second monitor problem recur. It's working well upon reboots at the moment. (except for the position of the login, which the login window app doesn't seem to change.... I'll take more time with that but have tried about all combos and will do some reading on my own about that.)

And I'll post the other issues in Boot and Installation.

Post by **SMG** » Mon Nov 29, 2021 9:51 am

krauster wrote: ⤴Mon Nov 29, 2021 8:42 am If it was the nvidia drivers getting reinstalled, would that happen from dpkg command? or from installing the 5.11 kernel, even though it is running the 5.13 kernel? Knowing very little I'd assume the nvidia drivers are not within the downloaded and installed 5.11 kernel.

The Nvidia driver is proprietary so it can not be included in the kernel. It is separate. However, the Nvidia driver works with the kernel and rebuilds itself each time a new kernel is installed. From the output you provided above, we can see it built its modules with the 5.13 kernel Mint was using at the time. I pulled out parts of the output from above so you can see where it mentions the building for the 5.13.0-21 kernel.

Code: Select all

------------------------------
Deleting module version: 470.82.00
completely from the DKMS tree.
------------------------------
Done.
Loading new nvidia-470.82.00 DKMS files...
Building for 5.13.0-21-generic
Building for architecture x86_64
Building initial module for 5.13.0-21-generic
Secure Boot not enabled on this system.
Done.

nvidia.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.13.0-21-generic/kernel/drivers/char/drm/

nvidia-modeset.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.13.0-21-generic/kernel/drivers/char/drm/

nvidia-drm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.13.0-21-generic/kernel/drivers/char/drm/

nvidia-uvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.13.0-21-generic/kernel/drivers/char/drm/

nvidia-peermem.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.13.0-21-generic/kernel/drivers/char/drm/

krauster wrote: ⤴Mon Nov 29, 2021 8:42 am It's working well upon reboots at the moment. (except for the position of the login, which the login window app doesn't seem to change....

See if this [TUTORIAL] Make Log in Screen (LightDM) use same Display Properties as When Logged in helps.

krauster · Post by **krauster** » Mon Nov 29, 2021 8:52 pm

See if this [TUTORIAL] Make Log in Screen (LightDM) use same Display Properties as When Logged in helps.

Did it. Thanks. It worked. I have the login screen showing up on the laptop and now in a good place at a good scale.

krauster · Post by **krauster** » Sat Dec 04, 2021 9:14 am

Another thing to report after switching the BIOS SATA setting from "optain with RAID" to "AHCI" covered in the other topic:
viewtopic.php?f=46&t=362326

Prior to AHCI we were seeing this broken window when I clicked on the nvidia icon in the tool tray:

: ksnip_20211126-151002.png (39.68 KiB) Viewed 2517 times

Now with AHCI I see this, which I assume means its working correctly:

Post by **SMG** » Sat Dec 04, 2021 10:39 am

krauster wrote: ⤴Sat Dec 04, 2021 9:14 amNow with AHCI I see this, which I assume means its working correctly:
2021-12-04_08-03.png

That looks correct.

I would expect you also have an nvidia-prime-applet in your tray which is a Mint applet. It may be showing an Intel logo for your On-Demand setting.

Linux Mint Forums

Acer laptop doesn't see second monitor [SOLVED]

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor

Re: Acer laptop doesn't see second monitor