unetbootin VS firmware-lenovo

format your USB drive and then you can retry with your software again, or you can try with a piece of software I know works successfully. https://unetbootin.github.io/

Linux on a USB large enough to hold your files. Linux does not care what OS made the file. You mat be able to Boot from the USB. Access the BIOS and try it. UNetbootin can also be used to load various system utilities. https://unetbootin.github.io/

I think UNetbootin could create a bootable installer directly from your current drive.

This is what you want. Bootcamp is the old way to do it. You want to use This for making a usb

use rufus or unetbootin to make setup the drive

You want to test out? Get a live image. You can put it on a bootable flash drive, too (e.g., unetbootin). Changes to the computer then require your explicit consent. (If the Ubuntu partition is encrypted, you might not access the data from an other Linux except with the credentials, though.)

I have sometimes had problems with ubuntus and mints image writer. I have found the dd method to be more effective. Since the dd command has the potential to be dangerous you really want to make sure that the usb destination location is correct. dd will write over any drive you tell it to indiscriminately! If the dd option is not something you feel comfortable with there are other options as there are other live usb image writers out there for linux. I have used and liked unetbootin

Windows Update ran this morning and updated a few Lenovo system updates, after which my laptop can now no longer charge. Windows reports it as 0% while the Bios reports it as 7% - has anyone else updated and ran into this? On the below GitHub page, looks to be a known issue but wondered if anyone else has managed a workaround? https://github.com/fwupd/firmware-lenovo/issues/329

Another relevant issue report on github.

ya that service has been very helpful and tracking issues is great, but there can still be issues when installing. For example, I am dealing with a bug found in this list of issues: https://github.com/fwupd/firmware-lenovo/issues on one of my laptops.

Has anyone had any success getting the ThinkPad Thunderbolt 4 Docking Station to work reliably on Linux? I'm running Pop-OS! and as per https://github.com/fwupd/firmware-lenovo/issues/191 it hard crashes (locks) the machine on boot and Lenovo have seemingly abandoned the issue for Linux users, despite the cost of this thing.

Unfortunately a UEFI capsule firmware update actually uses the old version of the firmware to apply the new version. So if you've got a super-old existing version you might need to use Windows (sad face) or a bootable CD to update to a slightly newer version, and from there fwupd can work. Lenovo are supposed to include a "old bios must be newer than X" in the firmware metadata, and so if you can file a bug in https://github.com/fwupd/firmware-lenovo/issues with your old BIOS version included, I can make sure it doesn't happen to anyone else. Sorry!

I have the same issue, as do others (see https://github.com/fwupd/firmware-lenovo/issues/191). Seems Lenovo just don't bother with Linux these days, given it's been 8 months since this was reported.

It does seem that updating firmware might be the only thing to worry about. Do you use the program called fwupd, a.k.a. fwupdmgr? That program works well when it actually works. I have had many problems with it. (See here for problems it has on ThinkPads.) I suggest that you try it (if you have not already) and see whether it works for you. Or, if Pop_OS has some sort of GUI front-end for fwupd (does it?) then try that.

The issue tracker for Linux firmware update troubles with Lenovo hardware is here, BTW: https://github.com/fwupd/firmware-lenovo/issues