Bye cable, hello glass

Bit the bullet a few months ago and decided to go for a glass fiber connection. So after 25 years of cable internet from Casema/Ziggo we’re now hooked up to the optic fiber universe. Let’s see if it turned out to be the right decision.

Last year our whole region got a glass fiber network and getting your household hooked up was free of charge initially. But that changed now and just before getting charged for a connection I applied to get it done. Also the new provider has cheaper subscriptions, multiple TV channels with Ziggo were not working properly and with a glass fiber connection we will be ready for the future. I did look up to it though because for getting connected some work had to be done in our front yard. And even though it turned out ok-ish in the end I wasn’t really happy with the unannounced ventures in our front yard. Quite a part of the garden had to be opened up twice and everything isn’t really put back the way it was. Definitely no gardeners but that’s completely understandable.

Today the last things were taken care of, the media converter has been installed together with the router of the provider. The employee of the provider made sure everything worked properly and was done in less than an hour. After he left I only had to pull the network cable of my home network out the new router, stick it in the media converter, configure IPTV for VLAN 300 and tada, working internet with my own router setup (two Asus RT-AC68U’s in an AiMesh configuration). Took out the new router of the meter cupboard and loaded my stash of beer back in.

And is it faster? Partially. I already had a 1Gbit/s connection with Ziggo, but that was an asynchronous connection so upload is way faster now, about 8 times. Other pro is that the media converter is way smaller and probably draws less power. Other than that nothing really changed after the media converter which I like, fortunately there was no need to overhaul my whole home setup.

Bye cable, hello glass

rtcqs v0.6.1 released

A new version of rtcqs, a Linux audio performance analyzer, is now available. Most notable changes include:

  • Fixed inconsistent use of single and double quotes
  • Replaced audio group check with a group agnostic check (fixes #4)
  • Governor check can now deal with systems that have SMT disabled
  • Tickless check now deals with all CONFIG_NO_HZ* variants and with nohz being set on the kernel command line (fixes #8)
  • File systems check has been expanded
  • IRQ check now loops through /sys/kernel/irq instead of parsing /proc/interrupts
  • rtprio check now checks if a SCHED_FIFO priority can be set instead of a SCHED_RR priority
  • Improved preempt RT check, check if “preempt=full” is part of the kernel command line (fixes #7)
  • Refactoring, created separate classes for main app, resources and GUI
  • Moved all packaging directives into pyprojects.toml

While working on this release I found out PySimpleGUI is not open source anymore so rtcqs’ GUI has become a bit of a moving target. I’m looking at alternatives like pygubu or even popsicle but that will be something for in the long run. In the short run there are more improvements in the pipeline. The swappiness check needs some attention and same goes for the IRQ check. I’ve been working on a different project to automate prioritizing IRQs and I’m planning to to reuse some parts of that project for the IRQ check in rtcqs. The idea is to have rtcqs not only list the status of all audio related IRQs but also any audio devices attached to those IRQs.

rtcqs is available on Codeberg, PyPI and is also included in the AUR.

rtcqs v0.6.1 released