geoffsim

I have test installed on a DELL 745 Core-2 Quad with 8GB RAM with no issues. I even upgraded it without massaging the update file. WOL works fine too, after setting WOL in BIOS and in DSM. I will try upgrading my N54L and N40L after a week or so.

All the information is in this thread and is not out of date. You just need to be able to see through all the chaff. If you are using nanoboot (which set the correct MAC addresses for the ethernet port) then, ssh to your NAS box and edit /etc/synoinfo.conf change the following: wol_enabled_options="" eth0_wol_options="g" if you have more than one ethernet port (I have three), you can set eth1_wol_options="g", and the same for 2, 3 etc. Save and reboot. QED,

I have noticed that a lot of kernel modules will not load in my DS VM. For example, the NFS module will not load: This is also true of a lot of other modules... Apologies, but I have just noticed that this is a repeat of a previous post, viewtopic.php?f=2&t=558&p=2504&hilit=nfsd.ko#p2600

I am running ESXI 5.1 on a Proliant Microserver N54L with 8GB RAM; a cut-down NC360T Dual NIC (to fit x1 slot); an HP P410 raid controller with 512MB cache and BBU; and 4 x Seagate 2TB hard disks in Raid 10 configuration. I am currently running two VMs: pfSense; and DSM 4.2. The DSM vm is running with 1 cpu (2.2GHz) and 2GB ram, and transfer rates using standard virtual disks is 80-100MB/s on average both reading and writing. CPU is around 40-60% during sustained transfer. I've just recently added a D-LINK D140 wireless USB dongle to the vm with no problems either, and am testing DSM as a wireless extender. I toyed with a native installation (I have DSM 4.2 installed on an HP N40L), but have found ESXI to be a far superior solution. BTW to access the boot disk to change the grub.conf mac and serial numbers, add a SCSI disk (pointing to the boot image) whilst DSM is running; ssh to the DSM vm; mount the disk; edit the file; unmounts the disk; remove the disk from the vm; reboot.