qualcomm_android_monitor_mode VS firmware-lenovo

Aircrack-ng

Use aircrack-ng to capture the WiFi 4-way handshake. Specifically;

https://www.aircrack-ng.org/ try this

I mainly used Wireshark and aircrack-ng

Under the right circumstances. https://www.aircrack-ng.org/

Have you looked at aircrack-ng?

I've had mixed results on laptops. I've never bothered to make the fingerprint reader work, that just isn't my thing. I've had decent luck with all the standard functions video, audio, storage, keyboard, mousepad, wifi on most models of Lenovo and Dell in the last decade. I've had mixed results on Asus laptops, especially the recent ones. The biggest challenge I've had is finding out ahead of time what wifi chipset is used and this has only affected me when using tools like aircrack-ng [1]. The way I quickly test how a laptop will behave is to boot Kali Linux [2] into ram. Sometimes a sales person at a computer store would let me do this on a demo model.

[1] - https://www.aircrack-ng.org/

[2] - https://www.kali.org/

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