Upgrading Your Hacked HR10-250 to 6.3

[rbautch]

Rbautch, I have two questions for you.
1. Do you know if the slicer will keep modification to "rc.Sequence_050.SetupCoreEnviroment" in 7.x in order to let you start bash at the beginning of startup without the TiVo locking up?What is this issue?

2. Any luck with modifying fakecall.tcl to work with 6.3?What error are you getting? Should't be too hard to update it.

[rbautch]

I have a serial connection established with my HR10-250 that was upgraded to 6.3 with slicer. How do I re-enable the TiVo hacks that were there before and enable the network adapter? What folders are they located in. The hacks were from the PTVnet install.First check your /ptvupgrade file to make sure it got copied over. I imagine everything should work as before once you get networking going.

[slydog75]

I've been in contact with Lou at PTVupgrade, and they've updated the slicer to hopefully set up networking without the need for a serial cable. He sent me a version to test, and it seems to work, but I've only tested it on my 6.2 boxes, since I don't have 6.3 slices at the moment.

Any chance that something in the zipper is keeping the slices from downloading? I thought the slices were broadcast to everyone at the same time.

[Lord Vader]

sly, they're rolling out on a random basis from September 13th through October 4th. In fact, some people with multiple HR10-250s got the upgrade on one or two of their units but not the others.

[Lord Vader]

I've been in contact with Lou at PTVupgrade, and they've updated the slicer to hopefully set up networking without the need for a serial cable. He sent me a version to test, and it seems to work, but I've only tested it on my 6.2 boxes, since I don't have 6.3 slices at the moment.

And once this is done, you'll be working on the "new and improved" Zipper, which will apply to 6.3 as well, right? :D

Seriously, though, I would guess that for those who haven't done the upgrade yet--I'm one of them because I haven't gotten 6.3 as of today--patience might be in order. By the time we get our upgrade, The Slicer may be all good and ready to go for 6.3, and that version will quite probably have all the bugs ironed out.

[bxs122]

I've been in contact with Lou at PTVupgrade, and they've updated the slicer to hopefully set up networking without the need for a serial cable. He sent me a version to test, and it seems to work, but I've only tested it on my 6.2 boxes, since I don't have 6.3 slices at the moment.

Cool ... I still don't have the slices but would love to get the latest Slicer. I do have Slicer 1.1 but now know that won't solve the network issue.


Expecting to use Slicer 1.1 I built a serial cable for my HR10-250 following directions posted previously where pin mapping is 2 -> tip, 3 -> ring, 5 -> shield

I can cross the tip and ring and from Hyperterminal see what I am typing so I know the COM port and cable are functioning.

When I plug it into the HR10-250 I get nothing ... I've tried every setting I could think of and the closest I got was to telnet in via Ethernet to force a reboot. On reboot I kept the Hyperterminal session open to watch if anyting came over the serial cable. Only thing I got was garbage.

How do I get a bash prompt using the serial cable??

[rbautch]

It's probably your settings in Hyperterminal. Make sure flow control is off, and speed is set to 115,200.

[Lord Vader]

russ, do you know where i can find a copy of dos2unix? I seem to have "misplaced" mine. :p

[W2DHS]

See here (http://www.tivocommunity.com/tivo-vb/showthread.php?p=4376444#post4376444).

<blush>

thanks.

[Lord Vader]

I just spoke with Lou at PTVupgrade, and he's attending to some personal business today. He gave me permission to distribute the test version of Slicer 1.2 to existing customers. If you're interested in giving it a go, email me at customerservice@mastersav.com with some kind of proof of purchase.

Personal business? You mean we actually have LIVES outside these forums and all? Amazing. :p

Anyway...sent you an Email w/ my receipt.

[bxs122]

It's probably your settings in Hyperterminal. Make sure flow control is off, and speed is set to 115,200.

Cool got a bash prompt ... exited Hyperterminal, went back in and now no prompt.

What is the proper way of disconnecting a from a serial connection?

[gazzie4]

I did the upgrade by slicer 1.2 Thursday night. Worked other than networking...I have access through teraterm through serial and get a bash prompt. when I plug in the usb I get the following:
bash-2.02# hub.c: port 1, portstatus 100, change 3, 12 Mb/s
hub.c: port 2, portstatus 100, change 0, 12 Mb/s
hub.c: port 3, portstatus 100, change 0, 12 Mb/s
hub.c: port 4, portstatus 100, change 0, 12 Mb/s
hub.c: port 5, portstatus 100, change 0, 12 Mb/s
hub.c: port 1, portstatus 100, change 0, 12 Mb/s
hub.c: port 2, portstatus 501, change 1, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 511, change 0, 480 Mb/s
hub.c: port 2, portstatus 503, change 10, 480 Mb/s
usb.c: USB device 3 (vend/prod 0x13b1/0x18) is not claimed by any active driver.
hub.c: port 3, portstatus 100, change 0, 12 Mb/s
hub.c: port 4, portstatus 100, change 0, 12 Mb/s
hub.c: port 5, portstatus 100, change 0, 12 Mb/s
it appears that I am just missing the drivers?!? is there any way to download these, or move these to the right location and reboot to test and see if this fixes the problem?

[gazzie4]

sorry slicer 1.1

[cheer]

I did the upgrade by slicer 1.2 Thursday night. Worked other than networking...I have access through teraterm through serial and get a bash prompt. when I plug in the usb I get the following:
bash-2.02# hub.c: port 1, portstatus 100, change 3, 12 Mb/s
hub.c: port 2, portstatus 100, change 0, 12 Mb/s
hub.c: port 3, portstatus 100, change 0, 12 Mb/s
hub.c: port 4, portstatus 100, change 0, 12 Mb/s
hub.c: port 5, portstatus 100, change 0, 12 Mb/s
hub.c: port 1, portstatus 100, change 0, 12 Mb/s
hub.c: port 2, portstatus 501, change 1, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 511, change 0, 480 Mb/s
hub.c: port 2, portstatus 503, change 10, 480 Mb/s
usb.c: USB device 3 (vend/prod 0x13b1/0x18) is not claimed by any active driver.
hub.c: port 3, portstatus 100, change 0, 12 Mb/s
hub.c: port 4, portstatus 100, change 0, 12 Mb/s
hub.c: port 5, portstatus 100, change 0, 12 Mb/s
it appears that I am just missing the drivers?!? is there any way to download these, or move these to the right location and reboot to test and see if this fixes the problem?That's normal, I think...I vaguely remember JamieP saying at one point that that "not claimed" message appears because usb.net (or whatever) hasn't loaded yet.

How did you set your networking information (IP, etc.)? What kind of adapter, by the way?

[nc88keyz]

With all the people who help out here and the other forum I find it hard to understand why a 6.3 image has not been created for those who would like to get our utilities and scripts up to speed.

Is it a technical issue at this point.

I would have thought emule would have a 6.3 image by now, even if it wasnt a stripped down one.

In order for a non encrypted slices install, i would imagine that the image would have to be had first.

Heres to the first person who creates a legit image for those who can better this process.

Whether the image is frowned upon or not.

[Lord Vader]

Wait on this and it'll pop up. Remember, not everyone has received the upgrade yet, so it's rather difficult to come up with an image this soon. It'll be out there. Even the PTV folks who do Instantcake will probably end up having it once they get their image of it to begin with.

[nc88keyz]

thats my whole point. why should ptv upgrade have to wait for it? obviously there are plenty that understand linux, tivo and imaging.


S>>>>>>>>>H>>>>>>>>>>>>>>>A>>>>>>>>>>>>R>>>>>>>>>>>>>>E !!!

Just DO it!

[gazzie4]

I tried upgrading the kernel to 7.2.2 and it didn't fix any of the problems. I did not on the reboot though, that it ended up going to hda9? is that a secondary or backup system boot?

[cheer]

I did not on the reboot though, that it ended up going to hda9? is that a secondary or backup system boot?
I have no idea what most of that sentence means, but /dev/hda9 is your /var partition.

[cheer]

thats my whole point. why should ptv upgrade have to wait for it? obviously there are plenty that understand linux, tivo and imaging.
Right. But perhaps we have other things going on -- life, etc. Plus, my one-and-only HR10-250 is the center of my family room; pulling it down again to create an image would likely cause a revolt, especially after I hosed it this morning with a typo in my monte config. :)

It'll come. Someone will get to it. Patience, grasshoppers.

[gazzie4]

I just formatted back to 3.1.5 with instacake and ptvnet, the 7.2.2 kernel did not work...I think I did something wrong though, as it locked up and wouldn't continue, I figure at this point its best to wait for slicer 1.12 or later.

[Lord Vader]

thats my whole point. why should ptv upgrade have to wait for it? obviously there are plenty that understand linux, tivo and imaging.


S>>>>>>>>>H>>>>>>>>>>>>>>>A>>>>>>>>>>>>R>>>>>>>>>>>>>>E !!!

Just DO it!

Impatient little bleep, aren't you? It's not that simple. Besides, the upgrade just arrived--on only SOME units--a few days ago. It takes time to iron out all the issues involved.

[Redux]

Patience, grasshoppers.Totally unacceptable. You offer trite excuses when we have hundreds of users here waiting. There's a total lack here of any sense of responsibility. Users know this is an exceeedingly trivial task, and it's just laziness, procrastination and incompetence that's keeping them from getting what they want.

Fewer excuses and more elbow grease, cheer!

[mattdb]

Totally unacceptable. You offer trite excuses when we have hundreds of users here waiting. There's a total lack here of any sense of responsibility. Users know this is an exceeedingly trivial task, and it's just laziness, procrastination and incompetence that's keeping them from getting what they want.

Fewer excuses and more elbow grease, cheer!

You have got to be kidding. I know just enough about this stuff to be dangerous, but I do know enough not to look a give horse in the mouth. If you are so anxious, like I am, fix it your self. I still haven't got mine to boot to 6.3. But who am I blaming.... ME ME ME ME ME ME ME.

Now, back to my problem, I can't get by assertion failure on either of my boot partitions now.

[Lord Vader]

Totally unacceptable. You offer trite excuses when we have hundreds of users here waiting. There's a total lack here of any sense of responsibility. Users know this is an exceeedingly trivial task, and it's just laziness, procrastination and incompetence that's keeping them from getting what they want.

Fewer excuses and more elbow grease, cheer!

I sure hope this post was intentionally facetious, because if it wasn't, it's one of the most asinine and insulting ones I've read here.

[cheer]

Totally unacceptable. You offer trite excuses when we have hundreds of users here waiting. There's a total lack here of any sense of responsibility. Users know this is an exceeedingly trivial task, and it's just laziness, procrastination and incompetence that's keeping them from getting what they want.

Fewer excuses and more elbow grease, cheer!
OK, who gave my wife the URL to TCF? :)

P.S. KIDDING! I'm kidding! My wife is a saint, she is.

[rbautch]

Right. But perhaps we have other things going on -- life, etc. Plus, my one-and-only HR10-250 is the center of my family room; pulling it down again to create an image would likely cause a revolt, especially after I hosed it this morning with a typo in my monte config. :)So true. Last night I was working on my MBR tivo and accidently dragged a serial cable accross the power supply. Big spark, and now tivo is dead. Had some splaining to do. Luckily it wasn't my HR10-250!

[gsr]

I sure hope this post was intentionally facetious, because if it wasn't, it's one of the most asinine and insulting ones I've read here.

Yikes, the only thing missing from Redux's post was the smiley.

Redux - clearly you need to include a smiley next time...

It really is amazing just how impatient some people can be. Nc88keyz - as others have said, the people who make this stuff happen need to be given the space they need. If anything, pressuring them is just going to annoy them which probably isn't a good thing for the rest of us.

If you don't really know what you're doing, either live with the current software for now (if you're hacked and have upgrades disabled) and wait until the dust settles. If you aren't hacked, then let 6.3 install itself and hold off on hacking until the Zipper supports 6.3 (which RBautch did say may be a while) or instructions that match your capabilities come along.

The reality is that while 6.3 will most definitely be a welcome upgrade, it doesn't have any features that any of us must have right this second. Yeah, the faster speed will be nice, but we've been living with what we have for so long now, is another few days or weeks really going to kill us?

I haven't received the 6.3 slices yet. Personally, I consider that a good thing as by the time I receive them the Slicer program might be ready to upgrade my hacked HR10-250 without any issues.

[Lord Vader]

So true. Last night I was working on my MBR tivo and accidently dragged a serial cable accross the power supply. Big spark, and now tivo is dead. Had some splaining to do. Luckily it wasn't my HR10-250!

Russ, call your insurance company, tell them you had a surge that damaged some of your home electronics items, and maybe you can get a claim check out of them.

Hint: It's worked for me more than once. :D

[mattdb]

So true. Last night I was working on my MBR tivo and accidently dragged a serial cable accross the power supply. Big spark, and now tivo is dead. Had some splaining to do. Luckily it wasn't my HR10-250!

Man I did that just last month. It was one of my HR10's but luckily I had a spare power supply.

PS: I sent you an email about getting the new slicer.

Matt

[mattdb]

Russ, call your insurance company, tell them you had a surge that damaged some of your home electronics items, and maybe you can get a claim check out of them.

Hint: It's worked for me more than once. :D

I did that and they went up on my rates when I lost a TV.

[rbautch]

I had a lightning strike in my backyard last year that fried everything I own, including a freshly built PC. I don't think my insurance company would be as understanding with this one. :p

Edit: A new power supply sells for $50. I just bought a used tivo on Ebay for $15. seller says video freezes, but who cares. It's funny to me that power supplies and network adapters cost more than the tivo itself. My first one was $300.

[willardcpa]

....Now, back to my problem, I can't get by assertion failure....Have you tried those little blue pills?? ;)

Oh, you said "assertion", nevermind. :o

[willardcpa]

....I just bought a used tivo on Ebay for $15. seller says video freezes, but who cares......Probably cause the power supply keeps hiccuping! :p :D

[mattdb]

OK I must be an idiot. I have a hacked HR10 we will call it TiVoA.

On TiVoA, I telneted is and dd'ed hda3, hda4 hda6 and hda7 to files.
FTP'ed those files off.

Now I have another HR10 we will call it TiVoB.

So now I took the files I made above on TiVoA and DD'ed them to TiVoB and it will not boot. I am on a reboot loop with the same error on both roots.

When I serial connect and get Kernel panic: No init found. Try passing init= option to kernel.

I am trying to salvage some recordings. I am clueless why this doesn't work.

[rbautch]

Check if /bin/init is missing. Also check your bootpage parameters.

[pdawg17]

I just want to confirm...I put my 3.1.5f backup image (tivo.bak) on a FAT32 hd...if I boot into windows with that drive will it corrupt the image? I want to make sure in case I need to go back to 3.1.5f if 6.3 screws up...

[mattdb]

Check if /bin/init is missing. Also check your bootpage parameters.

do you mean /sbin/init? there isn't one in any of my /bin/ on any of my TiVo's

well my sbin on hda7 has

ksyms restart rmmod

and on hda4

rc.Sequence_100.InovkeLateStressDiags.sh
rc.Sequence_300.CheckForDvdBurnTest.sh

But on my hacked tivo that I copied from has:

Bedroom-TiVo# cd sbin
Bedroom-TiVo# ls
badblocks e2fsck irprog pppd syslogd
bootpage ifconfig irtest restart tivoftpd
bootpclient init klogd rmmod tnlited
builddev insmod ksyms route updatekernel
buildskeleton irbmicro.hex mke2fs rsh updateroot
cmp irmicro.hex mknod syslog

What on earth gives?

Why is that folder not copied?

Well I copied the sbin files over and I still get the same error.

This is very frustrating.

Is there path setting that is missing? I did make sure I chmod the files. There is a path in the rc.sysinit file.

Ok one thing that is strange on this box it that when it check the bootpages I get

bootpage -p /dev/hdc

root=/dev/hda7 dsscon=true console=2,115200

bootpage -b /dev/hdc

Boot Partition 7.

Shouldn't that be 6? I tried to change it to 6, but I couldn't get it to take.

Looks like these recordings are gone. I just don't know where to go from here.

Matt

[rbautch]

I just want to confirm...I put my 3.1.5f backup image (tivo.bak) on a FAT32 hd...if I boot into windows with that drive will it corrupt the image? I want to make sure in case I need to go back to 3.1.5f if 6.3 screws up...No, it will be fine.

[rbautch]

Boot Partition 7.

Shouldn't that be 6?
MattYes it should be 6. Could you have copied a kernel to your root filesystem partition?

[mattdb]

Yes it should be 6. Could you have copied a kernel to your root filesystem partition?

I guess it's possible, but I was very careful in my dd'ing. How do I force a change?

[pdawg17]

I don't get it...I've had the slices for a full day at least and I can't get the slices to be installed with a phone call...it did a SDD last night as well but when I forced a call this AM, it just says "Succeeded"...it is a Zippered box but I did option 1 at the start of this thread...anything else I should check for?

[mattdb]

I don't get it...I've had the slices for a full day at least and I can't get the slices to be installed with a phone call...it did a SDD last night as well but when I forced a call this AM, it just says "Succeeded"...it is a Zippered box but I did option 1 at the start of this thread...anything else I should check for?


I am not sure but I think DTV is rolling out the upgrade in stages. Just because you have the slices doesn't mean it will install. DTV has to send another signal to your box to start the process.

Matt

[mattdb]

Just a bit of advice from experience. You really should back up your drive(s) before you manually attempt any of this.

Matt

[mattdb]

Well I just cloned one of my other tivo's and tried the new slicer and well, it just goes into a reboot loop.

Attached is the log. :-(


read 0x2aca0000 /lib/libcdaudio.so
0x02a7ea98 0x02a82cf0 0x02a24620 0x02a4ff2c 0x00691e28 0x02a28c08 0x02a28834
0x02a60cb8 0x02a2871c 0x02a28630 0x02a2b03c 0x02a3c7e4 0x02a3c6cc 0x02a3c57c
0x02a3bad8
END_OF_BT

Tmk Fatal Error: Activity TvBusProxy <115>: assertion failure



Althought it did alot more stuff on the first try than the last

[cheer]

Your iptables file is corrupt, not executable, or just missing.

[mattdb]

Your iptables file is corrupt, not executable, or just missing.


Well crap on it. I just tried the new slicer and it didn't work.

Is there anyway to install 6.3 and get that working then pull the drive and install the hacks manually. I am tired of trying to get this done the "easy" way.

do I just execute installSw.itcl

further does anyone if killhdinitrd will work on the kernel? Or are we still just copying it over?

[jasch]

What is this issue?

If you try to load bcm7315tty.o yourself in 7.2 before starting the tivo software: the tivo software will refuse to start if that module is already loaded. The simple fix is to edit /etc/rc.d/StateA_PreKickstart/rc.Sequence_050.SetupCoreEnviroment to force failOk to 1 at the start of the loadModule() function.

What error are you getting? Should't be too hard to update it.

It was giving an error, yet it seems the info was getting updated. Per a recommendation on DDB I changed

dbobj $ssobj set Complete 7

to

try { dbobj $ssobj set Complete 7 } catch junk { }

[cheer]

Well crap on it. I just tried the new slicer and it didn't work.

Is there anyway to install 6.3 and get that working then pull the drive and install the hacks manually. I am tired of trying to get this done the "easy" way.

do I just execute installSw.itcl

further does anyone if killhdinitrd will work on the kernel? Or are we still just copying it over?
The problem is I really don't know what state your various partitions are in at this point, so I don't know whether even a manual trigger will work. But if you want to try, edit installSw.itcl. Look for this line:exec /var/utils/updateroot /dev/hda /install /var/packages >&@ stdoutAnd change it to this:exec /var/utils/updateroot /dev/hda /install /var/packages $name >&@ stdoutThen run:/tvbin/installSw.itcl 6.3-01-2-357And you're off and running. It'll reboot at the end.

Killhdinitrd won't work. You need to replace the kernel. Ideally use a 7.2.2-oth-K1 killhdinitrd'd kernel (available on the ptvupgrade $5 boot CD), but if you don't have one you can use a 3.1.5 kernel so long as DHCP isn't a requirement.

[Lord Vader]

Just out of curiosity, has anyone tried the newest Slicer, the one rbautch had sent yesterday to PTV's customers? If so, did this version work?

[SacR32]

I still havent recieved the update. I was doing some research last night on past upgrades.

I have a zippered HR that was done a few months ago with 2 500gb HD.

I am unable to mount the hda4. My question is should I be able to mount it at this point? Could this be why I havent recieved the update yet?

[cheer]

I still havent recieved the update. I was doing some research last night on past upgrades.

I have a zippered HR that was done a few months ago with 2 500gb HD.

I am unable to mount the hda4. My question is should I be able to mount it at this point? Could this be why I havent recieved the update yet?
If your current active root is /dev/hda7 and you've never had a software update, then /dev/hda4 could be blank or unformatted. No big deal. So yes, you wouldn't be able to mount it, but no, that will not stop you from getting the update.

[samhammer]

Well my HR10 lost the hacks a while ago, so it took the 6.3 upgrade. I just tried to hack it again using the new zipper. I got no error messages, however it is in an endless boot loop. I searched on Boot Loop, and found other people getting this also, but did not find any info on what I need to do to fix it. I do have the drive hooked back up to my pc.

Can zipper still be used to get out of this, or do I need to do it without zipper as I did the first time many months ago?

And direction would be helpfull.

Sam

[mattdb]

Just out of curiosity, has anyone tried the newest Slicer, the one rbautch had sent yesterday to PTV's customers? If so, did this version work?

That is the one I tried and it didn't work for me. See my posts above.

Matt

[cheer]

Well my HR10 lost the hacks a while ago, so it took the 6.3 upgrade. I just tried to hack it again using the new zipper. I got no error messages, however it is in an endless boot loop. I searched on Boot Loop, and found other people getting this also, but did not find any info on what I need to do to fix it. I do have the drive hooked back up to my pc.

Can zipper still be used to get out of this, or do I need to do it without zipper as I did the first time many months ago?

And direction would be helpfull.

Sam
I wasn't aware the Zipper supported 6.3 yet.

Hard to tell exactly what is wrong without data. Since you have the drive hooked up to your PC, can you tell us what is in the kernel log?

[jjn]

Got the update on one HR10 last night.
Dl'd slicer this morning, ran it and it seemed to work.
It did not copy the enhancements folder, so i added it manually.
TWP folder was there but it was empty.
Added a new copy and it works.
I never lost my network connection.
The only problem is in system info it says my account is closed.
Guess I'll have to call D*.

Hope the update comes tonight for the other HR10

[rbautch]

Well my HR10 lost the hacks a while ago, so it took the 6.3 upgrade. I just tried to hack it again using the new zipper. I got no error messages, however it is in an endless boot loop. I searched on Boot Loop, and found other people getting this also, but did not find any info on what I need to do to fix it. I do have the drive hooked back up to my pc.

Can zipper still be used to get out of this, or do I need to do it without zipper as I did the first time many months ago?

And direction would be helpfull.

SamThe Zipper does not support 6.3 yet. One thing that immediately comes to mind is that 6.3 requires the iptables fix instead of disabling netfilter. That would be the first thing to try.

[hpfanatic]

The problem is I really don't know what state your various partitions are in at this point, so I don't know whether even a manual trigger will work. But if you want to try, edit installSw.itcl. Look for this line:exec /var/utils/updateroot /dev/hda /install /var/packages >&@ stdoutAnd change it to this:exec /var/utils/updateroot /dev/hda /install /var/packages $name >&@ stdoutThen run:/tvbin/installSw.itcl 6.3-01-2-357And you're off and running. It'll reboot at the end.

Killhdinitrd won't work. You need to replace the kernel. Ideally use a 7.2.2-oth-K1 killhdinitrd'd kernel (available on the ptvupgrade $5 boot CD), but if you don't have one you can use a 3.1.5 kernel so long as DHCP isn't a requirement.

Using the check4slices, mine shows the 6.3 are ready to be installed. I have tried doing the manual trigger, but can't get it to work. I run the modified InstallSw.itcl and get this:

OfficeTivo-TiVo# /tvbin/installSw.itcl 6.3-01-2-357
/tvbin/installSw.itcl: /tv/Inc.itcl: No such file or directory
/tvbin/installSw.itcl: tvsource: command not found
/tvbin/installSw.itcl: tvsource: command not found
/tvbin/installSw.itcl: tvsource: command not found
/tvbin/installSw.itcl: namespace: command not found
/tvbin/installSw.itcl: class: command not found
/tvbin/installSw.itcl: method: command not found
/tvbin/installSw.itcl: method: command not found
/tvbin/installSw.itcl: method: command not found
/tvbin/installSw.itcl: private: command not found
/tvbin/installSw.itcl: private: command not found
/tvbin/installSw.itcl: private: command not found
/tvbin/installSw.itcl: private: command not found
/tvbin/installSw.itcl: line 31: syntax error near unexpected token `}'
/tvbin/installSw.itcl: line 31: `}'

[nc88keyz]

just for ^&*@ts and giggles run the check for slices script on a 6.2 SD dtivo.

6.3 slices have arrived and are ready to install!!!



On a more serious note, why do i get the following

out2osd binary could not be found

yes i have NCID installed, yes i selected yes to all options on the zipper involving caller id.

out2osd is found in several locations as well

any takers?

[bxs122]

So is anyone having luck with the latest Slicer?

From the thread thus far it does not appear so.

Instead of tryng the Slicer I think I just want my Tivo to install the update thus losing my zipper install...I'll put the Zipper back when it is updated for 6.3.

What is the best way to approach an update that will not render my Tivo Deactivated from DirecTV?

[aaronwt]

Mine said account closed until I went through the setup process again. I used slicer to install 6.3 on my three HDTiVos. They are working fine with 6.3 just the PTVnet hacks are not working now or they need to be activated and I'm not sure how to do that even though I can gain access with a serial conection.

[Brillian1080p]

I'm terrible at acronyms, what is Dl'd?

[gsr]

I'm terrible at acronyms, what is Dl'd?

downloaded

[rbautch]

Mine said account closed until I went through the setup process again. I used slicer to install 6.3 on my three HDTiVos. They are working fine with 6.3 just the PTVnet hacks are not working now or they need to be activated and I'm not sure how to do that even though I can gain access with a serial conection.What hacks aren't working? Are you getting errors?

[cheer]

I run the modified InstallSw.itcl and get this:

OfficeTivo-TiVo# /tvbin/installSw.itcl 6.3-01-2-357
/tvbin/installSw.itcl: /tv/Inc.itcl: No such file or directory
/tvbin/installSw.itcl: tvsource: command not found
/tvbin/installSw.itcl: tvsource: command not found
How did you modify installSw.itcl? By any chance did you copy it to your PC and edit it there?

Run dos2unix on it.

[hpfanatic]

I used Joe to edit it. I will try the dos2unix and see if there is any difference.

[Lord Vader]

downloaded

You mean Dl'd doesn't mean "on the down low"? :confused: :D

[samhammer]

The Zipper does not support 6.3 yet. One thing that immediately comes to mind is that 6.3 requires the iptables fix instead of disabling netfilter. That would be the first thing to try.


So if I were to go back and just re install the kernel and not re run Zipper, should it be operational again?

I looked in the log directory but could not find the kernel log. I will look some more.

Sam

[hpfanatic]

How did you modify installSw.itcl? By any chance did you copy it to your PC and edit it there?

Run dos2unix on it.

My editing was the problem. I got the installSw.itcl that was posted earlier and now it is working, updating right now!

[rbautch]

So if I were to go back and just re install the kernel and not re run Zipper, should it be operational again?

I looked in the log directory but could not find the kernel log. I will look some more.

SamKernel + rc.sysinit.author file + modded iptables = hacked tivo. Probably also want to put some tools on there too, like Alphawolf's all-in-one toolset.

[samhammer]

Thanks rbauch

the kernel and author file I know about. Dont know how to do the iptables. Will try a search and see what I can find out.

Sam

[samhammer]

Well I got this from the Kernel log:

First temperature parameters set:
Sep 17 16:38:33 (none) kernel: Terminal temp: 71
Sep 17 16:38:33 (none) kernel: Critical temp: 62
Sep 17 16:38:33 (none) kernel: Logging temp: 60
Sep 17 16:38:33 (none) kernel: Target temp: 50
Sep 17 16:38:33 (none) kernel: Lowest fan speed: 7
Sep 17 16:38:33 (none) kernel: /tvbin/fancontrol is running in the background.
Sep 17 16:38:33 (none) kernel: Starting TvLauncher
Sep 17 16:38:39 (none) kernel: iptables: No chain/target/match by that name
Sep 17 16:38:39 (none) kernel: assert: Tmk Assertion Failure:
Sep 17 16:38:39 (none) kernel: assert: TmkServer, line 379 ()
Sep 17 16:38:39 (none) kernel: Tmk Fatal Error: Activity TvBusProxy <98> strayed!
Sep 17 16:38:39 (none) kernel: Paste the following into a shell to get a backtrace...
Sep 17 16:38:39 (none) kernel:



so it looks like it is the iptables. I have not been able to locate through searching any info on how to correct them though. If anyone can point me to the thread or document that explains the process I would appreciate it.

Thanks
Sam

PS. - Can someone confirm that the problem is the iptables from the past above?

[gazzie4]

I just got emailed a new slicer, anyone know if this one fixes the problems or not. Don't want to try again, as my wife will kill me if I have to format again.

[Lord Vader]

This might be the one that rbautch Emailed to Slicer customers Saturday (yesterday). I got it, too, but didn't do anything with it yet.

[cheer]

PS. - Can someone confirm that the problem is the iptables from the past above?
Yep. Sure is. OK, so in your active root partition, in /sbin there should be a file called iptables. The contents of this file need to be:#!/bin/bash
exit 0If there's an iptables file already there, rename it and create a new one with the above contents. (Note that that is a zero and not an uppercase O.)

Then make sure you make it executable ("chmod 755 iptables").

Finally, make sure you didn't rename /etc/netfilter-enable. At this point you should be good to go.

[gazzie4]

Well I think I am going to give it a go, I am uploading 7.2.2 kernel from ptvupgrade cd to /var/kernel directory and then going to do the update, hopefully this will work.

[tivoupgrade]

Well I think I am going to give it a go, I am uploading 7.2.2 kernel from ptvupgrade cd to /var/kernel directory and then going to do the update, hopefully this will work.

Gazzie - it is the same version.

I think we are close on this one; if another update is required, we'll send it out to everyone, as well.

[samhammer]

Yep. Sure is. OK, so in your active root partition, in /sbin there should be a file called iptables. The contents of this file need to be:#!/bin/bash
exit 0If there's an iptables file already there, rename it and create a new one with the above contents. (Note that that is a zero and not an uppercase O.)

Then make sure you make it executable ("chmod 755 iptables").

Finally, make sure you didn't rename /etc/netfilter-enable. At this point you should be good to go.

Cheer,

Thanks. I am through tonight, but will try that out tomorrow.


Sam

[gazzie4]

I thought my current kernel was 3.1.5?

[bxs122]

This post (http://www.tivocommunity.com/tivo-vb/showthread.php?p=4383363&&#post4383363) leads me to believe that the Slicer is now doing everything it's supposed to. The "account closed" problem has happened to a handful of people, apparently unrelated to the slicer. One guy on DDB fixed it simply by re-detecting the satellites.

Cool ... thanx for the update.

I only very recently zippered my HR10-250 and kept the original drive as a backup. So I'll give Slicer 1.2 a shot and thing go south I can always put the original drive in and hope for another download of 6.3.

[rbautch]

I thought my current kernel was 3.1.5?There are two kernels that will work with 6.3. Once is the 3.1.5 kernel that most everyone had on their hacked HR10-250's before the upgrade. By default, the slicer copies this kernel over to the new kernel partition when making the upgrade, unless you stick a new kernel in the /var/kernel directory. A limitation of the 3.1.5 kernel is that DHCP does not work once you're using 6.3 software. A 7.2.2 kernel with also work with 6.3, and also fixes the DHCP issue. Unless you're using DHCP, there's not much reason to use one or the other.

[HSaid]

I noticed that I got the new software 6.3. I have my bootpage set to softwareupgrade=false. I have 2 questions

1) How do I know if activation code has been sent to my machine?
2) If I set softwareupgrade=true, and if the software has been activated will the new release overaly all 'hacks'?, does it overlay PTVupgrade changes, e.g. change author file?

