User:CuriousMark

From NAS-Central Buffalo - The Linkstation Wiki
Revision as of 22:32, 5 January 2008 by CuriousMark (Talk | contribs)

Jump to: navigation, search

Contents

CuriousMark's Kurobox as a TiVo MediaServer Page

I have had a Kurobox for some time now and it has served well as a basic file server. I have been wanting to upgrade it to act as a media server for my TiVo, but didn't know enough Linux to feel comfortable attacking the task. Also, the thought of putting together all the pieces seemed a bit daunting. With the recent advent of nearly automatic upgrades to uboot and modern Debian distributions, plus the arrival of pyTiVo on the scene, it seems like now is the time to quit procrastinating and get started.

Resources

The primary resource is NAS-Central and the wonderful people who are behind it. I started by asking in the forums. Here is the thread that this page is based on. It shows the false starts and mis-steps that I will leave out here in order to keep things readable and usable. My thanks to Andre, mindbender, and davy_gravy for their help and patience with this Linux newbie.

Installing U-Boot on an original Kurobox

Here is Mindbender's directions with annotations and hints added.

how to install LNI uboot + 2.4.33.3-firmimg.bin + freelink to the original kurobox/LS1

Prerequisites: cd /mnt/
wget http://downloads.nas-central.org/LS1_PPC/Bootloader/Uboot/Precompiled/u-boot-lsppchd-flash-1.2.0-r2.bin
wget http://downloads.nas-central.org/ALL_LS_KB_PPC/Bootloader/UBoot/FirmimgBins/linux-2.4.33.3-list.mg.2-v3/firmimg.bin
wget http://downloads.nas-central.org/LS1_PPC/Distributions/Freelink/TmpImages/tmpimage-FL-1-21-LS1.tgz

(thats downloading the uboot binary + the 2.4.33.3 firmimg.bin and the freelink rootfs to /mnt/ which should be the point where /dev/hda3 should be mounted to)

Since my kurobox was only slightly updated, wget was not available to me. Instead I downloaded those files to my PC and then put them on the share drive of the kuro using windows networking. I then logged into the Kuro using telnet and moved them to the suggested directory. If you are working with a new drive, this may not be an option. The Kurobox supports telnet, and that is another way to get the files onto the box.

cd /mnt/
mv /mnt/share/u-boot-lsppchd-flash-1.2.0-r2.bin u-boot-lsppchd-flash-1.2.0-r2.bin
mv /mnt/share/firmimg.bin firmimg.bin
mv/mnt/share/tmpimage-FL-1-21-LS1.tgz

Ok, here is a link to the flash map of the LS1/kurobox original.
http://buffalo.nas-central.org/index.php/Information/PPCFlashROM
There you will see the bootloader-device "/dev/fl2" and the firmimg.bin device "/dev/fl1".

You can install latest uboot without compiling by flashing the binary to /dev/fl2
http://buffalo.nas-central.org/index.php?title=U-boot_bootloader#Flashing_U-Boot_from_Linux

This is the critical part of this guide. in case anything goes wrong when flashing uboot you will need jtag to recover the box. Be warned! It worked for me on three boxes... It worked for me with no trouble either, but you should know you are doing this at your own risk, you really can brick your Kurobox.

installing uboot to /dev/fl2 dd if=u-boot-lsppchd-flash-1.2.0-r2.bin of=/dev/fl2 bs=1k

In case you have cmp on board of your currently installed execute the cmp command also to be completely sure that it worked. I did not have cmp and did not compare. I ran into issues later and was able to compare from Freelink (as installed below) and found that Flashing worked flawlessly. If you do wish to compare, install it to your kurobox before beginning. cmp u-boot-lsppchd-flash-1.2.0-r2.bin /dev/fl2
cmp: EOF on u-boot-lsppchd-flash-1.2.0-r2.bin
EOF means a good comparison. The flash device doesn't end at the end of file, so this result is expected.

installing the 2.4.33.3 firmimg.bin to /dev/fl1 if you do this, I recommend to flash the 2.4.33.3/telnet/ftp-enabled firmimg.bin to flash....this has the functionality you are used to on your kurobox.
[image:EM_Welcome_Screen.JPG thumb]

