From f481908135470d55124013bb8770148544979712 Mon Sep 17 00:00:00 2001 From: Nicholas Chin Date: Sun, 12 Nov 2023 20:14:08 -0700 Subject: README.md: Add references to Open Security Training The old Open Security Training site had a course called Advanced x86: BIOS and SMM Internals, which had a set of slides outlining the method to supress SMIs by changing the GBL_SMI_EN bit. Add a reference to it as this is where I originally learned of this method. --- util/dell-flash-unlock/README.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'util/dell-flash-unlock') diff --git a/util/dell-flash-unlock/README.md b/util/dell-flash-unlock/README.md index ba45ddcc..7d9b4b85 100644 --- a/util/dell-flash-unlock/README.md +++ b/util/dell-flash-unlock/README.md @@ -100,3 +100,7 @@ There are other possible protection mechanisms that the firmware can utilize, such as Protected Range Register settings, which apply access permissions to address ranges of the flash, similar to the IFD. However, the E6400 vendor firmware does not utilize these, so they will not be discussed. + +## References +- Open Security Training: Advanced x86: BIOS and SMM Internals - SMI Suppression + - https://opensecuritytraining.info/IntroBIOS_files/Day1_XX_Advanced%20x86%20-%20BIOS%20and%20SMM%20Internals%20-%20SMI%20Suppression.pdf -- cgit v1.2.1 From ca28255db8f18dbcd2db077fb18a6075792ad41c Mon Sep 17 00:00:00 2001 From: Nicholas Chin Date: Sun, 17 Dec 2023 18:02:29 -0700 Subject: README.md: Add instructions for relaxing memory permissions As this utility requires access to /dev/mem, the default protections of Linux and OpenBSD must be relaxed to allow this. Make a note of this in the instructions. --- util/dell-flash-unlock/README.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'util/dell-flash-unlock') diff --git a/util/dell-flash-unlock/README.md b/util/dell-flash-unlock/README.md index 7d9b4b85..fd000efc 100644 --- a/util/dell-flash-unlock/README.md +++ b/util/dell-flash-unlock/README.md @@ -8,6 +8,8 @@ E6400, which mainly seem to be the Latitude and Precision lines starting from around 2008 (E6400 era). ## TL;DR +On Linux, ensure you are booting with the `iomem=relaxed` kernel parameter. +On OpenBSD, ensure you are booting with securelevel set to -1. Run `make` to compile the utility, and then run `sudo ./dell_flash_unlock` and follow the directions it outputs. -- cgit v1.2.1 From ab59f9128c68508a5c92f6495a2cf1786dbe69ba Mon Sep 17 00:00:00 2001 From: Nicholas Chin Date: Sun, 17 Dec 2023 18:30:53 -0700 Subject: README.md: Add E6500, E6420, and E6530 as supported --- util/dell-flash-unlock/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'util/dell-flash-unlock') diff --git a/util/dell-flash-unlock/README.md b/util/dell-flash-unlock/README.md index fd000efc..0ade92a6 100644 --- a/util/dell-flash-unlock/README.md +++ b/util/dell-flash-unlock/README.md @@ -14,10 +14,10 @@ Run `make` to compile the utility, and then run `sudo ./dell_flash_unlock` and follow the directions it outputs. ## Confirmed supported devices -- Latitude E6400 -- Latitude E6410 -- Latitude E4310 -- Latitude E6430 +- Latitude E6400, E6500 +- Latitude E6410, E4310 +- Latitude E6420 +- Latitude E6430, E6530 - Precision M6800 It is likely that any other Latitude/Precision laptops from the same era as -- cgit v1.2.1 From d207e9bc4594421e2ff405cc0977bf4d876acfdc Mon Sep 17 00:00:00 2001 From: Nicholas Chin Date: Sun, 17 Dec 2023 18:39:55 -0700 Subject: README.md: Add possibly not working systems These systems have a report that the unlock utility does not work. Until there are multiple reports of failed unlocks and a technical determination of why it doesn't work, they will not be listed as explicitly unsupported. --- util/dell-flash-unlock/README.md | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'util/dell-flash-unlock') diff --git a/util/dell-flash-unlock/README.md b/util/dell-flash-unlock/README.md index 0ade92a6..cbe33dad 100644 --- a/util/dell-flash-unlock/README.md +++ b/util/dell-flash-unlock/README.md @@ -24,6 +24,15 @@ It is likely that any other Latitude/Precision laptops from the same era as devices specifically mentioned in the above list will work as Dell seems to use the same ECs in one generation. +## Tested +These systems have been tested, but were reported as not working with +dell-flash-unlock. This could be due to user error, a bug in this utility, or +the feature not being implemented in Dell's firmware. If you have such a system, +please test the utility and report whether or not it actually works for you. + +- Latitude E6220 +- Latitude E6330 + ## Detailed device specific behavior - On GM45 era laptops, the expected behavior is that you will run the utility for the first time, which will tell the EC to set the descriptor override on -- cgit v1.2.1