[gazzie4]

I currently use DHCP, but wasn't sure if there was any other reason to use the 7.2.2. I am having problems ftp'ing it to my tivo anyway. will try to ftp again tonight and then send the slicer over for the update.

[rbautch]

I noticed that I got the new software 6.3. I have my bootpage set to softwareupgrade=false. I have 2 questions

1) How do I know if activation code has been sent to my machine?
2) If I set softwareupgrade=true, and if the software has been activated will the new release overaly all 'hacks'?, does it overlay PTVupgrade changes, e.g. change author file?Not sure about the activation code, but if you change upgradesoftware to true, all you hacks will be overwritten and you'll have a stock tivo.

[NickCat]

I'm bummed now because I had the slices used the 1.1 version of slicer and hosed my tivo, started over with my virgin 3.1.5f image and now I'm waiting for the slices again.

I got the slices on both of my machines after just one daily call on each.

I wonder though if I already got my slices if it won't send them again because it thinks I still have them.

[jasch]

It doesn't matter how many calls you 'force'. The slices do not come through the phone line. They are dowloaded from the satellite and activated when your Tivo does the phone call.

[NickCat]

It doesn't matter how many calls you 'force'. The slices do not come through the phone line. They are dowloaded from the satellite and activated when your Tivo does the phone call.

So it's really just conincidence that I had no 6.3 slices, made a the daily call on one machine, got the 6.3 slices that night. Checked the other machine, no 6.3 slices, made the daily call, had the slices the next night again. Keep in mind that I also had no 6.2 slices on either machine, so after I made a real daily call, using fakecall on both, both machines got 6.3.

Seems a bit too coincidental to not have some bearing on it.

I'm thinking I was in the queue to get the slices, but until I made my daily call to trigger that I was still alive and they should send them.

[rrr22777]

Does PTVnet add entries in the .author file to allow serial bash access?

[rbautch]

So it's really just conincidence that I had no 6.3 slices, made a the daily call on one machine, got the 6.3 slices that night. Checked the other machine, no 6.3 slices, made the daily call, had the slices the next night again. Keep in mind that I also had no 6.2 slices on either machine, so after I made a real daily call, using fakecall on both, both machines got 6.3.

Seems a bit too coincidental to not have some bearing on it.

I'm thinking I was in the queue to get the slices, but until I made my daily call to trigger that I was still alive and they should send them.I can corroborate this coincidence. I had no slices on one of my HR10-250's, forced a call last night over my network (I dont have a phone line), and had the slices this morning.

[bxs122]

I can corroborate this coincidence. I had no slices on one of my HR10-250's, forced a call last night over my network (I dont have a phone line), and had the slices this morning.

It is starting to sound like a little more than a coincident.

I am still waiting for the slices to arrive.

If I have a zippered drive what would be the best way to force a call? I have a phone line connected for caller ID and so my guess is fakecall is capturing any real call attempts. I also have a network connection so is there a way to force a call over the internet (i thought I read somewhere about a 400 prefix or something)?

[rbautch]

It is starting to sound like a little more than a coincident.

I am still waiting for the slices to arrive.

If I have a zippered drive what would be the best way to force a call? I have a phone line connected for caller ID and so my guess is fakecall is capturing any real call attempts. I also have a network connection so is there a way to force a call over the internet (i thought I read somewhere about a 400 prefix or something)?Here (http://www.tivocommunity.com/tivo-vb/showthread.php?p=4386229#post4386229) is how to force a call over your network.

[NickCat]

I can corroborate this coincidence. I had no slices on one of my HR10-250's, forced a call last night over my network (I dont have a phone line), and had the slices this morning.

Always good to know I'm not crazy. :)

The same thing action/reaction happening on my two boxes just seemed to coincidental to ignore.

I've made my first sucessful network call in today, so we'll see if I get the slices on my freshly rebuilt 3.1.5f box tomorrow.

And just to clarify what you said in your first post rbautch, the new 1.2 version of slicer is working properly to retain hacks and network connectivity? I'm a little gunshy at this point, after my weekend experience with 1.1, to pull the trigger on my second box still running 3.1.5f with the 6.3 slices on it.

[gazzie4]

has anyone used slicer 1.12 and if you did, did it work with keeping telnet, ftp?

[tnedator]

Ok. A question. I have zipper installed with the fake call turned on. If I initiate a regular call or network call to see if that results in the new software, will it automatically be installed, or is the noupdate flag still set and will the slice be there, but not be installed.

I am still a bit confused about this aspect of the upgrade.

[rbautch]

Ok. A question. I have zipper installed with the fake call turned on. If I initiate a regular call or network call to see if that results in the new software, will it automatically be installed, or is the noupdate flag still set and will the slice be there, but not be installed.

I am still a bit confused about this aspect of the upgrade.The Zipper sets your upgradesoftware bootpage parameter equal to false, so you'll get the software, but it won't be installed. Read the first post of this thread again to see if that makes sense to you.

[rbautch]

has anyone used slicer 1.12 and if you did, did it work with keeping telnet, ftp?No such thing as v.1.12. I used v.1.2 this morning and it worked great. Preserved telnet and ftp just fine.

[Draven X. Byrne]

No such thing as v.1.12. I used v.1.2 this morning and it worked great. Preserved telnet and ftp just fine.

RBautch -

did it work with backported drivers though ie. ASOHOUS Airlink?

Thanks

[Lord Vader]

No such thing as v.1.12. I used v.1.2 this morning and it worked great. Preserved telnet and ftp just fine.

Russ, did you use it on an HR10-250 that was hacked via Zipper or hacked via another method? Just curious, that's all. :)

[tnedator]

The Zipper sets your upgradesoftware bootpage parameter equal to false, so you'll get the software, but it won't be installed. Read the first post of this thread again to see if that makes sense to you.

Sorry, I missed the link to the post on forcing a call. However I posted here (http://www.tivocommunity.com/tivo-vb/showthread.php?p=4387230&&#post4387230) a question asking how to actually edit the file with the boardupdate paramater.

Also, that forces a call via the net, is it possible to just call via phone, or is the net preferable?

[rbautch]

Russ, did you use it on an HR10-250 that was hacked via Zipper or hacked via another method? Just curious, that's all. :)Zippered, of course. Are there other methods? ;)

[Lord Vader]

That's what I thought, but with all these posts about Slicer 'round here, I wanted to make sure. ;)

[gazzie4]

sorry rbautch, I did mean 1.2 my finger slipped when typing. Did you use the 3.1.5 kernel or the 7.2.2?

[rbautch]

RBautch -

did it work with backported drivers though ie. ASOHOUS Airlink?

ThanksIt should work, but the Slicer doesn't copy backported drivers over so you'll have to copy those over yourself before rebooting. You'll also need to edit the usb.map file to include your driver. Note that the drivers and usb.map are in a different directory than they were on 3.1.5f.

[rbautch]

sorry rbautch, I did mean 1.2 my finger slipped when typing. Did you use the 3.1.5 kernel or the 7.2.2?3.1.5

[JDAWG11]

I have a zippered hr10 and I am trying to make a daily call over the phone line. I keep getting an error during negotiation. Anyone know why this could be? TIA

[Lord Vader]

Have a lot of people NOT received 6.3 yet? I was just wondering how many here haven't. I have not, but I'm not nearly as impatient as others. ;)

[cheer]

I have a zippered hr10 and I am trying to make a daily call over the phone line. I keep getting an error during negotiation. Anyone know why this could be? TIA
Did you remove the route statements from rc.sysinit.author?

[kcmike]

Have a lot of people NOT received 6.3 yet? I was just wondering how many here haven't. I have not, but I'm not nearly as impatient as others. ;)

I am still waiting for my 6.3 slices...

[Lord Vader]

OK, just wondering. Neither I nor my father have received them, but as I said, I'm really not in any rush.

[slydog75]

I"ve not recieved them yet either and based off of rbautch's earlier post, there may be a link between recieving the slices and making a daily call.. I'm going to hopefully test that theory out tonight.

[Lord Vader]

Well, I would imagine Zippered units, even though they don't really make a call per se, would still be able to get the updates automatically like others anyway. Of course, they ARE rolling out the upgrade through October 4th, from what Earl said, so that gives folks another 2 1/2 weeks or so.

[JDAWG11]

Did you remove the route statements from rc.sysinit.author?

Do you have a link that would give a detailed description on this, or is it pretty easy. I'm not a noob, I just don't have a lot of time on my hands. Thanks.

[cheer]

Do you have a link that would give a detailed description on this, or is it pretty easy. I'm not a noob, I just don't have a lot of time on my hands. Thanks.
In your rc.sysinit.author file there are probably a couple of route statements. Delete them.

Sadly, you're on your own if you need more detailed instructions, as (though this may surprise you) I don't have a lot of time on my hands, either.

[JDAWG11]

Thanks guys.

[rrr22777]

Do you have a link that would give a detailed description on this, or is it pretty easy. I'm not a noob, I just don't have a lot of time on my hands. Thanks.

This is an actual upgrade with comments from a post on DDB

[ryan@roundel ~]$ telnet tivo
Trying 192.168.1.101...
Connected to hdtivo (192.168.1.101).
Escape character is '^]'.
bash-2.02# bootpage -p
No device name given, assuming /dev/hda
root=/dev/hda4 brev=0x100A
bash-2.02# nano -w /tvbin/installSw.itcl
[Edit line 86: "exec /var/utils/updateroot /dev/hda /install /var/packages >&@ stdout" to be
"exec /var/utils/updateroot /dev/hda /install /var/packages $name >&@ stdout"]
[Edit line 92: "reboot" comment it out
"# reboot"]
bash-2.02# installSw.itcl 6.3-01-2-357
09/17:15:36:44: /tvbin/installSw.itcl: id of /SwSystem/ACTIVE is 44090086
09/17:15:36:44: /tvbin/installSw.itcl: id of /SwSystem/6.3-01-2-357 is 78227711
09/17:15:36:44: /tvbin/installSw.itcl: Installing "6.3-01-2-357".
09/17:15:36:45: /tvbin/installSw.itcl: Removing old package files
09/17:15:36:45: /tvbin/installSw.itcl: Getting packages from database
09/17:15:36:59: /tvbin/installSw.itcl: Executing jpm install of utils-1-1.cpio
09/17:15:37:01: /tvbin/installSw.itcl: Executing updateroot /dev/hda /install /var/packages
Path prefix is /var/utils/
Sha1hash passed for updatekernel
Sha1hash passed for checkkernel.tcl
Sha1hash passed for messagelib.tcl
Sha1hash passed for buildskeleton
Sha1hash passed for SwInstall.tcl
Sha1hash passed for builddev

Searching /etc/fstab for current root

Old root is on /dev/hda4, new one goes on /dev/hda7

Creating new filesystem on /dev/hda7

Mounting new root filesystem on /install

Installing module core
Installing module hpk-Series2
Installing module kernel-Series2
Building basic filesystem skeleton on /install


Checking /install/etc/fstab

newroot is 7, copying fstab from fstab.alternate
Creating symlinks for /install/etc files
Dismounting /install and checking its integrity


Initializing First Activation Date


Modifying bootparams to point to /dev/hda7

Creating upgrade messages
upgrade_721_mb.msg does not apply to 357
upgrade_721_ptcm.msg does not apply to 357
Flipping root, setting boot parameters to 'root=/dev/hda7 brev=0x100A '

OK, reboot the system to use the new root filesystem

09/17:15:39:20: /tvbin/installSw.itcl: Attempting reboot...
bash-2.02# bootpage -p
No device name given, assuming /dev/hda
root=/dev/hda7 brev=0x100A
bash-2.02# dd if=/dev/hda3 of=/dev/hda6 bs=1024k
2+0 records in
2+0 records out
bash-2.02# mount -o remount,rw /
bash-2.02# cd /
bash-2.02# mount /dev/hda7 /mnt/
bash-2.02# cd mnt/
bash-2.02# cp /etc/rc.d/rc.sysinit.* /mnt/etc/rc.d/
bash-2.02# mv /mnt/sbin/dhclient /mnt/sbin/dhclient.orig
bash-2.02# cd /mnt/sbin/
bash-2.02# mv iptables iptables.old
bash-2.02# echo -e '#!/bin/bash\nexit 0' > iptables; chmod 755 iptables
bash-2.02# cp /.profile /mnt/
bash-2.02# nano -w /mnt/etc/rc.d/rc.sysinit.author
[Comment out insmod statements]
[Add netconfig script (Useage is: netconfig.tcl <static_ip> <subnet_mask> <gateway> <dns>), this is the line I used:
/var/hack/bin/netconfig.tcl 192.168.1.101 255.255.255.0 192.168.1.1 192.168.1.1]
bash-2.02# cd /tvbin
bash-2.02# mv tivoapp tivoapp_6.3_orig
bash-2.02# cp tivoapp_6.3_orig tivoapp
bash-2.02# chmod 755 tivoapp
bash-2.02# echo -ne "\x10\x40\x00\x2b" | dd conv=notrunc of=tivoapp bs=1 seek=6713192; #[30 Second Skip]
2+0 records in
2+0 records out
bash-2.02# echo -ne "\x24\x10\x00\x01" | dd conv=notrunc of=tivoapp bs=1 seek=2804900; #[Enable backdoors]
2+0 records in
2+0 records out
bash-2.02# echo -ne "\x3C\x02\x00\x00" | dd conv=notrunc of=tivoapp bs=1 seek=1602412; #[Disable Encryption]
2+0 records in
2+0 records out
bash-2.02# cd
bash-2.02# umount /mnt/
bash-2.02# sync
bash-2.02# mount -o remount,ro /
bash-2.02# reboot
[After it starts up, physically reboot it again so the Tivo will use the network settings inserted in the MFS via the netconfig.tcl script]

[tnedator]

Can you connect via serial cable with a serial cable and a USB to serial adapter, or do you have to make a cable going from the 1/8" plug to DB9?

It would be much easier to use a null modem cable and a usb to serial adapter if it will work.

[rbautch]

Do you have a link that would give a detailed description on this, or is it pretty easy. I'm not a noob, I just don't have a lot of time on my hands. Thanks.The original post of this thread details the exact lines that need to be deleted. Beyond that, editing a text file is something you can easily do with a little searching.

[rbautch]

Can you connect via serial cable with a serial cable and a USB to serial adapter, or do you have to make a cable going from the 1/8" plug to DB9?

It would be much easier to use a null modem cable and a usb to serial adapter if it will work.That's how I do it. My laptop does not have a serial port, and my PC and monitor are difficult to lug around from tivo to tivo.

[gazzie4]

I must have done something wrong... I am getting the following error when trying to run the new slicer:

bash-2.02# ./slicer 6.3-01-2-357
bash: ./slicer: No such file or directory

I am in the var/tmp directory and that is where I put the slicer

[MisterEd]

FWIW: http://www.tivocommunity.com/tivo-vb/showthread.php?t=317345

[gazzie4]

should that affect people who alread have the download in their system?

[MisterEd]

