TiVo Community Forums Archives - Cannot boot kernel

TiVoCommunity.com
(c)opyright 1995-2005 All rights reserved
indexcheckTC
This area is a static history of posts in the TiVo Community Forum Archive.
This archive history was made for the simple indexing of search sites like Google.

Pages:1

Cannot boot kernel
(Click here to view the original thread with full colors/images)

Posted by: babs33

I just attempted to install a turbonet card in a Sony Directivo with 3.0 installed. I was using the silcondust install instructions (because I missed the fact that there were special instructions for 3.0 users). As a result I ran the nic_install turbonet command. Everything seemed fine...

After installing the drive back in the tivo I now get a "Cannot boot kernel" error when trying to start-up the box.

I did make a backup of root1 partition using mfstool so I am hoping that restoring that will fix the problem (fingers crossed).

I was also taking a look at the partition table using pdisk and I get 13 partitions, the first is Apple_parition_map with a length of 63 and a base of 1. Is this correct?

Thanks in advance,

Brian

Posted by: babs33

So I make a second mistake... I mounted the tivo(hdd) drive partition 4 as /mnt/c and then used mfstool to backup to /mnt/c/tivo.bak /dev/hdd. So I created the backup file on the tivo drive root1 partition. Funny thing is now I do a df on the system and see 0 available space on that partition. I never got an error message during the backup, but I find it hard to believe that it did not run out of space.

So now my question is: Is there a way to uninstall the turbonet drivers I installed above? I am assuming that the turbonet install that I ran linked in drivers for version 2.5 in to the kernel for 3.0 and that the resulting kernel is toast. Assuming I'm on the right track... does anyone have any suggestions on how to yank those drivers back out of the kernel?

If I am way off base, can someone help me get back on course... thanks.

Posted by: babs33

For anybody else unfortunate enough to follow in these tracks...

I skipped a step. You are suppose to reflash the prom before installing the nic drivers. The problem with the step by step guides is that they rarely qualify the step with why you do it. After reading a ton of posts I infer that installing the nic drivers creates a new kernel image and that by default the directivo boxes only run certian kernels... the prom reflash bypasses that protection thus allowing the new kernel to execute. If I am wrong please correct me.

In the end I ran the prom reflash install and put the drive back in the tivo. It's up an running now.

The NIC however does not seem to be working yet. I again infer from the little output from the program that the reflash installer actually updates the inactive partitions and then makes them active, so the nic install I made before is now on the inactive partition. Which means the now active partition (which reports 3.0.1 software) should see and load the NIC card automatically, but doesnt.

This time I'll get the backup right before I mess with anything else.