Mac mini won't wake up when connected to TV

I just connected my Mac mini (2009) to my LCD TV via HDMI using a mini-DVI to HDMI converter. Twice now when I switch to another input on the TV for any length of time, then I switch back to the Mac's input, the Mac seems to have crashed. The fan starts blowing like crazy and the power light is off. Help!?

Gentlemen,
Thank you for your suggestions. However, I had already reset both my PRAM and SMU. (I should have mentioned that.) However, I have a first generation iMac G5 and I had only tried the unplug the power method. So, I excitedly removed the back cover in search of those little LED diagnostic lights and began experimenting. (BTW, the following link was more accurate for resetting the SMU on an iMac: http://support.apple.com/kb/TS2094).
First of all pressing the SMU button did not solve my problem.
Let me tell you about my diagnostic LEDs. They all come on and stay on just like they should. When I put it to sleep light number 3 goes out, but lights 1 and 2 remain on (just like they should). However, when I have my external HD connected and then put it to sleep, the third light goes out and then a few seconds after that so does the 2nd light.
For "fun" I restarted the computer without the external HD hooked up. My firewire cable WAS connected to the computer, but not to the external HD. I then put it to sleep and light 3 went out and lights 1 and 2 remained on. Then I took the other end of the firewire and connected it to my external hard drive and LED light 2 went out.
Just to clarify: when the computer starts up with the external HD connected all LED lights light just as they should. It is ONLY when the computer goes to sleep with the external HD connected that it shuts down.
One other symptom to throw into the mix (as if there are not enough). In my last several attempts to start up with the internal power button there has been great inconsistency in getting any response if the external HD is connected. However, if I disconnect the external HD, the internal power button powers it right up.
Any ideas? It seems to me that my external drive is the problem. However, I am hesitant to purchase a new hard drive only to find out that its not the problem.
Andy

Similar Messages

Mac mini won't wake properly since osx mavericks

Since I downloaded OSX mavericks, my Mac Mini doesn't wake from sleep. I can see notifications top right of screen and the mouse pointer, so the screen is on and working. Only way to get it going is to hold down the power button to power off and then resatrt. Not very convenient!

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 on some models, 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 models. 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.

Mac mini won't wake from network

Hi, I am confused and need some help.
SInce upgrading to 10.7.2 my mac mini no longer wakes for network access i.e. from ATV2. Worked perfectly before and now it does not.
Also, the screen shows (about once a week) snow on the screen from a wake from sleep. only a reboot solves this.
Any thoughts?

My Mac Mini server (2011) with 10.7.2 has the same problem since 10.7.2 update.

Mac mini won't start up when LCD TV connected

Hi,
I seem to have a problem which at the first glance looks similar to a lot others being discussed here. Just I am not sure if it really is.
Having received my Mac mini a few days ago I am trying desperately to use an LCD TV as display. Once connected powering on the Mac mini gives me that white screen you all know with the grey Apple symbol and the progress circle. At that point the TV says it’s running in 1080i mode. All looks good. -- Until a few seconds later the screen will turn black and not display anything anymore. (Just as if it would not get a signal.)
The TV is a quite popular one over here I would think: Philips 32PF9830, HDTV, with DVI and HDMI input ports. 1280 x 720p and 1920 x 1080i are supported video modes which I would like to run.
TV specs would be here: http://www.p4c.philips.com/files/3/32pf983010/32pf9830_10_psseng.pdf
TV and Mac are connected via a DVI-D cable. I’m having SSH and VNC access to the Mac.
Now with VNC I only get a proper desktop screen when the TV is not connected. When the TV is connected all I am getting presented via VNC is that white boot screen and the nice grey Apple logo. So with TV connected it appears the Mac doesn’t really start the window manager.
Looking at the process list this seems to confirm. Without having the TV connected after powering on the Mac I do see a process running called loginwindow.
When the TV is connected I don’t see that one, but instead 2 processes called WaitingForLoginWindow. See below for the full process lists.
All my trials configuring a good screen resolution via VNC before connecting the TV did not give a different result. Whatever I configure to be used as resolution, I am getting the above.
Funny enough running the Apple Hardware Test from the install disk shows a perfect picture in 1080i mode and also specifies 1920 x 1080i as screen resolution used.
Would anyone have an idea what’s going wrong here … and how to fix? I would suspect that communication between the TV and the Mac is broken. Would I have any chance to further troubleshoot on that?
Is there a way to tell the Mac not to do any auto configuration or auto discovery on the DVI port?
Any other ideas?
Marc
Process lists (NFS and SSH servers are enabled intentionally.)
TV not connected (look for process id 52):
<pre>
ps -axw
PID TT STAT TIME COMMAND
1 ?? 0:00.08 /sbin/launchd -v
23 ?? Ss 0:00.00 /sbin/dynamic_pager -F /private/var/vm/swapfile
27 ?? Ss 0:01.41 kextd
32 ?? Ss 0:00.02 /usr/sbin/KernelEventAgent
33 ?? Ss 0:00.38 /usr/sbin/mDNSResponder -launchdaemon
34 ?? Ss 0:00.20 /usr/sbin/netinfod -s local
35 ?? Ss 0:00.68 /usr/sbin/syslogd
37 ?? Ss 0:01.31 /usr/sbin/configd
38 ?? Ss 0:00.06 /usr/sbin/coreaudiod
39 ?? Ss 0:00.06 /usr/sbin/diskarbitrationd
40 ?? Ss 0:00.01 /usr/sbin/memberd -x
41 ?? Ss 0:00.11 /usr/sbin/securityd
42 ?? Ss 0:00.11 /usr/sbin/notifyd
45 ?? Ss 0:00.29 /usr/sbin/DirectoryService
47 ?? Ss 0:00.01 /usr/sbin/distnoted
49 ?? Ss 0:00.94 /usr/sbin/update
52 ?? Ss 0:00.19 /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow console
57 ?? Ss 0:00.13 /System/Library/CoreServices/coreservicesd
59 ?? Ss 0:00.73 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphic s.framework/Resources/Wind
60 ?? S 0:00.34 /usr/sbin/blued
64 ?? Ss 0:00.06 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer
66 ?? Ss 0:00.11 /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd -s
69 ?? S 0:00.02 /System/Library/CoreServices/SecurityAgent.app/Contents/Resources/authorization host
70 ?? S 0:00.90 /System/Library/CoreServices/SecurityAgent.app/Contents/MacOS/SecurityAgent
76 ?? Ss 0:00.00 /usr/libexec/crashreporterd
114 ?? Us 0:00.30 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mds
132 ?? Ss 0:00.10 ntpd -f /var/run/ntp.drift -p /var/run/ntpd.pid
146 ?? Ss 0:00.00 nfsiod -n 4
154 ?? Ss 0:00.00 rpc.statd
156 ?? Ss 0:00.01 /usr/sbin/portmap
157 ?? Ss 0:00.01 rpc.lockd
160 ?? S 0:00.00 rpc.lockd
173 ?? Ss 0:00.00 mountd
176 ?? Ss 0:00.00 nfsd-master
177 ?? S 0:00.00 nfsd-server
179 ?? S 0:00.00 nfsd-server
180 ?? S 0:00.00 nfsd-server
181 ?? S 0:00.00 nfsd-server
182 ?? S 0:00.00 nfsd-server
183 ?? S 0:00.00 nfsd-server
184 ?? Ss 0:00.02 /usr/sbin/automount -f -m /Network -nsl -mnt /private/var/automount
188 ?? Ss 0:00.01 /usr/sbin/automount -f -m /automount/Servers -fstab -mnt /private/Network/Servers -m /automount/static -s
193 ?? SNs 0:00.17 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdimpo
234 ?? S 0:00.19 /usr/sbin/sshd -i
238 ?? S 0:00.11 /usr/sbin/sshd -i
277 ?? SNs 0:00.17 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdimpo
282 ?? Ss 0:00.01 /usr/sbin/lookupd
239 p0 Ss 0:00.05 -bash
285 p0 R+ 0:00.00 ps -axw
</pre>
TV connected (look for PIDs 53 and 54 at end of the list):
<pre>
PID TT STAT TIME COMMAND
1 ?? 0:00.05 /sbin/launchd
23 ?? Ss 0:00.00 /sbin/dynamic_pager -F /private/var/vm/swapfile
27 ?? Ss 0:01.35 kextd
32 ?? Ss 0:00.02 /usr/sbin/KernelEventAgent
33 ?? Ss 0:00.30 /usr/sbin/mDNSResponder -launchdaemon
34 ?? Ss 0:00.13 /usr/sbin/netinfod -s local
35 ?? Ss 0:00.71 /usr/sbin/syslogd
37 ?? Ss 0:00.49 /usr/sbin/configd
38 ?? Ss 0:00.07 /usr/sbin/coreaudiod
39 ?? Ss 0:00.06 /usr/sbin/diskarbitrationd
40 ?? Ss 0:00.01 /usr/sbin/memberd -x
41 ?? Ss 0:00.14 /usr/sbin/securityd
42 ?? Ss 0:00.07 /usr/sbin/notifyd
44 ?? Ss 0:00.17 /usr/sbin/DirectoryService
45 ?? Ss 0:00.01 /usr/sbin/distnoted
50 ?? Ss 0:08.36 /usr/sbin/update
59 ?? Ss 4:43.49 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphic s.framework/Resources/Wind
60 ?? S 0:00.33 /usr/sbin/blued
61 ?? Ss 0:00.14 /System/Library/CoreServices/coreservicesd
65 ?? Ss 0:00.07 /usr/sbin/lookupd
79 ?? Ss 0:00.88 ntpd -f /var/run/ntp.drift -p /var/run/ntpd.pid
93 ?? Ss 0:00.00 nfsiod -n 4
101 ?? Ss 0:00.00 rpc.statd
102 ?? Ss 0:00.01 /usr/sbin/portmap
104 ?? Ss 0:00.01 rpc.lockd
109 ?? Ss 0:00.06 slpd -f /etc/slpsa.conf
110 ?? S 0:00.00 rpc.lockd
115 ?? Ss 0:00.00 /usr/libexec/crashreporterd
135 ?? Ss 0:00.05 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer
158 ?? Ss 0:00.12 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mds
164 ?? Ss 0:00.00 mountd
167 ?? Ss 0:00.00 nfsd-master
168 ?? S 0:00.00 nfsd-server
169 ?? S 0:00.00 nfsd-server
170 ?? S 0:00.00 nfsd-server
172 ?? S 0:00.00 nfsd-server
173 ?? S 0:00.00 nfsd-server
174 ?? S 0:00.00 nfsd-server
175 ?? Ss 0:00.02 /usr/sbin/automount -f -m /Network -nsl -mnt /private/var/automount
179 ?? Ss 0:00.01 /usr/sbin/automount -f -m /automount/Servers -fstab -mnt /private/Network/Servers -m /automount/static -s
196 ?? S 0:00.20 /usr/sbin/sshd -i
200 ?? S 0:00.06 /usr/sbin/sshd -i
205 ?? SNs 0:00.14 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdimpo
201 p0 Ss 0:00.03 -bash
209 p0 R+ 0:00.00 ps -axw
2 ?? Ss+ 0:00.03 sh /etc/rc
53 ?? S+ 0:00.02 /usr/libexec/WaitingForLoginWindow
54 ?? S+ 0:00.04 /usr/libexec/WaitingForLoginWindow
</pre>
Mac Mini Mac OS X (10.4.8)

A PRRAM reset did the trick.
http://docs.info.apple.com/article.html?artnum=2238
This Mac mini is a refurbished one, so probably had some old settings from being connected to something different before.
The TV now is recognized properly as 'Philips FTV'.
Marc

What's wrong with my trackpad? It was working fine, then I installed Lion 10.8.1 and now the mac mini won't see it, when I press the on button, a light comes on after a brief pause, stays on for a second or so, and then goes off, still no trackpad..

Ok, so if you haven't worked it out, this is my first post. My problem is all in the title, but once more won't hurt..
I have a bluetooth trackpad which has been attached to my mac mini for a few months now, with only the occasional connection lost, connection found saga that everyone seems to go through. Earlier today, I used the trackpad to upgrade to OSX 10.8.1 nd when the computer rebooted, no trackpad could be found. I've put fresh batteries in, I've tried rebooting the mac mini, I've checked sys preferences and am currently using an old usb keyboard which is v flimsy so forgive any typos please.
The light comes on about a second after the on button is pressed, (whether the button is held down or not) and then goes off after a second, still no trackpad is found..
Why?!!!!

No, not paired to anything else, fresh out the box connected to the mac mini I bought at the same time, never been paired with anything else.
I think it's a hardware issue. As I don't seem to be able to get it to turn off.

PB won't wake up when connected to ACD

I have a brand new (day old) Aluminum PB with the following configuration:
1. 1.67Ghz G4
2. 1.5G RAM (DDR2 SDRAM)
3. Mac OSX 10.4.3
It replaces a 3 year old Titanium running 10.4.3 which has never exhibited the problems below.
-- GOOD SITUATIONS --
When NOT connected to the ACD, and the screensaver kicks in, I can wake the PB just fine.
When connected to the ACD, and I force "Sleep" mode, I can wake the PB just fine.
-- MEDIOCRE SITUATIONS --
Sometimes, when the PB awakes, after a couple of minutes, the Finder stops responding and I get the spinning wheel of death. More on this in a separate posts "Finder Not Responding After PB Wakens"
-- BAD SITUATIONS (REASON FOR THE POSTING) --
HOWEVER, when connected to the ACD, and the screensaver kicks in and runs for more than a couple of minutes -OR- eventually goes to full sleep on its own, I cannot wake it.
When I try to wake it under these two circumstances, the PB sounds like it is awakening, and I get a black screen (screensaver goes away if not asleep), then I see my mouse pointer, then I get the spinning wheel of death and at that point it's all over (I can wait 10 minutes and nothing).
I've done a hardware test and all is OK according to the test.
I have done the following things to resolve and, yet, nothing works:
1. Repaired Disk Permissions
2. Cleared out my Login/Startup files
3. Reset the PRAM
4. Performed a control-option Restart (recommended before doing a PMU reset)
5. Performed a PMU reset
I am at a complete loss. Please help!!!
David
Powerbook G4 Aluminum Mac OS X (10.4.3)

I think I have narrowed the problem down to a USB issue (USB connection between the hub on the ACD (Apple Cinema Display) and the PB.
When I unplug the USB connector from the port, the login in window miraculously appears. Now, I need to track down the REASON for this.
Thanks for your help.
David

Mac Mini won't wake up

I've had my mini for about 3 months and it worked great plugged into my Samsung 52" display with Logitech wireless mouse and Kensington wireless keyboard.
Recently the mini has stopped waking from keyboard or mouse activity. Once in this mode, the LED on the front continues to pulse, but does not output a video signal. The only way to recover from this state is to hard power down the unit by holding the power button. Upon restart, the unit takes about 15 minutes to fully recover. It spends a small amount of time at the blank white screen and then spends the next 10-15 minutes on the blue screen. After this, it eventually recovers and allows me to use it.
If I perform a regular reset once the unit is responding, it still is taking the 15 minutes to reboot. Additionally, if I let it go to sleep, I must perform the entire forced shutdown again.
I performed the SMC and PMU resets with no luck.
Are there any logs or utilities I should be looking at?
Is it time to take this thing in for repair?
Here is a recent log of the minis ups and downs:
11/6/08 6:55:20 PM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
11/6/08 6:55:20 PM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
11/6/08 6:55:20 PM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
11/6/08 6:55:36 PM org.ntp.ntpd[14] Error : nodename nor servname provided, or not known
11/6/08 7:00:35 PM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[74]) Exited: Terminated
11/6/08 7:01:16 PM KeyboardSetupAssistant[98] writeKeyboardType <1166-1241-0> 40
11/6/08 7:01:16 PM KeyboardSetupAssistant[98] writeKeyboardType <259-4711-0> 40
11/6/08 7:07:40 PM com.apple.launchctl.System[2] fsck_hfs: Volume is journaled. No checking performed.
11/6/08 7:07:40 PM com.apple.launchctl.System[2] fsck_hfs: Use the -f option to force checking.
11/6/08 7:07:42 PM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
11/6/08 7:07:42 PM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
11/6/08 7:07:42 PM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
11/6/08 7:08:52 PM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
11/6/08 7:08:52 PM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
11/6/08 7:08:52 PM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
11/6/08 7:14:10 PM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[73]) Exited: Terminated
11/6/08 7:14:27 PM Finder[93] [QL ERROR] Generator database update takes too long... we will use what we currently have
11/6/08 7:16:10 PM com.apple.loginwindow[22] Shutdown NOW!
11/6/08 7:16:10 PM com.apple.loginwindow[22] System shutdown time has arrived
11/6/08 7:18:05 PM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
11/6/08 7:18:05 PM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
11/6/08 7:18:05 PM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
11/6/08 7:23:20 PM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[72]) Exited: Terminated
11/6/08 8:52:10 PM com.apple.launchctl.System[2] fsck_hfs: Volume is journaled. No checking performed.
11/6/08 8:52:10 PM com.apple.launchctl.System[2] fsck_hfs: Use the -f option to force checking.
11/6/08 8:52:12 PM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
11/6/08 8:52:12 PM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
11/6/08 8:52:12 PM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
11/6/08 8:57:33 PM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[74]) Exited: Terminated
Thanks,
Chris

Forced shutdowns can cause filesystem corruption and should be avoided when possible -- and not be used as standard operating procedure.
After a forced shutdown I always run DiskUtility and verify the hard drive.
Your longer startup time is probably due to the Mac trying to verify the system with fsck after the forced shutdown.
Suggestions:
1) Run DiskUtility and verify the hard drive; if it won't verify, you'll have to boot from the original install disc (hold down C key at boot -- using a wired usb keyboard) and run DiskUtility from the Utilities menu at the top of the install disc screen;if you can't repair the drive with DU you may have to back up your data and do a clean re-install of the OS; alternatively DiskWarrior may be able to repair a drive that DiskUtility can't.
2) Get to the bottom of this problem; your current MO is going to cause you more and more grief
3) Try pressing the menu button on the Apple remote once to wake the Mini
4) Don't do a PMU reset on an Intel Mini -- Intels get the SMC reset instead of the PMU reset -- the PMU reset procedure is known to cause problems when wrongly applied to Intels.
5) If you can get your hard drive to verify and you still have problems, reapplying the latest combo update of OSX can sometimes clear up problems.

New Mac mini won't come out of sleep because trackpad won't connect

I have a new Mac mini with a trackpad. When Mac is in sleep mode I can't wake it as trackpad and keyboard won't connect. On occasion they do but the Mac takes ~5mins to fully wake.
Andy

