IMac G5 Boot Up Problem

I have an iMac G5 running OS X Lepoard. When I boot up the computer it has lines going accross the screen ( my youtube video of it happening http://youtu.be/Hb-BiNcN7kA) and It will not boot up all the way but I can get it in safe mode. I tride reseting the PRAM and I did a HDD check in single user mode and still it won't work.

Unfortunately, it might be a hardware problem, such as graphics hardware, power supply, logic board...
Here are some things you can try, in case the cause is less serious.
Reset PRAM, if you have not already
http://support.apple.com/kb/HT1379
Also reset SMU (power management).  This is the procedure for iMac G5.
http://support.apple.com/kb/HT1767
When you connect it back to power, I saw in the video that you were using a direct connection to a wall outlet, by itself.  That's good, to rule out a faulty (or over-crowded) power strip.  Be sure to disconnect ALL peripheral devices; start it up with only the power cord connected, then add just a standard keyboard and mouse.  If that makes a difference (and it starts up properly), run it that way for a while to see if it continues.
Check the vents along the bottom (and elsewhere) for accumulation of dust, blocking airflow.  That could cause overheating, which may result in video issues.  If this is the older type of iMac G5 that is easy to open up, you can also check it internally for dust.
If the PRAM battery has never been changed, it could be weak or dead.  That can cause odd startup issues, but usually not like the issues you have.  The PRAM battery for an iMac G5 looks like this.
http://eshop.macsales.com/item/NewerTech/CR2032/
The fact that it works better in Safe Mode makes me think it is related to the graphics hardware.  In Safe Mode, the graphics hardware is not being used to full capacity, so it might work more reliably (if it's becoming faulty).  For similar reasons, it could be the power supply, which may be less "stressed" in Safe Mode. 

Similar Messages

  • IMac G5 Boot-Up Problem - What Next?

    Hi, All!
    I have 20" iMacG5, 1.8ghz, non-Intel, running 10.4.10
    All fine until yesterday morning. On bootup it just gets to the Apple and activity indicator screen and indicator spins indefinitely.
    Have tried the following:
    1. Unplugged everything but the keyboard and power cord.
    2. Zapped PRAM twice
    3. Reset the SRM??? (Sorry, forgot the acronym)
    4. Safe boot = Same Apple screen then iMac powers off
    5. Booting off system disk, running Disk Utilities, getting error message:
    The underlying task reported failure on exit (-9972)
    6. Booting into single-user mode, using /sbin/fsck/-fy command, performs first three tasks then I also get error message:
    I/O error
    invalid record count
    (3, 54)
    **VOLUME CHECK FAILED
    7. Using TechTools boot disk, stalls on repair, etc but shows that the HD IS mounting. (error -4)
    8. Took the back off to visually inspect for any loose cabling, dirt, etc. All seemed fine.
    Anything else? No indications of any trouble the previous evening. Most recent changes to software:
    1. Upgraded to 10.4.10 about two weeks ago
    2. Upgraded iTunes and QuickTime to most recent versions a week ago
    3. Bought newest Video iPod and synched it three days ago
    I'm styimied at this point. I wish I could make an OS X boot-up disk to get to the desktop to retrieve some secondary files I haven't backed up (major ones are backed up). I miss OS 9 sometimes. Many more workarounds.
    And the thought of having to start all over with a new drive is rather daunting considering all the software I'll have to try to re-register ...
    Thanks!
    --Ted
    iMac G5, Powerbook G4   Mac OS X (10.4.10)   iMac G5 -- Non-intel, 1.8 ghz
    iMac G5, Powerbook G4   Mac OS X (10.4.10)  
    iMac G5, Powerbook G4   Mac OS X (10.4.6)  

    It may be slow, but at least you'll have the data
    I do hope that you are using the external as a bootable clone drive, with Archive and Install as your backup app.
    Please let us know if you succeed in getting everything off,
    Miriam

  • Apple IMac 27 has a problem. Random black screen. Over 1 year without any fix

    Apple IMac 27 has a problem.
    Random black screen.
    Over 1 year without any successful fix.
    IMac 27 10.8.4 (12E55) - bought in 2010
    3.06 GHz Intel Core 2 Duo
    4GB 1067 Mhz RAM
    Graphics ATI Radeon HD 4670 256 MB
    The IMac computer screen goes black randomly but the machine still running beyond.
    In order to go back to normal i need to awake the computer by hitting with the pointer a hot corner previously created " sleep mode" ( top left ).
    ..the black screen would come back after one second again..and then again and then again and then again..with different intervals..sometime 2 seconds after the other, sometime as soon as appears the user login screen.
    I took the machine to an Apple Store two times over one year, they opened, cleaned it but they didn't replace anything has they could not understand what they real problem was. I was happy for that because they didn't try to make me spend money on something which was not going to solve my issue for sure.
    Last time i kindly asked them to inspect everything meticulously, part by part, i left the machine with them for over 2 months. They couldn't understand why this was happening..after couple of weeks, 5 more machines came in with the same problem.
    On some of them., upon request of the client they changed the graphic card but apparently this was not the fix, the problem come back again. Apparently changing the graphic card or the screen or else it didn't solve any problem to anyone. I'm almost thinking to "trough it out of the window"..we all spend money for this machines and i think we need to know if Apple is looking in to this or not.
    Lately i tried to do an SMS RESET and PRAM RESET, it feels it got better a little but problem still coming back.
    Also, all usb  devices are disconnected and the problem still there
    Below you will see a copy of the console report. I honestly don't understand much of it as i'm not a computer guy.
    27/07/2013 11:03:39.837 WindowServer[119]: Created shield window 0xb3 for display 0x04272d40
    27/07/2013 11:03:39.837 WindowServer[119]: device_generate_desktop_screenshot: authw 0x7fad92c79dc0(2000), shield 0x7fad92c34370(2001)
    27/07/2013 11:03:39.906 WindowServer[119]: device_generate_lock_screen_screenshot: authw 0x7fad92c79dc0(2000), shield 0x7fad92c34370(2001)
    27/07/2013 11:03:41.701 WindowServer[119]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7fad92c79dc0(2000), shield 0x7fad92c34370(2001), lock state 3
    27/07/2013 11:03:41.702 WindowServer[119]: handle_will_sleep_auth_and_shield_windows: err 0x0
    27/07/2013 11:03:41.704 WindowServer[119]: Created shield window 0xb4 for display 0x003f003d
    27/07/2013 11:03:41.704 WindowServer[119]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7fad92c79dc0(2002), shield 0x7fad92c34370(2001), lock state 3
    27/07/2013 11:03:41.704 WindowServer[119]: handle_will_sleep_auth_and_shield_windows: err 0x0
    27/07/2013 11:03:45.186 com.apple.launchd.peruser.502[163]: (com.akamai.client.plist[740]) Bug: 12E55: launchd + 95444 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0xd
    27/07/2013 11:03:45.208 com.apple.launchd.peruser.502[163]: (com.akamai.client.plist) Throttling respawn: Will start in 10 seconds
    27/07/2013 11:03:52.117 WindowServer[119]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
    27/07/2013 11:03:52.118 loginwindow[43]: find_shared_window: WID -1
    27/07/2013 11:03:52.118 loginwindow[43]: CGSGetWindowTags: Invalid window 0xffffffff
    27/07/2013 11:03:52.118 loginwindow[43]: find_shared_window: WID -1
    27/07/2013 11:03:52.118 loginwindow[43]: CGSSetWindowTags: Invalid window 0xffffffff
    27/07/2013 11:03:53.763 WindowServer[119]: Created shield window 0xba for display 0x04272d40
    27/07/2013 11:03:53.763 WindowServer[119]: device_generate_desktop_screenshot: authw 0x7fad92c87490(2000), shield 0x7fad92e6eef0(2001)
    27/07/2013 11:03:53.838 WindowServer[119]: device_generate_lock_screen_screenshot: authw 0x7fad92c87490(2000), shield 0x7fad92e6eef0(2001)
    27/07/2013 11:03:53.880 WindowServer[119]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7fad92c87490(2000), shield 0x7fad92e6eef0(2001), lock state 3
    27/07/2013 11:03:53.880 WindowServer[119]: handle_will_sleep_auth_and_shield_windows: err 0x0
    27/07/2013 11:03:53.883 WindowServer[119]: Created shield window 0xbb for display 0x003f003d
    27/07/2013 11:03:53.883 WindowServer[119]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7fad92c87490(2002), shield 0x7fad92e6eef0(2001), lock state 3
    27/07/2013 11:03:53.883 WindowServer[119]: handle_will_sleep_auth_and_shield_windows: err 0x0
    27/07/2013 11:03:55.209 com.apple.launchd.peruser.502[163]: (com.akamai.client.plist[742]) Bug: 12E55: launchd + 95444 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0xd
    27/07/2013 11:03:55.252 com.apple.launchd.peruser.502[163]: (com.akamai.client.plist) Throttling respawn: Will start in 10 seconds
    27/07/2013 11:04:04.482 WindowServer[119]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
    27/07/2013 11:04:04.482 loginwindow[43]: find_shared_window: WID -1
    27/07/2013 11:04:04.483 loginwindow[43]: CGSGetWindowTags: Invalid window 0xffffffff
    27/07/2013 11:04:04.483 loginwindow[43]: find_shared_window: WID -1
    27/07/2013 11:04:04.483 loginwindow[43]: CGSSetWindowTags: Invalid window 0xffffffff
    27/07/2013 11:04:04.704 WindowServer[119]: Created shield window 0xbf for display 0x04272d40
    27/07/2013 11:04:04.726 WindowServer[119]: device_generate_desktop_screenshot: authw 0x7fad92ebdb20(2000), shield 0x7fad92e6eef0(2001)
    27/07/2013 11:04:04.795 WindowServer[119]: device_generate_lock_screen_screenshot: authw 0x7fad92ebdb20(2000), shield 0x7fad92e6eef0(2001)
    27/07/2013 11:04:05.245 WindowServer[119]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7fad92ebdb20(2000), shield 0x7fad92e6eef0(2001), lock state 3
    27/07/2013 11:04:05.246 WindowServer[119]: handle_will_sleep_auth_and_shield_windows: err 0x0
    27/07/2013 11:04:05.253 com.apple.launchd.peruser.502[163]: (com.akamai.client.plist[744]) Bug: 12E55: launchd + 95444 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0xd
    27/07/2013 11:04:05.249 WindowServer[119]: Created shield window 0xc0 for display 0x003f003d
    27/07/2013 11:04:05.249 WindowServer[119]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7fad92ebdb20(2002), shield 0x7fad92e6eef0(2001), lock state 3
    27/07/2013 11:04:05.249 WindowServer[119]: handle_will_sleep_auth_and_shield_windows: err 0x0
    I'm now thinking to try to take the machine to its original firmware and see if it still does it, does anyone have any sugestion?
    I use a lot photoshop and other image software, this computer is essential for my work. For more then one year this issue caused me problems.
    Luckly i have a Macbook Pro too and i managed to do some of my work there. At last I was thinking to buy an external screen and attach it to the Macbook pro in order to work on my big images. But who wants to spend money again!!!???? This is not a fixture, this is silly. I wish to have my IMAc working again.
    The warranty it's obviously over and this problem happened right after the warranty was over...
    I write this post because i'm so tired of this issue and online nothing can be found apart from posts from so many people that have the same problem and no fixture has been found.
    The only fixture seams to be to buy a new computer... Ole'!!!..new money flowing in in the cashier!! forget it!!! i would rather change company if apple doesn't respond to this.
    For over 10 years i have been a Apple owner..
    When this problem appears it's like someone it's playing a joke at you...
    Comments welcome..
    Thanks

    Hi, I've seem to have found out the source of the problem.
    The issue is related to heat, and an iMac 27" gets hot pretty fast.
    If I boot the iMac straight after first start into Windows 7 I seem to get a lit built-in display at all times. I can also boot OS X first and then into Windows 7 and the built-in screen get lit every time as long as the iMac isn't hot.
    Strange thing is that the monitor connected to the display port gets lit every time. So I can only assume that the heat only interfere with output to the built-in LED screen.
    So this iMac is going to an Apple premium reseller for service, and I'll tell you guys how it went.

  • IMac 27" Boot issue

    I have a late '09 iMac 27" Quad Core i5. Almost every time I go to boot, I hear the hard drive spin up and then nothing, just a black screen. No beeps, just black and near silence. it does this about 95% of the time. Here's the kicker, if I take RAM out, or put some in, or  re-seat it, it'll boot OK, and then run fine. The problem initially started when I swapped some RAM trying to resolve some kernel panic issues (that turned out to be old, conflicting Digidesign drivers). When I put the new RAM in, it booted fine. When I put the RAM cover on, it wouldn't boot. Take the cover off again, booted no problem. Then a few boots later, nothing again.
    I've ruled out bad RAM, as I've used all new RAM and still the same issue, and putting the old RAM back again will sometimes allow it to boot, until next time, then taking some RAM out will boot it again. Sometimes unplugging everything form the back will allow it to boot, sometimes it won't. Once it boots, it runs nicely. If what I've said here doesn't make any sense, then it means I've explained it properly! Here's what I've tried already:
    All new RAM
    Run Hardware Test (overnight, looping and extended test mode, no issues)
    All external devices unplugged
    All software updates applied, including 3rd party
    Verify Disk
    Zap PRAM
    Reset the SMC
    A service centre I called said it may be the memory management controller, but that's part of the logic board and that's a last resort financially. It's also hard to see how they'll know for sure because of the nature of the issue. It's so consistent in it's non-booting, but what I have to do to get it to boot again is not consistent, and just doesn't make any sense to me.
    Anyone have any ideas? Thanks in advance...

    Thanks for the reply. It seems (at least for now) that my solution is the same as yours. Very bizarre. I ran diagnostics on the RAM and that came back without error. Currently I have no issues but obviously it would be a pain if I had to shuffle the RAM around every time I wanted to start the Mac from cold. Just in case it happens again I haven't yet replaced the cover to the RAM slots. Seriously though, if the Harware guys are watching these forums: This upgrade should be at least as reliable and almost as simple as inserting a usb stick. There are too many people who have RAM upgrade problems.
    Thanks again. Very much appreciated.

  • IMac wont boot up

    My IMac wont boot up! I installed the Mac OSX system disk and ran disk utility this is the results:
    invalid node structure
    The volume Macintosh HD needs to be repaired.
    Error: Filesystem verify or repair failed.
    What do I do to get this up and running again, I would appreciate any help.
    Thanks,
    Joe

    I called applecare and they were able to get my iMac up and running. Apparently there is an issue with updating software. I just had to do an update today and ended up with the same problem. So I re did what the applecare rep told me and I got it going again myself. I am hoping this will not continue. So anyway, I am going to provide the steps on how my I got iMac going.
    1. unplug the computer for approx 17 seconds.
    2. unplug everything from the computer except the mouse and keyboard.
    3. plug in the computer
    4. turn on the iMac and hold down the option key at the SAME TIME
    5. when the iMac comes on, it will make a loud beep noise, CONTINUE to hold the power and option key until a small the Mac HD icon displays.
    5. When the Mac HD icon shows on the screen, release the power button and option key. Then click on the arrow below the Mac HD icon.
    5. The iMac will boot and take you to the desktop. Then click applications
    6. choose the utility folder
    7 then choose disk utility
    8 a screen will appear that states first aid. At the bottom, there will be an option to repair disk. Click on that then choose Mac HD.
    9 When this is finished, you are good to go. These steps will repair what ever the software updates are doing to the hard drive.
    Hope this helps.

  • Imac wont boot

    My late 2008 iMac wont boot. I have tried everything that i understand but cannot accesss harddisk.
    I cannot boot fron dvd -cd or usb. I would like to run diskutil from terminal to repair and verify. System hangs/ stops running, when i try command+v ,message that (vmcl: Module initialized.)
    Command + s puts me in single user mode and i cannot run diskutil.
    Safe start is also not working.
    I have all my work on imac and depserately need help.
    Any ideas ???
    Imac 2008 24" 3.06GHZ/2GB/500GB/SD8X/GF8800GS/512.
    Downloaded and installed Lion recently, all software is ligitimate.
    Running vmware / Vista, occasionally.
    Machine just stopped, froze up.

    Hei, just to let you know. I gave up and delivered my machine to mac repair. It turned out that a module error was the cause of my problems. They have since replaced the defective part and my machine works like a dream. No reinstalling either, all existing files and software are intact.

  • Boot Camp problem + General partitioning

    First, the Boot Camp problem
    I don't know exactly how to explain, but I kind of made the partition and restored them into one single startup disk, for several times. It was OK for the first few times, but then it required me to run Disk Utility (from startup) to repair the disk before I can partition. It happened for one time. But after that, it started to ask me to back up the hard disk, format it, and restore it, then try Boot Camp again. So, the ending of the story is I can never do boot camp again now because I wouldn't waste at least 70 quid for a hard disk large enough to back up solely because I need to run Boot Camp. Is there anybody here know why this is happening? And, eventually I think I'd have to buy an external drive and back up, format, restore, then run Boot Camp. But doesn't it sound dumb and familiar? This is exactly the ONE AND ONLY way to fix any problems in a PC. Aren't macs supposed to be far better than PCs? Why do we have to do what PC users have to painfully do? I hope somebody here can come up with a solution that doesn't involve "backup>format>restore".
    Second, the partitioning,
    I came up with an idea to solve the above problem. But I don't know whether it actually works, so I'm seeking for advice. I was hoping if I run Disk Utility from start up, make two partitions (or more) for the mac HD, one HD being the one holding all the data, and the remaining being empty. Then I can format the empty one (which seems rather redundant), and do the Boot Camp thing on this partition. However, there are two points I have doubts with. One, if I split my current single mac HD into multiples of partitions, will any or even all my data be lost? Because I can only specify how much to partition, I wouldn't have the chance to "tell" the computer to keep all existing data on one partition. Two, I know that Boot Camp can run on an external HD, so is it possiible to run on a different partition?

    Just an idea for you. There is an entire Apple Discussion forum dedicated to Boot Camp and Windows XP.
    Whereas, not everyone here with an Intel iMac has installed, tried to install or has experience with BC & XP, everyone there has or at least has an interest. You may attract help more quickly there.
    The Forum is at the bottom of the main Apple Discussions page under Windows Compatible Technology.
    Here is a link;
    Forum: Boot Camp Public Beta

  • My iMac will boot, but loses contact with BlueTooth

    My iMac will boot, but loses contact with Bluetooth after logging in, and then there is no way to interact with the system.  I can only shut it down.  Any help in resolving this issue will really be appreciated.
    Thanks -
    Dudley Warner

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, or by corruption of certain system caches. 
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including sound output and  Wi-Fi on certain iMacs. The next normal boot may also be somewhat slow.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

  • My imac wont boot  and a small square shows up next to the cursor

    Hi
    my imac wont boot and a small square shows up next to the cursor. I can open in safe mode. I have reinstalled the OSX, but can't boot from back-up.
    Any advice?

    OK.....I figured it out.....after reading endless threads on the cursor issue, I found out that apple calls the cursor a MOUSE POINTER..! and the square that follows it a 'corruption'...GO FIGURE!
    Anyway, this is what I did.
    I tried reinstalling Mountain Lion....online install. It didn't resolve the issue. Same problems
    Then, I tried reinstalling from the original DVD install disc....this wasn't possible (no access sign over install icon).
    So I finally erased my hard drive (after rebooting command - r), BUT NOT BEFORE BACKING UP MY FILES, APPLICATIONS, SETTINGS and any other important data!!!!!!!
    Then started up command R
    Then reinstalled Mountain Lion online
    My iMac started up like it does when you install 'out of the box'...follow the instructions....
    my cursor, or mouse pointer is now free of it's 'corruption', and boots up just fine!
    Hope this helps anyone out there with the same issue

  • IMac wont boot up - stuck on Apple logo with Spinning wheel.

    (Title is the Problem) any fixes?
    Ive tried repairing disc using the installed disk/utility and it says that the Macintosh HD cannot be repaired & i really dont want to lose all my files.
    However..
    I have my iMac Dual booted with W7, Now is it possible to do the following....
    Go to:
    Windows icon (bottom left) > Computer > Copy Macintosh HD > External HDD > Paste?
    (so in effect its a backup)
    Will i then be able to reinstall OSX and then load my files from it, or restore from it? (from the Ex. HDD)
    Many Thanks in advance.
    (1st post by the by)
    Tom
    EDIT:
    Just thought:
    If i reinstall the OSX - Will my files already upload onto the new OS install? As i have a feeling that Windows does that when upgrading - whether its the same for Reinstalling is a different matter i s'pose.
    Message was edited by: Tom.Rhodes

    Boot with your install disc, launch Disk Utility from the Utilities menu after selecting your language, and repair the disk. You can't repair the boot volume. Now some other tips. Reinstalling Snow Leopard only replaces all the OS components and basic Apple apps, such as TextEdit, Mail, and Safari, but leaves everything else in place. There's no chance of losing data unless it's already corrupted and lost anyway. There's no need to muck around with the windoze stuff, which, IIRC, won't work anyway.

  • Imac wont boot after long time without restart

    Hi
    I've got a two month old new Imac 21,5" with fusion drive 1TB, i had it just before mavericks was launched..
    i update to mavericks. All was fine, But i allmost never shut down, or restart the imac.
    After some time, I did for a reason i dont remember, had to restart the imac. while booting, it was stuck on the grey screen.. i wasn't able to get it started up, not in safe mode, not after disk repair.. i think i might have tried all the little tricks to get it running again...
    luckily i did have a time machine back up...
    after installing this back up, everything was fine again..
    until 2 weeks later, for some reason i had to reboot again.. and again, it was stuck.. only thing to get the imac working again.. reinstall from time machine back up
    after this , it tried rebooting everyday, and the imac kept working..
    after a few days, i forgot to reboot for a few days.. and what did you think.. the imac is stuk again.. so while reinstalling the time machine back up. I am writing this. anyone else having this rather strange problem.. if i restart the imac now and then i keeps working.. if i dont after a few days, and i do reboot the imac.. is wont boot anymore..
    Any suggestions are welcome
    greetings

    The long tone is an indication that a firmware update is installing. Do you get a progress bar at the bottom of you screen after letting the power button go?
    Have you reset the PRAM? (cmdalt+PR when you restart the machine)
    Also repair permissions when the machine is up and running.

  • IMac G5 boots to gray screen with Apple logo only

    iMac G5 boots to gray screen with apple logo only.
    What I've tried:
    Won't boot to safe mode.
    Reset PRAM several times.
    Won't boot to install disk with "C" depressed at startup.
    Will boot to screen showing HD and arrow buttons when "alt" depressed at startup. But clicking HD icon and proceed arrow just goes back to the gray screen with apple logo. Note the HD icon has a blue "x" symbol.
    With install disc in, will boot with "alt" depressed at startup to three icons, HD, install disc, and apple hardware test. Both HD and install disc icons have the blue "x" symbol and won't run. BUT the apple hardware test icon doesn't have a blue "x" and runs. Extended test says all hardware OK.
    Finally, startup in single user mode with "apple-s" depressed goes to a non-gui white text (UNIX core?) which gives blocks of repetitive text starting "unresolved kernal trap (cpu0)...(lots of date)...latest crash.....backtrace:" My rough guide to the Mac gives me text to enter at that point but I can't input to the screen.
    That's where I'm stuck.

    You're encountering a kernel panic.
    [I got a black screen telling me I had to reboot in many languages, what was it?|http://www.dslreports.com/faq/4970] Also has detailed description of what happens during a KP.
    [Apple docs: What's a kernel panic? (Mac OS X)|http://docs.info.apple.com/article.html?artnum=106227]
    [Topic : kmosx: Kernel Panics? Don't panic too !|http://discussions.apple.com/thread.jspa?threadID=121923]
    [X-Lab: Resolving Kernel Panics|http://www.thexlab.com/faqs/kernelpanics.html]
    [Tutorial: Avoiding and eliminating Kernel panics|http://www.macfixit.com/article.php?story=20060911080447777]
    [Tutorial: An introduction to reading Mac OS X crash reports|http://www.macfixit.com/article.php?story=20060309075929717]
    [12-Step Program to Isolate Freezes and/or Kernel Panics|http://macosg.com/group/viewtopic.php?t=800]
    [Texas Mac Man's post on kernel panics|http://discussions.apple.com/thread.jspa?threadID=1723768&tstart=0]
    These are often attributed to hardware problems though they can also be due to corruption of software. Since you're also encountering it with your DVD I'd tend more towards the former. Your computer seems to be passing the early stage POST tests for RAM. Apple Hardware Test also seems to be passing but [X-Lab: The Apple Hardware Test|http://www.thexlab.com/faqs/aht.html] document recommends using this in loop mode to test for intermittent problems.
    Sometimes the crash logs (all the error messages you are seeing) contain information about the problem, but there's an art to reading those.

  • Intel iMac 20' users - any problems with noise on your firewire interfaces?

    Someone please tell me that they have a quiet intel iMac 20'/Firewire interface set up, I'm having problems with a lot of digital noise from my Saffire LE & badly am hoping it's 'fixable' or just a faulty unit but more so, praying it's not noise from the iMacs Power supply that will interfere with any firewire interface I get???
    I've read many posts about G5's suffering from noisy psu's which was one factor in my choosing an intel iMac & I chose the Saffire on it's great reviews for sound quality, there's no way I can work with the noise I'm getting & I'm pretty much panicking that if it IS the iMac & firewire thats the problem I'll be screwed as i only have 6 pin firewire as a useable option (really don't want to use usb2)
    Incidentally, the 'budget' set up I had previously (PC & soundblaster audigy) didnt suffer from any noise like this (at least not that was even audible with the mixer levels at conversational level!) which i guess rules out any blame of this on 'mains hum/interference'?
    The noise is there with the saffire's monitor output knob at any setting & with no inputs connected, it;s even worse if i power the saffire with it's external psu instead of off buss power. I'm not using a firewire hub & I've tried switching firewire leads & removing the firewire hard drive i have in the other port in case this was affecting it.
    Would really appreciate hearing from anyone with similar troubles or even better anyone thats NOT having this problem with a 20' intel iMac & firewire interface so at least i know there's light (& quiet!) at the end of the tunnel
    Adam
    Intel iMac 20'   Mac OS X (10.4.7)  

    funnily enough I'm going the other way, I have a rack of external modules/>sampler/fx etc & a crate of looms I've just unplugged as they've not been >turned on in so long!!!
    I hear you there!
    The noise is there without any inputs at all to the interface, its defiantely >digital though, its like a toned version of the sound of an old telephone >modem.
    What I mean, is try disconnecting everything, drives and all. You might even disconnect the interface and crank up the iMacs volume to see if it is there. If it is, you can try the UPS and see if that takes care of it. Then add them in one at a time. All it takes is one cheap power brick in the mix to cause all kinds of trouble (if your using powered monitors, that brick too). Noisy components can actually send noise back into the source power.
    I know it can be really frustrating, especially if you have noise coming from more that one source. The key is to strip everything until it is quiet and then add them back in to see where the worst is. Then come up with a plan to try to get rid of the noise.

  • IMac only boots in to Windows

    Hi
    My feonca got a copy of windows today and wanted me to install it for her. I created the partition using bootcamp setup the inserted the windows cd and rebooted. Competed the installation. Then I inserted the Leopard cd and ran the setup for the drivers. Some of the drivers would not install. It was then that I discovered the copy of windows is 64-bit and I cant get leopard back. The iMac only boots in to windows. What can I do to fix this.
    thanks Dan

    Holding down the option (or alt)-key during booting--as soon as you hear the apple chime--doesn't work?

  • Beige G3 boot from **** problem; open firmware issues; bad motherboard?

    Dear all,
    I'm having huge boot/startup problems with my beige G3 that had been happily running OSX 10.3.9, but for purposes of this discussion we can (mostly) revert to OS 9. Originally, the machine was a G3 @300; was upgraded more than a year ago to a ZIF G4 @500.
    To make a long story short, it won't boot from any hard drives, will not boot from any OS X CD, and will only occasionally boot from a 9.x startup CD (whether Apple or Norton Utilities). I think it's an open firmware issue, possibly caused by a bad motherboard (rev. 2).
    All this started happening after I used techtool pro, but I think that's coincidence (even though I acknowledge that, for cops and computer users, there are no coincidences.) Also, as discussed below, I'm having the same problems with an HD that wasn't even in the computer when all these things began.
    Here are some of the things I've done.
    --repeatedly reset PRAM, both with key combinations and removing battery. The only time it will boot from a 9.x CD is after resetting PRAM.
    --removed all add-on PCI cards.
    --removed additional VRAM
    --removed all memory cards and tried replacing one at a time.
    --disconnected both existing hard drives and replaced with an older OS 9.x hard drive (approx 60 mb) that I'd used before. Also tried different ribbon cables.
    --unplugged floppy drive
    --disconnected PCI ATA disk controller that I'd been using for running a large (1.8 gb) hard drive.
    --regarding open firmware: readenv usually shows totally normal default AND installed settings. Using reset-all works fine -- at least it makes the machine reboot, but doesn't solve the problem. reset-nvram does NOT work -- says it's an "unknown word."
    --using startup keys like holding down the option key, or shift key, or X key or cmd-option plus two others I can't remember, has no effect. Again, after I've tried any kind of reboot, the ONLY way to get the C-key at startup to boot the CD is by resetting the pram (key combination). Otherwise, the usual result of these experiments is a dark screen on startup -- nothing at all (and the LCD monitor tells me "no input.")
    --regarding OSX: sometimes (and I emphasize sometimes) I can get the machine to start booting from an OSX 10.2 CD, but it won't complete the process. Sometimes I get a "prohibited" (as in no-parking, no-smoking) icon; sometimes it will start booting (grey screen, OS X Apple icon), then crash (horizontal grey and white jagged bars); sometimes it will show the OS 9 start icon (the tiny smiling Mac SE), but not boot at all.
    --when I get the mac successfully booted with an OS 9.x CD (again, this works sometimes, but not always), the old hard drive with two partitions does show on the desktop and can be accessed. Using either disk repair or Norton Utilities shows the 9.2 system partition on the hard drive to be fine. But if I go to the startup disk control panel, confidently set the 9.2 partition as my startup disk, then reboot, there's no change. It won't boot and I'm back at square one.
    --even when I do get successfully booted with 9.x, the machine will still occasionally crash for no reason -- ie when I'm moving a Window.
    --the only thing I haven't done is slowed down the processor. It's a ZIF G4 bought more than a year ago from XLR8 your Mac. I'm running at the default 500 mhz, and it's never given me any trouble.
    So I think it's a bad motherboard or ROM. Thoughts?
    Thanks.

    The beige Mac is now operating happily again. My original tentative diagnosis remains the same (although still tentative): corrupted PRAM from bad battery, compounded by bad cables that wrote corrupted data to hard drives, and also (possibly) allowing Tech Tool Pro (a utility that I now regard with deep suspicion) to create a "virtual" startup partition.
    A few things I've learned along the way that hopefully may be useful:
    --remember that the Ex Post Facto utility can be used to help OS X startup, not just installation. This applies to hard drives, emergency CDs, installation CDs, etc. If you can boot into any working hard drive partition (OS 9 or a backup OS 10), then run Ex Post Facto (same program runs on either OS 9 or X -- don't ask me how) and tell it what system you want to start up from. Also, the utility has sometimes told me that the startup extensions on the disc that I wanted to boot up from were bad, and offered to fix them (which works).
    --at least on my Mac (beige, v. 2 motherboard), resetting the CUDA button, resetting the PRAM, resetting Open Firmware and "draining" the memory by unplugging the computer and disconnecting the battery for several hours ALL DO DIFFERENT THINGS.
    Specifically, if I'm having trouble booting (from a hard drive or a CD), the FIRST thing I do is restart and resetting the PRAM on the fly -- holding down command, option, P and R at startup, and waiting for the chimes (preferably at least 3-4 times).
    If I do that and DON'T hear the chimes, that's my cue for my SECOND action -- restarting into open firmware (command, option O and F keys on startup). That should bring up the black text on white background open firmware screen. View other posts or apple support for details, but if you do PRINTENV and see a bunch of weird gibberish after the default/installed lists, you know that it was messed up and you need to clear it through reset nvram and reset all commands. Be aware some of these commands do or do not work depending upon what version of Open Firmware you have.
    After I've rebooted with Open Firmware, then on restart I should be able to reset the PRAM on the fly. If that works, then either let the machine run and see what happens, or hold down the C command and see if it will boot from the CD
    Usually, if I've fixed everything as above, the machine will boot into whatever version of OS 9 it finds on a hard drive. That's fine with me -- at that point, use Ex Post Facto to reboot into your OS X. (Before I forget: I used the shareware startup CD creator program BootCD to make an emergency boot CD based on OS 10.2.8 (which theoretically will support a beige mac in native fashion) and Disk Warrior, the god of disk repair utilities. Even though the CD should boot just by holding down the C key on startup, it doesn't -- but if I use Ex Post Facto to boot it, no problems (although the process is very slow -- be patient). Then I can fix almost anything using Disk Warrior.)
    If none of the above works, then I'll try resetting the CUDA (on my beige minitower, it's a very small black button inconveniently located between a PCI slot and the side of the computer housing). Hold it down for 15 seconds. That should REALLY clear the PRAM. I know this does something different from the previous steps because this is the only action (except the battery disconnect -- next) that clears the date and time from the memory.
    If all else fails, I will unplug the computer and disconnect the battery, then push the CUDA button for 15 seconds and let the machine sit overnight.
    One final finding -- I thought I'd fixed everything, but both my hard drives suddenly quit working, I discovered that during all this repeated connect/disconnect of things, one of the male pins inside one of the connectors on my Acard ATA PCI card had broken off. Not good. Fortunately, the card had a second connector, which works fine. And I did some extensive shaking of the computer to make sure (I hope) that the broken pin hadn't landed on a circuit board.
    All this took more than two weeks, and the advice of this board was much appreciated. Now I'm on to my next adventure -- trying to figure out why a combo Firewire/USB PCI card won't mount an external drive on Firewire, but will on USB. I've tried two cards with same result -- but a Firewire-only card works just fine.)
    Regards to all,
    Graham

Maybe you are looking for