Hi so i tried booting the latest Beta for Bluefin LTS and it just stayed on the underscore blinking screen and it stopped blinking but i waited and it didnt boot.
Maybe you are not in UEFI mode?
But anyways, I recommend you to read this: Call for Testing: Bluefin LTS (Alpha) - #66 by j0rge
before going any further
1 Like
Do you only have Bluefin installed or do you dual boot with other operating systems present on the system? Also, did you try booting to other boot entries on the GRUB menu?
This is due to centos 10 dropping the x86_64/v2 architecture. T420 likely have a Sandy Bridge 2nd gen intel processor which dont support v2
“A notable change in this release is that the AMD/Intel 64-bit build now targets the v3 microarchitecture level.” CentOS Stream 10 Release Notes - The CentOS Project
AlmaLinux is building a v2 variant of centos 10 I can build Bluefin LTS images on v2 if there’s enough interest
Fedora still targets v2 too so you can use normal Bluefin
3 Likes
That would be amazing. I’m on a similar usecase, running Bluefin on a T430. Would love to run LTS on it.
1 Like
If your hardware is stuck on x86_64 v2 architecture you can check with:
/usr/lib64/ld-linux-x86-64.so.2 --help | grep ' x86-64'
In my case it is displayed:
x86-64-v4
x86-64-v3 (supported, searched)
x86-64-v2 (supported, searched)
If you have the hardware limitation issue you will only see “x86-64-v2” and others missing.
Interesting paradox. Users with older hardware want slower pace of hardware and software, so it should be: Blufin LTS, but because of x86_64_v2 limitation it requires newer hardware.
In this case in my humble opinion second best option is “Blufin GTS” and not “Blufin”.
3 Likes