Upgrading X220/X230 to FHD 1080p

[Matteone]

All backlight fuses are 3A/32V/Fast, usually have a letter P on them, and come in different sizes (most popular 0603), available from the likes of Mouser, Littlefuse, Bourns, Farnell, eBay, etc.

Thanks.I put my multi-meter in continuity mode. I get for all fuse connectivity. Just F6 seems blown. F7 is fine.

Redid all the work with a better multi-meter and can confirm that F6 is blown. All other fuses were fine. I bridged the F6 with a bit of solder to see if the machine does start and I get some beeps or display output. No luck so far. I was talking to somebody who said that maybe the U2 chip is broken. I have 3.3V on 1,2,3,8,7,6. When I understood the schematics right 4 is regulated by the machine. Is the chip fine when I have 0V at 4+ 5? Looks like no output at the moment.



I would like to order replacements. Ordering just one fuse is quite stupid. So I plan to order all fuses as replacements for my machines. Did I miss one fuse for the x230?

FUSE-1A32V-8-GP = 1A/32V, 0603 (1,6 x 0,8 mm)
FUSE-D5A32V-12-GP = 0,5A/32V, 0603 (1,6 x 0,8 mm)
FUSE-1D5A6V-10GP = 1,5A/6V, 1206, (3,2 x 1,6 mm)
FUSE-D5A13D2V-GP = 0,5A/13,2V, 1206, (3,2 x 1,6 mm)
FUSE-2A32V-7-GP = 2A/32V, 0603 (1,6 x 0,8 mm)
FUSE-7A24V-7-GP = 7A/24V, 1206, (3,2 x 1,6 mm)
FUSE-10A24V-GP = 10A/63V, 1206, (3,2 x 1,6 mm)
FUSE-3A32V-17-GP = 3A/32V, 0603 (1,6 x 0,8 mm)

[Matteone]

Another question: I also read somewhere when I use the x230 FHD Coreboot version that I do not need to solder one wire. Which one was that?

[munchausen]

@Matteone I have a friend who made a similar mistake, and when he took the board to a repair shop they told him the north bridge and several other chips were fried. Fortunately his quad core CPU was OK and he had it transplanted to a x230i motherboard. It might be better to cut your loses at this point and find a replacement motherboard.

[ips_clone]

Somehow it is now working correctly on the dock DP output.

I am trying to get brightness control working under Linux 5.14.5 which is the latest stable Linux. Unfortunately the linked patches in the FAQ are out of date. I tried to manually apply them to kernel 5.14.5 but had no success - the laptop booted with a blank screen.

Does anyone have a working 5.x patch?

Here are the modified files that I tried to get working without success:

Code: Select all

