The output can be pasted to notepad, saved as a text file, attach the text file to the post.
Printable View
The output can be pasted to notepad, saved as a text file, attach the text file to the post.
[TiVo [p0] ~]# route
route_info, afname=inet, options=33
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 32767 0 0 eth0
default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
[TiVo [p0] ~]# traceroute -p 21 210.48.107.133
traceroute to 210.48.107.133 (210.48.107.133), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 1.603 ms 1.111 ms 1.093 ms
2 203.109.128.91 (203.109.128.91) 55.333 ms 53.146 ms 58.741 ms
3 203.109.143.97 (203.109.143.97) 44.985 ms 45.981 ms 44.461 ms
4 203.109.130.161 (203.109.130.161) 48.179 ms 49.680 ms 48.679 ms
5 192.203.154.44 (192.203.154.44) 57.264 ms 45.571 ms 45.433 ms
6 192.203.154.44 (192.203.154.44) 47.081 ms 45.949 ms 45.113 ms
7 210.48.5.69 (210.48.5.69) 46.005 ms 48.279 ms 45.681 ms
8 210.48.5.2 (210.48.5.2) 45.998 ms 46.320 ms 44.913 ms
9 210.48.5.102 (210.48.5.102) 45.371 ms 46.185 ms 45.136 ms
10 210.48.17.201 (210.48.17.201) 46.467 ms 46.772 ms 45.205 ms
11 210.48.107.133 (210.48.107.133) 45.450 ms 46.488 ms 45.452 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[TiVo [p0] ~]# traceroute -p 8000 21 210.48.107.133
traceroute: "210.48.107.133" bad value for packet length
[TiVo [p0] ~]# ntpdate -v -b 210.48.107.133
[TiVo [p0] ~]# Time set to: Sat Sep 13 07:56:32 2008
Have a nice day.
David
David, run and paste
traceroute -p 8000 210.48.107.133
(and not traceroute -p 8000 21 210.48.107.133 )
You had a typo in the second last command, should be:
traceroute -p 8000 210.48.107.133
Peter.
EDIT: Jinx David. both responded together :)
Ooops. Sorry about that. Trying so hard too. Nothing has been done to TiVo since last post so this is directly following previous.
[TiVo [p0] ~]# traceroute -p 8000 210.48.107.133
traceroute to 210.48.107.133 (210.48.107.133), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 2.819 ms 1.163 ms 1.010 ms
2 203.109.128.91 (203.109.128.91) 54.016 ms 52.291 ms 53.482 ms
3 203.109.143.97 (203.109.143.97) 45.338 ms 45.481 ms 44.434 ms
4 203.109.130.161 (203.109.130.161) 45.496 ms 44.783 ms 46.112 ms
5 192.203.154.44 (192.203.154.44) 45.465 ms 44.811 ms 45.454 ms
6 192.203.154.44 (192.203.154.44) 45.170 ms 44.788 ms 45.555 ms
7 210.48.5.69 (210.48.5.69) 45.387 ms 46.738 ms 45.213 ms
8 210.48.5.2 (210.48.5.2) 45.155 ms 44.807 ms 45.682 ms
9 210.48.5.102 (210.48.5.102) 45.969 ms 45.775 ms 45.835 ms
10 210.48.17.201 (210.48.17.201) 46.350 ms 45.249 ms 45.681 ms
11 210.48.107.133 (210.48.107.133) 47.445 ms 47.428 ms 46.700 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[TiVo [p0] ~]#
David
I should have also got you to try this one:
traceroute -p 80 210.48.107.133
Peter.
[TiVo [p0] ~]# traceroute -p 80 210.48.107.133
traceroute to 210.48.107.133 (210.48.107.133), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 2.568 ms 1.150 ms 1.004 ms
2 203.109.128.91 (203.109.128.91) 52.879 ms 48.340 ms 49.444 ms
3 203.109.143.97 (203.109.143.97) 45.470 ms 45.498 ms 45.413 ms
4 203.109.130.161 (203.109.130.161) 45.039 ms 44.227 ms 45.193 ms
5 192.203.154.44 (192.203.154.44) 46.392 ms 46.705 ms 45.457 ms
6 192.203.154.44 (192.203.154.44) 44.785 ms 44.175 ms 46.192 ms
7 210.48.5.69 (210.48.5.69) 45.404 ms 47.636 ms 46.629 ms
8 210.48.5.2 (210.48.5.2) 45.192 ms 45.955 ms 45.975 ms
9 210.48.5.102 (210.48.5.102) 45.374 ms 45.693 ms 45.472 ms
10 210.48.17.201 (210.48.17.201) 46.413 ms 45.747 ms 46.140 ms
11 210.48.107.133 (210.48.107.133) 46.760 ms 46.425 ms 46.150 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[TiVo [p0] ~]#
Peter - it's version 1.3.
David
I guess you got the email notification before I edited the post :)
Ok, all the tests do show that there is no obvious proxy between you and the New Zealand server, and the TiVo seems to have normal access to the internet.
It would probably be a bit easier to start from scratch with the current image as it easier for me to support, as many files and locations have changed since 1.3.
But if you want to persevere, we can give it a go.
Please post the contents of your
/var/log/tclient
/etc/tclient.conf
/etc/rc.d/rc.net
/etc/rc.d/rc.sysinit.author
/etc/rc.d/rc.sysinit.local
Some may not exist, this is ok.
Due to the size of some you may need to zip the contents and post as an attachment.
Peter.
Thanks to you Pete and all the others who have given their time to try to help me through this.
I agree entirely that it's really wasting all our time to persevere beyond this point as there is clearly no easy fix, so it is time to bite the bullet and start from clean new software. I'm away for a few days from tomorrow so will give the reimage thing a go on my return. Look for a post on my success or otherwise towards the end of the week :-)
Thanks again
David
Ok, good luck!
Peter.
Just a further thought. If I got two TiVos, how do I control them separately? My Integra amplifier solves the problem of having two like pieces of gear in the same place by having three sets of codes built in. So I simply set the second one and it's remote to code set 2, and then I have no problems controlling each separately. But I doubt if the TiVo has this facility (especially Series 1)?
I'm assuming those of you who have more than one, site them in separate rooms and also watch recordings in those rooms so that all control is local and doesn't interfere with other TiVos you have. Is this correct?
David
It most certainly does. You can have up to 9 actually.Quote:
Originally Posted by David Stott
Easiest way is to set one to ID number 1 and the other to ID number 2 and then get a Series 2 remote that has a little switch on it that you can select between unit 1 and 2. You can also do it with Series 1 remotes but to do it easily you need to have two remotes. One Series 2 remote is more elegant.
For more info see here: http://www.oztivo.net/twiki/bin/view...iVosInSameRoom
Tivo (even series 1!) have this option too :)Quote:
Originally Posted by David Stott
http://www.oztivo.net/twiki/bin/view...iVosInSameRoom
Edit: Too slow, Darren beat me to it!
Excellent. How could I have doubted TiVo? Oh me of little faith.
David
Ah well. Maybe I'm just not supposed to have a working TiVo.
Have now done the reimage thing and putting disk into PC, booting up with Aug06 image and going through each of the setup menu options seemed to work fine. But putting disk back into TiVo, connecting all cords and plugging in power brought up "Your Recorder is starting up. Please wait a moment ..." and there it sat refusing to budge. Tried to Telnet in via Putty with no response and ditto vie IE7. Gave it 15 minutes with no change, so tried unplugging and replugging the power cord. Same result.
Things I could have done wrong:
1. I gave it the old network address of 192.168.0.111. Maybe I should have left it blank.
2. I changed the Tuner settings to Phillips instead of the Samsung default.
3. ???
Any ideas?
A possible clue is that trying to do a backup beforehand using WinSCP failed after spending time getting the directories. It then started to do the copy but quickly failed (after about 20 seconds and 2MB copied) with missing files and that soon deteriorated into a loss of the connection. Tried this a couple of times and it just kept failing at the same point. Starting to sound like a corrupt disk?
David
Tivo's just don't handle any disk errors whatsoever.Quote:
Originally Posted by David Stott
I would suggest testing the disk using the manufacturer's utility. The easiest way is to use:
http://www.ultimatebootcd.com/
It has all of them.
I think a problem disk is unlikely at this stage, it still would have gone beyond the prom screen.
That screen normally stays there if there is no drive attached.
I would first check that you have the Drive's jumper set to single drive master, and that the power and data cables are securely attached at both ends (drive & MB/PSU).
Peter.
Yes . . . well . . . ahem . . . cough, cough . . . shuffle of feet, etc.
Technically, my description of what I did is correct. I DID put the disk back into the TiVo. What I DIDN'T do, is connect it up. Seems to make a difference. (And in my defence had worked this out before Peter's message just now.)
1. However, fixing that small oversight, and plugging power cord back in had it coming up with Guided Setup OK but failing as before at the Connecting . . . step with "Failed. Service Unavailable" as before (but after 3minutes rather than the previous 16).
2. Putty'd in with no problem, and Pico'd /etc/postcodezones. Noticed that 02110 is missing so added that and tried again. No change.
3. Did a Full Restart (closest thing I could see on the new menu system that looks like a Reboot), which finished instantly (a bit suspicious that), and tried again but no joy.
4. Unplugged TiVo and plugged it back in. Browsed to TiVo and used SysAdmin/PAL-NTSC/Set PAL Guided Setup Mode which produced:
TiVo set for PAL Guided Setup. Please reboot.
root=/dev/hda4 runideturbo=false TV_STD=PAL GS=1 GS=1
Tried Full Restart but it really doesn't seem to do anything (doesn't even change the screen from the failure message) so unplugged power cord and plugged back in and it ran through GS again. No change.
5. Used SysAdmin to Set PAL and then SetPAL Guided Setup Mode (gets rid of the double GS = 1 at the end but don't suppose that matters). Used Pico to look at tclient.conf and found following:
126::66.23.218.193:80:::
# This is for the server emulator on minnie. Trouble if your ISP blocks HTTP .9
#127::131.244.9.101:80:::
# This uses emuProxy2 to avoid problems with transparent proxy. Thanks Tim!
127::127.0.0.1:8000:::
# NZ legacy
126::210.48.107.133:80:::
# NZ develop
128::210.48.107.133:8888:::
So now I need to know if there is anything I should change there.
a) The file is tiny compared with what was there before. Hope this is a good thing.
b) I note two live lines with 126 in them and referring to port 80.
c) Line 127 is the revised line that Wibble originally mentioned for getting around a proxy.
d) rc.sysinit.author does have the correct corresponding line
emuProxy2 -s 210.48.107.133 -p 8000 &
So that's probably all correct.
My next plan is to take it to a friend's house who has a different Telco and ISP to eliminate network issues as a cause but guess I'll have to go back into the reimage process to change over the network address to blank.
Have also downloaded Wibble's Ultimate Boot CD and will use it to test disk.
Unless anyone has any other ideas?
David
If your TiVo has been modified with an internal PAL tuner and you intend to use it as your program source I suggest you change this back. No, it does not affect your current connection problem, but not changing it back will mean you won't see anything via the internal tuner with it set to Philips. The brand of the internal tuner has nothing to do with the fact you have a Philips branded TiVo.Quote:
Originally Posted by David Stott
4. full restart only restarts TWP, not the TiVo.
5. To answer this, what is your DialConfig set for? To find it use TWP, go into MFS > State > PhoneConfig then look at your DialConfig setting.
b. This is an issue, put a # in front of the first one.
Can't answer the others till you answer 5.
Peter.
Peter
4. So where is Reboot now? Is unplugging power cord the only way to do it? Used to be an option from the browser and within System Reset from the menu on the TV.
5. I'm sorry, I have no idea what you are saying here. I assume that TWP means TiVo Web Plus but that's it. Am I using the browser, the main menu showing on the telly or something like WinSCP to look at the actual disk? None of these bring up anything that could be construed as MFS, so I'll need a bit of pointing in the right direction here.
5b. Did that and had no effect (would have been surprised if did since presumably it's not causing problems for others).
BTW, clicking on Info when accessing the TiVo using my browser brings up the following which doesn't seem right:
INTERNAL SERVER ERROR
--cut here--
action_info '/' ''
no such object:
while executing
"dbobj $channel get Number"
("uplevel" body line 4)
invoked from within
"uplevel $body"
invoked from within
"transaction {uplevel $body}"
(procedure "RetryTransaction" line 5)
invoked from within
"RetryTransaction {
set state [db $db open "/State/MyWorld"]
set channel [dbobj $state get LastChannel]
set chnum [db..."
(procedure "::action_info" line 63)
invoked from within
"::action_$action $chan $part $env"
("eval" body line 1)
invoked from within
"eval {::action_$action $chan $part $env}"
Further, when I use my browser to point directly at 210.48.107.133 I get the following:
"NZ Data Development Zone
You've reached the development root directory for the NZTivo data effort.
Confused? -> Visit the forums or the wiki for more info :P
What is a Tivo?
In short Tivo is a (smart) digital video recorder that uses Hard Disk technology as opposed to tape technology such as conventional VCR's! Tivo is defined as a Personal Video Recorder (PVR) or Digital Video Recorder (DVR), an acronym for a device that:
puts you in control of your TV viewing
allows you to quickly access lists of recordings
skip quickly through extraneous parts of the recordings
lets you watch what you want, when you want!
The Tivo combines several important technologies together, such as real-time hardware video encoding, hard disk storage, and an electronic program guide (EPG). The key features of this combination of technologies are the recording and playback of shows, time-shifting (the ability to rewind/pause/fast-forward live TV), the ability to schedule regular recordings (eg daily/weekly shows), and the ability to suggest and record new shows (based on your likes/dislikes), etc.
Last Updated: 9th March 2006"
Is that what's supposed to happen?
David
Darren - Re your question about my internal tuner, I have no such thing as far as I'm aware. I use a Freeview satellite decoder attached via RCA cables to tune into TV. So I assume no need to worry about the setting?
BTW, I'm still unable to see live TV via the TiVo. Has anyone else ever had this symptom, and if so how did you resolve it?
Also, I assume I'm going to have to change the network address to blank if I'm to try running the TiVo through someone else's router. Is there an easy way to do that or do I have to go through the full reimage procedure again?
David
David
Rebooting can also be done by typing "reboot" into a putty session. Yes use a browser to access TWP, the successor to what I think you were using. It can also be seen at http://thomson.tivo.googlepages.com/main.htm. Changes are noted at http://thomson.tivo.googlepages.com/tivowebplus2
Darren et al, David only has satellite available where he lives, so any terrestrial signal is not an option for him, seemingly making any TiVo tuner superfluous in his case.
4. I can't remember reboot being available from TiVoWeb, but is should still be available from the TiVo on screen menus or by typing reboot as David H has said.
5. You are probably running an older version of either TiVoWeb (TW) or TiVoWebPlus (TWP) than what I am using so I can't point you to exactly which menu has MFS. But if you can't find it by browsing through the menus then just try typing your TiVo's IP address followed by /mfs into a browser (eg. 192.168.1.16/mfs). Then follow the instructions I gave earlier.
You will need to set your TiVo to DHCP from the current fixed IP if you wanted to test elsewhere. I would rather you did not do this before giving the answer to 5.
The only problem I have is that I will be leaving soon and will not likely be back on the internet until Monday night.
Peter.
David
Thanks for Reboot tip. That works fine.
Thanks also for pointing me to Version 1.3.1 of TWP. Was on 1.2.3 from the Aug06 image and hadn't realised that should be updated. That's now running.
Unfortunately, I still can't work out what Peter wants me to do with it, as I can't see anything that looks like "MFS". However, if he's asking what the Dial Prefix is in GS Dialing Options, I can confirm it is ,#401.
Stop Press. I see my reply has crossed with Peter's. On to that now thanks Peter.
David
Peter
Found it under More. Contents of PhoneConfig are:
PhoneConfig 2276/10 {
Version = 163
CallWaitingPrefix = {}
LastSuccessCallSecInDay = 0
LastCallAttemptSecInDay = 1221983863
CallStatusInfo = 14
LocalAreaCode = 002
DialConfig = 127
DialPrefix = ,#401
LastCallStatus = Failed
NextCallAttemptSecInDay = 1221989987
IndexPath = /State/PhoneConfig
}
David
No, no need to worry about it then. Kind of begs the question why you thought it necessary to change it in the first place.Quote:
Originally Posted by David Stott
Thanks for that Darren. I was clearly confused.
I have now taken the TiVo to a friend's place but the result was still the same, just terminating even faster after about a minute from the "Connecting ..." message. Different router, telco, and ISP, so guess that confirms that there is definitely a problem with either the TiVo hardware or software.
Next step is to check the hard disk.
David
David
Did you restore it to full DHCP? It might pay to check it is getting the correct gateway address? When you changed ISP's did your router also change? With the second TiVo you will need to ensure the MAC addresses are different, else you'll probably notice more issues!
Wibble. Have tried to use the Ultimate Boot CD software you recommended but after installing it, it recommends running UBCD4WinBuilder.exe. This comes up and immediately fails as it can't find subfolder C:/UBCD4Win/i386. Since it created C:/UBCD4Win as part of the installation process, this hardly seems my fault.
Any ideas as to what I should do now?
David
Ok I'm back, that's what I was looking for.Quote:
Originally Posted by David Stott
So right now it is set to use emuproxy. Lets bypass that and see what happens.
In tclient.conf, an you put a # in front of the line below the emuproxy comment so it looks like this #127::127.0.0.1:8000::: and add a new line at the bottom that looks like this 127::210.48.107.133:8000:::
reboot and try again.
Peter.
Peter
Made that change , rebooted and went through GS. Same result as before except that now back to the old situation of it taking a full 16 minutes to fail.
Here's confirmation of my change:
# This uses emuProxy2 to avoid problems with transparent proxy. Thanks Tim!
#127::127.0.0.1:8000:::
127::210.48.107.133:8000:::
David
Do you have a /var/log/tclient file?
If you do please post it.
Peter.
Ps I don't think you are having drive issue. But it just shouldn't be this hard to get a Philips unit going in NZ.
Peter
Log of tonight's run attached.
David
Have you actually completed the guided setup?
Is this log from trying to run the guided setup, or is it from you trying to force a daily call?
Peter.
Peter - I have always run GS. Never just a daily call. The GS has failed EVERY TIME at the "Connecting ..." stage. The only variation has been in how long it takes to fail, which has varied from 1 minute (at my friends house with different Router, telco, and ISP), to 16 minutes (when I first started running it and now with your latest change). Before the latest change it was failing after 3 -4 minutes.
David
This doesn't sound right.Quote:
Originally Posted by David Stott
You want to download the ISO image, burn it to cd then boot off it on a PC with the tivo drive plugged in (and to be safe any other drive unplugged)
Here's one of the mirrors:
http://www.ausgamers.com/files/details/html/28473
You are now connecting to the server but are failing part way through.Quote:
Originally Posted by David Stott
If you look at the times, it fails and times out on "XferRqst timeout waiting to read"
Your log:
Sep 22 21:32:20 (none) comm[153]: CommUtil: connection to host 210.48.107.133, port 8000, err 0x0
Sep 22 21:32:20 (none) comm[153]: Uploading HTTP Header for modLog of /var/log/svclog: POST /tivo-service/mlog.cgi HTTP/1.0^M Content-Length: 1432^M ^M
Sep 22 21:32:20 (none) comm[153]: read HTTP Header: HTTP/1.1 200 OK^M Date: Mon, 22 Sep 2008 09:32:15 GMT^M Server: Apache/2.0.54 (Mandriva Linux/PREFORK-13.3.20060mdk) mod_ssl/2.0.54 OpenSSL/0.9.7g PHP/5.0.4 mod_perl/2.0.1 Perl/v5.8.7^M Connection: close^M Content-Type: text/plain; charset=IS
Sep 22 21:32:20 (none) comm[153]: O-8859-1
Sep 22 21:32:20 (none) comm[153]: SvcLogRqst::verify: enter
Sep 22 21:32:20 (none) comm[153]: SvcLogRqst::verify: unlink(/var/log/svclog.upload)ed (status = 0)
Sep 22 21:32:20 (none) comm[153]: CommUtil: connection to host 210.48.107.133, port 8000, err 0x0
Sep 22 21:32:20 (none) comm[153]: read 384 bytes of upload data for FourOneOneRqst
Sep 22 21:32:21 (none) comm[153]: CommUtil: connection to host 210.48.107.133, port 8000, err 0x0
Sep 22 21:32:21 (none) comm[153]: read 1892 bytes of upload data for HServerRqst
Sep 22 21:35:17 (none) comm[153]: XferRqst timeout waiting to read
Sep 22 21:46:22 (none) WatchdogAction[149]: WatchdogAction::Trigger: callActive for 900 interval-secs
Sep 22 21:47:45 (none) comm[153]: drainGetPostQ: doXfer failed err=65535 (0xffff)
Sep 22 21:47:45 (none) comm[153]: NetAgent: drainPostQ failed, err = 0xffff
Here's my working log:
Sep 23 00:51:29 (none) comm[153]: Uploading HTTP Header for modLog of /var/log/svclog: POST /tivo-service/mlog.cgi HTTP/1.0^M Content-Length: 753^M ^M
Sep 23 00:51:29 (none) comm[153]: read HTTP Header: HTTP/1.1 200 OK^M Date: Mon, 22 Sep 2008 12:51:32 GMT^M Server: Apache/2.0.54 (Mandriva Linux/PREFORK-13.3.20060mdk) mod_
ssl/2.0.54 OpenSSL/0.9.7g PHP/5.0.4 mod_perl/2.0.1 Perl/v5.8.7^M Connection: close^M Content-Type: text/plain; charset=IS
Sep 23 00:51:29 (none) comm[153]: O-8859-1
Sep 23 00:51:29 (none) comm[153]: SvcLogRqst::verify: enter
Sep 23 00:51:29 (none) comm[153]: SvcLogRqst::verify: unlink(/var/log/svclog.upload)ed (status = 0)
Sep 23 00:51:29 (none) comm[153]: couldn't stat input file, reason = No such file or directory
Sep 23 00:51:29 (none) comm[153]: NetAgent::doXfer: open failed on Rqst : No such file or directory
Sep 23 00:51:29 (none) comm[153]: drainGetPostQ: doXfer failed err=65535 (0xffff)
Sep 23 00:51:29 (none) comm[153]: Xfer Performance Log says errors are Ok!
Sep 23 00:51:29 (none) comm[153]: CommUtil: connection to host 127.0.0.1, port 8000, err 0x0
Sep 23 00:51:29 (none) comm[153]: read 384 bytes of upload data for FourOneOneRqst
Sep 23 00:51:29 (none) comm[153]: CommUtil: connection to host 127.0.0.1, port 8000, err 0x0
Sep 23 00:51:29 (none) comm[153]: read 2111 bytes of upload data for HServerRqst
Sep 23 00:51:30 (none) comm[153]: HTTP header: HTTP/1.1 200 OK^M
Sep 23 00:51:30 (none) comm[153]: HTTP header: Date: Mon, 22 Sep 2008 12:51:33 GMT^M
Sep 23 00:51:30 (none) comm[153]: HTTP header: Server: Apache/2.0.54 (Mandriva Linux/PREFORK-13.3.20060mdk) mod_ssl/2.0.54 OpenSSL/0.9.7g PHP/5.0.4 mod_perl/2.0.1 Perl/v5.8.
7^M
Sep 23 00:51:30 (none) comm[153]: HTTP header: Connection: close^M
Sep 23 00:51:30 (none) comm[153]: HTTP header: Content-Type: text/plain; charset=ISO-8859-1^M
Sep 23 00:51:30 (none) comm[153]: HTTP header: ^M
Sep 23 00:51:30 (none) comm[153]: Start TCD411Resp =====================
So your network setup looks goods. The only things I can think of is a flacky disk or a flacky network.
Thanks Wibble, that site looks better. Somehow following the previous site I ended up with a .exe file of a much older version of the software anyway (3.2.0).Quote:
Originally Posted by Wibble
However, starting up a PC with a CDRom with the 4.1.1 version of the .iso file copied to it and just the TiVo hard disk in the PC produced the following:
"Managed PC Boot Agent (MBA) v3.10
Copyright, etc, etc
Node: 00500462EF12
DHCP . . .
TFTP . . . . . . . . . . . . . .
Error:
Network boot aborted.
Press any key to continue
(which I did)
Operating System not found"
So does that mean I should have my standard C: PC disk in place and put the TiVo into the D: drive space instead and then boot with the CDROM loaded?
Sorry that it must seem like pulling teeth to get me to do the right thing but I did warn at the outset that I'm highly non-technical. Perhaps I should also have added "apt to chose the wrong option at every opportunity".
David
Ummm...no.Quote:
Originally Posted by David Stott
An .iso file is a complete images of what make up a whole CD all rolled into one file. You can't simply copy that file to a CD. You need a CD burning program that can load in the .iso file and burn the CD correctly. Most programs can do this and for example the program Nero is good at it. Try doing a Google for the phrase "burning iso files"
Which of course is what I would have done when I burned the TiVo image to disk. Did I mention my memory is crap too?
OK did all that and ran tests for Western Digital which was DLG Diagnostic V4.15. The Quick Test produced "No errors detected.", but the Extended Test (which took just over an hour) resulted in "One or more errors were detected. Final Code for this drive 0356"
So is that it? I should just get a new (bigger) drive? If so, any recommendations? I see Pricespy have a number of 1TB drives for only about $200.
David
Yes, it's failing while waiting for a response to the 411 request. I usually only see this on a daily call when the wrong options have been choosen.
Maybe you could tell us what you are selecting at each screen during setup, in case there is something obvious that is wrong.
Peter.
Edit: This was actually in response to post #89, looks like a few more came through since I loaded the page. I still do not think changing drives will fix this issue.
Ok Options I have been using are:
Source: Satellite (but also try Satellite and Cable as not sure of this one)
Zip Code: 02110
Time Zone: Eastern
Daylight Savings: No
Area Code: 002
Phone Dialling: No
Also, I reimaged the file earlier this afternoon, correcting the IP Address to null as suggested by others and leaving the Tuner option to the default of Samsung, not that that makes any difference. The NIC is set to Turbonet 100MBit Wired NIC. The MAC address was left as the default as was the Host Name (and I realise I will need to change these two with the new TiVo arriving tomorrow). I then did the disk testing referred to in my last post, and have just now put the disk back in the TiVo and rebooted.
Running GS, still brings up the same old error.
Note also that there is still the issue of hardware errors on the disk which may or may not be affecting things.
David
I'm not in NZ, but reading the FAQ try using just cable as your source.
Also to setup DHCP it is not enough to just blank the IP address, you need to re-run nic_config_tivo.
Again, I wouldn't worry about the drive errors for the moment.
Peter.
What is nic-config-tivo? I've never run it (or seen any reference to it in the literature) so not sure how to "re-run" it?
Also, trying to browse into the TiVo to bring up the online menu (and changing to 192.168.0.8 which the Router tells me it has now asigned it to) it now is asking me for a login name and password. I don't recall having to enter these in the past so what the hell do I do now? NB Putty gets in just fine.
David
Just type nic_config_tivo in putty (note _ is used not -) this will bring up the network settings menu, the same as you used when you ran the installer CD.
For the TWP username enter oztivo and no password.
Have you tried using only cable as the source as I suggested?
Peter.
OK did that with the following result:
[TiVo [p1] ~]# nic_config_tivo
TiVo TurboNet/AirNet/CacheCard on Tivo Configure - 20041218
Copyright 2002-2004 Silicondust Engineering Ltd. All rights reserved.
Detecting TiVo hard drive...
Detecting TiVo partitions...
Active kernel partition = /dev/hda3.
Inactive kernel partition = /dev/hda6.
Active root partition = /dev/hda4.
Inactive root partition = /dev/hda7.
Var partition = /dev/hda9.
Determining software version...
Philips HDR Series Stand Alone TiVo running 3.0-01-1-000
Remounting root partition...
Root successfully remounted as writable.
Checking installation type...
Configuring TurboNet installation.
Checking script...
Complete.
Current/New Configuration:
timing setting = optimal
mac address = 00:0B:AD:10:10:10
ip address = dhcp
ip subnet mask = dhcp
ip gateway = dhcp
debug level = off
Options
1: Change timing setting
2: Change MAC address
3: Change IP address/gateway
4: Change debug logging option
9: View/extract log file
0: Apply and exit
!: Exit without saving
[0..6]?
[TiVo [p1] ~]# nic_config_tivo
TiVo TurboNet/AirNet/CacheCard on Tivo Configure - 20041218
Copyright 2002-2004 Silicondust Engineering Ltd. All rights reserved.
Detecting TiVo hard drive...
Detecting TiVo partitions...
Active kernel partition = /dev/hda3.
Inactive kernel partition = /dev/hda6.
Active root partition = /dev/hda4.
Inactive root partition = /dev/hda7.
Var partition = /dev/hda9.
Determining software version...
Philips HDR Series Stand Alone TiVo running 3.0-01-1-000
Remounting root partition...
Root successfully remounted as writable.
Checking installation type...
Configuring TurboNet installation.
Checking script...
Complete.
Current/New Configuration:
timing setting = optimal
mac address = 00:0B:AD:10:10:10
ip address = dhcp
ip subnet mask = dhcp
ip gateway = dhcp
debug level = off
Options
1: Change timing setting
2: Change MAC address
3: Change IP address/gateway
4: Change debug logging option
9: View/extract log file
0: Apply and exit
!: Exit without saving
[0..6]? 0
Updating script...
Complete.
Clear the log file on the tivo [y/n]? n
Remounting root partition...
Root successfully remounted as readonly.
Configuration update complete, reboot for changes to take effect.
[TiVo [p1] ~]# reboot
I reran GS (using Cable) with no change in result. I haven't "cleared and deleted all" for a while since nothing has been recording. Should I still be doing this before each GS?
Separately, my second TiVo arrived today. Unfortunately, it only has wireless and presumably not configured for my router so I can't see it on the network. Should I simply buy a NIC for it (if so what type) or is there a way in via the image boot disk?
David
I thought that (well, for the Oz version of the image which I thought the NZ was based on) if you cannot successfully do a GS then the next time you boot the TiVo it comes back up to the start of GS. This is definitely the case if you reimage the hard disk and never complete a successful GS attempt.Quote:
Originally Posted by David Stott
As for your second TiVo: Do you mean that the network card installed is totally wireless, or is there a short network lead that plugs from the network card to a wireless adaptor?
Ok, it appears that the NZ image uses the Silicon Dust nic_config_tivo, and not the OzTiVo one which I was expecting. They don't really do all the same things.
At this point it would be best if you could take your machine to someone who already has a TiVo near you and test it on their system to see if the problem is on your network or in the box.
Is there anyone in NZ who can help David? (you may want to start a new post for the request)
I wouldn't waste any money on getting a card for the new TiVo yet until you have the other one up and running.
The one thing you could try is using your existing network card on this TiVo and loading the Australian OzTiVo image then trying to setup as if you were in Australia? It won't work as a TiVo for you, as you will be getting Oz guide data and times, but at least we can confirm whether calls to our server work and if the rest of your TiVo is ok. This way if you still have network issues, at least I'm familiar with the tools and setup of our image and server. once we are finished you just load the NZ image instead.
Peter.