If you already have it (and have NOT installed it) I would assume it would just overwrite it. should that affect people who alread have the download in their system?

[rbautch]

I must have done something wrong... I am getting the following error when trying to run the new slicer:

bash-2.02# ./slicer 6.3-01-2-357
bash: ./slicer: No such file or directory

I am in the var/tmp directory and that is where I put the slicerTry FTPing it again, maybe to another directory. Make sure you're in binary mode.

[madgrizzle]

Can you connect via serial cable with a serial cable and a USB to serial adapter, or do you have to make a cable going from the 1/8" plug to DB9?

It would be much easier to use a null modem cable and a usb to serial adapter if it will work.

If you are suggesting putting the USB to serial adapter on the HR10, that's not going to work. Serial access is only available through the serial port and you need the 1/8" plug to get to it. It's not really that hard to make a cable. I made one using by snipping ends off of old, obsolete parts and twisting the wires together. I did have to use a cheap ohmmeter to trace the pinout of the phono plug and DB9, but overall it was rather simple. Surprised me that it actually worked at 115.2Kbps though :)

[gazzie4]

erased and then ftp'd again (using binary) and got this instead

bash-2.02# ./slicer 6.3-01-2-357
bash: ./slicer: Permission denied

[mkbruce]

erased and then ftp'd again (using binary) and got this instead

bash-2.02# ./slicer 6.3-01-2-357
bash: ./slicer: Permission denied


Try

chmod u+x ./slicer

[gazzie4]

bash-2.02# chmod u+x ./slicer 6.3-01-2-357
chmod: ./slicer: Read-only file system
chmod: 6.3-01-2-357: No such file or directory
bash-2.02#
bash-2.02# rootwrite
making root filesystem writable; type 'rootread' to make read-only...

executing mount -o remount,rw /

done!
bash-2.02#
bash-2.02# chmod u+x ./slicer 6.3-01-2-357
chmod: 6.3-01-2-357: No such file or directory
bash-2.02#
bash-2.02# rootread
making root filesystem read-only; type 'rootwrite' to make writable..

executing mount -o remount,ro /

done!

[boody]

There are two kernels that will work with 6.3. Once is the 3.1.5 kernel that most everyone had on their hacked HR10-250's before the upgrade. By default, the slicer copies this kernel over to the new kernel partition when making the upgrade, unless you stick a new kernel in the /var/kernel directory. A limitation of the 3.1.5 kernel is that DHCP does not work once you're using 6.3 software. A 7.2.2 kernel with also work with 6.3, and also fixes the DHCP issue. Unless you're using DHCP, there's not much reason to use one or the other.

Trying to cut to the chase here, please confirm my understanding:
Status: I have a manually hacked HR10 running a 2.4.20 kernel from PTV (no cake, no zipper). I want to let it update to 6.3 naturally, keep my recordings and manually re-hack to the current state. I prefer not to run elaborate scripts that do all kinds of things to my TiVo, regardless of how customizable they are (no offense to the talented people who wrote them)- I'm a bit of a purist and I want to know exactly what I'm doing to my TiVo and why. So, to do this (please confirm):

1. I can dd in the PTV killinitrd'd image 7.2.2 and 6.3 will (still) run
2. these modules (included with 6.3?) will still work (usb ethernet will still function):
insmod /lib/modules/usbcore.o
insmod /lib/modules/ehci-hcd.o
insmod /lib/modules/ax8817x.o
3. I can assign a static IP in rc.sysinit.author and it will work
4. fakecall will work, or DEBUG_BOARD=true will allow network calls
5. What won't work is any hack I made to tivoapp which has yet to be re-hacked

Am I missing anything major? I guess what I'm really asking is what a manual hacking of a current tivo looks like today (w/o zipper or cake).

Lastly, given the rollout freeze, doesn't holding off on doing anything make the most sense in case yet another version of 6.3 comes down in the coming weeks rendering all work suggested above moot (once allowed to reboot/upgrade naturally).

[mkbruce]

bash-2.02# chmod u+x ./slicer 6.3-01-2-357
chmod: ./slicer: Read-only file system
chmod: 6.3-01-2-357: No such file or directory
bash-2.02#
bash-2.02# rootwrite
making root filesystem writable; type 'rootread' to make read-only...

executing mount -o remount,rw /

done!
bash-2.02#
bash-2.02# chmod u+x ./slicer 6.3-01-2-357
chmod: 6.3-01-2-357: No such file or directory
bash-2.02#
bash-2.02# rootread
making root filesystem read-only; type 'rootwrite' to make writable..

executing mount -o remount,ro /

done!

Given the output above, you should have done the following:

rootwrite

chmod u+x ./slicer

rootread

./slicer 6.3-01-2-357



chmod changes the permissions on the named file. In this case, u+x adds excecution privileges (i.e. makes it so you can run the script).

[tnedator]

If you are suggesting putting the USB to serial adapter on the HR10, that's not going to work. Serial access is only available through the serial port and you need the 1/8" plug to get to it. It's not really that hard to make a cable. I made one using by snipping ends off of old, obsolete parts and twisting the wires together. I did have to use a cheap ohmmeter to trace the pinout of the phono plug and DB9, but overall it was rather simple. Surprised me that it actually worked at 115.2Kbps though :)

Once you have the cable (I found a 1/8" to serial cable from my scanner), how exactly do you connect. It seems I have read you are supposed to reboot and then hit enter within 10 seconds, but I never get a bash. I can't be 100% sure that the pinout on this cable is the same, but I am also not sure if I am attempting to connect properly.

[Runch Machine]

Did the Caller ID function still work after the slicer finished or did you have to do something additional to get Caller ID to continue to work. What about Fake Call?

[rbautch]

bash-2.02# chmod u+x ./slicer 6.3-01-2-357
chmod: ./slicer: Read-only file system
chmod: 6.3-01-2-357: No such file or directory
bash-2.02#
bash-2.02# rootwrite
making root filesystem writable; type 'rootread' to make read-only...

executing mount -o remount,rw /

done!
bash-2.02#
bash-2.02# chmod u+x ./slicer 6.3-01-2-357
chmod: 6.3-01-2-357: No such file or directory
bash-2.02#
bash-2.02# rootread
making root filesystem read-only; type 'rootwrite' to make writable..

executing mount -o remount,ro /

done!
Try this:
mount -o remount,rw /
chmod u+x slicer
./slicer 6.3-01-2-357

If that doesnt work, reboot your tivo and try again.
If still donesnt work, mount your root filesystem read only, then run:
e2fsck -p /dev/hdaX, where X is your root filesystem partition, either 4 or 7.

[Lord Vader]

Did the Caller ID function still work after the slicer finished or did you have to do something additional to get Caller ID to continue to work. What about Fake Call?

Hell, I lost my Caller ID on all my hacked TIVOs, even those not upgraded yet and the Zippered ones, and nothing I've done has been able to bring it back.

[rbautch]

Trying to cut to the chase here, please confirm my understanding:
Status: I have a manually hacked HR10 running a 2.4.20 kernel from PTV (no cake, no zipper). I want to let it update to 6.3 naturally, keep my recordings and manually re-hack to the current state. I prefer not to run elaborate scripts that do all kinds of things to my TiVo, regardless of how customizable they are (no offense to the talented people who wrote them)- I'm a bit of a purist and I want to know exactly what I'm doing to my TiVo and why. So, to do this (please confirm):

1. I can dd in the PTV killinitrd'd image 7.2.2 and 6.3 will (still) run
2. these modules (included with 6.3?) will still work (usb ethernet will still function):
insmod /lib/modules/usbcore.o
insmod /lib/modules/ehci-hcd.o
insmod /lib/modules/ax8817x.o
3. I can assign a static IP in rc.sysinit.author and it will work
4. fakecall will work, or DEBUG_BOARD=true will allow network calls
5. What won't work is any hack I made to tivoapp which has yet to be re-hacked

Am I missing anything major? I guess what I'm really asking is what a manual hacking of a current tivo looks like today (w/o zipper or cake).

Lastly, given the rollout freeze, doesn't holding off on doing anything make the most sense in case yet another version of 6.3 comes down in the coming weeks rendering all work suggested above moot (once allowed to reboot/upgrade naturally).
All correct, except:
- fakecall has to be modified for 6.3 - see DDB for that.
- don't insmod any drivers, since 6.3 loads them automatically
- also (for others tuning in) note that you can only set up network params in the author file if you are using a 7.2.2 kernel.

[hpfanatic]

I"ve not recieved them yet either and based off of rbautch's earlier post, there may be a link between recieving the slices and making a daily call.. I'm going to hopefully test that theory out tonight.

On one of mine I had to force a call before I got the 6.3 slices, then let it update and overwrite my hacks.

On the second one, my main one, I am going to use the slicer on it. I just checked, and before doing anything to the Route statements, and forcing a call, I already have the slices, so they came with no phone call first on it.

Maybe one call from an account is needed before all DTivos on that account get the update?

[gazzie4]

tried all, and this was latest attempt:

bash-2.02#
bash-2.02# e2fsck -p /dev/hda7
/dev/hda7 is mounted. Do you really want to continue (y/n)? yes

/dev/hda7 has reached maximal mount count, check forced.
/dev/hda7: 1141/32768 files (0.9% non-contiguous), 44460/131072 blocks
bash-2.02# ./slicer 6.3-01-2-357
bash: ./slicer: Text file busy
bash-2.02#
bash-2.02# mount -o remount,rw /
bash-2.02#
bash-2.02# chmod u+x slicer
bash-2.02#
bash-2.02# ./slicer 6.3-01-2-357
bash: ./slicer: Text file busy
bash-2.02#

[rbautch]

See here: http://lists.freebsd.org/pipermail/freebsd-current/2003-September/009972.html

It's possible you have another instance of it running somewhere. Type ps to see if you can find another running copy. Also try renaming the file, and run it again.

[bxs122]

Here (http://www.tivocommunity.com/tivo-vb/showthread.php?p=4386229#post4386229) is how to force a call over your network.

1. Add the ,#401 dialing prefix to your phone options.
2. Edit the DEBUG_BOARD variable as shown above. It's on line 532 in case your searching for it with vi.

OK ... gonna give it a try.

In researching I've only found refs to entering ,#401 so I added it and tested and cannot tell if the call actually went thru - the screen seems to be stuck on Connecting (Configuring...)

What vallue do I set DEBUG_BOARD to?
Is the the DEBUG_BOARD variable in the rc.sysinit file? If so then on completing the edit do I reboot the Tivo?

Disregard questsion ... changed DEBUG_BOARD to true, rebooted then added ,#401 and am now testing. So far looks to have gotten further in that I now get a Connecting (Negotiating...) instead of just Connecting (Configuring...)

OK it ended up failing on Connecting (Negotiating...) , I tested three times. What else should I look at to change? I did telnet in and tested echo $DEBUG_BOARD and the value was returned as true.

thanx,

[gazzie4]

rbautch thank you for all your help...I finally got it to work, it looks like the file was getting corrupted during transfer. I tried a bunch of different programs for ftp, but was finally able to get one to work without error, and now my system is rebooting with the upgrades. It would not gunzip the new kernel (7.2.2) over but I guess I can add that later if all works out.

[gazzie4]

well it sort worked. The update took, no errors, however no network at all. and this was with slicer 1.2.

Oh well, I still have serial so hopefully a fix will come out so I can update it with the networking capability.

[mchahn]

I also have 6.3 running after using today's slicer, and I also have no network.

rbautch gave directions on what to do from here on page seven of this thread. I would post a link but the forum won't let me.

I have my serial working and I now want to run lghahn's script to configure the net. My current problem is that I cannot find netconfig.itcl anywhere. I looked through all the tivoweb stuff I have. I searched all the forums here.

Can some PLEASE tell me where to get netconfig?

[mchahn]

Never mind. I found netconfig.tcl over at the ddb forum. Now I have to figure out how to copy a text file to my tivo using hyperterminal. So far, sending text from a file while vi is in insert mode doesn't work, even with delays set for each char. Maybe there is some way to send text over a telnet link directly into a file.

[mchahn]

I copied netconfig.tcl over (after using cat > filename {duh}) and got this crash when I ran it:

------------------------------

bash-2.02# ./netconfig.tcl 192.168.1.52 255.255.255.0 192.168.1.1 192.168.1.1
86 0 1308 S /tvbin/AtscTu
assert: Tmk Assertion Failure:, portstatus 100, change 0, 12
assert: FsAllocateFunction, line 203 ()cTunerD
Tmk Fatal Error: Thread tivosh <2311> strayed!
ApgLogFrequency( 0 sec )
Paste the following into a shell to get a backtrace...i semaphore
tcd 1
hpk Series2
read 0x00400000 /tvbin/tivoapp
read 0x02000000 /lib/libc.so.6
read 0x02200000 /lib/libm.so.6
read 0x02400000 /lib/libpthread.so.0
read 0x02600000 /lib/libutil.so.1
read 0x02800000 /lib/libtvutil.so
read 0x02a00000 /lib/libtmk.so
read 0x02c00000 /lib/libtvstructures.so
read 0x2aaa8000 /lib/ld.so.1
read 0x2ab04000 /lib/libhpkoss.so
read 0x2ab50000 /platform/lib/libhpkhl.so
read 0x2ac18000 /platform/lib/libhpkll.so
read 0x2ac5c000 /lib/libdl.so.2
read 0x2aca0000 /lib/libcdaudio.so
0x02a7ea98 0x006af23c 0x02a4a878 0x02a4cc40 0x02a5a9b4 0x02a59964 0x00ced218
0x00cecedc 0x0074bef4 0x006e0274 0x0201455c
END_OF_BT

Tmk Fatal Error: Thread tivosh <2311>: assertion failure
flushing ide devices: hda hdb
Restarting system.

-----------------

I was using the netconfig that contained this header:

# Network Config 1.0 by l.g. kahn to get around the problem
# that dtivo v. 6.2 has no network menus.

Can someone give me a clue as to where to go from here?

[mchahn]

I am still not working, but I've discovered a few interesting things:

1) Slicer left a syntax error in rc.sysinit.author. It was apparently this code because removing it fixed it:

if [ -f /init/ptv_flags/STATIC_ON ]; then
fi

2) Slicer already ran an equivalent to netconfig.tcl. This was at the end of rc.sysinit.author:

if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
tivosh /hacks/network.tcl 192.168.1.52 192.168.1.1
mount -o remount,ro /
fi
fi

This didn't run on slicer's first reboot since the file had the syntas error. I tried running network.tcl and got similar results to what I got from netconfig.tcl:

bash-2.02# tivosh /hacks/network.tcl 192.168.1.52 192.168.1.1
assert: Tmk Assertion Failure:
assert: FsAllocateFunction, line 203 ()
Tmk Fatal Error: Thread tivosh <480> strayed!
Paste the following into a shell to get a backtrace...

bt -t /tvbin/tivoapp <<END_OF_BT
tcd 1
hpk Series2
read 0x00400000 /tvbin/tivoapp
read 0x02000000 /lib/libc.so.6
read 0x02200000 /lib/libm.so.6
read 0x02400000 /lib/libpthread.so.0
read 0x02600000 /lib/libutil.so.1
read 0x02800000 /lib/libtvutil.so
read 0x02a00000 /lib/libtmk.so
read 0x02c00000 /lib/libtvstructures.so
read 0x2aaa8000 /lib/ld.so.1
read 0x2ab04000 /lib/libhpkoss.so
read 0x2ab50000 /platform/lib/libhpkhl.so
read 0x2ac18000 /platform/lib/libhpkll.so
read 0x2ac5c000 /lib/libdl.so.2
read 0x2aca0000 /lib/libcdaudio.so
0x02a7ea98 0x006af23c 0x02a4a878 0x02a4cc40 0x02a5a9b4 0x02a59964 0x00ced218
0x00cecedc 0x0074bef4 0x006e0274 0x0201455c
END_OF_BT

