Anyways, once it is merged, we will not be able to install 24.10.0 via the firmware selector. Only snapshots will become available, and then they will be a part of the 24.10.1 release later, so there should be no rush for you.
I am trying to build vanilla 24.10.0 now, but it's tricky. My Surface Pro tablet with Fedora constantly crashes, and I have to mess with dependencies and other errors. Spent the whole day building again and again. Will give it another try tomorrow.
Strange thing but there is plenty of free space. Almost 7GB. When I am trying to update base-files in OpenWRT 23.05.5, first there is some boot count script access error and then kernel panic with read only.
Yeah no problem , I was just suprised that PR was closed that's why I asked.
I am still waiting router to come from China , it took longer than I expected.
@dunsky is up to speed on building Openwrt and submitting the relevant PR, as they also own the device I have closed mine as I don't own one.
It was just a suggestion, doesn't necessarily have to be correct.
I've tried to build clean vanilla 24.10.0 and got the same issue as I got on 23.05.5 while updating the base-files package. Any help is appreciated.
opkg install base-files
Upgrading base-files on root from 1~6df0e3d02a to 1655~6df0e3d02a...
Downloading https://downloads.openwrt.org/releases/24.10.0/targets/mediatek/filogic/packages/base-files_1655~6df0e3d02a_aarch64_cortex-a53.ipk
umount: devpts busy - remounted read-only
umount: tmpfs busy - remounted read-only
umount: can't remount overlayfs:/overlay read-only
umount: can't remount tmpfs read-only
umount: proc busy - remounted read-only
Removing obsolete file /etc/uci-defaults/99-fudy.sh.
Configuring base-files.
sysctl: error setting key 'vm.min_free_kbytes': Read-only file system
/etc/rc.common: line 32: can't create /proc/sys/net/ipv6/conf/default/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/all/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/br-lan/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/default/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/eth0/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/eth1/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/lo/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/phy0-ap0/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/phy1-ap0/accept_ra: Read-only file system
sysctl: error setting key 'kernel.panic': Read-only file system
sysctl: error setting key 'kernel.core_pattern': Read-only file system
sysctl: error setting key 'fs.suid_dumpable': Read-only file system
sysctl: error setting key 'fs.protected_hardlinks': Read-only file system
sysctl: error setting key 'fs.protected_symlinks': Read-only file system
sysctl: error setting key 'net.core.bpf_jit_enable': Read-only file system
sysctl: error setting key 'net.core.bpf_jit_kallsyms': Read-only file system
sysctl: error setting key 'net.ipv4.conf.default.arp_ignore': Read-only file system
sysctl: error setting key 'net.ipv4.conf.all.arp_ignore': Read-only file system
sysctl: error setting key 'net.ipv4.ip_forward': Read-only file system
sysctl: error setting key 'net.ipv4.icmp_echo_ignore_broadcasts': Read-only file system
sysctl: error setting key 'net.ipv4.icmp_ignore_bogus_error_responses': Read-only file system
sysctl: error setting key 'net.ipv4.igmp_max_memberships': Read-only file system
sysctl: error setting key 'net.ipv4.tcp_fin_timeout': Read-only file system
sysctl: error setting key 'net.ipv4.tcp_keepalive_time': Read-only file system
sysctl: error setting key 'net.ipv4.tcp_syncookies': Read-only file system
sysctl: error setting key 'net.ipv4.tcp_timestamps': Read-only file system
sysctl: error setting key 'net.ipv4.tcp_sack': Read-only file system
sysctl: error setting key 'net.ipv4.tcp_dsack': Read-only file system
sysctl: error setting key 'net.ipv6.conf.default.forwarding': Read-only file system
sysctl: error setting key 'net.ipv6.conf.all.forwarding': Read-only file system
sysctl: error setting key 'net.netfilter.nf_conntrack_acct': Read-only file system
sysctl: error setting key 'net.netfilter.nf_conntrack_checksum': Read-only file system
sysctl: error setting key 'net.netfilter.nf_conntrack_tcp_timeout_established': Read-only file system
sysctl: error setting key 'net.netfilter.nf_conntrack_udp_timeout': Read-only file system
sysctl: error setting key 'net.netfilter.nf_conntrack_udp_timeout_stream': Read-only file system
/etc/rc.common: eval: line 22: can't create /proc/sys/kernel/hostname: Read-only file system
sysctl: error setting key 'vm.min_free_kbytes': Read-only file system
/etc/rc.common: line 32: can't create /proc/sys/net/ipv6/conf/default/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/all/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/br-lan/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/default/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/eth0/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/eth1/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/lo/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/phy0-ap0/accept_ra: Read-only file system
/etc/rc.common: line 34: can't create /proc/sys/net/ipv6/conf/phy1-ap0/accept_ra: Read-only file system
sysctl: error setting key 'kernel.panic': Read-only file system
sysctl: error setting key 'kernel.core_pattern': Read-only file system
sysctl: error setting key 'fs.suid_dumpable': Read-only file system
sysctl: error setting key 'fs.protected_hardlinks': Read-only file system
sysctl: error setting key 'fs.protected_symlinks': Read-only file system
sysctl: error setting key 'net.core.bpf_jit_enable': Read-only file system
sysctl: error setting key 'net.core.bpf_jit_kallsyms': Read-only file system
sysctl: error setting key 'net.ipv4.conf.default.arp_ignore': Read-only file system
sysctl: error setting key 'net.ipv4.conf.all.arp_ignore': Read-only file system
sysctl: error setting key 'net.ipv4.ip_forward': Read-only file system
sysctl: error setting key 'net.ipv4.icmp_echo_ignore_broadcasts': Read-only file system
sysctl: error setting key 'net.ipv4.icmp_ignore_bogus_error_responses': Read-only file system
sysctl: error setting key 'net.ipv4.igmp_max_memberships': Read-only file system
sysctl: error setting key 'net.ipv4.tcp_fin_timeout': Read-only file system
sysctl: error setting key 'net.ipv4.tcp_keepalive_time': Read-only file system
sysctl: error setting key 'net.ipv4.tcp_syncookies': Read-only file system
sysctl: error setting key 'net.ipv4.tcp_timestamps': Read-only file system
sysctl: error setting key 'net.ipv4.tcp_sack': Read-only file system
sysctl: error setting key 'net.ipv4.tcp_dsack': Read-only file system
sysctl: error setting key 'net.ipv6.conf.default.forwarding': Read-only file system
sysctl: error setting key 'net.ipv6.conf.all.forwarding': Read-only file system
sysctl: error setting key 'net.netfilter.nf_conntrack_acct': Read-only file system
sysctl: error setting key 'net.netfilter.nf_conntrack_checksum': Read-only file system
sysctl: error setting key 'net.netfilter.nf_conntrack_tcp_timeout_established': Read-only file system
sysctl: error setting key 'net.netfilter.nf_conntrack_udp_timeout': Read-only file system
sysctl: error setting key 'net.netfilter.nf_conntrack_udp_timeout_stream': Read-only file system
Collected errors:
* resolve_conffiles: Existing conffile /etc/group is different from the conffile in the new package. The new conffile will be placed at /etc/group-opkg.
* resolve_conffiles: Existing conffile /etc/passwd is different from the conffile in the new package. The new conffile will be placed at /etc/passwd-opkg.
* resolve_conffiles: Existing conffile /etc/shadow is different from the conffile in the new package. The new conffile will be placed at /etc/shadow-opkg.
Could it be because I have to configure fstab but I don't know how to do it? I thought buildroot should configure it on it's own...
All other packages are installing or updating fine, I can create new files and edit them. The only issue is with base-files package.
They say it's not recommended to upgrade packages at all. Especially base-files. I just wanted to check out if this is kind of normal or if there is something I've missed in the make menuconfig or in my code edits trying to add support for a new device which makes this thing happen?
Hey guys, maybe I am crazy spending the whole day for that thing, but I've kinda fixed it! I've found out that during building base-files version became 1 because I've been on a --branch v24.10.0 --depth 1 Makefile script could not get PKG_RELEASE:=$(COMMITCOUNT) returning number 1. The real commit count is supposed to be 1655 for 24.10.0 release. You can check filename here: https://downloads.openwrt.org/releases/24.10.0/targets/mediatek/filogic/packages/base-files_1655~6df0e3d02a_aarch64_cortex-a53.ipk
So the bug was base-files_1~6df0e3d02a got an "update" to base-files_1655~6df0e3d02a trying to update it makes the system crash to read only with kernel panic similarly to what happened in past to someone mentioned in my previous comment links with OpenWRT 19 release IIRC.
After I've edited PKG_RELEASE:=1655 and rebuild
make package/base-files/clean && make package/base-files/compile
I've been able to rebuild my firmware, and now opkg doesn't show any updates to the base-files package since there are no real updates to that!
Do you think we should add that to this wiki page in case someone will ever build its vanilla firmware for a new device?
P.S. Just made the same for 23.05.5 but base-files version should be PKG_RELEASE:=1562. It works! No base-files update anymore!
So I finally received this router , installed OpenWRT 24.10 and everything works fine. Only thing I couldn't manage to control is fan. Anyone has any ideas how to implement fan-control in OpenWRT for this specific device? I'm a noob when it comes to coding but if anyone can guide where to start I can provide all the needed data from the router.
I installed fan controller modules from opkg repos but none of them works because fan is not identified by the firmware.Temperature sensors work but fan speed shows nothing.
Hey guys, can any of the maintainers here on the forum review my PR and get it closer to approval? It's been a long time since it's been there.
I've tested this on recent snapshots, and also backported this to 24.10.0 and 23.05.5. Everything seems to work well. No issues at all. Using 24.10.0 as a daily driver on this router now.
Today something strange happened , if anyone has any ideas to help I would appreciate that.
I simply disconnect power cable from the router to move it somewhere else and then when I connect the cable again router's blue LED light which shows that it is working turned to red and I couldn't connect to it through lan or through wifi. Router simply wouldn't get recognized by pc when I connect through lan port , it showed "Unidentified network"
Then with help of @dunsky we managed to get router recognized in pc connecting it through WAN port and pushing power button long while connecting power cable.
I could able to reach to u-boot screen to flash firmware but whichever firmware I tried (openwrt 23.05,24.10, official qwrt, immortalwrt) none of them woks. When I upload the file into router LED turns on red (otherwise it is off in u-boot mode) and then when I click update LED blinks red for a second and turns off then the error comes to screen.
How can I solve this problem anyone knows?
Sad story. Have you been able to replace a faulty hardware with a new router? I think even by the time when they will send you a replacement we will likely to get PR approved anyway.
I'm still waiting for refund seems like in Taobao you can't change the faulty router with a new one. You need to apply refund then order a new router but price has gone up significantly in 1 month. It seems like there is big demand for this specific router from many Chinese users. I'm waiting for price to go down slightly and then I'll reorder.
I feel like something got corrupted in eMMC because when I checked the router with "df -k" command just before it got broken it showed totally nothing but in fact it supposed to show all the mounted partitions. And after restart my guess is due to no partitions are visible (somehow partition table got broken) router simply refused to start. And even bootloader flash didn't work. Most likely I needed to connect through UART and format/reset eMMC totally. Maybe that would help but it's just a guess.
By the way for anyone who wants to buy this router I have to say Huasifei customer service is very responsive and supportive. They tried to find the reason and directed me to apply few solutions on the router but unfortunately nothing helped. In bootloader mode there isn't much you can do and they didn't want me to open the router so I sent it back at the end.
My PR stuck for ages 
I was thinking of asking about the PR today and you already replied.
What is the reason for PR taking so long to be approved?
I think here is the answer Slow issue, PR review on GitHub and inactive maintainers - #28 by Grommish
Okay, it's been merged finally! Will it automatically appear in the next release? Also, I've seen some guys backport their devices to 24.10.0 and 23.05.5, and they appear in the code as well as in the firmware selector later though initially there was no support for these devices. Is it possible, or am I wrong?
It will, and in snapshots within a day or two.
You're not, it'd pop up in the next minor release of current stable (if back ported to 24.10).
so is it better for me to create another PR with a backport to 24.10 if I want it to appear in next stable release?
It'll be in the next stable (25 ?), but not in current, make sure you understand the difference.
Dunno about better, but if you want a stable version soon(er), back porting is your only option.
