Talk:More System Information: Difference between revisions

From PS3 Developer wiki
Jump to navigation Jump to search
No edit summary
m (Reverted edits by 201.138.46.29 (talk) to last revision by Roxanne)
Tag: Rollback
Line 1: Line 1:
Thank you for taking time to read this message.Best regards,
=== Screenshot examples ===
* FW [http://imageshack.us/photo/my-images/832/img0007qsx.jpg 3.55 with strings spoofed to "True Blue v2.4"]<!--// sandungas //-->
* FW [http://666kb.com/i/c03rcbfae58uv9r4m.jpg 3.41ofw CECH-25xx example]<!--// sandungas //-->
* FW [http://img408.imageshack.us/img408/6233/04012012016.jpg 3.55 example]<!--// deroad //-->
* FW [http://img838.imageshack.us/img838/1074/cechj.jpg CECHJ04 3.55 example]<!--// mysis //-->
* FW [http://666kb.com/i/c09iu4e87wz0pajlc.jpg 3.55 CECHG example]<!--// ifcaro //-->
* FW [http://img824.imageshack.us/img824/2756/img0077os.jpg 3.55 (DEX) DevelopmentTool]
* FW [http://img812.imageshack.us/img812/953/img0029hf.jpg 3.56 example]<!--// TechnoDon //-->
* FW [http://img6.imageshack.us/img6/9382/img0017vv.jpg 3.56 Demonhades example]<!--// TechnoDon //-->
* FW [http://dl.dropbox.com/u/33281581/Image0261.jpg 3.65 example]
* FW [http://img266.imageshack.us/img266/9835/400tv.jpg 4.00 example]<!--// deroad //-->
* FW [http://img502.imageshack.us/img502/6174/img0053gj.jpg  4.00 example]
* FW [http://img26.imageshack.us/img26/5589/img0035vz.jpg  4.00 example] (SHOP)<!--// TechnoDon //-->
* FW [http://img189.imageshack.us/img189/5557/img0008dx.jpg 4.00 example] (DEX)
* FW [http://www.ps3hax.net/picture.php?albumid=663&pictureid=3591 3.41+ example] (CEX) <!--// garrettcorn from ps3hax //-->
* FW [http://img51.imageshack.us/img51/8382/15032010.jpg 4.11 ofw example] (CEX) <!--// Xpenet //-->
* FW [http://f.imgtmp.com/CGv35.jpg 4.11 ofw example]  CECHAxx or CECHBxx
* FW [[:File:8dhVe.jpg|Rogero 4.30 MFW example]] CECH2502B
* FW [https://dl.dropboxusercontent.com/u/109578126/CECH25-11_4.60_30_06_2014.jpg 4.60 ofw example] CECH-2511A


Below you will find a short overview of a study based on an analysis of 600,000 search queries, which then calculated the value of various local ranking parameters for each top-100 page.
<gallery>
File:MoreSystemInformation-CECHA01-102.JPG|[[CECHAxx|CECHA01]] with FW 1.02
File:IMG 0148.JPG|[[CECHAxx|CECHA00]] with FW 1.10
File:MoreSystemInformation-CECH2004B-270.JPG|[[CECH-20xx|CECH2004B]] with FW 2.70
File:MoreSystemInformation-CECH2004B-276.JPG|[[CECH-20xx|CECH2004B]] with FW 2.76
File:MoreSystemInformation-CECH2004B-280.JPG|[[CECH-20xx|CECH2004B]] with FW 2.80
File:MoreSystemInformation-CECH2004B-300.JPG|[[CECH-20xx|CECH2004B]] with FW 3.00
File:MoreSystemInformation-CECH2004B-301.JPG|[[CECH-20xx|CECH2004B]] with FW 3.01
File:MoreSystemInformation-CECH2004B-310.JPG|[[CECH-20xx|CECH2004B]] with FW 3.10
File:MoreSystemInformation-CECH2004B-315.JPG|[[CECH-20xx|CECH2004B]] with FW 3.15
File:MoreSystemInformation-CECH2004B-32100.JPG|[[CECH-20xx|CECH2004B]] with FW 3.21
File:MoreSystemInformation-CECH2004B-330.JPG|[[CECH-20xx|CECH2004B]] with FW 3.20
File:MoreSystemInformation-CECH2004B-340.JPG|[[CECH-20xx|CECH2004B]] with FW 3.40
File:MoreSystemInformation-CECH2004B-341.JPG|[[CECH-20xx|CECH2004B]] with FW 3.41
File:MoreSystemInformation-CECH2004B-342.JPG|[[CECH-20xx|CECH2004B]] with FW 3.42
File:MoreSystemInformation-CECH2004B-350.JPG|[[CECH-20xx|CECH2004B]] with FW 3.50
File:MoreSystemInformation-CECH2004B-355-spoofed.JPG|[[CECH-20xx|CECH2004B]] with FW 3.55 spoofed
File:MoreSystemInformation-CECH4004A-431.JPG|[[CECH-40xx|CECH4004A]] with FW 4.31
File:MoreSystemInformation-CECH4002C.jpg|[[CECH-40xx|CECH4002C]] with FW 4.31
File:CECH-2104A-pic1.jpg|[[CECH-21xx]] with FW 4.31
File:CECH-2104A-pic2.jpg|[[CECH-21xx]] with FW 4.31
File:CECH-2104A_-_pic1.jpg|[[CECH-21xx]] with FW 4.31
File:MoreSystemInformation-DECR-1000.jpg|[[DECR-1000]] with FW 3.55
File:8dhVe.jpg|More System Information on Rogero 4.30
</gallery>


===Syscon string format speculation===


Facts about Google’s Local Ranking
There are motherboards with 4.00 firmware with a string filled with zeroes after the "." (0000000000000000). This zeroes means that his SoftID includes all the needed patches (in other words... 4.00ofw contains no patches aplicables to this syscon)


There is a direct relationship between the numbers used in the names of the .pkg's and the info shown after the "." e.g: SYS_CON_FIRMWARE_01040402.pkg will be shown in screen as: 0E69.0001000400040002 (to convert the string just add a zeroed byte before every byte)


Is there at least one keyword in your list of keywords, like “keyword + City (or state)”, that you’d like to rank for?
Based in the numbers used in the patches them can be ordered in a timeline from "older to newer": 0100****.pkg 0101****.pkg 0102****.pkg 0103****.pkg 0104****.pkg 0105****.pkg (there are only patches for 6 different syscons in 4.00 firmware, but probably there are more syscon generations used in newer motherboards that doesn't need patches yet)


The only patch that doesn't follow this rules is SYS_CON_FIRMWARE_S1_00010002083E0832.pkg whose numbers string doesn't need conversion, but it keeps the format 00010002******** (its unknown why this patch is speciall, and if it uses a different install method than the others)


If so, then you’ll find the information below extremely useful! These findings are based on a large-scale research effort on Google’s local ranking algorithm, and highlights the importance of various local SEO ranking factors.


Note there are only 5 syscon hardware series known in this order: CXR713F120A, CXR713120-201GB, SW-30x, SW2-30x, and  SW3-30x


But before I go into further detail, let me take a moment to remind you that we are running a 20% Discount Special Offer for all 20-70 DA backlinks.
The SoftID versions are ordered chronologically, and are dependant of this hardware revisions of syscon. As an example the chronologicall order of SoftID availables for CXR713120-201GB is 0B8E--->0C16--->0D52--->0DBF--->0E69. After this SoftID the increasing numeration stops. In the next hardware revision of syscon (SW-30x series) the SoftID starts in 065D (is smaller than the previous series)... is not clear if this series continues with SW2-30x and later with SW3-30x because the numbers matches but the syscon hardware is a different series


The value used in SoftID is not an identifyer of syscon hardware itself, actually each syscon has several SoftiID compatibles (but this doesnt means that all the compatible versions can be installed because the syscon firmware contains code to initialize/manage/communicate with other components of the motherboard as cell, southbridge (and underlying starship?, sata/pata adaptor?), etc...). In the case of a syscon firmware installed in a compatible syscon but with an incorrect SoftID some components of the motherboard can stop working, the whole system unable to boot or permanently bricked


So, let’s briefly answer the question:
It seems CXR713F120A and CXR713120-201GB has the same package/pinout... so maybe this first 2 syscon models can be refered as "CXR713 series" his SoftID versions keeps the chronologically order. Then the "rare" version is "03FB" because there is a "jump" after it... maybe this strange behaviour in the versions is related with the "CP updates" ?


Note at the bottom of this page: http://www.ps3devwiki.com/wiki/Talk:System_Controller_Firmware (CXR713F120A syscon located ON the Communication Processor Board). Is the same component, but is an important change in the hardware, this can be a good reason to keep a different SoftID versioning for this "pre-release" DECR models


What is the priority of local SEO investment?
===Example tables (please help to fill it)===
{{Syscon Patches}}
*Table notes
**Is possible to add another interesting column "Syscon VER (UART command)" documented here: [[Syscon_Hardware#Syscon_UART]]. But we have only 1 example '''00000000 S1E 00 00 065D''', noted here because belongs to SoftID '''065D''' and gives a hint of the versioning used (S1E maybe is "Series 30" refered to "SW-30x part number")
**Based on [http://pastebin.com/ZMxvTxwL this code], the 4 numbers of the syscon firmware/patches are: major version, middle version, minor version, release version
----
i think that this will explain everything: http://pastebin.com/k8KHGkzB and these are the generation of the SC http://pastebin.com/aJ3gxRKx (probably the first group is the correct one).


Main Factors Impacting Local Ranking
<pre>
03FB -> 001111111011
0B67 -> 101101100111
0B8E -> 101110001110
0C16 -> 110000010110
0D52 -> 110101010010
0DBF -> 110110111111
0E69 -> 111001101001
065D -> 011001011101
0832 -> 100000110010
08A0 -> 100010100000
08C2 -> 100011000010
0918 -> 100100011000
098F -> 100110001111
</pre>


1. Links. While everyone understands that backlinks play a crucial part in local ranking, the lesser-known secret discovered by the study is that they have the strongest correlation to positive ranking. What really matters is how old your links are, target keywords usage and word count of on-page content. All of which helped towards creating positive local rankings.
[[User:Deroad|Deroad]] 19:06, 21 November 2012 (MSK)
 
 
2. Website factors. Not surprising, but use of the target keywords and the number of words on a page appeared to make a difference. Location pages with a lot of content tend to do better than those with smaller amounts.
 
 
3. Citations. While citations are important to establishing authority of a site, interestingly, the study found that citation did little to disrupt a site from its local ranking, especially if the site is already in Google’s Local Pack. This does not mean citation problems shouldn’t be fixed. It just confirms that while foundational in nature, citations do little to improve local rankings.
 
 
4. Factors related to Google My Business. The study’s results showed that, while inclusive in and of themselves, having a more complete Google My Business page did result in better local rankings. Given how these factors work, it’s difficult to determine the precise contribution of GMB factors to positive page rankings. However, factors such as verified business ownership, photos and good reviews in your GMB profile all helped with enhancing local rankings.
 
 
So, what does this mean
for your Local SEO Ranking strategy?
Well, for starters, you do need to tackle your citation issues ASAP.
 
 
And, if you are competing in a particularly competitive niche, you need to start acquiring backlinks – high-quality ones! – at the earliest. But more significantly, the results of the study lead us to conclude that Google’s organic Local SEO Ranking algorithm holds a lot more sway on Local Pack ratings than it did prior to its Pigeon upgrades.
 
Let a team of Pros give your site a Local Boost
 
With years of experience on our side, and in-depth knowledge of how Google’s Local SEO Ranking algorithm works, our team of professionals have already helped many of our clients:
 
  - get high quality backlinks (you can get the same now with 20% discount)!
 
  - enrich their site with top-notch content
 
  - get a long list of the citations as a BONUS for any of our backlinks package!
 
 
And that’s exactly what we’re offering you today! But you need to act NOW to take advantage of our special 20% discount offer, because the window is closing fast.
 
 
Chris Patterson
CEO, Assured SEO & Digital Consultancy

Revision as of 11:58, 24 June 2019

Screenshot examples

Syscon string format speculation

There are motherboards with 4.00 firmware with a string filled with zeroes after the "." (0000000000000000). This zeroes means that his SoftID includes all the needed patches (in other words... 4.00ofw contains no patches aplicables to this syscon)

There is a direct relationship between the numbers used in the names of the .pkg's and the info shown after the "." e.g: SYS_CON_FIRMWARE_01040402.pkg will be shown in screen as: 0E69.0001000400040002 (to convert the string just add a zeroed byte before every byte)

Based in the numbers used in the patches them can be ordered in a timeline from "older to newer": 0100****.pkg 0101****.pkg 0102****.pkg 0103****.pkg 0104****.pkg 0105****.pkg (there are only patches for 6 different syscons in 4.00 firmware, but probably there are more syscon generations used in newer motherboards that doesn't need patches yet)

The only patch that doesn't follow this rules is SYS_CON_FIRMWARE_S1_00010002083E0832.pkg whose numbers string doesn't need conversion, but it keeps the format 00010002******** (its unknown why this patch is speciall, and if it uses a different install method than the others)


Note there are only 5 syscon hardware series known in this order: CXR713F120A, CXR713120-201GB, SW-30x, SW2-30x, and SW3-30x

The SoftID versions are ordered chronologically, and are dependant of this hardware revisions of syscon. As an example the chronologicall order of SoftID availables for CXR713120-201GB is 0B8E--->0C16--->0D52--->0DBF--->0E69. After this SoftID the increasing numeration stops. In the next hardware revision of syscon (SW-30x series) the SoftID starts in 065D (is smaller than the previous series)... is not clear if this series continues with SW2-30x and later with SW3-30x because the numbers matches but the syscon hardware is a different series

The value used in SoftID is not an identifyer of syscon hardware itself, actually each syscon has several SoftiID compatibles (but this doesnt means that all the compatible versions can be installed because the syscon firmware contains code to initialize/manage/communicate with other components of the motherboard as cell, southbridge (and underlying starship?, sata/pata adaptor?), etc...). In the case of a syscon firmware installed in a compatible syscon but with an incorrect SoftID some components of the motherboard can stop working, the whole system unable to boot or permanently bricked

It seems CXR713F120A and CXR713120-201GB has the same package/pinout... so maybe this first 2 syscon models can be refered as "CXR713 series" his SoftID versions keeps the chronologically order. Then the "rare" version is "03FB" because there is a "jump" after it... maybe this strange behaviour in the versions is related with the "CP updates" ?

Note at the bottom of this page: http://www.ps3devwiki.com/wiki/Talk:System_Controller_Firmware (CXR713F120A syscon located ON the Communication Processor Board). Is the same component, but is an important change in the hardware, this can be a good reason to keep a different SoftID versioning for this "pre-release" DECR models

Example tables (please help to fill it)

Syscon Patches
[edit]
PS3 Model PS3 Type Motherboard Syscon Hardware SoftID.SysconPatch@SC Syscon Firmware Patches Notes
File Name Version Installed from
DECR-1000 0x01 TMU-520 CXR713F120A 0F3B.0000000000000000@SC v1.0.5c1_TMU510_u.bin v1.0.5 c 1 CP ver 1.33 Full firmware overwrite from Communication Processor
DEH-H1001-D 0x01 COOKIE-13 CXR713F120A 0B67.0000000000000000@SC n/a n/a n/a
DEH-H1000A 0x01 COK-001 (proto) CXR713F120A 0B67.0000000000000000@SC n/a n/a n/a
CECHAxx 0x01 COK-001 CXR713120 series 0B8E.0001000000000004@SC
0B8E.0001000000000005@SC
0B8E.0001000000000006@SC		 SYS_CON_FIRMWARE_01000004.pkg
SYS_CON_FIRMWARE_01000005.pkg
SYS_CON_FIRMWARE_01000006.pkg		 v1.0.0 release 4
v1.0.0 release 5
v1.0.0 release 6		 1.30 Firmware
1.81 Firmware
3.40 Firmware
CECHBxx 0x02
CECHCxx 0x03 COK-002 0C16.0001000100030002@SC
0C16.0001000100030003@SC		 SYS_CON_FIRMWARE_01010302.pkg
SYS_CON_FIRMWARE_01010303.pkg		 v1.1.3 release 2
v1.1.3 release 3		 1.81 Firmware
3.40 Firmware
CECHExx 0x04
CECHGxx 0x05 SEM-001 0D52.0001000200030002@SC SYS_CON_FIRMWARE_01020302.pkg v1.2.3 release 2 3.40 Firmware
CECHHxx 0x06 DIA-001 CXR714120 series 0DBF.0001000300030002@SC SYS_CON_FIRMWARE_01030302.pkg v1.3.3 release 2 3.40 Firmware
CECHJxx 0x07 DIA-002 0E69.0001000400040001@SC
0E69.0001000400040002@SC		 n/a
SYS_CON_FIRMWARE_01040402.pkg		 v1.4.4 release 1
v1.4.4 release 2		 Factory ?
3.40 Firmware
CECHKxx
DECR-1400 0x09 DEB-001 CXR713120 series 0E69.0001000400040001@SC n/a v1.4.4 release 1 Factory ?
CECHCxx 0x03 COK-002 with 65nm RSX CXR714120 series 0F29.0001000500000002@SC SYS_CON_FIRMWARE_01050002.pkg v1.5.0 release 2 3.40 Firmware Refurbished, new 65nm RSX, new syscon
CECHAxx 0x01 COK-001 with 40nm RSX CXR714120 series 0F38.0001000500010001@SC SYS_CON_FIRMWARE_01050101.pkg v1.5.1 release 1 3.41 Firmware Refurbished, new 40nm RSX, new syscon
CECHLxx 0x08 VER-001 SW-30x series 065D.0000000000000000@SC n/a n/a Factory No patches availables in System Firmware
CECHMxx
CECHPxx
CECHQxx
CECH-20xx 0x09 DYN-001 SW2-30x series 0832.00010002083E0832@SC SYS_CON_FIRMWARE_S1_00010002083E0832.pkg ??? 3.00 Firmware
CECH-21xx 0x0A SUR-001 08A0.0000000000000000@SC n/a n/a Factory No patches availables in System Firmware
CECH-25xx 0x0B JTP-001 or
JSD-001		 08C2.0000000000000000@SC n/a n/a Factory No patches availables in System Firmware
CECH-30xx 0x0C KTE-001 SW3-30x series 0918.0000000000000000@SC n/a n/a Factory No patches availables in System Firmware
CECH-40xx 0x0D MSX-001 or
MPX-001 or
NPX-001		 SW3-30x series 098F.0000000000000000@SC n/a n/a Factory No patches availables in System Firmware
CECH-42xx ? ? ? ? ? ? ? No patches availables in System Firmware
CECH-43xx ? ? ? ? ? ? ? No patches availables in System Firmware
Rows marked in grey are "reference tool" models
Rows marked in blue are "preproduction" models
Rows marked in red are "refurbished" models
  • Table notes
    • Is possible to add another interesting column "Syscon VER (UART command)" documented here: Syscon_Hardware#Syscon_UART. But we have only 1 example 00000000 S1E 00 00 065D, noted here because belongs to SoftID 065D and gives a hint of the versioning used (S1E maybe is "Series 30" refered to "SW-30x part number")
    • Based on this code, the 4 numbers of the syscon firmware/patches are: major version, middle version, minor version, release version

i think that this will explain everything: http://pastebin.com/k8KHGkzB and these are the generation of the SC http://pastebin.com/aJ3gxRKx (probably the first group is the correct one). 

03FB -> 001111111011
0B67 -> 101101100111
0B8E -> 101110001110
0C16 -> 110000010110
0D52 -> 110101010010
0DBF -> 110110111111
0E69 -> 111001101001
065D -> 011001011101
0832 -> 100000110010
08A0 -> 100010100000
08C2 -> 100011000010
0918 -> 100100011000
098F -> 100110001111

Deroad 19:06, 21 November 2012 (MSK)

Retrieved from "http://www.psdevwiki.com/ps3/index.php?title=Talk:More_System_Information&oldid=53881"