It seems....yes, collectd updated at 8/9 (last Friday), so you just missed it.
Now, I see, there're two parts of source codes, feeds are separated for main codes. So the packages' version may not be the same even build with the same main version.
Again, could you please consider to release the "Image Builder" by selecting the "Build the OpenWrt Image Builder" (without "include package repositories") option in the menuconfig?
Actually I don't want to build a private image, there're lots of people used your images and raised lots of feedback. So you are more experienced and your builds are good and stable.
I just wanted to re-assemble your image with my own Apks and configs, so that it's an out-of-box image and I won't need to configure it after installed/upgraded. As you know, update and re-configure the router would be a horrible thing as it may lead to no network for my family. So I have to do such of things in deep night.
With an "Image Builder", we can easily make this kinds of images based on your images in a few minutes.
I am confused by a package difference between this build and the official build for linksys wrt1200ac router.
in the official build the firmware for wifi is this (I think) mwlwifi-firmware-88w8864, but in this build it is CONFIG_PACKAGE_mwlwifi-firmware-88w8897=y .
do I understand this correctly?
am I missing something?
can I use that wifi firmware with my router and get wifi (before I test it and lose wifi I am asking here).
I have run into a weird issue when upgrading to the newer snapshots; input fields are missing throughout LuCI.
The first time I flashed the second partition was with the .img file and kept my settings. I then tried to do a sysupgrade w/ keep settings from the first partition as well. Not a huge deal for now since the build I am on is working just fine, but I would like to be able to have full functionality with updates in the future.. what am I doing wrong? Should I do a fresh update without any configs?
I am confused.
I removed the lower number version and installed the one in your config but then wifi stopped working.
does that mean I dont need that package and should stay with my own configured package?
(I use imagebuilder with 1200ac profile and custom added and removed packages)
How about uninstalling stuff that is included in David's built but not needed in my setup (e.g. Samba, USB mount)? Any idea on how to simplify update process, so that a) settings, b) installed and c) uninstalled packages are preserved between updates?
No, sir. I have not flashed the August build fyi. WRT1900AC
With the command line opkg update passes. The gui, the software screen just keeps loading and update gets stuck on executing. I'm just a gui kind of person.
I'm sorry I've not provided much detail. I was not thinking. This occurs after an initial setup and without changing around any settings. I'm assuming it's plug and play . And, if I am remembering correctly, this did not happen with builds previous to the second to last. Yes, the software screen did not always get stuck on loading.
What can I do? If anything to help. I guess I shall flash Augusts build and see if it is persistent for me.
I just installed your latest version on my WRT1200AC, but automount doesn't work on both USB ports with neither my HDD nor my USB flash drive. When I manually edit the config file I do get it to work.
@robocide Thanks for analysing. I can confirm that the following commands will help with loading pages, but it will not solve the issue. I do not understand what is causing the issue, is it also client related since only a few users experience it? Or ist it even hardware related (different hardware revisions, RAM/memory)?
Also: @davidc502
This Luci hang issue occurs with all four devices on the latest builds. Coming from stock Linksys firmware, i tested all but only got the WRT32X left for testing.
I just tried the following but i think it did not solve the issue completely. Unfortunately this is hard to measure with my productive device. I will try it with another clean flash:
uhttpd config file has an option to automatically redirect to https if possible. That is on by default. Just set this to 0 in /etc/config/uhttpd to enable using http login again: