![]() Document loading uImage and uInitramfs from USB (instead of tftp).Update/clean LaCie G762 driver for publication and perform DT conversion.Fix missing USB 3.0 (rear) ports init code.Add info on serial pins (VCC, RX, TX and GROUND).Write initial doc for XOR and cryptographic (CESA) engines.Give a summary of network/system performance.Document grsec/PaX limitations (ARMv5 lacks NX support).Build a list of unsupported hardware parts.Work on userland (sensors config for temperature and fan).Push a first set of patches upstream for comment.Document method to recover NETGEAR-specific patches.Fix halt process (at the moment, it reboots).January 2013: started working on Marvell/NETGEAR-patchedĢ.6.31.8 kernel to extract patches and gather information on.Full conversion toįalttened device tree (FDT). Hardware specs including pictures and datasheets when available, andĪdditional information on support status. February 2013: publication of this page w/ detailed.Kernel patches (readynas support, defconfig, G762 driver, thermalĭriver and CESA DMA) to prepare publication. Step by step install of Debian and 3.8.3 kernel. Kernel (added initialization code in board setup file). March 2013: documentation for serial pins layout.Specification for GMT G762 PWM fan controller. April 2013: made a local copy of a more detailed.May 2013: patch accepted upstream for PCIe init via DT.June 2013: patch accepted upstream for G762 PWM fan.July 2013: patch accepted upstream to reference G762 PWMįan controller in ReadyNAS Duo v2.Enhanced this page to document 3.11 kernel buildĪnd Debian install from scratch. Mainline kernel now includes everything necessary to boot on October 2014: Added a basic script to associate actionsĮven if the todo list below still has some minor remaining entries,.Automatic fan control based on NAS temperature.Here is the main table of contents for the page, with links to Location and be able to make a PDF out of it. Single page to have all the information available in a single Hardware specs to debian and kernel install) has been kept on a ![]() Missed or problems w/ this page, do not hesitate toĭrop me a mail. If you have comments, corrections, additional information I V2) and did the same work to get a recent kernel and Debian Support), I recently bought a NETGEAR ReadyNAS 102 (update of Duo ReadyNAS Duo v2 but with an ARMv7 processor (i.e. Note that if you are looking for a server similar to the a driver to support G762 PWM fan controller (drivers/hwmon/g762.c).dts file (arch/arm/boot/dts/kirkwood-netgear_readynas_duo_v2.dts) The major changes pushed in mainline kernel (via commits Kernel, and completed on September 2013 with the release of 3.11 The efforts was started at the beginning of 2013 on 3.7 Original (Marvell/NETGEAR-patched 2.6.31.8) kernel and custom This page documents some efforts to get a recent kernel and latestĭebian system running on NETGEAR ReadyNAS Duo v2, instead of the You can verify this by going to the FrontView’s Status?Health tab.Debian and upstream kernel on NETGEAR ReadyNAS Upon boot-up, your CPU fan should run at the expected speed. See picture below.ĭownload and install the ToggleSwitchProCPUFan add-on in FrontView’s System?Update?Localtab. Move the CPU fan connector from the main board to the IO card. Shut down the system and remove the side panel by taking out the two screws on the back of the unit and sliding the cover back. All that you’ll need is a Phillips screwdriver. If you have one of these systems, you can apply the easy workaround below to restore the automatic fan control. A number of ReadyNAS Pro systems were shipped with the wrong CPU fan cabling which prevents the fan speed from being temperature controlled, thus forcing the fan to run constantly at its maximum speed (in excess of 4000 RPM).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |