fstab causing my left monitor to not be detected

whicc · 2025-03-17 19:11:17

Hello all! I recently swapped over from running Windows and Manjaro to just Arch, and I've spent most of the day getting everything set up and configured. My machine has multiple drives, which I partitioned for ext4, and I have now been attempting to mount. I was able to mount them with the mount command, but when adding them to my fstab and rebooting, my second monitor stopped working entirely. This also caused hyprland to hang and eventually crash, but i3 still worked. I am totally stumped as to why anything with fstab would cause this, but thankfully I saved a backup of my previous (and completely working) fstab file. I've attached the info I think would be relevant, but if there is anything missing, just let me know and I'll send it in as well.

Current normally working fstab file:

# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p3
UUID=3804da10-120c-4bac-b4d4-9553838e3fc2	/         	ext4      	rw,relatime	0 1
# /dev/nvme0n1p1
UUID=2E87-A6FB      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2
# /dev/nvme0n1p2
UUID=4a88ad41-d3e2-4bf2-bf59-784a1d807855	none      	swap      	defaults  	0 0

Broken fstab file:

# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p3
UUID=3804da10-120c-4bac-b4d4-9553838e3fc2	/         	ext4      	rw,relatime	0 1
# /dev/nvme0n1p1
UUID=2E87-A6FB      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2
# /dev/nvme0n1p2
UUID=4a88ad41-d3e2-4bf2-bf59-784a1d807855	none      	swap      	defaults  	0 0
# /dev/sda1
UUID=5d344cfe-bca0-4d37-ba8b-523aa97d1288 /mnt/drive1 ext4 defaults 0 0
# /dev/sdb1
UUID=eb573e11-537b-49f6-96ed-808207094e57 /mnt/drive2 ext4 defaults 0 0
# /dev/sdc1
UUID=abd84061-0eb9-4e1a-b401-184dc1dc08cd /mnt/drive3 ext4 defaults 0 0
# /dev/nvme1n1p1
UUID=e5a2a446-21e0-4723-8031-f3e5ff2609eb /mnt/drive4 ext4 defaults 0 0

lsblk -f results:

sda                                                                                
└─sda1      ext4   1.0         5d344cfe-bca0-4d37-ba8b-523aa97d1288                
sdb                                                                                
└─sdb1      ext4   1.0         eb573e11-537b-49f6-96ed-808207094e57                
sdc                                                                                
└─sdc1      ext4   1.0         abd84061-0eb9-4e1a-b401-184dc1dc08cd                
nvme0n1                                                                            
├─nvme0n1p1 vfat   FAT32       2E87-A6FB                             830.3M    19% /boot
├─nvme0n1p2 swap   1           4a88ad41-d3e2-4bf2-bf59-784a1d807855                [SWAP]
└─nvme0n1p3 ext4   1.0         3804da10-120c-4bac-b4d4-9553838e3fc2  841.7G     1% /
nvme1n1                                                                            
└─nvme1n1p1 ext4   1.0         e5a2a446-21e0-4723-8031-f3e5ff2609eb

Any ideas or help with this would be greatly appreciated. I'm glad I made a backup of my fstab before trying all this. I have the feeling it's some small issue with my formatting that made it act up.

whicc · 2025-03-17 19:12:14

I should also mention I did make sure to create those directories in /mnt before doing all of this.

seth · 2025-03-17 21:54:41

race condition?
Try "noauto,x-systemd.automount" (mounts the drive on access only) and compare the system journals for the good and bad fstab (notably what actually makes hyprland crash and what kind of GPU it runs on, notably if this is a hybrid system) - it's it's a race condition, you want to take control of that situation anyway, not fumble w/ boot delays.

whicc · 2025-03-17 23:24:22

after setting up my fstab this way i was able to boot in with no trouble, and automount did work correctly. i'm still not entirely sure as to why hyprland crashed, as it looks almost like hyprpaper was the one causing issues. going through my journal, i found the boot where things went crazy, and there seemed to be no issues with mounting the drives. my next guess is something to do with nvidia drm? the only errors i saw were for fnott, but those came through well after boot anyways, when the problem with the monitor was starting. i will keep looking through, but for the time being you got my pc booting correctly, and with access to my storage. thank you!

kermit63 · 2025-03-17 23:29:27

If you're interested in pursuing this, you should post the journal in its entirety and have seth take a look at it. He eats journals for breakfast.

Check out the first link in seth's sig if the file is too large.

whicc · 2025-03-18 02:01:20

Here you go!

This was the boot with the fstab changes that led to the monitor issues: https://0x0.st/8Qd5.txt
This was the boot right before: https://0x0.st/8QdR.txt
And this is most recent, with the changes seth suggested: https://0x0.st/8Qd7.txt

seth · 2025-03-18 07:03:38

You only installed SDDM in the boot before the problem emerged?