Tmk Fatal Error: Thread tivosh <480>: assertion failure
flushing ide devices: hda hdb
Restarting system.

So I think my ip setup has never gotten to mfs, although I don't know how to check this.

[agzela]

http://www.tivocommunity.com/tivo-vb/showthread.php?t=317345&page=2&pp=30

[mchahn]

Apparently network.tcl and netconfig.tcl need to run during boot. I patched rc.sysinit.author to run network.tcl without the first_boot flag, rebooted, restored rc.sysinit.author, rebooted, and now I have a network connection and my hacks are working.

Apparently slicer is not quite ready for prime-time.

[bxs122]

1. Add the ,#401 dialing prefix to your phone options.
2. Edit the DEBUG_BOARD variable as shown above. It's on line 532 in case your searching for it with vi.


Well after rbautch excellent help I was successful in forcing a call out of my HR10-250. Sure enough there was about ten minutes of downloading and this morning I saw that the 6.3 slices had arrived.

Now the big question is, does the latest slicer work or should I follow one of the original options that would install 6.3 but lose my TivoWeb etc.

thanx,

[NickCat]

Just to add more proof to the "my you have to dial in to trigger the 6.3 slice download" theory. As theorized earlier in this thread, I got the 6.3 slices last night after my first forced call on my newly rebuilt 3.1.5f machine. (After it had already happened once on this same machine (pre-slicer incident), and once on my other machine)

I guess I'll just wait and see about upgrading though with this halt on the 6.3 rollout.

Stupid Question: Do I care about the 72.5 or 95 satellite issues? I have a triple LNB oval dish and I subscribe to Total Choice Premier and obviously get HD channels, but all my locals are OTA. Does this satellite issue with the 6.3 slice affect me at all?

[100Tbps]

Just to add more proof to the "my you have to dial in to trigger the 6.3 slice download" theory. As theorized earlier in this thread, I got the 6.3 slices last night after my first forced call on my newly rebuilt 3.1.5f machine. (After it had already happened once on this same machine (pre-slicer incident), and once on my other machine)

I guess I'll just wait and see about upgrading though with this halt on the 6.3 rollout.

Stupid Question: Do I care about the 72.5 or 95 satellite issues? I have a triple LNB oval dish and I subscribe to Total Choice Premier and obviously get HD channels, but all my locals are OTA. Does this satellite issue with the 6.3 slice affect me at all?

Same here - I did the call over ethernet last night and have the slices today.

I believe those satellites carry international channels and there's a thread explaining whatever else is going on there - I read it and stopped when I realized it didn't affect me but it seemed pretty detailed.

At this point, I'm willing to go ahead and slice it up, but I sure would like to see someone post to say slicer 1.2 not only upgrades the system, but retains networking (I have a Linksys USB200M - not wireless), retains fakecall even though now I guess I don't care, keeps the callerid pop-up, etc. And even then, is there something else that must be done in conjunction or ahead of time to get slicer to do all of this.

Lastly, is there something I can do to extract these slices to get them over to ptvupgrade or whoever else may need them? I saw some posts on this earlier but have yet to see anyone post explicit instructions on what to do or how to do it. I'm happy to help if I can.

[mkbruce]

Just to add more proof to the "my you have to dial in to trigger the 6.3 slice download" theory. As theorized earlier in this thread, I got the 6.3 slices last night after my first forced call on my newly rebuilt 3.1.5f machine. (After it had already happened once on this same machine (pre-slicer incident), and once on my other machine)

I guess I'll just wait and see about upgrading though with this halt on the 6.3 rollout.

Stupid Question: Do I care about the 72.5 or 95 satellite issues? I have a triple LNB oval dish and I subscribe to Total Choice Premier and obviously get HD channels, but all my locals are OTA. Does this satellite issue with the 6.3 slice affect me at all?

One more data point:

I forced a daily call (via phone after disabling the route statements in rc.sysinit.author and rebooting) on both my HR-10's yesterday. This morning, both had the slices. Coincidence?????

[cheer]

One more data point:

I forced a daily call (via phone after disabling the route statements in rc.sysinit.author and rebooting) on both my HR-10's yesterday. This morning, both had the slices. Coincidence?????
I never made a call, and I had the slices the first day.

[RockyL]

One more data point:

I forced a daily call (via phone after disabling the route statements in rc.sysinit.author and rebooting) on both my HR-10's yesterday. This morning, both had the slices. Coincidence?????


Well, I did the same thing yesterday on both of my boxes. This morning I had the slices on one, but not the other. At least this does confirm that DirecTV/TiVo has not halted the downloading of slices. Apparently they only halted the software installation process...

[gazzie4]

Apparently network.tcl and netconfig.tcl need to run during boot. I patched rc.sysinit.author to run network.tcl without the first_boot flag, rebooted, restored rc.sysinit.author, rebooted, and now I have a network connection and my hacks are working.

Apparently slicer is not quite ready for prime-time.
mchahn, can you give a little more detail on your exact steps to getting back internet. I am still a little new at all this stuff, and would like to get my network back.

Thanks

[muzzymate]

Well I just used the Slicer, purchased yesterday (so I presume I got 1.2), and lost all my network connectivity. It looks like it's grabbing an IP address but I can't ping, FTP, or telnet into it. Guess I'll have to pull the drive again which was the whole reason I purchased in to begin with. I had previously hacked it with the Zipper.

With news that the 6.3 upgrade is halted, I think I'll just wait until 6.3.1 is released so I don't need to pull the drive a third time. And even then, I'll probably just wait until the Zipper and enhancement scripts have been updated for the new software.

[bxs122]

One more data point:

I forced a daily call (via phone after disabling the route statements in rc.sysinit.author and rebooting) on both my HR-10's yesterday. This morning, both had the slices. Coincidence?????

Too many have noted the same for this to be coincidence.

[bxs122]

Well I just used the Slicer, purchased yesterday (so I presume I got 1.2), and lost all my network connectivity. It looks like it's grabbing an IP address but I can't ping, FTP, or telnet into it. Guess I'll have to pull the drive again which was the whole reason I purchased in to begin with. I had previously hacked it with the Zipper.

With news that the 6.3 upgrade is halted, I think I'll just wait until 6.3.1 is released so I don't need to pull the drive a third time. And even then, I'll probably just wait until the Zipper and enhancement scripts have been updated for the new software.

Bummer to hear slicer 1.2 did not work on your machine.

What do you mean 6.3 upgrade is halted?

[rbitting]

I got the 6.3 upgrade last night. Yesterday afternoon I used the ,#401 and modify the rc.sysinit and forced a call and then last night the 6.3 slices appeared on the unit. So I do think the call is necessary. I hope a new version of the slicer comes out that works without losing the network. So since I got the slices last night I doubt the upgrade is halted. I'm sure they can tell where the customer is at and whether they would be affected by the 6.3 upgrade.

[Finnstang]

I setup and forced a call over ethernet last night and had 6.3 slices this morning.

[tnedator]

Just to add more proof to the "my you have to dial in to trigger the 6.3 slice download" theory. As theorized earlier in this thread, I got the 6.3 slices last night after my first forced call on my newly rebuilt 3.1.5f machine. (After it had already happened once on this same machine (pre-slicer incident), and once on my other machine)

I guess I'll just wait and see about upgrading though with this halt on the 6.3 rollout.

Stupid Question: Do I care about the 72.5 or 95 satellite issues? I have a triple LNB oval dish and I subscribe to Total Choice Premier and obviously get HD channels, but all my locals are OTA. Does this satellite issue with the 6.3 slice affect me at all?

Ditto. After a fair amount of help from people walking me forcing through a call with ,#401 last night, I checked this morning and I have 6.3-01-2-357 listed.

I am not sure I want to attempt to install it with the halt in place, and I have been unclear of how well the currentl slicer is working.

What exactly is on 72.5 and 95? I believe I am just getting video from 101, 110 and 119.

[muzzymate]

What do you mean 6.3 upgrade is halted?

See here. http://www.tivocommunity.com/tivo-vb/showthread.php?t=317345

[HUGE2U]

6.3 this morning for me too (at least on one of them).



HUGE

EDIT: Is there any wayto tranfer the slices from one HR10 to the other?

[rrr22777]

Ditto. After a fair amount of help from people walking me forcing through a call with ,#401 last night, I checked this morning and I have 6.3-01-2-357 listed.

I am not sure I want to attempt to install it with the halt in place, and I have been unclear of how well the currentl slicer is working.

What exactly is on 72.5 and 95? I believe I am just getting video from 101, 110 and 119.

72.5 has midwest area locals and 95 has international.

[bxs122]

So does anyone know the latest state of Slicer ... is it usable? I have followed the upgrades and belive I have the latest but as most I have reservations about using it.

If it still does not work what will be the worst that can happen - if it is just losing the zipper then I guess there isn't anything to lose going with Slicer vs. the option 1 rbautch posted on the first page.

[Finnstang]

So does anyone know the latest state of Slicer ... is it usable? I have followed the upgrades and belive I have the latest but as most I have reservations about using it.

If it still does not work what will be the worst that can happen - if it is just losing the zipper then I guess there isn't anything to lose going with Slicer vs. the option 1 rbautch posted on the first page.
From what people are saying, everything is still there, but people are still losing network connectivity. You can get it back by using a serial cable to access the TiVo.

[kcmike]

Well after rbautch excellent help I was successful in forcing a call out of my HR10-250. Sure enough there was about ten minutes of downloading and this morning I saw that the 6.3 slices had arrived.

Now the big question is, does the latest slicer work or should I follow one of the original options that would install 6.3 but lose my TivoWeb etc.

thanx,


How did you get it to dial out, I have the same situation you did: failing on Connecting (Negotiating...)

--Mike

[HUGE2U]

So I used l slicer, work (I guess, I mean I am at 6.3) but lost network. The lights on the usb adapter do not even light up. I do have serial access. What's my next step?

HUGE

[hpfanatic]

I took the chance and used the Slicer 1.2, and like alot of others lost my networking. Now to find that serial cable I have somewhere around here...

[Tonedeaf]

How did you get it to dial out, I have the same situation you did: failing on Connecting (Negotiating...)

--Mike
Look HERE (http://www.tivocommunity.com/tivo-vb/showthread.php?t=316272)

and HERE (http://www.tivocommunity.com/tivo-vb/showthread.php?p=4386229#post4386229)

[bxs122]

From what people are saying, everything is still there, but people are still losing network connectivity. You can get it back by using a serial cable to access the TiVo.

As a precaution I built a serial cable over the weekend and tested bash via the serial port...works pretty good.

So if I lost my network then use the serial bash prompt what steps do I make to get my network back? I am a Windows guy and only now learning the Linux side so in explanation there can never be too much detail.

[mchahn]

A lot of you are where I was yesterday. The slicer worked except for no networking. I'll tell you exactly what I did to make it work (leaving out the wrong turns). Your mileage may vary.

1) I built a serial cable, downloaded a decent terminal emulator, and got serial bash working. Contrary to all the other reports mine worked at 9600.

2) I copied /etc/rc.d/rc.sysinit.author over to edit. (I don't know vi well enough to use).

3) I had noticed that there was a syntax error in the file so I found the offending lines and commented them out.

if [ -f /init/ptv_flags/STATIC_ON ]; then
fi

4) I also deleted the comment lines that were added for beginning and end of user section. The first of them made the #!bin/bash line go to the second line, which worried me.

5) The slicer code added to the end of the file looked like this:

## Slicer - run network script only once. Reboot after 20 minutes
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
tivosh /hacks/network.tcl 192.168.1.52 192.168.1.1
mount -o remount,ro /
fi
fi

I edited it to look like this so that it would run on the next reboot:

## Slicer - run network script only once. Reboot after 20 minutes
mount -o remount,rw /
tivosh /hacks/network.tcl 192.168.1.52 192.168.1.1
mount -o remount,ro /

6) I rebooted

7) I re-edited the file to return the slicer code at the end back to what it was.

8) I rebooted again.

Voila! Everything worked.

[HUGE2U]

A lot of you are where I was yesterday. The slicer worked except for no networking. I'll tell you exactly what I did to make it work (leaving out the wrong turns). Your mileage may vary.

1) I built a serial cable, downloaded a decent terminal emulator, and got serial bash working. Contrary to all the other reports mine worked at 9600.

2) I copied /etc/rc.d/rc.sysinit.author over to edit. (I don't know vi well enough to use).

3) I had noticed that there was a syntax error in the file so I found the offending lines and commented them out.

if [ -f /init/ptv_flags/STATIC_ON ]; then
fi

4) I also deleted the comment lines that were added for beginning and end of user section. The first of them made the #!bin/bash line go to the second line, which worried me.

5) The slicer code added to the end of the file looked like this:

## Slicer - run network script only once. Reboot after 20 minutes
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
tivosh /hacks/network.tcl 192.168.1.52 192.168.1.1
mount -o remount,ro /
fi
fi

I edited it to look like this so that it would run on the next reboot:

## Slicer - run network script only once. Reboot after 20 minutes
mount -o remount,rw /
tivosh /hacks/network.tcl 192.168.1.52 192.168.1.1
mount -o remount,ro /

6) I rebooted

7) I re-edited the file to return the slicer code at the end back to what it was.

8) I rebooted again.

Voila! Everything worked.


Where did you get network.tcl?


HUGE

[agzela]

ERROR: Didn't find any device list files in /install/platform/utils/DeviceList/
while executing
"exec tivosh /var/utils//buildskeleton /install"
("eval" body line 1)
invoked from within
"eval exec tivosh $prefix/buildskeleton $installdir"
(file "/var/utils/updateroot" line 147)
while executing
"exec /var/utils/updateroot /dev/hda /install /var/packages"
(object "::inst" method "::Installer::installSoftware" body line 46)
invoked from within
"inst installSoftware $name $Inc::TC_INSTALL_DIR "
(file "./installSw.itcl" line 182)

installSw.itcl failed to set up your new partitions. Please
run /tvbin/installSw.itcl manually to pinpoint the error.
Also check to see if installSw.itcl was edited properly.
Since your bootpage was not flipped, you will not lose your
existing hacks if you reboot, and The Slicer may safely be
run again. Exiting now...

[rbautch]

3) I had noticed that there was a syntax error in the file so I found the offending lines and commented them out.

if [ -f /init/ptv_flags/STATIC_ON ]; then
fi This is my fault. In the code I contributed for the network upgrade, I removed all lines from the author file that start with "ifconfig" or "route add". That leaves this remnant in the author file that causes it to halt, and never finish the network setup. NOTE THAT THIS ONLY AFFECTS PTVNET USERS.


## Slicer - run network script only once. Reboot after 20 minutes
mount -o remount,rw /
tivosh /hacks/network.tcl 192.168.1.52 192.168.1.1
mount -o remount,ro / I suggest not making this change, because it will reset your IP address to this value every time you reboot. The old code makes sure the network script only gets run once.

Bottom line is that if you are a PTVnet user, add an echo statement in the following location in your author file, and the slicer (v.1.2) should run fine:
if [ -f /init/ptv_flags/STATIC_ON ]; then
ifconfig eth0 $STATIC_IP broadcast $BROADCAST netmask $NETMASK
route add default gw $GATEWAY
echo
fi
I'll ask PTVupgrade to make this a permanent patch.

[HUGE2U]

This is my fault. In the code I contributed for the network upgrade, I removed all lines from the author file that start with "ifconfig" or "route add". That leaves this remnant in the author file that causes it to halt, and never finish the network setup. NOTE THAT THIS ONLY AFFECTS PTVNET USERS.

I suggest not making this change, because it will reset your IP address to this value every time you reboot. The old code makes sure the network script only gets run once.

Bottom line is that if you are a PTVnet user, add an echo statement in the following location in your author file, and the slicer (v.1.2) should run fine:
if [ -f /init/ptv_flags/STATIC_ON ]; then
ifconfig eth0 $STATIC_IP broadcast $BROADCAST netmask $NETMASK
route add default gw $GATEWAY
echo
fi
I'll ask PTVupgrade to make this a permanent patch.


