Hi,
I don't know why this morning I can't make sysupgrade from my last build update.
First time I have that problem.
I am on wrt3200.
the .bin is in my /tmp, and make cd /tmp and sysupgrade -v /tmp/*.bin" as usual but after the reboot, still the same version, not the new one.... If you need more infos just ask me.
idea?
thanks
Care to tell us how you built the firmware? Buildroot, ImageBuilder, ASU. . .
always buildroot, but as I said, same recipe since a year and never had a problem about it
Please try stopping wifi before sysupgrade. Wifi is not killed during the upgrade thus preventing the upgrade. Has helped in many devices.
Assuming Master Snapshot then. Any additional packages? See more than your one ?.bin in /tmp. Size limitations?
Not a lot to go on - just some ideas.
root@OpenWrt:/tmp# ls
BF_MIMO_Ctrl_Field_Output.txt hosts run
TZ lib shm
board.json lock state
cache log syscfg
collectd.conf luci-indexcache.ea04203a.json sysinfo
dhcp.leases overlay tmp
dnsmasq.d resolv.conf wireguard
etc resolv.conf.d
extroot rrd
Ive just tried the stable 22.03.2 and the same, I reboot on my actual version
I tried also the oem linksys firmware from ethernet cable and still reboot on openwrt actual image
I've read, but what is your recommandation? Remove openssl 3.08?
or something about cryptodev
Until resolved do not use
CONFIG_OPENSSL_ENGINE_BUILTIN_DEVCRYPTO=y
or
CONFIG_PACKAGE_libopenssl-devcrypto=y
hit the subscribe button in the issue to be notified as to progress.
ok thanks,
and I can select = m or really not set at all?
Either being in use will cause the kernel oops.
Should also add that afalg seems fine so you can switch to that in the interim.
I'm compiling and try again to sysupgrade
that should be good?
Enable RFC3779 support (BGP) │ │
│ │ *** Engine/Hardware Support *** │ │
│ │ [*] Enable engine support │ │
│ │ [*] Build chosen engines into libcrypto │ │
│ │ [*] Acceleration support through AF_ALG sockets engine │ │
│ │ [ ] Acceleration support through /dev/crypto (NEW) │ │
│ │ -*- libopenssl-conf......................... /etc/ssl/openssl.cnf config file │ │
│ │ < > libopenssl-gost_engine................. GOST engine for OpenSSL (library) (NEW) │ │
│ │
Symbol: OPENSSL_ENGINE_BUILTIN_DEVCRYPTO [=n] │
│ Type : bool │
│ Defined at package/libs/openssl/Config.in:248 │
│ Prompt: Acceleration support through /dev/crypto │
│ Depends on: PACKAGE_libopenssl [=y] && OPENSSL_ENGINE_BUILTIN [=y] │
│ Location: │
│ -> Libraries │
│ -> SSL │
│ -> libopenssl........................... Open source SSL toolkit (libraries) (PACKAGE_libopenssl [= │
│ -> Enable engine support (OPENSSL_ENGINE [=y]) │
│ (1) -> Build chosen engines into libcrypto (OPENSSL_ENGINE_BUILTIN [=y]) │
│ Selects: PACKAGE_libopenssl-conf [=y]
I did, new build, flashed, same thing, same build again..... Did not work
If you are on an image with openssl devcrypto (any flavour) sysupgrade will fail. You first have to get to an image without, presumably still on the other partition:
#!/bin/sh
#hacked from /lib/upgrade/linksys.sh
cur_boot_part=`/usr/sbin/fw_printenv -n boot_part`
target_firmware=""
if [ "$cur_boot_part" = "1" ]
then
target_firmware="kernel2"
fw_setenv boot_part 2
fw_setenv bootcmd "run altnandboot"
elif [ "$cur_boot_part" = "2" ]
then
target_firmware="kernel1"
fw_setenv boot_part 1
fw_setenv bootcmd "run nandboot"
fi
# re-enable recovery so we get back if the new firmware is broken
fw_setenv auto_recovery yes
echo "$target_firmware"
reboot
the other partition too have openssl devcrypto
Not possible since you cannot flash from an image with same.
Have you confirmed this is actually issue you are experiencing.
serial / tftp in play here?