dd if=firmimg.bin of=/dev/fl1 bs=1k

Again, if you have cmp onboard then use it to make sure everything got written correctly.


Do both of the above flash operations at the same time without rebooting. Then you can reboot the first time...you ll see the box behaving differently...hopefully as shown in this video: http://www.youtube.com/watch?v=pTPrrUYd8O8

then you effectively can only boot to 2 and 3 blink mode as you only have a bootable kernel in flash (thats why you are flashing the 2.4.33.3-firmimg.bin btw...if you don`t and reboot uboot will have problems to find a kernel to boot). the 1-blink mode will work as well, but in reality it will be 2 blink mode as it defaults to the flash kernel if no kernel is found in /boot

Install freelink to /dev/hda1 you booted to EM mode with uboot....then you can install freelink to /dev/hda1. login via telnet. Code: mount_disk cd /mnt/hda1 rm -r * tar xzvf ../hda3/tmpimage-FL-1-21-LS1.tgz

that should be all.

how to install LNI uboot + 2.4.33.3-firmimg.bin to the kuroboxHG/LS HG/LS HS

Prerequisites: Code: cd /mnt/ wget http://downloads.nas-central.org/LSHG_PPC/Bootloader/Uboot/Precompiled/u-boot-lsppchg-flash-1.2.0-r2.bin wget http://downloads.nas-central.org/ALL_LS_KB_PPC/Bootloader/UBoot/FirmimgBins/linux-2.4.33.3-list.mg.2-v3/firmimg.bin

(thats downloading the uboot binary + the 2.4.33.3 firmimg.bin to /mnt/ which should be the point where /dev/hda3 should be mounted to)

ok, here is the flash map of the LS HG/LS HS/kuroHG original. http://nas-central.org/index.php/Information/HGFlashROM there you see the bootloader-device /dev/mtd1 and the firmimg.bin device /dev/mtd0.

you can install the latest uboot without compiling by flashing the binary to /dev/mtd1 http://nas-central.org/index.php?title= ... from_Linux

this is the critical part of this guide. in case anything goes wrong when flashing uboot you ll need jtag. be warned. it worked for me on three boxes... installing uboot to /dev/mtd1 Code: dd if=u-boot-lsppchd-flash-1.2.0-r2.bin of=/dev/mtd1 bs=1k

in case you have cmp on board of your currently installed execute the cmp command also to be completely sure that it worked.

installing the 2.4.33.3 firmimg.bin to /dev/mtd0 if you do this, i recommend to flash the 2.4.33.3/telnet/ftp-enabled firmimg.bin to flash....this has the functionality you are used to on your kurobox. Image Code: dd if=firmimg.bin of=/dev/mtd0 bs=1k

again, if you have cmp onboard then use it to make sure everything got written correctly.

do both at the same time without rebooting. then you can reboot the first time...you ll see the box behaving differently...hopefully that way: http://www.youtube.com/watch?v=pTPrrUYd8O8

then you effectively can only boot to 2 and 3 blink mode as you only have a bootable kernel in flash (thats why you are flashing the 2.4.33.3-firmimg.bin btw...if you don`t and reboot uboot will have problems to find a kernel to boot). the 1-blink mode will work as well, but in reality it will be 2 blink mode as it defaults to the flash kernel if no kernel is found in /boot

BOTH =

Update to latest 2.6-kernel last desirable thing to do is to update to a late 2.6 by running andre`s webinstaller with variant-uboot mode: http://hvkls.dyndns.org/downloads/docum ... aller.html

Things left to do when upgrading to 2.6 remember that if you update to a 2.6 kernel you will have to modify /dev/fstab...in 2.4 all devices were called /dev/hdaX , in the current 2.6-kernels they use the /dev/sdaX device.

foonas is easier for testing you can between also test http://downloads.foonas.org/foonas/alph ... 062.tar.gz it has the advantage that you do not need to provide a 2.6-kernel as it already has one included...and /etc/fstab is already modified the right way.....so you would only need to untar it to /dev/hda1 and then reboot to 1 blink mode.