X210s

[dmdsoftware]

Which RAM module did you end up using? Got a link?

I've already posted my RAM testing results here:
viewtopic.php?p=833449#p833449
Both modules are working fine. I can even put both in and have 20Gb RAM and stable system.

thanks for the link

[L29Ah]

Did a bunch of testing using memtestx86+. After a bunch of passes, 0 errors on both modules.

I've now managed to upgrade to the latest possible in debian (debian 9.7 with kernel 4.19). With both modules installed, I rarely can even get into a logged in state without the system crashing. If I run only with 1 module, I can make some fair use of the system before crashing. The first sign of trouble is checksum filesystem errors.

Maybe some odd BIOS setting or these boards are garbage.

By the way, do you update intel microcode? I tried, and it made the machine unstable and hanging/rebooting at heavy loads.

[tpg_anon]

So the X201s and the X200s chassis' are a better fit than the non-s models?
And are there any differences between the chassis of the X201s and the X200s?

[dmdsoftware]

Did a bunch of testing using memtestx86+. After a bunch of passes, 0 errors on both modules.

I've now managed to upgrade to the latest possible in debian (debian 9.7 with kernel 4.19). With both modules installed, I rarely can even get into a logged in state without the system crashing. If I run only with 1 module, I can make some fair use of the system before crashing. The first sign of trouble is checksum filesystem errors.

Maybe some odd BIOS setting or these boards are garbage.

By the way, do you update intel microcode? I tried, and it made the machine unstable and hanging/rebooting at heavy loads.

Good catch. I can definitely see how the intel microcode can become an issue. I thought it wasn't included in Debian (being not considered "free"), but it is one of the exceptions if you have contrib packages installed. I just checked, and my standard debian has the intel microcode package installed. I'll try removing it and seeing if it helps.

Thanks for the advice.

[L29Ah]

The most glaring issues are the lack of ALPM for NVMe drives and a nasty SATA controller issue which renders drives unreadable after resuming from suspend, requiring a hard reboot.

I don't have these. The sata controller resumes ok, and nvme ASPM can be turned on in the bios: you have to manually switch on L0sL1 and ASPM substates for the last PCIe lane in the config. Alternatively you could try the script http://drvbp1.linux-foundation.org/~mcg ... nable-aspm

After enabling L1 substates for M2 NVMe Linux no longer sees it in lspci.

[harryK]

I don't have these. The sata controller resumes ok, and nvme ASPM can be turned on in the bios: you have to manually switch on L0sL1 and ASPM substates for the last PCIe lane in the config. Alternatively you could try the script http://drvbp1.linux-foundation.org/~mcg ... nable-aspm

After enabling L1 substates for M2 NVMe Linux no longer sees it in lspci.

You also need to set a custom CLKREQ number to 4.
The CLKREQ number is 1 for PCIe port 4, and 0 for ports 1 and 2. Setting this number is a requirement to enable L1 substates.

[L29Ah]

After enabling L1 substates for M2 NVMe Linux no longer sees it in lspci.

You also need to set a custom CLKREQ number to 4.
The CLKREQ number is 1 for PCIe port 4, and 0 for ports 1 and 2. Setting this number is a requirement to enable L1 substates.

Thank you, it worked! I wonder why wasn't all this the default tho.

Also, does enabling L0s even make sense when there's L1? Doesn't "L0sL1" mode introduce unnecessary delay before switching off the transceivers?

[harryK]

You also need to set a custom CLKREQ number to 4.
The CLKREQ number is 1 for PCIe port 4, and 0 for ports 1 and 2. Setting this number is a requirement to enable L1 substates.

Thank you, it worked! I wonder why wasn't all this the default tho.

The stock bios defaults are a little bit.. erratic, to say the least

Also, does enabling L0s even make sense when there's L1? Doesn't "L0sL1" mode introduce unnecessary delay before switching off the transceivers?

They are two separate power states, it makes sense to enable both. However what gets activated depends on what the devices/drivers implement. Intel Wifi cards only implement L1, for instance. In my case I see

Code: Select all

# lspci -vv | grep -i lnkctl:
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+

The Realtek WLAN card activates L1 only with the r8168 module and L0s and L1 with the stock (patched) r8169. The last entry is the NVMe drive (970 Evo) which also only activates L1.

They all turn on L1 substates though

Code: Select all

lspci -vv | grep -i l1:
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+

[greenblob]

My screen has been acting up recently. The image won't show unless the top panel is at a very specific angle. I suspect the ribbon cable is bad. Is there a place where I can purchase a replacement?

[L29Ah]

By the way, do you update intel microcode? I tried, and it made the machine unstable and hanging/rebooting at heavy loads.

Good catch. I can definitely see how the intel microcode can become an issue. I thought it wasn't included in Debian (being not considered "free"), but it is one of the exceptions if you have contrib packages installed. I just checked, and my standard debian has the intel microcode package installed. I'll try removing it and seeing if it helps.

Thanks for the advice.

Have you solved it? If not, try intel_idle.max_cstate=1 i915.enable_dc=0

[L29Ah]

Is it me, or the top minipcie port doesn't work? Do i need to tweak something in the BIOS setup to bring it up? Alternatively, can anyone confirm whether it is working in coreboot?