LinHES Forums
http://forum.linhes.org/

user mythtv and nvram-wakeup
http://forum.linhes.org/viewtopic.php?f=17&t=10920		 Page 1 of 1
Author:  sithlord39 [ Sat Jul 22, 2006 12:06 pm ]
Post subject:  user mythtv and nvram-wakeup
Hello all. I am try to get the wakeuptorecord feature to work. I am following the steps on the wiki over here http://www.knoppmythwiki.org/index.php?page=WakeupToRecord.
At step 6 it recommends working as user mythtv. The trouble is that I don't know the password for user mythtv. I thought that I had made it so that there was no password in step 3. However I tried to log in as user mythtv with no password and this does not work so there must be a password.I can log in as root so I should be able to get the password, I just don't know where to look. Thanks in advance.
Author:  silentmic [ Sat Jul 22, 2006 6:25 pm ]
Post subject: 
On my system, the mythtv user defaulted to a password of mythtv. I changed it. I also used that wiki article but then when 0.19 changed to using mythwelcome, which doesn't need the scripts. It means you don't have the problem of exiting the frontend and not having an easy way to get back in. I've been meaning to edit that wiki to show the mythwelcome instructions. You can find instructions for mythwelcome at http://www.mythtv.org/wiki/index.php/Mythwelcome
Author:  sithlord39 [ Sun Jul 23, 2006 9:21 am ]
Post subject: 
what steps do I need to follow in the old wiki. You mentioned that I don't need the scripts. I have done up to step five. Also, would it just be easier to wait until you change the wiki? Thanks for the heads up about mythwelcome.
Author:  silentmic [ Mon Jul 24, 2006 1:32 am ]
Post subject: 
I have copied the existing wiki and edited it for configuration with MythWelcome in a new page at http://www.knoppmythwiki.org/index.php?page=WakeupToRecordWithMythWelcome. I haven't done this for a few months so it might need editing.
Author:  sithlord39 [ Mon Jul 24, 2006 9:49 am ]
Post subject: 
Alright. Looks like I'm your guinea pig. As user mythtv I entered

Code:
sudo nvram-wakeup -s $((`date +%s` + 900))


as shown in the first part of your step 4.

This is the output that I received:

Code:
>>> sudoers file: syntax error, line 7 <<<
>>> sudoers file: syntax error, line 9 <<<
>>> sudoers file: syntax error, line 11 <<<
>>> sudoers file: syntax error, line 13 <<<
>>> sudoers file: syntax error, line 14 <<<
>>> sudoers file: syntax error, line 16 <<<
>>> sudoers file: syntax error, line 19 <<<
>>> sudoers file: syntax error, line 21 <<<
>>> sudoers file: syntax error, line 24 <<<
>>> sudoers file: syntax error, line 24 <<<
sudo: parse error in /etc/sudoers near line 7


Here is the contents of my edited /etc/sudoers:

Code:
# sudoers file.
#
# This file MUST be edited with the "visudo" command as root.
#
# See the man page for details on how to write a sudoers file.
#

# Host alias specification

# User alias specification

# Cmnd alias specification

# User privilege specification
root   ALL=(ALL) ALL

# KNOPPIX WARNING: This allows the unprivileged knoppix user to start commands as root
# KNOPPIX WARNING: This is totally insecure and (almost) makes knoppix a second root account.
# KNOPPIX WARNING: Never allow external access to the knoppix user!!!
knoppix   ALL=NOPASSWD: ALL

# changed for nvram-wakeup
#mythtv ALL=NOPASSWD:/usr/sbin/nvram-wakeup,/usr/bin/mythshutdown,/usr/local/bin/kmhalt.sh,/usr/sbin/hibernate,/usr/bin/eject,/s
bin/halt,/sbin/reboot,/bin/mount,/bin/umount,/usr/local/bin/mythbackup,/usr/local/bin/mythrestore,/etc/init.d/mythtv-backend,/usr/local/sbin/hibernate

mythtv ALL=NOPASSWD:/sbin/halt,/sbin/reboot,/bin/mount,/bin/umount,/usr/local/b in/mythbackup,/usr/local/bin/mythrestore,/usr/sbin/nvram-wakeup,/sbin/lilo


I noticed that at the top of the file it says that
Quote:
This file MUST be edited with the "visudo" command as root.


I haven't done anything like this, nor do I know how to. Could this be causing the error?
Author:  tjc [ Mon Jul 24, 2006 8:59 pm ]
Post subject: 
Actually from the looks of what you posted you corrupted the file in some interesting way. I see what looks two line breaks that don't belong there (one in s<LF>bin and one in "b<LF>in"). What did you use to edit this?
Author:  sithlord39 [ Mon Jul 24, 2006 10:22 pm ]
Post subject: 
I used WinSCP to get it on my Windows box and then used WordPad to edit it. I think I found the problem. In the wiki page the line that has to be inserted

Code:
mythtv  ALL=NOPASSWD:/sbin/halt,/sbin/reboot,/bin/mount,/bin/umount,/usr/local/bin/mythbackup,/usr/local/bin/mythrestore,/usr/sbin/nvram-wakeup,/sbin/lilo


is split up. I now made it one line before I put it in the file. Now when I run
Code:
sudo nvram-wakeup -s $((`date +%s` + 900))

as user mythtv I get the following:

Code:
nvram-wakeup: Your mainboard is currently not supported.
nvram-wakeup: Please try determining the addresses and sending the following
nvram-wakeup: information back to the maintainers:
nvram-wakeup:  - The addresses you found out (read README.mb)
nvram-wakeup:  - Mainboard vendor:
nvram-wakeup:  - Mainboard type:     1234
nvram-wakeup:  - Mainboard revision: 9189g10001
nvram-wakeup:  - BIOS vendor:        Award Software International, Inc.
nvram-wakeup:  - BIOS version:       6.00 PG
nvram-wakeup:  - BIOS release:       10/17/2001



I have run guess-helper and then
Code:
nvram-wakeup -C nvram-wakeup.conf

after copying the file to the /etc directory. I can post a copy if needed.
Author:  tjc [ Tue Jul 25, 2006 9:11 pm ]
Post subject: 
Editing Unix scripts and configuration files with Windows editors is a sure recipe for strange problems. ;-) MS-Windows has a nasty habit not just of sticking CRs in where Unix only expects a LF but also of including other invisible whitespace characters in places where they don't belong. VTs are another favorite which often have people ready to tear their hair out in large clumps. But even extra spaces at the end of a line can cause people grief.

I fix at least one of these a week for someone at work. I even configured my editor to show trailing whitespace and special characters in bright orange inverse video to make it easier. It looks incredibly ugly, but it makes potential problems really hard to miss. ;-)

I've posted a simple one line file cleaner in various threads around here for dealing with just this kind of issues....
Author:  sithlord39 [ Wed Jul 26, 2006 1:50 pm ]
Post subject: 
Alright - some progress:

I realized that I had to include the
Code:
-C /etc/nvram-wakeup.conf

in the command.

So I then issued the command:

Code:
sudo nvram-wakeup -s $((`date +%s` + 900)) -C /etc/nvram-wakeup.conf


as user mythtv.

I then did a
Code:
sudo halt

as directed in the wiki. The computer turned off and then came back on again about 10 min later (5 min less than I had told it to, but no sweat there.) However here is where I hit the problem. The BIOS spits the following error message.

Quote:
CMOS checksum error - Defaults loaded


I can press enter to boot, but that would defeat the whole point of auto-wakeup. When I actaully go into the BIOS and manually set a time to wake up everything works great. Any ideas?

PS - In case it helps here is my /etc/nvram-wakeup.conf
Code:
################################################
##  Mainboard autodetection information:
##
##    - Mainboard vendor:   ""
##    - Mainboard type:     "1234"
##    - Mainboard revision: "9189g10001"
##    - BIOS vendor:        "Award Software International, Inc."
##    - BIOS version:       "6.00 PG"
##    - BIOS release:       "10/17/2001"

addr_sec         = 0x3F
addr_min         = 0x40
addr_hour        = 0x41
#addr_stat        = 0x47
shift_stat       = 5
addr_day         = 0x51
addr_stat        = 0x6E   # but differs somewhere else
addr_chk_h       = 0x6C   # guessed
addr_chk_l       = 0x6D