I have a new Mac mini with a trackpad. When Mac is in sleep mode I can't wake it as trackpad and keyboard won't connect. On occasion they do but the Mac takes ~5mins to fully wake.
Andy

Mac mini won't connect to internet two days after installing 10.4.4

Two days after I installed 10.4.4 on my Mac mini. It will no longer connect to the internet. At first I thought it was just the airport extreme card malfunctioning. So today I turned off the airport extreme card, and tried the built-in ethernet and I'm having the same problem. The odd thing with the airport extreme card is that it showing that its connected to the right network but won't do anything.
Any suggestions?
Mac mini Mac OS X (10.4.4)

Hmm, this is interesting. I seem to be having the
same problem. I too have a Mac Mini and upgraded to
10.4.4 a couple of days ago. It doesn't seem to be
pulling an IP address from our DHCP server(Win and
Lin clients are working fine), and when I give it a
static IP, I can't ping anything from the Mini.
However, I can ping the Mini from other
boxes. It does it with wifi as well as ethernet. I
know the wifi AP is working fine - other clients are
running with it, and the Cat5 I used to connect the
Mini to a switch should be working fine(it was what
the access point is/was using to connect to the
switch).
Maybe its totally unrelated, but it your situation
seems eerily similar to mine.
It does your situation does sound very close to mine. Like you said in your post I can ping the mini from other machines and I get responses back, but I can't ping anything from the mini.
The more I think about this problem I'm not sure if its hardware related, software related, or both. I wish I had another hard drive that I could boot from externally to see if my theory is correct.

