Hi,
I have F9 on a PS3 and today I've update the PS3 software from Sony to 2.42
Then I booted Linux. No problem. Then I updated F9 (last update dated 11/07/08).
Many new RPM installed.
Then I rebooted and the PS3 on Linux does not boot anymore.
It goes to kboot prompt and then, in the next section it stops after some USB related lines.
These are the last 3 lines of output
ps3-ehci-driver sb_05 USB 0.0 started, EHCI 1.00, driver 10 Dec 2004 hub 1-0:1.0 USB hub found hub 1-0:1.0 2 ports detected
Then the only thing I can do is to press the switch until it switches off.
1) Does anybody know what happens? 2) How can I reboot the PS3 software? 3) How can I fix it?
Cheers
Andrea
On 08/03/2008 11:16 AM, Andrea wrote:
Hi,
I have F9 on a PS3 and today I've update the PS3 software from Sony to 2.42
Then I booted Linux. No problem. Then I updated F9 (last update dated 11/07/08).
Many new RPM installed.
Then I rebooted and the PS3 on Linux does not boot anymore.
It goes to kboot prompt and then, in the next section it stops after some USB related lines.
These are the last 3 lines of output
ps3-ehci-driver sb_05 USB 0.0 started, EHCI 1.00, driver 10 Dec 2004 hub 1-0:1.0 USB hub found hub 1-0:1.0 2 ports detected
Then the only thing I can do is to press the switch until it switches off.
- Does anybody know what happens?
- How can I reboot the PS3 software?
- How can I fix it?
A new kernel was installed. Try using the older kernel.
-Geoff
Geoff Levand wrote:
On 08/03/2008 11:16 AM, Andrea wrote:
Then the only thing I can do is to press the switch until it switches off.
- Does anybody know what happens?
- How can I reboot the PS3 software?
- How can I fix it?
A new kernel was installed. Try using the older kernel.
I thought about that, but I cannot figure out how to select the old kernel...
How do I choose it with kboot?
Andrea
Geoff Levand wrote:
On 08/03/2008 11:16 AM, Andrea wrote:
- How can I fix it?
A new kernel was installed. Try using the older kernel.
-Geoff
Ok, I've found it.
at kboot:
1) sh 2) cd /etc 3) cat kboot.conf
read the name of the label of your other kernel
for me it was something like
image_2_6_25_4_xxxxxxxxxxxx
4) exit 5) TYPE THE LABEL
it booted properly for me.
Andrea