Hello I have ASUS TUF Gaming F15 FX507 i7 13620H Laptop with RTX 4070 Graphic card, when I had windows 11 on my system, the external Samsung monitor works well.
The issue: I have Qube OS 4.2.2 and Debian 12 OS too. non of them detect external monitor. I installed 535 and 560 drivers via command line. still not works.
nvidia-smi
NVIDIA-SMI has failed because it couldn’t communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
nvidia-detect
No NVIDIA GPU detected.
nvidia-driver is already the newest version (560.35.03).
Secure boot: Disabled
uname -r
6.6.42-1.qubes.fc37.x86_64
Menu → Other → about xfce → GPU: Mesa Intel Graphic (3.8 GiB)
I know this doesn’t help you directly but on my computer other than qubes I also have windows and a normal linux distro, so if something hardware related doesn’t work in qubes I check in the other two (because you have to know if the problem is qubes-specific, linux-specific or hardware specific).
Also how exactly did you install the proprietary driver? Did you read the community guides?
Now external monitor detected by default, and I have mouse pointer on external monitor but the screen of it is black. do u have any suggestion? I enabled mirror display option and still not works
By changing display → refresh rate, screen shows desktop on external monitor but it’s freezes
sudo qubes-dom0-update kernel-latest
@dom0 ~]$ sudo qubes-dom0-update kernel-latest
Using sys-whonix as UpdateVM to download updates for Dom0; this may take some time...
Unable to detect release version (use '--releasever' to specify release version)
Fedora 37 - x86_64 246 kB/s | 70 MB 04:51
Fedora 37 - x86_64 - Updates 139 kB/s | 43 MB 05:18
Qubes Host Repository (updates) 135 kB/s | 2.9 MB 00:21
Last metadata expiration check: 0:00:12 ago on Thu Aug 22 18:00:17 2024.
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
kernel-latest x86_64 1000:6.10.3-1.qubes.fc37 qubes-dom0-current 13 M
Installing dependencies:
kernel-latest-modules x86_64 1000:6.10.3-1.qubes.fc37 qubes-dom0-current 82 M
Transaction Summary
================================================================================
Install 2 Packages
Total download size: 95 M
Installed size: 538 M
DNF will only download packages for the transaction.
Downloading Packages:
(1/2): kernel-latest-6.10.3-1.qubes.fc37.x86_64 106 kB/s | 13 MB 02:05
(2/2): kernel-latest-modules-6.10.3-1.qubes.fc3 230 kB/s | 82 MB 06:06
--------------------------------------------------------------------------------
Total 265 kB/s | 95 MB 06:08
Complete!
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Qubes OS Repository for Dom0 2.9 MB/s | 3.0 kB 00:00
Qubes OS Repository for Dom0 15 MB/s | 65 kB 00:00
Dependencies resolved.
=========================================================================================================================================
Package Architecture Version Repository Size
=========================================================================================================================================
Installing:
kernel-latest x86_64 1000:6.10.3-1.qubes.fc37 qubes-dom0-cached 13 M
Installing dependencies:
kernel-latest-modules x86_64 1000:6.10.3-1.qubes.fc37 qubes-dom0-cached 82 M
Transaction Summary
=========================================================================================================================================
Install 2 Packages
Total size: 95 M
Installed size: 538 M
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : kernel-latest-modules-1000:6.10.3-1.qubes.fc37.x86_64 1/2
Running scriptlet: kernel-latest-modules-1000:6.10.3-1.qubes.fc37.x86_64 1/2
Installing : kernel-latest-1000:6.10.3-1.qubes.fc37.x86_64 2/2
Running scriptlet: kernel-latest-1000:6.10.3-1.qubes.fc37.x86_64 2/2
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.10.3-1.qubes.fc37.x86_64
Found initrd image: /boot/initramfs-6.10.3-1.qubes.fc37.x86_64.img
Found linux image: /boot/vmlinuz-6.6.42-1.qubes.fc37.x86_64
Found initrd image: /boot/initramfs-6.6.42-1.qubes.fc37.x86_64.img
Found linux image: /boot/vmlinuz-6.6.36-1.qubes.fc37.x86_64
Found initrd image: /boot/initramfs-6.6.36-1.qubes.fc37.x86_64.img
Adding boot menu entry for UEFI Firmware Settings ...
done
Verifying : kernel-latest-1000:6.10.3-1.qubes.fc37.x86_64 1/2
Verifying : kernel-latest-modules-1000:6.10.3-1.qubes.fc37.x86_64 2/2
Installed:
kernel-latest-1000:6.10.3-1.qubes.fc37.x86_64 kernel-latest-modules-1000:6.10.3-1.qubes.fc37.x86_64
Complete!
lspci -k
@dom0 ~]$ lspci -k
0000:00:00.0 Host bridge: Intel Corporation Device a715
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device 14a3
0000:00:01.0 PCI bridge: Intel Corporation Device a70d
Subsystem: ASUSTeK Computer Inc. Device 250d
Kernel driver in use: pcieport
0000:00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [UHD Graphics] (rev 04)
DeviceName: Onboard - Video
Subsystem: ASUSTeK Computer Inc. Device 250d
Kernel driver in use: i915
Kernel modules: i915, xe
0000:00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device 14a3
Kernel driver in use: proc_thermal_pci
Kernel modules: processor_thermal_device_pci
0000:00:06.0 System peripheral: Intel Corporation RST VMD Managed Controller
DeviceName: Onboard - Other
0000:00:07.0 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port #0
Subsystem: ASUSTeK Computer Inc. Device 14a3
Kernel driver in use: pcieport
0000:00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module
DeviceName: Onboard - Other
0000:00:0d.0 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller
DeviceName: Onboard - Other
Kernel driver in use: pciback
Kernel modules: xhci_pci
0000:00:0d.2 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #0
DeviceName: Onboard - Other
Subsystem: Device 2222:1111
Kernel driver in use: pciback
Kernel modules: thunderbolt
0000:00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation
DeviceName: Onboard - Other
Subsystem: Intel Corporation Device 0000
Kernel driver in use: vmd
Kernel modules: vmd
0000:00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device 201f
Kernel driver in use: pciback
Kernel modules: xhci_pci
0000:00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01)
DeviceName: Onboard - Other
0000:00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi WiFi (rev 01)
DeviceName: Onboard - Ethernet
Subsystem: Intel Corporation Device 0074
Kernel driver in use: pciback
Kernel modules: iwlwifi
0000:00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device 14a3
Kernel driver in use: intel-lpss
0000:00:15.1 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #1 (rev 01)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device 14a3
Kernel driver in use: intel-lpss
0000:00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device 14a3
Kernel driver in use: mei_me
Kernel modules: mei_me
0000:00:1c.0 PCI bridge: Intel Corporation Device 51be (rev 01)
Kernel driver in use: pcieport
0000:00:1f.0 ISA bridge: Intel Corporation Raptor Lake LPC/eSPI Controller (rev 01)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device 14a3
0000:00:1f.3 Audio device: Intel Corporation Raptor Lake-P/U/H cAVS (rev 01)
DeviceName: Onboard - Sound
Subsystem: ASUSTeK Computer Inc. Device 14a3
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_avs, snd_sof_pci_intel_tgl
0000:00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device 14a3
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
0000:00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device 14a3
Kernel driver in use: intel-spi
Kernel modules: spi_intel_pci
0000:01:00.0 VGA compatible controller: NVIDIA Corporation AD106M [GeForce RTX 4070 Max-Q / Mobile] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 250d
Kernel driver in use: nouveau
Kernel modules: nouveau
0000:01:00.1 Audio device: NVIDIA Corporation Device 22bd (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 250d
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
0000:37:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
Subsystem: ASUSTeK Computer Inc. Device 208f
Kernel driver in use: pciback
Kernel modules: r8169
10000:e0:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port
Kernel driver in use: pcieport
10000:e1:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN770 / PC SN740 256GB / PC SN560 (DRAM-less) NVMe SSD (rev 01)
Subsystem: Sandisk Corp WD Black SN770 / PC SN740 256GB / PC SN560 (DRAM-less) NVMe SSD
Kernel driver in use: nvme
Kernel modules: nvme
Hello @Hellothere thank you for replay, as I said when I had windows 11 on my system, the external Samsung monitor works well. But Qube OS 4.2.2 and Debian 12 OS not work with external monitor.
And I downloaded latest Nvidia driver from official website and installed via terminal: https://www.nvidia.com/en-us/drivers/details/230918/
I have a RTX 4060, and I use an external 34’’ ultra wide. QUBES 4.2.2.
The way I did it was by changing a configuration in the BIOS. There is an option were I can choose between mix mode, just intel graphics or just GPU graphics, the terminology used by BIOS is different, but this is what they mean.
Using the just GPU graphics, I was able to use the external monitor. However, I can’t user the main monitor at the same time. Some times I can, other times it gets mirrored, other times it just gets crazy. So I opt just for the external one.
I read the topic and did: add new qube ‘sys-gui’ then in change mode to HVM and then in device tab added Nvidia to list
when I run sys-gui, it ask to login to system again then the external monitor goes off. what is my mistake?
There’s no chance to use external monitor in Discrete mode
Would you please explain more or give me a topic to understand, because I’m not a tech guy.
As I said, Nvidia won’t work on external monitors if not in Discrete mode (which is a BIOS setting and you cannot select “only Intel graphics” (iGPU) anywhere: it’s either Optimus (iGPU+dGPU), or Discrete, i.e. dGPU), regardless of drivers anywhere.
Sorry, my mistake, I wanted to say no chance on using Nvidia in Optimus mode on external monitor, as it was obvious from my topic quoted, except if it is attached to sys-gui-gpu or some other HVM. You also have to attach Nvidia audio device too, which is something like 01:00.1 Audio Device NVIDIA Corporation
If you want whole Qubes to run on external monitor, then you should try Discrete mode.
Sorry for the third post in a row, but it could matter for the ones reading via email.
If you would want whole Qubes to work in Discrete mode, most probably if you were installed Qubes in Optimus mode, simply changing setting in BIOS to Discrete wouldn’t work, so you’d probably have to reinstall Qubes again starting from Discrete setting in BIOS. For me it doesn’t work to switch this setting in BIOS and to successfully boot to Qubes.
Yes, that is the option dGPU. I was able to use both in extended mode in the past, but as it was temperamental across reboots, I stop to trying it.
Another issue I have is, if I select just the external, then I cannot use the main one again, only if I reboot again.
I just had similar issue. I run updates for all my qubes and dom0. After restart my external monitor connected via HDMI (which worked for last 2 years) stopped being detected.
To fix it, I installed the latest kernel in dom0 and restarted my machine again.
After the restart the monitor started working again.