Autoboot.txt not found upon reboot after updating slarm current on rpi4
by mEllis from LinuxQuestions.org on (#53YZN)
Over the weekend, I succeeded in installing Slackware Arm --current on my Raspberry Pi 4. I followed the directions exactly from the SARPi Project, except that I chose NOT to use the rpi-update because of all the warnings about it.
Everything was working perfectly until I ran the slackpkg update, install-new, upgrade-all, clean-system this morning (5/26/2020) and rebooted. During the update, I noticed that the kernel was upgraded too.
Upon reboot, I got a very scary screen that said that the autoboot.txt can't be found. Evidently, I messed up the boot process somehow.
Questions are: Do I have to start all over or can I repair the boot partition (process) so that it will work again? And what did I do wrong during the update/upgrade process?
I have access to other computers so that if the autoboot.txt file is something I can get at or add, I can. Would appreciate any help. First time setting up a Raspberry and wanted to use my favorite distro.
Everything was working perfectly until I ran the slackpkg update, install-new, upgrade-all, clean-system this morning (5/26/2020) and rebooted. During the update, I noticed that the kernel was upgraded too.
Upon reboot, I got a very scary screen that said that the autoboot.txt can't be found. Evidently, I messed up the boot process somehow.
Questions are: Do I have to start all over or can I repair the boot partition (process) so that it will work again? And what did I do wrong during the update/upgrade process?
I have access to other computers so that if the autoboot.txt file is something I can get at or add, I can. Would appreciate any help. First time setting up a Raspberry and wanted to use my favorite distro.