Last article I discussed the Fedora RAW file image and the first partition it contains. Now let us look at the second and third partitions.
Continue readingWhat is the Fedora 34 RAW Image. Part Two
2
Category Archives: Software
What is the Fedora 34 RAW Image. Part one
I was able to boot my Raspberry Pi using the Pi Imager and the Fedora AARCH64 Raw Image. While this makes me happy, I don’t really understand what these pieces are. So, I want to take a little more look at them.
Continue readingUpgrading QGo to QT5
My Day job has me messing around with QT5. We’rer building various RPMs for different RHEL and CentOS versions, and I wanted to get a little more experience on this. Specifically, I wanted to be able to do trial and error on a package that would not pollute our work stream. I wanted it to be something QT based. And I wanted it to be fun.
So I am working on repackaging QGo for Fedora 34 using QT5. Here’s what I am learning.
Continue readingUnmounting inside a container
We do RPM things. Some of those RPM things need the /proc file system. Not forever, but for a short while. So we mount /proc, do something, and unmount. Which works fine.
Until we tried to do it in a container.
Continue readingUnifying Audio with Pipewire
ALSA. Jack. PulseAudio. MIDI. Musescore. Jamulus.
My musical interactions with Linux are not the most complex in the world, but they ain’t trivial. The complexity of the Linux audio landscape has been a stumbling block so far. Pipewire has just gotten me past that.
The title of this article implies that you need to do something other than install Pipewire. So far, this is not true. On my system, at least, it Just works.
Continue readingCustom RPMS and meta-rpm
We are trying to enable the graphics hardware subsystem on the Raspberry Pi 4. This driver lives in mesa. The current Centos mesa.spec file does not enable the V3D Driver we need. Here are the steps I am going through to build the driver and integrate it into the meta-rpm build.
Continue readingRunning do_ scripts from yocto
I wanted to see how my work had diverged from the standard Raspberry Pi build. Specifically, the image creation stage is failing in my work. I can run the script in the original (upstream) version by doing thing following.
Continue readingUpdating config.sub in a bitbake recipe
config.sub is used to determine, among other things, the architecture of the machine. This is used in the configure script for an autotools based make file.
Older config.sub files don’t know how to handle aarch64, the generic name used for ARM64 servers in the build process. We have a recipe that pulls in code using an older config.sub file and I need to update.
My first approach was to build a patch. This works fine, and it was my fallback, but it is tedious to do for every recipe that needs this update, every time it needs it. It turns out we have a better approach that follows the guide of “don’t repeat yourself.”
Continue readingJamulus Server with a Low Latency Kernel on F33
I’m trying to run a Jamulus server . I got it running, but the latency was high. My first step was to add the real time kernel from CCRMA.
CCRMA no longer ships a super-package for core. The main thing missing seems to be the rtirq package.
- installed the ccrma repo file.
- installed the real time Kernel
- Set the RT kernel as the default.
- installed the rtirq scripts rpm
- enabler the systemd module for rtirq
- rebooted
- cloned the Jamulus repo from git
- configure, built, and installed Jamulus from the sources
- added a systemd module for Jamulus
- set selinux to permissive mode (starting Jamulus failed without this)
- started Jamulus
- ensured I could connect to it
- stopped jamulus
- set selinux to enforcing mode
- restarted Jamulus from systemctl
- connected from my desktop to the Jamulus server
- Jammed
It does not seem to have much impact on the latency I am seeing. I think that is bound more by network.
Setting the Default Kernel on Fedora 33
I have a server that I want to run the Real Time Kernel from CCRMA. Once I followed the steps to get the kernel installed, I had to reboot to use it.
Rebooting on a server with a short timeout for grub is frustrating.
Since the Fedora Kernel is installed, and I want to be able to run it as a backup kernel, I had to figure out how to change the default Kernel for Grub2. Most of the docs out there assume that you can list the menu-items in the grub2 config file, but that is a thing of the past. The lines are now auto-generated from a regex match of the places where one might place the vmlinuz files.
I ended up booting the machine and looking at the grub menu, which showed three Kernels installed; two Fedora Kernels and the RT from CCRMA. The RT Kernel was the second one on the list. But Grub is 0 relative, so to set the default Kernel:
sudo grub2-set-default 1 |
The next time it booted, it was set to the RT kernel;
$ uname -r 5.10.2-200.rt20.1.fc33.ccrma.x86_64+rt |