LaCie NAS wiki

User Tools

Site Tools

Trace:
usbboot

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
usbboot [2010/02/09 17:12] – 217.128.180.65usbboot [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't been tested so far.+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_ probably be used, but has not been tested.
  
 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://lacie-nas.org/usb_boot_kw_sid_arm.img.gz|usb_boot_kw_sid_arm.img]]+[[ftp://lacie-nas.org/images/usb_boot_kw_sid_arm.img.gz|usb_boot_kw_sid_arm.img]]
  
 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 > /dev/sd${scsi_dev_letter}   zcat usb_boot_kw_sid_arm.img.gz > /dev/sd${scsi_dev_letter}
  
-Please keep in mind that any kind of data that might reside on the target drive would be irremediably lost, so proceed with extreme caution!+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,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda2 rootwait+  echo -e 'setenv bootargs ip=dhcp console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda2 rootwait
   usb reset   usb reset
   usbboot 0x800000 0:1   usbboot 0x800000 0:1
   usb stop   usb stop
-  bootm" | ./clunc -i <NAS_IP> -w 60+  bootm' | ./clunc -i <NAS_IP> -t 60
  
 ''NAS-IP'' is the source IP used by U-Boot and Linux for the netconsole. ''NAS-IP'' is the source IP used by U-Boot and Linux for the netconsole.
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:~/work/lacie/src/clunc$ echo -e "setenv bootargs ip=dhcp netconsole=6666@${ipaddr}/,6666@${serverip}/+  simon@X31:~/work/lacie/src/clunc$ echo -e 'setenv bootargs ip=dhcp netconsole=6666@${ipaddr}/,6666@${serverip}/
   root=/dev/sda2 rootwait;   root=/dev/sda2 rootwait;
   usb reset;   usb reset;
   usbboot 0x800000 0:1;   usbboot 0x800000 0:1;
   usb stop;   usb stop;
-  bootm" | ./clunc -i 192.168.0.16 -w 60+  bootm' | ./clunc -i 192.168.0.16 -w 60
   Marvell>> setenv bootargs ip=dhcp netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda2 rootwait;   Marvell>> setenv bootargs ip=dhcp netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda2 rootwait;
   Marvell>> usb reset;   Marvell>> usb reset;
Line 133: Line 133:
 ===== Troubleshooting ===== ===== Troubleshooting =====
  
-  * CLUNC doesn't display the kernel console message: check that the clunc target IP and the netconsole source IP are the same. An utility like tcpdump could provide useful debugging information.+  * CLUNC doesn't display the kernel console message: check that the clunc target IP and the netconsole source IP are the same. An utility like tcpdump could provide useful debugging information. Perhaps you have plug the ethernet cable in the wrong slot, and the kernel assign an ip address to the other one.
  
   * 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 "''root=/dev/sda2''" should be correct. But possibly you will have to turn this into "''root=/dev/sdb2''".   * 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 "''root=/dev/sda2''" should be correct. But possibly you will have to turn this into "''root=/dev/sdb2''".
usbboot.1265731956.txt.gz · Last modified: 2010/02/09 17:12 by 217.128.180.65

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
GNU Free Documentation License 1.3 Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki