Differences
This shows you the differences between the selected revision and the current version of the page.
| information:firmware_info 2011/05/15 18:28 | information:firmware_info 2017/09/06 18:38 current | ||
|---|---|---|---|
| Line 17: | Line 17: | ||
| - It copies and links a lot of files from the squashfs image and mtdblock0 | - It copies and links a lot of files from the squashfs image and mtdblock0 | ||
| - mtdblock0 is unmounted | - mtdblock0 is unmounted | ||
| + | - Load /lib/modules/sd_mod.ko and usblp.ko to the kernel | ||
| - adjtimex -t 9960 | - adjtimex -t 9960 | ||
| - Writes time to system | - Writes time to system | ||
| Line 109: | Line 110: | ||
| These contain the more volatile configuration files of the firmware. 0 is represented in mtdchar0 and mtdchar1, while 1 is represented in mtdchar1 and mtdchar2. | These contain the more volatile configuration files of the firmware. 0 is represented in mtdchar0 and mtdchar1, while 1 is represented in mtdchar1 and mtdchar2. | ||
| - | The behaviour of the block devices is rather odd. One can read and write to them with no problems initially, however, on reboot, problems start to occur. If both blocks are mounted and a file is written to both, the data is not saved. If only one block is mounted, and a file written to it, the data is saved to both blocks. You also need to manually unmount to save the data. I haven't tested for deleting data, or in the case of power loss. | + | The behaviour of the block devices is rather odd. One can read and write to them with no problems initially, however, on reboot, problems start to occur. If both blocks are mounted and a file is written to both, the data is not saved. If only one block is mounted, and a file written to it, the data is saved to both blocks. You also sometimes need to manually unmount to save the data. I haven't tested for deleting data, or in the case of power loss. |
| The easiest thing to do is to only deal with 0 as the de-facto configuration block. Never mount or modify 1, and always ensure to unmount after your modifications. | The easiest thing to do is to only deal with 0 as the de-facto configuration block. Never mount or modify 1, and always ensure to unmount after your modifications. | ||
| Line 174: | Line 175: | ||
| When a RAID arrangement is set up between the SATA drives, they are mounted to /dev/md0 or both md0 and md1, depending on the RAID setting. | When a RAID arrangement is set up between the SATA drives, they are mounted to /dev/md0 or both md0 and md1, depending on the RAID setting. | ||
| + | |||
| + | ==== USB printer ==== | ||
| + | |||
| + | USB printers are automatically found and loaded to /dev/usblp0 with the usblp.ko kernel module. | ||
| ==== Loopback devices ==== | ==== Loopback devices ==== | ||
| Line 239: | Line 244: | ||
| ===== Issues ===== | ===== Issues ===== | ||
| - | * /mnt/HD_a2/fun_plug is NOT run when an unformatted hard drive is in the right bay. | + | * Sometimes /mnt/HD_a2/fun_plug is NOT run when an unformatted hard drive is in the right bay. This is because the DNS-323 assigns /dev/sda to the right bay and /dev/sdb to the left bay, oddly. Swap the drives around. |
| * The script waits 30 seconds before executing the fun_plug | * The script waits 30 seconds before executing the fun_plug | ||
| * rc.init.sh is not executed in the background | * rc.init.sh is not executed in the background | ||
| * Hotplug does not automount USB devices | * Hotplug does not automount USB devices | ||
