Guided Setup fails at first call

**Rich C** · 19-06-2006, 12:01 AM

Hi All,

Finally got around to hacking my old UK Tivo and have run into a few problems.

It all went well until I had to run guided setup and make the first call. It keeps stopping and saying connection failed : service unavailable. I have checked and double checked the settings (I selected cable and not antenna -

).

I have tried checking the network. I can ping the tivo. I can telnet into the tivo and it can ping google fine. I can force it to reboot over telnet and ping other machines on my home network.

But it will not connect to Minnie - does she not like Pommy Tivos?

I have recently tried to see if the emu proxy routine was running and so put in the following command and this is what I got out.

[TiVo [p0] ~]# ps ax
PID TTY STAT TIME COMMAND
1 ? SW 0:00 init
2 ? SW 0:00 (kflushd)
3 ? RW 0:00 (kswapd)
4 ? SW 0:01 bash /etc/rc.d/rc.sysinit
64 ? S 0:00 update (bdflush)
72 ? S 0:03 syslogd -p /var/dev/log -m 10000
74 ? SW 0:00 klogd
84 ? SW 0:00 bash /sbin/shondss.sh
85 ? SW 0:00 bash /sbin/tnlited.sh
87 ? RW 0:00 /sbin/tnlited 23 /bin/bash -login
88 ? SW 0:00 /bin/bash -login
92 ? SW 0:01 /tvbin/switcherstart -m -F
93 ? S 0:01 /tvbin/mfsd
97 ? S 0:00 fancontrol
129 ? SW 0:00 /tvbin/mcp
136 ? SW 0:00 PipeListen
137 ? S 0:00 Mcp event
139 ? SW 0:00 /tvbin/tcphonehome
143 ? R 0:03 tivosh /hack/bin/scartctl.tcl
144 ? SW 0:00 FsMpStream
145 ? SW 0:00 PipeListener
148 ? S 0:09 PhoneHome event hd
153 ? SW 0:00 /sbin/dhclient -q eth0
156 ? S 0:00 /tvbin/dbgc-mcp
157 ? SW 0:00 PipeListener
158 ? R 0:02 /tvbin/myworld
159 ? SW 0:00 FsMpStream
160 ? SW 0:00 PipeListener
161 ? SW 0:00 TmkSinkMixAud
162 ? S 0:00 TmkClipCache0
163 ? S 0:00 TmkClipCache1
164 ? R 0:16 TvMomCs22Sink
165 ? SW 0:00 TvMomCs22Sink
166 ? S 0:00 Mediaswitch0
167 ? R 0:00 TvVideoManager
168 ? R 0:00 TvRecorder
169 ? S 0:00 TmkTaskManager
170 ? S 0:00 Scheduler
171 ? S 0:00 Prioritizer
172 ? S 0:00 EventLog event
173 ? R 0:00 PvrMain
174 ? SW 0:00 bus handler
175 ? R 0:52 ContextMgr eve
241 p0 SW 0:00 /bin/bash -login
245 p0 RW 0:00 ps ax

Doesn't make much sense to me but maybe someone else will see something missing. I can't see the emu proxy routine that others have talked about in relation to problems getting the guide data.

I have even tried to get Minnie's web page which sort of works (see below):

[TiVo [p0] ~]# wget http://131.244.9.101/index.html
--14:00:00-- http://131.244.9.101/index.html
=> `index.html.1'
Connecting to 131.244.9.101:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7,388 [text/html]

0% [ ] 7,388 0.00B/s ETA 00:00

Last-modified header invalid -- time-stamp ignored.
14:00:00 (0.00 GB/s) - `index.html.1' saved [7388/7388]

Any other suggestions would be great as I would like to have this up and running again. I would have liked to copy the Aust v Brazil match tonight but I can't see that happening.
Hope someone can help

Rich

**petestrash** · 21-06-2006, 04:43 AM

This is a known issue with the current image and UK TiVo's.

See KnownIssuesCurrentImageRelease for the solution.

Peter.

**Rich C** · 21-06-2006, 12:48 PM

Much appreciated Pete. I found another thread (http://forums.oztivo.net/showthread.php?t=1055&page=2) that previously dealt with this issue late last night and it seemed to fix the problem. I had thought that I had read through everything but obviously that little known problem slipped through my understanding of the situation.

Maybe we could edit the Known Issues page as follows (underlined info is new):

The scartctl.tcl command needs to be placed in the background by appending an & to the line found near the bottom of the /etc/rc.d/rc.sysinit script. Without this all the stuff in rc.sysinit.author never gets started... things such as the emuProxy2, FTP, cron, TivoWeb, etc. This means that you won't be able to connect to download the program information and you'll get a "Failed: Service unavailable" error when Tivo tries to connect to Minnie. See this link to solve the problem (http://forums.oztivo.net/showthread.php?t=1055&page=2).

Hopefully all is now fixed.