restart wlan9 - Printable Version +- OpenMarine (https://forum.openmarine.net) +-- Forum: OpenPlotter (https://forum.openmarine.net/forumdisplay.php?fid=1) +--- Forum: How do I...? (https://forum.openmarine.net/forumdisplay.php?fid=3) +--- Thread: restart wlan9 (/showthread.php?tid=4340) |
RE: restart wlan9 - baltika_no_9 - 2022-12-03 Well that's promising, a bit surprising but positive. I wonder if it is worth making the same change for wlan0? Nothing to lose. I hope it continues to work for you. Regards Chris RE: restart wlan9 - tobias.e - 2022-12-03 actually, the chage can only be made for wlan0: Code: root@openplotter:~# iwconfig wlan0 power off Maybe, the problem was, that wlan0 is idle and "real" device goes into powersave, and the "virtual" device wlan9 doesn't like that ;-) RE: restart wlan9 - baltika_no_9 - 2022-12-03 Tobias I can certainly set power mode for both Code: pi@dolly:/etc $ sudo iw wlan0 set power_save off I also sudo the commands, again not sure if that is actually required. << forget that, I see you are logged in as the ROOT user for some reason. I'd be interested to know how you get on. Chris RE: restart wlan9 - tobias.e - 2022-12-04 Hi Chris, as i said, my Linux is a little rusty. I just learned that iwconfig is deprecated since 2015 . iw works for both interfaces. With power management on it was running for a couple of hours, but now i have 50h uptime without any problems: Code: root@openplotter:~# iw wlan9 get power_save RE: restart wlan9 - baltika_no_9 - 2022-12-04 That good news Tobias, let's hope others find the answer useful We should thank holgerw really as he identified the cause. After that it was just using the right commands. Have you thought about how you would make the change persistent, that is, so it will work after a reboot without needing to issue the commands? Thanks Chris RE: restart wlan9 - tobias.e - 2022-12-04 And its gone. The scan error seem harmless, they happened every now and then while it was working, but at 1434 hours "Firmware has halted or crashed" does not sound good. 15 seconds after that, wlan0 is restarted, but wlan9 is not. Which brings me back to my original question: how do i re-enable wlan9 in AP mode? Code: pi@openplotter:~ $ dmesg -e | tail -40 Whatever fixes this, will be put into rc.local - or it will become a cron job: check whether wlan9 is up, and if not, re-enable it. update: I did some more digging, and tried restarting hostapd, which complains: Code: Dec 04 16:38:47 openplotter hostapd[217076]: Configuration file: /etc/hostapd/hostapd.conf RE: restart wlan9 - baltika_no_9 - 2022-12-04 Don't you love technology, having solved one problem you just uncover the next one. I very much doubt there is any way of overcoming a firmware crash other than a reboot. I have never seen another way. The device is essentially screwed so cannot be expect to respond to the normal command set. As the errors suggest it is highly likely to be a firmware issue to be solved with an update or downgrade of the current version. rpi-eeprom-update should show if an update is available but there is always a risk when making any update of course. Good luck Chris UPDATE I see from your update that wlan0 has recovered but not wlan9. sudo ifconfig wlan9 up doesn't work I assume? RE: restart wlan9 - tobias.e - 2022-12-04 i still ty to figure out, what exactly happens during startup, how wlan9 is created. After all, wlan0 which shares the same hardware, comes back to life a few seconds after the firmware crash. P.S.: i actually do love technology, as it is a fun thin to play with in winter, when the boat is not in the water. And after all, the boat sails just fine without any technology .... RE: restart wlan9 - baltika_no_9 - 2022-12-04 Tobias When next in its failing state it will be interesting to see what messages the command "sudo ifconfig wlan9 up" shows. Also it might be worth trying: sudo sh /home/pi/.openplotter/Network/.openplotter/start1.sh You might want to double check that path in case it is different on your system Good luck Chris RE: restart wlan9 - tobias.e - 2022-12-04 Hi Chris, in the failed state, i get Code: root@openplotter:~# ifconfig wlan9 up whereas after a reboot, ifconfig wlan9 down; sleep10; ifconfig wlan9 up works. /home/pi/.openplotter/Network is a great hint! Until now, i was only searching in /etc but grep -ir wlan9 /etc/* did not turn up any usable results. This part from /home/pi/.openplotter/Network/.openplotter/start1.sh should do the trick: Code: #before adding an access point to the same device it must be turned off I'll try that after the next crash. Best regards, Tobias |