![]() |
For those of you that cannot wait to get in touch with the latest hot version of the Unslung-firmware, here is the recipe.I am a new member in the comunity, my first NSLU2 arrived yesterday, and I'm still in the process of unslinging ... so this document helps me to remember the steps taken and, possibly, will help the newbie to get a kickstart. The NSLU2 has been shipped with the firmware V23RA5?. The new version (called 6.x) of Unslung supports usb-hubs on the first port; this can be usefull if you intend, like me, to have an HDD and a printer sharing the first port, and the unslinging disk/flash on a second port. COMPILING the firmwareI use redhat fedora 3 to compile, but the steps that follow should work on every linux distribution. First of all you need something to read:
http://article.gmane.org/gmane.comp.misc.nslu2.linux/11103, http://groups.yahoo.com/group/nslu2-linux/message/10593) now you barely know what are the dangers, and you know that, in the worse case, you should simply reflash your firmware to get the NSLU2 working. Install on your system _boost_, _monotone 0.25_. Download them, unpack them, run ./configure; make && sudo make install (read http://venge.net/monotone/INSTALL) Or yum install monotone boost-devel. The latest Makefile only works with the latest monotone, at least you should have version 0.27. Now make a directory on a ext3 filesystem (some filenames, pathdepths could be to loong to be managed by a fat32); this will be the root for the building tree. mkdir -p /home/slug cd /home/slug mkdir downloads In the "downloads" directoy you will put the two files you download from the Intel site (do you rember? you have read it). It seems that you do not need to put the md5s of those files, they are never checked. get the Makefile wget http://www.nslu2-linux.org/Makefile and start processing it make setup make unslung Now take a break, read something. I am getting some strange error messages, mhhhh .... NOTE: package unslung-rootfs-2.3r63-r8: task do_package: started NOTE: unslung-rootfs contains dangling symlink to /var/tmp/log NOTE: unslung-rootfs contains dangling symlink to /usr/local/localtime NOTE: unslung-rootfs contains dangling symlink to /opt/doc NOTE: Couldn't find shared library provider for libnetwork.so ... Packaged contents of unslung-rootfs into /mnt/shared2/slug/unslung/tmp/deploy/ipk/unslung-rootfs_2.3r63-r8_armeb.ipk NOTE: package unslung-rootfs-2.3r63-r8: task do_package: completed In the thread but everything seems to end gracefully with NOTE: package unslung-image-1.0: completed NOTE: build 200601281100: completed Build statistics: Attempted builds: 34 make[1]: Leaving directory `/mnt/shared2/slug/unslung' After the compilation I issued (probably unusefull): make unslung-image And I got ( cd unslung ; make image) make[1]: Entering directory `/mnt/shared2/slug/unslung' . conf/topdir.conf && test "`pwd`" = "$TOPDIR" || echo "TOPDIR='`pwd`'" > conf/topdir.conf . ./setup-env; exec bitbake "unslung"-image NOTE: Psyco JIT Compiler (http://psyco.sf.net) not available. Install it to increase performance. NOTE: Using cache in '/mnt/shared2/slug/unslung/tmp/cache' NOTE: Parsing finished. 387 cached, 0 parsed, 16 skipped, 0 masked. NOTE: build 200601281239: started OE Build Configuration: BB_VERSION = "1.3.2.1" OE_REVISION = "7a7a7b77dc6e8829e4d9d213431730e12a84aa0b" TARGET_ARCH = "armeb" TARGET_OS = "linux" MACHINE = "nslu2" DISTRO = "unslung" TARGET_FPU = "soft" NOTE: package unslung-image-1.0: started NOTE: package unslung-image-1.0-r11: task do_fetch: started NOTE: package unslung-image-1.0-r11: task do_fetch: completed NOTE: package unslung-image-1.0-r11: task do_rootfs: started NOTE: package unslung-image-1.0-r11: task do_rootfs: completed NOTE: package unslung-image-1.0-r11: task do_build: started NOTE: package unslung-image-1.0-r11: task do_build: completed NOTE: package unslung-image-1.0: completed NOTE: build 200601281239: completed Build statistics: Attempted builds: 1 make[1]: Leaving directory `/mnt/shared2/slug/unslung' In the directory unslung-nslu2-20060128100038.flashdisk.img Flashing the firmwareNow starts the flash reprogramming ... Read
Following the readme file of the firmware 5.5, I flushed successfully the new firmware. UNSLINGINGThis took more than expected. I used 128Mb and 256Mb flash (as unslinging disks) disks and for both the web-interface was not able to format it. In this case read http://www.nslu2-linux.org/wiki/HowTo/UseAMemoryStickAsMainDrive. My partitioning is: 230 Mb for 1st partition 20 Mb for the second 6 Mb for the swap I followed the informations in http://download.berlios.de/unslung/Unslung-5.5-beta-README.txt to unslig, and everithing went file. After reboot, I have created the file #!/bin/sh mount -oremount,noatime /dev/sda1 / /sbin/swapoff /dev/sda3 return 1 This will prevent linux to corrupt the flash-disk because of the frequent rewriting of the inodes and the swap area. Now read my note on http://www.nslu2-linux.org/wiki/HowTo/UseAMemoryStickAsMainDrive where I explain how to ACTIVATE A SWAP PARTITION. The NSLU2 has too few memory, if you don't activate a swap partition on a secondary HDD you risk randoom errors!!! The NSLU is now unslugged! After some time playing around with the version V2.3R63-uNSLUng-6.5-alpha I can say that it works! Configuring CUPShttp://www.nslu2-linux.org/wiki/HowTo/AddPrinter I have an usb Laserjet printer, thus the CUPS installation is very easy.
Configuring the SAMBA file sharing/printer sharingThe Hdd and the printer are attacched through a USB-hub to the first port. The Web interface doesn't see the HDD, thus all the settings have to be done manually.
stay tuned ... do not consider the following links, I attach them only for my purposes, they are not related with the argument: http://thread.gmane.org/gmane.comp.misc.nslu2.linux/884
view ·
edit ·
print ·
history ·
Last edited by tnq.
Based on work by dustinemptyspace, marceln, and rwhitby. Originally by dustinemptyspace. Page last modified on August 05, 2006, at 05:39 PM
|