Mac mini won't connect to my wireless router!

I just bought my mac mini server then connected it to wifi, then after 2 weeks I had to go abroad for a week so I just turned off the switch connecting to my mac, without switching off my mac mini server. then when I get back home my mac mini won't connect to my wifi. I tried everything from manually setting up IP and DHCP nothing works. What happened?
thanks for help,
Jakarta

I didn't reset the machine/router itself because 2 of my computer is still connected to wifi-and working perfectly, but the mac mini server cannot connect to wifi.
what I did was to set up the "networking utilities"-having said that, what I did was to connect all over again to wifi, this did not work. I did tried to change from DHCP to manually set up IP, neither of these didn't work.
I'm now stucked!
Message was edited by: asea

Mac mini won't connect to printer unless other mac on network turned on

mac mini won't connect to printer unless other mac on network turned on

Copy the IP address of the printer from the Mac that can connect to it by itself. The IP shows when you start any print job.
Disable Printer sharing on this Mac.
Go to the Mac that cannot connect by itself and set up the printer from scratch using the printer's IP. To do this:
System Preferences / Print & Scan, then click the + sign, nxt select Add Printer or Scanner and click on IP. Fill in the info.

Suddenly Mac mini won't "see" external drives. Possible related to OS software update to 10.6.8?

Suddenly Mac mini won't "see" external drives, neither Firewire nor USB. Possible related to OS software update to 10.6.8? Worked fine under 10.6.4. Any advice? Thanks.

Turns out it was nothing to do with the OS update, it was just a loose cable plug connecting my FireWire/USB hub to the computer. But your tip is a good one -- I'd been wondering why the external drives (even when mounted properly) weren't showing up in the sidebar. Thanks!

My mac mini won't start up!

My mac mini won't start up but it will turn on, staying at the gray apple logo screen and nothing else.
I came home yesterday and it wouldn't 'wake up' from 'sleep' mode so I turned it off and tried to turn it back on. There's a netflix cd in there that I also can't get out. My friend suggested i slip a piece of paper in there and that it will eject, but this isn't working (maybe I'm doing this wrong?)
help! thanks.

I have the same problem. In addition, the same happens when attempting to boot from a DVD. I was able to boot it up in Target Disc Mode, and even erase the internal HD entirely, but I still cannot boot from DVD to reinstall the OS. I have tried the SMC reset, but to no avail. Also, while I can reset the PRAM, I cannot reset the Open Firmware. Any suggestions?

Mac mini won't boot anymore

My Mac mini won't boot anymore. It's been running fine for months.
It's running Leopard Server 10.5.2 Build 9C31
It starts to boot, I get the first spinning gear with the gray screen, then the blue desktop blinks, then a second spinning gear on a gray screen and it appears to hang (the gear stops spinning).
I booted off the install DVD, ran disk utility, repaired the HD, repaired the permissions: the behavior is the same.
Safe mode doesn't work (same hang as above).
Single user mode does work.
I can connect to it via Server Admin while it appears hung.
The last few lines of the system log are:
May 15 18:38:58 server emond[67]: SetUpLogs: uid = 0 gid = 0
May 15 18:38:58 server emond[67]: SetUpLogs: opening /Library/Logs/EventMonitor/EventMonitor.error.log
May 15 18:38:59 server kextd[23]: writing kernel link data to /var/run/mach.sym
May 15 18:39:09 server KernelEventAgent[59]: tid 00000000 received unknown event (12)
May 15 18:39:20 server kernel[0]: display: Not usable
May 15 18:39:20 server com.apple.KerberosAutoConfig[126]: Kerberos configuration is up to date
May 15 18:39:20 server com.apple.ATSServer[125]: FODBCheck: New annex file created
May 15 18:39:21 server ARDAgent [130]: ******ARDAgent Launched******
May 15 18:39:21 server com.apple.KerberosAutoConfig[132]: Kerberos configuration is up to date
May 15 18:39:22 server ARDAgent [130]: call logout from LoginLogoutProxyCallBackFunction
May 15 18:39:22 server com.apple.launchd[1] (com.apple.RemoteDesktop.agent): Throttling respawn: Will start in 9 seconds
May 15 18:39:24 server loginwindow[58]: Login Window Started Security Agent
May 15 18:39:29 server servermgrd[53]: servermgr_calendar: created default calendar virtual host
May 15 18:39:31 server ARDAgent [146]: ******ARDAgent Launched******
May 15 18:39:32 server ARDAgent [146]: ******ARDAgent Ready******
May 15 18:39:33 server mdworker[109]: (Error) SyncInfo: Boot-cache avoidance timed out!
May 15 18:39:54 server Python[47]: CGImageSourceCreateWithData data parameter is nil
May 15 18:39:54 server com.apple.wikid[47]: Thu May 15 18:39:54 server.jeff.carpenter.name Python[47] <Error>: CGImageSourceCreateWithData data parameter is nil\n
May 15 18:39:56 server kernel[0]: AppleYukon2 - bad packet received. length: 1440, packet status bits: MII error
May 15 18:39:56 server kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
May 15 18:49:54 server kernel[0]: serialnumberd 194 FSWRITEDATA SBF /dev/dtracehelper 13 (seatbelt)
May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /dev/autofs_nowait 13 (seatbelt)
May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /usr/sbin 13 (seatbelt)
May 15 18:55:12 server kernel[0]: AppleYukon2 - bad packet received. length: 23, packet status bits: MII error
Any ideas?

Yes, it's been running Server since I purchased it.
I doubt the serial number is in use elsewhere: I purchased the 10-user version at a retail store in a sealed package and I've only installed it once.

Mac Mini won't start and constantly makes disc ejecting noise

My Mac Mini won't start. It was working fine, then just locked up and won't start again. When I push the start button it just makes this repeated disc ejecting noise from the DVD drive. It doesn't make the chime noise or display anything on the monitor. I've disconnected the optical drive, but it didn't help. Then it just doesn't start at all. I thought that if I would disconnect the optical drive, that it would ignore it and just boot off the hard drive, but nothing happened. The power light comes on. Then, if I hold down the power button for 10 seconds it shuts down. The fan operates. It just never attempts to boot up. I can't put in a system DVD because the optical drive is just in eternal eject mode.
If you have any suggestions let me know. Thanks.

I have the same situation.
I think the drive thinks it has a disc to eject or part of the mechanism is stuck and can't return to it's resting position. I was going to disconnect as you tried but now I think I'll try to disassemble the drive to see if there might be some debris jamming things up.
Please let me know if you solve the problem.

Mac mini won't wake up when connected to TV

Similar Messages

Maybe you are looking for