Too soon old, too late smart – the ancient mariner gets a sharp rap with the clue bat

That’s my 1999 22 SeaSport up at the top of the page.  Main power is a Volvo-Penta 5.7 GSi.  Marinized Chevy 350 with throttle-body injection.

On our one halibut outing this year we ran out to the ‘but hole, fished an hour or so, then fired up the big engine to move.  Engine started but I could hear the high-pressure fuel pump screeching.   Shut down, restarted… more screech.  Finally it stopped but when throttling up the engine would surge and shut down.

This happened before a few years ago.  Can be caused by a failing pump (there are two: low pressure and high pressure) or by a fuel obstruction that causes pump cavitation.  They screech when they aren’t full of fuel.  Last time I replaced the HP pump and it was fine for 7 years or so.

Normally I’d spend some time troubleshooting and maybe take the one-thing-at-a-time approach but this happened just before leaving for a family reunion that was already going to wipe out  the first two weeks of king season, and there was no time for a leisurely approach to repair – or to try to find a boatyard that could take it on.

Larry and Richard – service manager and parts dude – at a major shop in Seattle were very generous with their time trying to get me going over the phone.  General consensus was that likely it was a failing pump.  Larry also suggested a clogged anti-siphon valve and since I wasn’t sure I could reach it on top of the fuel tank (and I HATE touching fuel components that I can’t monitor easily) he advised to test with an outboard fuel primer bulb and sure enough plenty of fuel flow.

So… many $$$ later I swapped out both pumps.  Did a sea trial that went fine, but on returning home to do an engine flush I got a little pump screech.   Per the book, it could have been vapor in the system after a hot soak (not a problem if so) but the old pumps never did that, so time to check the ant-siphon valve.

By removing the engine cover I was able to access it fairly easily and once it was off it proved to be completely unobstructed… BUT… when I went to remove the fuel hose from the valve barb – usually wrestling match after 23 years in place… it nearly fell off when I touched it.

Ah *bleep* the problem all along was most likely an air leak around the valve barb, not a pump failure or obstruction.  Could have fixed it on the water in seconds with a screwdriver and skipped the mad dash to repair… not to mention the $$$.  Replaced the valve with one that a more serious set of rings on the barb, and cranked down the hose clamp.  So far so good.  No screech and running fine.  (Knock on teak…)

Like I said, too soon  old and too late smart. And it’s never a good idea to rush these things – if only a measured approach had been an option.

Posted in Uncategorized | Leave a comment

Don’t panic – you can still secure boot Linux on new ThinkPads

There seems to be a whole lot of half-informed “information” floating around about Lenovo and/or MS locking out Linux on new ThinkPads. And as usual,  the torch and pitchfork crowd railing against the conspiracy.

Nope. You can still boot a signed distro, but it takes one more step. The ability to boot something that uses MS 3rd party certs has been split out in the secure boot options. Enter BIOS, switch that toggle, and Bob’s your uncle. Confirmed on my ThinkPad X1 Yoga Gen 7 and multiple other ThinkPads by my mates.  Whew.


X1 Yoga Gen 7 BIOS 3rd Party Certs – image updated

Posted in Uncategorized | 5 Comments

ThinkPad X1 Yoga Gen 7: Truly a New Generation

A preliminary look at the laptop that just took over the place of honor on my bench. Base specifications and the specifics of this top-of-the-line X1 Yoga – and how it compares to the previous tenant, a high-end Gen 6  X1 Yoga – ThinkPad X1 Yoga Gen 6: Future Perfect?.  There’s also a super-quick look at Linux issues.  By now you know the drill:

From time to time Lenovo sends me a gadget. They’re handy to have around – both for my own use and when trying to help out in the Lenovo forums. I do some testing and writing as well. Beyond the use of the laptop, I’m not otherwise compensated. Professional images are Lenovo’s. Amateur snapshots are mine. Opinions are exclusively mine. I do not work for, represent, or speak for Lenovo.

This one, like the Gen 6, is a pre-customer-ship unit.  I expect it to be representative of what is – or will be – available to the public, but it may vary in some details.  As always, I strive for accuracy, but please double-check anything I say here before using it to make a purchase decision.

[Update 2022.08.06] I’ve added an “Unresolved Issues” section at the end of this article.

On first look it seems that nothing has changed from the Gen 6, apart from the little bump at the top of the screen – the Communications Bar that contains the microphones and camera(s).  It’s an identical-appearing, aluminum-cased, 16×10 ThinkPad Yoga with the same set of ports.

