Talk:Resizing VFLASH Storage Device: Difference between revisions

From PS3 Developer wiki
Jump to navigation Jump to search
m (Created page with "Example of storage regions after installing debian (root=/dev/ps3vflashh3) '''ps3d - 3 accessable regions''' ps3da : 114473 MiB (234441648) ps3db : 74281 MiB (152128408) ps3...")
 
mNo edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 20: Line 20:
   ps3vflashh1 () ps3vflashh2 (swap) ps3vflashh3 (ext3)
   ps3vflashh1 () ps3vflashh2 (swap) ps3vflashh3 (ext3)


note: ps3dc is used by the PS3 as temp for installing updates. When installing PUP files, the content gets unpacked there, checked - the system flags the update bit and reboots. After reboot it sees the update bit and installs the files from ps3dc without rechecking (!)
notes: ps3dc is used by the PS3 as temp for installing updates. When installing PUP files, the content gets unpacked there, checked - the system flags the update bit and reboots. After reboot it sees the update bit and installs the files from ps3dc without rechecking! (only in older version though)
 
ps3dd (if present) is the partition made by 3.15 and older OtherOS from the XMB
 
graf proposes in [http://grafchokolo.com/ps3-development-page.html/comment-page-10/#comment-3964 his howto/guide] to partition the vflash region 7 (ps3vflashh) as follows:
 
ps3vflashh
  ps3vflashh1 (FAT) 100 MiB boot partition for later use
  ps3vflashh2 (SWAP) 2 GiB shared swap space
  ps3vflashh3 (EXT3) 20 GiB for Gentoo
  ps3vflashh4 (EXT3) 20 GiB for Debian
 
----
 
== original phat ps3's with 256mb nand flash ==
 
Q: Does this work on these models?
A: Use OtherOS++ that method seems to be working now both for NAND and NOR models
 
----
 
Resizing ps3dd via emer_init.self task patching (OtherOS++): http://pastebin.com/QJ4zt2Hm

Latest revision as of 19:42, 23 September 2011

Example of storage regions after installing debian (root=/dev/ps3vflashh3)

ps3d - 3 accessable regions
ps3da : 114473 MiB (234441648)
ps3db : 74281 MiB (152128408)
ps3dc : 2047 MiB (4194296)
ps3nflash - 4 accessable regions
ps3nflasha : 16 MiB (32768)
ps3nflashb : 14 MiB (30712)
ps3nflashc (256)
ps3nflashd (1024)
ps3vflash - 7 accessable regions
ps3vflasha : 38144 MiB (78118912)
ps3vflashc : 199 MiB (409088)
ps3vflashd : 16 MiB (32768)
ps3vflashe (1024)
ps3vflashf (16384)
ps3vflashg (512)
ps3vflashh : 37888 MiB (77594624)
  ps3vflashh1 () ps3vflashh2 (swap) ps3vflashh3 (ext3)

notes: ps3dc is used by the PS3 as temp for installing updates. When installing PUP files, the content gets unpacked there, checked - the system flags the update bit and reboots. After reboot it sees the update bit and installs the files from ps3dc without rechecking! (only in older version though)

ps3dd (if present) is the partition made by 3.15 and older OtherOS from the XMB

graf proposes in his howto/guide to partition the vflash region 7 (ps3vflashh) as follows:

ps3vflashh
  ps3vflashh1 (FAT) 100 MiB boot partition for later use
  ps3vflashh2 (SWAP) 2 GiB shared swap space
  ps3vflashh3 (EXT3) 20 GiB for Gentoo
  ps3vflashh4 (EXT3) 20 GiB for Debian

original phat ps3's with 256mb nand flash[edit source]

Q: Does this work on these models? A: Use OtherOS++ that method seems to be working now both for NAND and NOR models


Resizing ps3dd via emer_init.self task patching (OtherOS++): http://pastebin.com/QJ4zt2Hm