I have stated several times, including flashing with the stable release image, the switch does not do anything. The problem lies with the gpios, not with the rfkill script.
Unfortunately, I cannot see the allocations of the gpios any longer, since this file "/sys/kernel/debug/gpio" is no longer available.Please see here for the entire story of the problem, which persists on Archer C7 v2 at least.
Ah well that explains. Those images are built with:
#
# Kernel build options
#
CONFIG_KERNEL_BUILD_USER="r00t"
CONFIG_KERNEL_BUILD_DOMAIN=""
CONFIG_KERNEL_PRINTK=y
# CONFIG_KERNEL_CRASHLOG is not set
CONFIG_KERNEL_SWAP=y
# CONFIG_KERNEL_DEBUG_FS is not set
# CONFIG_KERNEL_KALLSYMS is not set
# CONFIG_KERNEL_DEBUG_KERNEL is not set
# CONFIG_KERNEL_DEBUG_INFO is not set
# CONFIG_KERNEL_MAGIC_SYSRQ is not set
# CONFIG_KERNEL_DEBUG_PINCTRL is not set
# CONFIG_KERNEL_DEBUG_GPIO is not set
Whereas my .config contains: (which are the default)
#
# Kernel build options
#
CONFIG_KERNEL_BUILD_USER=""
CONFIG_KERNEL_BUILD_DOMAIN=""
CONFIG_KERNEL_PRINTK=y
CONFIG_KERNEL_CRASHLOG=y
CONFIG_KERNEL_SWAP=y
CONFIG_KERNEL_DEBUG_FS=y
CONFIG_KERNEL_KALLSYMS=y
CONFIG_KERNEL_DEBUG_KERNEL=y
CONFIG_KERNEL_DEBUG_INFO=y
CONFIG_KERNEL_MAGIC_SYSRQ=y
# CONFIG_KERNEL_DEBUG_PINCTRL is not set
# CONFIG_KERNEL_DEBUG_GPIO is not set
So that's why you do not have the file "/sys/kernel/debug/gpio".
EDIT:
I just tried the build you named. You are correct, the switch does not work on that build.
Where is the kernel config? How did you manage to get it for the mod I am using? I made kernel compilations quite often on Linux, but with this router firmware I have no clue how I would call 'make menuconfig' etc.
I would be grateful for a short description how to get there. I read a lot about this "built environment" without understanding a single word .... hope this is not the required procedure
make menuconfig # optional: enable debugfs and probably other stuff
make download world -j4
If you are afraid of building your image yourself... You could try my ath79 C7v2 build...
Don´t think your used "optimized" image is much faster than the ath79 build!
Here you will have flow offload and debugfs... No need for this shortcut fe enabled build and you could install all packages you want with opkg.
I am not that kind of person that gets fascinated by figure comparisons. The reason for using that image is just the assumption that someone has taken a great deal of time to tailor the firmware to this particular router. The discussion on this image is pretty much focussed on speed, too much for me in fact. I will check your build ... only 2 days old ... a little challenge.
Nope. This has always been the part that I did not understand. In a virtual machine, or just on a Linux (Debian) Desktop? A quick check of your link did not improve my knowledge, but I shall check more in depth tomorrow.
You may be right, as previously it was enabled also in my installations (moved to an update few weeks ago only). However, as reported earlier in this thread, the allocation of the switch to gpio.23 has been fixed recently. So cross fingers, I'll find out tomorrow.
For sure you could optimize a lot in code performance, but the most important part of a router is definitely the kernel and not the high optimized packages.
The new 4.14 kernel is optimized for performance instead for size as on kernels <= 4.9
I´m not a fan of the highest compiler optimization option "-O3", because this could break a lot...
The gpio for the switch was fixed in 2016!
As i said, my assumption is that the following config option is disabled in your image: # CONFIG_PACKAGE_kmod-gpio-button-hotplug is not set
Had some problems because I could not use my configs from backup - just copied over network, wireless, firewall, dhcp - as they broke the settings completely. Configured through LuCI.
Works like a charm. Not only the image itself but also the wifi on/off slider. You made my day ... It seems that with the later images
and kmod-gpio-button-hotplug activated this switch is properly set up.
Thanks a million
Oscar
PS: @juppin can I get back to you on your image thread to ask for the vlan tagging for my ISP? Can't get it working so far
It might not be applicable to the Archer C7. The switch remains in the position/action during turn-off/reboot, i.e. the last action is "remembered" by the device.