Re: Xeon E3-1225 v2 Ivy bridge and MB DH67BL support

[tlaronde%polynum.com@localhost]

Le Wed, Aug 17, 2022 at 12:10:20PM +0200, tlaronde%polynum.com@localhost a écrit :
> Hello,
> 
> Context: Some weeks ago my ISP, without notice, switched my connexion
> to IPv6-CGNAT so I lost the ability to reach servers I manage, that were
> calling back to my IPv4 dynamic address. So, in emergency, I rent a
> baremetal server from OVH, to get an IPv4 back.
> 
> I tried to install NetBSD, using various methods starting by launching
> with a Linux rescue and writing to disk using qemu to installing a Linux
> Debian, resizing the Linux partition and trying a dual boot, with
> several variations (setting a flag in the MBR; chainloading from Debian
> GRUB2...) and without any success (this is the simplest offer, so
> there is no IPMI, and thus I can not see what is going on, or not,
> during the booting stage).
> 
> So I ended up leaving the Linux Debian and setting what I needed there,
> and I'm only going back to the problem now.
> 
> Before trying to build and install directly a raw image, can someone
> with a working NetBSD on Xeon v2 Ivy bridge with an Intel motherboard
> DH67BL confirm or infirm that NetBSD can, indeed, run on this?
> (This is ten years old hardware, so my guess was: yes very probably,
> but a confirmation would be better.)
> 

Partially answering to myself: mention of Ivy bridge is found here:

src/sys/arch/x86/pci/imcsmb/imc.c

with the following comment:

/* Depending on the motherboard and firmware, the TSODs might be polled by
 * firmware. Therefore, when this driver accesses these SMBus controllers, the
 * firmware polling must be disabled as part of requesting the bus, and
 * re-enabled when releasing the bus. Unfortunately, the details of how to do
 * this are vendor-specific. Contact your motherboard vendor to get the
 * information you need to do proper implementations.
 *
 * For NVDIMMs which conform to the ACPI "NFIT" standard, the ACPI firmware
 * manages the NVDIMM; for those which pre-date the standard, the operating
 * system interacts with the NVDIMM controller using a vendor-proprietary API
 * over the SMBus. In that case, the NVDIMM driver would be an SMBus slave
 * device driver, and would interface with the hardware via an SMBus controller
 * driver such as this one.
 */

Hence, the question is still opened. And furthermore:

> Auxiliary question: there is no graphic card. Is there the necessity to
> configure the second stage bootloader to not start anything fancy about
> the framebuffer or the default configuration will bypass this without
> ado?

This can be found here (several files):

src/sys/external/bsd/drm2/dist/drm/i915/

There is a Processor Graphics support : Intel® UHD Graphics P630, for
the processor, from datasheet, but what may be the link between
this and drm support and possible failure at boot time due precisely
to framebuffer support?

TIA,
-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                     http://www.kergis.com/
                    http://kertex.kergis.com/
                       http://www.sbfa.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C