More Newb problems ...

[mebgoin]

Thanks to everyone on this board in advance, you guys have definitely been an inspiration for me. I have leared tons already through working on this, but just when I start to feel confident about what I'm doing, I run into a roadblock like this:

I've been working on getting 4.0.1b installed on my RID box, and so far it's been going pretty well. When I first put the new HD in the tivo, it hung shortly after it started booting. I was able to figure out that the first LBA48 kernel I had used had somehow gotten corrupted, so I replaced that and I've made it much farther. Now this is what I get (through hyperterminal) when I boot:

(See attached text file)

Part of me wants to think that maybe the dssapp I used got corrupted too, considering that seems to be what loads next from what I've read (access card stuff, etc seems to always follow the "caminitread called" line) but I'm not sure. I'm going to try replacing the dssapp with another fresh one and see if that helps, but any suggestions would be very helpful. Thanks!

Matt

[mebgoin]

Ok ... replacing the DSSapp seems to have fixed that, but I'm still not getting a bash prompt ... at least I don't think I am. I was able to get the box up and running enough to do a 'clear and delete everything' but without a bash prompt I can't do much else, seeing that I don't yet have an ethernet connection for it. I have my bootpage set up for "console=2,115200" like it's supposed to, and I thought I had my rc.sysinit.author set up properly to start telnet with "tnlited 23 /bin/bash -login &" but I'll pull the HD again and see if I had a typo or something. As always ... any help is useful ...

Matt

[ronnythunder]

are you trying to get serial bash, or be able to telnet? if serial, did you place the proper statement somewhere in the boot script chain:/bin/bash </dev/ttyS2 &>/dev/ttyS2 &if telnet, did you load network drivers and configure the interface?

ronny

[mebgoin]

Trying for a serial bash. Would that statement go in the rc.sysinit.author file? I had a look at my rc.sysinit file and I'm not sure if it's exactly what it should be. Doesn't that file come from the image I start with? If so I may need to try another image (I've come across a couple.) I added the line " /bin/bash </dev/ttys2&> /dev/ttys2&" to my rc.sysinit.author file but haven't had a chance to put the drive back in the machine and test it ... I have to work while the wife doesn't have shows to watch (or record.)

Matt

[mebgoin]

Ok, I've got a serial bash now ... well, barely. For some reason I'm having issues with keystrokes. Not all of my keystrokes transfer, if that makes sense. Sometimes I have to tap a key repeatedly in order to get it to go through, and then sometimes all the keystrokes that didn't show up will show up later. I'm wondering if I need to check my serial cable ... I made it myself, but IMHO it looks pretty good. Do you think maybe trying to slow down the serial connection speed would help? I think I can do that by editing the bootpage parameters. Anyway. I was able to get fakecall.tcl to run, but I don't think I'm succeeding with the superpatch. I do the mount / remount, and then switch to the directory that contains the superpatch-4all, chmod it, and then attempt to run it. But nothing seems to happen. If it were giving me an error message I'd have something to work with, but it's not. And it doesn't seem to do anything after I've rebooted. Any tips?

Matt

[fixn278]

Ok, I've got a serial bash now ... well, barely. For some reason I'm having issues with keystrokes. Not all of my keystrokes transfer, if that makes sense. Sometimes I have to tap a key repeatedly in order to get it to go through, and then sometimes all the keystrokes that didn't show up will show up later. I'm wondering if I need to check my serial cable ... I made it myself, but IMHO it looks pretty good. Do you think maybe trying to slow down the serial connection speed would help? I think I can do that by editing the bootpage parameters. Anyway. I was able to get fakecall.tcl to run, but I don't think I'm succeeding with the superpatch. I do the mount / remount, and then switch to the directory that contains the superpatch-4all, chmod it, and then attempt to run it. But nothing seems to happen. If it were giving me an error message I'd have something to work with, but it's not. And it doesn't seem to do anything after I've rebooted. Any tips?

Matt

You are starting serial bash twice. 1st, as part of the uma6fix (test.conf), and second, your addition to rc.sysinit. Your first log shows bash starting already.

[mebgoin]

Thanks .... I'll address that and see if that takes care of the problem. I think the reason I wasn't getting it before was because I had hardware flow control turned on in hyperterminal.

[mebgoin]

Success! Thanks to fixn27 for pointing out the error with serial bash ... I had started to think the same thing was happening from researching here, and you confirmed my suspicion. I'm guessing that my superpatch-4all and set_mrv files got corrupted too. I re-copied them to my drive and after I rebooted with bash fixed I was able to run them just fine. Now to play around some with 4.01b and see what I think of it. I need to hurry up and get an ethernet adapter for it now. Thanks for all the help guys!

Matt