You are not logged in.
Pages: 1
So I have been trying to get my hdmi port to show up for a while now but only my second monitor shows up:
Screen 0: minimum 16 x 16, current 3286 x 1080, maximum 32767 x 32767
eDP-1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 340mm x 190mm
1366x768 59.80*+
1024x768 59.92
800x600 59.86
640x480 59.38
320x240 59.29
1152x720 59.75
960x600 59.63
928x580 59.88
800x500 59.50
768x480 59.90
720x480 59.71
640x400 59.95
320x200 58.14
1280x720 59.86
1024x576 59.90
864x486 59.92
720x400 59.27
640x350 59.28
DP-1 connected 1920x1080+1366+0 (normal left inverted right x axis y axis) 600mm x 340mm
1920x1080 59.96*+
1440x1080 59.99
1400x1050 59.98
1280x1024 59.89
1280x960 59.94
1152x864 59.96
1024x768 59.92
800x600 59.86
640x480 59.38
320x240 59.29
1680x1050 59.95
1440x900 59.89
1280x800 59.81
1152x720 59.97
960x600 59.63
928x580 59.88
800x500 59.50
768x480 59.90
720x480 59.71
640x400 59.95
320x200 58.14
1600x900 59.95
1368x768 59.88
1280x720 59.86
1024x576 59.90
864x486 59.92
720x400 59.27
640x350 59.28 apparently I have hybrid graphics, and my Nvidia card handles Hdmi output:
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1)
I have downloaded the drivers required but my Nvidia X server settings only gives me Applications Profiles and Nvidia settings configurations. so basically blank.
these are my logs:
Oct 20 15:40:13 Directhit kernel: Command line: BOOT_IMAGE=/vmlinu
z-linux root=UUID=7808ecfc-ddbd-4533-9550-147f7e3de28f rw zswap.en
abled=0 rootfstype=btrfs quiet splash nvidia-drm.modeset=1 nvidia-
drm.fbdev=1
Oct 20 15:40:13 Directhit kernel: Kernel command line: BOO
T_IMAGE=/vmlinuz-linux root=UUID=7808ecfc-ddbd-4533-9550-147f7e3de
28f rw zswap.enabled=0 rootfstype=btrfs quiet splash nvidi
a-drm.modeset=1 nvidia-drm.fbdev=1
Oct 20 15:40:13 Directhit kernel: nvidia
: loading out-of-tree module taints kernel.
Oct 20 15:40:13 Directhit kernel: nvidia
: module license 'NVIDIA' taints kernel.
Oct 20 15:40:13 Directhit kernel: nvidia:
module verification failed: signature and/or required key missing
- tainting kernel
Oct 20 15:40:13 Directhit kernel: nvidia
: module license taints kernel.
Oct 20 15:40:13 Directhit kernel: nvidia-nvlink: Nvlink Core is be
ing initialized, major device number 240
Oct 20 15:40:13 Directhit kernel: nvidia 0000:01:00.0: enabling de
vice (0004 -> 0007)
Oct 20 15:40:13 Directhit kernel: nvidia 0000:01:00.0: vgaarb: VGA
decodes changed: olddecodes=io+mem,decodes=none:owns=none
Oct 20 15:40:13 Directhit kernel: NVRM: loading
NVIDIA UNIX x86_64 Kernel Module 470.256.02 Th
u May 2 14:37:44 UTC 2024
Oct 20 15:40:13 Directhit kernel: nvidia-modeset: Loading NVIDIA K
ernel Mode Setting Driver for UNIX platforms 470.256.02 Thu May
2 14:50:40 UTC 2024
Oct 20 15:40:13 Directhit kernel: nvidia Last edited by directhit08 (2025-10-21 02:15:31)
Offline
Please use [code][/code] tags. Edit your post in this regard.
Also don't copy and paste out of the pager - that's a wrapped rendition of the first page of the journal or some grep.
xrandr output has extremely limited meaning on wayland since it's basically talking to a compatibility shim that prevents randr calls from crashing.
The HDMI output is likely to the nvidia GPU, so let's look there.
"nvidia-drm.fbdev=1" isn't supported by the 470.256.02 - you're might have a hard time with those on wayland anyway, but for starters: *what* "wayland" are we talking about (gnome, hyprland, plasma, sway, weston, enlightenment, …?) because they're all incompatible on this layer, so this matters *a lot*
Online
Please use [code][/code] tags. Edit your post in this regard.
Also don't copy and paste out of the pager - that's a wrapped rendition of the first page of the journal or some grep.xrandr output has extremely limited meaning on wayland since it's basically talking to a compatibility shim that prevents randr calls from crashing.
The HDMI output is likely to the nvidia GPU, so let's look there."nvidia-drm.fbdev=1" isn't supported by the 470.256.02 - you're might have a hard time with those on wayland anyway, but for starters: *what* "wayland" are we talking about (gnome, hyprland, plasma, sway, weston, enlightenment, …?) because they're all incompatible on this layer, so this matters *a lot*
So i am on hyprland
Offline
Please avoid bloating the thread with pointless full quotes.
https://wiki.hypr.land/Configuring/Multi-GPU/
https://man.archlinux.org/man/extra/hyp … prctl.1.en
Online
I followed what was on the wiki but it didn't work and it also says on the wiki, i need to switch to a dedicated GPU but my laptop doesn't have that option on the bios settings but i can switch off switchable graphics but my Hyprland setup crashes. So should i download optimum manager?
Offline
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
What have you done *exactly*?
it also says on the wiki, i need to switch to a dedicated GPU
Where?
https://deepl.com/
And no, you're not supposed to switch any GPU, let alone using optimus-manager.
You want a hybrid setup to have both GPUs drive all outputs and you want to check the situation w/ hyprctl, not any X11 tools.
Online
I've been attempting to configure a multi-GPU setup on my Dell Precision M4800 with Hyprland, following the instructions here: https://wiki.hypr.land/Configuring/Multi-GPU/.
I'm aware of the specific challenges with NVIDIA and Hyprland, particularly the "Other Issues" mentioned on this page: https://wiki.hypr.land/Nvidia/#multi-mo … d-graphics.
My steps and results are as follows:
I initially configured the hybrid GPU setup as described, but this did not resolve my monitor issues.
I then entered the BIOS and tried to disable "Switchable Graphics" to effectively remove one GPU from the system.
This change caused Hyprland to crash upon launch.
After re-enabling "Switchable Graphics" in the BIOS, Hyprland returned to its previous working state, but my HDMI output is still not detected when running hyprctl monitors.
Monitor eDP-1 (ID 0):
1366x768@59.99700 at 0x0
description: Samsung Display Corp. 0x5441
make: Samsung Display Corp.
model: 0x5441
physical size (mm): 340x190
serial:
active workspace: 1 (1)
special workspace: 0 ()
reserved: 0 40 0 0
scale: 1.00
transform: 0
focused: yes
dpmsStatus: 1
vrr: false
solitary: 0
solitaryBlockedBy: windowed mode,missing candidate
activelyTearing: false
tearingBlockedBy: next frame is not torn,user settings,missing candidate
directScanoutTo: 0
directScanoutBlockedBy: user settings,software renders/cursors,missing candidate
disabled: false
currentFormat: XRGB8888
mirrorOf: none
availableModes: 1366x768@60.00Hz 1366x768@39.99Hz
Monitor DP-1 (ID 1):
1920x1080@60.00000 at 1366x0
description: Samsung Electric Company S27D390 0x30333633
make: Samsung Electric Company
model: S27D390
physical size (mm): 600x340
serial: 0x30333633
active workspace: 5 (5)
special workspace: 0 ()
reserved: 0 40 0 0
scale: 1.00
transform: 0
focused: no
dpmsStatus: 1
vrr: false
solitary: 0
solitaryBlockedBy: windowed mode,missing candidate
activelyTearing: false
tearingBlockedBy: next frame is not torn,user settings,missing candidate
directScanoutTo: 0
directScanoutBlockedBy: user settings,software renders/cursors,missing candidate
disabled: false
currentFormat: XRGB8888
mirrorOf: none
availableModes: 1920x1080@60.00Hz 1920x1080@59.94Hz 1920x1080@50.00Hz 1680x1050@59.95Hz 1600x900@60.00Hz 1280x1024@75.03Hz 1280x1024@60.02Hz 1440x900@59.89Hz 1280x800@59.81Hz 1152x864@75.00Hz 1280x720@60.00Hz 1280x720@59.94Hz 1280x720@50.00Hz 1024x768@75.03Hz 1024x768@70.07Hz 1024x768@60.00Hz 800x600@75.00Hz 800x600@72.19Hz 800x600@60.32Hz 800x600@56.25Hz 720x576@50.00Hz 720x480@59.94Hz 640x480@75.00Hz 640x480@72.81Hz 640x480@59.94Hz Here are my logs for my nvidia GPU:
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=7808ecfc-ddbd-4533-9550-147f7e3de28f rw zswap.enabled=0 rootfstype=btrfs quiet splash nvidia-drm.modeset=1 nvidia-drm.fbdev=1
[ 0.041726] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=7808ecfc-ddbd-4533-9550-147f7e3de28f rw zswap.enabled=0 rootfstype=btrfs quiet splash nvidia-drm.modeset=1 nvidia-drm.fbdev=1
[ 2.303653] nvidia: loading out-of-tree module taints kernel.
[ 2.303663] nvidia: module license 'NVIDIA' taints kernel.
[ 2.303666] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[ 2.303667] nvidia: module license taints kernel.
[ 2.584614] nvidia-nvlink: Nvlink Core is being initialized, major device number 240
[ 2.585019] nvidia 0000:01:00.0: enabling device (0004 -> 0007)
[ 2.585102] nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
[ 5.185504] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 470.256.02 Thu May 2 14:37:44 UTC 2024
[ 5.219892] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 470.256.02 Thu May 2 14:50:40 UTC 2024
[ 5.237179] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
[ 5.322692] nvidia-uvm: Loaded the UVM driver, major device number 238.
[ 5.327296] nvidia_drm: unknown parameter 'fbdev' ignored
[ 5.327299] nvidia_drm: unknown parameter 'fbdev' ignored
[ 5.327435] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[ 8.936070] [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
[ 11.834005] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input13
[ 11.834066] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input14
[ 11.834122] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input15
[ 11.834175] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input16After reverting the BIOS setting, I consulted the Hyprland Discord server, where I was informed that my specific GPU model is likely incompatible with Hyprland.
Last edited by directhit08 (2025-10-21 12:32:09)
Offline
470xx drivers lack the stuff that makes Wayland workable on the Prop drivers. You'll either have to opt for nouveau or live with the situation.
Online
Pages: 1