However, I can still run strace program 2>&1 | grep cpuinfo, which will reveal something like: open("/proc/cpuinfo", O_RDONLY) = 3Īt this point, I can create a small library, cpuinfo. The program is copy-protected and tied to the serial, and I don't have the source code. For example, suppose a C program is using /proc/cpuinfo file to verify the serial number. My bad.Īs far as userspace programs are concerned, it's pretty easy to fool them and fake the contents of just about any file. What is the meaning of processor, physical id, siblings, core id, cpu cores in /proc/cpuinfo What is the meaning of the terms in /proc/cpuinfo Environment. This corresponds to the dmidecode output: ID: FB 06 00 00 01 03 00 00 matches a 06FB CPUID, i.e. Thus in your case it’s the CPU itself which is returning the Intel (R) Xeon (R) CPU E5335 2.00GHz string. The speed is obtained directly from the CPU and does apparently represent the thread processing speed, indicating that there is a small gap between that speed 2 and the actual running speed of the core which is most likely used for managing the threads. Your stealing" instead of answering the question. On x86, it uses the CPUID Processor Brand String feature, where supported. Also apologies to the asker, we all just gave you a "Why? Thats not nice. I honestly doubt that it was actually changed (on the CPU I mean), more like he changed some of the firmware code to return a different serial. I'd imagine that he is really just changing the source code that reads the serial and forcing it to return a different value. The information contained in /proc/cpuinfo while using an arm64 kernel contains less information than then 32-bit arm version, leading to the system not being recognized as a Raspberry Pi, e.g. This serial number is unique to every processor and is used by programs to identify individual processors. I'd say that as Dom has the source for the actual low level firmware. Intel’s processors have a unique serial number called pn, which is short for Processor Serial Number (PSN). Your unique serial is linked to the MP4 licence, so even if someone got your licence key, they will be unable to do anything with it (unless they could change the Raspberry Pi's serial number. pse: Page Size Extensions (4MB memory pages) 5. fpu: Onboard FPU(floating point support) 2. As that is the security around the licensing. See also Wikipedia and table 2-27 in Intel Advanced Vector Extensions Programming Reference 1. The only reason for changing the serial would be to copy someone else's MP4 licence and use it. To change the serial number would break the mechanism for codecĪdditionally as posted in the thread. And releasing any information to allow you we > should really show the same number in /proc/cpuinfo which means adding. However, I will leave this answer here for others searching for it.Dom has access to all the source code, the Videocore debugger and manyĬlosed VC specific tools. Is the use of the serial-number string property already. As per the updated question, the Atmel AT91SAM9 seems to not have this functionality. So one should interpret this /proc/cpuinfo entry as a 4-core CPU with hyperthreading. processor : 0 model name : ARMv7 Processor rev 10 (v7l) BogoMIPS : 3.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 CPU implementer : 0x41 CPU architecture: 7 CPU. Not all ARM SoCs support this functionality. My understanding so far has been that different cores within the same physical CPU would have different core id, and if core id s are identical, this is due to hyperthreading. I want to get CPU serial number,but serial from /proc/cpuinfo is 0.My kernel is Linux 4.1.152.0.0-g06465e7-dirty armv7l. It is also known that the reading can fail when u-boot is not properly configured. In the raspberry this number is generally used as a SN to buy a video codec license. And sometimes either software or configurations fail.įew use cases for the SID are, but not limited to: Getting Your Raspberry Pi Serial Number Using PythonĪbout this serial number : It is supposed to be unique, but it is read differently on different SoCs. (taken from my H3 based Soc, Orange Pi One with Armbian/Jessie kernel 3.4) (taken from my A20 based SoC, Lamobo R1 aka Banana Pi R1 and ArmBian/Jessie with kernel 4.5.2) grep Serial /proc/cpuinfo Get the serial of the device from /proc/cpuinfo grep Serial /proc/cpuinfo
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |