There are three chips we should talk about to clarify this:
i7-3632QM (listed by Nitrokey, not compatible with Qubes OS)
i7-3740QM (the one I used, NOT listed by Nitrokey)
i7-3840QM (listed by Nitrokey)
The i7-3632QM is that fastest 4 core 35 watt chip Intel makes and the socket 2 version of it, which you would need for the T430 does not have Vt-d. Although there is a i7-3632QM version that has it, but that one can't be used with the T430.
I originally ordered a i7-3632QM because I wanted to stay within the 35 watt design of the T430 and then found out that it lacks Vt-d when I tried to install Qubes OS. I asked Nitrokey about it and they continued to tell me that their i7-3632QM would have Vt-d. Then @Plexus made a post on the Qubes OS Forum regarding this and alerted the Qubes OS Team and that's when Nitrokey added the warning you saw.
You can however also use 45 watt chips with the T430 if you mod the cooling (like I've done). In that case the fastest chip is the i7-3840QM as offered by Nitrokey.
The one I've used is the i7-3740QM which was recommended by @Plexus. It's a tiny bit less powerful than the i7-3840QM but about half the price (if you shop right and not just go for the first listing on Amazon as I did).
Bottom-line: the i7-3740QM has Vt-d and works perfectly with Qubes OS!
Awesome work Sven and thank you for being the “one hard t430” guide collaborator and alpha tester. I have so many permutations of T430 in my home right now its hard to keep track of them all.
I will get the guide finished soon and change the repo to public so the community can benefit.,
Actually at least in the US the price difference is basically non-existent and I can't stand the fact that I *could* have a faster CPU. So I ordered the i7-3840QM and will pop it in / resubmit the HCL when it arrives.
I have to compliment your taste in hardware, I’m building almost exactly the same machine as we speak except for the SSD, I’m using a 1TB 870 Pro.
Although, I’m entirely new to coreboot and am trying to gather as much info as possible, I’m at the last stage before flashing but I am struggling to understand some of the config options.
If at all possible, could I have a look at your config file Sven as our builds are almost identical.
Also did you flash Coreboot with seabios and then internally flash heads?
Oh I see, okay that’s a key piece of info, thank you.
I am not aversed to research but Heads is seeming enigmatic, do you have any suggestions for guides etc. any advice you could give me would be much appreciated.
Will I have to add my FHD 1080p screen to the build?
I basically used whatever was the HEAD revision of the Heads project at that time. That worked reasonably well, but a few issues remained:
-> A weird seemingly random data corruption issue when restoring backups [1], which I cannot reproduce any longer. I suspect either the VRAM change (see below) or the switch to the 4.19 kernel (see below) or maybe a combination of both fixed it.
-> Distorted graphics (looked like random data in the video buffer) for the first 1-2 seconds when booting. This went away after setting 'gfx_uma_size=224M' in cmos.default and 'select USE_OPTION_TABLE' and 'select STATIC_OPTION_TABLE' in Kconfig. I use an external 4K screen and never checked if this is also an issue without it being connected. You might not need to do this.
-> Random freezes of the system ... this is clearly connected to the 5.4 kernel and never happens when using the 4.19 kernel. As long as the 4.19 kernel is supported I feel no pressure to do anything about it and hope that when the day comes, the newer kernel at that time will not have this issue anymore. There is some talk about this being connected to the i915 driver.
-> Some warnings about the CPU having issues when booting... that's a bug in Coreboot you can simply ignore. If you however want to fix it, just apply this fix [2] manually.