On a 2nd look it becomes clear that many things have changed – both base components and options: CPU, RAM, camera, and display, to name a few. As usual, before digging into the details, a few pretty pictures (clickable gallery – images Lenovo):


The specifications:

X1 Yoga Gen 7 Datasheet Snip

The full Datasheet:

The current sales page:  It describes features I don’t address here, like “breathing through the keyboard”.

The ports on the Gen 6 and 7 appear to be identical:

X1 Yoga Gen 7 Ports – image Lenovo


That one external difference – the communications bar containing microphones and cameras:

X1 Yoga Gen 7 Communications Bar


And the substantial component differences:

Links to the base specifications:
      X1 Yoga Gen 6
      X1 Yoga Gen 7

The range of CPU options:

X1 Yoga Gen 6 CPUs

X1 Yoga Gen 7 CPUs

That’s right.  Up to 14 cores and 20 threads.  Good grief.  12th Gen Intel® Core™ Mobile Processors

X1 Yoga Gen 6 Memory – LPDDR4x-4266

X1 Yoga Gen 7 Memory – LPDDR5-5200

X1 Yoga Gen 6 Multimedia – Cameras

X1 Yoga Gen 7 Multimedia – Cameras

X1 Yoga Gen 6 Displays

X1 Yoga Gen 7 Displays

Note that OLED option.  Gorgeous!

X1 Yoga Gen 6 Network

X1 Yoga Gen 7 Network


And for completeness a few of the similar component options:

X1 Yoga Gen 7 Graphics

X1 Yoga Gen 7 Monitor Support

X1 Yoga Gen 7 Storage

Storage notes:

The Gen 6 storage options don’t mention m.2 2242 – only 2280.  The Hardware Maintenance Manuals for both show identical SSD mounting, so it’s likely 2242 would work in either – with an appropriate mechanical extender.

Both machines list PCIe 4.0 x4, and PCIe 4.0 x4 Performance drives.  SSD manufacturers offer PCIe 4.0 drives in (at least) two performance tiers.  The ones Lenovo lists without the “Performance” label have speeds approximately equivalent to top-end PCIe 3.0 drives.  The “Performance” SSDs are roughly twice as fast as the non-performance drives.

Lenovo uses multiple SSD vendors.  Drive models and speed may vary from one machine to another as shipped, but the “Performance/non-Performance” qualifiers should be roughly representative.


The specifics of these two top-of-the-line machines:

X1 Yoga Gen 6:
     WQUXGA IPS display
     IR & 720p hybrid camera, with privacy shutter, fixed focus
Intel Core i7-1185G7  (4 core) processor
     32GB LPDDR4 memory
     2TB PCIe G4 performance SSD
     Windows 10 Pro

X1 Yoga Gen 7:
     WQUXGA OLED display
     FHD IR MIPI camera with Computer Vision Technology
     Intel 12th gen i7-1280P (14 core) processor
     32GB LPDDR5 memory
     2TB PCIe G4 performance SSD
     Windows 11 Pro


A few basic performance comparisons:

SSD performance.  As noted, different vendors, somewhat different speeds but both in the PCIe 4.0 “Performance” realm

X1 Yoga Gen 6 PCIe 4.0 SSD

X1 Yoga Gen 7 PCIe 4.0 SSD

Passmark combined performance:

X1 Yoga Gen 6 Passmark

X1 Yoga Gen 7 Passmark

Battery runtime (not “life”):

X1 Yoga Gen 6 Runtime MP3

X1 Yoga Gen 7 Runtime MP3

X1 Yoga Gen 6 Runtime MP4

X1 Yoga Gen 7 Runtime MP4

The above tests were run at half brightness and 20% volume.  Sound through internal speakers.  The runtime trend follows what I observed with the Gen 6 compared to earlier ThinkPad Yogas: high-DPI displays, top-end CPUs (14 cores!), maximum RAM and SSD capacity and speeds, all lead to reduced battery runtime.  My presumption is that the OLED display also causes an additional increment of power consumption compared to an IPS panel.  That was true in the past, unsure if it’s still the case.  Gen 7 machines with other components should have increased runtimes compared to this maxed-out unit.

I would call this Gen 7 a 7, maybe 8 hour machine when playing media.  The runtime estimate with just an idle desktop showing at half brightness was about 12 hours, so I’d expect the runtime with an editor up to be decent, if not stellar.  I wonder if there will be further tuning of how the performance vs efficient cores are managed and assigned tasks, but I have no information about that.  One can hope…


