On Tue, 2025-08-19 at 21:40 -0400, Felix Miata wrote:
> Van Snyder composed on 2025-08-19 16:30 (UTC-0700):
> 
> > MS says Windoze 11 isn't
> > supported on Intel i5 
> 
> I suspect this is inaccurate. What I believe may be that Win11 is not
> supported on
> the particular i5 tested for support.

I asked Dell about Win11 on Latitude E5470 and the reply was "Microsoft
doesn't provide driver support" … "but many users report it works
anyway," I decided to install Windoze 10.

> 
> # inxi -SC
> System:
>   Host: ab250 Kernel: 6.12.38+deb13-amd64 arch: x86_64 bits: 64
>   Console: pty pts/0 Distro: Debian GNU/Linux 13 (trixie)
> CPU:
>   Info: quad core model: Intel Core i5-7500T bits: 64 type: MCP
> cache:
>     L2: 1024 KiB
>   Speed (MHz): avg: 800 min/max: 800/3300 cores: 1: 800 2: 800 3: 800
> 4: 800
> # /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --help | tail -11
> Shared library search path:
>   (libraries located via /etc/ld.so.cache)
>   /lib/x86_64-linux-gnu (system search path)
>   /usr/lib/x86_64-linux-gnu (system search path)
>   /lib (system search path)
>   /usr/lib (system search path)
> 
> Subdirectories of glibc-hwcaps directories, in priority order:
>   x86-64-v4
>   x86-64-v3 (supported, searched)
>   x86-64-v2 (supported, searched)
> #
> 
> # inxi -CS
> System:
>   Host: hp750 Kernel: 6.12.41+deb13-amd64 arch: x86_64 bits: 64
>   Console: pty pts/0 Distro: Debian GNU/Linux 13 (trixie)
> CPU:
>   Info: dual core model: Intel Core i5 660 bits: 64 type: MT MCP
> cache:
>     L2: 512 KiB
>   Speed (MHz): avg: 1200 min/max: 1200/3334 cores: 1: 1200 2: 1200 3:
> 1200
>     4: 1200
> # /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --help | tail -11
> Shared library search path:
>   (libraries located via /etc/ld.so.cache)
>   /lib/x86_64-linux-gnu (system search path)
>   /usr/lib/x86_64-linux-gnu (system search path)
>   /lib (system search path)
>   /usr/lib (system search path)
> 
> Subdirectories of glibc-hwcaps directories, in priority order:
>   x86-64-v4
>   x86-64-v3
>   x86-64-v2 (supported, searched)
> #
> 
> # inxi -CS
> System:
>   Host: k9msi Kernel: 6.12.41+deb13-amd64 arch: x86_64 bits: 64
>   Desktop: TDE (Trinity) v: R14.1.5~[DEVELOPMENT] Distro: Debian
> GNU/Linux
>     13 (trixie)
> CPU:
>   Info: dual core model: AMD Athlon 64 X2 5000+ bits: 64 type: MCP
> cache:
>     L2: 1024 KiB
>   Speed (MHz): avg: 2587 min/max: N/A cores: 1: 2587 2: 2587
> root@k9msi:~# /lib64/ld-linux-x86-64.so.2 --help | tail -11
> Shared library search path:
>   (libraries located via /etc/ld.so.cache)
>   /lib/x86_64-linux-gnu (system search path)
>   /usr/lib/x86_64-linux-gnu (system search path)
>   /lib (system search path)
>   /usr/lib (system search path)
> 
> Subdirectories of glibc-hwcaps directories, in priority order:
>   x86-64-v4
>   x86-64-v3
>   x86-64-v2
> #
> 
> Of the three installations above, the first two meet the v2
> "specification", but
> not the third. In all likelihood, M$ does an equivalent check to what
> is shown
> resulting above from Trixie, and below from openSUSE Leap, to see
> whether specific
> CPU features are available. Leap 16.0 due in October requires v2 as a
> minimum,
> while SUSE 16 according to the following URL will require v3.
> 
> <https://en.opensuse.org/X86-64_microarchitecture_levels>
> 
> I imagine Win11's requirements are different from *SUSE's, but the
> idea of
> requiring specific CPU features is not. Whether any i5s would fail to
> meet v2 I
> have doubts, as I believe the first post-Core2Duo/Core2Quad "Core"
> (e.g. i5-xxx)
> CPUs from Intel provide the minimum features constituting v2, though
> it could be
> i5-2xxx or even i5-3xxx. The Pentium and Celeron chips in the i3/5/7-
> 4xxx series
> do not meet v3, while the 3/5/7 do. Maybe for Win11 the minimum is
> stricter than v2.
> 
> # inxi -CS
> System:
>   Host: hp750 Kernel: 6.12.0-160000.19-default arch: x86_64 bits: 64
>   Console: pty pts/0 Distro: openSUSE Leap 16.0 Beta
> CPU:
>   Info: dual core model: Intel Core i5 660 bits: 64 type: MT MCP
> cache:
>     L2: 512 KiB
>   Speed (MHz): avg: 1200 min/max: 1200/3334 cores: 1: 1200 2: 1200 3:
> 1200
>     4: 1200
> # /lib64/ld-linux-x86-64.so.2 --help | tail -11
> This program interpreter self-identifies as: /lib64/ld-linux-x86-
> 64.so.2
> 
> Shared library search path:
>   (libraries located via /etc/ld.so.cache)
>   /lib64 (system search path)
>   /usr/lib64 (system search path)
> 
> Subdirectories of glibc-hwcaps directories, in priority order:
>   x86-64-v4
>   x86-64-v3
>   x86-64-v2 (supported, searched)
> #
> 
> # inxi -CS
> System:
>   Host: k9msi Kernel: 6.4.0-150600.23.60-default arch: x86_64 bits:
> 64
>   Console: pty pts/0 Distro: openSUSE Leap 15.6
> CPU:
>   Info: dual core model: AMD Athlon 64 X2 5000+ bits: 64 type: MCP
> cache:
>     L2: 1024 KiB
>   Speed (MHz): avg: 2587 min/max: N/A cores: 1: 2587 2: 2587
> k9msi:~ # /lib64/ld-linux-x86-64.so.2 --help | tail -11
> This program interpreter self-identifies as: /lib64/ld-linux-x86-
> 64.so.2
> 
> Shared library search path:
>   (libraries located via /etc/ld.so.cache)
>   /lib64 (system search path)
>   /usr/lib64 (system search path)
> 
> Subdirectories of glibc-hwcaps directories, in priority order:
>   x86-64-v4
>   x86-64-v3
>   x86-64-v2
> #
> 
> The i5 host hp750 would qualify to run Leap 16, but the Athlon X2
> host k9msi now
> running Leap 15.6 won't be able to upgrade to 16, or install it
> afresh. This kind
> of limitation looms as a potential in other distros to come, such as
> Forky,
> somewhat like Trixie shed 32bit support. :(

Reply via email to