Difference between revisions of "User:CuriousMark"

From NAS-Central Buffalo - The Linkstation Wiki
Jump to: navigation, search
(My brand new Linkstation Live is here)
 
(24 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==CuriousMark's Kurobox as a TiVo MediaServer Page==
+
==I have published my first how-to==
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 taskAlso, the thought of putting together all the pieces seemed a bit dauntingWith 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.
+
I put out a page on how to configure SAMBA so that TiVo's TiVo Desktop software doesn't choke on the NASTheir software has a bug(feature) that makes it NAS unfriendlyA tweak to SAMBA is my workaround.  The Page is [[Make your NAS Compatible with TiVo Desktop]].  Please let me know if it is helpful to you on my discussion page.
 +
<BR>
  
===Resources===
+
==I now have a second how-to==
The primary resource is NAS-Central and the wonderful people who are behind it.  I started by asking in the forums.  [http://forum.nas-central.org/viewtopic.php?f=2&t=4546 Here is the thread] that this page is based onIt 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.
+
It was the mess I had here for a very long timeKeeping it here kept from being visible to those who might benefit so I put it out there, even though I still consider it incompleteYou can find it at [[Freelink+UBoot+kernel2.6 on Kurobox]].  Please make suggestions or improvements.
 +
<BR>
  
===Installing U-Boot on a Kurobox HD===
+
==My brand new Linkstation Live is here==
 
+
It is now going to be the box upon which I plan to get TiVo server software running.  I was not successful with the Kurobox, but I think that was due to not having enough RAM (only 64MB) to get pyTivo or Galleon working well enough to considered a successThe Live has 128M and I think it will do much betterFirst I need to explore and see whether to openlink or freelink it. I am thinking since it has some pretty good software on it already, openlink will be the way to go. For starters, I need to figure out what firmware version it has...
Here is Mindbender's directions with ''annotations and hints'' added.
+
Installing Buffalo's NAS Navigator on my PC answered that. It is Firmware version 2.10, and is as current as it gets.
 
+
====how to install LNI uboot + 2.4.33.3-firmimg.bin + freelink to the original kurobox/LS1====
+
 
+
Prerequisites:
+
<blockquote>
+
cd /mnt/<br>
+
wget http://downloads.nas-central.org/LS1_PPC/Bootloader/Uboot/Precompiled/u-boot-lsppchd-flash-1.2.0-r2.bin<br>
+
wget http://downloads.nas-central.org/ALL_LS_KB_PPC/Bootloader/UBoot/FirmimgBins/linux-2.4.33.3-list.mg.2-v3/firmimg.bin<br>
+
wget http://downloads.nas-central.org/LS1_PPC/Distributions/Freelink/TmpImages/tmpimage-FL-1-21-LS1.tgz
+
</blockquote>
+
(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 kuro was only slightly updated, wget was not available to meInstead 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.''
+
<blockquote><code>
+
# 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
+
</code></blockquote>
+
 
+
ok, here is the flash map of the LS1/kurobox original.
+
http://nas-central.org/index.php/Inform ... PCFlashROM
+
there you 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://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/fl2
+
Code:
+
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.
+
 
+
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
+
Code:
+
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 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
+
 
+
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 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.
+

Latest revision as of 17:07, 1 September 2008

I have published my first how-to

I put out a page on how to configure SAMBA so that TiVo's TiVo Desktop software doesn't choke on the NAS. Their software has a bug(feature) that makes it NAS unfriendly. A tweak to SAMBA is my workaround. The Page is Make your NAS Compatible with TiVo Desktop. Please let me know if it is helpful to you on my discussion page.

I now have a second how-to

It was the mess I had here for a very long time. Keeping it here kept from being visible to those who might benefit so I put it out there, even though I still consider it incomplete. You can find it at Freelink+UBoot+kernel2.6 on Kurobox. Please make suggestions or improvements.

My brand new Linkstation Live is here

It is now going to be the box upon which I plan to get TiVo server software running. I was not successful with the Kurobox, but I think that was due to not having enough RAM (only 64MB) to get pyTivo or Galleon working well enough to considered a success. The Live has 128M and I think it will do much better. First I need to explore and see whether to openlink or freelink it. I am thinking since it has some pretty good software on it already, openlink will be the way to go. For starters, I need to figure out what firmware version it has... Installing Buffalo's NAS Navigator on my PC answered that. It is Firmware version 2.10, and is as current as it gets.