On Sun, 6 Jun 2010, NB wrote:

> Hi Randy,
> 
> My intention to use WOL is solely to switch my pc on from S3, my NAS 
> is located in the loft (attic) hard to get at and previously when 
> using Freenas, it worked great.
> 
> My bios set up is as follows:
> ACPI suspend type             S3 (suspend to Ram)
> -USB resume from S3         Disabled
> Power button function        Instant off
> Wake up by PME# of PCI     Disabled
> Wake up by onChip LAN      Enabled
> Wake up by Alarm              Disabled
> Power on Function              Button Only
> Restore on AC Power loss    Power off

  The intention here, then, is to selectively wake the machine from 
another machine on the same LAN?  Do you also expect it to be awakened 
from a WAN or through routers (the WOL has an interesting ARP issue)?  
What about awakening on selected access (i.e. SMB access)?

> 
> I am using: WOL Magic Packer Sender from:
> http://magicpacket.free.fr/
> 
> I have also tried: Wake on Lan from:
> http://www.aquilatech.com/
> 
> Both above utilities worked under FreeNAS when sending a magic 
> packet to the mac address of the NAS.

  I have a Perl tool that works quite well, and runs well on the 
machines I have tried.

> 
> When using the FreeNAS web gui, there is an option where you can 
> select Wake on Lan, I am not sure what this option changes in the 
> FreeBSD OS itself mind you, maybe it configured the NIC drivers 
> correctly to accept magic packets.

  It changes nothing in the OS, but configures the driver to enable MP 
WOL.  Effectively, the driver must be put into a mode where it 
continues to be powered (at least the network receiver) while the 
machine is otherwise off.  When it gets the Magic Packet, all it does 
is generate a hardware signal (PME: Power Management Event) which 
causes the machine to wake.  The OS is not involved at all, except to 
pass the configuration information to the driver.

> 
> My NIC is an Nvidia nge0, I have tried adding a line "S3-support 
> enabled" under: etc/power.conf: to try and get the NAS to not fully 
> shut down without success.

  (Previously mentioned Matrox driver problem)

> 
> PC Hardware:
> Abit AN8 SLI
> AMD64 Opteron dual core 165
> 2GB of ram
> ide 80GB hdd for the OS
> Matrox PCI Graphics
> 4 x 1.5tb samsung f2 hdd connected to the mobo
> LSI SAS3442E-R Controller
> 4x 2tb samsung f3 hdd connected to the LSI controller
>  I understand that under linux there is ethtool where the NIC 
> drivers can be changed to accept magic packets, I have tried to do 
> the same under dladm but not sure exactly whether this option is 
> available or not.
> 
> You mention turning off the PHY's, how do you do that, I will try it 
> and see if this wil make a difference.

  Actually, you don't want to do this.  The PHY is the hardware that 
connects to the network.  If it is off (at least the receiver), then 
it won't be able to see the packet.  And also (unfortunately), the 
last time I checked, nge was one of the drivers that turned off the 
PHY on suspend.  But even if it still does, it shouldn't be hard to 
make it work.  Your bigger issue, is working through the framebuffer.

> 
> Your help is greatly appreciated, I have been trying to find a 
> solution for a number of days now without success, I do not want to 
> go back to FreeNAS and wish to stay with Opensolaris but without the 
> WOL capability this is impossible for me.

  There might be a Magic Packet WOL solution enabled through the BIOS, 
but not unless the machine can go to sleep.  You might also consider 
acquiring an nVidia FB to replace the Matrox (you might ask on 
driver-discuss which models are best).

> 
> Please let me know if you require anymore information.
> 
> Many thanks for all your help.


  To get you to something that you can use, I have enough.  However, 
to create a good Solaris solution, we could use input on usability 
(i.e. best way to describe controls, interaction with the driver, 
etc.).  Right now, we expect the BIOS to know what to do, and the 
driver not to screw it up (which is way too easy to do).  There is a 
proposed WOL project, and for it to get underway, we would need to 
define the API's from the user down to interaction with drivers.  
Suggestions at any of those levels would be apprciated.


  Cheers!


        ---- Randy
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org

Reply via email to