Linux, the other OS:

OS support:

I usually (and will at some point soon) take a look at Linux.  Both live and installed.  For now some brief observations:

From what I read – on the sales and support sites – there will be Linux support for the Gen 7.  <soapbox> I often see complaints that new hardware “doesn’t support Linux!!!” That’s backward IMHO.  I’ve been around Linux since the install started with a floppy, and the question is whether and when kernels and drivers will catch up with new hardware, not the other way around. </soapbox>

It’s early days for this hardware setup and some things will take longer than others.  The MIPI camera may be problematic for some time, as described in this forum reply: Re:X1 Yoga Gen 7: Live Linux testing…  This represents things at the time of that reply.  I’m confident it will get sorted but it might be wise – as suggested – to avoid the MIPI camera for now.  I’m sure there will be much more discussion of Linux on the Gen 7 going forward.  Keep an eye on the forums:

I’ll probably be adding additional Linux notes here as information becomes available.

Secure Boot revisited –  “Allow Microsoft 3rd Party UEFI CA”:

This caught me by surprise.  My Linux test live media – Ubuntu 21.10 and Fedora 35 – would not boot in secure mode on the Gen 7.  The distros are signed, and they would boot secure on all my earlier UEFI/Secure Boot machines., so what the heck?

With a little inside help I found the answer: there’s additional granularity in how BIOS handles signed media.  In addition to the Secure Boot ON/OFF toggle, there is a BIOS switch that enables secure booting media that has Microsoft 3rd-party signing.  If this is enabled both OS-en will boot in secure mode, and one doesn’t have to forego that level of security.  Whew!  There’s no “Linux lockout” thankfully, but there is one more toggle in BIOS to get things working

X1 Yoga Gen 7 BIOS 3rd Party Certs – image updated


[Update 2022.04.14] For those interested in the nuts and bolts, here’s a picture of the internals.  Shown with the SSD removed from its socket, giving a good look at it, both thermal pads, and the heat spreader.

X1 Yoga Gen 7 Internals


Unresolved Issues – added 2022.08.06

Let’s call this the lingering frustration section 🙁  This is a very high-spec machine that should be a stellar performer.  In some ways it is, but there are a few things that aren’t performing as I think they should.  I’ve not been able to pin the issues down as to what might be the root cause(s): SVT (pre-customer-ship hardware), unique new hardware (mixed P and E cores and their management), operating system, app software, PEBKAC, or all of the above.

Some are Heisenbugs. I welcome any feedback.  In no particular order…

Virtual Machine Performance

This was a real surprise.  Benchmarks looked pretty good but one real-world use case was nasty.  Building a Ubuntu 21.10 virtual client with VMware Workstation Player took about 5 minutes on my X1 Yoga Gen 6.  On the Gen 7 it can take over 20 minutes.  Ouch.  Once built the VM client on the Gen 7 was just plain slow.

When starting a build on the Gen 7 VMware presents this:

X1 Yoga Gen 7 VMware Side Channel Mitigations Warning

Disabling side channel mitigations in the vmx file (requires first building an empty VM client, editing, then running the Ubuntu install) helps a bit.  Not much.

I found online discussions speculating that the problem was Workstation Player defaulting to using the E cores in the laptop.  Another .vmx edit adding thread lockouts also helped, but again, not much.  The .vmx addition including the mitigation disable and thread lockout entries:

Processor0.use = "TRUE"
Processor1.use = "TRUE"
Processor2.use = "TRUE"
Processor3.use = "TRUE"
Processor4.use = "TRUE"
Processor5.use = "TRUE"
Processor6.use = "TRUE"
Processor7.use = "TRUE"
Processor8.use = "TRUE"
Processor9.use = "TRUE"
Processor10.use = "TRUE"
Processor11.use = "TRUE"
Processor12.use = "FALSE"
Processor13.use = "FALSE"
Processor14.use = "FALSE"
Processor15.use = "FALSE"
Processor16.use = "FALSE"
Processor17.use = "FALSE"
Processor18.use = "FALSE"
Processor19.use = "FALSE"

What finally did make a major difference was going to Windows Settings and setting the power mode to “Best Performance” instead of “Balanced”.  This brought the build speed up to almost what the Gen 6 does.  Note that the Gen 6 was running in Balanced mode when doing 5 minute builds.

My strong suspicion is that best performance mode restricts apps to using the performance cores – at the OS level – rather than letting the app just use whatever got assigned (assigned by who/what… I have no idea).  Not a direct performance change – like raising CPU clock speeds – but restriction on cores used.