So post slicer - and not a PTVnet person, how do I restore network?

HUGE

[tivoupgrade]

If you have the gotomydvr client installed, you'll find that it won't run properly on 6.3 (we are working to fix that).

Three ways to work around it...

Before running 1.2 of The Slicer, if you have a /gotomydvr directory, rename it to something else, OR after running it, rename in the /install directory, OR delete the startup lines from rc.sysinit.author.

More to come.

[tivoupgrade]

Type the following to repair the section of the rc.sysinit.author file Russ was talking about:


rootwrite <enter>
vi /install/etc/rc.d/rc.sysinit.author <enter>
:77 <enter>
o echo <esc>
:x! <enter>
sync ; reboot <enter>

[bxs122]

I'm just about to run Slicer ... does it matter where I run it from?

Is there anything I should do in advance ?

thanx

[Beantownbeanie]

HI
I am buying the slicer when I get home today. Many posts mention FTP'ing it to the Tivo. Is how to do this in the instructions? I know it's File Transfer Protocol and that I am uploading the slicer to my Tivo...I just need the steps. I'm worried I will mess this up and it is premiere week. My other half would have my head but I really want to upgrade. Also my IP address is the fake one behind the firewall. Is this ok. I saw this mentioned in posts too. I am trying to do this on my own but I searched and I didn't see the answers.
I don't care if I lose the network as I can pull a drive easy and use my instant cake (to restart all over) and other cd I bought when this died the first time and I had to replace the hard drive.
I also plan to buy the instant cake upgrade for this 6.3 but just can't wait!!!!
It was so easy and worked the first time. I am hoping this goes as well.
Thanks in advance for your time.

[bxs122]

HI
I am buying the slicer when I get home today. Many posts mention FTP'ing it to the Tivo. Is how to do this in the instructions? I know it's File Transfer Protocol and that I am uploading the slicer to my Tivo...I just need the steps. I'm worried I will mess this up and it is premiere week. My other half would have my head but I really want to upgrade. Also my IP address is the fake one behind the firewall. Is this ok. I saw this mentioned in posts too. I am trying to do this on my own but I searched and I didn't see the answers.
I don't care if I lose the network as I can pull a drive easy and use my instant cake and other cd I bought when this died the first time and I had to replace the hard drive. It was so easy and worked the first time. I am hoping this goes as well.
Thanks in advance for your time.

Easiest utility i FileZilla ... download, install, run, connect to your Tivo then set transfer mode to binary and upload the slicer file to var/tmp

[bxs122]

Well ran the slicer - did not get any errors.

The tivo rebooted and I am now at a DirecTV screen with 'Preparing the service update...This may take up to an hour'

I wasn't expecting that. I thought running slicer did the install.

[Lord Vader]

Let us know if you retained connectivity.

[tivoupgrade]

Type the following to repair the section of the rc.sysinit.author file Russ was talking about:


rootwrite <enter>
vi /install/etc/rc.d/rc.sysinit.author <enter>
:77 <enter>
o echo <esc>
:x! <enter>
sync ; reboot <enter>


and then "reboot" one last time...

[bxs122]

Let us know if you retained connectivity.

CRAP ... no network and no sound. Now what do I do?

Should I try to connect via the serial cable and do the following:

rootwrite <enter>
vi /install/etc/rc.d/rc.sysinit.author <enter>
:77 <enter>
o echo <esc>
:x! <enter>
sync ; reboot <enter>

My tivo is an HR10-250 instantcaked 3.x with zipper, other than that I could tell you anything more about it.

[tivoupgrade]

CRAP ... no network and no sound. Now what do I do?

Should I try to connect via the serial cable and do the following:

rootwrite <enter>
vi /install/etc/rc.d/rc.sysinit.author <enter>
:77 <enter>
o echo <esc>
:x! <enter>
sync ; reboot <enter>

My tivo is an HR10-250 instantcaked 3.x with zipper, other than that I could tell you anything more about it.

that is what you should try to do.

but if you have no sound, that may be a different issue.

also note that i edited my post - you need to do one more reboot for the network settings to take effect.

[Lord Vader]

I wonder if The Slicer will be revised to version 1.3 or something to correct these network problems. I can just see total newbies messing up their TIVOs trying to edit things.

[bxs122]

I got my sound back ... tivo Dolby setting (i think)

Got the serial cable connected and will attempt the script above

I also lost 30 second skip so at this point I don't know what state the tivo is in.



Off the bat rootwrote <enter> failed with not found

moving ahead I think this is same as rw ... but of course rw does not work either.

[tivoupgrade]

I got my sound back ... tivo Dolby setting (i think)

Got the serial cable connected and will attempt the script above

I also lost 30 second skip so at this point I don't know what state the tivo is in.



Off the bat rootwrote <enter> failed with not found

moving ahead I think this is same as rw

its rootwrite... if it failed with not found its because you do not have a PTVnet drive, you can also do a

mount -o remount,rw /

[bxs122]

its rootwrite... if it failed with not found its because you do not have a PTVnet drive, you can also do a

mount -o remount,rw /


I am stuck on the sync ; reboot

How do you do this in vi? or is :x! supposed to exit from vi

OK I am pretty stuck ... when I type :77 and press enter, the prompt just sits there. If I then press 0 as in to start type o echo the screen scrolls with a bunch of ~

At this point I have no idea the state of the file so I do a :q! to quit without saving.

[tivoupgrade]

I am stuck on the sync ; reboot

How do you do this in vi? or is :x! supposed to exit from vi

OK I am pretty stuck ... when I type :77 and press enter, the prompt just sits there. If I then press 0 as in to start type o echo the screen scrolls with a bunch of ~

At this point I have no idea the state of the file so I do a :q! to quit without saving.

:77 --- takes you to the 77th line of the file
o --- puts you into "overwrite mode"
echo --- space echo is just the text to type in
<esc> --- gets you out of overwrite mode
:x! --- writes the file and exits vi

[bxs122]

:77 --- takes you to the 77th line of the file
o --- puts you into "overwrite mode"
echo --- space echo is just the text to type in
<esc> --- gets you out of overwrite mode
:x! --- writes the file and exits vi

thanx for the help ... but whenever I follow exactly as listed above I end up with a screen that looks like

~
~
~
ech

with the cursor blinking where the o is supposed to be.

At that point I just :q! to get out without doing any damage.

What am I missing?


OK got it -- I moved to the install/rc.d folder then types vi rc.sysinit.author and well as you can guess I saw the actual file and was able to follow your instructions. Machine is rebooting now.

Sorry for having been a nudge on the vi stuff.

So how do I get joe back in there...I liked it much more than vi

[rbautch]

I am still not working, but I've discovered a few interesting things:

1) Slicer left a syntax error in rc.sysinit.author. It was apparently this code because removing it fixed it:

if [ -f /init/ptv_flags/STATIC_ON ]; then
fi
These lines need to be deleted for the network script to run. See my post above.



2) I tried running network.tcl and got similar results to what I got from netconfig.tcl:

bash-2.02# tivosh /hacks/network.tcl 192.168.1.52 192.168.1.1
assert: Tmk Assertion Failure:
assert: FsAllocateFunction, line 203 ()
Tmk Fatal Error: Thread tivosh <480> strayed!
Paste the following into a shell to get a backtrace...In order to run a tivosh script, you need to have the following lines in your author file: export TIVO_ROOT=
export MFS_DEVICE=/dev/hda10Add those to your author file, and reboot your tivo, twice. That should bring up the network.

[fatdad1]

Not trying , but in...But if you are serial (all I had many years ago) make sure you have an ansi console (vi being keyboard driven) and that you are rwrite cableable, already covered.

[rbautch]

Well I just used the Slicer, purchased yesterday (so I presume I got 1.2), and lost all my network connectivity. It looks like it's grabbing an IP address but I can't ping, FTP, or telnet into it. Guess I'll have to pull the drive again which was the whole reason I purchased in to begin with. I had previously hacked it with the Zipper.

With news that the 6.3 upgrade is halted, I think I'll just wait until 6.3.1 is released so I don't need to pull the drive a third time. And even then, I'll probably just wait until the Zipper and enhancement scripts have been updated for the new software.Sounds like you didn't reboot after the tivo finished "loading the service update" The reboot is what triggers the network settings to take effect.

[rbautch]

So does anyone know the latest state of Slicer ... is it usable? I have followed the upgrades and belive I have the latest but as most I have reservations about using it.

If it still does not work what will be the worst that can happen - if it is just losing the zipper then I guess there isn't anything to lose going with Slicer vs. the option 1 rbautch posted on the first page. I think the only issue remaining is compatibility with PTVnet users who have a complicated author file. Version 1.2 is still a viable option for PTVnet users - all that's needed is to delete or comment out the following lines from the author file before you start: if [ -f /init/ptv_flags/STATIC_ON ]; then
ifconfig eth0 $STATIC_IP broadcast $BROADCAST netmask $NETMASK
route add default gw $GATEWAY
fi
If you've already run The Slicer and lost networking, the lines in the author file that need deleting look a little different (2 middle lines missing): -f /init/ptv_flags/STATIC_ON ]; then
fi...you'll also need to add these to lines near the top of the author file just below #!/bin/bash:
export TIVO_ROOT=
export MFS_DEVICE=/dev/hda10Note that these steps are not necessary in v1.3 of The Slicer, which addresses these issues.

[rbautch]

Where did you get network.tcl?
HUGEIt is packaged with The Zipper. It gets created on the fly in /hacks when you run The Slicer. If you have PTVnet and lost connectivity, just make the changes in my post above, and then reboot, twice. You can make the changes using a serial cable, OR by mounting the drive in your PC.

[willardcpa]

thanx for the help ... but whenever I follow exactly as listed above I end up with a screen that looks like

~
~
~
ech

with the cursor blinking where the o is supposed to be.

At that point I just :q! to get out without doing any damage.

What am I missing?
I may have the answer for you. Or I might not. :D
Looking at your previous posts looks like you used the zipper. Lou's instructions are written from his persepctive - using PTVnet. I think the~~~ are caused because your are using Lou's "vi /install/etc/rc.d/rc.sysinit.author <enter>" If you used the zipper I don't think that it has the word "install" on any files in it. So I think you are trying to modify a file that doesn't exist. If you look at Russ's previous post on this he says "Bottom line is that if you are a PTVnet user, add an echo statement in the following location in your author file, and the slicer (v.1.2) should run fine:
if [ -f /init/ptv_flags/STATIC_ON ]; then
ifconfig eth0 $STATIC_IP broadcast $BROADCAST netmask $NETMASK
route add default gw $GATEWAY
echo
fi
I'll ask PTVupgrade to make this a permanent patch."

So I think that it is not working for you because the "fix" is not for your situation "zippered, and not PTVnet'd".

I am an expert at seeing the ~~~ all the time in vi. I finally (I think) figured it out, what is happening is that vi couldn't find a file by the name I was using "fat fingered typing" and was in essence giving me the chance to edit a brand new one. :cool:

Of course I may be way off, maybe the file Lou is referring to is part of the slicer. Which I haven't been following all that well since I don't need it, not having hacked my 11-250 yet.

[bxs122]

rootwrite <enter>
vi /install/etc/rc.d/rc.sysinit.author <enter>
:77 <enter>
o echo <esc>
:x! <enter>
sync ; reboot <enter>


Well I did all the above and rebooted twice ... still no network :-(

oh darn, I forgot to run sh ./enhancements/var-symlinks.sh before makng the above changes.

[tivoupgrade]

willardcpa -

you are right in that i'm looking at things from a ptvnet standpoint (rbautch and i have been discussing compatibility issues, offline) but the /install/etc/rc.d/rc.sysinit.author should exist in either case -- that file is the "new" instance of rc.sysinit.author created by copying the "working" one into what will be the new root partition; the mount point is called "install"

sorry to turn the thread into a "vi" support thread - i hadn't anticipated that; for those of you who want to use 1.2 and the workaround, the alternative is simply to ftp the rc.sysinit.author file over to your PC; use a programmers editor (I like ultraedit); one that won't put ^M characters at the end of every line, and just insert that darn "echo" statement and that should solve the problem...

... we'll have an updated slicer available in a couple of days; so if you are stressed about this, just chill out and wait. at this point, it sounds like other evils may be lurking within 6.3, so i wouldn't be in such a hurry to jump into it anyway...

[bxs122]

Still no network ... tried running tivosh /hacks/network.tcl myip mygw from the bash prompt and got no errors. Rebooting now to see if I get my network back.

[gazzie4]

per tivoupgrade, added the echo on line 77:

I did this and rebooted twice, still no network. However i edited the /etc/rc.d/rc.sysinit.author as there is nothing in my install folder. any suggestions on how to get my network back?? thanks

[bxs122]

per tivoupgrade, added the echo on line 77:

I did this and rebooted twice, still no network. However i edited the /etc/rc.d/rc.sysinit.author as there is nothing in my install folder. any suggestions on how to get my network back?? thanks


I'm in the same exact boat.

My original setup was a instantcaked drive that was then zippered.
Ran the latest slicer and have been trying to get my network back ever since

When I connect via serial cable and reboot I notice all my zipper stuff is failing.

Does anyone have an rc.sysinit.author file they can PM me so I can see what it is supposed to look like?

[tivoupgrade]

per tivoupgrade, added the echo on line 77:

I did this and rebooted twice, still no network. However i edited the /etc/rc.d/rc.sysinit.author as there is nothing in my install folder. any suggestions on how to get my network back?? thanks

If you've already rebooted, then the /install folder is gone. Its only there after you run the slicer and before you reboot.

The point is to do what rbautch originally suggested, verify that the IF-THEN statement assocated with the STATIC_ON variable is either removed completely or has an echo statement in the middle of it.

So what I'd recommend you do at this point is copy the contents of your /etc/rc.d/rc.sysinit.author file into a post so we can all see what it looks like and we'll tell you what to change...

[bxs122]

If you've already rebooted, then the /install folder is gone. Its only there after you run the slicer and before you reboot.

The point is to do what rbautch originally suggested, verify that the IF-THEN statement assocated with the STATIC_ON variable is either removed completely or has an echo statement in the middle of it.

So what I'd recommend you do at this point is copy the contents of your /etc/rc.d/rc.sysinit.author file into a post so we can all see what it looks like and we'll tell you what to change...

I welcome the same help ... via bash prompt how do I copy the rc.sysinit.author file for posting here to review?

[gazzie4]

## ~~ Start of user section ~~ ##
#!/bin/bash

# PTVupgrade PTVnet rc.sysinit.author for Series2 DirecTV DVR
#

# If you want to have a static IP address, you need to change
# the STATIC_IP variables below to your desired IP address,
# and rename DHCP_ON to STATIC_ON
#
# For more information on this, go to http://forum.ptvupgrade.com
# and make sure you know what you are doing. If you make a mistake
# doing this, you may not find your TiVo on your network, ever again...
#
# Oh, and if you don't have a serial cable, get one, it could save you
# a lot of trouble if you mess this up.
#
STATIC_IP=192.168.1.175
NETMASK=255.255.255.0
BROADCAST=192.168.1.255
GATEWAY=192.168.1.1

#
#
######### First time booting? ########
#
# This checks for the FIRSTTIME_ON flag and does a few neat things.
# Mainly, it runs 51killer.tcl so you don't have to do a Clear and
# Delete everything when putting a new drive in your TiVo.
# It also restores the splashscreen to the appropriate one.
#
# Note: If you set this flag back to ON after you've been using your
# TiVo and recording programs, running 51killer.tcl again will mess up
# your existing recordings. We use this flag when preparing new drives
# for installation in different units to save time for customers, you
# probably don't ever need to use this.

if [ -f /init/ptv_flags/FIRSTTIME_ON ]; then
/ptvupgrade/bin/rootwrite;
rm -rf /init/ptv_flags/FIRSTTIME_ON
cp /init/ptv_images/PromScreen2Version7.NTSC.png /tvbin
if [ -f /init/ptv_flags/IC2_OFF ]; then
tivosh /ptvupgrade/bin/51killer.tcl
rm -rf /init/ptv_flags/IC2_OFF
/ptvupgrade/bin/rootread;
sync
restart
fi
/ptvupgrade/bin/rootread;
fi
#######

# This sets the priority of hacks and shell commands to the lowest
# possible priority so that the TiVo operation is not affected by
# your tinkering; uncomment this if you find your tinkering gets in the
# way, just note that sometimes you can lock up the shell if you do have this
# uncommented, so be prepared with a serial cable, just in case you mess things
# up.
# setpri fifo 1 $$

# Startup BASH in case you are using a serial cable to connect
# This has been moved to the /init directory so that shell starts
# right at boot time
# /bin/bash -login</dev/ttyS2&>/dev/ttyS2 &

# Lets set the path to look in our own bin first, and then busybox
export PATH=$PATH:/ptvupgrade/bin:/ptvupgrade/busybox

# An extra library directory needed for yac and elseed
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/ptvupgrade/lib

# Check flags for IP address (we recommend you just stick with DHCP)
if [ -f /init/ptv_flags/DHCP_ON ]; then
/ptvupgrade/bin/dhcp_enable.ptv
fi

if [ -f /init/ptv_flags/STATIC_ON ]; then
echo
fi

sleep 3

#start telnet

if [ -f /init/ptv_flags/TELNET_ON ]; then
tnlited 23 /bin/bash -login &
fi

#start ftp

if [ -f /init/ptv_flags/FTP_ON ]; then
/ptvupgrade/bin/tivoftpd
fi

#start tivoweb

if [ -f /init/ptv_flags/TIVOWEB_ON ]; then
rootwrite
mkdir -p /var/hack
if [ -f /init/ptv_flags/IC2_ON ]; then
sleep 120
rm -rf /init/ptv_flags/IC2_ON
fi
/ptvupgrade/tivowebplus/tivoweb
fi

if [ -f /init/ptv_flags/PHONE_OFF ]; then
if ! [ -f /var/spool/cron/crontabs/root ]; then
/ptvupgrade/misc/cron_stuff/setup_cron
fi
phonereset.tcl
fakecall.tcl
crond
fi

# start extended tpm apps or other things
# thanks mike for the tpm structure
for i in /init/ptv_start/S[0-9][0-9]*
do
# Check if the script is there
[ ! -f $i ] && continue
source $i start
done
### ~~ End of user section ~~ ###
## Slicer - run network script only once. Reboot after 20 minutes
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
tivosh /hacks/network.tcl 192.168.1.175 192.168.1.1
mount -o remount,ro /
fi
fi

[charlestwaters]

Once your HR10 gets upgraded to 6.3, can you get the Telnet and FTP and TWP stuff back once you login to your Tivo via PPP?

Or is that the only way that you can get into it now!? My HR10 downloaded 6.3 and installed it itself. No slicer was used on mine!

--- Goobz!

[Gunnyman]

if you got 6.3 installed, chances are you didn't have upgradesoftware=false on your bootpage. Hacks are gone. You're going to have to manually hack 6.3 for now.

[willardcpa]

Once your HR10 gets upgraded to 6.3, can you get the Telnet and FTP and TWP stuff back once you login to your Tivo via PPP?

Or is that the only way that you can get into it now!? My HR10 downloaded 6.3 and installed it itself. No slicer was used on mine!

--- Goobz!Man, I hope that Charles middle initial is "T". ;)

