jks

I had to fix a bug in v1.267. So there is now a v1.268 and I added the time limit exemption password to the list of URL parameters. Use "pwd=..." or "password=..."

Login to the Beagle of your Kiwi, either using ssh from Linux/Mac, PuTTY from Windows or from the console tab of the admin page.
Type "scs avahi-daemon". Do you see messages like this that give the impression avahi is running?
(in all the following messages "www" will likely be replaced with "kiwisdr", the default Linux hostname of the Kiwi. My Kiwi happens to be named "www")

Feb 26 18:22:26 www avahi-daemon[679]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.103.
Feb 26 18:22:26 www avahi-daemon[679]: New relevant interface eth0.IPv4 for mDNS.
Feb 26 18:22:26 www avahi-daemon[679]: Registering new address record for 192.168.1.103 on eth0.IPv4.

If not, try restarting with "scst avahi-daemon", "scsa avahi-daemon" and another "scs avahi-daemon" and see if you get something like this:

root@www:~# scs avahi-daemon
? avahi-daemon.service - Avahi mDNS/DNS-SD Stack
   Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled)
   Active: active (running) since Wed 2019-02-27 01:46:17 UTC; 8s ago
  Process: 6088 ExecReload=/usr/sbin/avahi-daemon -r (code=exited, status=0/SUCCESS)
 Main PID: 6109 (avahi-daemon)
   Status: "avahi-daemon 0.6.31 starting up."
   CGroup: /system.slice/avahi-daemon.service
           ??6109 avahi-daemon: running [www.local]
           ??6111 avahi-daemon: chroot helper

Feb 27 01:46:17 www avahi-daemon[6109]: Process 679 died: No such process; trying to remove PID file. (/var/run/avahi-daemon//pid)
Feb 27 01:46:17 www avahi-daemon[6109]: Found user 'avahi' (UID 107) and group 'avahi' (GID 112).
Feb 27 01:46:17 www avahi-daemon[6109]: Successfully dropped root privileges.
Feb 27 01:46:17 www avahi-daemon[6109]: avahi-daemon 0.6.31 starting up.
Feb 27 01:46:17 www avahi-daemon[6109]: Successfully called chroot().
Feb 27 01:46:17 www avahi-daemon[6109]: Successfully dropped remaining capabilities.
Feb 27 01:46:17 www avahi-daemon[6109]: No service file found in /etc/avahi/services.
Feb 27 01:46:17 www avahi-daemon[6109]: Joining mDNS multicast group on interface usb0.IPv4 with address 192.168.7.2.
Feb 27 01:46:17 www avahi-daemon[6109]: New relevant interface usb0.IPv4 for mDNS.
Feb 27 01:46:17 www avahi-daemon[6109]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::9a84:e3ff:fe93:a341.
Feb 27 01:46:17 www avahi-daemon[6109]: New relevant interface eth0.IPv6 for mDNS.
Feb 27 01:46:17 www avahi-daemon[6109]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.103.
Feb 27 01:46:17 www avahi-daemon[6109]: New relevant interface eth0.IPv4 for mDNS.
Feb 27 01:46:17 www avahi-daemon[6109]: Network interface enumeration completed.
Feb 27 01:46:17 www avahi-daemon[6109]: Registering new address record for 192.168.7.2 on usb0.IPv4.
Feb 27 01:46:17 www avahi-daemon[6109]: Registering new address record for fe80::9a84:e3ff:fe93:a341 on eth0.*.
Feb 27 01:46:17 www avahi-daemon[6109]: Registering new address record for 192.168.1.103 on eth0.IPv4.
Feb 27 01:46:17 www avahi-daemon[6109]: Registering HINFO record with values 'ARMV7L'/'LINUX'.
Feb 27 01:46:18 www avahi-daemon[6109]: Server startup complete. Host name is www.local. Local service cookie is 3560849908.

If that doesn't work type "which avahi-daemon". Does it answer "/usr/sbin/avahi-daemon" ?

It's the middle of the night now in the EU, but here's a quick fix until a software update in a few hours.

If your Kiwi receives no signals because the IQ balance has ended up with huge offset values simply do this:
Open the IQ extension.
Set the PLL mode to OFF (very important).
IQ balance as normal (AM mode, antenna disconnected, no signals or spurs within passband when zoomed in).

Everything should now be back to normal.

The update will improve the IQ balancing user interface and fix a bug related to 20 kHz mode (the above fix works for both 12 and 20 kHz mode).

Okay, v1.266 is out with some fixes.

So the problem is that you can't be doing an IQ balance with the PLL turned on. This fact is now documented with the IQ balance instructions in v1.266. What's happening is that the PLL is trying to find something to lock onto and as a result is pulling the I and Q values around causing the sampling for IQ balance to be, well, unbalanced. That's why repeatedly doing a balance with the PLL on was causing the I offset value to start moving significantly away from zero until the offset itself was overwhelming the desired I signal component. This has the of effect drowning out the received signals causing the volume to go down, large S-meter reading, etc. that you observed.

Each IQ balance you make is cumulative since the prior IQ balance is in effect each time you make a new balance. That's why it's so important that there is no signal or spur within the passband while you balance -- so the I & Q offset numbers measured are not skewed by any signals being received (only influenced by the uniform noise level).

There is a new button in the balance popup that allows the offsets to be restored to their default values. And also fields for manual entry on the admin config tab. So in the future you shouldn't get stuck if somehow a bad balance occurs (e.g. there was something other than uniform noise in the passband).

Interestingly, I discovered that the default IQ offset value for 12 kHz mode (4 and 8-channel mode), -0.02, is not the correct one to use for 20 kHz mode. It seems to scale with channel bandwidth. The correct value is -0.02 * 20.25/12.0 (kHz) = ~ -0.034 So I had to add some code to use the correct default depending on mode.

There is really no reason to ever be rebalancing the IQ. The Kiwi is not like those analog sampling SDRs (e.g. SoftRocks) that need to be individually tuned. The default values have been shown to be correct for all Kiwis with their modern differential input ADC and ADC preamp. The only thing that is currently unknown is why the required Kiwi IQ offset values are not zero. The fact that the same value is required for all Kiwis (either -0.02 or -0.034 as mentioned earlier) seems to indicate there is a software/firmware reason someplace. Today's finding that this offset value is channel-bandwidth dependent is an important clue. But this is not really a problem, it's just an open question.

One of the best ways to understand the effects of IQ offset is to try the following. Find a moderately weak carrier such as an Ethernet spur with the antenna disconnected. In AM mode set the tuning so the carrier is in the low frequency part of the passband, like 300 Hz or so. Narrow the passband to 1 kHz by typing '/1k' in the frequency entry box. If you're in AM mode you should not hear a 300 Hz tone if the IQ is balanced properly. Now open another browser tab and connect to the admin config tab. Change the I balance offset to -1.0 You should hear a 300 Hz tone in the now unbalanced condition. When you change the value back the tone should stop. This is how I discovered the default balance value was wrong in 20 kHz mode. You get tone when using the 12 kHz mode balance value.

Calm down, it's just a bug with 20 kHz mode. I'm looking at it now.