I use Nas4Free on HP ProLiant MicroServer. Nas4Free is based on FreeBSD and I and some other people have a problem that is related to the bge NIC driver included in the last FreeBSD kernel. We can't use Wake On Lan feature, even if it is enabled in BIOS. It is an issue with FreeBSD, because we can use WOL with other OS (such as Linux) on the same hw. Someone noticed the WOL feature works if the NIC is connected to a Gigabit Ethernet, but not if the link is 100Mbps. Unfortunately I can't test Gigabit on my system. Someone says older Nas4Free versions worked, for example that based on FreeBSD 9.2. You can read much more details on a specific thread present on Nas4Free forum, here (https://www.nas4free.org/forums/viewtopic.php?f=58&t=4756&start=30).
The same applies for FreeNAS which is also based on FreeBSD. With my HP ProLiant MicroServer N54L I have the same issue that WOL is not available - even with Gigabit ethernet connected. Patches seem to exist (e.g., https://bitbucket.org/w4w/bge-wol-freebsd-10.1-patch).
Created attachment 186870 [details] if_bge.c patched with the bge-WOL patch from https://bitbucket.org/w4w/bge-wol-freebsd-10.1-patch/overview
Created attachment 191147 [details] WOL patch for bge. This patch was posted to PR 171744. The caveat is listed there, though the problem may simply be my laptop. I'll consider closing either this or 171744 as a dup of the other.
Please try not remove group assignment when "Taking" bugs.
Not sure what the fix is, and how 171744 is relevant (it's about the wake command, if I understand correctly). Just wanted to chime in. I have a machine with a bge-driven card for which WOL worked perfectly with 10.3-RELEASE. I activated it with 'ifconfig bge0 wol_magic' and then used the wakeonlan utility on a linux (ubuntu 16.04) machine to wake up the freebsd machine. Yesterday I upgraded to 11.1-RELEASE (something I have put off for ages because I was afraid something would break, but with the EOL coming up I decided to take the risk), and WOL just stopped working. It isn't even advertised anymore as a capability in ifconfig: # ifconfig -m bge0 bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE> capabilities=8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE> ether 00:1e:c9:5b:75:11 hwaddr 00:1e:c9:5b:75:11 inet 10.1.3.8 netmask 0xffffff00 broadcast 10.1.3.255 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active supported media: media autoselect mediaopt flowcontrol media autoselect media 1000baseT mediaopt full-duplex,master media 1000baseT mediaopt full-duplex media 1000baseT mediaopt master media 1000baseT media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP Needless to say, 'ifconfig bge0 wol_magic' doesn't enable it anymore either.
I don't understand why it worked on 10.3. The WOL code was not in bge at the time. The patch is for 12-CURRENT. I'll rework it for 11-STABLE.
The patch attached to this PR also works with stable/11 and releng/11.1.
(In reply to Cy Schubert from comment #6) Hi, thanks for the reply (and the reworked patch). I guess the patch won't go upstream because of the reasons mentioned (ie. potential to blow up boards that can't support enough power when the system is powered down)? I'm also surprised it did work for me. I actually woke up the machine with wake-on-lan to ssh into it and upgrade it to 11.1-RELEASE.
(In reply to Koen Martens from comment #8) That bug has been fixed in the latest patch I posted here. No worries about drawing too much current when powered off any more. I've been using it and previous versions of this patch on my laptop (only machine I have with bge) for about a year. I suppose I should submit the patch in phabricator for review prior to commit.
There still have issue with WOL patch for bge driver on FreeBSD 11.2. It seems there is boot issues, see here: https://www.xigmanas.com/forums/viewtopic.php?f=78&t=13807#p85480
(In reply to NK from comment #10) Sketchy details. There's nothing to go on. The WOL patch was developed for 12-CURRENT only. The only issue is a system will not halt -p after being woken by WOL, but will after a reboot. I'll try to port it back to 11-STABLE if anyone is interested.
(In reply to Cy Schubert from comment #11) I would very much appreciate it. Thanks a lot for your efforts!
Created attachment 197700 [details] WOL patch for stable/11 Same patch, for stable/11. I haven't tried to build or use this particular patch on stable/11. However a previous version was developed for current/11 at the time. This patch has the same problem as the -CURRENT patch, the system will reboot on halt -p the first time around. I'm not sure of the solution for this yet.
I had 11.1 patched with https://github.com/NamTaf/if_bge_wol and it worked can I apply the same patch on 11.2 p4 ? I only need this for WOL.
Any hope to make it work please ? I have an old but full functional HP Microserver and I can't upgrade because of this issue. A fix would really appreciated
Created attachment 212388 [details] Latest WOL patch for bge The patch generally works, I currently use it. However halt -p after a WOL will not power off the machine but reboot it. Only after the next reboot will it be able to power off. I don't know if this is isolated to my laptop only or if this is a general problem. Try the patch if it has the same behavior as on my laptop and report here or back to me your result. Ping me if the patch posted here doesn't apply. I'll backport the one from 13-CURRENT again.
*** Bug 171744 has been marked as a duplicate of this bug. ***
Hy guys, Can anyone explain me how to patch the driver? I cannot find the file if_bge.c anywhere... is there a way to make it to one of the next version? this would be really appreciated! Best Tony
(In reply to tony from comment #18) > Can anyone explain me how to patch the driver? copy your choice of one of the 2 attached diff files to /usr/src. # cd /usr/src # patch < your-chosen-diff-file Done. see man diff && man patch for greater detail(s). :-) > I cannot find the file if_bge.c anywhere... # cd /usr/src # find . -type f -name if_bge.c > is there a way to make it to one of the next version? > this would be really appreciated! HTH --Chris
(In reply to Chris Hutchinson from comment #19) The latest patch is for 14-CURRENT. It works here except for a bug which I cannot track down. The bug is that after waking the machine the next time you do a halt -p the machine will reboot if the machine hasn't been rebooted using reboot in the mean time. It appears that some kind of status bit has been set in the NIC that when the machine powers itself off the first time after being woken it powers itself back on again. Only that once and only if there haven't been any reboots prior to that. Otherwise this patch would have been committed long ago. Please apply the patch and let me know if you experience this or if it is simply my laptop that has this problem. (My laptop doesn't experience this when booted from Windows 10 or Fedora, only with the patch I cobbled up for FreeBSD.)
I use acer note 3820. This machine have alc interface. alc support wol. I can wol this machine on releng/13. But poweroff do reboot. I think wol poweroff problem is not driver issue. I doubt ACPI or other code.
Mine is an Acer 4752, same problem. Windows and Fedora don't have the problem. This suggests I've missed something in my patch. But poweroff does work after that initial reboot following WOL. I suspect this is some bit in a NIC register that fails to be reset after WOL power up.
With "Latest WOL patch for bge" on FreeBSD 13/HPE ProLiant N36L multiple shutdown -p/wake works fine.
(In reply to Peter Libassi from comment #23) Thank you for the confirmation and feedback Peter
(In reply to Cy Schubert from comment #20) I successfully use the patch bge-wol-13-current-200313.diff on FreeBSD-13. I use it on a HP ML110 G6 server. Usable after shutdown -p. I didn't test halt command though. However, I had to "buildkernel" and "installkernel after a freebsd-update fetch install to get to FreeBSD-13 p3. Hassle 8-) Why don't you submit your patch to FreeBSD project so they can "integrate" it in the kernel?
(In reply to Michel Marcon from comment #25) I am a committer. I will commit it when one last bug in the patch has been fixed. After using WOL to wake a bge equipped system, the next power off is in fact a power cycle (poweroff/poweron, similar to a reboot but you hear the system power off for a second or less). Do you experience this bug when you applied the patch? The bug manifests itself on Acer laptops equipped with bge0. My Acer exhibits the behavior but doesn't under Windows. I must conclude that the patch still needs set or clear a bge register. Let me know if your system experiences the poweroff/poweron bug if you poweroff or halt -p anytime following a wake from WOL. The bug does not manifest itself if the machine is rebooted before poweroff or halt -p: i.e. WOL the system, reboot, then power off does not exhibit the bug. Whereas WOL, then power off manifests the bug.
(In reply to HIROKI MORI from comment #21) My Acer 4752 with bge exhibits the bug. My Acer 3620 with rl does not exhibit the bug. Noting that your Acer 3820 with alc also has the bug might mean that there is an ACPI or other issue. (My 4752 exhibits other ACPI bugs that the 3620 did not under FreeBSD.) If other people can confirm that this is not a bug on their systems (and this bug only manifests itself on Acer laptops), I will commit the patch and MFC it. I do want people to confirm that it works fully on their computers before committing this patch.
*** Bug 184718 has been marked as a duplicate of this bug. ***
*** Bug 177184 has been marked as a duplicate of this bug. ***
(In reply to Michel Marcon from comment #25) Please halt test.
(In reply to Cy Schubert from comment #30) On my FreeBSD 13/HPE ProLiant N36L with the latest WOL patch I did the following test: 1. wake 2. shutdown -h now, went down to halt state and stayed there 3. cycled power 4. shutdown -p now 5. wake, succeful Let me know if you want me to do the test differently.
(In reply to Peter Libassi from comment #31) This is perfect. The problem isn't the patch but Acer ACPI. I will commit this patch then.
PR/226763 is not related to this. Different NIC (re).
Phabricator review is at https://reviews.freebsd.org/D31834.
(In reply to Peter Libassi from comment #31) On my HP Proliant server HP ML110 G6 w/ FreeBSD 13, I've done exactly the same procédure (Shutdown -h, cycle power, shutdown -p, and then wake WOL) and it works. But then, after a simple "shutdown -p now", WOL doesn't work.
(In reply to Michel Marcon from comment #35) What does ifconfig of the interface show? Are any of the WOL flags still on?
(In reply to Cy Schubert from comment #36) Yep. The flag WOL_MAGIC is on: zombie/usr/home/cmic >ifconfig bge0 bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=c219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO,LINKSTATE> ether 2c:41:38:87:3a:6f inet 192.168.1.102 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
(In reply to Michel Marcon from comment #37) To make sure I understand this correctly, you followed the test procedure of: 1. Enable WOL. 2. halt -p or shutdown -p 3. WOL the machine (it works) 4. shutdown -p and the machine fails to halt. Is this correct?
Removed regression flag because this is not a regression. bge(4) never supported WOL. The patch adds WOL support to bge(4).
(In reply to Michel Marcon from comment #37) In the absence of a reply, I will assume this is the same problem experienced on Acer laptops. This proves that the problem is not caused by Acer ACPI but that the patch is incomplete.
(In reply to Cy Schubert from comment #40) Sorry to be so late. After a lots of "shutdown -p now" and restarts I can only say that the behaviour is erratic: sometimes WOL works, sometimes not. (bang my head on the wall ?) But stay tuneed: I keep on searching for a reproductible behaviour. By the way, are you interested by a lot of acpi lines in /var/log/messages?
(In reply to Michel Marcon from comment #41) Actually, it is not erratic at all. But your tests have confirmed why I haven't committed it yet. There is something lacking and I haven't discovered it yet. Here are two scenarios: Your test: 1. halt -p. 2. Machine powers off. 3. WOL wakes the machine. 4. halt -p. 5. Machine appears to reboot. It doesn't reboot, actually. It powers off but a second later it powers back on again. You can tell by the sound of the CPU fan. The second scenario: 1. halt -p 2. Machine powers off. 3. WOL wakes the machine. 4. Reboot (like after an installkernel or other reason). 5. halt -p. 6. WOL wakes the macihne. 7. halt -p. 8. Machine powers off. 9. WOL will work. The difference is the reboot in the second scenario. This suggests that something is missing from the patch to reset a bit in a bge(4) hardware register to not wake it a second time. This could also be an ACPI issue. (HP and Acer ACPI rely on WMI.) This is the reason the patch hasn't been committed yet. If you remember to do a scheduled reboot sometime after a WOL it will appear fine. I will commit this patch when this last bug has been resolved.
hello Any news from this bug ? I updated wy Proliant server with freebsd 12.3, but nothing new at the moment... Best and thank you
Hello, any news? I installed FreeBSD 13.2-p2 to my HPE Proliant Microserver Gen10 (Broadcom 5720 with bge driver), and I could not wake it by WoL. 1. poweron 2. poweroff by the power button on Gen10 3. WoL not works
This project seems to be abandoned. I e-mailed the indicated official maintainer, received no response. If anybody takes over, my offer below still stands. As long as I have those computers. Regards, Keve -------- Original Message -------- From: keve@xxxxxxxxxxxxxxx To: cy@FreeBSD.xxx Subject: fbsd bug 218579 - bge(4): Wake on Lan (WoL) does not work Date: Sun, 3 Sep 2023 12:35:13 +0200 Hello Cy Schubert, I have a HP T610 Thin Client and a HP MicroServer N40L, both with an on-board bge interface. I am happy to run tests for you, or can even provide you with an ssh access to these machines. Let me know if any of that helps you in taking the bge-WOL issue further. Regards, Keve Nagy * Debrecen * Hungary
(In reply to Keve Nagy from comment #45) Are you able to test the patch on your machine. On my machine it will wake the machine but any subsequent poweroff it will briefly power itself of and on again. However if I reboot first the subsequent poweroff will work. I don't know if this is unique to my Acer laptop, with its various ACPI issues, or if this is problem with my patch. So far I haven't received much feedback regarding this issue. Until it can be determined that this only affects my Acer I'm reluctant to commit the patch.
No problem. I will test it in the next 2 weeks and report back with my findings.
Created attachment 248615 [details] Files and logs collected during testing the bge-patch, 2024-FEB The summary is: * the bge_wol patch works on 13.2R * the bge_wol patch makes no improvement on 14.0R Used two computers for the tests. A HP T610 Thin Client with an onboard bge interface, which boots in UEFI+GPT mode only. And a HP MicroServer N40L with an onboard bge interface, which boots in BIOS+MBR mode only. Both computers were set up to dual-boot between FreeBSD 13.2R and FreeBSD 14.0R, with sources installed, and "freebsd-update fetch install" applied. Before my tests, I connected the bge interface of both computers to an isolated network switch. For reference I also connected a third computer without a bge interface, this had em0. Booted a live Linux from an USB stick on one of the 3 computers at a time, shut it down, and successfully woke it up via FreeBSD's built in "wake aa:bb:cc:dd:ee:ff" command to verify that BIOS settings, cabling, switch, collected addresses are all OK and WOL actually works for each of them. Then ... * For each system, I booted the factory GENERIC kernel, run "ifconfig" to see what it shows (WOL_MAGIC was never shown, even an "ifconfig bge0 wol" did not activate it), issued a "shutdown -p now", and tried to wake it from one of the other hosts. WOL with the factory kernel never woke the bge-based nodes, but always woke the em-based computer (which did always show WOL_MAGIC in ifconfig output). Then booted the system again, issued a "cd /usr/src", followed by a "patch < ~/if_bge_patch240113.diff" which always completed successfully. Then "make buildkernel", followed by "make installkernel", and "shutdown -r now". ** I booted the bge-patched GENERIC kernel, run "ifconfig" to see what it shows, issued a "shutdown -p now", and tried to wake it from one of the other hosts. Both bge-based nodes successfully woke when they were "shutdown -p now" from under a bge-patched FreeBSD 13.2, but never woke when they were "shutdown -p now" from under a bge-patched FreeBSD 14.0. The em-based host always woke, regardless of being shut down from under FreeBSD 13.2 or 14.0. The bge-patched 13.2 GENERIC kernel works reliably. I tried multiple times. Also tried doing a "shutdown -r now" after a successful WOL and then doing a "shutdown -p now". Always worked perfectly fine. In none of the cases I experienced that the computer booted up unexpectedly after a "shutdown -p now". So it never behaved like a "shutdown -r". Except when I explicitly run a "shutdown -r". See attached files. Let me know if I can help any further. Regards, Keve
Booting the bge-patched GENERIC kernel DOES ALWAYS display WOL_MAGIC in the output of "ifconfig bge0", without needing an "ifconfig bge0 wol". Yet, WOL only wakes the host when it was shut down from a bge-patched 13.2, and does not wake it when it was shut down from a bge-patched 14.0. A ...132n.log was made on 13.2 NOT yet patched, factory kernel. A ...140p.log was made on a 14.0 with a bge-PATCHED kernel. So n = not-patched, p = patched.
If I understand correctly, WOL automatically displays on 13R but not 14R? Correct? It should _not_ automatically display. It should only display after WOL has been enabled, like this: ifconfig_bge0="DHCP wol"
Created attachment 248888 [details] Latest version of the patch for 15-CURRENT I've been using this patch for over a year. Use this patch on 15-CURRENT.
Created attachment 248890 [details] Latest version of patch for 14-STABLE Use this patch on 14-STABLE.
Created attachment 248891 [details] 13-STABLE version of the patch Use this patch on 13-STABLE.
When bge(4) is a member of a lagg(4) you will not see WOL listed in ifconfig bge0 output. You must /etc/rc.d/netif stop lagg0 before power off in /etc/rc.shutdown or /etc/rc.final. And when bge(4) is a member of a lagg(4) you must enable it only through rc.conf and either boot or use service netif. The reason for this is that lagg(4) has no knowledge of WOL. bge(4) will inherit lagg(4)'s view of the interface (without WOL).
(In reply to Cy Schubert from comment #50) With my bge-patched GENERIC kernels, WOL displayed on both 13.2R and 14.0R by default, without the need to issue an `ifconfig bge0 wol` or setting this in rc.conf. However, the wake-on-lan magic packet only woke the computers after they were shut down from the patched 13.2R, and did not wake either of them when they were shut down from the patched 14.0R or a not-yet-patched kernel from either version.
I will also try your new patch on 13.2R and 14.0R, and report back with my findings.
Created attachment 249663 [details] bge WOL patch 2024-03-03 test on FreeBSD amd64 13.3R
Created attachment 249664 [details] bge WOL patch 2024-03-03 test on FreeBSD amd64 14.0R
Uploaded the new test logs. With the most recently shared patch applied, bge WOL works on both 13.3R and 14.0R. Mind you, booting the patched GENERIC kernel automatically enables WOL_MAGIC, no need to issue an "ifconfig bge0 wol". In fact, that command does not seem to change anything at all. For reference, I also included the "ifconfig em0" output from a Dell Optiplex 7050 (has no bge). And the behaviour is the same there. WOL_MAGIC is immediately enabled for the em0, no need for an "ifconfig em0 wol". Although, this command does seem to enable other WOL_ options for the em0, and those options I have never seen with the bge interface. Summary: as much as I can tell, these bge patches achieve WOL, work reliably on both 13R and 14R. Tested on two different computer models: HP T610 Thin Client, HP MicroServer N40L. I hope to see this incorporated to the base system.
(In reply to Keve Nagy from comment #59) And when the machines are powered off following an earlier WOL, do they power off? Or do they reboot? My Acer laptop will momentarily power off, then power itself back on again if WOL was previously received and no intervening reboot performed. This could be an Acer ACPI problem -- there are other Acer ACPI problems which are either resolved or worsened by successive ACPI imports. If the ifconfig wol keyword doesn't work, that's a problem. It works properly here on 15-CURRENT and did on 14-CURRENT. The two main things I need to understand from people testing this patch are: 1. Does power off still work if the system was woken using WOL and no intervening reboot performed? (This is busted on my Acer laptop.) 2. Does ifconfig wol do anything? This works here. One caveat. ifconfig wol will not work if bge(4) is a member of lagg(4). This is a lagg(4) problem. Anyone testing this patch must not use lagg(4) or they must implement a lagg(4) in rc.shutdown or rc.final. lagg(4) disables WOL. lagg(4) masks any function supported by underlying interfaces unless that same function has been implemented in lagg(4). Can you please answer the two questions above? Thanks.
Q1. Does power off still work if the system was woken using WOL and no intervening reboot performed? A1. In my tests, I experienced no unexpected reboots/autostarts. I always finished with a "shutdown -p now;exit" command, and the computer properly shut down and powered off each time. Regarless of which computer I used (T610 or MicroServer), which version of FreeBSD I used (13.3R or 14.0R), or which kernel I booted (bge patched GENERIC or factory GENERIC). So powering down worked always fine. The difference in unpatched or patched kernel meant that "wake" did wake the computer up or did not. When I used "shutdown -r now", THEN and ONLY THEN the computer automatically restarted after shutting down. Q2. Does ifconfig wol do anything? A2. On those of my computers with an on-board bge interface, "ifconfig bge0 wol" seems to make no difference at all. If I boot with the factory GENERIC kernel, then WOL_MAGIC is off by default, and this command does not enable it. If I boot the bge-patched GENERIC kernel, then WOL_MAGIC is enabled by default, and it stays that way after an "ifconfig bge0 wol" with nothing new added either. Hence, again, this command seems to make no difference. On the Optiplex 7050 with no bge interface and an on-board em interface, "ifconfig em0 wol" enables WOL_MAGIC and some other WOL_ options. The uploaded files will show you all details about this. I stay away from FREEBSD-CURRENT, but if you see the bge interface on 14-CURRENT coming up by default without WOL_MAGIC and then "ifconfig bge0 wol" enables WOL_MAGIC, then there is already a significant difference between 14-RELEASE and 14-CURRENT.
(In reply to Keve Nagy from comment #61) Q1, A1: This is not what I asked. I did not ask if there were any unexpected reboots or crashes. I did ask, when a subsequent poweroff without subsequent intervening reboot, that the machine rebooted instead of power off. Subsequent reboot works normally. Subsequent poweroff does not without a subsequent reboot first. I assume you have the same problem I do then (meaning this patch is not ready for commit). Q2, A2: This is a problem. Was this on stable/14 or stable/13? It should not be enabled by default. It should be enabled only after enabling it.
The second issue is a non-issue.
No problem. To clarify, I was not talking about crashes either. You mentioned that after a successful WOL, when you shut your computer down, it did not stay powered off, instead moments later it automatically started. That is an automated start-up you did not expect. In other words, unexpected. Again, I experienced no such phenomena. When I issued a "shutdown -p", my test computers always powered down properly and always stayed off. Regardless of how they were started up in advance, manually by their power button or woken by magic packet. To further clarify, they also properly powered down and stayed turned off if I sent WOL magic packets to them while they were on, even if it was moments before "shutdown". However, I did not test the particular case when a WOL magic packet is sent to the computer WHILE it is already in the process of shutting down. None of my tests were performed on -STABLE or -CURRENT branch. I only tested on -RELEASE. The experience now was the same on 13.3R and 14.0R. With my previous set of tests, WOL only woke the computer if it was shut down from a bge-pached 13.2R kernel, and did not wake it when it was shut down from a bge-patched 14.0R. In that sense, the latest patches are better. My problem was that the bge-based computer could not be woken up once it was powered down. With these patches, they wake up exactly as expected, on 13.3R and on 14.0R too. So the problem I had, is now fixed. I don't really care that WOL_MAGIC is automatically enabled and that I do not need to run an "ifconfig bge0 wol". The em0 in my Optiplex does exactly the same. I would call THIS the expected behaviour. Others may disagree. I can do more tests in May, if needed.
(In reply to Keve Nagy from comment #64) Thanks for testing. This is not an Acer ACPI problem then. It's likely a BGE register that requires reset.