What is the spec of the Intel Atom machine? Is it 64-bit?
$ grep flags /proc/cpuinfo | grep " lm "
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm dtherm arat
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm dtherm arat
$ sudo dmidecode -t processor
# dmidecode 3.4
...
Version: Intel(R) Atom(TM) CPU N2600 @ 1.60GHz
Voltage: 1.6 V
External Clock: 400 MHz
Max Speed: 1600 MHz
Current Speed: 1600 MHz
...
Core Count: 2
Core Enabled: 2
Thread Count: 4
Characteristics:
64-bit capable
$ sudo lshw -C processor | grep width
width: 64 bits
width: 64 bits
width: 64 bits
width: 64 bits
width: 64 bits
$ lscpu
Architecture: i686
CPU op-mode(s): 32-bit, 64-bit
...
Vulnerabilities:
Gather data sampling: Not affected
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Retbleed: Not affected
Spec rstack overflow: Not affected
Spec store bypass: Not affected
Spectre v1: Not affected
Spectre v2: Not affected
Srbds: Not affected
Tsx async abort: Not affected
ark.intel.com
So it does boot? If it wasn't able to boot you wouldn't get to see the boot menu. When exactly are you getting this error? I'm not too fond of pictures but in this case it would probably help identify the issue.
I understand. But Tier 2 doesn't mean it is ok to crash whenever it likes. This is abnormal for a mainstream BSD system to fail like this. This is a failure for a project. And this is old hardware. A ThinkPad, which is said to be most compatible with non-Windows systems. I haven't even tried it on Atom machine yet. Boy this is just unexpectedly bad.
It came with Windows 7 originally, which was 32-bit. Checked the BIOS settings, there isn't any settings related to 64-bit support or even No Execute / NX. It is a HP Mini 110-4100 machine with 2g of RAM. it could be that HP disabled 64-bit support.
Devuan daedalus (stable) i686
$ uname -mrs
Linux 6.1.0-17-686 i686
$ cat /etc/os-release
PRETTY_NAME="Devuan GNU/Linux 5 (daedalus)"
NAME="Devuan GNU/Linux"
VERSION_ID="5"
VERSION="5 (daedalus)"
VERSION_CODENAME="daedalus"
...It just shows the FreeBSD bootloader menu. When I press enter it tries to load the kernel and it fails with that message. I'll have to write the 64-bit image again to USB. Will run it and report on what it shows on screen (probably some time later).
There seems to be a problem with the BIOS.
Would love to have 64-bit support on that device, but flashing the BIOS seems risky. I don't have enough experience with this, neither have SPI flash clip etc. Besides there is no success mentioned with the process for the HP hardware.
What should I flash? I checked the links shared, searched around and found no HP Mini user saying that they have successfully enabled 64-bit support. Did you find anything?
What if Void Linux i686 runs fine on that Atom machine too? Should I give up on that machine still?
Good to hear. Can it play videos on mpv, with fullscreen/resize? Does acceleration work? What's your cpu model?
That is next on my list too.
No. I did not say there are installation issues on 64-bit. There are other reasons which I said earlier:
Give me some time and I'll install it. But the point is, even if it works on 64-bit, the problem still remains on 32-bit. 32-bit is still not discontinued (yet) and it crashes, has serious issues on a ThinkPad. On A ThinkPad!
Loading kernel...
/boot/kernel/kernel text=0x... ... ...
Loading configured modules...
cannot load '/boot/entropy'
cannot load '/etc/hostid'
CPU doesn't support long mode
Hit [enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
CPU doesn't support long mode
Type '?' for a list of commands, 'help' for more detailed help.
OKMy understanding is that if it was not supposed to work then it shouldn't have worked on Void Linux i686.
The CPU, yes. The AMD64/Intel 64 instructions are extensions on the IA-32 instruction set. This type of CPU is therefor still compatible with the original IA-32 instruction set. The Itanium for example has a true IA-64 instruction set, it is NOT compatible with IA-32. The original IA-32 platform is pretty much dead now though. There's even talk of actually removing the old IA-32 instructions from the next generation of CPUs.
It appears HP more or less crippled the hardware. See Charlie_ 's post on it. They probably did this so they can sell you a non-crippled version at a higher price.
The quote I commented on was about ThinkPad machine. Here's the full paragraph:
I'm testing FreeBSD 14 i386 on a ThinkPad x201i machine. This machine supports running 64-bit OSs. blackbird9's argument was that why run 32-bit when there is 64-bit support. There is logic behind the reasoning. I'd choose 64-bit OS normally too. I was testing it for using it later with Intel Atom machine. My point is that it is not working as expected. Video is not playing, if I can make it play with older mesa ports it slows down when I resize mpv window. And it crashes under default kernel. These issues are not there on Void Linux i686 Live XFCE image when I ran it on the same ThinkPad. I can play videos, resize mpv and it plays just fine. That's why I blamed FreeBSD implementation of Intel graphics drivers.
Well, you can complain about what is or you can run the way more stable 64bit version on your Thinkpad.
i686 is a 32-bit platform...
Yeah... that's why you're stuck using 32-bit OSes with it. So, go with FreeBSD i386, which will be compatible.
I got you. I previously said I'll install FreeBSD 64-bit and report back.
But I can show errors! I can describe issues.
Then tell me which configurations might be causing this.
I had to test Void Linux i686 because people were saying that ThinkPad x201i is old hardware, graphics acceleration will not work, and to replace it. Then it worked ok on Void. I wonder where are they now. Comparison was necessary here. And FreeBSD uses Linux drivers through LinuxKPI, so shouldn't it be relevant?
Yes. This ThinkPad x201i can give graphics acceleration on 32-bit Linux system. But not on FreeBSD 32-bit for some reason.
Maybe I will. But this issue isn't solved on the ThinkPad x201i machine. It seems to be an issue on the FreeBSD side.
$ uname -a
FreeBSD ... 14.0-RELEASE FreeBSD 14.0-RELEASE #0 releng/14.0-n265380-f9716eee8ab4: Fri Nov 10 05:57:23 UTC 2023 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
$ xdriinfo
Screen 0: crocus
$ glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel (0x8086)
Device: Mesa Intel(R) HD Graphics (ILK) (0x46)
Version: 23.3.2
Accelerated: yes
Video memory: 1536MB
Unified memory: yes
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics (ILK)
OpenGL version string: 2.1 Mesa 23.3.2
OpenGL shading language version string: 1.20
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 23.3.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
$ xvinfo
X-Video Extension version 2.2
screen #0
Adaptor #0: "GLAMOR Textured Video"
number of ports: 16
port base: 133
operations supported: PutImage
supported visuals:
depth 24, visualID 0x21
number of attributes: 5
"XV_BRIGHTNESS" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_CONTRAST" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_SATURATION" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_HUE" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_COLORSPACE" (range 0 to 1)
client settable attribute
client gettable attribute (current value is 0)
maximum XvImage size: 8192 x 8192
Number of image formats: 3
id: 0x32315659 (YV12)
guid: 59563132-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
id: 0x30323449 (I420)
guid: 49343230-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
id: 0x3231564e (NV12)
guid: 4e563132-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 2
type: YUV (planar)
$ glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
304 frames in 5.0 seconds = 60.665 FPS
302 frames in 5.0 seconds = 60.305 FPS
302 frames in 5.0 seconds = 60.305 FPS
...I said the above in the first post. Thankfully I found a FreeBSD 12.4 32-bit install. Graphics acceleration used to work on ThinkPad x201i with FreeBSD 12 32-bit. But it is not on 32-bit 13 and 14.
$ uname -a
FreeBSD ... 12.4-RELEASE FreeBSD 12.4-RELEASE r372781 GENERIC i386
$ xdriinfo
Screen 0: crocus
$ glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel (0x8086)
Device: Mesa Intel(R) HD Graphics (ILK) (0x46)
Version: 22.3.7
Accelerated: yes
Video memory: 1536MB
Unified memory: yes
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics (ILK)
OpenGL version string: 2.1 Mesa 22.3.7
OpenGL shading language version string: 1.20
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 22.3.7
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
$ xvinfo
X-Video Extension version 2.2
screen #0
Adaptor #0: "GLAMOR Textured Video"
number of ports: 16
port base: 133
operations supported: PutImage
supported visuals:
depth 24, visualID 0x21
number of attributes: 5
"XV_BRIGHTNESS" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_CONTRAST" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_SATURATION" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_HUE" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_COLORSPACE" (range 0 to 1)
client settable attribute
client gettable attribute (current value is 0)
maximum XvImage size: 8192 x 8192
Number of image formats: 3
id: 0x32315659 (YV12)
guid: 59563132-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
id: 0x30323449 (I420)
guid: 49343230-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
id: 0x3231564e (NV12)
guid: 4e563132-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 2
type: YUV (planar)I'm here.
pkg install vdpauinfo and run it. in terminal then post back here the output of "Decoder capabilities:" section for all video codecs.