Proud x201 user here.

Wifi works perfectly, suspend/resume, docking/undocking too.

As for battery life, it was around 19W/h when I first switched to linux after FreeBSD. After installing tld and powertop it is stable around 10.8-12W with wifi enabled.

Maybe you might want to try a recent distro, I'm using Fedora and I really like it.

Even my 3G usb dongle worked flawlessly with zero config.

PS: I remember having a flaky wifi under Debian 8, but that was due to an old version of wifi driver. It has since long been fixed in every distro I tried -including Debian-.

PS 2: My laptop is pretty old (x201), so your mileage may vary. You might want to check out thinkwikis for further info.

Partly, that's because the x201 is so old. It's had about 7 years to mature support.

I had an x201 new, and I ran into all those problems listed above for the first two years. Hell, I had to use a USB WIFI dongle for the first year or so because the drivers hadn't stablized.

Yeah, I'm so tired of hearing this come up when people are looking for Linux laptops. It's very old, and VERY ugly. Most of us want something modern that runs Linux well.

I can only speak about myself of course but running Ubuntu 16.04 on a thinkpad x250 I have absolutely none of the issues you have listed above. Maybe you hear more about people having bad experiences than good ones?

I remember having these issues on an x60 series maybe 8 years ago, but my friends who have thinkpads are all running them fine, even on the jankiest distros with a bit of careful driver picking

Owner of a Thinkpad X1 3rd gen running Debian (started with Jessie, now Stretch), and my experience is quite different but there are some things to know. Let's trade anecdotes:

> - Wifi is flaky (ier than on windows)

No problem there, always been rock solid. The chipset is likely to matter, my laptop uses an Intel chipset. Performance wise Intel may not be the best, but the Linux support has always been good in my experience.

> - Battery life is shit (ier than on windows)

A very common misunderstanding, and very easy to solve. The thing is, a stock Linux distro is made independently of the PC hardware that will run it. There's no integration like any PC vendor does when installing Windows, making sure the Windows configuration is well tuned. In order to be functional on most devices, a Linux distro is typically conservative, and will typically stay away from enabling low-power modes that are flaky on some crappy PC models.

But for most tier 1 PC brands, the hardware is fine and it's perfectly safe to enable aggressive low-power. So just install a package like The Laptop Project (tlp), or the older laptop-mode, and you're good to go. You can even tune the configuration, it's simple and well commented. For example, with a fast SSD (no spin up/down), one can be very aggressive on putting the drive into low-power.

With this done, taking about 10 mn tops, I have a longer battery life on Linux as on the stock Windows8.1. And this is as reported by the firmware through ACPI, so same estimator on both sides.

> [Various sleep mode issues]

There was a very nasty bug in Linux MMU set-up that's been solved in 4.8. Before this, it could trigger some random and sometimes hard to reproduce bugs on some models, leading to crashes on resume. I've been affected, and it was a pain. The bug was there for a long time apparently.

Since 4.8, it's been rock solid. Zero issues. And it's really night and day in term of user experience. In case some of your issues were related, you may want to make sure you're running a recent enough kernel.

As for the unwanted wake-ups in a bag turned into an oven? Only ever happened to me on my work TP running Win7. From experience, sleep is not perfect there too.

No experience on using an external monitor with my Linux laptop.

One of the main weakness is that there's no ODM integration if you install Linux yourself. With big brands like TP, it's still mostly been smooth in my experience, except for the nasty resume bug fixed in 4.8. If that's a problem for you, there are now vendors with pre-installed Linux. Then it's a similar situation to Windows.

> A very common misunderstanding, and very easy to solve.

If it were that easy to solve, I would think Linux installers would take care of this.

> The thing is, a stock Linux distro is made independently of the PC hardware that will run it. There's no integration like any PC vendor does when installing Windows, making sure the Windows configuration is well tuned.

You make it sound like Windows needs to be fine-tuned (by the vendor) to provide good battery life. This is absolutely not the case. You install a bare Windows 10 on a random laptop, and battery performance will likely be much better than on Linux.

Anecdata, but my desktop Lenovo workstation's suspend function worked well with Linux, but after an update (few months ago) it never resumes successfully. Nothing in logs -- just simply doesn't wake up properly. (4.10 kernel.) These are painful things.

> Anecdata, but my desktop Lenovo workstation's suspend function worked well with Linux, but after an update (few months ago) it never resumes successfully. Nothing in logs -- just simply doesn't wake up properly. (4.10 kernel.) These are painful things.

That sounds like my experience with Windows 10 on my gaming PC. I only use that machine when gaming, and while it has a <10 second cold boot time (god I love NVMe), I prefer to leave it running and let it fall asleep after a few minutes of inactivity. Some time last week or so, I noticed it never cycles fully to sleep; it will fall asleep and almost immediately wake up. I'm positive this was due to a Windows update, as I haven't changed any settings on it before or after the incident first occurred.

Now, this is on a PC I built, but I used a common motherboard (Gigabyte Z170M) and never had this issue on my previous build, also based on a Gigabyte Z series board. My wife's computer is a mini-PC made by HP, and it started having the same sleep/wake issues during the same week. Something in a recent Windows update has affected sleep states.

I had similar, terrible issues with my gaming rig when I let Windows auto-update from 7 to 10. I found that there is an option in system update to "restore" or "auto-fix" the OS. You might start by trying that.

I found that I needed to let the entire thing be wiped (including all software) and re-installed in order to get it working. A long time and complete pain in the ass, but it's much better now.

Just as a piece of warning if you go that route: MS decided that my legit MS office keys were "Pirated" because they were old and wanted me to upgrade (after telling me that it was a valid key 3 hours before) so I told them to pound sand and I was going to buy MAC's from now on, and I'm not a fan of Apple at all. They offered me nothing, but the chance to give them more money.

> Just as a piece of warning if you go that route: MS decided that my legit MS office keys were "Pirated" because they were old and wanted me to upgrade (after telling me that it was a valid key 3 hours before)

This happened to me after my first upgrade to Windows 10. I had a legit copy of Office 2010, and when I upgraded my Windows 7 installation to Windows 10 during the free year, I opted to do a clean OS install after 10 was activated. Upon reinstalling Office and inputting my key, at first it activated then it threw my Office install into an unactivated state and told me to contact my administrator. Umm, what? I'm the administrator and this was a retail purchased and licensed copy that worked fine before being installed on Windows 10. I even tried reverting to Windows 7 and installing Office on that, but it never activated and gave me the same message.

Thankfully I don't really rely on Office anymore and can get by with F/OSS alternatives or Office Online, but it definitely sucks that Microsoft appears to try pushing its business customers into O365 subscriptions and away from traditionally licensed software using what I feel should be illegal tactics.

Completely agree with you. I have in writing that my key would be good, even though the MS site said that there was an error and I needed to check with Customer Service. I then explained this to three people, whom found the written statement and said they couldn't/refused to fix the problem. They just wanted to sell my an O365 subscription.

As to how legal their tactics are, I'm not sure. I do know before I would never have considered anything other than MS, I'm now left to moving onto Mac's because I cannot give them more money and the work I do tends to now work in the Linux or alternative OS environments. Lots of industrial software that is touchy enough as it is...

I only boot into Windows once a month or so. This Monday, when I had my laptop sitting idle for a bit, I noticed the sound of the hard drive settling down and spinning up again in a regular pattern. At the time, I thought it was the Antivirus deciding to do an idle scan just when the OS put the drive to sleep, but now I think I might be affected by the same bug you mention.

That got an NVidia GPU?

Not much can be done with vendors that are actively hostile.

> Admittedly, mine is not Thinkpad

nuff said