XFP panic after b15 upgrade -7500 |
August, 09, 2002 6:47 PM |
blel |
I used the "Reinstall extentions" option to upgrade from b14 to b15. The restart ended in a panic: "Unable to find driver for this platform: "Appl,7500." Then I used b14, and used the "Reinstall extentions" with it. The restart was successful! Also tried the OldWorld package from OS X, same result with a panic. Reverting back to b14 in OS 9, and reinstalling extentions, got things back to normal. b15 seems to need some work. |
. |
RE: XFP panic after b15 upgrade -7500 |
August, 19, 2002 12:56 PM |
OSXGuru |
. |
You've probably seen this in other threads, but this was a bug in version 2.2b15--it should be fixed in 2.2b16. |
. |
RE: XFP panic after b15 upgrade -7500 |
August, 12, 2002 11:26 AM |
acies |
. |
Under the uninformative subject head "Successful narrow escape" I had exactly the same experience described above "unable to find driver for this platform: Apple,7500" . . . I failed to describe it properly. I assumed it was because I had a 604e chip. Was able to reboot in b14 by reinstalling extensions. Thanks! |
. |
RE: XFP panic after b15 upgrade -7500 |
August, 10, 2002 5:09 AM |
willschou1 |
. |
I had the same problem. Neither beta 14 nor 15 will boot OSX 10.1.5 for me. If I uncheck all the debugging stuff it will try to boot OSX 10.1.5 but stops with an error message early on. Jaguar is no luck as well but I was trying to install over 10.1.5 will try again on a new partition but since the J700 doesn't like beta 14 nor 15 not sure it will boot. Will Schoumaker Beta 7 is my version of choice at the moment Thanks for all the work you do to get this going! |
. |
RE: XFP panic after b15 upgrade -7500 |
August, 09, 2002 11:33 PM |
OSXGuru |
. |
I have a theory now about what is causing this problem (and why it affects some people and not others). I will work on a solution. |
. |
RE: XFP panic after b15 upgrade -7500 |
August, 09, 2002 10:48 PM |
OSXGuru |
. |
I'm getting a fair number of reports like this, so I will need to figure out what is going wrong. Unfortunately, it works for me :-) |