Fairly small release, but I really wanted to switch to the 4.19 kernel.
This has been running on my system for quite some time now without any issues, so let’s do this.
For the rest some ‘under the hood’ changes in preparation for RopieeeXL.
Got the update and threw my wifi off. Connected up the ethernet, logged in and the SSID is missing and I can not see any drop-down. Tried to uncheck wifi and remove password. Save changes does not work.
I might be doing something wrong, but for every Ropieee upgrade, I end up rebooting the Ropieee (literally) five times.
The option is set to check for updates on reboot. I would expect then that two reboots are required; first to trigger the check for the upgrade (I assume after the reboot has actually taken place) and the second time to activate the new version that got checked for (and downloaded) after the first reboot.
I can guess that what happens is that perhaps indeed on the first update a check is made for a new Ropieee version, but that the download and install of said new version takes… an unknown amount of time. I sit there rebooting Ropieee like a madman, and for all I know I could reboot it 10 times and still not get an update, because there is no indication that there is an update, and that if there is an update, that the update is ready to be installed and activated.
But it works, after 5 reboots, I have Ropieee 262!
well, this update jumped the kernel on a minor level. That also requires firmware stuff to be updated as well, hence the second reboot.
The good news is that this kernel jump on a minor level only happens once a year (or even less). I’m thinking of a way to make these kind of updates (that require an actual reboot to work) manually.