LS Pro Debootstrap Howto - Revision history

Chilledrat: Checksums for Lenny_REQ.tar don't match the linked file; edited other entries to make clear what checksums were generated for, plus additional checksums added. Other minor amendments.

Chilledrat — Tue, 20 Mar 2012 17:33:54 GMT

Checksums for Lenny_REQ.tar don't match the linked file; edited other entries to make clear what checksums were generated for, plus additional checksums added. Other minor amendments.

Show changes

Tx413: /* Files required */

Tx413 — Fri, 06 Mar 2009 16:18:52 GMT

Files required

← Older revision		Revision as of 16:18, 6 March 2009
Line 144:		Line 144:


-	*2 [http://buffalo.nas-central.org/download/Users/davy_gravy/kernelpackages/2.6.26-	+	*2 [http://buffalo.nas-central.org/download/Users/davy_gravy/kernelpackages/2.6.26-update_full_debian.tgz You should use a new kernel (2.6.26 from davy_gravy's package)]
-	update_full_debian.tgz You should use a a new kernel (2.6.26)]	+

	uImage-2.6.26		uImage-2.6.26
Line 158:		Line 157:
	lb_worm's image does not require to change the bootloader, but there comes no kernel with that		lb_worm's image does not require to change the bootloader, but there comes no kernel with that
	image. So take a kernel from one of davy_gravy's packages.		image. So take a kernel from one of davy_gravy's packages.
-
-

	== Once you have all of this. ==		== Once you have all of this. ==

Foowiki: added side note

Foowiki — Fri, 24 Oct 2008 06:35:28 GMT

added side note

← Older revision		Revision as of 06:35, 24 October 2008
Line 166:		Line 166:

	Reboot. And hope it works !		Reboot. And hope it works !
		+	Oh and if you find that the linkstation is rebooting and beeping you can disable the watchdog microapl -a system_set_watchdog 255 . Others have reported that decreasing or turning off the polling will also fix the problem.

Foowiki: done

Foowiki — Fri, 24 Oct 2008 06:27:52 GMT

done

