4 ms·
Bizarrely, this works fine in WSL (only missing max frequency), but doesn't work on Ubuntu Server running on bare metal. It identifies the CPU as Intel, but tha
by ryankrage77 6y ago
Bizarrely, this works fine in WSL (only missing max frequency), but doesn't work on Ubuntu Server running on bare metal. It identifies the CPU as Intel, but that's it.
- loeg 6y agoWSL1 is essentially bare metal and can run the CPUID instruction directly. WSL2 would run the same instruction, but it would trap cpuid in HyperV; passing-through some information, and synthesize other pieces (or at least, that's what I've seen other hypervisors do). Maybe the CPU in your Ubuntu machine is new and unrecognized by the program? I don't have any better guess.