I do manual updates only, so after reading posts I did ssh as root (keys auth) and done these:
rm -r Beagle_SDR_GPS build build.log
gclone KiwiSDR ; cd KiwiSDR ; gup ; mc ; m ; mi ; ku
After ku got sth like: can't cd to Beagle_SDR_GPS so did Ctrl-C. Checking ku and cdp aliases realised ${PROJ} is outdated so logged out and in and did ku again without errors and rebooted at end. Kiwi2 is up and running 1.800.
Checking df -h / got only about 0.5G so from other posts got: journalctl --vacuum-time=1d and apt clean.
Next spotted old kernels in /boot and purged them with apt purge linux-image-5.10.168-ti-r72 linux-image-5.10.168-ti-r76 linux-image-5.10.168-ti-r77 which left only latest r79.
Now have above 1.2G free disk space. Thanks a lot for all advise I can find here.
Short feedback - my update story: Debian 8.5, kiwi-version was some steps behind because automatic updates are disabled. Update initiated by "build now" button. It took a very long time, then I ended up with 1.800. Afterwards, my antenna switch (homebrew gpio-based) didn't work anymore - it was disabled. After enabling it manually, it worked normally, but "Measure SNR now" complained about all antennas grounded (which wasn't true). But after another reboot, all seems to be fine.
Well, I ignored the msd input, followed the procedure using the admin console (on a Windows 11 machine) and about 2 hours later my KiwiSDR-1 is at V1.800 😀!
My Linux knowledge is rather limited, e.g. I had to go to Google to figure out what is SSH.
@Zyg Sorry. You're right about the msd (stop/disable the Kiwi server). That command should be skipped if those instruction are being used inside the admin console window. I have updated the instructions to say so.
Comments
I do manual updates only, so after reading posts I did ssh as root (keys auth) and done these:
rm -r Beagle_SDR_GPS build build.log
gclone KiwiSDR ; cd KiwiSDR ; gup ; mc ; m ; mi ; ku
After ku got sth like: can't cd to Beagle_SDR_GPS so did Ctrl-C. Checking ku and cdp aliases realised ${PROJ} is outdated so logged out and in and did ku again without errors and rebooted at end. Kiwi2 is up and running 1.800.
Checking df -h / got only about 0.5G so from other posts got: journalctl --vacuum-time=1d and apt clean.
Next spotted old kernels in /boot and purged them with apt purge linux-image-5.10.168-ti-r72 linux-image-5.10.168-ti-r76 linux-image-5.10.168-ti-r77 which left only latest r79.
Now have above 1.2G free disk space. Thanks a lot for all advise I can find here.
Short feedback - my update story: Debian 8.5, kiwi-version was some steps behind because automatic updates are disabled. Update initiated by "build now" button. It took a very long time, then I ended up with 1.800. Afterwards, my antenna switch (homebrew gpio-based) didn't work anymore - it was disabled. After enabling it manually, it worked normally, but "Measure SNR now" complained about all antennas grounded (which wasn't true). But after another reboot, all seems to be fine.
>Did you do the entire procedure though or just click the server restart button? If you did the entire procedure you should be running v1.800
I just clicked the server restart button. I will follow with the full procedure when I get more comfortable with it.
Just started with the entire procedure. It is straight forward until coming to msd.
After entering msd the console is lost (the Kiwi server is stopped) and no further inputs can be made.
As stopping the Kiwi server is only done to speed the build time, is it safe to ignore msd and continue with the rest of the procedure?
smoothly...KiwiSDR 1, MacOS, Kiwi with Debian GNU/Linux 11 (bullseye)
update from v1.709 with admin reloading to v1.800
Well, I ignored the msd input, followed the procedure using the admin console (on a Windows 11 machine) and about 2 hours later my KiwiSDR-1 is at V1.800 😀!
My Linux knowledge is rather limited, e.g. I had to go to Google to figure out what is SSH.
The system works!
73,
-Zyg- AF4MP
@Zyg Sorry. You're right about the
msd(stop/disable the Kiwi server). That command should be skipped if those instruction are being used inside the admin console window. I have updated the instructions to say so.