I had to comment out one addr_stat because there were two. Perhaps I should try the other one?
and here is my /root/guess-directisa/guess-error.log
Code:
$Id: guess.c,v 1.22 2004/03/04 08:38:14 bistr-o-math Exp $
Opened file 31.23.59.59+ readonly...
Opened file 11.12.13.14+ readonly...
Opened file 01.00.00.00+ readonly...
Opened file 01.00.00.00- readonly...
Couldn't read byte 0x80 from 31.23.59.59+
Assuming size of files 128 bytes
guess: Opening /dev/mem in O_RDONLY mode...
guess: _DMI_ table found: base: 0xF0800, size: 0x3FD, count: 37
guess: data block   1 at offset 0x000: type   0, size 0x013 ( 19)
guess: found string "Award Software International, Inc."
guess: found string "6.00 PG"
guess: found string "10/17/2001"
guess: data block   2 at offset 0x04A: type   1, size 0x019 ( 25)
guess: data block   3 at offset 0x089: type   2, size 0x008 (  8)
guess: found string ""
guess: found string "1234"
guess: found string "9189g10001"
guess: data block   4 at offset 0x0B1: type   3, size 0x00D ( 13)
guess: data block   5 at offset 0x0C7: type   4, size 0x020 ( 32)
guess: data block   6 at offset 0x10B: type   5, size 0x016 ( 22)
guess: data block   7 at offset 0x123: type   6, size 0x00C ( 12)
guess: data block   8 at offset 0x137: type   6, size 0x00C ( 12)
guess: data block   9 at offset 0x14B: type   6, size 0x00C ( 12)
guess: data block  10 at offset 0x15F: type   7, size 0x013 ( 19)
guess: data block  11 at offset 0x182: type   7, size 0x013 ( 19)
guess: data block  12 at offset 0x1A5: type   8, size 0x009 (  9)
guess: data block  13 at offset 0x1BD: type   8, size 0x009 (  9)
guess: data block  14 at offset 0x1D7: type   8, size 0x009 (  9)
guess: data block  15 at offset 0x1E7: type   8, size 0x009 (  9)
guess: data block  16 at offset 0x1F8: type   8, size 0x009 (  9)
guess: data block  17 at offset 0x209: type   8, size 0x009 (  9)
guess: data block  18 at offset 0x21A: type   8, size 0x009 (  9)
guess: data block  19 at offset 0x22F: type   8, size 0x009 (  9)
guess: data block  20 at offset 0x24D: type   9, size 0x00D ( 13)
guess: data block  21 at offset 0x25F: type   9, size 0x00D ( 13)
guess: data block  22 at offset 0x271: type   9, size 0x00D ( 13)
guess: data block  23 at offset 0x283: type   9, size 0x00D ( 13)
guess: data block  24 at offset 0x295: type   9, size 0x00D ( 13)
guess: data block  25 at offset 0x2A7: type   9, size 0x00D ( 13)
guess: data block  26 at offset 0x2B9: type   8, size 0x009 (  9)
guess: data block  27 at offset 0x2C9: type  13, size 0x016 ( 22)
guess: data block  28 at offset 0x31A: type  16, size 0x00F ( 15)
guess: data block  29 at offset 0x32B: type  17, size 0x015 ( 21)
guess: data block  30 at offset 0x350: type  17, size 0x015 ( 21)
guess: data block  31 at offset 0x375: type  17, size 0x015 ( 21)
guess: data block  32 at offset 0x39A: type  19, size 0x00F ( 15)
guess: data block  33 at offset 0x3AB: type  20, size 0x013 ( 19)
guess: data block  34 at offset 0x3C0: type  20, size 0x013 ( 19)
guess: data block  35 at offset 0x3D5: type  20, size 0x013 ( 19)
guess: data block  36 at offset 0x3EA: type  32, size 0x00B ( 11)
guess: data block  37 at offset 0x3F7: type 127, size 0x004 (  4)
guess: Following DMI entries found:
guess:  - Mainboard vendor:   ""
guess:  - Mainboard type:     "1234"
Author:  sithlord39 [ Mon Jul 31, 2006 8:59 am ]
Post subject: 
Hi. Are there any German speakers out there who would like to give this a shot? A google search http://www.google.com/search?hs=clY&hl=en&lr=&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=nvram-wakeup+CMOS+checksum+error&btnG=Search
for nvram-wakeup CMOS checksum error leads to a number of responses but the ones that seem to be most relevant are in German. I would REALLY appreciate it if someone could look into the first few pages a bit and see if
they can spot my error.
Author:  sithlord39 [ Fri Aug 18, 2006 10:08 pm ]
Post subject: 
Alright! I flashed the BIOS to version 1.03 and reran the nvram-wakeup guess-helper. Now wake up works!!
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/