Author |
Message |
sithlord39
|
Posted: Fri Aug 18, 2006 10:16 pm |
|
Joined: Fri Feb 03, 2006 12:22 pm
Posts: 56
|
Hi guys,
I am trying to get mythwelcome to work on my mythbox. I finally got nvram-wakeup working! I am following the directions over at http://www.knoppmythwiki.org/index.php?page=WakeupToRecordWithMythWelcome
I am working on step 4. I tried giving the command
Code: sudo mythshutdown --setwakeup $((`date +%s` + 900)) but I then get the following Code: QTime::fromString: Parameter out of range QDate::setYMD: Invalid date 1155-61-63
This leads me to think that the script is not getting the actual variable it needs, but it getting the actually string "date" etc. Anyone have any luck with this bad boy?
_________________ PVR-150 MCE
Radeon-9000 Pro
Seagate Barracuda 120-GB
AOpen AX34-U Motherboard
R5C7 KnoppMyth
|
|
Top |
|
 |
sithlord39
|
Posted: Sat Aug 19, 2006 9:10 am |
|
Joined: Fri Feb 03, 2006 12:22 pm
Posts: 56
|
update:
It may have been somewhat as I expected. I tried the following as user mythtv:
Code: mythshutdown --setwakeup 2006-8-19T10:41 and it took it just fine. I then gave the following command: Code: sudo mythshutdown --shutdown and the machine shutdown correctly. However, upon checking the RTC wakeup timer, nothing has been set. So something is happening along the way which is preventing nvram-wakeup from being called. Any ideas guys? Additionally, when I tried the commands Code: mythshutdown --status and Code: mythshutdown --check did not yield anything.
I also follow the wiki over at http://www.mythtv.org/wiki/index.php/Mythwelcome
_________________ PVR-150 MCE
Radeon-9000 Pro
Seagate Barracuda 120-GB
AOpen AX34-U Motherboard
R5C7 KnoppMyth
|
|
Top |
|
 |
sithlord39
|
Posted: Mon Aug 21, 2006 10:15 pm |
|
Joined: Fri Feb 03, 2006 12:22 pm
Posts: 56
|
Alright gang I got it working. I am going to update the wiki to make it easier for others.
_________________ PVR-150 MCE
Radeon-9000 Pro
Seagate Barracuda 120-GB
AOpen AX34-U Motherboard
R5C7 KnoppMyth
|
|
Top |
|
 |
tophee
|
Posted: Tue Aug 22, 2006 12:40 am |
|
Joined: Tue Sep 13, 2005 10:48 am
Posts: 852
Location:
London, UK
|
Nice one. I've been keeping an eye on your documented progress, as I too am investigating the mysteries of wakeup to record.
Glad you got it sorted. Hope I do too.
Regards Chris
Oh, one thing I would ask: If the backend is detecting frontends not conneced to trip the shutdown routine, how does that work with a single frontend/backend machine?
As far as I know, the frontend of this single machine is always on, well when the backend is at least.
Ta
_________________ Version:R8 Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)
|
|
Top |
|
 |
sithlord39
|
Posted: Tue Aug 22, 2006 7:15 am |
|
Joined: Fri Feb 03, 2006 12:22 pm
Posts: 56
|
Good question. Here's how mythwelcome handles that:
When the machine starts up, mythwelcome starts up. Mythwelcome then determines if was
1) woken up (by nvram-wakeup) to record something or
2) woken up by someone manually turning it on
If it is the first case, the front end does not launch. Therefore, when the recording/commercial flagging is complete it shuts down
If it is the second case, mythwelcome launches the frontend so you can watch your recordings
That is what you are changing in step 6 of the wiki by changing "knoppmyth-run" to "mythwelcome". Also, if the the machine wakes to record and there is no frontend, there is a button to launch one.
Hope that helps. If you have any other questions, just post them. After putting alot of work into it, I am glad to be able to help others
Cheers
_________________ PVR-150 MCE
Radeon-9000 Pro
Seagate Barracuda 120-GB
AOpen AX34-U Motherboard
R5C7 KnoppMyth
|
|
Top |
|
 |