Toggling power modes is an emergency “fix” but not really acceptable in the long run. It shouldn’t be necessary and is particularly inappropriate when running on battery.  Whether the proper fix is with the OS’s core management or VMware’s… that’s above my pay grade.  I don’t know if this issue affects other applications.

Virtual Machine Bugs

An intermittent show-stopper.  Once a Ubuntu VM client is up and running, logging in is often impossible. When Workstation Player has focus the keyboard Caps Lock LED is lit and keyboard input isn’t possible at all.  Mouse still works.  The Gen 6 has no such problem.

Power, Temps, Fans

The Gen 7’s fans run pretty much non-stop at idle, and frequently sneeze/whoosh for a second or two – all for no reason that I can see. Temps at idle seem fine.  One thing I noticed is that idle CPU power consumption is at least twice that of the Gen 6.

CoreTemp Gen6 at Idle

CoreTemp Gen7 at Idle

A fresh install of the Lenovo OS image (and perhaps some updates) brought the idle power consumption down but fans still run at idle… and still sneeze.

[Update 2022.08.12] After reinstalling most of my apps and running updates processor power consumption at 2% load is back up to 4W+.  Fans continue to run at idle.

Another related concern is core temperatures under load.  Normal tasks like Windows updates can spike the P core temps to 100C.  They don’t stay that high for long, but perhaps fan management needs to be tuned a bit.  That seems too high.

Core Temp Gen 7 Updating


Linux vs Thunderbolt 4 Dock

This may well be something that has to be corrected by the Linux distros, but it’s a show-stopper.  When connected to a ThinkPad Universal Thunderbolt 4 dock, Linux – live and installed – is pretty much unusable.

Testing with Ubuntu 21.10 & 22.04, and Fedora 36b produce similar unfortunate results.  If the dock is connected things seem OK at first.  The only connected device is the LAN, and it appears to be working.  At login time, things get sideways.  The dock disconnects – as verified by the LAN LED going out.  This persists when rebooting to Windows.  No dock, no LAN.  It’s necessary to disconnect/reconnect the dock to get it back in Windows – where it seems to function correctly.

Both distros hang solid when attempting to do anything post-login with the dock connected.  If it survives long enough, the Fedora install option just spins for a while and exits.  Then hangs…

This does not happen with the Gen 6 + dock, nor does it happen with the Gen 7 when connected to the stock charger or to a Lenovo USB-C Mini Dock.

[Instant Update]  Good news 🙂  Lenovo Vantage just offered a dock firmware update.  It didn’t help this situation.  Ubuntu 22.04 LTS still b0rked the dock and eventually hung. But… back on the AC brick and ran the Ubuntu software updater.  Several updates and now it seems to be happy with the TB4 Dock.  Yay!

[Update 2022.08.08] Cancel the yay 🙁  It worked a couple of times… I swear.  But today we’re back to the same problems: After logging into Ubuntu the LAN LED goes out.  If I try to do much of anything – launch Firefox, select shutdown or restart from the dropdown – the display locks solid.  No response to kbd or mouse.  There is something still alive though, since un/replugging the USB-C connector produces tones.  Rats!  Still works fine on the charger.

Additional data point: connected to the dock but with the LAN cable unplugged, Ubuntu 22.04 seems fine (apart from the occasional shutdown hang) and wifi is usable.

As I said, feedback, comments, fixes gladly accepted.  And sorry for being so negative…

Posted in Uncategorized | Leave a comment

ThinkBook 14s Yoga: not (quite) a ThinkPad, but not too bad…

I’m a hard-core, dyed-in-the-wool, rabid, militant TrackPoint fan. I did not expect to like this ThinkBook as much as I do. It’s a tight piece of engineering, and other than missing that red nubbin, it’s a first-rate machine.  Slim, decent weight, good specs and options, a stylus, and an aluminum case.  And it’s a Yoga.

From time to time Lenovo sends me a gadget. They’re handy to have around – both for my own use and when trying to help out in the Lenovo forums. I do some testing and writing as well. Beyond the use of the laptop, I’m not otherwise compensated. Professional images are Lenovo’s. Amateur snapshots are mine. Opinions are exclusively mine. I do not work for, represent, or speak for Lenovo.

I’ve done my best to gather accurate information, but things are subject to change and correction.  Please double-check anything I say here before using it to make a purchase decision.

As usual, this is not quite a review.  More a survey of things that interest me.  We’ll dig into the details, but first – Lenovo images and a video  (edited).  Click on gallery for full-sized images.




Base Specifications:

ThinkBook 14s Yoga Sales Spec Snip – image Lenovo (edited)

Full base specifications:

ThinkBook 14s Yoga.pdf (local copy 2021.12.27)
ThinkBook 14s Yoga.pdf (
ThinkBook 14s Yoga – all PSREF pages, including models, specifications, photos, documentation, and service (



ThinkBook 14s Yoga Ports – image Lenovo (edited)

It’s worth noting that the fingerprint reader is incorporated with the power button,  which is on the right side.  It works surprisingly well, as does the one on the top deck of my ThinkPad X1 Yoga Gen 6.  All of my earlier ThinkPads that use the small square FPR have problems with reading my prints consistently.

Another thing to note is the privacy shutter that can cover the camera lens.  It’s small, easy to miss, and easy to accidentally slide over the lens.  You’d be surprised how many times someone shows up in the forums with a “defective” camera, only to leave humbled by that little thing.  It really is easy to miss.  Nice that the ‘Book shipped with a reminder 😉

ThinkBook ThinkShutter

Yet another nice touch: the sheet that protects the display from the keyboard during shipping includes some tips.  Thoughtful.

ThinkBook Keyboard Shipping Protector Tips


This unit’s specifications:

In brief:

  • Processor:  Intel® Core™ i5-1135G7 (4C / 8T, 2.4 / 4.2GHz, 8MB)
  • Graphics:  Integrated Intel Iris® Xe Graphics
  • Memory:  8GB Soldered DDR4-3200 + 8GB SO-DIMM DDR4-3200
  • Storage:  512GB SSD M.2 2242 PCIe 3.0×4 NVMe
  • Card Reader:  MicroSD Card Reader
  • Audio Chip:  High Definition (HD) Audio, Realtek® ALC3287 codec
  • Speakers:  Stereo speakers, 2W x2, Dolby® Audio™, Harman Speakers
  • Camera:  720p with ThinkShutter
  • Microphone:  2x, Array
  • Battery:  Integrated 60Wh
  • Max Battery Life:  MobileMark® 2018: 8.4 hr
  • Power Adapter:  65W USB-C (3-pin)
  • Display:  14″ FHD (1920×1080) IPS 300nits Glossy, Glass, 100% sRGB,
    Touch, Dolby Vision™
  • Touchscreen:  10-point Multi-touch
  • Keyboard:  Backlit, English (US)
  • Case Color:  Mineral Grey
  • Surface Treatment:  Anodizing Sandblasting
  • Case Material:  Aluminum (Top), Aluminum (Bottom)
  • Pen:  ThinkBook Yoga® Integrated Smart Pen
  • Dimensions (WxDxH):  320 x 216 x 16.9 mm (12.60 x 8.62 x 0.67 inches)
  • Weight:  1.5 kg (3.3 lbs)
  • Operating System:  Windows® 10 Pro 64, English
  • Ethernet:  None
  • WLAN + Bluetooth®:  11ax, 2×2 + BT5.1
  • Standard Ports:  1x USB 3.2 Gen 1, 1x USB 3.2 Gen 1 (Always On),  USB-C 3.2 Gen 2 (support data transfer, Power Delivery 3.0 and DisplayPort™ 1.4), Thunderbolt™ 4 / USB4™ 40Gbps (support data transfer, Power Delivery 3.0 and DisplayPort 1.4), HDMI® 1.4, microSD card reader, Headphone / microphone combo jack (3.5mm)
  • Security Chip:  Discrete TPM 2.0

In detail:

ThinkBook 14s Yoga 20WE001FUS.pdf (local copy 2021.12.27)
ThinkBook 14s Yoga 20WE001FUS – PSREF page (


Operating system and initial setup:

The machine shipped with Windows 10 Pro.  Windows 11 was offered during OOBE (out of box experience) and I accepted the offer.  It starts chugging away on the download in the background, and once Windows 10 is up and running it asks to update to ’11.

ThinkBook 14s Yoga OOBE Windows 11 Offered

I would normally have made local recovery media for Windows 10, but since the Lenovo Win 10 image was available I downloaded that instead.  Lenovo Digital Download Recovery Service (DDRS) – Lenovo Community    Once Win 11 was fully up – and updated – I made recovery media from that using the standard tool available in Windows 10 & 11 – as I have with other laptops: ThinkPad P1 Gen 2: a Beauty AND a Beast -> Initial Setup -> Locally created media.

Even though Windows 11 is shipping on new kit, it still seems it’s a work in progress. Some things are missing… or lost in the ozone somewhere… An example is hibernation.  It’s still possible to enable hibernation as an option in the shutdown menu, and it works.  What’s missing is the time setting that used to be available with sleep in the advanced settings.

Similarly on my X1 Yoga Gen 6 it’s the same story along with the Human Presence Detection (HPD) settings. They are still there in Commercial Vantage, but are not honored.  The search bar takes one to the Windows 11 sleep settings and suggests that’s where the controls are… but they aren’t there.

My WAG is that this is all part of MS deciding that all these sorts of controls should be gathered in settings.   OK, Fine… but how about actually putting them there after removing them from their traditional locations?  </soapbox>

A couple of other things that distress me – in both ’10 and ’11 – the incessant push to use an MS account as a login, and Bitlocker.  I recognize the advantages of both for convenience and security but that’s not the way I prefer to set up my laptops.

MS bangs away at trying to force an MS login.  At least with the Pro versions there’s a way to avoid that, although it’s often hidden in the fine print.

ThinkBook 14s Yoga OOBE Account Nag #1

ThinkBook 14s Yoga OOBE Account Nag #2

So sign me up for “Offline Account” and “Limited Experience”.

One of the things about an MS login that can cause some serious problems is that if a machine is capable of using Bitlocker, signing in that way will activate it.  The process should offer the key and store it in one’s MS account, but that too often gets missed by users. All is fine until later when they need to provide the key for forensics or recovery, or to simply access their drive after an update of OS or BIOS or some random event.

Even if Bitlocker isn’t fully activated the as-installed encryption will prevent other OSen like Linux from accessing the drive.  That’s a major problem if one is trying to salvage data, or simply setting up a dual-boot situation as I usually do.  Some of my machines provided a button in the Bitlocker management console (Control Panel -> System and -> Security -> BitLocker Drive Encryption or “bitlocker” in the search box) but some didn’t, even though the console was there.  I use a command line process to fully disable it.  In a CMD window run as Administrator:

ThinkBook 14s Yoga Disable Bitlocker

ThinkBook 14s Yoga No Longer Says Encrypted


Major components and performance:

Note: The performance tests and device information below were gathered while running Windows 11.


The “hidden” component.  This ThinkBook uses an insyde BIOS, not the Phoenix BIOS I’m used to in my ThinkPads.  It does have a GUI BIOS setup program that looks very similar to the one in my recent ThinkPads, and it appears to have the “self healing” feature.

ThinkBook 14s Yoga insyde BIOS

Navigating the BIOS setup GUI is inconsistent.  Scrolling via touchpad, for instance, sometimes works, sometimes doesn’t.  For now (hopefully this will be fixed) it may be necessary to use both touchpad and keyboard.

The BIOS is “Modern Standby” only (S0ix sleep) and does does not have an option to toggle modes to old-school S3 sleep.

ThinkBook 14s Yoga Modern Standby

NOTE: the BIOS is also missing a legacy boot mode option.  It is UEFI only.  Legacy mode has been deprecated: Legacy BIOS Boot Support Removed in Lenovo 2020 products.


The SSD slot supports PCIe/NVMe Gen 3 x4 and not the newer Gen 4.  The installed SSD takes nearly full advantage of Gen 3 performance.

ThinkBook 14s Yoga SSD Model and Performance


This ThinkBook doesn’t have an Ethernet port, although an inexpensive USB-C or USB-2.0/3.0 dongle could be used to provide one if needed.  The AX wifi card performs very well, and nearly saturates my Gigabit cable connection.

ThinkBook 14s Yoga Wifi Model and Performance


The ‘Book has plenty of RAM for virtual machines (although more would always be welcome) and the i5 can handle the load (although an i7 would be my choice if this was a purchased machine).  BIOS was already configured for virtualization so all I had to do was install VMware Workstation Player (free) and copy a few existing VMs over for testing.

ThinkBook 14s Yoga Virtual Machines

Battery runtime (not “life”):

Windows 11 no longer provides a “time remaining” estimate with the battery icon in the tool bar.  It wasn’t super accurate but it provided a very simple metric that for my ThinkPads seemed to be fairly close to the truth.

My admittedly simple runtime test consisted of running the appropriate software for 30 minutes or longer and noting the battery charge percentage drop reported.  All were at approximately half screen brightness, and one third volume.

Just sitting idle at the screen wallpaper or a quiet Edge browser the drop was about 2% per hour.  So forever… The media streaming tests were via wifi from a Windows host and gave roughly 15 hour runtime for MP3, and 12 hours for MP4.  I’d expect that with much else going on the results would be considerably lower, but I’d call this a 10hr+ battery.

ThinkBook 14s Yoga MP3 Battery Runtime – 40 minutes, 4% drop

ThinkBook 14s Yoga MP4 Battery Runtime – 60 minutes, 8% drop


Linux – live:

Something I always do with a new machine is boot one or more live Linux distros to take a quick look at what works – and what doesn’t.  It’s a very good indication of how a particular distro will work when installed (see below) and verifies that if I (or anyone…) needs to boot same for forensics or recovery it can be expected to function.

I went through my usual quick shakedown with Ubuntu 21.10, and everything I tried seemed to work well.  Also took a quick look with Fedora 34 and while it generally worked a few things didn’t.  They are noted below.

It wasn’t necessary to change  any BIOS settings to boot either distro.  Both will boot in secure mode.  The Ubuntu flash media was created my usual way: extract the contents of the ISO and drop them on a FAT32 flash drive.  The Fedora media was built using their tool.  They use their own partitioning and formatting which makes it a little difficult to build media manually.  It can be done – I’ve done it – but it may not be worth the fuss.

To boot USB media, hit F12 on startup or restart and select the drive from the boot menu.  NOTE: if Windows Fast Startup is enabled (it is by default) startup is more like resume from hibernation and it will be necessary to first shut down with SHIFT+Shutdown to get a full shutdown so the next startup will recognize F12 (or any other boot option key) but a restart should always permit using those keys.

ThinkBook 14s Yoga Boot Menu – Ubuntu

Odd that the BIOS recognizes Ubuntu as Linpus.  That seems to be common for many machines and BIOSen.

ThinkBook 14s Yoga Live Ubuntu Welcome

ThinkBook 14s Yoga Live Ubuntu Fully Booted

ThinkBook 14s Yoga Live Ubuntu Wifi

ThinkBook 14s Yoga Live Ubuntu Camera

ThinkBook 14s Yoga Live Ubuntu Speakers

ThinkBook 14s Yoga Live Ubuntu Microphone

Also verified that dedicated keys  – volume and brightness, shared with function keys – work.

ThinkBook 14s Yoga Live Ubuntu Bluetooth

ThinkBook 14s Yoga Live Ubuntu Stylus (… fine art …)

With Ubuntu 21.10 booted, all the “touch” stuff worked as expected: touchscreen, touchpad, and tablet mode.  With Fedora 34 one thing I noticed is that “tap to click” did not work on the touchpad.  Press to click did.

ThinkBook 14s Yoga Live Ubuntu Tablet Mode and On Screen Keyboard

ThinkBook 14s Yoga Live Ubuntu Windows Partition Access

NOTE: the above after Bitlocker disabled in Windows 11.

ThinkBook 14s Yoga Live Ubuntu Connect to Windows Network Shares

ThinkBook 14s Yoga Live Ubuntu Windows Network Shares Accessed

A note about how the screenshots were saved: when booted from a live USB flash drive the media is treated as if it’s a CDROM – it isn’t writable.  That can be changed via the command line.

ThinkBook 14s Yoga Live Ubuntu Copy to Flash Drive


Linux – installed:

The final exercise was an actual install of Ubuntu 21.10. Wow, what a difference from the old days.  In this new age of GPT drives and UEFI BIOS it’s nothing like the bad old days.  That and the sophistication of modern Linux installers make it simple and easy.

This went almost exactly as described in How to Dual Boot Ubuntu and Windows – the Picture Book Edition so I won’t go over it again here.  The only difference I noticed was due to the insyde BIOS.  The location of and procedure for changing boot order is  a bit different.  Access BIOS setup via F1 at boot or restart, then access the boot order “fine print” as shown below.  Note – again – that if Fast startup is still on in Windows (you should have turned it off by now if you’re doing a dual boot install) you need to either do a restart or SHIFT+shutdown then startup in order to access BIOS.

Ubuntu will put itself first in the boot order.  That can be changed.

ThinkBook 14s Yoga Ubuntu Post-install Boot Menu

ThinkBook 14s Yoga Ubuntu BIOS Boot Order


Bonus Mouse:

The ThinkBook wasn’t the only thing in the box when it arrived.  No, this isn’t an included option, it was a pure bonus.  The timing was perfect since my go-to Bluetooth mouse gave up the ghost during ‘Book testing.

The Lenovo Go Wireless Multi-device Mouse is a small wonder.  Two Bluetooth IDs and an included RF dongle – with the ability to use a mouse button to select which is active – allows pairing with three different host devices and switching from one to the other with ease.  Very handy.  It will charge via USB-C cable (provided) or wirelessly (charger not provided – I’ve charged it with my “brand S” phone charger.)  And it’s inexpensive.  What a nice bit of design and engineering.

ThinkBook and Mouse

ThinkBook, Mouse And Qi Charger



Lenovo Sales:  General  ThinkBook 14s Yoga

PSREF (specification) Pages:  General  ThinkBook 14s Yoga

Support:  General  ThinkBook 14s Yoga  User’s Guide  Hardware Maintenance Manual

Lenovo Forums:  All  ThinkBook  Linux

Linux:  Ubuntu  Fedora


Posted in Uncategorized | Leave a comment

Windows 10/11 ISO: install.wim too large for FAT32 Flash Drive

As I indicated in previous whinge post, the size of the install.wim file in Windows install ISOs can present some problems when creating USB flash install media: Windows 10 USB Install Media … or MS BS  This came up again when I wanted to try a pure clean install of Windows 11 on a ThinkPad X1 Yoga Gen 4.  The MS download site is offering the Windows 11 ISO to all visitors – not just non-windows hosts as it did with ’10 – and others may trip over this.

Some UEFI machines – ThinkPads for instance – will only boot FAT32 USB install media.  The multi-version ISO has an install.wim file too large for FAT32, so just dropping its contents on a FAT32 flash drive as I usually do won’t work.  The ISO produced by the MS media creation tool (so far) produces an install.esd file that will fit, but may not always be the desired option.

I’ve just come across another way to tackle this that allows creating FAT32 + NTFS media with the multi-version ISO, and may also be handy if using a custom install.wim file. First, this is not my invention.  Full credit and kudos to the sites and people linked below:

USB install media with WIM file larger than 4GB

Create bootable USB installer if install.wim is greater than 4GB

Very useful and bears repeating.  My take in detail … perhaps too much detail…

To recap, simply mounting the ISO with Windows Explorer or an archiving tool like 7zip and extracting the contents to a FAT32 flash drive won’t work.  It is possible with an NTFS drive, but ThinkPad UEFI BIOS isn’t NTFS-aware. (Some other brands and models are able to boot from NTFS media.)  There are ways to split the overlarge file using Windows or Linux tools from the command line. ( Windows:  Linux: )    Another reported possibility is using Rufus to create a split FAT32/NTFS drive but so far I’ve not found the appropriate options – if they exist at all.

The approach described in those links at the top of this article does make use of a flash drive with both FAT32 and NTFS partitions.  This is made possible by a pair of things: Windows now allows creation of – and access to – multiple partitions on a flash drive, and the unmodified windows installer is capable of finding the install.wim file in the NTFS partition.

SIDE NOTE: regardless of multiple posts on the interweb claiming that to do a UEFI install to a GPT main drive the flash drive must be GPT partitioned – that is not the case.  The MBR partitioning on most flash drives out of the box is fine.  Either for this split drive or the simpler FAT32-only drives I use for both Windows and Linux installs. In fact, the MS media creation tool builds an MBR/FAT32 flash drive.

The process in words and pictures using Windows in-built tools.  It should also be possible to do this from Linux.

Use Disk Management to delete any existing partition(s)

Create the FAT32 partition

1GB is sufficient

Make it FAT32 and name it if you like

And the NTFS partition

Use the rest of the drive – 7GB is enough

NTFS and name it if desired

Ready – specific drive letters are not important as long as they are assigned

Open ISO with Windows Explorer or (un)archiving or mount tool

Copy ISO contents to FAT32 but do not include sources folder

Contents minus sources copied

Use “New folder” button to manually create an empty sources folder in FAT32

Open the sources folder in the ISO and copy boot.wim to sources in FAT32

Copy entire ISO contents to NTFS partition

All copied

And that’s it.  It probably wasn’t necessary to copy all of the folders in both cases, but it was easier than figuring out what was required in each partition.

Eject the flash drive, plug into the target machine, boot or restart and access the boot menu (F12 on a ThinkPad). Install…

On the way…

And we’re up – this screenshot after Lenovo Commercial Vantage installed


Posted in Uncategorized | 1 Comment