I hope I did rmLogs right, because I lost Bash!! - help!

[groundhog]

I didn't use extreme25 for my hack, I did it right before extreme came out.

I didn't have a tvbin directory.

What I found was /tcl fixup02c.tcl
From what I remember that was the original hack file

So I moved fixsub.tcl and rmLogs to the /tcl dir. using zmodem.
I didn't delete fixup02c.tcl because I wasn't 100% sure it was the same as fixsub. & could still reside in the same dir, seeing that it had a different name.

I entered chmod +x fixsub.tcl rmLogs

Then I went to /etc rc.d & renamed rc.sysinit to rc.sysinit.old
Then I transfered superzaps rx.sysinit file to /etc rc.d
Then I chmod +x rc.sysinit

I didn't remove rc.sysinit.old, either.....

I guess maybe my problem is that rc.sysinit.old and fixup02c.tcl are both still existing and executable???

When I rebooted, I got the bash command, but when I enter ls, cd, or any other command I get no responce. :(

The tivo still works, and I still get "sucessded" when I make a phone call. Hopefully everything else still works.

Any idea how I can still get in with bash?

What should I do different when I try to fix the log problem with my other tivo hacked the same way that this one used to be??

[groundhog]

on second thought, I guess the new sysinit file points to /tvbin fixsub.tcl & mine is at /tcl fixsub.tcl... But if this is the case & it could cause problems, then how come my phone calls still = "Succeeded"?

[groundhog]

THIS THREAD (http://dealdatabase.com/forum/showthread.php?s=&threadid=4746) could also explain the problems I'm having. The image mentioned in this thread is the one that I used.

P.S. Ignor my posts in the linked thread here. Pay attention to posts by flipsoft, formula, and bubba J. My old problem(in that thread) has nothing to do with the problem I'm having now.

[genericuser]

Looks like you changed several things at once.

Check your rc.sysinit. Scroll tot he end where there is an 'if' test that checks for the existance of SubTest and FixSub.

Verify there is a space between the closing bracket and the test. IE:

old:
if [ -e blah] ; then
if [ -x blah] ; then

new:
if [ -e blah ] ; then
if [ -x blah ] ; then

If your bash prompt is after this code, it is not getting executed.

Is your terminal program set to the correct baud rate? Is there a .bashrc file in your / area? And if so, does it set the baud rate?

[groundhog]

My baud rate is set to 9600 bps in Terra Terminal. The thread that I posted above mentions other buad rates. I'll try that first. In order to check the rc.sysinit, I would have to pull the drive. I'm not ready to do that yet. If I have to pull the drive, it would assume that it would probably be best to just replace the rc.sysinit with the original, get rid of the fixsub & rmlog files and see if it would revert back to working like it used to. At that point, I would just have to look into one of the other approaches to the logging problem. Thanks for your advice. I'll start by adjusting the baud rate first.

[SP7128]

reboot your pc and the tivo machine ..............i've had to do that before too

[_Formula]

Tried sending this PM, but your mailbox is full??! Good lord.


The directories you mention don't seem right to me. I believe the fixup02c script on mine (if I included it, I don't remember) would be under '/var/tivo/tcl'. There is no problem leaving the rc.sysinit.old and fixup02c.tcl scripts on the unit.

If you had everything working before, you'll need to keep fixup02c.tcl because the TClient-lib looks for it. If you want to use the fixsub thing you'll need to do the necessary mods.

You say you don't have a tvbin directory. I don't see how that could be. The reason the phone call still says SUCCEEDED is because TClient-lib still executes fixup02c on every call attempt.

Baud rate could be your problem. From what I've seen, I think if your not matching baud rate you will lockup the BASH process running over serial. Check the new rc.sysinit to see what baud rate it's setting (if any) and set your term program. Reboot your Tivo if you get no response. If you set the baud rate correctly and go ahead and connect to the serial port, then boot the Tivo you should see a prompt shortly afterwards. If you get a few garbage characters, your baud rate is set wrong. You can try 38400, 57600 and 115200. Those are pretty common rates.

I hope all this mess helps in some way. Let me know how it goes...



groundhog wrote on 01-29-2002 10:31 AM:
Please see this thread. I tried to fix the logging problem on my Tivo with your 25hack image from November. I screwed something up and lost some bash abilities. You may be the only one that can help because the directory stucture is different than the extreme image that everyone else is using.
Please let me know if you have any ideas for fixing it.

Thanks :)

