I don't think it's dust. My core2duo was sleeping when I left in the afternoon. I came home around 10:30 at night. Around 11:30, 11:45 I noticed that the machine was on, although I hadn't gone near it. I checked the logs and found the following. FYI, BlueTooth and AirPort are turned off on this machine (10.4.9).
Apr 29 15:25:11 bliss cp: error processing extended attributes: Operation not permitted
Apr 29 23:09:33 bliss kernel[0]: System Sleep
Apr 29 23:09:33 bliss configd[35]: AppleTalk shutdown
Apr 29 23:09:33 bliss kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Apr 29 23:09:33 bliss kernel[0]: Started CPU 01
Apr 29 23:09:33 bliss kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep Apr 29 23:09:33 bliss kernel[0]: System Wake
Apr 29 23:09:33 bliss kernel[0]: USB caused wake event (EHCI) Apr 29 23:09:33 bliss kernel[0]: IOBluetoothHCIController::terminateWL .. done
Apr 29 23:09:34 bliss kernel[0]: AppleYukon - en0 link active, 100-Mbit, full duplex, symmetric flow control enabled
Apr 29 23:09:40 bliss configd[35]: AppleTalk shutdown complete Apr 29 23:09:40 bliss configd[35]: AppleTalk startup
Apr 29 23:09:40 bliss kernel[0]: CSRHIDTransitionDriver::probe: Apr 29 23:09:40 bliss kernel[0]: CSRHIDTransitionDriver::start before command
Apr 29 23:09:41 bliss kernel[0]: CSRHIDTransitionDriver::stop Apr 29 23:09:42 bliss kernel[0]: IOBluetoothHCIController::start Idle Timer Stopped
Apr 29 23:09:42 bliss kernel[0]: Registering For 802.11 Events Apr 29 23:09:42 bliss kernel[0]: [HCIController][setupHardware] AFH Is Supported
Apr 29 23:09:46 bliss configd[35]: AppleTalk startup complete Apr 30 09:24:19 bliss kernel[0]: System Sleep
See the line that begins:IOBluetoothHCIController::restartShutdownWL this is a wake from sleep.
What's that about? I'm beginning to suspect some randome cellphone walk-by as the culprit.
On 2007-04-30 09:26:39 -0500, RobertB said:
See the line that begins:IOBluetoothHCIController::restartShutdownWL this is a wake from sleep.
What's that about? I'm beginning to suspect some randome cellphone walk-by as the culprit.
You missed this line:
Apr 29 23:09:33 bliss kernel[0]: USB caused wake event (EHCI)
A cell phone is not the culprit. Something on your USB bus is doing this.
JR
On 2007-04-30 09:26:39 -0500, RobertB said:
(snip)Apr 29 23:09:33 bliss kernel[0]: System Sleep
Apr 29 23:09:33 bliss kernel[0]: System Wake
Your system recorded consecutive sleep and wake events at 11:09:33 PM. How sure are you the computer was asleep prior to this event?
JR
Previously, Jolly Roger wrote:
On 2007-04-30 09:26:39 -0500, RobertB said:
See the line that begins:IOBluetoothHCIController::restartShutdownWL this is a wake from sleep.
What's that about? I'm beginning to suspect some randome cellphone walk-by as the culprit.
You missed this line:
Apr 29 23:09:33 bliss kernel[0]: USB caused wake event (EHCI)
A cell phone is not the culprit. Something on your USB bus is doing this.
There's nothing on the USB but the keyboard and mouse. Yes, I noticed that. Any idea what EHCI might be?
Previously, Jolly Roger wrote:
On 2007-04-30 09:26:39 -0500, RobertB said:
(snip)Apr 29 23:09:33 bliss kernel[0]: System Sleep
Apr 29 23:09:33 bliss kernel[0]: System Wake
Your system recorded consecutive sleep and wake events at 11:09:33 PM. How sure are you the computer was asleep prior to this event?
Well, it was asleep when I left in the afternoon, of that I am certain. It was asleep when I returned around 10:230 (22:30:00), of that I'm more or less certain since the screen was dark. How could it go to sleep and wake up at the same time?
On 2007-05-01 09:17:27 -0500, RobertB said:
Previously, Jolly Roger wrote:
On 2007-04-30 09:26:39 -0500, RobertB said:
See the line that begins:IOBluetoothHCIController::restartShutdownWL this is a wake from sleep.
What's that about? I'm beginning to suspect some randome cellphone walk-by as the culprit.
You missed this line:
Apr 29 23:09:33 bliss kernel[0]: USB caused wake event (EHCI)
A cell phone is not the culprit. Something on your USB bus is doing this.
There's nothing on the USB but the keyboard and mouse. Yes, I noticed that. Any idea what EHCI might be?
I take it back. I forgot that Bluetooth compatibility is implemented with HCI through a USB interface.
JR
Previously, Jolly Roger wrote:
On 2007-05-01 09:17:27 -0500, RobertB said:
Previously, Jolly Roger wrote:
On 2007-04-30 09:26:39 -0500, RobertB said:
See the line that begins:IOBluetoothHCIController::restartShutdownWL this is a wake from sleep.
What's that about? I'm beginning to suspect some randome cellphone walk-by as the culprit.
You missed this line:
Apr 29 23:09:33 bliss kernel[0]: USB caused wake event (EHCI)
A cell phone is not the culprit. Something on your USB bus is doing this.
There's nothing on the USB but the keyboard and mouse. Yes, I noticed that. Any idea what EHCI might be?
I take it back. I forgot that Bluetooth compatibility is implemented with HCI through a USB interface.
You referring to the fact that one can use a Bluetooth mouse and keyboard? Could an external Bluetooth device wake a computer like that? It would have to have been a cell phone used by someone passing in the hallway outside the apartment. Although I have a Bluetooth-enabled cell phone. However, I have never used the Bluetooth feature on the phone. Also, I have it turned off on the iMac. Just some random signal?
On 2007-05-02 11:57:34 -0500, RobertB said:
Previously, Jolly Roger wrote:
On 2007-05-01 09:17:27 -0500, RobertB said:
Previously, Jolly Roger wrote:
On 2007-04-30 09:26:39 -0500, RobertB said:
See the line that begins:IOBluetoothHCIController::restartShutdownWL this is a wake from sleep.
What's that about? I'm beginning to suspect some randome cellphone walk-by as the culprit.
You missed this line:
Apr 29 23:09:33 bliss kernel[0]: USB caused wake event (EHCI)
A cell phone is not the culprit. Something on your USB bus is doing this.
There's nothing on the USB but the keyboard and mouse. Yes, I noticed that. Any idea what EHCI might be?
I take it back. I forgot that Bluetooth compatibility is implemented with HCI through a USB interface.
You referring to the fact that one can use a Bluetooth mouse and keyboard? Could an external Bluetooth device wake a computer like that? It would have to have been a cell phone used by someone passing in the hallway outside the apartment. Although I have a Bluetooth-enabled cell phone. However, I have never used the Bluetooth feature on the phone. Also, I have it turned off on the iMac. Just some random signal?
You have to pair Bluetooth devices with Macs in order to connect and do things. And pairing requires user interaction on both ends to authenticate the operation. I suppose it could be that someone is *attempting* to pair up to your computer or something like that. Have you looked around in your Bluetooth settings in System Preferences to make sure things are set in a secure manner?
JR
RobertB wrote:
I don't think it's dust. My core2duo was sleeping when I left in the afternoon. I came home around 10:30 at night. Around 11:30, 11:45 I noticed that the machine was on, although I hadn't gone near it. I checked the logs and found the following. FYI, BlueTooth and AirPort are turned off on this machine (10.4.9).
Apr 29 15:25:11 bliss cp: error processing extended attributes: Operation not permitted
Apr 29 23:09:33 bliss kernel[0]: System Sleep
Apr 29 23:09:33 bliss configd[35]: AppleTalk shutdown
Apr 29 23:09:33 bliss kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Apr 29 23:09:33 bliss kernel[0]: Started CPU 01
Apr 29 23:09:33 bliss kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep Apr 29 23:09:33 bliss kernel[0]: System Wake
Apr 29 23:09:33 bliss kernel[0]: USB caused wake event (EHCI) Apr 29 23:09:33 bliss kernel[0]: IOBluetoothHCIController::terminateWL .. done
Apr 29 23:09:34 bliss kernel[0]: AppleYukon - en0 link active, 100-Mbit, full duplex, symmetric flow control enabled
Apr 29 23:09:40 bliss configd[35]: AppleTalk shutdown complete Apr 29 23:09:40 bliss configd[35]: AppleTalk startup
Apr 29 23:09:40 bliss kernel[0]: CSRHIDTransitionDriver::probe: Apr 29 23:09:40 bliss kernel[0]: CSRHIDTransitionDriver::start before command
Apr 29 23:09:41 bliss kernel[0]: CSRHIDTransitionDriver::stop Apr 29 23:09:42 bliss kernel[0]: IOBluetoothHCIController::start Idle Timer Stopped
Apr 29 23:09:42 bliss kernel[0]: Registering For 802.11 Events Apr 29 23:09:42 bliss kernel[0]: [HCIController][setupHardware] AFH Is Supported
Apr 29 23:09:46 bliss configd[35]: AppleTalk startup complete Apr 30 09:24:19 bliss kernel[0]: System SleepSee the line that begins:IOBluetoothHCIController::restartShutdownWL this is a wake from sleep.
What's that about? I'm beginning to suspect some randome cellphone walk-by as the culprit.
I don't have bluetooth, but my Mac has occasionally waked when I came in the door. Moving the mouse will wake it, and my theory was that sometimes the vibration of walking could cause the optical mouse to signal movement.
The other day I discovered more about it. The cursor kept freezing. The light in my cordless USB mouse would stay bright or stay off or flicker until I reinstalled the batteries. Then the cursor would work.
With a magnifier I saw tiny bits if debris on the eye in the mouse. I stuck the corner of a handkerchief in there and turned it. That cured the problem.
So an optical mouse can respond to dirt even when you aren't touching it. Maybe debris or a hair or a tiny bug caused your mouse to wake your Mac.
Previously, Denominator wrote:
I don't have bluetooth, but my Mac has occasionally waked when I came in the door. Moving the mouse will wake it, and my theory was that sometimes the vibration of walking could cause the optical mouse to signal movement.
Hmmm, no amount of mouse motion will wake my iMac when it's sleeping. Moving the mouse will wake a sleeping display, but not a sleeping processor, only a keystroke will do that.
Tom Stiller
PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3
7BDA 71ED 6496 99C0 C7CF
Tom Stiller wrote:
Previously, Denominator wrote:
I don't have bluetooth, but my Mac has occasionally waked when I came in the door. Moving the mouse will wake it, and my theory was that sometimes the vibration of walking could cause the optical mouse to signal movement.
Hmmm, no amount of mouse motion will wake my iMac when it's sleeping. Moving the mouse will wake a sleeping display, but not a sleeping processor, only a keystroke will do that.
I have a G4 Mini with 10.4.9 and a Logitech cordless mouse/keyboard set interfacing through USB. It seems that one small move won't wake the Mac. One big move (an inch or so), or several little moves will wake it.
I think maybe if there's some sort of debris under the eye, the mouse could wake the Mac without being moved.
I see that if I put it to sleep at 23:40 and wake it at 23:50, the system log will say it went to sleep and woke at 23:50. So the OP's log was probably wrong in reporting that it woke at the same time it went to sleep.
Previously, Jolly Roger wrote:
On 2007-05-02 11:57:34 -0500, RobertB said:
Previously, Jolly Roger wrote:
On 2007-05-01 09:17:27 -0500, RobertB said:
Previously, Jolly Roger wrote:
On 2007-04-30 09:26:39 -0500, RobertB said:
See the line that begins:IOBluetoothHCIController::restartShutdownWL this is a wake from sleep.
What's that about? I'm beginning to suspect some randome cellphone walk-by as the culprit.
You missed this line:
Apr 29 23:09:33 bliss kernel[0]: USB caused wake event (EHCI)
A cell phone is not the culprit. Something on your USB bus is doing this.
There's nothing on the USB but the keyboard and mouse. Yes, I noticed that. Any idea what EHCI might be?
I take it back. I forgot that Bluetooth compatibility is implemented with HCI through a USB interface.
You referring to the fact that one can use a Bluetooth mouse and keyboard? Could an external Bluetooth device wake a computer like that? It would have to have been a cell phone used by someone passing in the hallway outside the apartment. Although I have a Bluetooth-enabled cell phone. However, I have never used the Bluetooth feature on the phone. Also, I have it turned off on the iMac. Just some random signal?
You have to pair Bluetooth devices with Macs in order to connect and do things. And pairing requires user interaction on both ends to authenticate the operation. I suppose it could be that someone is *attempting* to pair up to your computer or something like that. Have you looked around in your Bluetooth settings in System Preferences to make sure things are set in a secure manner?
Well, how secure do they need to be if Bluetooth is turned off?
Previously, Denominator wrote:
RobertB wrote:
I don't think it's dust. My core2duo was sleeping when I left in the afternoon. I came home around 10:30 at night. Around 11:30, 11:45 I noticed that the machine was on, although I hadn't gone near it. I checked the logs and found the following. FYI, BlueTooth and AirPort are turned off on this machine (10.4.9).
Apr 29 15:25:11 bliss cp: error processing extended attributes: Operation not permitted
Apr 29 23:09:33 bliss kernel[0]: System Sleep
Apr 29 23:09:33 bliss configd[35]: AppleTalk shutdown
Apr 29 23:09:33 bliss kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Apr 29 23:09:33 bliss kernel[0]: Started CPU 01
Apr 29 23:09:33 bliss kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep Apr 29 23:09:33 bliss kernel[0]: System Wake
Apr 29 23:09:33 bliss kernel[0]: USB caused wake event (EHCI) Apr 29 23:09:33 bliss kernel[0]: IOBluetoothHCIController::terminateWL .. done
Apr 29 23:09:34 bliss kernel[0]: AppleYukon - en0 link active, 100-Mbit, full duplex, symmetric flow control enabled
Apr 29 23:09:40 bliss configd[35]: AppleTalk shutdown complete Apr 29 23:09:40 bliss configd[35]: AppleTalk startup
Apr 29 23:09:40 bliss kernel[0]: CSRHIDTransitionDriver::probe: Apr 29 23:09:40 bliss kernel[0]: CSRHIDTransitionDriver::start before command
Apr 29 23:09:41 bliss kernel[0]: CSRHIDTransitionDriver::stop Apr 29 23:09:42 bliss kernel[0]: IOBluetoothHCIController::start Idle Timer Stopped
Apr 29 23:09:42 bliss kernel[0]: Registering For 802.11 Events Apr 29 23:09:42 bliss kernel[0]: [HCIController][setupHardware] AFH Is Supported
Apr 29 23:09:46 bliss configd[35]: AppleTalk startup complete Apr 30 09:24:19 bliss kernel[0]: System SleepSee the line that begins:IOBluetoothHCIController::restartShutdownWL this is a wake from sleep.
What's that about? I'm beginning to suspect some randome cellphone walk-by as the culprit.
I don't have bluetooth, but my Mac has occasionally waked when I came in the door. Moving the mouse will wake it, and my theory was that sometimes the vibration of walking could cause the optical mouse to signal movement.
The other day I discovered more about it. The cursor kept freezing. The light in my cordless USB mouse would stay bright or stay off or flicker until I reinstalled the batteries. Then the cursor would work.
With a magnifier I saw tiny bits if debris on the eye in the mouse. I stuck the corner of a handkerchief in there and turned it. That cured the problem.
So an optical mouse can respond to dirt even when you aren't touching it. Maybe debris or a hair or a tiny bug caused your mouse to wake your Mac.
Someone had suggested that once before. Could be, but it seems odd that the vibrations would be felt on the desktop, especially since I'm not in the habit of slamming doors when I come in. The mouse looks clean.
Previously, Denominator wrote:
Tom Stiller wrote:
Previously, Denominator wrote:
I don't have bluetooth, but my Mac has occasionally waked when I came in the door. Moving the mouse will wake it, and my theory was that sometimes the vibration of walking could cause the optical mouse to signal movement.
Hmmm, no amount of mouse motion will wake my iMac when it's sleeping. Moving the mouse will wake a sleeping display, but not a sleeping processor, only a keystroke will do that.
I have a G4 Mini with 10.4.9 and a Logitech cordless mouse/keyboard set interfacing through USB. It seems that one small move won't wake the Mac. One big move (an inch or so), or several little moves will wake it.
I think maybe if there's some sort of debris under the eye, the mouse could wake the Mac without being moved.
I see that if I put it to sleep at 23:40 and wake it at 23:50, the system log will say it went to sleep and woke at 23:50. So the OP's log was probably wrong in reporting that it woke at the same time it went to sleep.
That's interesting. Why would the log be set up that way?
On 2007-05-03 09:02:26 -0500, RobertB said:
You have to pair Bluetooth devices with Macs in order to connect and do things. And pairing requires user interaction on both ends to authenticate the operation. I suppose it could be that someone is *attempting* to pair up to your computer or something like that. Have you looked around in your Bluetooth settings in System Preferences to make sure things are set in a secure manner?
Well, how secure do they need to be if Bluetooth is turned off?
Not at all, since the radio receiver is powered off in that state. If this is the case on your Mac when it has these wake-from-sleep issues, then the problem must be coming from elsewhere.
JR
RobertB wrote:
Previously, Denominator wrote:
Tom Stiller wrote:
Previously, Denominator wrote:
I don't have bluetooth, but my Mac has occasionally waked when I came in the door. Moving the mouse will wake it, and my theory was that sometimes the vibration of walking could cause the optical mouse to signal movement.
Hmmm, no amount of mouse motion will wake my iMac when it's sleeping. Moving the mouse will wake a sleeping display, but not a sleeping processor, only a keystroke will do that.
I have a G4 Mini with 10.4.9 and a Logitech cordless mouse/keyboard set interfacing through USB. It seems that one small move won't wake the Mac. One big move (an inch or so), or several little moves will wake it.
I think maybe if there's some sort of debris under the eye, the mouse could wake the Mac without being moved.
I see that if I put it to sleep at 23:40 and wake it at 23:50, the system log will say it went to sleep and woke at 23:50. So the OP's log was probably wrong in reporting that it woke at the same time it went to sleep.
That's interesting. Why would the log be set up that way?
I suppose it's a programming oversight. It goes to sleep without writing in the log.
RobertB wrote:
Previously, Denominator wrote:
RobertB wrote:
I don't think it's dust. My core2duo was sleeping when I left in the afternoon. I came home around 10:30 at night. Around 11:30, 11:45 I noticed that the machine was on, although I hadn't gone near it. I checked the logs and found the following. FYI, BlueTooth and AirPort are turned off on this machine (10.4.9).
Apr 29 15:25:11 bliss cp: error processing extended attributes: Operation not permitted
Apr 29 23:09:33 bliss kernel[0]: System Sleep
Apr 29 23:09:33 bliss configd[35]: AppleTalk shutdown
Apr 29 23:09:33 bliss kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Apr 29 23:09:33 bliss kernel[0]: Started CPU 01
Apr 29 23:09:33 bliss kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep Apr 29 23:09:33 bliss kernel[0]: System Wake
Apr 29 23:09:33 bliss kernel[0]: USB caused wake event (EHCI) Apr 29 23:09:33 bliss kernel[0]: IOBluetoothHCIController::terminateWL .. done
Apr 29 23:09:34 bliss kernel[0]: AppleYukon - en0 link active, 100-Mbit, full duplex, symmetric flow control enabled
Apr 29 23:09:40 bliss configd[35]: AppleTalk shutdown complete Apr 29 23:09:40 bliss configd[35]: AppleTalk startup
Apr 29 23:09:40 bliss kernel[0]: CSRHIDTransitionDriver::probe: Apr 29 23:09:40 bliss kernel[0]: CSRHIDTransitionDriver::start before command
Apr 29 23:09:41 bliss kernel[0]: CSRHIDTransitionDriver::stop Apr 29 23:09:42 bliss kernel[0]: IOBluetoothHCIController::start Idle Timer Stopped
Apr 29 23:09:42 bliss kernel[0]: Registering For 802.11 Events Apr 29 23:09:42 bliss kernel[0]: [HCIController][setupHardware] AFH Is Supported
Apr 29 23:09:46 bliss configd[35]: AppleTalk startup complete Apr 30 09:24:19 bliss kernel[0]: System SleepSee the line that begins:IOBluetoothHCIController::restartShutdownWL this is a wake from sleep.
What's that about? I'm beginning to suspect some randome cellphone walk-by as the culprit.
I don't have bluetooth, but my Mac has occasionally waked when I came in the door. Moving the mouse will wake it, and my theory was that sometimes the vibration of walking could cause the optical mouse to signal movement.
The other day I discovered more about it. The cursor kept freezing. The light in my cordless USB mouse would stay bright or stay off or flicker until I reinstalled the batteries. Then the cursor would work.
With a magnifier I saw tiny bits if debris on the eye in the mouse. I stuck the corner of a handkerchief in there and turned it. That cured the problem.
So an optical mouse can respond to dirt even when you aren't touching it. Maybe debris or a hair or a tiny bug caused your mouse to wake your Mac.
Someone had suggested that once before. Could be, but it seems odd that the vibrations would be felt on the desktop, especially since I'm not in the habit of slamming doors when I come in. The mouse looks clean.
When I experienced lockups, I took my mouse apart to clean the internal stuff. I looked at the eye under a light with reading glasses. It looked clean. I blew it out.
The problem persisted. With a lighted 10x magnifier, I saw a couple of specks on the eye. Apparently sticking the corner of a handkerchief in there removed them because the problem disappeared.
Denominator schreef:
RobertB wrote:
Previously, Denominator wrote:
RobertB wrote:
I don't think it's dust. My core2duo was sleeping when I left in the afternoon. I came home around 10:30 at night. Around 11:30, 11:45 I noticed that the machine was on, although I hadn't gone near it. I checked the logs and found the following. FYI, BlueTooth and AirPort are turned off on this machine (10.4.9).
Apr 29 15:25:11 bliss cp: error processing extended attributes: Operation not permitted
Apr 29 23:09:33 bliss kernel[0]: System Sleep
Apr 29 23:09:33 bliss configd[35]: AppleTalk shutdown
Apr 29 23:09:33 bliss kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Apr 29 23:09:33 bliss kernel[0]: Started CPU 01
Apr 29 23:09:33 bliss kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep Apr 29 23:09:33 bliss kernel[0]: System Wake
Apr 29 23:09:33 bliss kernel[0]: USB caused wake event (EHCI) Apr 29 23:09:33 bliss kernel[0]: IOBluetoothHCIController::terminateWL .. done
Apr 29 23:09:34 bliss kernel[0]: AppleYukon - en0 link active, 100-Mbit, full duplex, symmetric flow control enabled
Apr 29 23:09:40 bliss configd[35]: AppleTalk shutdown complete Apr 29 23:09:40 bliss configd[35]: AppleTalk startup
Apr 29 23:09:40 bliss kernel[0]: CSRHIDTransitionDriver::probe: Apr 29 23:09:40 bliss kernel[0]: CSRHIDTransitionDriver::start before command
Apr 29 23:09:41 bliss kernel[0]: CSRHIDTransitionDriver::stop Apr 29 23:09:42 bliss kernel[0]: IOBluetoothHCIController::start Idle Timer Stopped
Apr 29 23:09:42 bliss kernel[0]: Registering For 802.11 Events Apr 29 23:09:42 bliss kernel[0]: [HCIController][setupHardware] AFH Is Supported
Apr 29 23:09:46 bliss configd[35]: AppleTalk startup complete Apr 30 09:24:19 bliss kernel[0]: System SleepSee the line that begins:IOBluetoothHCIController::restartShutdownWL this is a wake from sleep.
What's that about? I'm beginning to suspect some randome cellphone walk-by as the culprit.I don't have bluetooth, but my Mac has occasionally waked when I came in the door. Moving the mouse will wake it, and my theory was that sometimes the vibration of walking could cause the optical mouse to signal movement.
The other day I discovered more about it. The cursor kept freezing. The light in my cordless USB mouse would stay bright or stay off or flicker until I reinstalled the batteries. Then the cursor would work.
With a magnifier I saw tiny bits if debris on the eye in the mouse. I stuck the corner of a handkerchief in there and turned it. That cured the problem.
So an optical mouse can respond to dirt even when you aren't touching it. Maybe debris or a hair or a tiny bug caused your mouse to wake your Mac.
Someone had suggested that once before. Could be, but it seems odd that the vibrations would be felt on the desktop, especially since I'm not in the habit of slamming doors when I come in. The mouse looks clean.
When I experienced lockups, I took my mouse apart to clean the internal stuff. I looked at the eye under a light with reading glasses. It looked clean. I blew it out.
The problem persisted. With a lighted 10x magnifier, I saw a couple of specks on the eye. Apparently sticking the corner of a handkerchief in there removed them because the problem disappeared.
Try: http://www.mouserug.com/ Works fine with both a "ball" and laser mouse. Your ball will stay clean. Cheers, Stephan.
Previously, Jolly Roger wrote:
On 2007-05-03 09:02:26 -0500, RobertB said:
You have to pair Bluetooth devices with Macs in order to connect and do things. And pairing requires user interaction on both ends to authenticate the operation. I suppose it could be that someone is *attempting* to pair up to your computer or something like that. Have you looked around in your Bluetooth settings in System Preferences to make sure things are set in a secure manner?
Well, how secure do they need to be if Bluetooth is turned off?
Not at all, since the radio receiver is powered off in that state. If this is the case on your Mac when it has these wake-from-sleep issues, then the problem must be coming from elsewhere.
I checked today's log (see below):
May 3 14:58:58 bliss cp: error processing extended attributes: Operation not permitted
May 4 09:59:40 bliss kernel[0]: System Sleep
May 4 09:59:40 bliss kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
May 4 09:59:40 bliss kernel[0]: Started CPU 01
May 4 09:59:40 bliss kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep May 4 09:59:40 bliss kernel[0]: System Wake
May 4 09:59:41 bliss kernel[0]: AppleYukon - en0 link active, 100-Mbit, full duplex, symmetric flow control enabled
May 4 09:59:47 bliss configd[35]: AppleTalk shutdown
May 4 09:59:47 bliss configd[35]: AppleTalk shutdown complete May 4 09:59:47 bliss configd[35]: AppleTalk startup
May 4 09:59:53 bliss configd[35]: AppleTalk startup complete
Apparently, that BluetoothController line is a standard part of the wake-up process. And I recall seeing it in the past, just never paid too much attention to it. So it's presence may not be an anomaly.
On 2007-05-04 09:24:03 -0500, RobertB said:
I checked today's log (see below):
May 4 09:59:40 bliss kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep May 4 09:59:40 bliss kernel[0]: System Wake
Apparently, that BluetoothController line is a standard part of the wake-up process. And I recall seeing it in the past, just never paid too much attention to it. So it's presence may not be an anomaly.
Yes, I'm thinking it's something else on your USB bus. You might try disconnecting one USB device a night to see if you can figure our which one is the culprit.
(If you send an email to this address, please notify me ahead of time so I can watch for it among the sea of SPAM that gets filtered out daily.)
JR
Previously, Jolly Roger wrote:
On 2007-05-04 09:24:03 -0500, RobertB said:
I checked today's log (see below):
May 4 09:59:40 bliss kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep May 4 09:59:40 bliss kernel[0]: System Wake
Apparently, that BluetoothController line is a standard part of the wake-up process. And I recall seeing it in the past, just never paid too much attention to it. So it's presence may not be an anomaly.
Yes, I'm thinking it's something else on your USB bus. You might try disconnecting one USB device a night to see if you can figure our which one is the culprit.
Well, that would be the keyboard or mouse, since the keyboard is the only think plugged into the USB bus and the mouse is plugged into the keyboard.
On 2007-05-05 12:18:48 -0500, RobertB said:
Previously, Jolly Roger wrote:
On 2007-05-04 09:24:03 -0500, RobertB said:
I checked today's log (see below):
May 4 09:59:40 bliss kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep May 4 09:59:40 bliss kernel[0]: System Wake
Apparently, that BluetoothController line is a standard part of the wake-up process. And I recall seeing it in the past, just never paid too much attention to it. So it's presence may not be an anomaly.
Yes, I'm thinking it's something else on your USB bus. You might try disconnecting one USB device a night to see if you can figure our which one is the culprit.
Well, that would be the keyboard or mouse, since the keyboard is the only think plugged into the USB bus and the mouse is plugged into the keyboard.
Which brings us back to the dust hypothesis. ; )
(If you send an email to this address, please notify me ahead of time so I can watch for it among the sea of SPAM that gets filtered out daily.)
JR
Previously, Jolly Roger wrote:
On 2007-05-05 12:18:48 -0500, RobertB said:
Previously, Jolly Roger wrote:
On 2007-05-04 09:24:03 -0500, RobertB said:
I checked today's log (see below):
May 4 09:59:40 bliss kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep May 4 09:59:40 bliss kernel[0]: System Wake
Apparently, that BluetoothController line is a standard part of the wake-up process. And I recall seeing it in the past, just never paid too much attention to it. So it's presence may not be an anomaly.
Yes, I'm thinking it's something else on your USB bus. You might try disconnecting one USB device a night to see if you can figure our which one is the culprit.
Well, that would be the keyboard or mouse, since the keyboard is the only think plugged into the USB bus and the mouse is plugged into the keyboard.
Which brings us back to the dust hypothesis. ; )
I was afraid of that. The idea of eliminating dust from my office is, well, rather daunting.
On 2007-05-07 17:59:15 -0500, RobertB said:
Previously, Jolly Roger wrote:
Which brings us back to the dust hypothesis. ; )
I was afraid of that. The idea of eliminating dust from my office is, well, rather daunting.
You really only need to eliminate it from the optics area of the mouse. Got a can of compressed air handy?
Also, what type of mouse pad do you use?
What type of mouse is this, for that matter?
Do you happen to have any small animals that might jump on the desk and press the space bar every so often?
JR
Previously, Jolly Roger wrote:
On 2007-05-07 17:59:15 -0500, RobertB said:
Previously, Jolly Roger wrote:
Which brings us back to the dust hypothesis. ; )
I was afraid of that. The idea of eliminating dust from my office is, well, rather daunting.
You really only need to eliminate it from the optics area of the mouse. Got a can of compressed air handy?
Yes.
Also, what type of mouse pad do you use?
Mouse pad? The old pad from my very old Micron PC. I didn't use a mouse pad for a while with this mouse but it doesn't get much purchase on the slipper formica desktop surface.
Apple Optical mouse that came with the core2duo. The new mouse with the little scroll button on top.
Do you happen to have any small animals that might jump on the desk and press the space bar every so often?
Not that I know of. But then again, you never know what goes on at night.
User-Agent: Unison/1.7.9
On 2007-05-09 09:16:43 -0500, RobertB said:
Previously, Jolly Roger wrote:
On 2007-05-07 17:59:15 -0500, RobertB said:
Previously, Jolly Roger wrote:
Which brings us back to the dust hypothesis. ; )
I was afraid of that. The idea of eliminating dust from my office is, well, rather daunting.
You really only need to eliminate it from the optics area of the mouse. Got a can of compressed air handy?
Yes.
Well use it! : )
Also, what type of mouse pad do you use?
Mouse pad? The old pad from my very old Micron PC.
Yes - but what kind is it? Soft an fuzzy? Lint-and-dust attracting? Full of cat hair? Hard plastic? Etc.
I didn't use a mouse pad for a while with this mouse but it doesn't get much purchase on the
slipper formica desktop surface.
Yeah, my desk surface is frosted glass, so I *have* to use a pad, unfortunately.
Apple Optical mouse that came with the core2duo. The new mouse with the little scroll button on top.
That's the MightyMouse.
Do you happen to have any small animals that might jump on the desk and press the space bar every so often?
Not that I know of. But then again, you never know what goes on at night.
I take it you do have small animals roaming the house? If so, I can imagine one of them stepping on the space bar or clicking the mouse, causing your computer to wake up.
JR
Previously, Jolly Roger wrote:
User-Agent: Unison/1.7.9
On 2007-05-09 09:16:43 -0500, RobertB said:
Previously, Jolly Roger wrote:
On 2007-05-07 17:59:15 -0500, RobertB said:
Previously, Jolly Roger wrote:
Which brings us back to the dust hypothesis. ; )
I was afraid of that. The idea of eliminating dust from my office is, well, rather daunting.
You really only need to eliminate it from the optics area of the mouse. Got a can of compressed air handy?
Yes.
Well use it! : )
Assuming I can find it. Also, I don't like the fact that the air is ice cold. I'm not sure that's good for delicate components.
Also, what type of mouse pad do you use?
Mouse pad? The old pad from my very old Micron PC.
Yes - but what kind is it? Soft an fuzzy? Lint-and-dust attracting? Full of cat hair? Hard plastic? Etc.
Semi-hard. Not hard plastic. Not soft and fuzzy either. No cat hair. No cat, ergo, no cat hair.
I didn't use a mouse pad for a while with this mouse but it doesn't get much purchase on the
slipper formica desktop surface.Yeah, my desk surface is frosted glass, so I *have* to use a pad, unfortunately.
Apple Optical mouse that came with the core2duo. The new mouse with the little scroll button on top.
That's the MightyMouse.
One of these days I'll figure out what the two button things on the side do. <g>
Do you happen to have any small animals that might jump on the desk and press the space bar every so often?
Not that I know of. But then again, you never know what goes on at night.
I take it you do have small animals roaming the house? If so, I can imagine one of them stepping on the space bar or clicking the mouse, causing your computer to wake up.
No. I do not have any small animals. Like no cats or dogs. Never saw a mouse here either. But the universe might change while I'm asleep.
User-Agent: Unison/1.7.9
On 2007-05-10 12:05:36 -0500, RobertB said:
Got a can of compressed air handy?
Yes.
Well use it! : )
Assuming I can find it. Also, I don't like the fact that the air is ice cold. I'm not sure that's good for delicate components.
Spray it from a distance of about 4-5 inches, and do not tilt the can while spraying, and it should be just fine.
JR
User-Agent: Unison/1.7.9
On 2007-05-10 12:05:36 -0500, RobertB said:
That's the MightyMouse.
One of these days I'll figure out what the two button things on the side do. <g>
Whatever you've programmed them to do in System Preferences > Keyboard & Mouse > Mouse, of course. : D
JR
User-Agent: Unison/1.7.9
On 2007-05-10 12:05:36 -0500, RobertB said:
Do you happen to have any small animals that might jump on the desk and press the space bar every so often?
Not that I know of. But then again, you never know what goes on at night.
I take it you do have small animals roaming the house? If so, I can imagine one of them stepping on the space bar or clicking the mouse, causing your computer to wake up.
No. I do not have any small animals. Like no cats or dogs. Never saw a mouse here either. But the universe might change while I'm asleep.
LOL. One never knows!
JR
Previously, Jolly Roger wrote:
User-Agent: Unison/1.7.9
On 2007-05-10 12:05:36 -0500, RobertB said:
Got a can of compressed air handy?
Yes.
Well use it! : )
Assuming I can find it. Also, I don't like the fact that the air is ice cold. I'm not sure that's good for delicate components.
Spray it from a distance of about 4-5 inches, and do not tilt the can while spraying, and it should be just fine.
Don't they sometimes leave a water (or liquid) residue?
Previously, Jolly Roger wrote:
User-Agent: Unison/1.7.9
On 2007-05-10 12:05:36 -0500, RobertB said:
That's the MightyMouse.
One of these days I'll figure out what the two button things on the side do. <g>
Whatever you've programmed them to do in System Preferences > Keyboard & Mouse > Mouse, of course. : D
You mean it requires user intervention!
On 2007-05-11 09:09:07 -0500, RobertB said:
Previously, Jolly Roger wrote:
User-Agent: Unison/1.7.9
On 2007-05-10 12:05:36 -0500, RobertB said:
Got a can of compressed air handy?
Yes.
Well use it! : )
Assuming I can find it. Also, I don't like the fact that the air is ice cold. I'm not sure that's good for delicate components.
Spray it from a distance of about 4-5 inches, and do not tilt the can while spraying, and it should be just fine.
Don't they sometimes leave a water (or liquid) residue?
Not if you don't tilt the can while spraying and keep a 4- to 5-inch distance. Besides, manufacturers recommend that you clean peripherals with a damp cloth with water on it. A small amount of water would just evaporate and wouldn't harm the thing anyway.
JR
On 2007-05-11 09:09:26 -0500, RobertB said:
Previously, Jolly Roger wrote:
User-Agent: Unison/1.7.9
On 2007-05-10 12:05:36 -0500, RobertB said:
That's the MightyMouse.
One of these days I'll figure out what the two button things on the side do. <g>
Whatever you've programmed them to do in System Preferences > Keyboard & Mouse > Mouse, of course. : D
You mean it requires user intervention!
Well the default settings apply automatically. I forget whether the side buttons bring up Dashboard or Expose by default - one of the two.
JR