[SOLVED]Every boot the resolution is wrong and monitor not recognized

seth · 2023-09-11 12:59:43

It's there, you could add it to GRUB_CMDLINE_LINUX_DEFAULT, but that should™ not matter.
How do you generate the grub.cfg
Are you multi-booting (and is maybe the other OS writing grub.cfg as well?)

pepper · 2023-09-11 14:41:39

Added in GRUB_CMDLINE_LINUX_DEFAULT but it seems nothing changed. In this computer I have only archlinux, only 1 bootable ssd where I only installed archlinux, I don't use multi-booting.

I installed grub in this way the first time (>1 year ago)

grub-install --target=x86_64-efi --efi-directory=/boot –bootloader-id=GRUB --removable

and I generate config with this command

grub-mkconfig -o /boot/grub/grub.cfg

I have only 1 fat partition for /boot/ and 1 main partition with LVM+LUKS for the full system (no other partitions).
Maybe could I manually remove the additional monitor None-1-1? (I don't know if the monitor is generated again every time or it's just randomly "selected" at boot)

Last edited by pepper (2023-09-11 14:58:40)

seth · 2023-09-11 15:08:13

Maybe could I manually remove the additional monitor None-1-1?

You should focus on why your grub.cfg isn't properly written - that's a MUCH bigger problem and once you've nvidia-drm.modeset=1 in there, the ghost monitor will be gone.

Does grub-mkconfig issue any errors?
What's the output of

sudo grub-mkconfig | grep nvidia

?

pepper · 2023-09-11 15:40:49

➜  ~ sudo grub-mkconfig -o /boot/grub/grub.cfg  
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-lts-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
done

it seems there isn't any error

➜  ~ sudo grub-mkconfig | grep nvidia
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
	linux	/vmlinuz-linux-zen root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
		linux	/vmlinuz-linux-zen root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-zen-fallback.img
		linux	/vmlinuz-linux-zen root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-lts.img
		linux	/vmlinuz-linux-lts root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-lts-fallback.img
		linux	/vmlinuz-linux-lts root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
		linux	/vmlinuz-linux root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-fallback.img
		linux	/vmlinuz-linux root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
done

If it's useful: I used grub-editor in the past (months ago) but only to set the "previously booted entry" option (screenshot https://i.imgur.com/PtnsDXJ.png), and the waiting seconds from 10s to 5s, nothing more.

Last edited by pepper (2023-09-11 18:32:07)

seth · 2023-09-11 18:57:01

grub-mkconfig certainly adds the parameter, are you suggesting

sudo grep nvidia /boot/grub/grub.cfg

doesn't show it??

pepper · 2023-09-12 08:11:45

➜  ~ sudo grep nvidia /boot/grub/grub.cfg
linux	/vmlinuz-linux-zen root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
linux	/vmlinuz-linux-zen root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
linux	/vmlinuz-linux-zen root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
linux	/vmlinuz-linux-lts root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
linux	/vmlinuz-linux-lts root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
linux	/vmlinuz-linux root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
linux	/vmlinuz-linux root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1

Last edited by pepper (2023-09-12 08:12:14)

seth · 2023-09-12 08:18:33

Well, it's in there - twice.
Reboot, re-check the grub.cfg and "cat /proc/cmdline"

pepper · 2023-09-13 06:19:20

rebooted, and:

➜  ~ sudo grep nvidia /boot/grub/grub.cfg
linux	/vmlinuz-linux-zen root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
linux	/vmlinuz-linux-zen root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
linux	/vmlinuz-linux-zen root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
linux	/vmlinuz-linux-lts root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
linux	/vmlinuz-linux-lts root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
linux	/vmlinuz-linux root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1
linux	/vmlinuz-linux root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1

➜  ~ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux-zen root=/dev/mapper/volgroup0-lv_root rw cryptdevice=UUID=49bb1478-8b71-49fb-9386-cccc6a65b04c:encrypted_lvm root=/dev/volgroup0/lv_root nvidia-drm.modeset=1 loglevel=3 quiet nvidia-drm.modeset=1

seth · 2023-09-13 07:18:44

And is the simpledrm device gone?

pepper · 2023-09-13 11:29:42

oh wow, I checked the monitor settings and the ghost monitor is not there anymore, the cause can only be the kernel flag because I didn't do other updates..
I hope it will not appear again

https://i.imgur.com/h0Q1sAY.png

moderator edit -- replaced oversized image with link.
Pasting pictures and code

Last edited by 2ManyDogs (2023-09-13 11:35:33)

seth · 2023-09-13 11:36:47

I hope it will not appear again

Not as long as you can keep the module parameter in place.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

pepper · 2023-09-13 11:52:32

thank you for all your time and support

Arch Linux

#26 2023-09-11 12:59:43

Re: [SOLVED]Every boot the resolution is wrong and monitor not recognized

#27 2023-09-11 14:41:39

Re: [SOLVED]Every boot the resolution is wrong and monitor not recognized

#28 2023-09-11 15:08:13

Re: [SOLVED]Every boot the resolution is wrong and monitor not recognized

#29 2023-09-11 15:40:49

Re: [SOLVED]Every boot the resolution is wrong and monitor not recognized

#30 2023-09-11 18:57:01

Re: [SOLVED]Every boot the resolution is wrong and monitor not recognized

#31 2023-09-12 08:11:45

Re: [SOLVED]Every boot the resolution is wrong and monitor not recognized

#32 2023-09-12 08:18:33

Re: [SOLVED]Every boot the resolution is wrong and monitor not recognized

#33 2023-09-13 06:19:20

Re: [SOLVED]Every boot the resolution is wrong and monitor not recognized

#34 2023-09-13 07:18:44

Re: [SOLVED]Every boot the resolution is wrong and monitor not recognized

#35 2023-09-13 11:29:42

Re: [SOLVED]Every boot the resolution is wrong and monitor not recognized

#36 2023-09-13 11:36:47

Re: [SOLVED]Every boot the resolution is wrong and monitor not recognized

#37 2023-09-13 11:52:32

Re: [SOLVED]Every boot the resolution is wrong and monitor not recognized

Board footer