diff --git a/linux-5.14.5/drivers/gpu/drm/i915/display/intel_lvds.c b/intel_lvds.c
index 7f40e9f..f177b65 100644
--- a/linux-5.14.5/drivers/gpu/drm/i915/display/intel_lvds.c
+++ b/intel_lvds.c
@@ -519,209 +519,10 @@ static int intel_no_lvds_dmi_callback(const struct dmi_system_id *id)
 static const struct dmi_system_id intel_no_lvds[] = {
 	{
 		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Apple Mac Mini (Core series)",
+		.ident = "X230 Full HD Upgrade",
 		.matches = {
-			DMI_MATCH(DMI_SYS_VENDOR, "Apple"),
-			DMI_MATCH(DMI_PRODUCT_NAME, "Macmini1,1"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Apple Mac Mini (Core 2 series)",
-		.matches = {
-			DMI_MATCH(DMI_SYS_VENDOR, "Apple"),
-			DMI_MATCH(DMI_PRODUCT_NAME, "Macmini2,1"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "MSI IM-945GSE-A",
-		.matches = {
-			DMI_MATCH(DMI_SYS_VENDOR, "MSI"),
-			DMI_MATCH(DMI_PRODUCT_NAME, "A9830IMS"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Dell Studio Hybrid",
-		.matches = {
-			DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
-			DMI_MATCH(DMI_PRODUCT_NAME, "Studio Hybrid 140g"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Dell OptiPlex FX170",
-		.matches = {
-			DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
-			DMI_MATCH(DMI_PRODUCT_NAME, "OptiPlex FX170"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "AOpen Mini PC",
-		.matches = {
-			DMI_MATCH(DMI_SYS_VENDOR, "AOpen"),
-			DMI_MATCH(DMI_PRODUCT_NAME, "i965GMx-IF"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "AOpen Mini PC MP915",
-		.matches = {
-			DMI_MATCH(DMI_BOARD_VENDOR, "AOpen"),
-			DMI_MATCH(DMI_BOARD_NAME, "i915GMx-F"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "AOpen i915GMm-HFS",
-		.matches = {
-			DMI_MATCH(DMI_BOARD_VENDOR, "AOpen"),
-			DMI_MATCH(DMI_BOARD_NAME, "i915GMm-HFS"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-                .ident = "AOpen i45GMx-I",
-                .matches = {
-                        DMI_MATCH(DMI_BOARD_VENDOR, "AOpen"),
-                        DMI_MATCH(DMI_BOARD_NAME, "i45GMx-I"),
-                },
-        },
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Aopen i945GTt-VFA",
-		.matches = {
-			DMI_MATCH(DMI_PRODUCT_VERSION, "AO00001JW"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Clientron U800",
-		.matches = {
-			DMI_MATCH(DMI_SYS_VENDOR, "Clientron"),
-			DMI_MATCH(DMI_PRODUCT_NAME, "U800"),
-		},
-	},
-	{
-                .callback = intel_no_lvds_dmi_callback,
-                .ident = "Clientron E830",
-                .matches = {
-                        DMI_MATCH(DMI_SYS_VENDOR, "Clientron"),
-                        DMI_MATCH(DMI_PRODUCT_NAME, "E830"),
-                },
-        },
-        {
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Asus EeeBox PC EB1007",
-		.matches = {
-			DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK Computer INC."),
-			DMI_MATCH(DMI_PRODUCT_NAME, "EB1007"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Asus AT5NM10T-I",
-		.matches = {
-			DMI_MATCH(DMI_BOARD_VENDOR, "ASUSTeK Computer INC."),
-			DMI_MATCH(DMI_BOARD_NAME, "AT5NM10T-I"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Hewlett-Packard HP t5740",
-		.matches = {
-			DMI_MATCH(DMI_BOARD_VENDOR, "Hewlett-Packard"),
-			DMI_MATCH(DMI_PRODUCT_NAME, " t5740"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Hewlett-Packard t5745",
-		.matches = {
-			DMI_MATCH(DMI_BOARD_VENDOR, "Hewlett-Packard"),
-			DMI_MATCH(DMI_PRODUCT_NAME, "hp t5745"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Hewlett-Packard st5747",
-		.matches = {
-			DMI_MATCH(DMI_BOARD_VENDOR, "Hewlett-Packard"),
-			DMI_MATCH(DMI_PRODUCT_NAME, "hp st5747"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "MSI Wind Box DC500",
-		.matches = {
-			DMI_MATCH(DMI_BOARD_VENDOR, "MICRO-STAR INTERNATIONAL CO., LTD"),
-			DMI_MATCH(DMI_BOARD_NAME, "MS-7469"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Gigabyte GA-D525TUD",
-		.matches = {
-			DMI_MATCH(DMI_BOARD_VENDOR, "Gigabyte Technology Co., Ltd."),
-			DMI_MATCH(DMI_BOARD_NAME, "D525TUD"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Supermicro X7SPA-H",
-		.matches = {
-			DMI_MATCH(DMI_SYS_VENDOR, "Supermicro"),
-			DMI_MATCH(DMI_PRODUCT_NAME, "X7SPA-H"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Fujitsu Esprimo Q900",
-		.matches = {
-			DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"),
-			DMI_MATCH(DMI_PRODUCT_NAME, "ESPRIMO Q900"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Intel D410PT",
-		.matches = {
-			DMI_MATCH(DMI_BOARD_VENDOR, "Intel"),
-			DMI_MATCH(DMI_BOARD_NAME, "D410PT"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Intel D425KT",
-		.matches = {
-			DMI_MATCH(DMI_BOARD_VENDOR, "Intel"),
-			DMI_EXACT_MATCH(DMI_BOARD_NAME, "D425KT"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Intel D510MO",
-		.matches = {
-			DMI_MATCH(DMI_BOARD_VENDOR, "Intel"),
-			DMI_EXACT_MATCH(DMI_BOARD_NAME, "D510MO"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Intel D525MW",
-		.matches = {
-			DMI_MATCH(DMI_BOARD_VENDOR, "Intel"),
-			DMI_EXACT_MATCH(DMI_BOARD_NAME, "D525MW"),
-		},
-	},
-	{
-		.callback = intel_no_lvds_dmi_callback,
-		.ident = "Radiant P845",
-		.matches = {
-			DMI_MATCH(DMI_SYS_VENDOR, "Radiant Systems Inc"),
-			DMI_MATCH(DMI_PRODUCT_NAME, "P845"),
+			DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+			DMI_MATCH(DMI_PRODUCT_NAME, "2324B14"),
 		},
 	},

and

Code: Select all

diff --git a/linux-5.14.5/drivers/gpu/drm/i915/display/intel_dp.c b/intel_dp.c
index 862c1df..2f62218 100644
--- a/linux-5.14.5/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/intel_dp.c
@@ -105,7 +105,7 @@ bool intel_dp_is_edp(struct intel_dp *intel_dp)
 {
 	struct intel_digital_port *dig_port = dp_to_dig_port(intel_dp);
 
-	return dig_port->base.type == INTEL_OUTPUT_EDP;
+	return dig_port->base.type == INTEL_OUTPUT_EDP || strncmp(intel_dp->attached_connector->base.name, "DP-3", 4) == 0;
 }
 
 static void intel_dp_unset_edid(struct intel_dp *intel_dp);
@@ -4664,7 +4664,7 @@ bool intel_dp_is_port_edp(struct drm_i915_private *dev_priv, enum port port)
 	if (DISPLAY_VER(dev_priv) < 5)
 		return false;
 
-	if (DISPLAY_VER(dev_priv) < 9 && port == PORT_A)
+	if (DISPLAY_VER(dev_priv) < 9 && port == PORT_D)
 		return true;
 
 	return intel_bios_is_port_edp(dev_priv, port);

Hi, I missed that so thanks for pointing it out. I have just done the mod with some tape over the specific pins required using a microscope:

https://i.imgur.com/cIOH82y.png

This does not make DP#1 work unfortunately. I am using Linux.

I have an unmodded laptop that still works with DP#1 in case it matters. Any ideas what I am doing wrong? I double checked the pins that I've covered up match the image linked from the FAQ:

https://i.imgur.com/XjGmbz3.jpeg

Edit: to clarify, I have a different dock to that used in the instructional photo. My dock is 4338 on this page: https://support.lenovo.com/us/en/soluti ... 0-overview
and when I say DP#1 and DP#2 I am referring to the 2 DP ports on the back of the dock.

[munchausen]

I am using the following patch on 5.13:

Code: Select all

--- linux-oem-5.13-5.13.0/drivers/gpu/drm/i915/display/intel_dp.c	2021-10-10 21:21:22.000000000 +0100
+++ linux-oem-5.13-mod/drivers/gpu/drm/i915/display/intel_dp.c	2021-10-07 13:30:21.835011519 +0100
@@ -103,7 +103,7 @@
 {
 	struct intel_digital_port *dig_port = dp_to_dig_port(intel_dp);
 
-	return dig_port->base.type == INTEL_OUTPUT_EDP;
+	return dig_port->base.type == INTEL_OUTPUT_EDP || strncmp(intel_dp->attached_connector->base.name, "DP-3", 4) == 0;
 }
 
 static void intel_dp_unset_edid(struct intel_dp *intel_dp);
@@ -4655,7 +4655,7 @@
 	if (DISPLAY_VER(dev_priv) < 5)
 		return false;
 
-	if (DISPLAY_VER(dev_priv) < 9 && port == PORT_A)
+	if (DISPLAY_VER(dev_priv) < 9 && port == PORT_D)
 		return true;
 
 	return intel_bios_is_port_edp(dev_priv, port);
--- linux-oem-5.13-5.13.0/drivers/gpu/drm/i915/display/intel_lvds.c	2021-06-27 23:21:11.000000000 +0100
+++ linux-oem-5.13-mod/drivers/gpu/drm/i915/display/intel_lvds.c	2021-10-07 13:24:03.275263136 +0100
@@ -518,6 +518,14 @@
 static const struct dmi_system_id intel_no_lvds[] = {
 	{
 		.callback = intel_no_lvds_dmi_callback,
+		.ident = "ThinkPad x330",
+		.matches = {
+			DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+			DMI_MATCH(DMI_PRODUCT_NAME, "2325AEG"),
+		},
+	},
+	{
+		.callback = intel_no_lvds_dmi_callback,
 		.ident = "Apple Mac Mini (Core series)",
 		.matches = {
 			DMI_MATCH(DMI_SYS_VENDOR, "Apple"),

Note that probably the patches did not work for you because you must replace 2325AEG with whatever your machine reports from

Code: Select all

cat /sys/devices/virtual/dmi/id/board_name

Actually, it would make more sense to change the `DMI_MATCH(DMI_PRODUCT_NAME, "2325AEG"),` to `DMI_MATCH(DMI_PRODUCT_FAMILY, "ThinkPad X230"),`, and add another entry for X220, as this would match any x220/x230 instead of only specific configurations. Although in my case there is something wrong with my x230 in this respect and it only reports "ThinkPad" for product family (I am not sure if maybe this happened as a side effect of installing the quad core CPU)... which made it very hard to install 1vyrain and thinkpad-ec

I generally go through updating these patches with every kernel upgrade (though I also build out-of-tree to save building the whole kernel, which requires more patching). But I haven't got to 5.14 yet. The Makefile for my project automatically edits the patch with sed to put the right product name in place. I keep the patches on github but I need to get more practiced at updating them...

EDIT: I updated my repo with 5.13 patches. You should be able to just "make" "sudo make install"... and avoid having to rebuild the whole kernel... but no promises! https://github.com/static-void/i915-nolvds

[ips_clone]

Thank you so much. It now works great and I can dim the screen and enjoy long battery life. I had no idea about the cat thing.

Only (very minor) thing is that the lowest setting gives the brightest screen. The second lowest setting is the lowest brightness of screen. The third lowest setting is the second lowest screen brightness etc etc.

Note that probably the patches did not work for you because you must replace 2325AEG with whatever your machine reports from

Code: Select all

cat /sys/devices/virtual/dmi/id/board_name

[munchausen]

I have that issue with brightness too, but I got used to it. I am not sure if it's an issue in the kernel or the nitrocaster board.

[peddy22]

has anyone found a method for forcing the brightness OSD to appear in Windows 10? I am using 1vyrain with the disable LVDS patch, so the brightness dialog does not appear anymore - because there is no 'clone' display to use for this.

I'm using a custom script to read changes in brightness and send it to my FHD adapter serial port, and I could do this without the OSD but the OSD is nice.

Thanks

edit: this looks useful but I can't make sense of it

also this

[dthompson]

I got an itch to try this mod again after my last nearly successful but ultimately failed attempt, but I'm still stuck. I can't get the display to turn on at all. To reduce the number of variables, I reverted back to stock BIOS firmware instead of Coreboot with the FHD patch, removed the F1-J1 bridge, and soldered the power wire back onto the board. Continuity test with multimeter says that the soldering for the power wire is good, so why doesn't the display backlight turn on? Did I kill the display? What else can I test with my multimeter to track down the point of failure? An earlier post mentioned using the multimeter to check for a clean 3.3V between the nitrocaster board's power pad and a ground pin on a cable connector. I haven't been able to clearly identify such a ground pin, though. Could anyone point one out? I was hoping to take this one small step at a time and get the backlight to turn on before moving onto debugging any issues with the tiny through-hole connections.

Update: I looked at the schematic for the nitrocaster board and found a ground pin on the eDP connector. Multimeter reads 3.3V, so power is good. Should the display at least be turning on the backlight if it's receiving power? Starting to feel like I killed the display somehow.

[emultra]

Hello Thinkpad modders.

I just soldered in the nitrocaster board and got no image and no backlight to the lcd.

Continuity test on solder joints - ok
Continuity test on fuse F1 -ok
Set default display to DP#2
Reseated cables
When plugged into dock, no image from DP#1 or #2

When original panel is connected,
Original panel works.
DP#1 and #2 work

Just waiting on a new ribbon cable, edp cable and edp driver board to test lcd.
Any other troubleshooting steps I'm missing?

[peddy22]

Hello Thinkpad modders.

I just soldered in the nitrocaster board and got no image and no backlight to the lcd.

Continuity test on solder joints - ok
Continuity test on fuse F1 -ok
Set default display to DP#2
Reseated cables
When plugged into dock, no image from DP#1 or #2

When original panel is connected,
Original panel works.
DP#1 and #2 work

Just waiting on a new ribbon cable, edp cable and edp driver board to test lcd.
Any other troubleshooting steps I'm missing?

how did you test continuity on the docking pins?

[emultra]

I tested continuity from the solder through holes to the bottom of of the caps and then to the pins inside the dock connector.

[peddy22]

I tested continuity from the solder through holes to the bottom of of the caps and then to the pins inside the dock connector.

gotcha. the most common issue i've seen is poor solder connections. i had to use a hot iron for about 10 seconds on each joint to get a sufficient connection.

[ips_clone]

I have that issue with brightness too, but I got used to it. I am not sure if it's an issue in the kernel or the nitrocaster board.

Good news. I booted an Ubuntu live CD and the brightness controls worked perfectly on my new LCD, and in fact I think they made the screen brighter than it was with my modded kernel.

I did this to get the latest Ubuntu kernel that gave me a fully working screen:

Code: Select all

git clone git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git

I'm going to have a look at it tonight for differences.

[peddy22]

Docking my fhd X230: whenever the external LCD switches off (after 10min idle), it alternates between "monitor is going into sleep", turning off, then turning back on with the same message. When the laptop goes to sleep, it turns off properly.

I've taped the pins on the dock, yes.

However I am using the 51nb mod board.

Any ideas guys?

[peddy22]

Docking my fhd X230: whenever the external LCD switches off (after 10min idle), it alternates between "monitor is going into sleep", turning off, then turning back on with the same message. When the laptop goes to sleep, it turns off properly.

I've taped the pins on the dock, yes.

However I am using the 51nb mod board.

Any ideas guys?

Anyone?

Does NC have this issue?