NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
OS6 now works on x86 Legacy WARNING: NO NTGR SUPPORT!
Update: It is now unofficially possible using NTGR images to update legacy hardware to os6.X
See Post #3, for directions to install 6.2.1 on x86 Ultra and Pro Models. (ARM NOT SUPPORTED by this OS)
Be forewarned, this requires a SYSTEM WIPE and likely voids any warranty support from NTGR
Supported so far: pro 2/4/6, ultra 2/4/6, old pro / Pioneer Pro, 2100v2
Not Supported: NVX and 2100v1
Thanks go out to "HomeBrew Anonymous" for making this possible.
Update 2: A firmware image to downgrade back to 4.2.26 is now available. See this thread. While this downgrade should get you a working system again on the supported firmware, be forewarned this requires a SYSTEM WIPE and NetGear also does not provide support for this downgrade. If you have issues seek help on these forums.
Original Post/Gripes
I have been reading these forums since Monday's announcement and there has been a resounding "ooof" regarding the fact the Ultras and Pros are unsupported for future OS improvements.
To clear the air: it would appear Netgear will never support os6 on past hardware. I have almost come to grips with this, and at least they have been open and honest with their forward direction and aren't stringing us along. viewtopic.php?f=138&t=70131
The upside is our devices still work and are mostly stable and eventually we can upgrade to a new shell that has os6 support, but in the meantime our $500-1000 investment is unable to take advantage of modern features we all desire.
I don't think I can add a poll here at RN forums, but I would like to garner support for a 100% unsupported home brew of the os6 on Pro6 units.
If we get enough support perhaps a talented member(s) here would help release a homebrew of sorts.
The 3 main caveats are:
1. Netgear will never be held responsible/your warranty is void
2. A format is required (new FS and OS)
3. Data loss is highly possible
If you are still interested please post a reply to this thread.
mdgm and I have decided that its time to lock this thread. So please do post any new OS6 on Legacy issues on their own threads.
1,274 Replies
Replies have been turned off for this discussion
- See post #3 in this thread. There is currently a link in that post to an image that will update a system straight to 6.1.6.
- Does anyone know where frontview saves the "Wake on LAN" status?
I've witten a dummy default service per simonhang's note:simonhang wrote:
The solution for me is to add a dummy default service which will stop at runlevel 0, 6, . Add command ethtool -s eth0 wol g to the stopping routine and it works just fine even I used frontview interface to shutdown my readynas....
Simon
but I'd like to make it to set (or clear) WOL based on the "Wake on LAN" setting in the fronview Settings screen. Only problem is that I cant find where the config is saved. I thought it would be saved in file /etc/frontview/backup_wol_addr - but this file is empty and never updates/changes.
In fact I've checked all the files in /etc/frontview and none of them change with WOL.
I suspect WOL status is not being saved - at least on my Ultra 2 Plus ...
Any suggestions?
P.S. Will share the service and and install procedure once I get the thing working with fronview settings. - You can check /etc/default/services for WAKE_ON_LAN.
- As the latest topic in the thread deals with WOL, I would like to know if any of you have been able to get it to work on Pro models. I have checked my services as WOL is enabled (i.e.WAKE_ON_LAN=1), however, I have tried sending a magic packet to the nic and nothing ever happens.
Thanks. - It seems that the customers got OS 6 to mostly work with this "legacy" hardware. Yet folks at Netgear are putting the word on the street via various channels that this old, outdated legacy hardware that is still being sold is incompatible with OS6. So is there some type of marketing and sales initiative internally that has deemed it incompatible or are there other reasons why Netgear can't go the 1% to make sure that what is still being sold is supported?
slinky wrote: It seems that the customers got OS 6 to mostly work with this "legacy" hardware. Yet folks at Netgear are putting the word on the street via various channels that this old, outdated legacy hardware that is still being sold is incompatible with OS6. So is there some type of marketing and sales initiative internally that has deemed it incompatible or are there other reasons why Netgear can't go the 1% to make sure that what is still being sold is supported?
Money talks b***s**t walks
Here is your reason.
You can always edit apt source->install the original wheezy kernel with webmin or openmediavault and call it a day ;)- Just out of curiosity, what is the preferred / acceptable /safest way to keep the Apps that are published on the "Available Apps" tab in the GUI up to date?
For example: If you install qBittorrent from the "Available Apps" tab in the GUI, you wind up with version 2.9.8. However, the current version is 3.1.8.
Is there a safe way to upgrade an existing version to the "Latest and Greatest"?
Details please. . .
Thanks in advance, - I'm back. BTW, I really hate this forum's password rule. Make thing unnecessarily complex.
I haven't got chance to get my script yet. But here are a few points.
1. forntview do save the settings and also it does make the necessary change to the Ethernet device. But this still doesn't work. I will explain later.
2. I guess PRO & ULTRA has the same problem. So I believe the workaround works on both
3. Manually set the flag on eth0 device will work, but only work when it was set shortly before shutdown
4. That make me suspect something wrong with the ethernet kernel driver/module as it routinely stuff up the WOL on lower level which the device still reports WOL enabled.
5. My solution is create a dummy service make system to stop it right before shutdown. It that service, it will reenable WOL when existing. That's best way I can find to enable WOL right before power off.
The service is very simple as only one line of code is doing the real job. The rest is just copied from the service template somewhere in /etc. I will try find it if I can find some time at home. - Heres my fix for Wake On LAN on Legacy.
To implement:
First, create a file called wolset.sh containing the following script:
#!/bin/sh
### BEGIN INIT INFO
# Provides: wol
# Required-Start: $remote_fs $syslog $network
# Required-Stop: $remote_fs $syslog $network
# Should-Start: udev
# Default-Start: S
# Default-Stop: 0 6
# Short-Description: Enable / Disable Wake-on-LAN
# Description: WOL not working with 6.1.6. This service checks "WAKE_ON_LAN" setting
# and issues ethtool command to enable / disable Wake On LAN on eth0
### END INIT INFO
PATH=/sbin:/usr/sbin:/bin:/usr/bin
# Get WOL status
. /etc/default/services
do_set () {
if [ "$WAKE_ON_LAN" -eq "1" ] ; then
# Initiate WOL on eth0
ethtool -s eth0 wol g
else
# Disable WOL on eth0
ethtool -s eth0 wol d
fi
}
case "$1" in
start|"")
# Set WOL at start per setting
do_set
;;
restart|reload|force-reload)
echo "Error: argument '$1' not supported" >&2
exit 3
;;
stop)
# Reset WOL at shutdown per setting
do_set
;;
*)
echo "Usage: wolset.sh [start|stop]" >&2
exit 3
;;
esac
:
With root access, execute the following commands:
cp wolset.sh /etc/init.d/wolset.sh
chmod 755 /etc/init.d/wolset.sh
update-rc.d wolset.sh defaults
You can ignore the warning messages from the update-rc.d command.
And thats it. Wake on LAN will be enabled / disabled depending on settings in frontview.
To enable, go to frontview System / Settings and tick "Wake on LAN" under "Power". To disable WOL, clear said tick.
Thanks to Skywalker for helping me with the WAKE_ON_LAN config setting. - Mm.. This sounds like better idea. Read frontview settings rather than set WOL regardless.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
