I recently made a 40nm frankenstein ps3 that I did not realize was on too low of a firmware before installing the 40nm RSX (it's on fw3.0.1).
I get the expected 'rsx rom abort' message in the southbridge logs while attempting to boot, however, I am also getting an 'rsx driver assert failed' message later in the logs. At first I figured this made sense as, of course the driver will fail if the RSX is not supported. However, I feel like I remember seeing another log that did not have the 'rsx driver assert failed' message, and instead showed a dump of the rom info, even with the 'rsx rom abort' message. I'm left with a 1701 as opposed to a GLOD. I recently opened another unit to retrofit while I wait for my hardware flasher to arrive, and noticed it has the same 'rsx driver assert failed' with only a 1701 syscon error reported.
So, I'm wondering, is this potentially expected? Or is it indicative that the 40nm may also be bad? If anyone has seen similar SB logs prior to updating (particularly the 'rsx driver assert failed' message), it would be great to share.
I get the expected 'rsx rom abort' message in the southbridge logs while attempting to boot, however, I am also getting an 'rsx driver assert failed' message later in the logs. At first I figured this made sense as, of course the driver will fail if the RSX is not supported. However, I feel like I remember seeing another log that did not have the 'rsx driver assert failed' message, and instead showed a dump of the rom info, even with the 'rsx rom abort' message. I'm left with a 1701 as opposed to a GLOD. I recently opened another unit to retrofit while I wait for my hardware flasher to arrive, and noticed it has the same 'rsx driver assert failed' with only a 1701 syscon error reported.
So, I'm wondering, is this potentially expected? Or is it indicative that the 40nm may also be bad? If anyone has seen similar SB logs prior to updating (particularly the 'rsx driver assert failed' message), it would be great to share.
