How to start automatically with a programmed recording?[SOLVED]

Hi. I have a Shuttle XS35GT and it is working well with yavdr, but I have to keep it allways awake in order to do recordings, because it does not start automatically from S3 (suspend to ram) state.

I have been finding out how to solve it but I have not found anything to solve the problem. Can someone give me a clue to fix it?

Thanks.

Should I give more information?

Thanks.

Hi.

I tried ACPI-Wakeup but it do not worked.
S3 state works well because I can start yavdr from this state by mean my remote control. I have fear to use nvram-wakeup because I have read that can cause problem in the bios. Is that true?

Zitat

Originally posted by utiltiy
Did you enable ACPI-Wakeup in the Config-File? Default is it disabled!

The Path wrote cekaro.

Yes or No?

Yes I did. I tried suspend to ram and suspend to disk with ACPI-Wakeup enabled in config-file, but none of them wake up to do programmed recordings.

From suspend to ram state I am able to wake with de remote but from suspend to disk, the remote does not work to wake up the sistem (I write this information just in case it is usefull, I do not know).

Is there any log file that is usefull to see what happens?

Zitat

Originally posted by Saxman2k

Hi jbjbjb,

if S3 is not stable with your System, you can try to use the normal powerdown (is it S5?) in combination with ACPI-Wakeup. If ACPI-Wakeup does not work on your board, give NVRAM-Wakeup a try.

Saxman2k

Alles anzeigen

I think S3 is stable in the system, because I can shutdown to a S3 state and start again by mean the remote control. What is not functional is the wake up from S3 to do a recording, configuring properly /etc/vdr/vdr-addon-acpiwakeup.conf.

Doing a total shutdown with /etc/vdr/vdr-addon-acpiwakeup.conf configured, do not awake the system either.

The Shuttle XS35GT is a new hardware, could be possible it does not support any kind of programmed awake?

nvram-wakeup could damage the bios? I am not an expert, and for me the information is confusing.

Zitat

Originally posted by szymex
Did you make it work? I have same problem, I use Asus AT3IONT motherboard. I did enable it in configuration /etc/vdr/vdr-addon-acpiwakeup.conf. (I tested and waking up under windows works fine.)

Sorry, no. I am looking for answers yet. If you achieve it, please, let us know.

I have tried another time:

Enabled ACPI-Wakeup in the Config-File and configured from web front-end to do suspend to disk.

Not working, the computer do not wake up by itself, and when I start the computer manually, a disk checking is allways done.

Is there a page where I can read more about nvram-wakeup before trying?

Zitat

Originally posted by Licherkette
I have Zotac ION-F system and observed no ACPI wakeup on S3 too. But I did not look into it yet.
I found an entry in Bios I wanted to check where I can set up ACPI comliance for ACPI Ver 1.0 2.0 or 3.0.
Please check if you have such an entry in your Bios and if it helps working ACPI with other comliance version.

I think that I do not have any option to configure ACPI but I will find out again.

Zitat

Originally posted by Licherkette
I noticed on other systems that ACPI wakeup only works with timers at least 30min in the future. Please also check, if a Timer 1 hour appart works fine or not.

greetings, Uwe

Thanks, I will prepare again the acpi config file, and I will prepare to start more than 1 hour in the futur.
I will be back with de results.

Zitat

Originally posted by jbjbjb
Thanks, I will prepare again the acpi config file, and I will prepare to start more than 1 hour in the futur.
I will be back with de results.

Negative. It should have started by now, and it is down yet.

Zitat

Originally posted by Hulk
Hi,

My mainboard come from ASUS, but for work only adding "hpet=disable" as kernel parameter at boot.

Some other hints : http://www.mythtv.org/wiki/ACPI_Wakeup

Andreas

Alles anzeigen

Thanks for the advice. Another thing to try.

But now, I am a little bit outside. When tried to connect remotely to know if the Shuttle waked-up, it was off. But I just tried again and it is """ON""", it has waked up 36 minutes after the time it was suposed to do a recording. So, what is happening here??? Why 36 minutes later and no other time???

More information. File messages when it was shutting down and in the new starting:

Jan 26 17:10:05 yavdr recordingaction: executing /usr/share/vdr/recording-hooks/R90.custom  as shell script
Jan 26 17:11:16 yavdr vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S50.noad as shell script
Jan 26 17:11:16 yavdr vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.acpiwakeup as shell script
Jan 26 17:11:17 yavdr vdr-addon-acpiwakeup: Setting ACPI alarm time to: 2011-01-26 18:06:16
Jan 26 17:11:17 yavdr vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Jan 26 17:11:17 yavdr vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Jan 26 17:11:17 yavdr vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.custom as shell script
Jan 26 17:11:17 yavdr vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.nvram-wakeup as shell script
Jan 26 17:11:17 yavdr vdr-nvram-wakeup: nvram-wakeup functionality is disabled
Jan 26 17:11:17 yavdr vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.shutdown
Jan 26 17:11:17 yavdr vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S91.lifeguard as shell script
Jan 26 17:11:17 yavdr vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S92.imonlcd
Jan 26 17:11:17 yavdr vdr-sxfe[1971]: [1971] [vdr-fe]    caught signal 15
Jan 26 17:11:18 yavdr vdr-sxfe[1971]: [1971] [input_vdr] Connections closed.
Jan 26 17:11:18 yavdr vdr: [1969] [xine..put] Closing connection 0
Jan 26 17:11:21 yavdr vdr: [1901] [xine..put] cXinelibOsdProvider: shutting down !
Jan 26 17:11:21 yavdr kernel: [10762.499684] lirc_imon: IR port closed
Jan 26 17:11:23 yavdr kernel: [10764.924556] jme 0000:02:00.5: PCI INT A disabled


WAKE-UP


Jan 26 19:06:22 yavdr kernel: [10765.891043] PM: Syncing filesystems ... done.
Jan 26 19:06:22 yavdr kernel: [10765.892807] Freezing user space processes ... (elapsed 0.00 seconds) done.
Jan 26 19:06:22 yavdr kernel: [10765.893309] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Jan 26 19:06:22 yavdr kernel: [10765.893522] Suspending console(s) (use no_console_suspend to debug)
Jan 26 19:06:22 yavdr kernel: [10765.972692] dvb-usb: Pinnacle PCTV 73e successfully deinitialized and disconnected.
Jan 26 19:06:22 yavdr kernel: [10766.020667] dvb-usb: Pinnacle PCTV 73e successfully deinitialized and disconnected.
Jan 26 19:06:22 yavdr kernel: [10766.036058] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jan 26 19:06:22 yavdr kernel: [10766.036674] sd 0:0:0:0: [sda] Stopping disk
Jan 26 19:06:22 yavdr kernel: [10766.649311] PM: suspend of drv:sd dev:0:0:0:0 complete after 613.254 msecs
Jan 26 19:06:22 yavdr kernel: [10766.750145] ============> r8192E suspend call.
Jan 26 19:06:22 yavdr kernel: [10766.750150] RTL819XE:UI is open out of suspend function
Jan 26 19:06:22 yavdr kernel: [10766.750153] r8192E support WOL call??????????????????????
Jan 26 19:06:22 yavdr kernel: [10766.750220] rtl819xSE 0000:03:00.0: PCI INT A disabled
Jan 26 19:06:22 yavdr kernel: [10766.785047] jmb38x_ms 0000:02:00.3: PCI INT B disabled
Jan 26 19:06:22 yavdr kernel: [10766.801108] sdhci-pci 0000:02:00.0: PCI INT B disabled
Jan 26 19:06:22 yavdr kernel: [10767.265057] HDA Intel 0000:01:00.1: PCI INT B disabled
Jan 26 19:06:22 yavdr kernel: [10767.281021] PM: suspend of drv:HDA Intel dev:0000:01:00.1 complete after 464.000 msecs

We can see the line:
Jan 26 17:11:17 yavdr vdr-addon-acpiwakeup: Setting ACPI alarm time to: 2011-01-26 18:06:16

The time of the shutdown is correct (17:11:17), the time for the programmed recording is 18:30:00. Why the startup is programmed at 18:06:16? and why the real startup is at 19:06:16?

Zitat

Originally posted by Licherkette
what about time zone? For me it looks somehow like such thing. Did you change any settings refering to time zone?

I guess not. In the installation of yavdr I choose the time zone of Madrid, Paris, London, but I do not remember doing more changes.
The time is well written in the file messages.