Acard 6280M and Tiger = BOOM!

I have solved my hanging gray Apple screen of death issue referenced earlier many times on this blog (most recently here - follow the trail yourself back to Jan 9, 2006 when I tried to upgrade from Panther to Tiger 10.4.4 on my relatively old, but heavily upgraded, G4 AGP.

In my last post, I had discovered on the Apple discussion boards information about the Acard PCI Adapter interfering with versions of Tiger after 10.4.2. I figured this was likely my problem as well, as I have that very PCI card and was attempting to boot Tiger off of a drive connected to that Acard adapter.

It so happened that I had a fairly large 120 GB drive still attached to the main ATA bus on the system, so I duplicated my Tiger partition over to that drive. I’ve been cruising along fine since in Tiger 10.4.5. I also emailed Acard the following regarding this issue:

Dear Acard,

I have recently upgraded from Panther to Tiger (10.4.5) and may be having issues with my Acard 6280M. I have loaded the most recent drivers, but the problem still remains.

If I do any system maintenance (cache deletion) or add any new kernel extension, I will get stuck at the Apple gray startup screen. I have to do a safe-boot and then delete the following folder to be able to boot again:

/System/Library/Cache/com.apple.kernelcache/

I perused the file inside that directory and found a line referencing the 6280M. Are there any issues with the current driver and Tiger 10.4.5?

Thank you...

Shane Hendricks

Acard hasn’t yet responded and they may never respond; the current broken driver is version 1.5.7. This driver should work fine with 10.4.2 and below. They did answer some folks on the Apple discussion regarding this topic, which you can read for yourself. They basically passed the buck to Apple, which is bogus. It’s Acard’s responsibility (as a peripheral maker) to support Apple, not the other way around damn it. In another answer, they recommended doing a complete new reinstall and AVOIDING MIGRATING OR UPGRADING from Panther, which is crap for those of us with a nice running Panther system.

Anyway, this problem is solved for me, and my system seems to be running much better under Tiger. Good luck to others with this problem.

SystemStarter woes continue...

Nope...problem not gone.

Reference my previous posts here and here about this issue I’ve faced upgrading my old G4 AGP to Tiger and getting the weird, unpredictable, hanging gray-Apple-screen-of-frozen-death, which I’ve traced to SystemStarter in the console.

I’ve narrowed the culprit files down to something in the /System/Library/Cache/, as today I decided to delete recommended items stepwise in Safe Boot until I could boot normally again.

First, I tried deleting a few things in /Library/Cache that I thought might be the culprit, going simply by the date of modification/crreation (i.e., today). No help. So then I tried getting rid of Extensions.kextcache alone, but I still faced the screen-of-death.

So finally, I just deleted the entire contents of /System/Library/Cache, and this seems to be the cause (or something in here).

As far as what’s causing this: I’m not sure. I had a crash shortly before this happened and I ran Applejack. Reboot was fine, but a subsequent test restart was not.

BTW, here’s a great site for troubleshooting startup: http://www.thexlab.com/faqs/startupitems.html

Searching the Apple Discussion boards led me to this thread, which might be related to my problems (i.e. the Acard 6280M IDE PCI controller).

To be continued I’m sure...?

Stuck at the gray apple screen in Tiger

This is a problem I was having (see previous post) after upgrading to 10.4.3. Well, I’m finally up and running 10.4.5 and seem to have eliminated the issue (so far). I’d like to describe my solution for others having the problem (see my original post for background info).

I believe the problem has to do with using the Migration Assistant--specifically, the option to move over Files and Folders at the root level, so I recommend leaving this option unchecked during your migration. As a matter of fact, leave anything you can absolutely do without unselected to minimize the chance of corrupting your new system during migration.

My solution:

The first thing I did was install and upgrade completely (from 10.4.2. to 10.4.5. using the Combo installer and the Software Update panel to get it all up to speed). Then, after repairing permissions, I manually installed every kernel extension I could think of (i.e., xxx.kext) that I thought I would use; this way, no extensions would be installed via the migration from Panther to Tiger. After getting to this point (with a system that would restart fine every time), I made a backup using SuperDuper just in case I had to go back to square one.

Finally, I proceeded to use Migration Assistant, but I did not migrate root-level files and folders, and I also didn’t migrate my network settings. Everything else migrated fine, and I’ve noticed no major differences so far (except that Tiger is much snappier on my system than Panther was). So far, the dreaded, sneaky gray-Apple-screen-of-death issue has been averted. I don’t know why or exactly how, but for those of you having this problem, you should attempt this fix in the Migration Assistant. Better yet, don’t use it all and start over from the beginning (manually copying over stuff you need).

Again, my issue is different from some others in that I was migrating on the same computer...on old, heavily-upgraded G4 AGP Mac. All seems great right now...

10.4.4. update is big crash-bang-boom!

I just made the mistake of loading this update via Software Update without backing up first. Let’s this be a lesson to everyone. Don’t do it! Backup, backup, backup!

Remember when I said that a Safe Boot was getting me out of trouble in 10.4.3? Well, I’m stuck at the gray Apple screen of death again, and I can’t Safe Boot or boot into Single-User mode. I can’t even do an Archive and Install...I tried and the stupid thing still doesn’t recognize the file system. All the usual troubleshooting steps were ineffective. The only real option is to blank the drive and start over, and I don’t have the time anymore. I’ve spent a week trying to get running with Tiger and it has been a waste of time.

Sticking with Panther for now, which is rock solid for me at 10.3.9! Maybe Apple with fix this crap eventually instead of breaking it.

Upgrading from Panther to Tiger 10.4.3

What a pain in the patootie! My old, trusty G4 AGP 400, which has been heavily updated and modified into a dual G4 1.2 GHz Panther beast, gave me fits when I decided to load Tiger and then update it to 10.4.3. The problem: hanging at the gray Apple screen during startup without any progress indicator (the spinning wheel). I spent the better part of three days troubleshooting this nightmare, to include two separate clean installs and migrations. I discovered lots of folks were having this issue on G4s after the 10.4.3 update around the net, but no one had any solutions (other than using another Mac in target mode to install the 10.4.3 combo updater). There had to be another way.

So, I used a safe boot (⇧ during startup) to drop into safe mode, which would work every time. Single-user mode was a no go (⌘-S); the Mac stubbornly ignored the snag. I perused the Console and kept seeing this:

Jan 9 12:37:23 Studio-Mac SystemStarter[800]: authentication service (815) did not complete successfully
Jan 9 12:37:25 Studio-Mac SystemStarter[800]: The following StartupItems failed to properly start:
Jan 9 12:37:25 Studio-Mac SystemStarter[800]:
/System/Library/StartupItems/AuthServer

After much troubleshooting, I found that I could reboot normally once if I installed something on the machine that modified the extensions. Subsequent reboots would hang, however. The log entries above may or may not have indicated the ultimate problem. I’ll have to watch the system.log to see if they go away. After digging around in the Apple forums and other places, I found a solution for my nettlesome situation.

While in safe mode, I deleted the following files (* means delete directory contents):

/Library/Caches/*
/System/Library/Caches/*
/System/Extensions.kextcache


After rebooting, the problem went away, even for subsequent reboots. I’ll monitor and see if installing new kernel extensions requires repeating the deletion sequence. So far, all is good for now.