Mar 17 13:14:19 archbox sudo[2985]:    james : TTY=pts/0 ; PWD=/home/james/.config/hypr ; USER=root ; COMMAND=/usr/bin/pacman -S sddm
Mar 17 13:15:15 archbox sudo[3084]:    james : TTY=pts/0 ; PWD=/home/james/.config/hypr ; USER=root ; COMMAND=/usr/bin/systemctl enable sddm.service
Mar 17 13:15:15 archbox sudo[3136]:    james : TTY=pts/0 ; PWD=/home/james/.config/hypr ; USER=root ; COMMAND=/usr/bin/systemctl start sddm.service

Bad:

Mar 17 13:55:48 archbox kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=3804da10-120c-4bac-b4d4-9553838e3fc2 rw loglevel=3 quiet
Mar 17 13:55:49 archbox kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
Mar 17 13:55:49 archbox kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
Mar 17 13:55:49 archbox kernel: EXT4-fs (nvme0n1p3): re-mounted 3804da10-120c-4bac-b4d4-9553838e3fc2 r/w. Quota mode: none.
Mar 17 13:55:49 archbox systemd[1]: Finished Remount Root and Kernel File Systems.
Mar 17 13:55:49 archbox kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  570.124.04  Release Build  (archlinux-builder@)  
Mar 17 13:55:51 archbox sddm[676]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_CaLzjC -noreset -displayfd 16
Mar 17 13:56:04 archbox sddm[676]: Session "/usr/share/wayland-sessions/hyprland.desktop" selected, command: "Hyprland" for VT 1
Mar 17 14:37:56 archbox sudo[7449]:    james : TTY=pts/0 ; PWD=/mnt ; USER=root ; COMMAND=/usr/bin/mkdir drive1
Mar 17 14:38:21 archbox kernel: EXT4-fs (sda1): mounted filesystem 5d344cfe-bca0-4d37-ba8b-523aa97d1288 r/w with ordered data mode. Quota mode: none.
Mar 17 14:38:47 archbox kernel: EXT4-fs (sdb1): mounted filesystem eb573e11-537b-49f6-96ed-808207094e57 r/w with ordered data mode. Quota mode: none.
Mar 17 14:39:10 archbox kernel: EXT4-fs (sdc1): mounted filesystem abd84061-0eb9-4e1a-b401-184dc1dc08cd r/w with ordered data mode. Quota mode: none.

Lazy mount:

Mar 17 18:48:28 archbox kernel: Linux version 6.13.7-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1 20250207, GNU ld (GNU Binutils) 2.44) #1 SMP PREEMPT_DYNAMIC Thu, 13 Mar 2025 18:12:00 +0000
Mar 17 18:48:28 archbox kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
Mar 17 18:48:29 archbox systemd[1]: Finished Remount Root and Kernel File Systems.
Mar 17 18:48:29 archbox kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  570.124.04  Release Build  (archlinux-builder@)  
Mar 17 18:48:31 archbox sddm[679]: Initializing...
Mar 17 18:48:41 archbox sddm[679]: Session "/usr/share/wayland-sessions/hyprland.desktop" selected, command: "Hyprland" for VT 1

There's not much difference, the nvidia modules load late, SDDM starts on X11 ~2s afterwards and you log into hyprland manually.
But the supposedly "bad" boot also has only manual mounts of those drives fairly late, the mountpoints are at least attempted to be created (and the system reboots ~6 minutes later)
Sure it's the right one and not the one that included the changes leading to the issue in the subsequent boot?

whicc · 2025-03-18 15:20:12

Good eye! That was definitely the session where I mounted the drives myself and made my fstab changes. This is the boot immediately after, and it does look like the correct one (I think so at least). There are a load of nvidia drm errors near the end, which I think would be the culprit, but I'm not sure what would have caused them still.
https://0x0.st/8QFF.txt

seth · 2025-03-18 22:04:23

Mar 17 14:45:51 archbox kernel: nvidia: loading out-of-tree module taints kernel.
Mar 17 14:45:51 archbox systemd[1]: Mounting /mnt/drive1...
Mar 17 14:45:53 archbox systemd[1]: Mounted /mnt/drive3.
Mar 17 14:45:54 archbox sddm[696]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_uyuSVL -noreset -displayfd 16
Mar 17 14:46:09 archbox sddm-helper[740]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "Hyprland"
Mar 17 14:46:25 archbox kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000b00] Flip event timeout on head 1
Mar 17 14:46:29 archbox kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000b00] Failed to apply atomic modeset.  Error code: -22
Mar 17 14:46:35 archbox kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000b00] Flip event timeout on head 1
Mar 17 14:46:39 archbox kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000b00] Failed to apply atomic modeset.  Error code: -22
Mar 17 14:46:42 archbox kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000b00] Flip event timeout on head 1
Mar 17 14:46:45 archbox kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000b00] Flip event timeout on head 1

