Deep suspend to “mem” works. I checked journalctl. I turned the screen on by pressing the power button, but it stays frozen for about 20-30 seconds before I can use it. I also have to restart sys-net and sys-usb for them to work even if they are powered on… could just be a natural result of suspending. Idle suspend seemed to work, but I couldn’t turn the screen back on even though I tapped some keys and pressed the power button. Mic and camera work. Everything else is fine I think.
Can you change it to partial suspend/wake? One option works, the other option doesn’t. When I just shut my computer and open it again I only wait for about 5-10 seconds to login when using i3 and the default lock (forgot the name). When I suspend with the command line it seems more unreliable. I tried one troubleshooting thing that failed but I forgot what it was.
This thread is linked from the entry and users can come here see all the things you posted after the fact. Ping me when suspend works reliably. The difference between “no” and “partial” suspend support is a bit esoteric for the HCL overview.
Had to edit this post since my .cpio.gz mail attachment got rejected and the message got cut entirely.
I’d attach it here but it seems this format is not allowed.
Also: the cpio file is only really helpful or needed in combination with an actual qubes-issues investigation, so as a standard contribution to the HCL the yml file is sufficient. Thank you for reporting!
you didn’t indicate whether everything works, but since we already have several positive T480 reports I am assuming yours is positive too – please speak up if that’s mistaken
I moved your report along with @SoPunny’s into this original thread by @den1ed in an effort to have all reports for a particular make/model in one thread (easier to find and consume for other forum users)
Hello,
for my daily usage I cannot see anything wrong with it apart from one annoyance - when I have my cursor located somewhere in the bottom of the screen, the display glitches out and starts flickering. Though this might not be a Qubes issue at all - should double check with another Live system.
I haven’t tested Bluetooth, fingerprint scanner, or the smart card reader, but everything else seems to work.
Sometimes it takes the system a long time (~30sec) to return from suspend. I did 10 suspend testes before uploading the hcl and one of them took a long time, but the system did wake up.
Would it make sense to investigate if the T480 could be added to the community list?
Has anyone experienced any issues with this model?
I have had one for 2 weeks, and my experience seems inline with that of other users, everything just seems to work.
I think the main reason for adding it to the list is the low price point, I bought mine from a Lenovo certified reseller and a used model (grade c) cost me $225 before sales tax, upgraded with 32 GB memory and 500 GB NVMe and the total price was around $400.
ME_cleaner seems to work with the stock firmware, but cleaning the firmware adds a 30 sec delay when booting the system, HAP disable (without cleaning) doesn’t add the delay.
I have not had a chance to test the thunderbolt dock yet.
Graphics, networking, audio & suspend work without troubleshooting
Recommended 16 GB RAM 52 are possible
Keyboard can be connected via PS/2 in case of desktops
Readily available to be purchased (including pre-owned)
Multiple community members have confirmed the above (machines that were included in a previous release version of this list need only one good report to be re-included)
Also the list is structured in a make/model/CPU way. So let’s have a look:
i7-8650U reported twice, once for R4.1 and once for R4.0, both positive, but mentions having to detach the second USB controller from sys-usb for suspend to work
i7-8850U reported by one user positively for both R4.0 and R4.1
i5-8250U reported once for R4.1 as partial because of suspend issues
i5-8350U reported twice for R4.0, one of them as partial and reporting various issues / workarounds.
R4.0 is EOL so the only reason I mention it here is that if I had overlooked a valid case for inclusion in the R4.0 list this could count to weaken the two reports requirement for the R4.1 list.
We only have one R4.1 report not mentioning any issues / workaround. But we also do not have any R4.1 report for the T480 from you … so why don’t we start there: please submit a report and let’s see how that changes the above summary.
That sound great, can you point me to those “other users” / their posts for further investigation?
It’s true that it takes 20-30 sec to return from suspend, but I also have a T490 running Windows 11 and it also takes the T490 a long time to return from sleep, I’ve not had to reset sys-net or sys-usb.
Maybe it would make sense to make a thread just to compare experiences with the model, me saying it works doesn’t do anyone any good if I’m the minority.
That’s what the thread you linked is for. Also, these reports are snapshots over time. It is entirely conceivable that with the latest R4.1 install media the T480 is ready to go on the “just works” list.
Next steps:
get your HCL report and see what CPU your T480 has
identify other community members who have the same model/CPU
ask them how their experience with R4.1 install was / if the criteria are fulfilled
Thank you @renehoj for your report, which is online now!
I have moved our posts into this thread. So you are using the i5-8250U like @SoPunny.
I think we are close if we can clarify whether there are suspend issues or not. What’s the difference between “Deep Suspend” and “Idle Suspend”? Has anything changed in the last few weeks – @SoPunny?
I’ve spent most of the evening testing the suspend function, and I can’t reproduce the situation where it takes a long time to wake up.
Reconfiguring the thunderbolt port can result in pci devices being added/removed, which means you manually need to update the sys-usb device list.
Enabling hyper-threading adds a 5-10 sec delay on waking up the system, but it doesn’t add the really long delay. This seems similar to how suspend works on my Windows system.
With sys-usb/thunderbolt correctly configured and hyper-threading disabled, it takes ~2 sec to wake up the system.
Sadly, I didn’t check the logs when I experienced the slow wake-up, I think some software/OS error happened during the wake-up, and the long delay is a software timeout.
Tomorrow I’ll try and get a dock and see if using the thunderbolt port makes suspend fail.
For the community recommended list it is critical that a PC works “out of the box” using just the installer and no other instructions or workarounds. Would you say that’s the case with your T480?
I haven’t found any bios settings that prevent you from using Qubes, but I need a dock to test if the thunderbolt port actually works, hopefully I can do this today.
I tried reinstalling Qubes with a couple different Thunderbolt settings, and they all worked “out of the box” with sys-usb being created during installation.
If after installing Qubes you go into the bios and change the thunderbolt configuration, it reconfigures the pci devices and this can result in an unknown or missing device in the sys-usb device list. I assume this is considered outside the standard installation.
… so why don’t we start there: please submit a report and let’s see how that changes the above summary.