tophee
|
Posted: Tue Aug 22, 2006 7:23 am |
|
Joined: Tue Sep 13, 2005 10:48 am
Posts: 852
Location:
London, UK
|
So when you decide to shut down, instead of doing a normal shutdown routine, mythwelcome works out when it needs to be on next and writes to the bios to wake up again at that time? In theory anyway?
Have got to stage 4. of the wiki. when i run sudo nvram-wakeup -s $(('date + %s' +900)) I get an 'date +%s' +900 is an unknown token.
_________________ Version:R8 Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)
|
|
Top |
|
 |
khrusher
|
Posted: Tue Aug 22, 2006 9:27 am |
|
Joined: Tue Apr 13, 2004 6:51 pm
Posts: 890
Location:
Groton, MA
|
make sure the single quotes around the date +%s are back quotes.... the backquote is on the key with the tilda ~
executing a program within backquotes directs the output of the program back into the command line
so Code: echo $(('date +%s' +900)) translates into 1) execute Code: date +%s 2) take the output of that command (which will be a big number in this case....1156260004 ) and put it back into the command line. This turns into Code: echo $$((1156260004 +900)) 3) and outputs Code: 1156260904
_________________ R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA
|
|
Top |
|
 |
tophee
|
Posted: Wed Aug 23, 2006 5:28 am |
|
Joined: Tue Sep 13, 2005 10:48 am
Posts: 852
Location:
London, UK
|
Thanks khrusher, That worked. It certainly helps getting the right syntax in commands!
Now another question: How do I get guess-helper to re-run and do the check on the BIOS again? I ran it through, and accepted it. Got distracted. Fiddled with the wake up time. Went back to guess-helper and it says it's completed it, but when I run nvram-wakeup again it tells me I've an unsupported board. I have looked at the website for nvram-wakeup and it appears to be supported : http://sourceforge.net/tracker/index.php?func=detail&aid=1237713&group_id=35022&atid=412959
but the additional settings don't seem to work.
Regards and thanks in advance
_________________ Version:R8 Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)
|
|
Top |
|
 |
sithlord39
|
Posted: Thu Aug 24, 2006 7:01 pm |
|
Joined: Fri Feb 03, 2006 12:22 pm
Posts: 56
|
Hi,
I too needed to rerun guess-helper. To be able to do this I simply deleted the
/root/guess-directisa and /root/guess-nvram-module/ folders and then issued the guess-helper command. Also I received the message that you did. Even when you have successfully completed guess-helper there are a few things that you must do.
1) move the nvram-wakeup.conf file from one of the above-mentioned directories to the /etc directory
2) Whenever you issue the command to nvram-wake up in step 4 you must include the directory of the file. For example, my command was the following:
Code: sudo nvram-wakeup -s $((`date +%s` + 900)) -C /etc/nvram-wakeup.conf The -C parameter lets nvram-wakeup know the location of the configuration file.
_________________ PVR-150 MCE
Radeon-9000 Pro
Seagate Barracuda 120-GB
AOpen AX34-U Motherboard
R5C7 KnoppMyth
|
|
Top |
|
 |
tophee
|
Posted: Fri Aug 25, 2006 2:17 am |
|
Joined: Tue Sep 13, 2005 10:48 am
Posts: 852
Location:
London, UK
|
Thanks for that. I was 75% - 90% on my way there to getting that. I'd read the man pages after running guess-helper the first time hence the need to rerun. I'd moved the nvram-wakeup.conf to /etc, but I didn't get it right.
Quote: sudo nvram-wakeup -s $((`date +%s` + 900)) -C /etc/nvram-wakeup.conf
THis code should sort the problems once I rerun guess-helper. I think I may have tried a similar command, but as my nvram-wakeup.conf file was wrong it still didn't work regardless.
Now trying to do things properly, I should get further.
I will give it a go and report back.
Thanks again
_________________ Version:R8 Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)
|
|
Top |
|
 |