← Older revision		Revision as of 06:27, 24 October 2008
Line 125:		Line 125:


		+	==Files required==

		+	Either get them this way or download them from ---[https://freepository.com/cgi-bin/download.pl?file=lenny_REQ.tar&rev=1.1&cvsroot=/fp1/85VSgDwerUxeILS_PRO&where=none/lenny_REQ.tar lenny_REQ.tar]

		+	*lenny_REQ.tar
		+	md5sum c3bfb83fdeeb7020d6644af11245a1cf
		+	sha1sum 5cb463e7ee6861d4d862546fc3f34e02fc60b0b4
		+	sha256sum lenny_REQ.tar f6044746e9dec3c42fc9fb013193aabaa8fe320504a9714b0077f9713a981420
		+
		+
		+	-----------------
		+	OR

-
-	~~==Files required==~~
-
-	~~Either get them this way or download them from ---~~
	*1 [http://buffalo.nas-central.org/download/ALL_ARM9/ARMel%20Lenny/ lb_worm's new initrd / image. ]		*1 [http://buffalo.nas-central.org/download/ALL_ARM9/ARMel%20Lenny/ lb_worm's new initrd / image. ]
	md5sum 885b1b61f0f00a9459c434dd47ef32f5		md5sum 885b1b61f0f00a9459c434dd47ef32f5
Line 156:		Line 162:

	== Once you have all of this. ==		== Once you have all of this. ==
-	Reboot / get into EM mode. I suggest you copy the files to another computer (so you can pick up the pieces).	+	Reboot / get into EM mode. I suggest you copy the files to another computer (so you can pick up the pieces). Rename the boot_options to the correct name, rename initrd.buff... to the correct name remove the link from the current kernel to the uImage2.6.26 (2.6.26 kernel).
		+	mount /dev/sda2 untar the lenny armel tar / other file / files to it. extract the modules.tar / modules to /lib/modules (move to the appropriate place).
		+
		+	Reboot. And hope it works !

Foowiki: changed to make title

Foowiki — Fri, 24 Oct 2008 06:15:05 GMT

changed to make title

← Older revision		Revision as of 06:15, 24 October 2008
Line 82:		Line 82:

	--------------------------------		--------------------------------
-	==Then you will need the following. ==	+	==Then you will need the following. ==

	*DATA BACKUP - NO ONE BUT YOU CAN BE BLAMED IF YOU FORMAT, MOVE, LOOSE OR DESTROY DATA AND DO NOT		*DATA BACKUP - NO ONE BUT YOU CAN BE BLAMED IF YOU FORMAT, MOVE, LOOSE OR DESTROY DATA AND DO NOT
	HAVE A BACKUP.		HAVE A BACKUP.
		+	*BACKUP OF the WORKING /boot partition (files).

	* The debootstrapped debian armel lenny tar file you made (or other method of storing it).		* The debootstrapped debian armel lenny tar file you made (or other method of storing it).
Line 92:		Line 93:
	the last time i looked at it.		the last time i looked at it.
	*be able to get into and out of safe mode.		*be able to get into and out of safe mode.
		+
	* The files below.		* The files below.
-	* I suggest you give the root filesystem 2GB.	+	* I suggest you give the root filesystem 2GB or the larger 5GB as stated above. For a linkstation
		+	2gb should be fine. However, it is probably safer to give it 5GB.
		+
		+

	My hard is paritioned disk looks like this. I am using ext3 for my data and rootfs file systems.		My hard is paritioned disk looks like this. I am using ext3 for my data and rootfs file systems.
Line 104:		Line 109:
	/dev/sda6 319 38913 310014306 83 Linux		/dev/sda6 319 38913 310014306 83 Linux

-	See the custom partitions page for how to get this kind of a setup.	+	See the custom partitions page for how to get this kind of a setup. (it is referenced above).

	My Fstab looks like		My Fstab looks like
Line 124:		Line 129:


-		+	==Files required==
-		+
-	Files required	+

	Either get them this way or download them from ---		Either get them this way or download them from ---
Line 142:		Line 145:
	sha1sum 2ffc50231d4141bcbb1d82d6b1504fe1411acb2b		sha1sum 2ffc50231d4141bcbb1d82d6b1504fe1411acb2b
	sha256sum 9c86038c3cf48d2667d62bdaabe3b745ea050eb86710c732cd15c91af80610da		sha256sum 9c86038c3cf48d2667d62bdaabe3b745ea050eb86710c732cd15c91af80610da
-


Line 148:		Line 150:


		+	lb_worm's image does not require to change the bootloader, but there comes no kernel with that
		+	image. So take a kernel from one of davy_gravy's packages.



-		+	== Once you have all of this. ==
-	~~lb_worm's image does not require~~ to ~~change~~ the ~~bootloader, but there comes no kernel with that~~	+	Reboot / get into EM mode. I suggest you copy the files to another computer (so you can pick up the pieces).
-	~~image~~. ~~So take a kernel from one of davy_gravy's packages.~~	+
-		+
-	~~-------------------------------~~	+

Foowiki: adding / chopping to make it clearer and easier

Foowiki — Fri, 24 Oct 2008 06:05:08 GMT

adding / chopping to make it clearer and easier

Show changes

Foowiki: added info to get it working

Foowiki — Sun, 12 Oct 2008 03:27:38 GMT

added info to get it working

← Older revision		Revision as of 03:27, 12 October 2008
Line 78:		Line 78:
	as root do --		as root do --
	echo "APT::Install-Recommends 0;" >/etc/apt/apt.conf.d/99recommends		echo "APT::Install-Recommends 0;" >/etc/apt/apt.conf.d/99recommends
		+
		+
		+
		+	Follow @evo's instructions but use your rootfs instead of davy's. I have followed this guide and it works ^^
		+
		+	"@evo
		+	I installed lenny and the new kernel directly on a new harddisk without any changes to Uboot.
		+	I would reccomend not to play around with the bootloader.
		+
		+	lb_worm's image does not require to change the bootloader, but there comes no kernel with that image. So take a kernel from one of davy_gravy's packages.
		+
		+	What i did to install lenny and a new kernel on my linkstation live:
		+
		+	- install the new HD to your desktop PC (disconnect all the other drives)
		+	- start Linux from Live CD (e.g. Knoppix or Parted Magic Live CD: http://buffalo.nas-central.org/index.ph ... ic_live_cd)
		+	- open GParted (with knoppix you have to change the blank root password before)
		+	- delete all existing partitions on the drive
		+	- make new partitions:
		+	- sda1: about 100MB format to ext3
		+	- sda2: about 8 GB format to ext3
		+	- sda4: extended
		+	- sda5 (below sda4): 500MB Linux swap
		+	- sda6 (below sda4): all the rest size format to JFS
		+	- do not use any XFS-Filesystem, the newer kernels have problems with that on ARM, my Linkstation didn't boot with xfs
		+	- download: http://buffalo.nas-central.org/download ... _24.tar.gz
		+	- unzip the archive to the sda2 partition
		+	- copy the file boot_options and initrd.buffalo from here http://buffalo.nas-central.org/download ... l%20Lenny/ to the sda 1 partition
		+	- create blank files linkstation_release, hddrootmode and rootfs_ok at sda1 (i copied the old files from the former linkstation hdd)
		+	- download davy_gravy's image (i used version 0.3, the newer kernel should work as well, but i haven't tested)
		+	- go to directory /boot in davy gravy's tgz file
		+	- there is a file called uImage-<kernelversion>
		+	- copy this file to sda1 and rename it to uImage.buffalo
		+	- go to the /lib/modules directory in the tgz file
		+	- there is a directory named like the kernelversion (for example 2.6.25.6)
		+	- copy this directory (with all subdirectorys) to /lib/modules on sda2, so that it looks like /lib/modules/2.6.25.6
		+	- on sda2 have a look at /etc/network/interfaces to configure it to your needs
		+	- install the new drive to your linkstation
		+	- it should boot up
		+	- make a ssh connection and run depmod -a
		+	- Have fun with it!"

Foowiki: added info to turn recommends off

Foowiki — Fri, 10 Oct 2008 05:56:58 GMT

added info to turn recommends off

← Older revision		Revision as of 05:56, 10 October 2008
Line 74:		Line 74:
	umount /mnt/disk1/proc /mnt/disk1		umount /mnt/disk1/proc /mnt/disk1
	reboot		reboot
		+
		+	On reboot, it probably is a good idea to turn recommends off.
		+	as root do --
		+	echo "APT::Install-Recommends 0;" >/etc/apt/apt.conf.d/99recommends

Tarpman: point to working micro_evtd package

Tarpman — Sat, 31 May 2008 22:22:57 GMT

point to working micro_evtd package

← Older revision		Revision as of 22:22, 31 May 2008
Line 56:		Line 56:
	You also need to install <tt>micro_evtd</tt>, which keeps the watchdog timer in the LS Pro happy, adjusts the fan speed for you, and such. The binaries and configuration files for <tt>micro_evtd</tt> are provided by lb_worm and stored in [http://buffalo.nas-central.org/downloads the downloads area].		You also need to install <tt>micro_evtd</tt>, which keeps the watchdog timer in the LS Pro happy, adjusts the fan speed for you, and such. The binaries and configuration files for <tt>micro_evtd</tt> are provided by lb_worm and stored in [http://buffalo.nas-central.org/downloads the downloads area].
	cd /		cd /
-	wget http://buffalo.nas-central.org/download/Users/~~davy_gravy~~/micro_evtd-~~20080529~~.tar.gz	+	wget http://buffalo.nas-central.org/download/Users/goat/micro_evtd-20080531.tar.gz
-	tar xvzpf micro_evtd-~~20080529~~.tar.gz	+	tar xvzpf micro_evtd-20080531.tar.gz
-	rm micro_evtd-~~20080529~~.tar.gz	+	rm micro_evtd-20080531.tar.gz

	Next, update the package lists and install <tt>sshd</tt> so that you can access the Pro over the network after the install is done, and <tt>udev</tt>, the dynamic <tt>/dev</tt> manager:		Next, update the package lists and install <tt>sshd</tt> so that you can access the Pro over the network after the install is done, and <tt>udev</tt>, the dynamic <tt>/dev</tt> manager:

Tarpman: add mounting of /proc

Tarpman — Sat, 31 May 2008 22:04:31 GMT

add mounting of /proc

← Older revision		Revision as of 22:04, 31 May 2008
Line 35:		Line 35:
	There are two files that need to be configured before the system will run correctly, <tt>/etc/fstab</tt> and <tt>/etc/network/interfaces</tt>. The first describes the layout of filesystems on your disk; the second, as the name implies, configures network interfaces.		There are two files that need to be configured before the system will run correctly, <tt>/etc/fstab</tt> and <tt>/etc/network/interfaces</tt>. The first describes the layout of filesystems on your disk; the second, as the name implies, configures network interfaces.

-	~~You~~ can use <tt>chroot</tt> to enter the system and modify the configuration files:	+	After mounting the <tt>proc</tt> filesystem, you can use <tt>chroot</tt> to enter the system and modify the configuration files:
		+	mount -t proc proc /mnt/disk1/proc
	chroot /mnt/disk1 /bin/bash		chroot /mnt/disk1 /bin/bash
	vi /etc/fstab		vi /etc/fstab
Line 71:		Line 72:
	echo 'LS-GL' > /etc/hostname		echo 'LS-GL' > /etc/hostname
	exit		exit
-	umount /~~dev~~/~~sda2~~	+	umount /mnt/disk1/proc /mnt/disk1
	reboot		reboot