Kernel Panic
Weird but when I upgraded to 10.5.5 w/ the new voodoo I started having kernel panics in mail. The panic only comes after I add my first account. As in, I am using the program for the first time and adding my first e-mail account and it…
- Primary Author
- @axhi Published 2008-12-07
- Collection
- Leopard 10.5
- Archival Footprint
- 13,378 historical reads · 6 curated field notes (from 13 dispatches) · 2008-12-07 – 2008-12-17
- Credited Voices (3)
- @axhi (6)@nfoav8or (5)@jazZbaR (2)
Weird but when I upgraded to 10.5.5 w/ the new voodoo I started having kernel panics in mail.
The panic only comes after I add my first account. As in, I am using the program for the first time and adding my first e-mail account and it suddenly just crashes after i hit continue.
Anyone think its just my build on the program? Any help is great, i'm currently using thunderbird anyway, but I just really like Mac's mail client. its great.
,
Joey
Author Updates & Technical Revisions
Follow-up dispatches by @axhi
so ill try and get that error post. but i think i may have messed it up when i copied my mail.app from my macbook pro to my osx86. i feel like that did it. i repaired permissions but im just getting a kernel panic all day.
is there anywhere i can download an installer app for mail?
nf0av8or - i have my retail disk and i tried from that and nothing. It installed fine and what not but after i hit take account online or whatever from the first account add screen, kernel panic.
how do i get it to save my kernel panic so i can upload to you?
interesting, i am not certain. i believe i am using a backup now because its the only thing that doesnt make my stuff crash. How do i make sure that my mach_kernel.voodoo is gonna be mach_kernel?
ya, figured out the mac_kernel thing. I'm using mach_kernel. the weird thing is it worked fine before i decided to copy all my files and what not from my mbpro to my hackintosh
Synthesized Community Field Notes
6 technical responses curated from 13 original dispatches
hmm... I'm using mail just fine with the new kernel. can you post your console output for the errors produced (to show the KPs... not the entire output)?
its on a retail DVD in one of the packages folders... If you don't have this I'll PM you later with a link to mine after I upload it to mediafire.
@axhihow do i get it to save my kernel panic so i can upload to you?
hi,
i have a similar problem and wouldn´t open a new thread. i tested parallels desktop and vmware fusion successful under lawlessppc 10.5.4 with voodoo kernel rc1. now after update to 10.5.5 i get a kernel panic at the both applications when i starting a virtual machine.
@axhinf0av8or - i have my retail disk and i tried from that and nothing. It installed fine and what not but after i hit take account online or whatever from the first account add screen, kernel panic. how do i get it to save my kernel panic so i can upload to you?
go to /Applications/Utilities/ and open Console.app
Then find the output associated with the kernel panic.
Also, you could take a picture with a camera of the kernel panic on your screen (like so many others do here) and post it...
@jazZbaRi have a similar problem and wouldn´t open a new thread. i tested parallels desktop and vmware fusion successful under lawlessppc 10.5.4 with voodoo kernel rc1. now after update to 10.5.5 i get a kernel panic at the both applications when i starting a virtual machine.
have you made sure you are using the kernel properly? remember this is a bug with VMWare Fusion at least... you need to have the kernel being used be named "mach_kernel" not "mach_kernel.voodoo"
which are you using?
@axhiinteresting, i am not certain. i believe i am using a backup now because its the only thing that doesnt make my stuff crash. How do i make sure that my mach_kernel.voodoo is gonna be mach_kernel?
well for starters you could simply rename it... or read the documentation.
directly from the documentation:
Note: If you want to use VMware Fusion, you kernel must be named /mach_kernel. This is a bug in VMware, which requires the running kernel to use the default name. The recommended workaround is to rename the existing kernel, and create a symlink as follows (in Terminal) : sudo mv /mach_kernel /mach_kernel.original sudo ln -s…
now the two kernels (mach_kernel and mach_kernel.voodoo are actually the same one so VMWare and Parallels don't have issues...
I hope this helps because if its not a kernel panic then I don't know what else it could be... both work on my system and I'm doing exactly what I told you to do.
@jazZbaRthank you nfoav8or's. you are very qualified and a big help. (Y)
haha. well thanks and you're welcome. I'm not that great, but I'll take the compliment.