[connection] # 0: default, 1: leave untouched, 2: disable, 3: enable wifi.powersave = 2
26 April 2022
I had previously flailed around trying to fix occasional WiFi drops on my Pop_OS(Ubuntu) laptop. The intermittency made it hard to know if I really fixed it or not, and it turns out I hadn’t.
I installed Arch Linux on another computer here on my desk. While it sat around idle, I found it one day having lost its internet connection just like the Pop_OS machine does!
Now I knew this problem with the network connection wasn’t isolated to one machine. To recap:
the wired connection is fine
the Mac on the wireless network is fine
the mobile devices are fine
the 2 linux machines drop their connections every couple days
I started the search again for a solution with more information. I found some hints about power-saving options in NetworkManager.
On the Pop_OS machine,
there’s a configuration file,
/etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
,
that I changed to disable powersaving:
[connection] # 0: default, 1: leave untouched, 2: disable, 3: enable wifi.powersave = 2
I had to add a file to the Arch machine in the same location to hold this configuration. Now these machines have been maintaining their connections for days.
12 July 2021
Upon the release of Pop OS 20.10, my System76 laptop and my Arris router started having some disagreements. The laptop would drop connection every couple hours and not reconnect itself. I’d see the little question mark in the WIFI indicator, and I needed to manually turn WIFI off and back on to restore the connection.
I found mentions of this behavior in Ubuntu and in Pop OS forums, and supposedly newer NetworkManager from Gnome would fix it, so I suffered and waited for the beta of Pop OS 21.04 to be available. That didn’t fix it, so I started digging around some more in System76’s page for Troubleshooting Wireless.
I picked my way through the tips and applied some of them. Disabling band steering in the router finally seems to have fixed the problem. I’ve kept my WIFI connection up and running for days now. I didn’t need to name the 5GHz and 2.4GHz networks differently.
19 April 2021
I have a desktop server running Debian Unstable in the house, and I occasionally reboot it without logging back into the local desktop session. If I don’t login, I’d later find the machine mysteriously inaccessible — asleep. It’s set to never sleep, but that’s when I’m logged in.
To disable sleep in the GDM3 Greeter,
I edited the /etc/gdm3/greeter.dconf-defaults
,
found the "Automatic suspend"/[org/gnome/settings-daemon/plugins/power]
section and followed the comments to add:
sleep-inactive-ac-timeout=0
Now the machine will act a little more like it’s a server.
02 November 2020
I took the update to PopOS 20.10,
and my Overtone setup stopped working.
When I’d try to boot up
the internal SuperCollider server
from Emacs or from the leiningen repl
on my music projects
which all (:require [overtone.live :refer :all])
,
get an error in native libraries.
I could also try to start the server
with (boot-internal-server)
or (boot-external-server)
,
but it gives the same error.
--> Booting internal SuperCollider server... Cannot read socket fd = 107 err = Success CheckRes error Could not read result type = 22 Client name = Overtone conflits with another running client Cannot connect to the server JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock could not initialize audio. # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f5eec0e9ba7, pid=30517, tid=30605 # # JRE version: OpenJDK Runtime Environment AdoptOpenJDK (15.0.1+9) (build 15.0.1+9) # Java VM: OpenJDK 64-Bit Server VM AdoptOpenJDK (15.0.1+9, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64) # Problematic frame: # C [libscsynth.so.1+0x63ba7] World_WaitForQuit+0x7 # # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/john/workspace/music/hs_err_pid30517.log --> Connecting to internal SuperCollider server... [thread 30576 also had an error] # # If you would like to submit a bug report, please visit: # https://github.com/AdoptOpenJDK/openjdk-support/issues # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #
Since it can no longer start the server internally
from within Overtone,
I start the server manually.
I wrapped a script around the start up,
so I can set the environment variables
for configuring jack
and starting up the synth:
#!/bin/sh # automatically connect up jack ports export SC_JACK_DEFAULT_INPUTS="system:capture_1,system:capture_2" export SC_JACK_DEFAULT_OUTPUTS="system:playback_1,system:playback_2" scsynth -u 57110
To get Overtone going again,
I disabled the automatic boot
of the server within Overtone
by switching all the requires
in each file
from overtone.live
to overtone.core
,
and I connect
to that external server
from my REPL manually
with (connect-external-server)
before doing anything else.
Finally,
Overtone was consistently
failing to find my MIDI keyboard.
When things were working
well enough a couple months ago,
it still had required
a little dance of killing off jackd
and restarting Overtone,
since something had been
tying up the MIDI interface.
This workaround was no longer adequate,
since scsynth
and jackd
needed to already be started.
I disabled MIDI connection in jackd
by removing the -Xseq
option
from my ~/.jackdrc
.
I’m back in business,
and it’s probably more robust
with these manual steps now.
I think I’m also seeing
some other odd little things working
with the external server
that didn’t previously,
like using (mouse-x)
for reading mouse positions into the synth values.
The built-in piano synth is also
working where it hadn’t previously.
Update 2021-02-13:
I had lost the ability
to send desktop audio (pulseaudio)
through to the Jack Sink
with this setup,
so I figured out
to start qjackctl
before my supercollider.sh
.
That gets the Jack Sink
available again to pulseaudio
and the desktop sound menu.