@ChuckPa it’s a 12900K
So it’s currently a Kernel/Linux issue then?
Do you think the latest Kernel Index of /~kernel-ppa/mainline/v5.19-rc4 could help?
@ChuckPa it’s a 12900K
So it’s currently a Kernel/Linux issue then?
Do you think the latest Kernel Index of /~kernel-ppa/mainline/v5.19-rc4 could help?
I’m concerned.
The preinstall performs the same tests as postinstall.
If the IF test were to fail, it would have failed in preinstall.
Would you mind looking at the preinstall module?
If you’re using the update/bug fix I gave to Engineering, you’ll have:
Line#
610
611 # Where is Beignet available and viable ? (below 21.04)
612 [ "$DistroName" = "ubuntu" ] && [ $DistroVersion -lt 2100 ] && BeignetAvailable=1
613 [ "$DistroName" = "debian" ] && BeignetAvailable=1
614
615
616 # Beignet? - (KabyLake, GeminiLake, and CoffeeLake)
617 if [ $BeignetAvailable -eq 1 ]; then
618 [ $HaveIntelCore -gt 0 ] && [ $CPUSKU -ge 7000 ] && [ $CPUSKU -lt 10000 ] && NeedBeignet=1 && NeedOpenCL=1
619 else
620 [ $HaveIntelCore -gt 0 ] && [ $CPUSKU -ge 7000 ] && NeedIntelCompute=1
621 fi
622
623
624 # Intel Compute Runtime? - (CometLake, TigerLake, AlderLake, and above)
625 [ $HaveIntelCore -gt 0 ] && [ $CPUSKU -ge 10000 ] && NeedIntelCompute=1
626
As for the CPUSKU parsing, this is the code – which has not failed since first used.
600 # Attempt to determine QSV level based on CPU family (SKL, KBL, etc / selected Xeons)
601 CPUSKU="$(echo $Processor | sed -e 's/[^-]*-//' | sed -e 's/ .*$//' | tr -d '[A-Za-z]')"
So I wasn’t using the chuckpa-preinst.tar, I just tried that and I get:
./chuckpa.preinst: line 620: [: (): integer expression expected
./chuckpa.preinst: line 625: [: (): integer expression expected
Also if I try that line to only get CPU I get nothing returned:
cody@ubuntu:~/Downloads$ CPUSKU="$(echo $Processor | sed -e 's/[^-]*-//' | sed -e 's/ .*$//' | tr -d '[A-Za-z]')"
cody@ubuntu:~/Downloads$ echo $CPUSKU
I think I don’t have $Processor env variable set, which could be 100% user error:
cody@ubuntu:~/Downloads$ echo $Processor
^ It doesn’t return anything
If I do lscpu I get:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 46 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 24
On-line CPU(s) list: 0-23
Vendor ID: GenuineIntel
Model name: 12th Gen Intel(R) Core(TM) i9-12900K
CPU family: 6
Model: 151
Thread(s) per core: 2
Core(s) per socket: 16
Socket(s): 1
Stepping: 2
CPU max MHz: 5200.0000
CPU min MHz: 800.0000
BogoMIPS: 6374.40
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 syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopolo
gy nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdr
and lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clf
lushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq
tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 640 KiB (16 instances)
L1i: 768 KiB (16 instances)
L2: 14 MiB (10 instances)
L3: 30 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-23
Vulnerabilities:
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Enhanced IBRS, IBPB conditional, RSB filling
Srbds: Not affected
Tsx async abort: Not affected
It is interesting the post install sees it’s an Intel CPU.
User error? Need me to test anything else?
Oh no… You should not use ANYTHING here anymore.
I’ll remove all those packages.
If you go to the current PMS Beta download (plex.tv/downloads)
you’ll get the fully debugged and active code (pre and post install).
My post above is from the current BETA with one ‘hotfix’
Here, Run these two commands at the command line.
Processor="$(cat /proc/cpuinfo | grep 'model name' | uniq | awk -F ': ' '{print $2}' | awk '{print $3}')"
CPUSKU="$(echo $Processor | sed -e 's/[^-]*-//' | sed -e 's/ .*$//' | tr -d '[A-Za-z]')"
echo $Processor
echo $CPUSKU
Sure thing:
cody@ubuntu:~/Downloads$ Processor="$(cat /proc/cpuinfo | grep 'model name' | uniq | awk -F ': ' '{print $2}' | awk '{print $3}')"
cody@ubuntu:~/Downloads$ CPUSKU="$(echo $Processor | sed -e 's/[^-]*-//' | sed -e 's/ .*$//' | tr -d '[A-Za-z]')"
cody@ubuntu:~/Downloads$ echo $Processor
Intel(R)
cody@ubuntu:~/Downloads$ echo $CPUSKU
()
cody@ubuntu:~/Downloads$
show me cat /proc/cpuinfo | grep 'model name' | uniq
cody@ubuntu:~/Downloads$ cat /proc/cpuinfo | grep 'model name' | uniq
model name : 12th Gen Intel(R) Core(TM) i9-12900K
cody@ubuntu:~/Downloads$
THOSE BOZOS!
![]()
Intel change naming scheme?
yes they did.
[chuck@lizum ~.2002]$ cat /proc/cpuinfo | grep 'model name' | uniq
model name : Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz
[chuck@lizum ~.2003]$
Where were you when I was testing this? ![]()
Ha sorry been busy ![]()
This wouldn’t really be an issue though right, or rather this wouldn’t fix my issue? This is more for logging?
My issue is I am waiting on Linux to support the new CPU right? So for now nothing, Plex or I can do?
In Ubuntu 22.04, they will be releasing the 5.18 kernel
With this update to the packaging, I did remove the set -e .
This will allow it to install even with the error printing.
PMS will upgrade but I don’t know how it will do on a fresh installation.
5.18 kernel is the first kernel which supports the AlderLake computationally.
I don’t know when the support for video (DRM/HW transcoding) will reach sufficient maturity.
Your problem makes me rethink how I do CPUSKU processing.
The only consistency is that Intel seems to still maintain XX-YYYYYYY format.
e.g. model name : Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz
I think I’m going to need a regex to strip the first part and then strip everything from the @.
After doing that, CPUSKU will need overhauling.
There is a lot of work here. i have to burn down my existing work and start again.
Cool okay thanks for confirming I’ll hold tight then and software transcode ![]()
You need anything else for the logging/scheme change?
I’m good for now thanks.
I see that I need to do…
Oh well… Yet another packaging update ![]()
Sounds good thanks, job security at least ![]()
Signing off.
Want my job?
offers ![]()
![]()
care to try this little hatchet job for me?
I don’t like it. I need something more elegant which can also handle the N and G series CPUs if possible.
[chuck@lizum ~.2010]$ cat cpusku
#!/bin/bash
# find Intel CPUSKU anywhere in model name
Processor="$(cat /proc/cpuinfo | grep 'model name' | uniq)"
# Find the xx-yyyyy CPUSKU
pos=1
CPUSKU=""
while [ $pos -lt 16 ] && [ "$CPUSKU" = "" ];
do
Arg="$(echo $Processor | awk \{print\$$pos\} | grep \-)"
[ "$Arg" != "" ] && CPUSKU="$Arg"
pos=$((pos + 1))
done
CPUSKU="$(echo $CPUSKU | sed -e 's/[^-]*-//' | sed -e 's/ .*$//' | tr -d '[A-Za-z]')"
[ "$CPUSKU" = "" ] && CPUSKU=0
echo CPUSKU=\"$CPUSKU\"
[chuck@lizum ~.2011]$
Test cases:
[chuck@glockner ~.2003]$ cat /proc/cpuinfo | grep 'model name' | uniq
model name : Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz
[chuck@glockner ~.2004]$ ./cpusku
CPUSKU="2690"
[chuck@glockner ~.2005]$
[chuck@lizum ~.2011]$ ./cpusku
CPUSKU="8809"
[chuck@lizum ~.2012]$
Artificially injecting CPU info:
[chuck@lizum ~.2023]$ ./cpusku
CPUSKU="12900"
[chuck@lizum ~.2024]
Looks good
cody@ubuntu:~$ cat /proc/cpuinfo | grep 'model name' | uniq
model name : 12th Gen Intel(R) Core(TM) i9-12900K
cody@ubuntu:~$ ./cpusku
CPUSKU="12900"
cody@ubuntu:~$
Care to give something a try for me?