I just built the latest snapshot (r19393-0392644083)
After installation, some commands hang on execution
Wanted to enable LuCI, but I cannot reach the Web UI after starting nginx service
Internet connection also became unstable. I wanted to revert to my latest working snapshot via sysupgrade but it also hangs, same with mtd.
Was able to restore the snapshot via Rufus and restored my configuration from there.
Can anyone help test the latest snapshot and see if the same problem exists? My device is a NanoPi R2S.
This is the first time I have encountered a problem after upgrading to snapshot with this device.
I am currently on r19234-2c26eb4e48
hnyman
April 8, 2022, 3:46pm
2
Those commands work normally for me with r19393 with ipq806x/R7800.
OpenWrt SNAPSHOT, r19393-0392644083
-----------------------------------------------------
root@router1:~# cat /etc/banner
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt SNAPSHOT, r19393-0392644083
-----------------------------------------------------
root@router1:~# htop
...
0[||| 2.6%] Tasks: 28, 10 thr, 73 kthr; 1 running
1[ 0.0%] Load average: 0.24 0.50 0.24
Mem[||||||||||||||| 71.8M/463M] Uptime: 00:03:52
Swp[ 0K/0K]
PID USER PRI NI VIRT RES SHR S CPU%-MEM% TIME+ Command
5675 root 20 0 2172 1876 940 R 2.0 0.4 0:00.21 htop
5657 root 20 0 952 708 652 S 0.0 0.1 0:00.12 /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -
1 root 20 0 1460 916 720 S 0.0 0.2 0:03.54 /sbin/procd
241 ubus 20 0 1088 720 624 S 0.0 0.2 0:00.35 /sbin/ubusd
242 root 20 0 744 476 440 S 0.0 0.1 0:00.01 /sbin/askfirst /usr/libexec/login.sh
282 root 20 0 864 600 552 S 0.0 0.1 0:00.10 /sbin/urngd
1034 logd 20 0 1228 732 576 S 0.0 0.2 0:00.06 /sbin/logd -S 192
1088 root 20 0 2044 1180 876 S 0.0 0.2 0:00.62 /sbin/rpcd -s /var/run/ubus/ubus.sock -t 30
1 Like
Will be waiting for other results before I retry flashing. Thanks @hnyman for checking.
hnyman
April 8, 2022, 3:52pm
4
SiNONiMiTY:
before I retry flashing
You should like do a "make dirclean" and rebuild everything from scratch, so that you can be sure that there are no buggy/conflicting build artefacts.
1 Like
I actually built from a newly downloaded imagebuilder archive. But I will run make clean and dirclean to make sure there are no conflicts once I rebuild. Thanks.
I think I found the culprit
Was still using an old .config
file during the build process. I rebuilt the image after making sure that everything is fresh. Works properly now.
2 Likes
system
Closed
April 18, 2022, 4:35pm
7
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.