Ulf Frisk
Ulf Frisk
Try to avoid the probe command if possible. Probe is unfortunately super aggressive and if you're on AMD things are guaranteed to stop working until you reboot. You can check...
Thanks for the suggestion. I'll add a warning about it since it's not the first time I get this question. I'll add it probably on Thursday since I'll update some...
probing is super aggressive and you can try to dump memory instead, i.e. with `./pcileech dump -out none -device fpga -v` to see if things improve. possibly also use a...
You can try to add `-device fpga://algo=2` and retry, maybe it will be more stable (but also a bit slower unfortunately, but if it works the speed will still be...
To be honest I only recompile the `.ksh` kernel modules whenever I make a change in them. If Microsoft changed things around it may very well be that they broke....
It seems to be locating some memory before it starts to fail. You can try to use a memory map as per the instructions here: https://github.com/ufrisk/LeechCore/wiki/Device_FPGA_AMD_Thunderbolt to see if things...
I'm really sorry, but I don't have a Lenovo Legion 5 pro system to test against. You'd have to find some way to disable DMA and Kernel DMA protection in...
Nice to hear that you managed to get around / configure the SMMU to allow PCILeech. I haven't looked into attacking Android / ChromeOS or similar so I can't really...
Thunderbolt is quite well secured by default. But you indicate that you changed some settings. Also, Windows 11 employs a few protection techniques when the computer is locked in addition...
It seems like communicating with the device works fine, but DMA is not working. Ensure Thunderbolt security mode is set to no security / legacy in BIOS settings. Also if...