The KiwiSDR 2 online store is open for orders! Please visit kiwisdr.nz
I have successfully updated my KiwiSDR to V1.486
Points to ponder:
- Having had your KiwiSDR V1.486 flashed to your SD by belenaEtcher which has also validated the flashing process, don't look around and check-see your SD card about the file, as you would nothing there except zeros and a prompt " the volume does not contain a recognized file system " which might be mistaken for a corrupted SD card, leading you into a vicious and also futile reflashing cycle dealing with " a corrupted SD card. " The suspected corrupted SD card is actually where your new KiwiSDR version is now located, whose integrity could be verified using your Windows Disk Management that would detect your SD card and files as " healthy " So all you should do is to leave it at that and go about reflashing your KiwiSDR from this SD card.
- Give your KiwiSDR a good reset-flashing: a good reset-flashing means you should allow long enough time, like about twenty seconds by pressing the reset button above the SD slot on board before powering it up, when your KiwiSDR could respond and kick in the flashing process that might last from four to seven minutes before all lights were out.
- With your KiwiSDR updated to v1.486, you are on your way to auto-updating when your KiwiSDR is connected to WiFi. Congrats!
Comments
It's KiwiSDR v1.486 on Debian version 10.11and now put online via a wired broadband for updating. I was wondering how long it will take before my KiwiSDR gets updated to v1.553 and if there is a manual way to do that.
When you power-up the Kiwi with an Ethernet connection that has Internet service an automatic update should start automatically. Here's how you can tell: Connect to the admin page. Perhaps at
kiwisdr.local:8073/admin
or by ip address ifkiwisdr.local
doesn't work for you. Click on theUpdate
tab on the top line. Click the blueCheck Now
button. It will say what version you are running, if it is current or not, and if an update is in progress.To monitor the progress of an update: Click on the
Console
tab on the top line. Click theConnect
button. In the enter shell command field at the page bottom typem blog
(make build log). You should then see many scrolling messages from the update build process. The Kiwi server will automatically restart when the build completes.this is what I see at m blog, then nothing happened.
According to that you're already running v1.522
What does the
Check Now
button say on theUpdate
tab?Installed version: v1.486, built Jan 18 2022 01:12:00
Available version: v1.553
This is what " check now " button gets. Incidentally, I got this with " m blog ", after force bulid:
What should be done about this, please?
Are you in China or Russia?
That was a serious question, btw. Made just a few minutes before I had to retire for the day.
Not having access to GitHub.com is a serious problem since that's where the Kiwi sources are kept. Note that this failure is not a DNS lookup issue (which we've had problems with in the past) since it is a timeout. Presumably the lookup worked.
On the admin page, console tab, try doing a
ping -c3 1.1.1.1
andping -c3 github.com
andping -c3 kiwisdr.com
to see if you can reach these sites. If you can't then there is a serious problem with your Internet connectivity.this is my ping results.
Installed version: v1.486, built Jan 18 2022 01:12:00
Available version: v1.553
I am on v1.486 and " check now " found v1.553 available but updating hasn't been done, just yet.
KiwiSDR persistently stayed on V1.486 and updating remains unaccomplished. What seems to be the problem?
It seems GitHub.com can't be pinged anymore.
What happens when you try:
cdp
git show origin:Makefile | head -n 2
Any problems with this?
Wondered if this pull was in process and automatically.
No problem with that. Although since v1.555 was just released the git log has progressed a little bit.
To see the recent git log use the
gcoms
alias, i.e.cdp
gcoms
The "develop" branch is used as a staging area for the release under development.
But I need to know the updating status and when it is expected to complete.
To see if there is an update available just go to the admin page,
update
tab. Click theCheck now
button. If you get an error message instead of the update status go to theconsole
tab and click thecheck gitHub.com
button. If this gives an error then there is a problem with your Internet connectivity.If the
check now
button says "update available" then restart your Kiwi (control
tab,restart
button). This assumes you have theAutomatically check for / install software updates?
switches both set to yes. Otherwise you can force an update by clicking thebuild now
button.To monitor the build progress go to the
console
tab and click themonitor build progress
button. Be patient as there are several points in the build where the output will stop for up to a minute or so.When the build is finished the Kiwi will automatically restart no matter which method you use.
I did work through on the first scheme but nothing happened after many hours. And I did try " build " as well but there is no " monitor build progress " button on the interface with V1486.
Sorry, I somehow thought you had gotten further than v1.486. So we need to figure out a few things.
First, in the admin
console
tab, connect and typegit show origin:Makefile | head -n 2
This should reply with:VERSION_MAJ = 1
VERSION_MIN = 556
If at any point in the following you don't get the expected result, or you get an error message, copy and paste as much of the console window as possible into an email to
support@kiwisdr.com
If the above works then type:
gup
This will update the sources from GitHub.com Will take about a minute to run.
mc
Cleans the build directory. Doesn't take long.
m
The main part of the build. Will take 20 to 30 minutes to run. Should produce output at least every 30 seconds or so. If there is no output after several minutes something is wrong.
mi
Does the install of the build. Takes a minute or so.
If all of the above worked without error messages go to the
control
tab and click theserver restart
button. You should be running the latest version after the restart.By the end, got this error message.
Okay, but without seeing the messages that came BEFORE the "1 error generated" I can't tell anything that happened.
Also, what made you think you needed to do a
dpkg --configure -a
? You generally only do that if you are getting serious package system corruption errors. In which case that has to be fixed first before even attempting to compile the Kiwi stuff.At command m, got this error msg and the building process halted at that. What should be done about this?
There MUST be more error message before this. What are they??
I have had problems at m command, with one error msg generated at the end of the session. What should be done to troubleshoot this?
I have kept having problems at m command, in areas as listed right before the " 1 error generated " message.
Also, what does
ls -la /usr/include/openssl/ssl.h
print?Try reinstalling libssl:
apt-get reinstall libssl-dev
ls -la /usr/include/openssl/ssl.h
If the
ls
above no longer gives an error then try them
command again and see if it gets further.