[groundhog]

Thanks for responding to my PM _Formula. I cleaned up my Inbox, just now. The baud rate isn't the problem. I just played with it last night. I get bash prompt at 9600. If I type 'stty sane', I can see the commands I type, afterwards, but I get "no such file or directory, with every ls or cd command. If i type 'stty 38400' & terra term is still at 9600, then when I type something I get junk. Then if I set terra term to 38400, I can see what I type again. If I type 'stty 115200' then I see junk when I type. But if I set terra term to 115200, then I correctly see what I type again. It appears that I'm communicating with the tivo, getting a bash promt, and I'm able to change baud rates in the tivo and terra term to match each other, but that's as far as I get. I can't type any other linux command, and get it to work.

[groundhog]

If you want to use the fixsub thing you'll need to do the necessary mods.

O.K. this is what I think I need to do to fix it. The only thing that I did that would drastically change anything was to replace the rc.sysinit file that existed on your(Formula's) image with one provided by superzap. I replaced it because I thought that somehow the supersap file would reference the fixsub file. If you think that your original rc.sysinit file will work with fixsub, I will restore your rc.sysinit file, first. Then I will try to find the TV Bin folder & do the mods the way that they were originally meant to be done. I'll post what I find as my file structure. From what I rember. After typing 'cd' a few times, all I saw was lib and bin. That seemed to be the lowest part of the dir structure that I could get to. Then if I typed 'cd bin' I would see a few files and folders and one of them was tcl. Fixup02c was in the tcl folder. I could never find a TVbin directory. I tried 'ls -m', 'ls --color', 'cd root', etc. I don't know how else to look for the directory.

_Formula, does your image include Joe? If so, what directory does it exist in?

[genericuser]

Glad to hear you do not have to pull the drives. Always make sure you match the baud rates before you start typing or you can hang the serial session and will ahve to reboot.

Here is what I do on reboot. Set teraterm to 9600, wait for the prompt to show up. Type stty sane, then type stty 57600. Then I immediately set the serial rate to 57600. Now I continue as normal.

As for your problem. Sounds like maybe your /var/hack area is gone. Try this. Get your 9600 baud prompt. type:

cd /

Now do your:

ls

Can you see a directory?

[_Formula]

Why are you trying to get fixsub working? If fixup02c already works I wouldn't worry about it. Using fixsub or fixup02c shouldn't have any effect on your bash prompt. I'd say it's a problem in rc.sysinit. Send it to me and I'll look at it.

I just thought of something... Your new rc.sysinit probably doesn't set the correct PATH to ls. Do this...cd /var/tivo/bin
./lsIf you get a directory listing, do this...PATH=$PATH:/var/tivo/binThis should enable you to use ls from any directory. This looks like your problem to me. If this fixes your problem, you'll need to add the PATH statement above to your rc.sysinit (or modify the current PATH statement).

[groundhog]

Thanks genericuser & _Formula, I'll try your suggestions and see what happens.

_Formula, the reason that I'm trying to get fixsub working is that I ran into the problem with the log files becomming to large. I lost the ability to fake the phone call. I restored the original image, and then did the modifications mentioned in this thread. I'm still unsure if I fixed the logging problem.

[genericuser]

It is possible that your /var/hack got wiped out because the log files got too large. If you cd / and then echo * and see a directory, but you can not ls, that means you have lost some of the commands and you will have to restore.

[groundhog]

It is possible that your /var/hack got wiped out because the log files got too large. If you cd / and then echo * and see a directory, but you can not ls, that means you have lost some of the commands and you will have to restore.

In case there's any confusion....To clear things up:
Yes. According to what I've read here relating to the logging problem, I must have lost my Var/hack. That's what caused the phone calls to fail. Then I fully resored & had a working hack again. To avoid losing the var/hack again, I looked into the fixsub & rmLogs fix. By attempting to do the rmLogs fix(along with replacing the rc.sysinit file), I screwed something up and lost some of my bash abilities.

[groundhog]

Is there a command in linux that will allow me to look for a specific directory, file, or directory path?

Example: 'find tvbin'

[_Formula]

You could probably do something like this...ls -R / | grep tvbinNever tried it, but it should work. Did you try what I suggested with the PATH deal? Did it work? I'm sure that's whats wrong with your ls command. When you added the rc.sysinit from xtreme, the PATH env variable is now being set to something else. The files on my image are all under /var/tivo, not /var/hack. Since the PATH isn't set, you can't run anything under /var/tivo. I believe ls will be under /var/tivo/bin, but it's possible it's under just /var/tivo.

[groundhog]

O.K. Back in Business!! Thanks Formula. You da man. The PATH command worked. It was in /var/tivo/bin.


I do have a tibin directory, but fixsub doesn't exist there.

Here is the rc.sysinit file that I used and the statement that went along with it:


Attached is the same speedboot rc.sysinit that Glitched posted with a change removing the rm/mkdir. It is designed to be used on surgeon's v2.5Xtreme with fixsub activated in conjuction with the rmlogs files I posted above or the logsnull files I posted in another thread. Don't use both rmlogs and logsnull at the same time. They both should be effective, so it's your choice.

Recommended install procedure:
1. Unzip rc.sysinit to your pc. (if you modify it make sure you use a unix compatible editor like TextPad)
2. From bash:
cd /etc/rc.d
3. Since rc.sysinit is a critical file, let's rename the old one just in case:
mv rc.sysinit rc.sysinit.old
(If you used chattr +i previously on rc.sysinit remember to use chattr -i first [chattr isn't necessary anyway])
4. enter:
rz
5. Using Tera Term Pro:
files menu->transfer->ZMODEM->send
select the rc.sysinit file and click Open.
wait for transfer to complete, there'll be some garabge on the bash command line so just hit <enter>.
6. enter:
chmod +x rc.sysinit
7. reboot and if all is ok cleanup old rc.sysinit:
rm rc.sysinit.old
CLICK HERE TO DOWNLOAD (http://dealdatabase.com/forum/attachment.php?s=&postid=22723)



New problem. I tried to edit rc.sysinit for the new path, and couldn't get joe to work. This is what I did:

mkdir /var/hack
Zmodem transfered Joe
Zmodem transfered Joerc
chmod +x *
joe /etc/rc.d/rc.sysinit

When I typed the last statement above I got several(maybe hundreds?) of lines saying something like


Joe = joe/var/hack = command failure ^K
Joe = joe/var/hack = command failure ^K
Joe = joe/var/hack = command failure ^K
Joe = joe/var/hack = command failure ^K
Joe = joe/var/hack = command failure ^K
Joe = joe/var/hack = command failure ^K
Joe = joe/var/hack = command failure ^K

& ending in. "Joe did not execute properly, do you want to continue?"

I've transfered and used joe before. I guess I just have a bad joe file?

[groundhog]

p.s. i also tried adding a path statment showing where joe existed, then I went to the rc.d directory and typed:
joe rc.sysinit.

I got the same results(joe failed to load properly)

[_Formula]

Never used joe before (I'm partial to vi). Probably the easiest thing to do would be to make your changes on your PC first and transfer it to the tivo. Just make sure you use a good editor like textpad that can save in UNIX format.

[groundhog]

thanks :)

I think my next step will be to replace the rc.sysinit & try a different approach. This whole problem was caused by files and instruction made to be used with 25extreme. There are other ways to fix the logging prob, that mention fixup02c & don't mention 25extreme.

Either way. I need to be able to edit rc.sysinit. I'll look into textpad.

[groundhog]

I think I found the problem with with Joe. Apparently Joerc needs to be converted to linux with DOStoUNIX, then transfered to the tivo.

[groundhog]

Done :) I used the method described HERE (http://dealdatabase.com/forum/showthread.php?s=&threadid=8350&perpage=15&pagenumber=1)


Thanks All for your help. :)