Main Menu --- Click to Unfold ---HOME
Skywave Linux 11/2020 Update
i3 Key Bindings
Neovim Key Bindings
Tmux Key Bindings
Other Top Notch Linux Distros
Skywave Linux Hard Drive Installation
Skywave Linux USB Installation
WebSDRs in 2019
Programmatic RTL-SDR Calibration
Fixing Audio: Dell, HP, Compaq
Skywave Linux Tumblr Page
Gqrx Spyserver Linux Client
Best Internet SDR Servers
Quick Tune HFGCS List
Quick Tune VOLMET List
Skywave Linux Notes and Bugfixes
i3 Window Manager
Note one: i3 is not like conventional user interfaces. Refer to the i3 keybindings and learn how to manage your windows, bring up the menu, and create your keyboard oriented workflow. It is fabulous, but it is not like Windows, or vanilla Gnome or MATE. Toggle your floating windows with "Shift + Super + Space" exit your session with either "Ctrl + Alt _ Del" or "Shift + Super + e".
Key bindings for i3, Neovim, and Tmux are linked from the README page bookmarked in Firefox.
Neovim has a couple of bugs, which are easily fixable and are indeed fixed in Skywave Linux v 4.2.
First, there is a tendency for Neovim to not render properly when opened in a tiled or floating terminal. The problem seems to be that i3 resizes the window after Neovim has set its dimensions, so the window you get is "jacked up" and needs to be cycled (unfloat / float again) or (float /unfloat). The problem does not occur if Neovim is run fullscreen. The following code in the init.vim file seems to fix it:
" Prevent rezize glitch on open autocmd VimEnter * :silent exec "!kill -s SIGWINCH $PPID"
A second issue involves the fzf plugin in Skywave Linux version 4.1, resulting from a silly dev attempt to save space by linking the plugin to the system installed fzf. The plugin and main system have a version mismatch, so the fzf plugin fails. If you try to view color schemes or do a fuzzy search, it does not work. The fix is to do one of these:
- Install an updated binary into the main system at /usr/local/bin/fzf
- In the home .config/nvim/plugged folder, remove the fzf and fzf.vim directories. Then reinstall the fzf and fzf.vim plugins. Use :PlugInstall to do that.
Skywave Linux 4.2 will have updated fzf and the plugins, plus a freshened setup
based on the language server protocol. It be will be a faster, smoother, better tool
for editing text and code.
If you use your own grub or syslinux bootloader setup, be aware that for Skywave Linux 4, point the bootloader to "initrd" not "initrd.lz" and likewise, "vmlinuz" is simply "vmlinuz" (both within the /casper directory). The intensely annoying livecd integrity check can be disabled by using fsck.mode=skip as a boot option.
Bootloader error in version 3.0: Isolinux is incorrectly pointed to the kernel file vmlinuz.efi instead of vmlinuz. If you use grub or isolinux to boot the iso, edit the file to use vmlinuz. Else, simply use version 3.0.1 or later.
Users with Nvidia Video Hardware: Boot and shutdown times are longer than usual on the current 4.4.0 Linux Kernel due to Ubuntu's use of sub-optimal video drivers. Users who fully install Skywave Linux can download the proprietary drivers and realize faster speeds.
SDR Updater and certain packages using SoapySDR drivers failed to run after switching Skywave 3.1.0 to apt repository drivers. The issues are resolved as of version 3.1.1. Users on earlier Skywave versions should skip to version 3.1.1 or later.
External USB drives will not properly mount in version 3.1.0. Kernel, 4.15.0-xanmod1, with supporting modules, was a bit too fresh and buggy. On fully installed systems or systems with persistence may be updated to a more mature kernel with these terminal commands:
apt update && apt install linux-xanmod-4.15 linux-firmware
A after kernel installation is complete, reboot and enjoy more device friendly behavior.
Installer crashes on versions 2.0 and earlier: Ubiquity had a bug which caused installations to fail when selecting languages and time zones. To remedy the bug, use "sudo apt update" and then "sudo apt upgrade" to freshen the running system before attempting a full installation.
Some users report "no audio" on certain hardware. In some cases it is due to the system not recognizing the hardware and loading improper audio drivers. Try the solutions well documented in the Ubuntu forums to modprobe the best audio modules. In other cases, the fault was in a too narrow device specification in the Pulse Audio configuration. In the file /etc/pulse/default.pa, look near line 46 for the code:
load-module module-alsa-sink device=hw:0,0 sink_name=processed_output
Replace it with:
load-module module-alsa-sink device=sysdefault sink_name=processed_output
Restart Pulse Audio or reboot the system. Check the audio by entering "sound Settings" and clicking the test buttons.
SDRPlay Devices on Skywave Linux 1.6
SDRPlay USERS: There is a software bug in Skywave Linux 1.6 which interferes with the configuration of Dump1090 for the SDRPlay. Please use the following shell command to correct the script and restore normal functionality. The command needs to be run only once for fully installed versions of Skywave Linux 1.6. Users booting from the iso file or DVD should run the command once per computing session before running Dump1090 on the SDRPlay:
sudo sed -i 's/\/sbin\/dump1090/\/sbin\/dump1090_sdrplay/g' /usr/local/sbin/dump1090_sdrplay/dump1090.sh
Tags:Skywave Linux, HPSDR, GHPSDR3, RTL-SDR, Cubic SDR, Gqrx, SDR Software, OpenWebRX, Linux SDR, SDRTrunk