couldn't open /dev/tivoconfig

[blasted bill]

I installed tivo net and lots of other hacks and everthing was working fine. I modifiied the rc.sysinit to make sure everthing started on boot up, now the tivo won't boot up. I looked the rc.sysinit. my system boots from 4. 4 had a blank copy(nothing was in it) and 7 had a good copy. so i restored 4's copy from 7's and mad sure it was +x. tivo still will not boot

what it does is it comes up with the "your tivo is starting up, please wait" screen(i have a tivo 1 phillips) then flickers and goes to a blank gray screen, then goes back to the 1st screen and endlessly loops like that.

so i checked on the logs on 9 and the kernal log says "couldn't open /dev/tivoconfig". so i look at 4 and 7 again. 7 has it, 4 does not. i try to copy it from one to that other using dylan's but disk, but it told me "the device does not exist". the permisions were crw-rw-rw-, which i found to be odd cause i've never seen a c like that before. so i downloaded the tivo utility iso and booted from the cd, i was able to copy /dev/tivoconfig from one partion to the other. made sure the permission were the same, but the tivo still does the same thing when trying to boot and the kernal log still says "couldn't open /dev/tivoconfig.

does any one know what else i can try? thanks

[TheWickedPriest]

You could copy the entire /dev/hda7 partition to /dev/hda4 (dd if=/dev/hda7 of=/dev/hda4). Or you could change your boot parameters back to /dev/hda7. But I'd be more concerned about how your /dev/hda4 got that way to begin with.

The 'c' indicates a character-mode device. 'b' is for block devices.

[blasted bill]

*sigh* it did not work. still has the reboot loop with the intro screen. i have not had time to load it up and check the kernal log again. i still have the orginal tivo drive untouched and prestine, should i try copy the /dev 4 from there?

some one told me i could restore the boot partion of the drive with out destroying the saved shows, but didn't tell me how. can any one point me in the right direction to do that.

thanks for all your help (:

[blasted bill]

ok, i went throught the rc.sysinint line by line and found the program it was trying to call that wasn't there. the tivo boots again YA!! but my network doesn't work. i have link lights on the router and the linux box in the same configuration that it was before when it worked fine. i put tivo into back door mode and accessed the log files. the /var/log/messages log says...

dhclient:send_packet:network is unreachable
dhclient:send_packetlease consult README file regarding broadcast address

and it loops over and over. if i watch the screen long enough, i can watch it add new entires to the file

could i have messed something else up in the rc.sysinint? how can i fix it and what README is it talking about?

i have bash# back over serial btw.

[FauxCaster]

I don't think "/dev/tivoconfig" is a critical file. I think it's a default override file. It's showing up in the logs because it wasn't or'd in the code gracefully. In your logs are variables echoed immediately AFTER the "Couldn't open dev/tivoconfig".

I could be wrong, but the logs I've seen, suggest this interpretation to me.

Could you you post the chunk of the logs before and after?

[blasted bill]

oh, thanks for the reply. i was able to get the tivo to connect to the network by manually running ipconfig from bash. thanks though.