No, the RealtimeClock was trying to set the OS Clock to Feb 29th, which the frontend clock refused to do, because it knew that was a bogus date.
Some PS3's (most of the 80GB units, and all the slims), the RTC was setting the correct date.
In a way, the PS3 firmware was TOO smart, it knew the date the RTC was trying to set was bogus and refused to have it. The fix is either to code a workaround in the PS3 firmware so the next time the realtime clock tries to set a bogus date, rather than refusing to accept it, it does something more sensible like patch the date temporarily until the Realtime clock starts trying to set a valid date again.
Register
@Raspy32
No, the RealtimeClock was trying to set the OS Clock to Feb 29th, which the frontend clock refused to do, because it knew that was a bogus date.
Some PS3's (most of the 80GB units, and all the slims), the RTC was setting the correct date.
In a way, the PS3 firmware was TOO smart, it knew the date the RTC was trying to set was bogus and refused to have it. The fix is either to code a workaround in the PS3 firmware so the next time the realtime clock tries to set a bogus date, rather than refusing to accept it, it does something more sensible like patch the date temporarily until the Realtime clock starts trying to set a valid date again.