HCL - DELL XPS 17 9730 rtx 4050

User Support HCL Reports
1 
---
layout:
  'hcl'
type:
  'Notebook'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  '2.0'
remap:
  'yes'
brand: |
  Dell Inc.
model: |
  XPS 17 9730
bios: |
  1.19.1
cpu: |
  13th Gen Intel(R) Core(TM) i7-13700H
cpu-short: |
  FIXME
chipset: |
  Intel Corporation Device [8086:a706]
chipset-short: |
  FIXME
gpu: |
  Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
gpu-short: |
  FIXME
network: |
  Intel Corporation Raptor Lake PCH CNVi WiFi [8086:51f1] (rev 01)
memory: |
  97988
scsi: |

usb: |
  4
certified:
  'no'
versions:
  - works:
      'yes'
    qubes: |
      R4.2.4
    xen: |
      4.17.5
    kernel: |
      6.14.4-1
    remark: |
      rtx4050 had to be detached from dom0 or some hangs on start/shutdown
    credit: |
      FIXAUTHOR
    link: |
      FIXLINK

Remarks

Video, audio (in and out) work. Nvidia RTX4050 card was getting a bit in the way (Cannot disable in BIOS) so in order to get to the login screen had to disable gfx screen at luks password entry press esc), once I followed the steps to do GPU passthrough into a different qube - that problem went away (GPU itself works for llm inference with cuda and all as the result).
4K screen is still a hassle, so had to drop the resolution in settings as a workaround for now.
suspend to RAM works.
I self-upgraded the RAM to 96G (2x48G ddr5-5200 dimms), a configuration not listed as a supported by Dell, but listed as supported by Intel for this CPU.

Attachments

Qubes-HCL-Dell_Inc_-XPS_17_9730-20250610-195400.yml (789 Bytes)
Qubes-HCL-Dell_Inc_-XPS_17_9730-20250610-195400.cpio.gz (14.6 KB)

3 Likes
2

After using the machine for a couple of weeks exclusively, some problems became apparent:

The suspend appears to work, I get all the expected messages and all, but with the lid closed, the temperature goes up rapidly so something sucks power and converts it into heat (much more so than when the computer is actually used)

With dGPU detached from the dom0 by default (for gpu passthrough), it seems to be heating things up and I have to start the vm for dgpu (that inits it I guess?) to drop this power drain.

when resuming from suspend if the vm for dGPU was up, is uses a bunch of CPU in the qubes suspend script of some sort sitting in a tight cpu loop that I have not yet fully debugged. Have to kill (normal shutdown does not complete) the vm and restart it. Also post suspend the dgpu is not visible in this vm.

1 Like