The mounts do seem to stall the boot a bit and get the nvidia initalization marginally closer to the SDDM start, but it takes another 15s before hyprland starts and and 15s more before nvidia logs flipping errors.
Yet

Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: Loading qrc:/theme/Main.qml...
Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: file:///usr/lib/qt6/qml/SddmComponents/LayoutBox.qml:35:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: file:///usr/lib/qt6/qml/SddmComponents/ComboBox.qml:105:9: QML Image: Cannot open: file:///usr/lib/qt6/qml/SddmComponents/angle-down.png
Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: file:///usr/lib/qt6/qml/SddmComponents/ComboBox.qml:105:9: QML Image: Cannot open: file:///usr/lib/qt6/qml/SddmComponents/angle-down.png
Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: qrc:/theme/Main.qml:41:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: Adding view for "DP-2" QRect(0,0 2560x1440)
Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: Loading qrc:/theme/Main.qml...
Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: file:///usr/lib/qt6/qml/SddmComponents/LayoutBox.qml:35:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: file:///usr/lib/qt6/qml/SddmComponents/ComboBox.qml:105:9: QML Image: Cannot open: file:///usr/lib/qt6/qml/SddmComponents/angle-down.png
Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: file:///usr/lib/qt6/qml/SddmComponents/ComboBox.qml:105:9: QML Image: Cannot open: file:///usr/lib/qt6/qml/SddmComponents/angle-down.png
Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: qrc:/theme/Main.qml:41:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: Adding view for "DP-0" QRect(2560,0 2560x1440)
Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: Message received from daemon: Capabilities
Mar 17 21:46:09 archbox sddm-greeter-qt6[30122]: Message received from daemon: HostName
Mar 17 21:46:20 archbox sddm-greeter-qt6[30122]: file:///usr/lib/qt6/qml/SddmComponents/PictureBox.qml:106:13 Parameter "event" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead.
Mar 17 21:46:20 archbox sddm-greeter-qt6[30122]: Reading from "/usr/share/wayland-sessions/hyprland.desktop"

Mar 17 14:45:55 archbox sddm-greeter-qt6[720]: Loading qrc:/theme/Main.qml...
Mar 17 14:45:55 archbox sddm-greeter-qt6[720]: file:///usr/lib/qt6/qml/SddmComponents/LayoutBox.qml:35:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Mar 17 14:45:55 archbox sddm-greeter-qt6[720]: file:///usr/lib/qt6/qml/SddmComponents/ComboBox.qml:105:9: QML Image: Cannot open: file:///usr/lib/qt6/qml/SddmComponents/angle-down.png
Mar 17 14:45:55 archbox sddm-greeter-qt6[720]: file:///usr/lib/qt6/qml/SddmComponents/ComboBox.qml:105:9: QML Image: Cannot open: file:///usr/lib/qt6/qml/SddmComponents/angle-down.png
Mar 17 14:45:55 archbox sddm-greeter-qt6[720]: qrc:/theme/Main.qml:41:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Mar 17 14:45:55 archbox sddm-greeter-qt6[720]: Adding view for "DP-2" QRect(0,0 2560x1440)
Mar 17 14:45:55 archbox sddm-greeter-qt6[720]: Message received from daemon: Capabilities
Mar 17 14:45:55 archbox sddm-greeter-qt6[720]: Message received from daemon: HostName
Mar 17 14:46:09 archbox sddm-greeter-qt6[720]: file:///usr/lib/qt6/qml/SddmComponents/PictureBox.qml:106:13 Parameter "event" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead.
Mar 17 14:46:09 archbox sddm-greeter-qt6[720]: Reading from "/usr/share/wayland-sessions/hyprland.desktop"

There also seems impact on the soundcard enumeration (though that may be related to the differences in the pulseaudio/pipewire/wireplumber installaion)

Make sure to fix the sound stack: pipewire + pipewire-pulse + wireplumber.
If that doesn't allow an automounting fstab, add the nvidia modules to the initramfs and see whether it's really just down to that split-second delay…

Arch Linux

#1 2025-03-17 19:11:17

fstab causing my left monitor to not be detected

#2 2025-03-17 19:12:14

Re: fstab causing my left monitor to not be detected

#3 2025-03-17 21:54:41

Re: fstab causing my left monitor to not be detected

#4 2025-03-17 23:24:22

Re: fstab causing my left monitor to not be detected

#5 2025-03-17 23:29:27

Re: fstab causing my left monitor to not be detected

#6 2025-03-18 02:01:20

Re: fstab causing my left monitor to not be detected

#7 2025-03-18 07:03:38

Re: fstab causing my left monitor to not be detected

#8 2025-03-18 15:20:12

Re: fstab causing my left monitor to not be detected

#9 2025-03-18 22:04:23

Re: fstab causing my left monitor to not be detected

Board footer