NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
6.9.5 GPL not posted.
OOM-9
https://kb.netgear.com/2649/NETGEAR-Open-Source-Code-for-Programmers-GPL has a link to 6.9.5 GPL, but the zip itself hasn't been posted yet. https://www.downloads.netgear.com/files/GPL/R...
Hi StephenB,
The 6.9.5 GPL zip file has been posted already. You should now be able to download the file.
Regards,
Same here. I tried to use the generic kernel sources from kernel.org but had the same effect, which would lead me to agree that either it is the .config file that is incorrect, or the kernel is not actually the version reported in uname. I also tried the .config files from 6.9.3 and 6.9.4 but had no better luck with either set of sources, so I'm at a loss to determine exactly what's wrong with the sources. I rolled back to 6.9.4 and accompanying source and Virtualbox drivers compiled fine.
Hoping for a good source archive for 6.10 or a fixed 6.9.5 if possible.
I'm in contact with NTGR. What they told me is:
* Due to a change in their build environment the kernels shipping with the firmware 6.9.5 and newer are no longer compatible with modules you build from the GPL sourcces
* The suggested workaround is to not only install the modules but also the kernel as well. I tested this and it works but I don't really like it
* Thanks to NTGR I received a copy of their new build env and I'll see whether I can make that one work again for general usage
I'll keep you posted on my progress.
-Stefan
Hi WhoCares_
Thanks for your feedback !
Can you share the command to install the kernel ?
make install does not seem to be enough (this is done in Virtual Machine ReadyNAS)
make install sh ./arch/x86/boot/install.sh 4.4.157.x86_64.1 arch/x86/boot/bzImage \ System.map "/boot" Cannot find LILO.Thanks
Hi All,
I got the same message from NTGR as Stefan did. I haven't tried the kernel replacement yet because it can brick the device and that'st too dangerous for my taste for a production device. If Stefan cannot figure out how to avoid this I will have to keep all my RN716 boxes on 6.9.4.
Hello,
can you share the command to install the Kernel ?
"make install" is it enaugh ?
Unfortunately it isn't as easy as a simple "make install". Basically you'd need to make the normally invisible USB flash drive (that's where the kernel of the ReadyNAS is stored) accessible from the OS. Then you have to manually copy the newly built kernel over the original one, adjust some checksums, then unmount the flash drive, reboot and pray that it works - otherwise you may have either to recover from USB or even have bricked your NAS.
That's also why you'd have to take utmost care when building the kernel. A good idea would be to NOT have anything built right into the kernel but using modules wherever possible. But even then you're not 100% safe since some modules silently enable other kernel settings which as a result may leave you with a disfunctional kernel.
In essence: To prevent users without the proper knowledge from accidentially bricking their system by trying things they don't fully understand I won't post a list of commands here. I'd rather prefer to make the new environment work so everyone can safely build kernel modules without the risk of creating a 2-6 disk paperweight.
-Stefan
This obstruction to building modules is not a small issue for customers who need support for a particular device or want to add features to their machines. For 6.10.x, Netgear needs to make a bold notice to let potential upgraders know that there currently is no easy path to customizing modules or the kernel at this time, and no easy path to downgrade from 6.10.
Will the build environment to make this work be downloadable or redistributable?
I'm sure Stefan can come up with a reasonable process to compile with the tools he's been given, but there's no need to make users jump through hoops to customize their gear. I'm also sure this mess is to prevent tampering with the kernel or encrypt and sign some proprietary pieces of software or some blustery nonsense like that, but like all DRM, it only serves to place barriers and traps for legitimate use.
In any case, I'm eager to either see your results or figure out a safe procedure to do this myself, because I rather like having VirtualBox installed, and there's no reason I shouldn't be able to compile some GPL drivers for this GPL kernel, GPL it!
Unsurprisingly, there's very little information as to how to mount the flash memory from a running system. Maybe it's visible from BusyBox, but I usually had other concerns if I was using that mode.
Then, like you're saying, you have to trust that there are no errors in the .config and that you can produce an identical kernel to the one shipped with the OS with no loss of reliability or function. However, if we're going by history and the mistakes and inconsistencies with source archives in the past, that does not instill confidence in the procedure for the future. One should not have to put their NAS at risk to compile a module that works.
Maybe we should drop RMS a note explaining the situation...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
