(Update: there is an updated hardware compatibility table in this post - as suspend/resume and hibernation as well as SD card reader work now with OpenBSD)
I’ve spent the last week with the InfinityBook Pro 14 Gen 6 as my primary laptop, so it’s time to give a first review. The one I’m using is equipped with the Intel i5-1135G7 - this is the 11th generation of the i5 called Tigerlake, two NVMe drives (Samsung SSD 980 PRO 500GB) and 16 GB of memory. I asked for the two drives in order to easily switch between OpenBSD and Linux. The tests I did with FreeBSD were done with an external SSD attached via USB. This is a first dive into covering this laptop - as I’m going to keep working with it for a while, there will be more to come.
When I initially received the Infinitybook and unpacked it I was actually very pleasently surprised by the haptics of the device. For once it is a really lightweight laptop, however it does not have a cheap touch to it. Throughout my professional life, I’ve mainly used Thinkpads as well as devices that originated from Cupertino so my standard is fairly high in that regard. The next surpise came when I turned it on and actually saw the display. It is really sharp and the resolution (2880x1800) is the type of high resolution I favor.
While the Infinitybook comes with a small sized charger it can also be supplied with power via USB-C, which means my usual setup at home (one 32” EIZO acting as a USB hub being connected to the laptop via USB-C supplying power as well as driving the display) works just as nicely. Configuration works easily with xrandr under OpenBSD. Aside from the USB-C external displays can be attached via hdmi - works just as good. Example output of xrandr(1) with my external display connected as well.
A few words on the keyboard. Well, aside from the display the most crucial part and I’m also very picky about keyboards. Admittetly I’m used to a bit of pain (having suffered from the Apple Macbook Pro Butterfly disaster). For a non-thinkpad and not mbp keyboard it is very good. It is not as pleasant as the keyboard in my 2020 MBP (the M1 edition), but close to.
So far the fans have not been bothering me at all. While stressing the system they do come on every now and then but are hardly to be heard.
As written above, I’m running in a dual boot configuraiton with OpenBSD and Linux. For the linux part I’ve chosen Manjaro and must say that it all “works out of the box”. Booted with a recent linux kernel I’ve not discovered anything that is not working as it should. I still have on my list to dive into the specifics that Tuxedo Computers published in their github repos.
The overall punchline is: Everything works out of the box. I’ve been basically using this laptop with a default linux installation including participating in video calls with bluetooth headsets and everything. Totally smooth. There was one tiny thing I adjusted:
I’m booting with
i915.enable_psr=0 to avoid screen flickering.
I’m running with OpenBSD-current - here a complete dmesg. What is currently not working properly:
One of the most crucial parts is wireless. The device comes with an Intel AX200. This is working nicely - thanks to stsp@’s work on iwx(4):
iwx0 at pci4 dev 0 function 0 "Intel Wi-Fi 6 AX200" rev 0x1a, msix iwx0: hw rev 0x340, fw ver 63.c04f3485.0, address a4:42:3b:f8:b6:91
Fn special keys all work and adjust the corresponding values visible via wsconsctl(8) and mixerctl(8).
cpu0 at mainbus0: apid 0 (boot processor) cpu0: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz, 4190.34 MHz, 06-8c-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,PT,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 256KB 64b/line disabled L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 38MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.1.184.108.40.206, IBE [...] cpu0: Enhanced SpeedStep 4190 MHz: speeds: 2401, 2400, 2300, 2100, 2000, 1800, 1700, 1500, 1400, 1300, 1100, 900, 800, 700, 500, 400 MHz
Battery status is properly reported via acpibat(4). From sysctl (device is currently charging):
hw.sensors.acpibat0.volt0=11.61 VDC (voltage) hw.sensors.acpibat0.volt1=12.57 VDC (current voltage) hw.sensors.acpibat0.current0=2.43 A (rate) hw.sensors.acpibat0.amphour0=4.57 Ah (last full capacity) hw.sensors.acpibat0.amphour1=0.00 Ah (warning capacity) hw.sensors.acpibat0.amphour2=0.00 Ah (low capacity) hw.sensors.acpibat0.amphour3=2.51 Ah (remaining capacity), OK hw.sensors.acpibat0.amphour4=4.57 Ah (design capacity) hw.sensors.acpibat0.raw0=2 (battery charging), OK
The webcam works nicely and can be disabled in the bios. There are two video devices reported, the webcam sits on video0.
uvideo0 at uhub1 port 6 configuration 1 interface 0 "SunplusIT Inc HD Webcam" rev 2.01/0.03 addr 4 video0 at uvideo0 uvideo1 at uhub1 port 6 configuration 1 interface 2 "SunplusIT Inc HD Webcam" rev 2.01/0.03 addr 4 video1 at uvideo1
(Update: there is an updated table in this post - as suspend/resume and hibernation as well as SD card reader work now)
This table is inspired by jcs who has - for each of the devices he tests with OpenBSD - such a table on his site:
|Audio||partially - no sound through speakers||azalia(4)|
|Bluetooth||no||OpenBSD has no bluetooth support|
|Hibernation||no||System does not hibernate fully|
|Keyboard backlight||yes||Fn+space - three different states|
|Micro SD Card Reader||no||theoretically supported by sdmmc(4), but problems initalizing cards|
|Suspend/Resume||no||System does not wake up properly from suspend|
|USB||yes||all USB ports work fine, including the USB Type C|
|Webcam||yes||uvideo(4) - can be disabled in BIOS|