Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Alex Atkin UK]

Thing is, the last bare bones I bought has random lockups, which was partly why I didn't this time.

Also apparently the N100 is very finicky with RAM.

[Alex Atkin UK]

Yes loaded on bootup.

I finally switched back to my N100 using a known good SATA SSD instead.

Where should I be looking to see if it is using the latest microcode?  Nothing seems to be mentioned in /var/log//dmesg.boot which I was under the impression is where it should be.

[Chrysalis]

x86info works.

From what what I can see, the info should be present in the boot logs (although not dmesg), so either check the system log right after booting or watch the console.

I think but am not sure this is the relevant microcode patch on my system.  It has high up time so I have no access to the console boot log, and also no hdmi cable available to plugin to my unit right now to check the console locally.

Code: [Select]

# ls -l /usr/local/share/cpucontrol/06-be-00.11
-rw-r--r--  1 root wheel 136192 Nov 29  2023 /usr/local/share/cpucontrol/06-be-00.11
It wont be the latest unless you move to a snapshots build.

The commands below.

'fetch -v https://pkg.freebsd.org/FreeBSD:14:amd64/latest/All/x86info-1.31.s03_1.pkg'
'pkg install x86info-1.31.s03_1.pkg'
select yes on the prompt which includes fetching some dependencies from pfSense repo.
'x86info -a | grep "Microcode version"'

This shows I am on version 011.

[Alex Atkin UK]

Well were on the same microcode, so hopefully I can eliminate that as being the reason it corrupted.