AFP548 - Topic: B&W G3 will not boot Jaguar (hangs at apple logo)

This topic has 9 replies, 6 voices, and was last updated 19 years, 9 months ago by andrina.

Viewing 7 posts - 1 through 7 (of 7 total)

Author

Posts
December 1, 2004 at 10:12 pm #360073

spectre_240sx
Participant

Ok, so I’ve got a B&W G3 with Jaguar freshly installed on it that stops booting at the gray apple screen. There is no spinning indicator when it reaches this screen and with the computer open I see no activity on either IDE channel. I’ve tried swapping memory and the machine is a bit finicky with what it will take. Some memory that works in other machines will cause this machine to not sync video after the “bong.” I’ve tried doing a PMU reset to no avail and I zapped the pram with the same result. The thing that really gets me is that the machine will boot just fine from: OS 9, OS 9 install media and OS X install media.

I’m running out of ideas so if anyone has anything else I could try I’d be very grateful.

December 2, 2004 at 6:09 pm #360081

spectre_240sx
Participant

Ok, I tried the permissions repair and while it did fix some things, it didn’t solve the problem. I was finally able to get the system to boot verbosely and it’s complaining about missing extensions, which seems pretty odd to me. I should mention I’ve tried clean installs with multiple hard drives, I’ve tried switching the motherboard, ram… I think I tried a different CD drive as well.

Here is the error that I’ve been able to get

Recording startup extensions
/* Copyright information here */

using 481 buffer headers and 491 cluster IO buffer headers
verifyCompatibility(): Extension “com.apple.kernel.iokit” cannot be found.
getDependencyListForKmod(): Dependancy com.apple.kernel.iokit of com.apple.driver.AppleGossamerPE is not compatible or is unavailable

/* nasty graphics messup, looks like whitish 5px repeating background */

Latest stack backtrace for cpu 0:
Backtrace:

0x000856CC 0x00085AFC 0x000287A8 0x0021E8E8 0x0021E6E4 0x0021F034 0x0021F690 0x0020FB10 0x0020FAD4

/* more nasty graphics */

Kernel Version
Darwin Kernel Version 6.3:
Sat Dec….

No debugger configured – dumping debug info
MSR=00001030
Latest stack backgrace for cpu 0:
/* backtrace information duplicated */

Proceeding back via exception chain:
exception state (sv=0x01411500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 6.3
date….

panic: We are hanging here

Sorry if this is too verbose, but I thought it best to include all information rather than having to go back and get something I missed.

February 10, 2005 at 10:11 pm #360675

hhavel
Participant

Try installing OS 9.1 or above. Then see if software update finds a firmware update for your B/W I seem to remember having same problem with Jaguar. Hope that helps.

March 22, 2005 at 3:44 pm #361043

Moofo
Participant

[QUOTE]Also if it is a rev. a G3 then make sure you are using a 40 pin HD cable and only have one master drive.[/QUOTE]

Where did you get that info ? Is the cable coming with the machine a 40 Pins Cable ?

I know the problems with the first generation these machines,that they don’t support new drives….. IS the proper cable supposed to solve the problem ?

June 30, 2005 at 5:34 pm #362165

Anonymous
Guest

I had the exact same thing happen to me after I did a fresh install of Jaguar 10.2. I installed it in one of the partitions I created. Blessing the folder using the command line command “bless…” didn’t help. Trying to repair the partition using First Aid didn’t work either. What finally worked was booting from the Jaguar install CD, then using the Jaguar Disk Utility to erase the partition I wanted to install Jaguar on (I had created the partition using the Tiger install CD disk utility). After doing so, I re-installed Jaguar onto the newly erased partition, and it worked fine–thus, no more boot hang at the gray apple.

July 7, 2005 at 10:47 am #362253

Waragainstsleep
Participant

I am unfortunate enough to own what is possibly the least reliable B&W G3 in existence. Someone generously removed the connector for the firewire module from the logic board before I bought it, which I suspect doesn’t help matters. It is also a rev.a of course.

Since I built it myself, it has neither stock HD or IDE cables. It too is happy running OS 9 with all manner of different RAM installed, but it came to OS X (Panther in this case eventually, but Jag to start with) it was a different matter. First trick I tried was to remove all RAM except one stick of 256MB PC133 7.5ns. After a couple of attempts, this would usually get all the way through the installer and all was well. Putting other RAM back in afterwards would screw things up again.

After running it under X for a few days/weeks however, it would eventually stop booting again. Sometimes DU would fix, sometimes Diskwarrior. Often another clean install was the only way.

I gather you can get away with more than one piece of RAM if it all matches and its all less than 10ns latency. The 10ns is no good. Must be 8ns or 7.5ns, and as I say all matching. (I have a feeling the firmware update mentioned above might disable 10ns or slower stuff, but I might be thinking about one of the old PowerBooks)

I gather that the correct cable will help, since the ones shipped with these Macs were not identical to standard IDE, but it looks like you have that. (If it has Foxconn tags at either end, thats probably the original).
I understand that the only way to truly combat the data corruption issue is to install a PCI drive controller. ATA, SATA or SCSI is fine. Its the rev.a drive controller which is the problem. It reads OK (mostly) but has a problem writing to any drive bigger than the stock 6 or 12GB ones.

I have another rev.a at work which runs happily with mixed, slow RAM and oversized ATA drives on its on-board channels. Right up to Tiger I think. The complete opposite of my own.

July 20, 2005 at 6:07 am #362390

andrina
Participant

The new PCI ATA card would certainly help you out, but the other thing I’ve come across (also having the service centre background like Josh) is the magic 8GB partition…. If you partition your drive so the first partition is no larger than 8GB, and install your OS on that partition it should clear up your issues… there’s something about system files being moved out of that 8GB space over time and leading to an unstable and unbootable system without the partition… There’s a lot of discussion around about this really only being valid on the beige G3 generation, but with your machine being a rev A B&W I’d be suspicious…
Cheers,
Andrina
Author

Posts