Boot Kernel Panic Issue

[llamahead]

When I try to boot my new 10.4.6 JaS installation, I get the following error:

 

Panic(CPU 0 Caller 0X001A429B): Unresolved Kernel Trap (CPU 0, Type 0=Divide Error)

 

I saw a post about this that was telling me to disable "Limit CPUID" in the BIOS, but I don't seem to have that option (AMI BIOS).

 

Any other ideas, or anyone know where to find this option in the AMI bios?

 

I'm also wondering if maybe I chose the wrong installation packages. I have an AMD Athlon 64 X2 2.6GHz. Anyone know what options I should have picked? I know I picked the AMD packages, as well as the SSE3 package.

[~pcwiz]

Could you please post up a screenshot of the ENTIRE error screen, not just that panic line. You have a problem but I don't think that that line is where the problem resides...

[llamahead]

Here's the entire error message. Sorry, it's a bit blurry. My camera isn't too good. Tell me if you need a better picture, but I think it's readable anyways.

[~pcwiz]

Thats a weird error... Usually happens when you apply the wrong CPU patch. Doesn't seem to be the problem in this case. Try downloading the Uphuck 10.4.9 1.3 Universal DVD and see what happens...

[llamahead]

I also want to note that I am booting with GRUB on hd0, partition 0.

 

If boot from the OSX86 drive itself, instead of the Ubuntu GRUB drive, I get a dollar sign with a blinking underscore, but I can't type anything...

 

Does that mean anything? Am I booting to the wrong parition?

 

EDIT: Also, could anyone maybe list what packages I should have installed? Maybe I'll reinstall with the suggested packages.

[~pcwiz]

I think its a problem with the DVD you installed with. 10.4.6 is too old. Download the Uphuck 10.4.9 1.3 Universal DVD like I said and install with that.

 

pcwiz

[llamahead]

Okay, I finally got around to downloading the 10.4.9 Uphuck disk. I installed with all the AMD-required things (SSE3), and the Titan nVidia driver.

 

It's much better than the 10.4.6 JAS disk so far, but I'm still having an issue. I don't have my camera right now, so I can't post a screenshot, but here are the important parts:

 

Titan says it's found the card and tells me to 'cross my fingers', and then I get this line:

 

NVDA::start(display) <1> failed

 

It then goes on with a few non-critical problems, like it failed to mount my Linux EXT file system. Then, it gets stuck on:

 

MacFUSE: starting

 

My best guess is that at that point, it's trying to open up the graphical login, and failing. There was another nVidia drive option, starting with an 'n', I can't remember exactly. Should I try that? Any other ideas/advice? Is there a way to start in some kind of 'safe mode' where it just uses the generic VGA driver?

 

I have an NVIDIA 7950GT, incase it matters.

[Envying]

try boot with flag "cpus=1"

[llamahead]

If I do that, it gets stuck on the line:

 

using 10485 buffer headers and 4096 cluster IO buffer headers

 

I have an AMD Athlon 64 X2, and I start with "cpus=2", since, if I don't, I get panics.

[~pcwiz]

That using 10485 buffer headers and 4096 cluster IO buffer headers can usually be solved by checking the AppleACPIManagement 10.4.8 option or something like that and the Uphuck installation options screen.

[llamahead]

I did install that :-(

 

Okay, so, I figured it must have to do with me having a 512MB video card, so I re-installed without Titan, figuring it would just fallback to some generic drivers or whatever it uses during the installation, and I would just deal with accelerated graphics later.

 

To my surprise, it didn't really work. I no longer get "NVDA::start(display) <1> failed", but once it says "Login Window Application Started", nothing happens. No hard drive activity. It gives me the following lines, and then nothing...

 

localhost mDNSResponder: mDNSPlatformRawTime: last_mach_absolute_time <some long hex value>

localhost mDNSResponder: mDNSPlatformRawTime: this_mach_absolute_time <some long hex value>

 

I did notice this, before the NVDA lines:

 

display: family specific matching fails

 

I don't know if that means anything...

 

So, basically, even though I'm not using accelerated graphics drivers (at least, I think I'm not), it still seems to lock-up when it tries to start the graphical login window. Any advice? I'm really hoping this will work out...

 

