OUPS! The system crashed before I could use Marvin's utility.
The system crashed before I could use Marvin's utility. So I don't have a patch folder neither patcher.sh script. My system kernel panics on an encrypted binary but I am able go in single user mode. Is there a way to run Marvin's utility…
- Primary Author
- @okapi Published 2008-06-17
- Collection
- Leopard 10.5
- Archival Footprint
- 2,754 historical reads · 3 curated field notes (from 8 dispatches) · 2008-06-17 – 2008-06-19
- Credited Voices (3)
- @okapi (5)@Voyn1x (2)@milanca
The system crashed before I could use Marvin's utility.
So I don't have a patch folder neither patcher.sh script.
My system kernel panics on an encrypted binary but I am able go in single user mode.
Is there a way to run Marvin's utility using a CLI. If not what can I do to manually recreate what Marvin does.
Author Updates & Technical Revisions
Follow-up dispatches by @okapi
No GUID the drive is formatted as MBR, but I have another disk.
Wouldn't it be possible to run Marvin's utility directly from the livecd without reinstalling on another drive?
Saving my install is exactly what I want. My install setup was full blown and up to date.
I have a MBP for my main desktop anyway. There is no chance of having bad CPU IDS on this system.
I will install another instance on my spare disk then and recover from it.
I was able to patch using a second disk.
I created a patches folder and patched it in single user mode.
But now the kernel panics on dsmos.kext
Synthesized Community Field Notes
3 technical responses curated from 8 original dispatches
Not sure if you can run Marvins via cli, but if you formatted your disk as GUID originally you could make a new partition using disk utility off the cd, do a second install and run Marvins from there.
Or you could install to a different drive if you have one?
@okapi
What have you installed exactly without applying marvin's patches? We can send you a cpuid text and a patcher to try to resque your system just be a bit more specific, is it 10.5.3 update or what was it.
Hmm.. this will cause getting the correct cpuids from us next to impossible since you have rather a unique situation there. I doubt many people are running server here, if at all.
I really think the only way to save your install is by making another one and recovering it from there. It's always good to have a second install especially on AMDs. I have a small 10gb partition set aside just in case something breaks my system.