The conversation on this page has been archived and is no longer active.

Sandisk Imagemate 8-in-1 prevents complete sleep, why?

Message #1 - Posted 2004/12/26 - Greg White

I have a very old Sandisk USB 1.1 imagemate CF reader and a new Sandisk USB 2.0 Imagemate SDDR-88 8-in-1 card reader. If the old card reader is connected through -either- USB1.1 or added USB 2.0 ports (see below for the system configuration) then the machine will sleep properly and it can be awakened via the keyboard. If the new 8-in-1 card reader is connected through either of the USB connections, when commanded to sleep the machine will shut off its video but the fans stay on and the disks continue to run. The machine can't be brought back from sleep, either, it has to be re-booted.

Apart from that the card reader works fine. "Apart from that, Mrs. Lincoln, how did you like the play?"

-Why does the new card reader prevent the machine from sleeping properly? -Can you recommend a USB 2.0 card reader (SD, CF) that does not cause this problem?

The machine is a MDD 2x1.25 G4 (3.3) with added Atto ExpressPCI UL3D SCSI and D-Link DU-520 USB2.0 cards. OS 10.3.7. 1 GB RAM. All the USB stuff has coexisted peacefully with SCSI until this issue developed.

Thanks -

Greg

from the net TLD, sonic domain, user gw+2.
there is a character in the user name that should be removed.

Message #2 - Posted 2004/12/26 - John Albert

RE the posting:
<< Why does the new card reader prevent the machine from sleeping properly? -Can you recommend a USB 2.0 card reader (SD, CF) that does not cause this problem?
The machine is a MDD 2x1.25 G4 (3.3) with added Atto ExpressPCI UL3D SCSI and D-Link DU-520 USB2.0 cards. OS 10.3.7. 1 GB RAM. All the USB stuff has coexisted peacefully with SCSI until this issue developed. >>

I'm not sure there really _is_ a solution for you there.

I have a g4 1.25 DP MDD, with a USB2/PCI card and a USB2/Firewire combo hub, and it behaves in much the same way.

On mine, I have my keyboard connected through the USB/2 card/hub. The mouse is connected directly to the USB1.1 port on the back of the Mac.

For both of the following situations, I have the keyboard as the ONLY device connected through the USB2 card/hub:

Situation 1. If I leave the machine alone, it will go into "light sleep" on its own, and awaken from side-to-side movement of the mouse, or by clicking a mouse button. By "light sleep" I mean the monitor shuts off and the internal drives spin down, but the power supply remains active (the power supply fan still runs).

Situation 2. If I choose "Sleep" from the Finder, the computer _does_ go down into full "deep sleep". However, the ONLY way to wake it is by clicking the mouse button. Sideways movement of the mouse seems to have no effect, nor does touching the keyboard (which, again, is connected through the USB2/PCI card).

HOWEVER, adding a USB card reader (a USB1.1 Smartmedia card reader, no-name, in my case) changes things for the worse. I tried connecting the card reader both directly to the USB2/PCI card port, and "through the USB2 hub", and in both instances, the computer goes into light sleep, but CANNOT be awakened without a hard restart.

I'm guessing that there is _something_ about USB2 [when obtained through a PCI card, i.e., the USB2 controller is non-native to the Mac] that conflicts _somewhere_ with the pre-conditions that the Mac OS software (or hardware) requires for "full sleep". Not sure exactly what, but perhaps others with more knowledge will jump in and clarify. What seems noteworthy is that - when in deep sleep - my keyboard in the above example becomes unresponsive. I will guess that in deep sleep, the Mac is "putting the USB2/PCI card to sleep" as well, and it no longer can accept or respond to input from the keyboard.

Throw a "mounted storage device" into the mix, however, such as a card reader or drive, and things probably get more complicated. Apparently, immediately before sleep, the Mac is trying to communicate or pre-condition the mounted devices in _some_ way that throws the entire sleep process into disarray. The only way out becomes a hard reboot.

The only solution, really, is to completely dismount and disconnect the USB device that is giving you the problem _before_ attempting to put the Mac to sleep. I don't see any other way, unless _some_ Mac-oriented vendor out there has tweaked a USB2/PCI card to work properly without conflicts.

I believe more info can be found on this subject at xlr8yourmac.com.

- John

Message #3 - Posted 2004/12/26 - Greg White

Previously, John Albert wrote:

[...]

I'm not sure there really _is_ a solution for you there.

[...]

The only solution, really, is to completely dismount and disconnect the USB device that is giving you the problem _before_ attempting to put the Mac to sleep. I don't see any other way, unless _some_ Mac-oriented vendor out there has tweaked a USB2/PCI card to work properly without conflicts.

I believe more info can be found on this subject at xlr8yourmac.com.

Yup, there certainly is more there, and it all fits with what you say. That is a misfortune, and it seems there's little incentive for anyone to remedy it; I'm certainly not competent to do it.

Thanks for your informative post.

-Greg

from the net TLD, sonic domain, user gw+2.
there is a character in the user name that should be removed.

Need Help? Have a Question?

Looking for more help, comments, and answers?

Ask your questions on Ask Different. Ask Different is a community of Apple users ready to help.