[bxs122]

As feared slicer and the 6.3 upgrade has left my tivo in a not so healthy state.
Watching tv I happened to have the serial cable connected and no prompt the tivo rebooted. I looked at the hyperterminal session and found

Tmk Fatal Error: Activity Phone <1166>: unexpected signal 10

followed by a flush and reboot



Here is my rc.sysinit.author file ... any help at this point is much appreciated.

#!/bin/bash
export PATH=./:.:/utils:/bin:/sbin:/tvbin:/tivobin:/busybox:/enhancements
export TIVO_ROOT=
export MFS_DEVICE=/dev/hda10
tnlited 23 /bin/bash -login &
tivoftpd
/bin/bash </dev/ttyS2&> /dev/ttyS2&
fakecall.tcl

sleep 60
echo
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
mount -o remount,ro /
reboot
fi
fi

######################################
mount -o remount,rw / &>/dev/null
rm /zipper_flag &>/dev/null
mount -o remount,ro / &>/dev/null

#############################################
# starting NCID CallerID
touch /var/log/cidcall.log &
cd /var/hack/sbin; ./ncidd
cd /var/hack/bin; ./tivocid &

#############################################
# starting EndPadPlus
tivosh /enhancements/endpadplus.tcl 1 1 -seq -auto >> /dev/null &

#############################################
# starting Tivowebplus
/enhancements/TWPrun.sh

#############################################
# start crond after waiting 30 seconds
sleep 30
/busybox/crond

#############################################
# Check if var got wiped, and if so, rebuild symlinks from /enhancements/varhacks
if [ ! -e /var/vardelete_flag ]; then
sh /enhancements/var-symlinks.sh
fi

#start vserver
/var/hack/vserver &
## Slicer - run network script only once. Reboot after 20 minutes
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
tivosh /hacks/network.tcl 192.168.15.22 192.168.15.1
mount -o remount,ro /
fi
fi
echo

[tivoupgrade]

As feared slicer and the 6.3 upgrade has left my tivo in a not so healthy state.
Watching tv I happened to have the serial cable connected and no prompt the tivo rebooted. I looked at the hyperterminal session and found

Tmk Fatal Error: Activity Phone <1166>: unexpected signal 10

followed by a flush and reboot



Here is my rc.sysinit.author file ... any help at this point is much appreciated.

#!/bin/bash
export PATH=./:.:/utils:/bin:/sbin:/tvbin:/tivobin:/busybox:/enhancements
export TIVO_ROOT=
export MFS_DEVICE=/dev/hda10
tnlited 23 /bin/bash -login &
tivoftpd
/bin/bash </dev/ttyS2&> /dev/ttyS2&
fakecall.tcl

sleep 60
echo
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
mount -o remount,ro /
reboot
fi
fi

######################################
mount -o remount,rw / &>/dev/null
rm /zipper_flag &>/dev/null
mount -o remount,ro / &>/dev/null

#############################################
# starting NCID CallerID
touch /var/log/cidcall.log &
cd /var/hack/sbin; ./ncidd
cd /var/hack/bin; ./tivocid &

#############################################
# starting EndPadPlus
tivosh /enhancements/endpadplus.tcl 1 1 -seq -auto >> /dev/null &

#############################################
# starting Tivowebplus
/enhancements/TWPrun.sh

#############################################
# start crond after waiting 30 seconds
sleep 30
/busybox/crond

#############################################
# Check if var got wiped, and if so, rebuild symlinks from /enhancements/varhacks
if [ ! -e /var/vardelete_flag ]; then
sh /enhancements/var-symlinks.sh
fi

#start vserver
/var/hack/vserver &
## Slicer - run network script only once. Reboot after 20 minutes
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
tivosh /hacks/network.tcl 192.168.15.22 192.168.15.1
mount -o remount,ro /
fi
fi
echo

Well, its pretty obvious from the looks of this file that you did not have a unit that was networked with PTVnet; rbautch's post (and my subsequent instructions) were specific to the case of rc.sysinit.author files created using PTVnet.

I can see that you put an "echo" at the bottom of the file - sort of unnecessary as the point of the "echo" was to go into the IF-THEN wrapper associated with the STATIC variable that is edited by the slicer.

In any case, you might try creating an empty file (touch /firstboot_flag) and see if that helps, but what I would strongly recommend at this point is to restore your drive back to your 3.1.5f/networked instance, let your unit catch the slices and wait for a version of the slicer that is bulletproof when it comes to this upgrade - otherwise, you'll need to do a bit more lurking and experimenting for now.

I wouldn't not worry about the "echo" statement that is now at the bottom of the rc.sysinit.author file, but if you want to vi the file, you can use ^G to get to the end of it "dd" to erase the last line and :x! to write and quit... consider it an exercise in vi, at the worst...

more testing tonight, and probably an update that will allieviate the need to mess with 1.2 and workarounds

[bxs122]

Well, its pretty obvious from the looks of this file that you did not have a unit that was networked with PTVnet; rbautch's post (and my subsequent instructions) were specific to the case of rc.sysinit.author files created using PTVnet.

I can see that you put an "echo" at the bottom of the file - sort of unnecessary as the point of the "echo" was to go into the IF-THEN wrapper associated with the STATIC variable that is edited by the slicer.

In any case, you might try creating an empty file (touch /firstboot_flag) and see if that helps, but what I would strongly recommend at this point is to restore your drive back to your 3.1.5f/networked instance, let your unit catch the slices and wait for a version of the slicer that is bulletproof when it comes to this upgrade - otherwise, you'll need to do a bit more lurking and experimenting for now.

I wouldn't not worry about the "echo" statement that is now at the bottom of the rc.sysinit.author file, but if you want to vi the file, you can use ^G to get to the end of it "dd" to erase the last line and :x! to write and quit... consider it an exercise in vi, at the worst...

more testing tonight, and probably an update that will allieviate the need to mess with 1.2 and workarounds

I have to say slicer is not the best 20 dollar investment I've made ... ended up causing more grief for me then good.

thanx for the help.

I have a backup of my rc.sysinit.author from before runnign the slicer - do you think restoring that will help at all?

*If I tried creating an empty file what would be in it? you reference touch /firstboot_flag but not sure what that means. At this point I've got a pretty ugly tivo due to trying to slice the 6.3 so I figure I've got nothing to lose.

[fatdad1]

I have a PVnet drive, but show no files or directory (/hacks) that has the file "network.tcl" Is the file and directory added by slicer. I tired the first beta, lost network, reimaged with instant cake. 6.3 worked just couldn't get my network back. Had serial connection. Afraid to try second beta. Think I'll wait. Will you make the latest available when ready?

[gsr]

I have to say slicer is not the best 20 dollar investment I've made ... ended up causing more grief for me then good.

I don't think it's fair to be criticising the Slicer at this point. It was made clear from the start that it hadn't been tested with 6.3 yet (how could it have been?) and to tread lightly. PTVUpgrade seems to have only had 6.3 slices to work with for a few days now. As a software engineer myself, it seems reasonable that it might take him a day or 3 (or more) to get all the kinks worked out. Couple that with having to deal with various starting points (hacked with Zipper, manually hacked, original PTVUpgrade install, etc....) and it might actually take a bit of time to get something that works without any manual intervention required.

The 6.3 upgrade should be nice to have, but doesn't add any features that anyone absolutely has to have right this second. If you're not willing to take the risk of having a Tivo that's left in an unusable state, it's your responsibility to hold off on manually installing the upgrade until things have clearly stabilized (as in several days or more of success stories with minimal problem reports). Couple that with the fact that DTV has halted the upgrade due to problems that have been found and it doesn't seem like a good idea to install the upgrade at all. This is probably the worst time of the year to screw up your Tivo with the fall TV season taking off this week.

And I thought I was impatient... :rolleyes:

I'm actually tempted to Zipper my 2nd HR10-250 so I have control over when the software does get upgraded. Presumably a replacement for 6.3 will come out reasonably soon and I'd rather not be the first to have it installed.

The software we have right now works pretty well IMO - it may be slow, but at least it works :).

[tivoupgrade]

I have to say slicer is not the best 20 dollar investment I've made ... ended up causing more grief for me then good.

thanx for the help.

I have a backup of my rc.sysinit.author from before runnign the slicer - do you think restoring that will help at all?

Well, it depends on what your expectations were. The tool is intended to make it easier to migrate to the newer versions of software while attempting to preserve your old hacks. In this particular discussion, the slicer has been stretched to its limit (and we are continuing to update it although its being used in a way in which it was not initially intended to be used).

I'd suggest if you've learned anything though the process of trying new things, then it might be $20 well spent, but again, it depends on what you expected.

In any case, what I'd recommend is that you restore your drive back to its 3.1.5f/networked state - and wait until there is a clearer path to 6.3 with the full networking capability using this tool, in combination with an appropriate how-to or other more 'cookbook' like set of instructions.

As I said earlier, we will provide an update to the slicer that preserves the networking capabilities, so its just a matter of patience if you don't want to spend any more time on it.

[gazzie4]

I hate to be pushy to tivoupgrade or rbautch, you guys have been a of help so far and really appreciate it, but I must ask, any ideas on getting my network working. I really want to get it done before I tape too many shows.

Thanks

[rbautch]

I you have a Zippered tivo and lost networking after running The Slicer v1.2, this is the offending section of your author file that needs to be deleted:
sleep 60
echo
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
mount -o remount,ro /
reboot
fi
fi Note that the similar looking section at the end needs to stay. Unfortunately I used the same firstboot_flag variable in the zipper, and it's causing your tivo to reboot before it gets to the part of author file that sets up the network. Here are two options:

1. Delete the text above in the author file. Check if the /firstboot_flag is present, and if not, recreate it by typing "touch /firstboot_flag" at your bash prompt.

2. A more definitive (and better) way to do is this: If you have a serial cable, then you can connect and get a serial bash prompt while your tivo is running. Then run "tivosh /hacks/network.tcl 192.168.15.22 192.168.15.1", then reboot, and your network should come up.

Note that v1.3 of the Slicer fixes this issue.

[tivoupgrade]

I don't think it's fair to be criticising the Slizer at this point. It was made clear from the start that it hadn't been tested with 6.3 yet (how could it have been?) and to tread lightly. PTVUpgrade seems to have only had 6.3 slices to work with for a few days now. As a software engineer myself, it seems reasonable that it might take him a day or 3 (or more) to get all the kinks worked out. Couple that with having to deal with various starting points (hacked with Zipper, manually hacked, original PTVUpgrade install, etc....) and it might actually take a bit of time to get something that works without any manual intervention required.

The 6.3 upgrade should be nice to have, but doesn't add any features that anyone absolutely has to have right this second. If you're not willing to take the risk of having a Tivo that's left in an unusable state, it's your responsibility to hold off on manually installing the upgrade until things have clearly stabilized (as in several days or more of success stories with minimal problem reports). Couple that with the fact that DTV has halted the upgrade due to problems that have been found and it doesn't seem like a good idea to install the upgrade at all. This is probably the worst time of the year to screw up your Tivo with the fall TV season taking off this week.

And I thought I was impatient... :rolleyes:

I'm actually tempted to Zipper my 2nd HR10-250 so I have control over when the software does get upgraded. Presumably a replacement for 6.3 will come out reasonably soon and I'd rather not be the first to have it installed.

The software we have right now works pretty well IMO - it may be slow, but at least it works :).

Thx, that's appreciated. I don't want to start a pile on or anything, so I'm happy to leave it at that.

In any case, for anyone who is just joining the thread... the current state of the slicer is that it WILL preserve your serial/bash access. It can allow you to get your networking running again with some of the techniques discussed here, and lastly, I'll personally recommend extremely light treading - if you are looking for a one-stop-shop for networking your 6.3 unit, this is NOT the tool to use.

I really wish I could link to the one pager at d-v-r-playground because I think that pretty effectively outlines what the product was designed to do, but admittedly, there's a bit of an expectation management issue and I feel responsible for that -- we'll try to keep everyone happy as long as folks are patient through the transition... thx again

[bxs122]

Well, it depends on what your expectations were. The tool is intended to make it easier to migrate to the newer versions of software while attempting to preserve your old hacks. In this particular discussion, the slicer has been stretched to its limit (and we are continuing to update it although its being used in a way in which it was not initially intended to be used).

I'd suggest if you've learned anything though the process of trying new things, then it might be $20 well spent, but again, it depends on what you expected.

In any case, what I'd recommend is that you restore your drive back to its 3.1.5f/networked state - and wait until there is a clearer path to 6.3 with the full networking capability using this tool, in combination with an appropriate how-to or other more 'cookbook' like set of instructions.

As I said earlier, we will provide an update to the slicer that preserves the networking capabilities, so its just a matter of patience if you don't want to spend any more time on it.

I like your approach -- it has been a learning experience. As a Software Architect on the Wintel platform I've been itching to get my hands into Linux and more. The twenty spent is nothing in comparison to the 150 I spent this weekend at Borders picking up Linux and Tivo books.

Sorry my frustration flowed over into my previous post - just try to get back to something useable before NipTuck airs (the wife is not so happy at the moment).

Just curious ... couldn't I reuse Slicer to go back to the previous 3.x install? Would those slices still be in mfd/swsystem?

[Lord Vader]

I have run the Slicer 4 times now, and each time it runs fine and preserves networking and hacks. I think the only issue remaining is compatibility with PTVnet users who have a complicated author file. Version 1.2 is still a viable option for PTVnet users - all that's needed is to delete or comment out the following lines from the author file before you start: if [ -f /init/ptv_flags/STATIC_ON ]; then
ifconfig eth0 $STATIC_IP broadcast $BROADCAST netmask $NETMASK
route add default gw $GATEWAY
fi
...and add these to lines near the top of the author file:
export TIVO_ROOT=
export MFS_DEVICE=/dev/hda10I smell a version 1.3 on the way.

Is that what smells, Russ? I thought it might have been our White Sox. :( :(

[bxs122]

Edit: this is the offending section of your author file and should be deleted:
sleep 60
echo
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
mount -o remount,ro /
reboot
fi
fi Unfortunately it looks like I used the same variable in the zipper, and it's causing your tivo to reboot before it gets to the network part of the script. Here are two options:

1. Delete the text above in the author file. Check if the /firstboot_flag is present, and if not, recreate with "touch /firstboot_flag" as suggested above.

2. A more definitive (and better) way to do is this: If you have a serial cable, then you can connect and get a serial bash prompt while your tivo is running. Then run "tivosh /hacks/network.tcl 192.168.15.22 192.168.15.1", then reboot, and your network should come up.


thanx ... I'll give it a try.
So delete the
sleep 60
echo
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
mount -o remount,ro /
reboot
fi
fi
and replace with
sleep 60
echo
if [ -e /firstboot_flag ]; then
touch /firstboot_flag
fi

[mchahn]

Is this the right thread to discuss problems with things like tivowebplus after successfully upgrading? If so, can anyone tell me why the times everywhere in twp are an hour off? Does anyone know a fix?

[rbautch]

thanx ... I'll give it a try.
So delete the
sleep 60
echo
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
mount -o remount,ro /
reboot
fi
fi
and replace with
sleep 60
echo
if [ -e /firstboot_flag ]; then
touch /firstboot_flag
fiNot quite. I edited my post above to be more clear. Just delete those lines in your author file, and don't replace them with anything. The simliar looking commands at the end of the author file will run the network script, and should stay. The touch command is not added to your author file, it's typed in as a command, and just recreates the /firstboot_flag.

[tladle]

I read somewhere that the HR10-250 did not support wireless adapters on software 3.1.5 but that the DirecTivo's running 6.2 did. Does this mean that 6.3 for the HR10-250 does now support wireless adapters and if so is the NetGear MA111 still the best option?

Thanks in advance.

[bxs122]

Not quite. I edited my post above to be more clear. Just delete those lines in your author file, and don't replace them with anything. The simliar looking commands at the end of the author file will run the network script, and should stay. The touch command is not added to your author file, it's typed in as a command, and just recreates the /firstboot_flag.


`touch`

Dooohhh -- I knew that.

Should I still touch firstboot_flag before the reboot?

So what I'll do is remove the lines of code you mentioned.
exit VI
touch firstboot_flag
reboot

thanx again all for the help.

[rbautch]

`touch`

Dooohhh -- I knew that.

Should I still touch firstboot_flag before the reboot?

So what I'll do is remove the lines of code you mentioned.
exit VI
touch firstboot_flag
reboot

thanx again all for the help.You got it. You'll have to reboot twice. Once to run the author file, and once for the new settings to take effect.

[bxs122]

You got it. You'll have to reboot twice. Once to run the author file, and once for the new settings to take effect.

Doesn't look like I am going to get the chance. I lost the bash prompt and had to pull the plug to reboot. Unfortunately I still cannot get a bash prompt. The last items to scroll up in Hyperterminal is:


Scanning for phase4 repair scripts
Running boot Stage G_PostApplication scripts
/etc/rc.d/rc.sysinit: /etc/rc.d/rc.sysinit.author: Permission denied
rc.sysinit is complete
ApgManager Transition from state BOOT to SECONDARY_BOOT
ApgManager Transition from state SECONDARY_BOOT to FAST_LOAD
ApgManager Transition from state FAST_LOAD to FAST_LOAD
ApgManager Transition from state FAST_LOAD to FAST_LOAD
ApgManager Transition from state FAST_LOAD to FAST_LOAD
ApgManager Transition from state FAST_LOAD to FAST_LOAD
ApgManager Transition from state FAST_LOAD to FAST_LOAD
ApgManager Transition from state FAST_LOAD to STEADY_STATE
<BroadcomDirectvInputReinitialize> Set tuner mux pin state to DSS
<BroadcomDirectvInputReinitialize> Set tuner mux pin state to DSS

After that I can't do anything.

I suspect I have to chmod 777 on rc.sysinit.author
I pulled the drive, booted in another machine with an LBA disk but don't know how to mount hdc to access the filesystem. Any help appreciated.

[rbautch]

I read somewhere that the HR10-250 did not support wireless adapters on software 3.1.5 but that the DirecTivo's running 6.2 did. Does this mean that 6.3 for the HR10-250 does now support wireless adapters and if so is the NetGear MA111 still the best option?

Thanks in advance.Yes wireless works with 6.3. The MA111 shoud work, but make sure there's not a new version of it that's not on tivo's list of compatible adapters.

[gazzie4]

Yes wireless works with 6.3. The MA111 shoud work, but make sure there's not a new version of it that's not on tivo's list of compatible adapters.
only if you can get your dtivo to recognize the usb adapter

[rbautch]

I suspect I have to chmod 777 on rc.sysinit.author
I pulled the drive, booted in another machine with an LBA disk but don't know how to mount hdc to access the filesystem. Any help appreciated.Type "bootpage -p /dev/hdc" to find out if your root filesystem is hdc4 or hdc7, then make a temp directory like this "mkdir /tivo", then mount it with mount /dev/hdcX /tivo" Where X is the root filesystem you determined in the previous step. Then "chmod 755 /tivo/etc/rc.d/rc.sysinit.author".

[bxs122]

Type "bootpage -p /dev/hdc" to find out if your root filesystem is hdc4 or hdc7, then make a temp directory like this "mkdir /tivo", then mount it with mount /dev/hdcX /tivo" Where X is the root filesystem you determined in the previous step. Then "chmod 755 /tivo/etc/rc.d/rc.sysinit.author".


thanx -- gonna give it a go.

YOU DA MAN!!!! That did it.

Might as well delete that section you mentioned above since I've got the drive mounted.

thanx again,

[gazzie4]

Any thoughts on getting mine up and running?

not to be pushy, but I would like to fix this before my wife cuts me off for good for messing with her TV

[agzela]

Im not getting my lights on my linksys usbm200 ver 2 adapter after I used slicer....

Do I need to reinstall the usb 2.0?

Im getting this at bootup

usb.c: USB device 2 (vend/prod 0x13b1/0x18) is not claimed by any active driver

[rbautch]

Any thoughts on getting mine up and running?

not to be pushy, but I would like to fix this before my wife cuts me off for good for messing with her TVAh, your original post quickly got swallowed by this fast growing thread. You need to add the following two lines at the top of your author file, just after #!/bin/bashexport TIVO_ROOT=
export MFS_DEVICE=/dev/hda10

[gazzie4]

Thank you, I will try that this evening...I really do appreciate all the time you guys put into this for us wanna be hackers.

[rbautch]

Im not getting my lights on my linksys usbm200 ver 2 adapter after I used slicer....

Do I need to reinstall the usb 2.0?Yes. The latest slicer does not copy over usb drivers from the old partition. You can copy them over yourself my mounting the old partion either with a serial cable or by mounting the drive in your PC. You'll also need to edit the usb.map file (can't just copy the old one), which is now in /platform/etc/hotplug.

[agzela]

Yes. The latest slicer does not copy over usb drivers from the old partition. You can copy them over yourself my mounting the old partion either with a serial cable or by mounting the drive in your PC. You'll also need to edit the usb.map file (can't just copy the old one), which is now in /platform/etc/hotplug.

rbautch, could you pls give me the commands to use from my serial BASH prompt for the above?

Whats the change to make on the usb.map file?

[rbautch]

rbautch, could you pls give me the commands to use from my serial BASH prompt for the above?

Whats the change to make on the usb.map file?
You can mount the alternate file partition with mount /dev/hdaX /install where X is your alternate filesystem partition. Then navigate to /install, find your drivers, and copy them over. Posting an exact series of commands rarely turns out well - see Lou's vi tutorial above :) If you need help beyond this, either read up on basic linux file manipulation, or buy an adapter that works with the stock drivers.

See Jamies thread on DDB for modifying usb.map. You need to add an entry right under the usbnet heading.

[agzela]

You can mount the alternate file partition with mount /dev/hdaX /install where X is your alternate filesystem partition. Then navigate to /install, find your drivers, and copy them over. Posting an exact series of commands rarely turns out well - see Lou's vi tutorial above :) If you need help beyond this, either read up on basic linux file manipulation, or buy an adapter that works with the stock drivers.

See Jamies thread on DDB for modifying usb.map. You need to add an entry right under the usbnet heading.

I have the mount all set which files/dir do I need to move over for usb?
What are the changes to be made to the usb.map?

I can figure out the commands as i go along....

[tnedator]

Ok, I am not real clear on the current status of the slicer. It appears that it 'almost' works, and if I followed it correctly, there are some problems related to the PTVnet networking.

So straight question: I had a copy of my stock drive that I applied the zipper and then tweak.sh on a couple weeks ago. If I run the slicer 1.2 on it, what should I expect?

Also, anyone have an opinion on installing the current version of 6.3 or waiting for D* to release the next version?

Thx

[Tonedeaf]

Also, anyone have an opinion on installing the current version of 6.3 or waiting for D* to release the next version?

Thx
I decided to not go the slicer route and just install 6.3 and let it overwrite the hacks I had on mine. Never extracted or anything with it so I figured what the heck. I did not want to have to purchase serial cable to get access to it again.

If you have no need for 72.5 or 95, then I would say get it installed and enjoy folders. The programming gods here will have an easy way to zipper this one soon I would imagine.

[tivoupgrade]

Ok, I am not real clear on the current status of the slicer. It appears that it 'almost' works, and if I followed it correctly, there are some problems related to the PTVnet networking.

So straight question: I had a copy of my stock drive that I applied the zipper and then tweak.sh on a couple weeks ago. If I run the slicer 1.2 on it, what should I expect?

Also, anyone have an opinion on installing the current version of 6.3 or waiting for D* to release the next version?

Thx

current status of 1.2, within the context of moving 3.1.5f systems to 6.3, is that serial/bash will be preserved, and the majority of hacks and startup commands will be moved over, as well.

to regain network access you will need to do some workarounds which are discussed in the previous posts of this thread...

an updated version of the slicer is forthcoming that will preserve network, however will require the use of a static IP address. and i can tell you right now, the only thing we are testing it on is the usb ethernet adapters that are known to work with PTVnet (eg Netgear FA120)...

... more to come...

[tnedator]

current status of 1.2, within the context of moving 3.1.5f systems to 6.3, is that serial/bash will be preserved, and the majority of hacks and startup commands will be moved over, as well.

to regain network access you will need to do some workarounds which are discussed in the previous posts of this thread...

an updated version of the slicer is forthcoming that will preserve network, however will require the use of a static IP address. and i can tell you right now, the only thing we are testing it on is the usb ethernet adapters that are known to work with PTVnet (eg Netgear FA120)...

... more to come...

Thanks for the update. I think I will wait for the update. Since I bought my two FA120's from you guys, I should be in good shape :)

[tivoupgrade]

I've just updated to 1.3 and links have been regenerated for everyone who previously ordered.

Notable differences include pretty much everything discussed up to this point; it was mostly changes to the generated output of the rc.sysinit.author file.

If you've ordered the product but did not receive your download link, please check your SPAM folders; and PM me with your order info if you need the link regenerated. If you botched your drive using the Slicer, and you didn't make a backup, we are extending the offer for a 3.1.5f InstantCake distro; send us your Slicer order info and we'll send you a link. This offer only applies to folks who've purchased the slicer prior to this post. Thx for your patience.

[Lord Vader]

Thanks, Lou. BTW, if we're looking to get an actual Instantcake image of 6.3 at some point--to use for virgin drives--do you expect that sometime? Just curious.

[Finnstang]

Excellent job, guys! Way to stay on top of this and support everyone in this thread.

[bxs122]

I've tried most of what has been posted here but am still experiencing an occasional reboot and no network.

So I think tonight I'll pull the drive and use my instantcake 3.1.5f to go back to the previous version.

A few weeks back when I first purchased instantcake 3.1.5f I also purchased a new drive. Today I have a drive that unfortunately has quite a few recordings on it. If I run instantcake 3.1.5f do I need to first reformat the drive? If not then will I lose my recordings?

thanx

[rbitting]

I finally got up the courage and ran the Slicer last night. Seemed to work just fine. I had to run the tweak enhancement script again to get TiVoWebPlus back. The only thing I had a problem with was I didn't have the PATH statement in rc.sysinit.author like before so I put it in there the way it was and rebooted and it is back to normal.
As far as the limited testing I have done so far, I find 6.3 to be much faster in most aspects. I definitely like the folder option. Only one thing is not the same as before and I don't know if it can be fixed or not. Hopefully there is an answer in DDB since we can not discuss it here. Plus it would be nice if MRV and HMO worked on it :)

Oh and Kudo's to rbautch and everybody else who has done so much good work here and on the enhancements that make life SO nice on a TiVo. :up:

[cheer]

A few weeks back when I first purchased instantcake 3.1.5f I also purchased a new drive. Today I have a drive that unfortunately has quite a few recordings on it. If I run instantcake 3.1.5f do I need to first reformat the drive? If not then will I lose my recordings?You don't need to reformat the drive, but you will lose all recordings on it.

[bxs122]

You don't need to reformat the drive, but you will lose all recordings on it.

bummer

[rbitting]

I may have spoken too soon on the success of my upgrade. This morning everything was working fine even after an overnight reboot. TivoWebPlus, FTP, Telnet. Now I just tried getting into TiVoWebPlus and no response. Tried Telnet, no response. Tried FTP, no response. However I can ping it just fine. :mad:

Any ideas on what might have happened? I hope that the new 6.3 doesn't have some code to disable these hacks on a periodic basis.

I'll have to make up a serial cable tonight and see if I can get back in to see what happened. Any ideas or suggestions or similiar experiences?

P.S.

I'll also try to reboot the unit when I get home and see if that makes everything work again. That is one thing I can't do remotely from the net...yet. Still if this is a daily occurence then it isn't a good thing.

[gazzie4]

I have done all steps to get back network, but still have no lights on my adapter. I used slicer 1.2, then after the reboot, made the changes to rc.sysinit.author. both adding the 2 lines under the #!/bin/bash and removed the lines around line 77 as mentioned above.

I checked my usb.map and it shows the usb200m. I am missing something here?