always been like that for me no matter the firmware... (then again... your hostapd output is kinda different)
anyways... I will switch it back to something else... any ideas... go back to official 2020 version? or linux-firmware?
Anything that works ^^
Same here.
It would be great to be able to use the RPi WiFi despite its short range! 
By the way, in my logs you probably noticed that before the first cli prompt I get a couple of red messages. Even now, with the WiFi already working if I ssh to the RPi i get this:
...
#FriFeb415:34:542022 plugin: rrd_update_r failed: /tmp/rrd/rpi4-dca632da63/processes/ps_state-sleeping.rrd: ope
FriFeb415:34:542022 plugin: rrd_update_r failed: /tmp/rrd/rpi4-dca632da63/processes-dnsmasq/ps_stacksize.rrd:
FriFeb415:34:542022 plugin: rrd_update_r failed: /tmp/rrd/rpi4-dca632da63/processes-dropbear/ps_rss.rrd: openi
update-unavailable
root@rpi4-dca6000003 /39#
Is this some kind of other error?
Regards
new build wifi fw is now totally stock... ( 5.0.77-59 )
all custom mods are gone
(sorry 400 or bluetooth users)
any issues once your service is enabled you'll have to head to
the main forum
search the thread for rrd update failed been covered a few times
1 Like
in brighter news... i'm augmenting the ROOTFSEXPAND option
to support an additional persistent partition...
(instead of stretching the rootfs which is lost on upgrade)
still not a good reason not to backup or use an additional drive
for data... but may appeal to something like light docker use
(i.e. the guest OS's loads from disk but does not write much)
or storing rolling backups or something
(any data over 100MB that you don't have somewhere else
to put)
changing
ROOTFSEXPAND=1
to
ROOTFSEXPAND_DATAPART=1
should get you a persistent /z folder on the first upgrade from
5.0.77-59 or second upgrade if coming from an older build...
Hi again
I just tried this new version and I still got the "Wireless is not associated" issue!
But as you can check in my logs after some wpad commands (with a successful YUP) and a second reboot the Wifi was back:
#FriFeb416:16:152022 disparity of 3695 minutes detected
FriFeb416:16:352022 only 2s because the next interval is 221625.089 seconds in the past!
FriFeb416:17:052022 device 'radio0' setup failed, retry=0
online:5.0.77-59 = onsys:5.0.77-59 https://rpi4.wulfy23.info/builds/rpi-4_snapshot_5.0.77-59_r18711_extra
root@rpi4-dca632da63 /36# reboot
INTERACTIVE shutdown_57-checkbeforereboot> checking for new boot dependent ini changes
INTERACTIVE shutdown_57-checkbeforereboot> checking for new boot dependent ini changes
INTERACTIVE dca632da63d7.sh> /etc/custom/dca632da63d7.sh shutdown
root@rpi4-dca632da63 /36#
...
#FriFeb416:16:432022 25.936809] everyboot_751-bootnotices> update luci boot banner msgs
FriFeb416:16:432022 servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
FriFeb416:20:052022 30.020287] 27-ntp> BOOTSTATE:TIMESET:step> Fri Feb 4 16:20:05 UTC 2022
online:5.0.77-59 = onsys:5.0.77-59 https://rpi4.wulfy23.info/builds/rpi-4_snapshot_5.0.77-59_r18711_extra
root@rpi4-dca6000003 /37# logread -e hostapd
root@rpi4-dca6000003 /36# /etc/init.d/wpad enabled && echo YUP
root@rpi4-dca6000003 /37# /etc/init.d/wpad status
inactive
root@rpi4-dca6000003 /36# /etc/init.d/wpad enabled && echo YUP
root@rpi4-dca6000003 /37# /etc/init.d/wpad enable
root@rpi4-dca6000003 /37# /etc/init.d/wpad enabled && echo YUP
YUP
root@rpi4-dca6000003 /37# /etc/init.d/wpad status
inactive
root@rpi4-dca6000003 /37# logread -e hostapd
root@rpi4-dca6000003 /37# reboot
INTERACTIVE shutdown_57-checkbeforereboot> checking for new boot dependent ini changes
INTERACTIVE shutdown_57-checkbeforereboot> checking for new boot dependent ini changes
INTERACTIVE dca6000003 d7.sh> /etc/custom/dca6000003 d7.sh shutdown
root@rpi4-dca6000003 /37#
...
#FriFeb416:20:202022 servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
FriFeb416:23:062022 29.916832] 27-ntp> BOOTSTATE:TIMESET:step> Fri Feb 4 16:23:06 UTC 2022
FriFeb416:24:412022 packet received on eth0 which has no address
online:5.0.77-59 = onsys:5.0.77-59 https://rpi4.wulfy23.info/builds/rpi-4_snapshot_5.0.77-59_r18711_extra
root@rpi4-dca632da63 /40# logread -e hostapd
Fri Feb 4 16:20:18 2022 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0) --> new PHY
Fri Feb 4 16:20:18 2022 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Fri Feb 4 16:20:18 2022 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->ENABLED
Fri Feb 4 16:20:18 2022 daemon.notice hostapd: wlan0: AP-ENABLED
root@rpi4-dca632da63 /40#
1 Like
ok so that could be some kind of firstboot issue
(build related i think)
next time you upgrade please post
dmesg | grep -E '(wpad|wifi)'
grep '^WIFI' /root/wrt.ini
before rebooting and after the upgrade fully initializes
(5 minutes)
Please noticed that I did not upgraded from the previous version.
I flashed the new image in my pendrive (since I'm not using a microSD card).
I tried again, doing several reboots and nothing!
Only when I preformed the wpad "voodoo", and getting the YUP (notice that sometimes I don't), I was able to get the WiFi again. Recall one question I asked about the "enable" vs "enabled" parameter.
Here is the log:
#FriFeb416:52:102022 24.765683] dca632da63d7.sh[bg]> /etc/custom/dca632da63d7.sh everyboot
FriFeb416:52:102022 24.828238] everyboot_751-bootnotices> update luci boot banner msgs
FriFeb416:52:122022 servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
online:5.0.77-59 = onsys:5.0.77-59 https://rpi4.wulfy23.info/builds/rpi-4_snapshot_5.0.77-59_r18711_extra
root@rpi4-dca632da63 /40# logread -e hostapd
root@rpi4-dca6000003 /38# dmesg | grep -E '(wpad|wifi)'
root@rpi4-dca6000003 /38# grep '^WIFI' /root/wrt.ini
WIFIAUTOSETUP=1
root@rpi4-dca6000003 /38# /etc/init.d/wpad enabled && echo YUP
root@rpi4-dca6000003 /40# /etc/init.d/wpad enabled
root@rpi4-dca6000003 /39# /etc/init.d/wpad enabled && echo YUP
root@rpi4-dca6000003 /40# /etc/init.d/wpad enable
root@rpi4-dca6000003 /39# /etc/init.d/wpad enabled && echo YUP
YUP
root@rpi4-dca6000003 /40# dmesg | grep -E '(wpad|wifi)'
root@rpi4-dca6000003 /38# grep '^WIFI' /root/wrt.ini
WIFIAUTOSETUP=1
root@rpi4-dca6000003 /39# reboot
INTERACTIVE shutdown_57-checkbeforereboot> checking for new boot dependent ini changes
INTERACTIVE shutdown_57-checkbeforereboot> checking for new boot dependent ini changes
INTERACTIVE dca6000003 d7.sh> /etc/custom/dca6000003 d7.sh shutdown
root@rpi4-dca6000003 /39#
#FriFeb416:58:142022 25.165145] everyboot_751-bootnotices> update luci boot banner msgs
FriFeb416:58:162022 servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
FriFeb416:59:332022 30.319184] 27-ntp> BOOTSTATE:TIMESET:step> Fri Feb 4 16:59:33 UTC 2022
online:5.0.77-59 = onsys:5.0.77-59 https://rpi4.wulfy23.info/builds/rpi-4_snapshot_5.0.77-59_r18711_extra
root@rpi4-dca6000003 /41# logread -e hostapd
Fri Feb 4 16:58:14 2022 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0) --> new PHY
Fri Feb 4 16:58:14 2022 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Fri Feb 4 16:58:14 2022 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->ENABLED
Fri Feb 4 16:58:14 2022 daemon.notice hostapd: wlan0: AP-ENABLED
root@rpi4-dca6000003 /41#
So I presume that we are missing yet something, right?
1 Like
go to luci > system > startup > local startup
find ENABLEDSERVICES add wpad there (and remove the # if present);
ENABLEDSERVICES="wpad"
this is an odd bug... I wonder if your board is special or something...
rpi-support.sh | head -n7
1 Like
I tried that but with no success!
I had to repeat the "wpad voodoo"! 
Here is the log:
#FriFeb417:27:542022 plugin: rrd_update_r failed: /tmp/rrd/rpi4-dca632da63/cpu-2/percent-user.rrd: opening '/tm
FriFeb417:27:542022 plugin: rrd_update_r failed: /tmp/rrd/rpi4-dca632da63/cpu-2/percent-softirq.rrd: opening '
FriFeb417:27:542022 plugin: rrd_update_r failed: /tmp/rrd/rpi4-dca632da63/disk-sda2/disk_ops.rrd: opening '/tm
online:5.0.77-59 = onsys:5.0.77-59 https://rpi4.wulfy23.info/builds/rpi-4_snapshot_5.0.77-59_r18711_extra
root@rpi4-dca632da63 /40# logread -e hostapd
root@rpi4-dca632da63 /40# dmesg | grep -E '(wpad|wifi)'
root@rpi4-dca632da63 /39# grep '^WIFI' /root/wrt.ini
WIFIAUTOSETUP=1
root@rpi4-dca632da63 /41# /etc/init.d/wpad enabled && echo YUP
root@rpi4-dca632da63 /40# /etc/init.d/wpad enable
root@rpi4-dca632da63 /40# /etc/init.d/wpad enabled && echo YUP
YUP
root@rpi4-dca632da63 /40# reboot
INTERACTIVE shutdown_57-checkbeforereboot> checking for new boot dependent ini changes
INTERACTIVE shutdown_57-checkbeforereboot> checking for new boot dependent ini changes
INTERACTIVE dca632da63d7.sh> /etc/custom/dca632da63d7.sh shutdown
root@rpi4-dca6000003 /40#
#FriFeb417:30:592022 61.602078] rpi-perftweaks.sh[bg]> sysval: eth0/queues/tx-4/xps_cpus[0>2]
FriFeb417:30:592022 61.627189] rpi-perftweaks.sh[bg]> sysval: eth0/queues/rx-0/rps_cpus[0>7]
FriFeb417:30:592022 61.652121] rpi-perftweaks.sh[bg]> sysval: eth1/queues/rx-0/rps_cpus[0>7]
online:5.0.77-59 = onsys:5.0.77-59 https://rpi4.wulfy23.info/builds/rpi-4_snapshot_5.0.77-59_r18711_extra
root@rpi4-dca6000003 /42# logread -e hostapd
Fri Feb 4 17:25:50 2022 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0) --> new PHY
Fri Feb 4 17:25:50 2022 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Fri Feb 4 17:25:50 2022 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->ENABLED
Fri Feb 4 17:25:50 2022 daemon.notice hostapd: wlan0: AP-ENABLED
root@rpi4-dca6000003 /41#
Take noticed in the "enable vs enabled" sequence to obtain the YUP that seems to allow the success!
1 Like
Hi
My RPi 4B has 8GB.
Is that which makes it special?
root@rpi4-dca632da63 /44# rpi-support.sh | head -n7
################################# root-dev: /dev/sda2:02050230-02 boot-dev: /dev/sda1
################################# root-partinfo: root@boot: PARTUUID=02050230-02 root@cmdline: PARTUUID=02050230-02
################################## 4B 1.4 8GB Sony_UK d03114
############ buildid:r18711-4367d4f869 localversion:5.0.77-59 files:390f3daca variant:fullest
############ fwV:Apr292021 vlV:000138a1
############ fwWIFI: Firmware: BCM4345/6 wl0: Mar 23 2020 02:20:01 version 7.45.206 (r725000 CY) FWID 01-febaba43
############ fwGPU: 2021-08-19T12:27:01, ef2c018dccdeb94b0376db62a2ea4c882f9b500d
1 Like
nice... 8gb from usb
good to know... was wondering how many people had 1.4 aka "smiley face" units
you may wish to check out this if not already aware
1 Like
What about this?
As I told you I found in the Startup file a commented line with the ENABLEDSERVICES and added one with the wpad, and nevetheless the issue with wpad remained, since I had to repeat the "Hocus Pocus" in the CLI.
ENABLEDSERVICES="wpad"
# ENABLEDSERVICES="banip adblock" #[fboot/upgrade] enable+start
1 Like
i've checked a few things but at this stage i'm pretty lost...
(need to wait for two more reports of wifi disabled on firstboot)
next time it happens... (before fixing and while still booted from firstboot) you can PM me;
cat $(find /boot/plog/pdmesg* | tail -n1)
cat $(find /boot/plog/plogread* | tail -n1)
other option you have is to switch to the official OpenWrt images
Tomorrow I will do a fresh install and send you that info.
But even like this, I prefer your image!
Thanks for that!
If I can abuse a little more from your time, let me share another problem I found.
I implemented a OpenVPN access using precisely the link you already mentioned here.
The only problem I have is that after each reboot I have to manually start the server (hitting Start in the Web interface). Can't that be done automatically?
Regards
1 Like
enable it...
and make sure the connection definition in luci/uci is enabled
/etc/config/openvpn
config openvpn 'anenabledconnection'
option enabled '1'
I believe I have both, like that:
root@rpi4-dca632da63 /44# cat /etc/config/openvpn
...
config openvpn 'server'
option enabled '1'
option config '/etc/openvpn/server.conf'
root@rpi4-dca632da63 /44# cat /etc/openvpn/server.conf
user nobody
group nogroup
dev tun
port 1194
proto udp
server 192.168.8.0 255.255.255.0
topology subnet
client-to-client
keepalive 10 60
persist-tun
persist-key
push "dhcp-option DNS 192.168.8.1"
push "dhcp-option DOMAIN lan"
push "redirect-gateway def1"
push "persist-tun"
push "persist-key"
<dh>
-----BEGIN DH PARAMETERS-----
MIIBCAKCAQEA5q
1 Like
disabled is clickable... means you have not clicked it
you will also want this for your next upgrade;
1 Like
Are you sure?!?
Because for instance in the Wireless when it is enabled, the button show Disable (the action that is preformed if pressed), right?
Note that the OpenVPN server is working, that specific client line is the one that after a reboot goes:
... from Started (button Stop):
... to Stoped (button Start):
clicking Disabled enables the service...
there is no correlation with whether the service is started or not (unless you just clean booted) which can be done independantly of enabling the service as you have already done
1 Like