Hi everyone,
At the beggining I'd like to sorry for my english.
Recently I installed OpenWRT (18.6.1) on my router (Asus RT-AC58U) using stock2openwrt.trx from
4pda.ru
.
Everything works fine, but due to my mistake I lost connection with router (disabled DHCPs). So I followed "soft factory reset" method described OpenWRT's Wiki.
Unfortunately, after 1st command (/overlay) I've received alert (I don't rememebr meaning...). After the whole procedure the router restarted, assigned addresses to PCs, but there is no possibility to connect with router via Web (192.168.1.1) or over SSH ("connection refused"). I found, that the similar situation was described
here
.
But I'm totally newbie in OpenWRT and in general in Linux-world - I don't know, what should I do now to not cause major problems and restore access to the router (re-flash device?)... Could you please help me?
I would go with reflashing just to be sure that everything is as it should be.
https://openwrt.org/toh/asus/rt-ac58u
Use the sysupgrade image
First try to Reset the router, by pressing the reset button for about 10 seconds while the router is on. The leds should start blinking and the router will reboot. Check if after that you can access web/ssh/telnet.
Otherwise try the option to push the image by tftp while the router is booting.
https://openwrt.org/docs/guide-user/installation/generic.flashing.tftp#bootloader_contains_tftp_server
Ok., so I have last 2 questions
Installing once again OpenWRT (sysupgrade) via Web (without saving settings) -> is it ok., solves any potential problems or may produce some problems?
I've checked syslog and found few "problems" - is it ok.?
Example:
[ 18.107081] UBIFS (ubi0:6): recovery needed
Thu Aug 16 07:51:35 2018 kern.info kernel: [ (...)
Thu Aug 16 07:51:35 2018 kern.info kernel: [ 11.667677] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
Thu Aug 16 07:51:35 2018 kern.info kernel: [ 11.674840] hub 4-0:1.0: USB hub found
Thu Aug 16 07:51:35 2018 kern.err kernel: [ 11.682611] hub 4-0:1.0: config failed, hub doesn't have any ports! (err -19)
Thu Aug 16 07:51:35 2018 user.info kernel: [ (...)
Thu Aug 16 07:51:35 2018 kern.notice kernel: [ 17.377936] UBIFS (ubi0:6): background thread "ubifs_bgt0_6" started, PID 209
Thu Aug 16 07:51:35 2018 kern.notice kernel: [ 18.107081] UBIFS (ubi0:6): recovery needed
Thu Aug 16 07:51:35 2018 kern.notice kernel: [ 19.421809] UBIFS (ubi0:6): recovery completed
Thu Aug 16 07:51:35 2018 kern.notice kernel: [ 19.422137] UBIFS (ubi0:6): UBIFS: mounted UBI device 0, volume 6, name "rootfs_data"
Thu Aug 16 07:51:35 2018 kern.notice kernel: [ 19.425204] UBIFS (ubi0:6): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Thu Aug 16 07:51:35 2018 kern.notice kernel: [ 19.433174] UBIFS (ubi0:6): FS size: 69709824 bytes (66 MiB, 549 LEBs), journal size 3428352 bytes (3 MiB, 27 LEBs)
Thu Aug 16 07:51:35 2018 kern.notice kernel: [ 19.442993] UBIFS (ubi0:6): reserved for root: 3292567 bytes (3215 KiB)
Thu Aug 16 07:51:35 2018 kern.notice kernel: [ 19.453233] UBIFS (ubi0:6): media format: w4/r0 (latest is w5/r0), UUID 5D1D0208-7E71-4E68-BA04-C946A78C860E, small LPT model
Thu Aug 16 07:51:35 2018 user.info kernel: [ 19.513678] mount_root: switching to ubifs overlay
Thu Aug 16 07:51:35 2018 user.warn kernel: [ (...)
Thu Aug 16 07:51:35 2018 kern.warn kernel: [ 22.538417] ath10k_ahb a000000.wifi: Direct firmware load for ath10k/QCA4019/hw1.0/firmware-6.bin failed with error -2
Thu Aug 16 07:51:35 2018 kern.warn kernel: [ 22.538465] ath10k_ahb a000000.wifi: Falling back to user helper
Thu Aug 16 07:51:35 2018 kern.err kernel: [ 22.591645] firmware ath10k!QCA4019!hw1.0!firmware-6.bin: firmware_loading_store: map pages failed
Thu Aug 16 07:51:35 2018 kern.info kernel: [ 23.744610] ath10k_ahb a000000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003b00ff sub 0000:0000
Thu Aug 16 07:51:35 2018 kern.info kernel: [ 23.744657] ath10k_ahb a000000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
Thu Aug 16 07:51:35 2018 kern.info kernel: [ 23.798226] ath10k_ahb a000000.wifi: firmware ver 10.4-3.4-00104 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps crc32 6c332c67
Thu Aug 16 07:51:35 2018 kern.info kernel: [ 23.868288] ath10k_ahb a000000.wifi: board_file api 2 bmi_id 0:16 crc32 83549421
Thu Aug 16 07:51:35 2018 kern.info kernel: [ 25.217897] ath10k_ahb a000000.wifi: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1
(...)
Thu Aug 16 07:51:35 2018 kern.warn kernel: [ 25.433799] ath10k_ahb a800000.wifi: Direct firmware load for ath10k/QCA4019/hw1.0/firmware-6.bin failed with error -2
Thu Aug 16 07:51:35 2018 kern.warn kernel: [ 25.433847] ath10k_ahb a800000.wifi: Falling back to user helper
Thu Aug 16 07:51:35 2018 kern.err kernel: [ 25.712135] firmware ath10k!QCA4019!hw1.0!firmware-6.bin: firmware_loading_store: map pages failed
Thu Aug 16 07:51:35 2018 kern.info kernel: [ 25.712774] ath10k_ahb a800000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003b00ff sub 0000:0000
Thu Aug 16 07:51:35 2018 kern.info kernel: [ 25.720118] ath10k_ahb a800000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
Thu Aug 16 07:51:35 2018 kern.info kernel: [ 25.733000] ath10k_ahb a800000.wifi: firmware ver 10.4-3.4-00104 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps crc32 6c332c67
Thu Aug 16 07:51:35 2018 kern.info kernel: [ 25.780442] ath10k_ahb a800000.wifi: board_file api 2 bmi_id 0:17 crc32 83549421
Thu Aug 16 07:51:35 2018 kern.info kernel: [ 27.129622] ath10k_ahb a800000.wifi: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1
(...)
Thu Aug 16 07:51:40 2018 daemon.notice procd: /etc/rc.d/S96led: /etc/rc.common: eval: line 1: can't create /sys/class/leds/rt-ac58u:blue:usb/ports/usb4-port1: Permission denied
Thu Aug 16 07:51:40 2018 daemon.notice procd: /etc/rc.d/S96led: setting up led WAN
Thu Aug 16 07:51:40 2018 daemon.notice procd: /etc/rc.d/S96led: setting up led LAN
Thu Aug 16 07:51:40 2018 daemon.info procd: - init complete -
(...)
Annette:
Installing once again OpenWRT (sysupgrade) via Web (without saving settings) -> is it ok., solves any potential problems or may produce some problems?
It can solve potential config problems (if your config attempts have caused invalid values). Installing again OpenWrt sysupgrade without saving settings basically causes all OpenWrt settings to start again from OpenWrt defaults. If the defaults are ok, you are good. (But if the device's defaults are wrong, then you may have similar problems as with the earlier time(?) )
You can also cause the same effect by resetting the router via LuCI or via "firstboot" command.
