TGViewer
Channel Public Channel
Linux - Reddit

Linux - Reddit

@r_linux

Stay up-to-date with everything Linux!
Content directly fetched from the subreddit just for you.

Powered by : @r_channels
Open in Telegram
Subscribers
1.04K
Photos
4.5K
Videos
207
Links
41.8K

Showing posts older than #42904 · Back to latest

Older Posts 20 shown
Post #42897 61
Master Blaster – A simple Qt6 SoundFont manager for Creative EMU10K1 sound cards.

For the two people who still care. 🙂

I hadn't touched Python in around 20 years, so I used ChatGPT as a coding assistant to help me get back up to speed. The project itself is something I wanted because I missed having a small GUI for managing EMU10K1 SoundFonts.

Master Blaster is a simple Qt6 frontend for the tools provided by awesfx (sfxload) and alsa-utils.

It's mostly a nostalgia project inspired by the little Creative utilities from the 90s that let you tweak your sound card through a simple control panel.

Features:

Load .sf2 SoundFonts
Clear sample memory
Display SoundFont RAM usage
Test SoundFonts with a MIDI file
Remember the last loaded SoundFont
Remember the selected MIDI port

The source code is available on Codeberg, along with a README and a screenshot:

[Master-Blaster](https://codeberg.org/mxl84/master-blaster)

I'm using an Audigy Rx, but it should work with any card supported by the snd_emu10k1 driver.

The python file is small and should be easy to read, with different sections outlining functions.

Roadmap? No, not really. I might add support for loading your own MIDI file for testing, and I'd like to redesign the progress bar to look a bit more... 90s.

https://redd.it/1vcz9of
@r_linux
Codeberg.org master-blaster Qt6 SoundFont Manager for EMU10K1 sound cards.
Post #42890 66
Fresh Install Samsung MZAL NVMe drops to D3cold and fails to wake (Ryzen 5 5600U)

Hello,

I am attempting a fresh installation of CachyOS using the latest live ISO, but the boot sequence consistently fails due to my main NVMe drive dropping off the bus.

Hardware:

CPU: AMD Ryzen 5 5600U
RAM: 16GB
Motherboard: HP 8861 (KBC Version 41.35.00)
Storage: SAMSUNG MZAL8256HDJD-00BL2 (Firmware Version: 1L1QKXD7, NVMe Version: 2.0)
Boot Method: Ventoy loading CachyOS LTS ISO (Kernel 6.10.4)


During the live boot initialization, the system hangs and throws an endless loop of I/O timeout errors:
nvme0n1: Read(0x2) @ LBA... Host Aborted Command
nvme 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible
Because the drive physically drops offline, all dependent targets (like mounting /boot and creating swap on /dev/zram0) fail, resulting in a system hard lock before I can reach the live environment login.

Troubleshooting Steps Already Taken:

Graphics Isolation: I initially suspected an AMD integrated graphics hang. I passed nomodeset 3 in the boot parameters, which correctly threw an amdgpu failed with error -22, confirming the GPU was bypassed and isolating the issue entirely to the storage controller.

Kernel Flags Added: To combat the aggressive APST/ASPM power management forcing the drive into deep sleep, I modified the boot parameters with the following flags:
nvmecore.defaultpsmaxlatencyus=0 pcieaspm=off pcieportpm=off iommu=pt nvme.noacpi=1

Hardware Reset: Between attempts, I performed a 30-second physical power drain to clear the motherboard capacitors and ensure the PCIe port was reset from the frozen D3cold state.

Despite these modifications, the OEM firmware on this Samsung drive still ignores the kernel overrides and drops the connection. I cannot provide exported journalctl or dmesg text files since I cannot reach a stable shell, but I have attached photos of the kernel logs.

Has anyone encountered a specific patch or module flag for this Samsung OEM firmware, or is this particular drive fundamentally incompatible with the current kernel's ASPM routing?

https://redd.it/1vcibtw
@r_linux
Reddit From the linux community on Reddit Explore this post and more from the linux community
Post #42888 60
PID 1 inside a namespace does not receive the signals you think it does

This is the reason docker stop takes ten seconds on a container that is doing nothing at all, and it is not Docker being slow. It is documented kernel behaviour, in pidnamespaces(7), and it surprised me for longer than I would like to admit.

Try it:

docker run -d --name t alpine sleep 1000
time docker stop t

Ten seconds, near enough exactly. The container is running `sleep`. There is nothing to flush, nothing to close, no shutdown work of any kind. It sits there for the full grace period and then gets killed.

The reason is that the first process in a PID namespace is treated as an init process, and the kernel protects it from itself. From pidnamespaces(7):

> a process in an ancestor namespace can send signals to the "init" process of a child PID namespace only if the "init" process has established a handler for that signal. SIGKILL or SIGSTOP are treated exceptionally: these signals are forcibly delivered when sent from an ancestor PID namespace.

So SIGTERM to a PID 1 that has not installed a handler is not ignored by the process. It is discarded by the kernel, before the process ever sees it. sleep has no SIGTERM handler, so the signal goes nowhere, and the ten seconds are the runtime correctly waiting out a grace period for a shutdown that can never begin. Then SIGKILL, which is the one signal that gets through regardless.

You can see whether a given process will do this before you try to stop it. SigCgt in /proc/PID/status is a hex bitmask of the signals that process has installed handlers for:

grep SigCgt /proc/$(pgrep -n sleep)/status

Bit 15 is SIGTERM, so the mask is significant against 0x4000. All zeroes means nothing is caught, which means SIGTERM will be discarded, which means you are going to wait the full grace period.

Three ways out, and they are not equivalent. --init puts a tiny init as PID 1 which does have handlers and forwards them, which fixes it for anything. A trap in your entrypoint fixes it for your own script. Changing --stop-signal only helps if the process actually handles the signal you switch to.

The part I find worth knowing regardless of containers: this is why an entrypoint shell script that ends with a command instead of exec behaves differently from one that does. Without exec your shell is PID 1, and shells do not install a default SIGTERM handler for non-interactive use either.

https://redd.it/1vcfsm9
@r_linux
Reddit From the linux community on Reddit Explore this post and more from the linux community
Post #42887 49
Can I require LUKS to use both the passphrase and Yubikey?

I've been using LUKS for a while and would like to add an additional layer of security of a hardware security key (Yubikey). Currently on boot I enter the LUKS passphrase then it decrypts and brings up the regular user login and I enter that password and it loads into the the OS. I would like the functionality to be on boot both the LUKS passphrase and Yubikey are required to decrypt then it brings up the regular user login and I enter that password and it loads into the OS.

The guides and documentation I've seen seem to be based around using the Yubikey as an alternative to the LUKS passphrase which is not what I want to do. I want to increase the layers and security not decrease it. I do have multiple Yubikeys to add as backup so that's not a concern. I'm assuming there has to be a way to do this but it's been difficult to find information on it. With KeePassXC I can have it require all of database file/key file/password/Yubikey and I would like a similar level of security for my entire linux install (usually Debian or Linux Mint).

Is there a way to setup the functionality I'm looking for? If so please either point me in the direction of a guide or documentation on setting this up or let me know how to.

https://redd.it/1vcbulm
@r_linux
Reddit From the linux community on Reddit Explore this post and more from the linux community
Post #42886 50
AMA Today: Yuhang Wu (Ex-Tesla & TikTok) Red Team Engineer & Exploit Developer | Linux Kernel Exploit Creator

Don't miss the AMA with Yuhang Wu, where we learn about elite enterprise infrastructure hacking, Linux kernel exploitation, and the future of autonomous Al security.

When: Today - Friday, July 31, 12:00 PM PT

Guest Credentials:

Former Red Team Engineer at TikTok, targeting cloud and application-layer defenses.
 Former Security Engineer at Tesla, securing vehicle software, factory systems, and internal applications.
Co-developer of "DirtyCred", a groundbreaking Linux kernel exploitation technique.
 AI Security Innovator, who built LLM-based autonomous agents that uncovered 8 P1 (critical-severity) production vulnerabilities.

Ask your questions here and we’ll get them answered during the live AMA today (Friday @ 12 Noon Pacific)!

https://redd.it/1vbtrdb
@r_linux
Reddit From the linux community on Reddit Explore this post and more from the linux community
Post #42884 59
Is PipeWire still unusable for Pro Audio in 2026? Is it even aiming for that?

I check every 6 months, and always find that my Focusrite Clarett+ 4Pre XRUNs at like "15ms" buffer sizes and below, while Windows handles "2.5ms" just fine on the same machine.

https://wiki.archlinux.org/title/Professional\_audio notes that pipewire might not be usable for pro audio, but the linked discussion is from 2023.

What's your experience? Should anyone aspiring to use Linux for music production just stick to JACK?

https://redd.it/1vbwta0
@r_linux
Older posts →
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →