After update to 10.5.4 system won't boot
I used Zeph's ASUpdater to install 10.5.4 on my 10.5.2 system, first I installed the 9.4.0 kernel without the update and the system worked fine, but after downloading and patching the 10.5.4 update and installing the boot hangs at this…
- Primary Author
- @SashaSki Published 2008-07-19
- Collection
- Leopard 10.5
- Archival Footprint
- 2,780 historical reads · 3 curated field notes (from 5 dispatches) · 2008-07-19 – 2008-10-18
- Credited Voices (3)
- @SashaSki (2)@nfoav8or (2)@endlesssnowfall
I used Zeph's ASUpdater to install 10.5.4 on my 10.5.2 system, first I installed the 9.4.0 kernel without the update and the system worked fine, but after downloading and patching the 10.5.4 update and installing the boot hangs at this message:
MAC Framework successfully initialized
using 10485 buffer headers and 4096 cluster io buffer headers
Using -f -x -s results in the same thing, any suggestions or help would be great! I can access the drive to get the log but I don't know where it's located on the disk.
System is:
Mobo: ASUS A8N-SLI SE
CPU: AMD Athlon 64 3800
Gfx: PNY Geforce 7300GS
Author Updates & Technical Revisions
Follow-up dispatches by @SashaSki
No matter I managed to fix it after fiddling with some kexts. But now I have another problem, everytime I boot my system after all the lines of text my monitor goes black and into standby mode and then after about 2 minutes it will turn on and the desktop will appear, this is such a pain as it means I have to wait quite a bit everytime I boot up.
Any ideas why this is?
Synthesized Community Field Notes
3 technical responses curated from 5 original dispatches
I prefer to update one at a time instead of a combo update. Its more stable and you can check your system in between updates to make sure everything is still working.
are you using the boot flags "-f -x -s" all at once or have you tried them individually? -x goes to safe mode... -s goes to a bash terminal login only. these two flags don't mix.
Which kexts did you have to fix to get it to work? Also, how did you fix them, by booting into another osx installation and using kext helper?
@ SashaSki - This sounds like an injector problem with your gfx card. Do you use inject or another kext or do you use EFI... I strongly recommend EFI on this one.
@ endlesssnowfall - I'm not sure which kexts SashaSki messed with to make it work; try looking around the net for this one a bit. To get in and fix it, SashSki could have used the boot flag "-s" and then would have been able to gain access to the file system via a Terminal base.
Sources & Contributor Provenance (3 credited usernames · Thread #1244)
| Username | Dossier Contribution | Dispatches | Active Window |
|---|---|---|---|
| @SashaSki | Primary Author | 2 | 2008-07-19 |
| @nfoav8or | Contributor | 2 | 2008-07-19 → 2008-10-18 |
| @endlesssnowfall | Contributor | 1 | 2008-10-18 |