Again, my specs are:

 

AMD Athlon 64 X2

2GB DDR2 800 RAM

MSI K9N4SLI

Gigabyte NVIDIA 7950GT 512MB

 

PS:

 

My other conclusion is that it's having a problem with my ethernet or wireless card. The reason I think that may be is that all that localhost stuff seems to be related to ethernet.

[~pcwiz]

display: family... doesn't really matter. I think it disappears after you install a video driver. Yes, your problem is related to Ethernet. Did you install any networking drivers? If you did, try installing without them and if you did not install any networking drivers, then try installing the driver for your Ethernet.

 

EDIT: If it does this after Login Window Application Started, then install loginwindow 10.4.4 from your install disc.

 

pcwiz

[llamahead]

In the description of loginwindow, it only talks about Intel CPUs, would it still make a difference if I have AMD?

[llamahead]

Okay, I reinstalled with the loginwindow patch, and no extra drivers of any sort. It didn't change anything, but here's what I've learned:

 

The last line(s) always have to do with "localhost mDNSResponder", it varies between 1-4 lines, and those are the lines after the Login Window line. Before the Login Window line, there are many more "localhost" lines.

 

Is there some way I can boot without it trying to use my network card (if that is the problem)? What should I do now?

[~pcwiz]

Did you install network drivers for your Ethernet?

[llamahead]

Not that I know of. I didn't select any network driver packages when I installed.

 

I have an NVIDIA ethernet chip. I don't know how easy it will be to find drivers for it...

[llamahead]

Okay, it tends to vary a bit, but here is the section where all the 'localhost' stuff started last time I tried to boot:

localhost mDNSResponder-108.4: starting

localhost DirectoryService: Launched Version 2.1

localhost kextd[25]: kextd_watch_volumes: couldn't setup diskarb sessions.

com_triton_forcedeth: Ethernet address 00:19:db:24:8e:77

localhost configd[51]: No AirPort driver found.

localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started.

localhost mDNSResponder: couldn't read user-specified Computer Name: using default instead.

localhost mDNSResponder: couldn't read user-specified local hostname: using default instead.

localhost mDNSResponder: Adding browse domain local

 

then hangs...

 

Do you make anything else of this? I mean, I guess I know we decided it was the ethernet, but I was wondering if this gave any more clues to the exact problem?

[~pcwiz]

Hold on...I'll get back in a sec. I'm pretty sure there is an Ethernet driver.

 

I found the LAN model for your MoBo: Vitesse VSC8601

 

I'll see if I can find a driver.

 

EDIT: I found someone with the same LAN as you: http://forum.insanelymac.com/index.php?showtopic=61562

 

Apparently, they have not found an LAN driver either but they managed to install OS X successfully by using a Tubgirl AMD ISO.

[llamahead]

Wait, are you saying my Mobo is a Vitesse VSC8601? Or just the on-board LAN? I know my mobo is a MSI K9N4SLI.

 

By the way, I won't even be using the on-board LAN, as I have to use a PCI wireless card to connect anyway. Is there a way I can just disable it/the driver? I tried disabling it in the BIOS, and there was an option, but it didn't seem to make a difference when booting.

[~pcwiz]

No, I'm saying that the onboard LAN is Vitesse. Did you try removing the wireless card and then trying to boot?

[llamahead]

Yea, and I tried reinstalling with the LAN disabled in BIOS and removing the wireless card, but I still get those messages and that hang.

[~pcwiz]

It might be related to your motherboard and not the Ethernet. Hmm... Oh but I see that you have an nForce chipset. The problems could be related to that. Did you install nForce4 drivers when you installed?

[llamahead]

I don't remember seeing that... is that even an option on the Uphuck DVD?

[~pcwiz]

The nForce4 SATA option should be under Drivers >> System in the installation options screen. Its there in the Uphuck v1.4iR3 ISO.

[llamahead]

I think I was using that earlier, but I'll try it again. Wouldn't that only have to do with accessing the SATA hard drive? OSX86 isn't installed on my SATA.