Differences

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

--- doc:appunti:hardware:lacie_d2_network_2 [2011/01/26 17:48] – [Dissecting the original kernel] niccolo
+++ doc:appunti:hardware:lacie_d2_network_2 [2014/01/28 10:22] (current) – [Hacking the LaCie d2 Network 2] niccolo
@@ Line 1: / Line 1: @@
 ====== Hacking the LaCie d2 Network 2 ======
-The **LaCie d2 Network 2** is very similar to the **[[lacie_d2_network|LaCie d2 Network]]**, luckily enough the hardware is better and gives better performances. Just one thing is worst than before: the Wake-On-LAN is not longer handled by the U-Boot code, it is handled by the init scripts. This means that if you install a plain GNU/Linux system, you must install special software to get the Wake-On-LAN function (if it is possible at all).
+{{.:lacie:lacie_d2_network.jpg?160  |LaCie d2 Network}}
+The **LaCie d2 Network 2** is very similar to the **[[lacie_d2_network|LaCie d2 Network]]**, luckily enough the hardware is better and gives better performances. Just one thing is worst than before: the Wake-On-LAN is not longer handled by the U-Boot code, it is handled by the init scripts. This means that if you install a plain GNU/Linux system, you must install special software to get the Wake-On-LAN function.
 The LaCie software is changed a lot. May be it is possible get root access without disassembling it, have a look at the [[#the_auto-update_function|Auto-Update function]].
@@ Line 211: / Line 213: @@
 The Wake-On-LAN is **not handled by the U-Boot code** (like in the LaCie d2 Network). When the power switch is onto the ON position, the U-Boot always begins the boot process spinning-on the disk, during the boot process a script checks if the Deep Sleep Mode is active, in that case it halts the disk and wait for the Magic Packet.
+If you install a plain Debian operating system, you can use the **[[#fake_wake-on-lan|Fake Wake-On-LAN]]** software to simulate a Wake-On-LAN.
 ===== Installing Debian =====
@@ Line 319: / Line 323: @@
 </code>
-Extract the gzip data and expand it:
+Say the gzip signature offset is 12504, extract the gzip data and expand it:
 <code>
@@ Line 326: / Line 330: @@
 </code>
-Search again for a gzip signature, extract the gzip data and expand it. The resulting file is the initramfs cpio archive:
+Search again for a gzip signature, extract the gzip data and expand it. The resulting file is the **{{.:lacie:d2net2_initramfs.cpio.gz|initramfs cpio}}** archive:
 <code>
@@ Line 332: / Line 336: @@
 gunzip vmlinux_data2.gz
 mv vmlinux_data2 initramfs.cpio
+mkdir initramfs
+cd initramfs
+cat ../initramfs.cpio | cpio --extract --make-directories  --no-absolute-filenames
 </code>
@@ Line 428: / Line 435: @@
 dd if=uImage of=/dev/sda6
 </code>
+===== Fake Wake-on-LAN =====
+The Ethernet chip does not have WoL capabilities (whereas the old d2 Network does), so we can only simulate it. This is my first attempt to make a software Wake-on-LAN.
+At an early stage of the boot process the **''fake-on-lan''** program suspends the USB power, turn off the blue LED and suspend the disk. Then the program waits for a Wake-on-LAN Magic Packet or for a Power Button press/release before to proceed. The device is effectively powered-on and running the Linux kernel, just the USB, the LED and the disk are turned off. I'm running the program with a **Debian Squeeze** installation.
+You can download the program here: **{{.:lacie:fake-on-lan-20110324.tar.gz|fake-on-lan-20110324.tar.gz}}**.
+===== The EEPROM =====
+The content of the EEPROM is exposed for read and write via the pseudo file **''/sys/bus/i2c/devices/0-0050/eeprom''**, like with the previous d2 Network model, but the meaning is changed. This is what I know:
+^ Offset  ^ Length  ^ Content  ^
+|       0 |       2 | 0x00 0x02              |
+|       2 |       6 | Ethernet MAC address.  |