how do i wake from standby

[rhendrix9]

I've set the Bios on my shuttle to start the pc at a certin time everyday,
then using the scheduler in XP it goes into standby a little later. At he end of the day I have scheduled the pc to shutdown. I am missing the part in the middle to wake up the pc for recording.

I have seen alot of questions and some replies/promises from snapstream, but i can't seem to find the solution.

I seem to be so close to getting my shuttle to wake but i can't find the secret.
Evidently mythtv and gbpvr can do it., anyone know how to make beyondtv wake up and run?
Thanks

[merrypig]

AFAIK, BTV already should be waking your system. It's never been an 'option' - it's just done it by design. (it sets a wake up event before each recording so should bring a machine out of standby if the bios is set to permit it)

[Fonceur]

Originally Posted by rhendrix9

I've set the Bios on my shuttle to start the pc at a certin time everyday,
then using the scheduler in XP it goes into standby a little later. At he end of the day I have scheduled the pc to shutdown. I am missing the part in the middle to wake up the pc for recording.

Just use the S3 standby all the time... Not much point doing a shutdown + forced wakeup (unless you have a specific reason to do that). BTV will get the PC out of standby (and back to it) by itself.

[JeffD]

I can never get Link to work when resuming from standby.

[gsinpei]

In power options I have system standby set for 1 minute. Whenever I shut down the BTV GUI if nothing is recording the system will go into standby.
The system will start up on its own to record and then go back to standby mode.
I use a wireless mouse to bring the system out of standby in order to start up the GUI again with a button press on my ATI remote wonder which is set to run BTV.

[rhendrix9]

Ok I've set the bios to S3 and set standby to occur, testing it now...... BTV cranked up from standby and started recording, I believe my problem was trying to use the RTC timed start in the bios. I found a blurb on annoyances.org that says that do that screws up APM.

The reason I shut it down was to turn off the fans so it be real quiet. I still need to check if S3 will turn off the fans.

Anybody know what the difference is in S1 and S3?

BTW the monitor did not turn back on for recording.. is that a problem?

[merrypig]

S0
The system is turned on. The CPU is executing or ready to execute instructions, PCI activity is full, AGP activity is full. RAM is being read from, written to or refreshed. Hard disks are on.

S1 "Power On Suspend/Stopgrant" MS: Standby
The system is turned on. The CPU is not executing and is not ready to execute instructions, although registers and caches are maintained. Devices signalling support for S1 are in the on state, devices without support for S1 are in the off state. RAM is idle, but refreshed. Any device currently in S1 with support for resuming may resume the system (WOL, WOR, keyboard, mouse, timer, etc.). PSU state is on. Hard disks are off in this state and all states deeper.

S2 "Standby"
Confusing "common" names. S2 is quite logically an intermediate between S1 and S3. RAM refreshes normally. The CPU is in state much like S3. In fact, this is pretty much S3 but with a faster RAM refresh.
S2 is in the spec, but not usually implemented.

S3 "Suspend to RAM" MS: Standby (if notified by BIOS)
S3 often needs enabling by jumper on the motherboard or by support in BIOS. The CPU is not executing instructions, is not ready to execute instructions, does not maintain its registers and does not maintain cache. The OS must flush dirty pages from the cache when S3 is entered. Devices able to support S3 and are enabled for resuming, may resume the system. PSU state is off, system RAM is refreshed (at reduced refresh) using 5Vsb. External peripherals (keyboard, mouse) may or may not be able to resume the system, depending on what their host controller does.


[edit: In other words; fans are off! ]

S4 "Suspend to disk" MS: Hibernate
All hardware is in the off state and maintains no context. The system may only be resumed by timer or other hardware resume devices (such as WOL or WOR), but not by interrupts. The contents of RAM are saved to disk and replaced on resume. The PSU is in the off state. Power may be mechanically removed without ill effect.
Note: S4BIOS is a variation of S4 wherein the BIOS reloads the image and not the OS boot loader. As NTLDR is S4 compatible, this is generally used with other OS'. Linux S4BIOS support is "experimental". Note also that using Windows2000 or XP with grub or lilo WILL break S4 support.

S5 "Soft-Off" MS: Hibernate
All hardware is in the off state and maintains no context. CMOS is maintained by 5Vsb, as in S4. The PSU is in off state. Power may be mechanically removed without ill effect.

S6
As S5, but the PSU is isolated. CMOS is maintained by battery. This is not an "official" ACPI state, but is included in many motherboard manuals for some strange reason. This is the best I can dig up about it.

[Fonceur]

Originally Posted by rhendrix9

The reason I shut it down was to turn off the fans so it be real quiet. I still need to check if S3 will turn off the fans.

Anybody know what the difference is in S1 and S3?

The main difference is that S3 does switch off the fans and such, while S1 does not.

BTW the monitor did not turn back on for recording.. is that a problem?

You can always move your mouse or such if you want the monitor on (and the normal timer before standby to start), but otherwise BTV does not need to wake up the monitor to perform its recording...

[rhendrix9]

Thanks,
I learn something everyday!

[rhendrix9]

Originally Posted by gsinpei

In power options I have system standby set for 1 minute. Whenever I shut down the BTV GUI if nothing is recording the system will go into standby.
The system will start up on its own to record and then go back to standby mode.

This seems to work for me, but the remote record feature doesn't. Am I missing something or is tht your experience too?

[Kilrsat]

Remote recordings can't happen while the system is in standby.

[ZetaVu]

Ok, my new mobo was suspending to ram fine until I switched PS, installed my capture cards, btv, etc. My bios only has suspend to ram with disabled or auto as option. WHen I go into standby now, it seems to start, but fans never stop running, and the system wakes up half a minute later. I also use an lcdsmartie parallel connection, but I've already tried disabling this. Any advice?

[ZetaVu]

Ok, update on my issues. I tried booting to another hard drive with a previous ghost of the OS (pre btv and a bunch of other programs) I also unplugged my two capture cards and lcd smartie. Computer suspended to ram fine, HOWEVER, when I resumed, the computer rebooted. Did not have this problem before. I plugged my lcd (smartie) back in, and both cards, no difference. I disconnected everything by one hard drive, replaced my old PS, went to my original ghost of just xp install, same thing, suspends to ram fine, all fans off, but resume and xp reboots.

So, I cannot find anything in BIOS that is different, I went to almost the exact same system as when I suspended to ram and resumed fine before (only difference is tv out pluged in on my fx5200, and using logitech wireless keyboard and mouse. Also had my serial tuner plugged in to com) and the reboot on resume issue.

So, here is what I think is possible

1. still something in bios askew and I haven't found it
2. ghosted image on HD at issue, need to try a reinstall from scratch
3. logitech mouse/keyboard screwing with me (or serial tuner plug) (maybe they draw too much current or ram loses current?)
4. something messed up on my MB, meaning I got a couple weeks to sort out so I can RMA if needed. (of course could be ram as well, but I tried 2 PS's)

I went back to my regular config, suspend to ram does not work, just goes into standby and fans still run, but on resume it does not reboot. I figure this is a software issue as my only BIOS option is auto for suspend to ram (so the OS has to allow it) This should get sorted out with a reinstall.

I hope it's not a ghost issue, (installing the os from a ghost image) as this is how I back up all os'

Any ideas or advice will be greatly appreciated.

[ZetaVu]

Ok, loaded the same basic ghost image discussed above on another hard drive (I like to have two bootable os' on my system in case one crashes)

Left all cards in, unplugged usb (ati remote wonder), it booted to xp, loaded drivers it had, did not have drivers for my two capture boards, told it to ignore. Went to suspend to RAM, resumed IT WORKED!

Plugged in the ATI Remote wonder, restarted windows, STR and resume still works!!!

Ok, so problem was not using a ghosted OS install, so I don't have to install XP from scratch. It was not (apparently) the usb from ATI, it was not my logitech wireless keyboard, and doesn't look like mobo PS, or memory are an issue. Did not change anything in BIOS, but I did swap back to my ati AIW 7500 (from fx5200, however that did work initially)

Now, when I tested with fx5200, that was just connected through analog to an ldc flatpanel. In my system, it goes to a crt and through s-video to my tv. ATI is same way, but it could be a driver issue or how the nvidia recognizes tv's etc. Moot point, I'm sticking with ATI from here on.

Also, could be the HD I was testing with in my above post, an old Maxtor, although that is the one I originally tested on. Of course original tests were not on a ghost image, and maybe something got messed up in the ghost restore to that disk.

Either way, my clean xp (from ghost) install works correctly on STR and resume, now to start the long and tedious task of loading capture drivers, ATI remote drivers, BTV, etc etc, and test each to see if one breaks STR. Much ghosting will occur for every step.

[ZetaVu]

Ok, update since I am thoroughly pleased with myself (almost) got my str and my new build to work. (although still having Hauppauge short length recordings, not sure if str affects that yet)

So, installed Hauppauge and A180 drivers, btv, autogk, lcdsmartie (had to upgrade to 5.3.2 because the older lcdsmartie would lock up with my new MB, it was a known problem) MBM, MP, and I now have a fully working install. System suspends to ram, and wakes without rebooting. I set it on a 30 minute timer to str, works fine, mouse click or keyboard wake it up.

I also wanted to be able to access my shared folders which meant waking on lan, this took some time to figure out, but what you have to do is go to hardware settings for the LAN (Device manager, network adaptors, choose adaptor, properties, and power management) and check both "Allow the device to bring computer out of standby" as well as "only allow management stations to bring the computer out of standby". This lets me wake from another computer on my network, but if you don't set the second one it wakes with any network traffic. This requires a magic packet, so I downloaded the depicus program (there's a list over here so I'm gonna try them all out http://en.wikipedia.org/wiki/Wake-on-LAN#Magic_Packet ) and that works like a charm.

Now, apart from fixing the Hauppauge issue, the only other thing I'd like to do is get my ATI remotewonder to be able to wake from str. This is a usb connection, and I think I may need to change a jumper on my MB to get this active (not sure if it needs a separate power source or not) Alternatively, I could always sqap to another remote if that's what's needed, but for now that and my hauppauge pvr250 remote are what I have. Any suggestions would be appreciated.