Can you check /proc/cpuinfo flags for your cpu? I believe one of the listed features is missing (probably CMPXCHG16B)

x_wing の投稿を引用：

Can you check /proc/cpuinfo flags for your cpu? I believe one of the listed features is missing (probably CMPXCHG16B)

cpuinfo:

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
stepping : 10
microcode : 0xa0b
cpu MHz : 2477.639
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
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 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni tm2 ssse3 lahf_lm pti dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 4999.53
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

my motherboard is Gigabyte g41m-combo, and i have the latest version of BIOS (according to gigabyte's site - 26/02/2012).

microcodes - last version:

modprobe cpuid && iucode_tool -tb -lS /tmp/micro
iucode_tool: system has processor(s) with signature 0x0001067a
microcode bundle 1: /tmp/micro/intel-microcode-64.bin
selected microcodes:
001/041: sig 0x00010676, pf_mask 0x80, 2010-09-29, rev 0x060f, size 4096
001/042: sig 0x00010676, pf_mask 0x40, 2010-09-29, rev 0x060f, size 4096
001/043: sig 0x00010676, pf_mask 0x10, 2010-09-29, rev 0x060f, size 4096
001/044: sig 0x00010676, pf_mask 0x04, 2010-09-29, rev 0x060f, size 4096
001/045: sig 0x00010676, pf_mask 0x01, 2010-09-29, rev 0x060f, size 4096
001/046: sig 0x00010677, pf_mask 0x10, 2010-09-29, rev 0x070a, size 4096
001/047: sig 0x0001067a, pf_mask 0xa0, 2010-09-28, rev 0x0a0b, size 8192
001/048: sig 0x0001067a, pf_mask 0x44, 2010-09-28, rev 0x0a0b, size 8192
001/049: sig 0x0001067a, pf_mask 0x11, 2010-09-28, rev 0x0a0b, size 8192
linux-ocjh:/home/rchnh2cooh/Downloads/intel-microcode-3.20151106.1 # dmesg | grep "updated"
[] microcode: microcode updated early to revision 0xa0b, date = 2010-09-28

Ok, in the flags cx16 is not listed and there is a report already:

https://github.com/ValveSoftware/steam-for-linux/issues/7046

But as is stated in that thread, some CPU do support the instruction but are wrongly detected. In your case, your CPU seems to support that instruction:

http://www.cpu-world.com/CPUs/Xeon/Intel-Low%20voltage%20Xeon%20L5420%20-%20EU80574JJ060N%20-%20AT80574JJ060N%20(BX80574L5420A).html


So maybe you can use the workaround mentioned in the thread:

x_wing の投稿を引用：

Ok, in the flags cx16 is not listed and there is a report already:

https://github.com/ValveSoftware/steam-for-linux/issues/7046

But as is stated in that thread, some CPU do support the instruction but are wrongly detected. In your case, your CPU seems to cpu that instruction:

http://www.cpu-world.com/CPUs/Xeon/Intel-Low%20voltage%20Xeon%20L5420%20-%20EU80574JJ060N%20-%20AT80574JJ060N%20(BX80574L5420A).html


So maybe you can use the workaround mentioned in the thread:

cp /proc/cpuinfo /etc/cpuinfo nano -w /etc/cpuinfo # and add lm, cx16 and pni to all of the flags lines. mount --bind /etc/cpuinfo /proc/cpuinfo

this method isn't work. cpuinfo contains modified info, but steam client still is not running.

Can you share the file that you modified? (i.e. /etc/cpuinfo)

x_wing の投稿を引用：

Can you share the file that you modified? (i.e. /etc/cpuinfo)

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
stepping : 10
microcode : 0xa0b
cpu MHz : 2473.901
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 cx16 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 sse3 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni tm2 ssse3 lahf_lm pti dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 4999.84
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
stepping : 10
microcode : 0xa0b
cpu MHz : 2448.017
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 cx16 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 sse3 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni tm2 ssse3 lahf_lm pti dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 4999.84
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
stepping : 10
microcode : 0xa0b
cpu MHz : 2284.587
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 cx16 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 sse3 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni tm2 ssse3 lahf_lm pti dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 4999.84
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
stepping : 10
microcode : 0xa0b
cpu MHz : 2489.869
cache size : 6144 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 cx16 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 sse3 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni tm2 ssse3 lahf_lm pti dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 4999.84
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
power management:

@xwing
nice catch figuribg out their checker is a bash script!

also this means it's easier to debug and approach Valve later with proosed fixes, as we know exactly how they run their checks

Marlock の投稿を引用：

@xwing
nice catch figuribg out their checker is a bash script!

also this means it's easier to debug and approach Valve later with proosed fixes, as we know exactly how they run their checks

FYI It's not a bash script, steam-runtime-check-requirements is a binary exe that's part of the steam runtime (I discovered a man page entry that allowed me to emulate the error he was getting).

@xwing
thank you so much
soooo much so you can't imaging
you saved me and my money)

oh, pity!

in any case, it's nice to know that it can still be replaced by a dumb script

RCHNH2COOH の投稿を引用：

@xwing
thank you so much
soooo much so you can't imaging
you saved me and my money)

Good to know it worked! Bare in mind that the issue can come back whenever steam updates the runtime. Anyway, running once again the script should fix it.

Also, it's weird that cpuinfo doesn't list as supported this instructions. In the end this may be a motherboard bug (some mentioned that updating their bios fixed the issue) or a kernel bug.

x_wing の投稿を引用：

Good to know it worked! Bare in mind that the issue can come back whenever steam updates the runtime. Anyway, running once again the script should fix it.

Also, it's weird that cpuinfo doesn't list as supported this instructions. In the end this may be a motherboard bug (some mentioned that updating their bios fixed the issue) or a kernel bug.

I'd really prefer such a solution. They're probably not asking for the instruction just for fun...

Zyro の投稿を引用：

x_wing の投稿を引用：

Good to know it worked! Bare in mind that the issue can come back whenever steam updates the runtime. Anyway, running once again the script should fix it.

Also, it's weird that cpuinfo doesn't list as supported this instructions. In the end this may be a motherboard bug (some mentioned that updating their bios fixed the issue) or a kernel bug.

I'd really prefer such a solution. They're probably not asking for the instruction just for fun...

Yes to that!

Figuring out how to silence the error is progress for your situation, but should be treated as a temporary workaround...

The refusal to run is due explicitly to safety concerns and when those concerns are linked to a web browser, they are much more likely to hit you if ignored.

So don't forget the alarm is turned off and start looking for a fix for enabling the instruction as soon as you have a chance.

I know this is somewhat of an old thread but is also the only information out there to fix this issue, but, when I run the commands above for some reason I get:
"mv: cannot move 'FakeCheck' to '~/.steam/bin/steam-runtime/amd64/usr/bin/steam-runtime-check-requirements': No such file or directory"
(this is my own directory) the file is located there, i'm not sure why it is not seen?
I have manually copied the file and this fixes nothing.