Hi folks,
I've got a SeriTek/1S2 SATA host adapter PCI card installed in my G4 MDD and it is working great. The only thing it doesn't seem to support is Sleep when you set it in the System Preferences/Energy Saver to "put the computer to sleep when it is inactive for... [enter desired time]".
When the time comes up, the computer just keeps running as usual - it doesn't go to sleep.
If I manually put the computer to sleep, then it will sleep (and wake) just fine. It just doesn't respond to the Energy Saver timer setting.
So, I'm just wondering if this is normal behaviour? Are the Energy Saver settings for Sleep in a G4 MDD incompatible with the SeriTek/1S2 card?
I know I don't have the latest firmware update on my card. The latest firmware is "SeriTek/1S2 5.1.3" but the firmware currently on the card is 5.0.9.
I was hesitant to update the firmware, though, unless it would definitely fix the issue as everything else is running fine and this is really only a small issue. Also, I've read some horror stories with firmware updates for some people.
So, if someone with similar experiences could shed some light on this, that would be most appreciated.
Thanks
I've got a SeriTek/1S2 SATA host adapter PCI card installed in my G4 MDD and it is working great. The only thing it doesn't seem to support is Sleep when you set it in the System Preferences/Energy Saver to "put the computer to sleep when it is inactive for... [enter desired time]".
When the time comes up, the computer just keeps running as usual - it doesn't go to sleep.
If I manually put the computer to sleep, then it will sleep (and wake) just fine. It just doesn't respond to the Energy Saver timer setting.
So, I'm just wondering if this is normal behaviour? Are the Energy Saver settings for Sleep in a G4 MDD incompatible with the SeriTek/1S2 card?
I know I don't have the latest firmware update on my card. The latest firmware is "SeriTek/1S2 5.1.3" but the firmware currently on the card is 5.0.9.
I was hesitant to update the firmware, though, unless it would definitely fix the issue as everything else is running fine and this is really only a small issue. Also, I've read some horror stories with firmware updates for some people.
So, if someone with similar experiences could shed some light on this, that would be most appreciated.
Thanks