WOL and HP microservers [SOLVED, but]

[alexey123]

OlafD01, generaly you right. I just type my drivername, I have it unzipped

[ChriZathens]

Add to loader.conf

Code: Select all

if_bge_load="YES"

save driver on your share, for example /mnt/data/if_bge.ko
Then execute as root

Code: Select all

umount /cf
mount /dev/da0a /cf
rm /cf/boot/kernel/if_bge.ko.gz
cp /mnt/data/if_bge.ko /cf/boot/kernel/
reboot

So this procedure survives a reboot? Cool..
But still, including the 9.1 driver in the 9.2 release is the best thing to do IMHO... (Unless, for some reason, it can't be done..)

[alexey123]

if_bge driver for 9.2 release was complete rewrited. So, old patches not works
loader.conf work during boot stage

[OlafD01]

...But still, including the 9.1 driver in the 9.2 release is the best thing to do IMHO... (Unless, for some reason, it can't be done..)

if_bge driver for 9.2 release was complete rewrited. So, old patches not works
loader.conf work during boot stage

When compiling - it must be possible to use the 9.1.0.1.847-if_bge-source (and patches) instead of
the new-9.2.0.1 one, until WOL gets fixed in the rewritten if_bge-source, isn't it ?

Regards, OlafD01

[OlafD01]

Pls also check driver from 925 version

Hi, so it's possible to load the if_bge.ko.gz-Drivers of r943, r925 and r847, as a module, within nas4free_9.2.0.1.943
( 'kldstat' are showing that the drivers are loaded ) .

They all work as a Network-Driver, but only the driver of r943 and r847 advertise the possibility of WOL_MAGIC
( which could be checked with ---> 'ifconfig -m' ) .

And like it's described in this post, it's only possible with the r847-bge-driver, to get WOL up working
within the nas4free_9.2.0.1.943-Build ...

Regards, OlafD01

[ChriZathens]

Hello, OlafD01 and thanks a lot for posting the results of your tests. I said I would test but unfortunately found no time to do so...
To my understanding, now, we have two ways to solve the wol issue:
1. The devs must compile the 9.1 driver in the 9.2 release, but if it is not doable (as mentioned by alexey)
2. Anyone who has a microserver should use the 9.1 driver as a module using loader.conf

Let's hope that we get a final answer from the devs (I hope they can do the first... )

[tses]

Hi experts,

If it is possible please put the driver file if_gbe.ko.gz from Nas4Free 9.1.0.1.847 in a public location for download.

TIA

Yiannis

[ChriZathens]

Here you go..

if_bge.ko.gz

[Alestrix]

Thanks!
I signed up here just to say "it worked"
Replacing the if_bge driver and adding the if_bge_load="YES" in loader.conf did the trick. I can now WOL my HP Microserver from my smartphone and from my PC.
Thanks again,
Alex

PS: I was confused to realize that there is no remount option in FreeBSD mount command!?

[Digi-Quick]

well done "how To", Thanks!
hopefully we don't need to redo this workaround again on the next upcoming releases and this issue will be fixed generally!

[tavik]

Hi,


first of all: thank you for your hints regarding this WOL-related promblem.
Unfortunately, I seem to miss something.
I am using the N54L and an embedded install of Nas4free 9.2.0.1 and I cannot get the WOL feature to work properly.

I copied the *.gz archive and the extracted *.ko file to the kernel directory as described in your tutorial.
Afterwards I added the line within the loader.conf (my first experience with vi, by the way).
However, on startup (apparently when other modules are loaded) the if_bge.ko seems to fail.

While the other "modules" (kernel, opensolaris and zfs) come up with tags like "text", "data" and "syms", if_bge.ko doesn't.
The loading continues for some time and then the startup continues.

kldstat only shows: kernel, zfs.ko, opensolaris.ko, isboot.ko and aio.ko but no if_bge.ko.
Any suggestions or hints?


kind regards

[jabami]

Hi there,

I tried to implement the above mentioned WOL work-around. When executing the statements I get the following:

Code: Select all

nas4free: / # mount /dev/da0a /cf
mount: /dev/da0: Operation not permitted

I´m not very much into Linux and can thus not interpret the command above correctly. What device is "da0a"? As I´m booting from a USB Stick running the emebeded install my USB-Stick is mounted as da0. I tried that too, but it did´nt work either. Any help is very much appreciated.

Best regards,
Jan

Setup: N40L; 4x1TB RED; 16 GB; NAS4free 9.2.0.1 - Shigawire (Revision 943)

[jabami]

Hi there,

just wanted to post that the current Nas4Free Beta NAS4Free-x64-embedded-9.2.0.1.959 does not solve the WOL issue discused in this Thread. Furthermore I´m still not able to execute the above mentioned workaround.

Best regards,
Jan

[Alestrix]

Hi jabami,

Did you execute the mount command as user root?

Gesendet von meinem Nexus 4 mit Tapatalk

[jabami]

Hi Alestrix,

Thanks for answering. I did login as root via ssh and then executed the statements and commands mentioned earlier in this thread.

All the best,
Jan

[Alestrix]

Hi jabami,
You could try
mount /cf
This might also work since mount should get the device name from fstab (or whatever the name is in BSD).
Did the unmount work correctly before the mount?

BR
Alex

Gesendet von meinem Nexus 4 mit Tapatalk

[Digi-Quick]

where is an answer from the Developers on this issue.

as posted above the newest Beta doesn't fix, the same with the new release.

THIS is one signifikant argument against OS!

[raulfg3]

where is an answer from the Developers on this issue.

as posted above the newest Beta doesn't fix, the same with the new release.

THIS is one signifikant argument against OS!

Answer is that developers do not compile old 9.1 drivers to new 9.2 , this can be done in the BSD forums.

You must understand that Nas4Free is a NAS not a O.S and kernel and driver problems are not in the responsabilities of developpers.

[Digi-Quick]

The current version of FreeBSD is 10.0, though there might be no more developement on 9.x.

That means, we have to live with this flaw or patch manually on each update - that's really inefficient.

btw, On the FreeBSD Forum I didn't find any posting for this issue. does this mean, that nobody informed the devs of FreeBSD about this flaw? On other Forums (googlesearch) this issue seems to be well known and currently not fixed - even in FreeBSD 10.

We had a working feature in 9.1 and it's not working in newer Versions, but who cares!

[b0ssman]

just get the HP Micro Server Remote Access Card Kit
it adds ipmi to the microserver and the power on feature becomes independent of wol

[Digi-Quick]

I don 't need IPMI!

"Who's responsible"
"Sorry, we aren't responsible, the others must be responsible!"

an so on and on.

In fact, I'll patch it again and won't install Updates on this system in the future.
Probably the next NAS will rely on OmniOS.

If NVIDIA Or ATI has any Problem with an actual Driver for Windows and it won't be fixed during a few days - a shitstorm would overload the net

This is only Opensource - the "better" System ???? *lol*

[b0ssman]

yes this is open source. if you want the feature and its not there you can patch it yourself.
if you cant do that you can pay someone to do it for you or donate money to the freebsd project and ask them to do it.

and as for nvidia or ati. you actually pay for their products. how much did you pay for nas4free?

and regarding omnios. that is solaris bases. and as far as i know solaris does not support wol at all.

and no you dont need ipmi. you could also leave your server running 24/7. i am just suggesting ipmi, because with that you could actually get a working "wol" setup now.

[crowi]

Probably the next NAS will rely on OmniOS.

Absolutely your choice, but WOL is not supported on the combination Omnios/HP microserver, too.

[jabami]

Dear b0ssmann,

that might be true, but you cannot use ipmi from a router! For example I use a Fritz!Box to wake up my server whenever a client is present in my network. However, there is no ipmi implementation for current >= FritzOS 6.03. This said, even if I have a HP Remote Access Card Kit I´m still not able to start and shutdown my server automatically by means of an automated script running on my router/NAS respectively.
So bringing back the full WOL support as it was in 9.1 is at least for me very desirable.

Cheers,
Jan

[ChriZathens]

IPMI is something like a web interface with which you can control remotely the hardware part of the server (besides the software part) meaning that with it you can even shutdown the server , upgrade BIOS etc, as if you were in front of it, even if you are on the other side of earth...
You can use port forwarding on your router and use IPMI on a server inside your network. The router does not need to support IPMI
Automatically turning on the server, is possible, too ( but I admit not as easy as wol). However if you search the forum, you will see it is doable: viewtopic.php?f=70&t=5984&hilit=useful+scripts (those are VB scripts, but it should be possible to achieve the same thing with shell scripts)

[zoon01]

Hi,
today rev1316, wol patch added to 9.3.0.2 with upstream bge driver.

[ChriZathens]

That's great news!
Thank you very much for this!
Once the next n4f version is out I will try and post feedback!

[sarwanov]

you really did your best.Well done

[Jericho3453409]

Has anyone verified with the latest (1349) release?

[tses]

I made the mistake updating to the latest version ...
The 9.3.0.2.1349 seems that does not detect the onboard LAN adapter at all.
I would appreciate any help or idea.

Yiannis