Jump to content
5 posts in this topic

Recommended Posts

I'm having what I think is the issue described here. I have a new 10.4.8 AMD Final/Tubgirl installation on my Sempron 2800+/VIA K8T800/Geforce 6200 system. The install is on a separate drive on the only partition on the drive. The drive is setup as a slave to my XP drive.

 

What's happening is that only rarely will OS X successfully boot. Much more often it will cause the system to reboot while loading extensions. I've tried various startup switches (-v, -x, -f, rd=) with no apparent effect.

 

When it does boot up successfully, things work well. My Geforce is detected and QE/CI are enabled, sound works, etc.

 

Any advice? BTW, I've tried the JaS 10.4.8 (without the latest ppf patch) and it won't install for me.

That's actually what I did. I had partition problems when partitioning/installing from 10.4.8, so I completely deleted the partition with fdisk and cfdisk, then reinstalled using JaS 10.4.6 to erase/format the partition before installing from 10.4.8.

Just to update this situation, I tried several things to fix my reboot loop issue. I replaced the AppleSMBIOS.kext and IOATAFamily.kext with those from Paulicat's website as recommended in another thread. No dice. I tried a new install without NV40/Titan support. Same problem.

 

The reboot occurs just after System.kext is loaded. System.kext comes up a few times, so it must be some specific component of it.

 

As a sidenote, I'm not sure if this may be related, but I actually had to install to this drive on another system (same basic specs as above except with an Nforce (3 I think) motherboard, since the neither the JaS 10.4.8 or Tubgirl 10.4.8 ISOs would boot on my main system.

 

Could having installed from another box be causing this issue?

So, I swapped drives from the target system to the system I was forced to use to install from, and, indeed, that system did not suffer the reboot loop and was able to boot successfully every time.

 

At this point I'm leaning towards just swapping motherboards, but I'd ideally like to have a real solution to the issue with the VIA mobo.

 

So, to summarize, the VIA K8T800-based AOpen AK86 suffers the reboot loop while the Nforce3 250-based Asus K8N works perfectly. Am I wrong to attribute this to the chipset? I personally don't think so, but I'm open to other suggestions. The video cards are basically the same...both AGP Geforce 6200's.

×
×
  • Create New...