1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Network Caller ID (NCID)

Discussion in 'TiVo Underground' started by jlc, May 21, 2003.

  1. Oct 9, 2006 #81 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    I found this thread that talks about a zipper'd HR10-250. It seems that it also needs a DEBUG_BOARD variable set in order to make the TiVo call in via broadband.
     
  2. Oct 9, 2006 #82 of 282
    charlestwaters

    charlestwaters New Member

    70
    0
    Dec 19, 2003
    Shoreline...
    This is what the file is supposed to look like. It is located in "/etc/rc.d/StageD_PreMfs/", and is called "rc.Sequence_150.CheckForDebug.sh". You can just take the contents of this file, and change yours, or copy this to your hard drive, one of the two...

    Code:
    ##############################################################################
    #
    #   File: rc.CheckForDebug.sh
    #
    #   Description: Stage D system startup script fragment
    #                Check for debug attachment and invoke debug environment
    #                if appropriate
    #
    #   Environment:
    #       Exports: DEBUG_BOARD
    #                TMK_DEBUGGER (conditionally)
    #
    #   Copyright (c) 2003-2004 TiVo Inc.
    #
    #############################################################################
    
    # Pick up DNS server information the kernel obtained via BOOTP
    function setupDns () {
        if [ -f /proc/net/pnp ]; then
            cat /proc/net/pnp > /var/etc/resolv.conf
        else
            cat /dev/null > /var/etc/resolv.conf
        fi
    }
    
    function configGateway () {
        local -a gw_route
        local gw
    
        # Add the routes to the internal network, because the default
        # route will come and go
        gw_route=(`/sbin/route -n | grep ^0.0.0.0`)
        gw=${gw_route[1]}
        if [ "$gw" != "${gw##192.168.}" -o "$gw" != "${gw##10.}" ]; then
            /sbin/route add -net 192.168.0.0 gw $gw netmask 255.255.0.0
            /sbin/route add -net 10.0.0.0 gw $gw netmask 255.0.0.0
        else
            echo "Can't determine internal net, subnet route not set"
        fi
        /sbin/route add default gw $gw metric 1
    }
    
    
    echo "Look for debug board"
    export DEBUG_BOARD=true
    
    if /sbin/ifconfig eth0 2>/dev/null | grep -q UP ; then
        PATH=/bin:/sbin:/tvbin:/devbin
    
        echo "Setting up network for debug" 
        configGateway
        setupDns
    
        export TMK_DEBUGGER=sleep
        export DEBUG_BOARD=true
        echo "Starting Telnet Listener..." 
        /sbin/tnlited 23 -r 9911 /bin/bash -login &
    
        echo "Starting /proc Listener..." 
        /tvbin/procd
    fi
     
  3. Oct 10, 2006 #83 of 282
    QAI

    QAI New Member

    3
    0
    Jun 11, 2002
    Okay I have a problem getting tivoncid working on my series1 with networking over the serial port (ppp0). Hopefully someone has the answer. I can start the ncidd daemon but when I try to start tivoncid I get the following error:
    invalid command name "0" while executing "0" (procedure "displayLog" line 1) invoked from within "displayLog "Connecting to $Host:$Port"" (procedure "connectCID" line 15) invoked from within "connectCID $Host $Port" (file "./tivoncid" line 579)

    If I start tivoncid -V I get:
    Connecting to 127.0.0.1:3333
    BGError: invalid command name "0"


    Any suggestions? I'm using the 0.66 version of ncid. Maybe the use of PPP0 for my network versus eth0? thx
     
  4. Oct 11, 2006 #84 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    Two suggestions, try them in this order, and see if one works:
    - Remove the ncid.conf file and try again
    - Try the ncid client from 0.65

    A few people reported the problem and each of the solutions above were reported to work. At the moment the cause is unknown, but it is investigated.
     
  5. Oct 12, 2006 #85 of 282
    A.C.

    A.C. New Member

    190
    0
    Sep 16, 2002
    South
    Thanks. I went ahead and made the change. I was playing around with this because I still couldn't get it to work. What I ended up doing was removing the dialing prefix. It doesn't seem like you need it once you edit this file. Matter of fact once you edit this file, you have no choice but to dial via network.

    So what i have now is a updated rc.Sequence_150.CheckForDebug.sh, and ncid seems to be working without changing the dial prefix. Does that sound right?
     
  6. Oct 13, 2006 #86 of 282
    harpegw

    harpegw Occasional Poster

    235
    0
    Feb 28, 2001
    Northwest...
    jlc, I'd like to say thank you for ncid. I zippered my two directivos a year ago, but never took advantage of ncid until yesterday. I now have one directivo with a phone line connected running ncidd serving itself, my other directivo, and my xp desktop and ibook via ncidpop. I don't know how I got along without this functionality, it's already saved me lots of scrambling when the phone rings. Thanks from a satisfied user.
     
  7. Oct 13, 2006 #87 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    Thank you for the positive feedback.
     
  8. Oct 14, 2006 #88 of 282
    A.C.

    A.C. New Member

    190
    0
    Sep 16, 2002
    South
    My box rebooted on me lastnight. I checked the kernel log and here's the last entry:

    Recursive _stray_ call, signal 11ApgManager Transition from state FAST_LOAD to FAST_LOAD

    Anyone know what it might mean? I'm doing daily call via the internet, and using NCID.
     
  9. Oct 14, 2006 #89 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    This problem was found to be in the ncid.conf file. It seems tivosh requires the set Program variable to be at the end of the file. The fix is to rename ncid.conf or move the set Program line and its comments to the end of the file.
     
  10. Oct 14, 2006 #90 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    I do not know if this is a NCID problem or not. The error message does not seem to point to NCID, but error messages are often misleading. Could you answer some questions?

    Does the log file indicate if this was around the time of the daily call?
    What version of NCID are you using (it should be v0.66)?
    How long have you been using NCID before you had the reboot?
     
  11. Oct 14, 2006 #91 of 282
    A.C.

    A.C. New Member

    190
    0
    Sep 16, 2002
    South
    Nevermind. It's fixed. I was too impatient.
     
  12. Oct 15, 2006 #92 of 282
    A.C.

    A.C. New Member

    190
    0
    Sep 16, 2002
    South

    Well it seems I spoke too soon. This morning I woke to find my HR10-250 had rebooted. So I looked at the kernel log, and saw the following just before the unit rebooted.

    Oct 15 06:30:02 (none) kernel: 0x008c901c 0x00947904 0x004726b4 0x00ef1318 0x02a2871c 0x02a304bc 0x02a298cc
    Oct 15 06:30:02 (none) kernel: 0x02a28a48 0x02a28834 0x02a60cb8 0x02a2871c 0x02a28630 0x02a2b03c 0x02a3c7e4
    Oct 15 06:30:02 (none) kernel: 0x02a3c6cc 0x02a3c57c 0x02a3bad8
    Oct 15 06:30:02 (none) kernel: END_OF_BT
    Oct 15 06:30:02 (none) kernel:
    Oct 15 06:30:02 (none) kernel: Tmk Fatal Error: Activity Phone <8583>: unexpected signal 10

    I also checked to see what time my last call happened, and it was at 1:29 AM CST, which is almost exactly the when the unit rebooted. Anyone know what might be causing this??

    JCL, I never had reboot problem until I started using NCID. I want to try something for about a week. I'm going to comment out my NCID lines in my rc.sysinit.author. I want to also remove the dubug=true line. And I'm going to remove the dialing prefix too. I want to run it for a week and see if I get reboots.
     
  13. Oct 15, 2006 #93 of 282
    A.C.

    A.C. New Member

    190
    0
    Sep 16, 2002
    South
    Would someone mind looking at an unmodded copy of their rc.Sequence_150.CheckForDebug.sh and let me know if both the DEUBG_BOARD statements are set to false? Or if someone knows off hand which way they were. Thanks
     
  14. Oct 15, 2006 #94 of 282
    MisterEd

    MisterEd Very Large Member

    645
    0
    Jun 6, 2001
    TV Land
    If you are running 6.3 or 6.3(a) it is a known issue that NCID and elseed are causing reboots when TiVo dials out. Don't think anyone has resoved it yet.
     
  15. Oct 15, 2006 #95 of 282
    A.C.

    A.C. New Member

    190
    0
    Sep 16, 2002
    South
    6.3(a). I thought the reboot issue had been resolved.
     
  16. Oct 15, 2006 #96 of 282
    Cheezmo

    Cheezmo New Member

    453
    0
    Apr 26, 2004
    Plano, TX
    You could always use cron to kill ncidd at midnight and start it up again before you normally start watching in the morning. As long as you don't force a manual call during the day that should allow them to coexist.
     
  17. Oct 15, 2006 #97 of 282
    A.C.

    A.C. New Member

    190
    0
    Sep 16, 2002
    South
    That would work well, but I don't think calls are always happening in the middle of the night.
     
  18. Oct 15, 2006 #98 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    No need to kill ncidd off, just create the lock file and it will ignore the modem, allowing the call to succeed. I seem to remember that the daily calls were a tcl script. If it still is, the call script could be modified to create the lock file before the call and remove it after the call.
     
  19. Oct 27, 2006 #99 of 282
    Cheezmo

    Cheezmo New Member

    453
    0
    Apr 26, 2004
    Plano, TX
    I had been watching the nightly call times on mine and they had always been between midnight and 2:00 AM. But, I noticed today that it has started setting the next call date to 10 days out, mid morning. Wonder why the change from nightly calls to every 10 days, but that is for another thread...

    I guess I'll look into the lock file solution.
     
  20. harpegw

    harpegw Occasional Poster

    235
    0
    Feb 28, 2001
    Northwest...
    Okay, I attempted to upgrade my installation of ncid today, to .66 from an older version. I downloaded out2osd tar file, and the ncid-0.66-series2-tivo tar file, for use on my series 2 directivo. I ftp'd the files (binary mode), then un-tarred the files per instructions. I think it's right, I have out2osd in /var/hack, and ncid, tivocid, tivoncid, all in /var/hack with newer dates. Now, ncidd appears to start upon reboot (i can see it in ps-a process list), but the tivocid command fails, Here is the output executed form the command line:

    Morpheus-TiVo# ./tivocid &
    [1] 347
    Morpheus-TiVo# invalid command name "0"
    while executing
    "0"
    (procedure "displayLog" line 1)
    invoked from within
    "displayLog "Connecting to $Host:$Port""
    (procedure "connectCID" line 15)
    invoked from within
    "connectCID $Host $Port"
    (file "./tivocid" line 579)

    Any clue what I have done wrong?
     

Share This Page