It looks like itās out of order with the other items in the HCL. There are two other ThinkPad P50 items further down the list and my submission along with the ThinkPad T560 directly under it arenāt in alphabetical order.
It looks like itās out of order with the other items in the HCL.
I thought the cause was that I accidentally used āThinkPad-P50ā in the file name instead of āThinkPad_P50ā. Same for the T560. But that doesnāt seem to be the case.
Also if I click on the āModelā header the list sorts correctly. Maybe we can make that the default when the page is initially loaded? (I wouldnāt know how to, otherwise Iād make the PR myself).
Iām afraid I donāt know how to do that either. Iām not sure if we have control over the default sorting. If youād like to file an issue for it, I can add the help wanted on it.
@Sven, I would also like to add the P50 to the Community-recommended hardware list. What specifically would still be required to do so? I can think of the TPM for AEM, but is there anything else?
Edit:
Nevermind, I just saw your post in Lenovo ThinkPad P51 - #3 by Sven. I didnāt know that multiple submissions needed to have the same processor in order to be included. I would recommend listing that in the criteria for inclusion, though.
@Sven, I would also like to add the P50 to the Community-recommended hardware list. What specifically would still be required to do so? I can think of the TPM for AEM, but is there anything else?
Like I just pointed out in my answer to @MrTea, as soon as there are two reports using the same CPU and one of the reporters confirms the āno workaroundsā criteria, it can be added.
This is by no means arbitrary: there a plenty of examples in the HCL where one CPU works perfectly fine, while another one necessitates lots of troubleshooting/workarounds with the same model. Also, obviously the CPU needs to support IOMMU.
@tech3599, @adw ā¦ it turns out the root cause was indeed the filename, but the page was not automatically refreshed. Today, after committing another unrelated HCL report, the sorting was fixed. I assume only a change in the files contents opposed to the filename triggers the generation of the page. Knowing this now, I can account for it in the future.
Not on mine! Only thing here is - it canāt do a proper restart. If I do so - it just shutdown without the restart.
But guess - this is the wrong topic for discussing it.
Video, networking, sleep/suspend, audio, keyboard, trackpad, and trackpoint are working.
Touch screen does not work.
I have not tested the integrated microphone or webcam, but they are listed in Qubes Devices. I have also not tested AEM.
I have not found any other problems.
This report is for Qubes R4.1 . If I should add new reports to previous topics for the same hardware in the future, please let me know.
External Monitor via HDMI port - 2560 x 1440 @ 60Hz - both Landscape and Potrait modes (given local factors like monitor and HDMI cable used)
External monitor via Mini DisplayPort - 2048 x 1536 @ 75Hz - both Landscape and Potrait modes (given local factors like monitor, HDMI cable, and Mini DisplayPort-to-HDMI convertor used)
Ethernet Networking
Wi-Fi Networking
Suspend/resume seems to work
Wi-Fi connection correctly resumes, after Suspend/resume of the laptop
Audio - Local music players, Spotify and YouTube audio all worked
ā In-built speakers work
ā USB audio works
ā 3.5mm audio jack works
Videos - VLC and YouTube video worked (a small bit of screen tearing occurred on some videos, but mostly worked well. I never looked further into it)
Microphone - gnome-sound-recording(1) on both fedora-41-xfce and debian-12-xfce both worked. The microphone recordings were loud and sounded ātinnyā on playback - it picks up a lot of ambient noise (could be this environment, but never looked into it further)
Webcam - Tested with cheese(1), webcam quality isnāt brilliant for modern standards, but it does work on Qubes 4.2
Not Tested
HDMI Audio
Which of the GPUs was being utilised by the dom0 AdminVM to draw the GUI
Anti evil maid
ThinkPad Dock
Fingerprint Reader (138a:0090) - sys-usb detects the Validity Sensors, Inc. VFS7500 Touch Fingerprint Sensor, and seems like this could be made to work using Marco Trevisanās validity-sensors-tools (see https://snapcraft.io/validity-sensors-tools) and fprintd(1) / pam_fprintd(8), but didnāt work on this any further.
X-Rite, Inc. X-Rite Pantone Color Sensor (0765:5101) - Attached to sys-usb by default in Qubes 4.2, and lsusb(1) detects the device, but I have no interest in it.
A handful of other unidentified USB devices attached to sys-usb that I never looked into.
Any other devices not listed
Not Working
USB C - The laptop has a single USB C port on the laptop, tried both low and high powered devices on the port but sys-usb didnāt recognise them. Didnāt do any testing to see if it could be resolved though, because I have never tried connecting anything before now on the USB C under alternative operating systems. I canāt rule out this port is broken on this laptop and Iāve just never noticed it.
TPM 2.0 module (Intel Platform Trusted Technology with TPM 2.0 mode) - Qubes 4.2 couldnāt detect it.
3f:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) - not understood by the kernel.
Other Notes
After the BIOS was updated with the latest revision, disable TPM 2.0 by entering the BIOS; then go to Security ā Security Chip ā Security Chip Selection; and change default value of Intel PTT (the TPM 2.0 module) to Discrete TPM (the TPM 1.2 module). Qubes 4.2 canāt recognise the Intel PTT, but it can recognise the Discrete TPM.
Once Qubes 4.2 is installed, permanently move the ā3f:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Readerā PCI device from dom0 to sys-usb; in order to prevent this card reader from being able executing arbitrary code in dom0, whilst the laptop is unattended.