Thank you, the hint about "/overlay/upper" is great.
I'm already keeping track of all installed extra packages (in a shell script with opkg commands) and their config paths (in /etc/sysupgrade.conf), but i was looking a better "overall" solution for disaster recovery, and the backup of "/overlay/upper" seems what i was looking for.
About the "opkg backup" thing... opkg command has no "backup" parameter, what were you referring to? I use sysupgrade -b to backup config files.
Sorry if that question does not fit here, but I'm thinking of extending my Wifi (main AP is R7800) with an additional repeater (have a WNDR3700 and a Archer C7 with 802.11r). I've read somewhere that WDS is only supported with same brand WiFi NICs (like Qualcom for me).
As the new AP should be mounted to the ceiling I was a bit reluctant to put a R7800 up there (more so my wife I guess) and came across the UniFi AP AC PRO which I was thinking uses the same WIFI NIC, but screw me (or the naming scheme of Qualcom; QCA988x != QCA9984)
First question would be: Would it make sense to use a similar WIFI chip or would any ath9/ath10k device work well with WDS?
I looked around further and found:
CF-E385AC (COMFAST)
ECW5410 (Edge-corE)
FRITZ!Repeater 3000 (AVM)- which I maybe also don't want on my ceiling...
Any experiences with the first two routers (I've never heard of that brands), or any other good AP that works well with R7800? Maybe a dualband 5GHz for doing Client and STA on different channels?
Gonna xpost this over here bc its probably more general to ath10k-ct than hnyman's builds. Once or twice a day I've been having my 5Ghz radio stall out-effectively a crash as no signal is picked up on my scanner-and it doesnt come back up until I restart the wireless bit entirely. Relevant kernel log in the link. Let me know what might be helpful for debug.
Somewhat related, ( more to the IPQ8065/IPQ8064 than R7800 specifically )
Does anyone know how to resize the NAND filesystem on IPQ8065 based devices ( or generate the NAND volume table so I can use pack.py to recreate the nand singleimage ) ?
I have a 256MB nand flash, but rootfs is limited to 64MB - would like to get this to 192 or 200 ish MB by combining unused partitions form the factory image)
From the TOH it looks like it has been done for the R7800 :
when comparing the factory layout with the openWRT layout.
I'm trying to port another IPQ8065 based board ( WPQ865 ) and the factory layout also has lots of partitions that end up being unused by Openwrt ( each partition has a backup, but in the initial flashing script they are not flashed ).
it looks like this tool is used to create the "factory NAND singleimage" for these devices ( IPQ8064 and IPQ8065 ) but it requires a "partition.mbn" file ( ubi volume table / QCA multi partition boot format ? ) - in the wpq865 It looks the MBIB partition which holds the volume table for a " Qualcomm multi partition" )
I have not have not unpacked the R7800's nand-image yet to see if it has a similar partition in there - not called MBIB - will get to that eventually )
also... like resizing the partitions of the R78-00 in posts further up..
using the factory map in uboot, but defining rootfs to be larger in the DTS ( for linux ) works until one does a sysupgrade ( or a large package/ lots of data ) and then upon reboot uboot complains that it cannot find the volume table ( I suspect its because the"Bootconfig" partition has been overwritten, but MBIB - unchanged- still points to it ) . why did they put bootconfig after the rootfs... Grrrr
The factory partition map I'm trying to change :
Hello,
I´m new on this forum and I had bought a Netgear R7800 with running the original Netgear FW from Voxel. Did anybody know how I can test what NAND Flash is built-in? So that I have no reboot problem with openwrt.
And here is the dicussion related to that, where you can see the testing work that I did to prove the return possiblity to the original OEM partition structure:
(messages 1118-1158 of this thread)
Hi! I bought a R7800, and as I tried to set up OpenWrt I hit weird problems.
When I installed the fresh 19.07.5 I couldn't log in, I received the error below:
gismo:~> ssh root@192.168.1.1
ssh_dispatch_run_fatal: Connection to 192.168.1.1 port 22: error in libcrypto
After several retries the login succeeded. But ssh more often failed than succeeded, so I thought to try out 19.07.4 and see how it behaves there. Now the error very rarely came up - in fact only once in over 20 tries.
But now sometimes a package install or upgrade fails, and after 1 or more retries it succeeds. Below is an example:
root@OpenWrt:~# opkg install coreutils
Installing coreutils (8.30-2) to root...
Downloading http://downloads.openwrt.org/releases/19.07.4/packages/arm_cortex-a15_neon-vfpv4/packages/coreutils_8.30-2_arm_cortex-a15_neon-vfpv4.ipk
Segmentation fault
Collected errors:
* opkg_install_pkg: Failed to verify the signature of /var/opkg-lists/openwrt_packages.
* opkg_install_cmd: Cannot install package coreutils.
root@OpenWrt:~# opkg install coreutils
Installing coreutils (8.30-2) to root...
Downloading http://downloads.openwrt.org/releases/19.07.4/packages/arm_cortex-a15_neon-vfpv4/packages/coreutils_8.30-2_arm_cortex-a15_neon-vfpv4.ipk
Collected errors:
* opkg_install_pkg: Failed to verify the signature of /var/opkg-lists/openwrt_packages.
* opkg_install_cmd: Cannot install package coreutils.
root@OpenWrt:~# opkg install coreutils
Installing coreutils (8.30-2) to root...
Downloading http://downloads.openwrt.org/releases/19.07.4/packages/arm_cortex-a15_neon-vfpv4/packages/coreutils_8.30-2_arm_cortex-a15_neon-vfpv4.ipk
Configuring coreutils.
root@OpenWrt:~#
Could it be there's somewhere a fault in hardware?
Is there anything I can do about these weird problems?
