47 karma · joined March 21, 2019
THIS!
Here is a link to a photo of my setup at office: https://i.imgur.com/yT8CRfp.jpg
System > Display > Graphics > Default Graphics Settings
I decided not to alter rootfs, so I left it in RO mode. Instead I installed everything I need via flatpak and installed homebrew to have a build tools, compilers and so on.
Using thunderbolt monitor makes it a decent work horse. Basically some days I commute only with steam deck to my office, because I have monitor, keyboard and mouse there as well.
EDIT: I work on 4K monitor. And by the way, I have a running VM on my steam deck just in case I need something extra.
It's already happened to:
- Juju
- Upstart
- Unity
- Mir
- Quickly
- Ubiquity
- Landscape (barely maintained)
- Ubuntu One
- Ubuntu Phone
- you_name_it
I think it's due to Canonical thinks that they have their own very special dedicated way and vision. But always ends up screwed.
1. It is written on the given website: Centos 8.2 and Ubuntu 20.04
2. As many as 5U server can fit. Each drive is 8TB in passthru mode to your VM.
3. I think they are willing to work with users who know what is ZFS. At least for now.
4. Because it's your box. Do whatever you want.
5. Agree with you on that.
So if you have proper Docker installation, containers will restart on reboot.
On macOS/Windows it will run a small VM with Linux Kernel first.
Please check my comment: https://news.ycombinator.com/item?id=19451272
To be honest it is not doing its best, I mean not everything works at its best out of the box.
What is broken:
1) There is some bug in intel firmware out of the box. You will never get your peak CPU freq @ turbo boost mode. Check dmesg and see some fake errors like:
```[35678.237593] CPU0: Core temperature above threshold, cpu clock throttled (total events = 123) [35678.237593] CPU4: Core temperature above threshold, cpu clock throttled (total events = 123) [35678.237595] CPU4: Package temperature above threshold, cpu clock throttled (total events = 179) [35678.237597] CPU0: Package temperature above threshold, cpu clock throttled (total events = 179) [35678.237637] CPU5: Package temperature above threshold, cpu clock throttled (total events = 179) [35678.237638] CPU1: Package temperature above threshold, cpu clock throttled (total events = 179) [35678.237639] CPU6: Package temperature above threshold, cpu clock throttled (total events = 179) [35678.237640] CPU3: Package temperature above threshold, cpu clock throttled (total events = 179) [35678.237640] CPU2: Package temperature above threshold, cpu clock throttled (total events = 179) [35678.237641] CPU7: Package temperature above threshold, cpu clock throttled (total events = 179)```
It's well known problem, just google "Lenovo throttling fix".
I am sitting on 4.20.16 and still I've to apply some workarounds, such as undervolting CPU and so on.
2) Huge power consumption.
I spent weekend to lower it up to 4-6 wh in idle from 14 wh in idle (sic!)
You have to turn everything unneeded off in BIOS (smartcard reader, card reader, ...?). Changing Thunderbolt Assist Mode to Enabled is a must. But be aware of some nasty bug, when after turning assist mode on you will get a brick instead of working device. To avoid it you have to upgrade BIOS, thanks I get BIOS updates in Gnome Software Center (Fedora). Of course take care and install tlp and so on.
3) There is bug in ACPI, when you enter into S3 mode (by design only CPU0 should be online) all of cores will wake up immediately after entering sleep mode. This leads to increased power consumption in sleep mode (approx 10-15% during all night).
There are some other little quirks that I don't remember at the moment. However overall it's a great laptop.
I am running Fedora 29 and pretty happy.