This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
usbboot [2010/02/08 22:41] – 81.57.81.19 | usbboot [2011/01/24 23:13] (current) – 82.234.233.9 | ||
---|---|---|---|
Line 5: | Line 5: | ||
This project intends to provide help for booting an alternative distribution on a LaCie NAS. An USB key is an attractive way to do that because it is rather non intrusive for the legacy OS and the hardware (no need to open a case). | This project intends to provide help for booting an alternative distribution on a LaCie NAS. An USB key is an attractive way to do that because it is rather non intrusive for the legacy OS and the hardware (no need to open a case). | ||
- | This document provides information on how to boot a Debian ARM on a Network Space v2 board. Any other Linux ARM distributions or any other Kirkwood based board _could_ be used, but hasn' | + | This document provides information on how to boot a Debian ARM on a Network Space v2 board. Any other Linux ARM distributions or any other Kirkwood based board _could_ |
This howto has been written in the hope to be useful but it comes without any warranty. In other words, the lacie-nas project is not responsible if you break your Kirkwood board during an USB boot attempt. So take care! | This howto has been written in the hope to be useful but it comes without any warranty. In other words, the lacie-nas project is not responsible if you break your Kirkwood board during an USB boot attempt. So take care! | ||
Line 14: | Line 14: | ||
You could initialize your USB disk or key with the raw image | You could initialize your USB disk or key with the raw image | ||
- | [[ftp:// | + | [[ftp:// |
This disk image embeds two partitions. The first contains a kernel uImage and the second a Debian (unstable flavour) ARM rootfs. | This disk image embeds two partitions. The first contains a kernel uImage and the second a Debian (unstable flavour) ARM rootfs. | ||
Line 22: | Line 22: | ||
zcat usb_boot_kw_sid_arm.img.gz > / | zcat usb_boot_kw_sid_arm.img.gz > / | ||
- | Please keep in mind that any kind of data that might reside on the target drive would be irremediably lost, so proceed with extreme | + | Please keep in mind that any kind of data that might reside on the target drive would be irremediably lost, so proceed with caution. |
===== U-Boot and USB boot ===== | ===== U-Boot and USB boot ===== | ||
Line 32: | Line 32: | ||
Here is a [[CLUNC|clunc]] command line example: | Here is a [[CLUNC|clunc]] command line example: | ||
| | ||
- | echo -e "setenv bootargs console=ttyS0, | + | echo -e 'setenv bootargs |
usb reset | usb reset | ||
usbboot 0x800000 0:1 | usbboot 0x800000 0:1 | ||
usb stop | usb stop | ||
- | bootm" | + | bootm' |
'' | '' | ||
Line 42: | Line 42: | ||
Here is the [[CLUNC|clunc]] output during a successful USB boot: | Here is the [[CLUNC|clunc]] output during a successful USB boot: | ||
- | simon@X31: | + | simon@X31: |
root=/ | root=/ | ||
usb reset; | usb reset; | ||
usbboot 0x800000 0:1; | usbboot 0x800000 0:1; | ||
usb stop; | usb stop; | ||
- | bootm" | + | bootm' |
- | Marvell>> | + | Marvell>> |
Marvell>> | Marvell>> | ||
(Re)start USB... | (Re)start USB... | ||
Line 133: | Line 133: | ||
===== Troubleshooting ===== | ===== Troubleshooting ===== | ||
- | * CLUNC doesn' | + | * CLUNC doesn' |
* U-Boot fails to scan the USB bus: retry. | * U-Boot fails to scan the USB bus: retry. | ||
- | * How to get my system IP ? use a tool like dhcpdump or set the NAS IP by configuring your dhcp server. | + | * How to get the system IP ? use a tool like dhcpdump or set the NAS IP by configuring your dhcp server. |
* rootfs not found: the SCSI device name for USB key depends on a lots of parameters. On the majority of LaCie products the kernel command line argument "'' | * rootfs not found: the SCSI device name for USB key depends on a lots of parameters. On the majority of LaCie products the kernel command line argument "'' |