- Joined
- Apr 11, 2023
Typical GNUisance bloatware. Try dtach + abduco.
The Linux Thread - The Autist's OS of Choice
- Thread starter tehpope
- Start date
-
Want to keep track of this thread?
Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
Create account
- Joined
- Sep 13, 2018
The icons are so distracting. I prefer the black/white icons that KDE uses. That being said, fuck the guy who decided to put a dolphin on the Dolphin icon.
- Joined
- May 12, 2017
I actually just switched over to a basic compressor/limiter. My preset as below
Code:
{
"output": {
"blocklist": [],
"plugins_order": [
"compressor#0",
"limiter#0"
],
"compressor#0": {
"attack": 8.0,
"bypass": false,
"input-gain": 0.0,
"knee": -6.0,
"makeup": 6.0,
"mode": "Downward",
"output-gain": 0.0,
"ratio": 4.0,
"release": 100.0,
"sidechain": {
"lookahead": 5.0,
"mode": "RMS",
"preamp": 0.0,
"reactivity": 10.0,
"source": "Middle",
"type": "Feed-forward"
},
"threshold": -18.0
},
"limiter#0": {
"attack": 1.0,
"bypass": false,
"gain-boost": true,
"input-gain": 8.0,
"lookahead": 5.0,
"output-gain": 0.0,
"oversampling": "x4",
"release": 8.0,
"sidechain-preamp": 0.0,
"threshold": -0.5
}
}
}It certainly helps with the onboard sound on my motherboard, but it's all moot anyway because I also did something I probably should've done a year ago. I unplugged the jack for my speakers out of my mainboard and plugged it into my Blue Yeti that's been collecting dust on my desk while still inexplicably remaining plugged in. The difference is like night and day. Even without EasyEffects presets, the sound's pretty loud even when testing under
amixer -c 2 Speaker 5%. With the Realtek codec on my motherboard, it's fucking inaudible at 5% when I run amixer -c 0 Master 5%. Apparently I just made myself prematurely bald by wasting so much time and energy on the Realtek shit when I should've just gone with the easy solution out the gate.I AM UNDOUBTEDLY FIZZED8%
kiwifarms.net
- Joined
- Jul 14, 2025
Everytime this absolute shit-eating cuck of a dev uploads a video, a few babies within a billion mile radiance have indirectly suffocated themselves to death from his 
aura.
aura.
- Joined
- Dec 17, 2019
I got an idea for a new distro: DARVO OS, with a very simple troubleshooting guide:
It always works flawlessly.
And if it doesn't,
It's your fault for not knowing how to fix it yourself.
It's your fault for needing something you don't actually need.
It's your fault for expecting something to work without a hitch.
It's your fault for using an OS you don't understand and you don't deserve it.
Think it'll catch on pretty damn well.
It always works flawlessly.
And if it doesn't,
It's your fault for not knowing how to fix it yourself.
It's your fault for needing something you don't actually need.
It's your fault for expecting something to work without a hitch.
It's your fault for using an OS you don't understand and you don't deserve it.
Think it'll catch on pretty damn well.
- Joined
- Mar 4, 2019
- Joined
- Mar 21, 2020
You have no idea how true this is.
While working in college I once created a number of boot USBs for our office, and my boss's reaction to me demonstrating the process was that I had worked some kind of arcane wizardry.
This was at a company whose entire business is selling computer hardware.
If someone like that can't wrap his head around something so braindead simple there is zero chance for Bubba sitting at home who's just decided he wants to remove Microsoft's stick from his ass.
Day of the Linux desktop will never come because the cattle are already too lobotomized.
- Joined
- May 12, 2017
Niggercattle gonna niggercattle; I had an uphill battle trying to convince my coworkers to do basic fucking QOL to make their lives easier.
- ALT+D to highlight any address bar
- Windows+V to enable and utilise the Clipboard Manager
- Actually sharing shit via OneDrive within the team, instead of emailing the same damn PDF a million times
- Using Outlook, Teams, and Excel via the web apps that come built into Edge instead of submitting unnecessary IT support tickets when Outlook the desktop client takes a billion fucking years to properly sync up after an extended holiday break
- Actually using AdBlock Plus to get rid of all the dodgy banner ads on those vocation-specific websites we need to interact with. Not even uBlock Origin Medium Mode; I daily drive that shit. AdBlock Plus is actually sanctioned for employee use by corporate IT, but no, they wanna bitch about search ads and dodgy banner ads on outdated vocational websites.
- $insert_other_minor_thing_here
Meanwhile, I was consistently told "not everyone's into tech like you are." Bitch, I wasn't trying to uproot our workflow by forcing a switchover to Emacs with Org Mode+Roam. This is all shit that's bog standard in our enterprise Windows 10-11 setups or comes bog standard in our goddamn Office 365 suite. Learned helplessness and its consequences are an unmitigated disaster for long-term productivity gains both in and out of the workplace, but I digress.
In other news, I have no use for EasyEffects anymore because the sound coming out of my Blue Yeti is significantly better compared to the on-board
snd-hda-intel sound with the shitty Realtek codec I was using previously. It still rustles my jimmies hardcore that snd-usb-audio is significantly better than the fucking built-in motherboard sound that every OEM ships. Bear in mind: Realtek ALC codecs are not unique to my hardware. If you ever bought any type of HP, Dell, Lenovo, Fujitsu, ASUS, Acer, Gigabyte, MSI, ASRock, or even a fucking CyberpowerPC/iBUYPOWER in your life, it more than likely shipped from the factory with a Realtek audio chip powering the audio jacks and pins on your motherboard. Realtek is so fucking ubiquitous that there are bug reports on Launchpad, Bugzilla, and so on dating back to like 2008 whinging about borderline inaudible sound without cranking your shit up past 50%.Obviously, the big fancy tech slop channels from JayzTwoCents to Linus Tech Tips to Level 1 Techs to Gamer Nexus and everyone else in between, those guys will have dedicated external DACs that they'll be routing all their sound equipment through for the inevitable content they're gonna churn out about Linux this, Bazzite that, Steam Deck this, or the Enshittification of Windows making Linux appealing that. Odds are that Linus and Luke will never have to do so much as touch
alsamixer, let alone worry about PipeWire because their audio equipment's plugged in via USB. But what about your average, everyday jack-off where the price of a "budget" DAC would run him the cost of a brand new mid-range PC altogether?I'm making a big stink about this because, like @Slav Power baits us into arguing over every other page, someone who's technologically literate by Windows standards wouldn't necessarily pick up on how:
a) ALSA is the part of the Linux kernel that directly deals with drivers and handles how your hardware functions.
b) PipeWire, PulseAudio, and Jack are all userspace sound servers that let you handle all sorts of stuff like managing gain/boosts/EQ, mixing sound between applications, stuff along those lines.
c) Desktop environments and window managers have sound management tools that can interact with ALSA, a sound server like PipeWire or PulseAudio, or both
d) None of these layers are remotely standardised, they're interoperable on some level, but it's never clear precisely what you're fiddling with unless you're using something like
alsamixer or Easy Effects.e) If the driver has a bazillion fucking variants, ALSA will immediately default to an implementation that's generic with conservative defaults. You'd need to set up an
alsa-base.conf file to ensure that you correctly list the audio driver and the implementation you need (i.e. options snd-hda-intel model=alc892).f) Windows does a lot of stuff behind the scenes with EQ, boost, and stuff along those lines. Realtek deals with Microsoft most frequently because Realtek's on basically every damn home consumer OEM's motherboard on the planet. Why would they care about Linux?
g) ALSA engineers and driver developers on the kernel team need to make do with what they got, settings need to be conservative for liability reasons, suddenly you lose 25-30dB's worth of sound if you jump over to Linux.
h) Years of community trial and error, the users discover the front panel headphone jack doesn't lose audio anywhere near as bad as the rear motherboard jack. The workaround then becomes "find some way to treat your rear jack as the front panel headphone jack." Tools like
hdajackretask enter the fold. Apply an override, reboot, and then you're good as gold... kinda. Don't forget to unmute and boost the channels on the correct sound card (F6 to select a device, never forget it!)i) You now have "adequate" sound, but the easiest way to manage it (i.e. volume control in your GUI) is a crapshot, so you'd need to rely on fucking
alsamixer for any meaningful precision. If you don't wanna roll the dice, you're basically keeping alsamixer open in a terminal window just to use as a goddamn volume knob.j) Or y'know... buy some random USB sound card and use that instead of your damn motherboard's sound jack because
snd-usb-audio somehow manages to run laps around Realtek despite also having a bazillion fucking variations in implementation. You can get away with using an Apple USB-C to 3.5mm dongle... and if your motherboard doesn't have a USB-C outlet, just use a USB-A to USB-C adapter and it somehow fucking works... and is better than your own damn motherboard's sound card.This is an uphill battle that was literally impossible for me to win when I was a high school kid running Ubuntu 10.04. 15 years later, I finally managed to "win" the battle... but now I'm basically here with my speaker cable plugged into my microphone's headphone jack because somehow... the soundcard on a Blue Yeti runs laps around dedicated audio hardware manufactured by a proper hardware vendor.
Would you believe me if I told you that I jumped ship from Ubuntu 12.04 to Windows 8.1 back in 2014 because the audio thing was genuinely a pain in the ass, especially when I bought new powered Dell speakers and I still had to crank the damn volume up in 12.04 to like 40% to get anything remotely audible? If Windows 10 never went EOL, I would've just stayed on LTSC for the rest of my life... and I'm an extremely autistic SOB who actually enjoys bashing his head against the wall trying to get his technology to work.
- Joined
- Aug 25, 2023
tldr: audio sucks on linux
- Joined
- Dec 17, 2019
So do window composers. It's a marvel that we got the most stable foundation for window composing and system audio from the nuclear shitfest that was the Longhorn project and to this day that code still holds up insanely well.
No, the loss of 3D audio was all on the greedy monopolistic cunts on Creative and I'm about to go on another rant about it fuck Creative hope they go bankrupt and die for what they did to Aureal and 3D audio
- Joined
- Mar 4, 2019
If I could travel back in time and do only one thing, it would be to shoot whoever the fuck decided to create alsa instead of forking OSS for Linux.
Without alsa, there's no pulse audio, which means poettering gains no community mindshare, which means no systemd homunculus sucking all the dev energy away from established toolsets.
- Joined
- Apr 11, 2023
I am sorry to hear about your issues. The Realtek on my current Asus B550 Prime Plus has never caused me a single issue, and I've used it under ALSA, Pulseaudio, and Pipewire explicitly. Audio code is a particular specialty of mine, so perhaps I'm just too old-hat at these systems for them to frustrate me, but I've long had more audio problems under Windows than Linux. I wonder if you're working with a vendor whose implementation sucks. Kinda sounds like it with your 5% volume anecdotes and whatnot.
- Joined
- May 12, 2017
I too am using an ASUS board, but it's a B350 series. The precise audio codec that
snd-hda-intel uses is ALC887, and it's an impossibly ancient codec that's been giving Windows refugees to Linux headaches since ~2008. I'm fixating on that year specifically because that's the oldest bug report I was able to find pertaining to the codec. Other, older bug reports circa 2006-2007 I've found were hideously imprecise but mentioned stuff like "Realtek" or "snd_intel_hda" in passing. Allegedly, newer motherboards coming out have better Realtek codecs that don't always require an alsa-base.conf file made, let alone an hdajackretask boot override that treats your rear motherboard jack as "Headphones" instead of "Line Out." Unfortunately, I'm stuck with the shitty ALC887 codec unless I decide to buy a whole new motherboard... and at that point, I might as well rebuild the whole PC. I'd sooner upgrade my CPU to a Ryzen 7 5800XD and my GPU to a 9070XT and slot in some extra storage than buy a new motherboard and rebuild from there.
- Joined
- Apr 11, 2023
dmesg said:
This is my rig. Maybe -VD is configured differently.
This 100% sounds like vendor misconfiguration. I presume you're up to date with eg. BIOS updates and whatnot? These are retaskable boards, and the problems you're describing are 100% your system getting the wrong information about retask state somewhere. This could be, like, some jeet put in the wrong floppy, or deleted the wrong line in a source file. But I've never done a thing to any of Gentoo/Arch/Debian that I've run on this, and I've done a lot of things that expose breakage, custom kernel builds, et cetera.
- Joined
- May 12, 2017
Alright, I'll bite. Output of my own
dmesg | grep snd_hda_codec_realtek
Code:
[ 36.277416] snd_hda_codec_alc882 hdaudioC0D0: autoconfig for ALC887-VD: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:line
[ 36.277424] snd_hda_codec_alc882 hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 36.277428] snd_hda_codec_alc882 hdaudioC0D0: hp_outs=1 (0x14/0x0/0x0/0x0/0x0)
[ 36.277431] snd_hda_codec_alc882 hdaudioC0D0: mono: mono_out=0x0
[ 36.277433] snd_hda_codec_alc882 hdaudioC0D0: dig-out=0x11/0x0
[ 36.277436] snd_hda_codec_alc882 hdaudioC0D0: inputs:
[ 36.277438] snd_hda_codec_alc882 hdaudioC0D0: Rear Mic=0x18
[ 36.277441] snd_hda_codec_alc882 hdaudioC0D0: Front Mic=0x19
[ 36.277444] snd_hda_codec_alc882 hdaudioC0D0: Mic=0x1aContents of my
/etc/modprobe.d/alsa-base.confSide note: I've already tried the below models, followed by
sudo dracut -f && sudo rebootoptions snd-hda-intel model=generic
options snd-hda-intel model=auto
options snd-hda-intel model=asus
options snd-hda-intel model=asus-mobo
options snd-hda-intel model=alc887-analog
options snd-hda-intel model=alc887-6stack-dig
options snd-hda-intel model=auto position_fix=1
Code:
options snd_hda_intel model=alc887-vd id=ALC887-VD index=0
options snd-usb-audio id=Yeti,HyperX index=1,2
options snd_hda_intel id=HDMI index=3Contents of my
/etc/modprobe.d/hda-jack-retask.conf file.
Code:
# This file was added by the program 'hda-jack-retask'.
# If you want to revert the changes made by this program, you can simply erase this file and reboot your computer.
options snd-hda-intel patch=hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fwOutput of
aplay -l
Code:
**** List of PLAYBACK Hardware Devices ****
card 0: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Generic [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Yeti [USB Advanced Audio Device], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: HyperX [HyperX Virtual Surround Sound], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: HDMI [HDA ATI HDMI], device 3: HDMI 0 [LG FHD]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
Subdevices: 1/1
Subdevice #0: subdevice #0I don't doubt that my shit's incorrectly configured. I already see ALC882 when I'm using ALC887.
EDIT: BIOS is up-to-date.
EDIT x 2: Gay as it is to use LLMs for tech troubleshooting, the Perplexity space I have set up with local references is telling me as below:
1) Apparently, the difference between my audio setup and your audio setup could very well be differences in the way our motherboards are designed.
Your setup and all troubleshooting details provided are correct and thorough—you have done everything right for your ASUS B350M-A / Realtek ALC887-VD system, and your experience matches what’s known about this codec, especially on older/mainstream AMD motherboards.
Bottom line:
Why You Needed All This Setup (and Others Don't)
- Motherboard and Vendor Differences:Even with the “same” codec (ALC887-VD), audio output quality and loudness is strongly affected by:
- The motherboard’s actual analog circuit design and grounding (cheaper or older boards, like B350, often skimp here).
- Vendor-specific ACPI, UEFI/BIOS quirks, and how the HD Audio chip’s pins are wired up and powered.
- B550 vs B350 Reality:
- Newer boards like B550 may have better power to the codec or fixed quirks in BIOS/board design, so Linux’s “auto” configuration works out of the box with ideal pin mappings and output gain.
- Many B350 (and B450) boards are documented by users to require pin overrides (like your
hda-jack-retask.fw) to get more than a whisper out of the rear line/headphone jack.
Model Assignments and ALSA Output
- Your device lines are fine; trying all the relevant
model=options was the correct approach. Some Realtek chip/board combos only work “best” withmodel=autoand a manual pin override, exactly as you’re doing. - Your
/etc/modprobe.d/alsa-base.confandhda-jack-retask.confare set up sensibly and, importantly, match what the kernel sees and uses. aplay -landdmesgoutput show all hardware addressed and mapped—nothing is “missing.”
Why The Other User’s Setup “Just Works”
- Their newer B550 board likely has:
- Higher-power HD Audio output circuitry.
- Correct pin routing baked into the UEFI/Windows/Linux ACPI tables.
- Maybe even better kernel quirks in recent Linux releases.
- Unfortunately, even with the same codec, board designs can differ so much that what “just works” on one fails or is quiet on another. This is a frustrating but well-known Linux PC hardware behaviour.
Your EasyEffects Preset
- Your EasyEffects config is “good” for maximizing loudness without obvious distortion.
- The real-world difference, however, will always be gated by the maximum analog output and power that the ALC887-VD implementation on your B350M-A can produce—no software can overcome hardwired voltage/output limitations.
Summary Table
| Config Aspect | Your B350M-A | B550 Example |
|---|---|---|
| Pin handling | Needs manual override (retask) | Often auto/ideal by default |
| Output level | Known low (needs workarounds) | Often full/adequate |
| ALSA config | Requires custom options/patch | Usually does not |
| EasyEffects help? | Moderate | N/A or even less needed |
Bottom line:
- Your config is fully correct and well-tested.
- What you’ve experienced is due to board-level analog output and ACPI quirks, not user error.
- Anyone with a B350/ALC887 board who suffers low volume and fixes it with retask+ALSA options is experiencing a common—if annoying—Linux hardware reality.
- You are “done” with manual setup for this hardware.
No additional model or preset will overcome the physical loudness cap of the Realtek implementation on this board.
2) I uploaded my most recent
alsa-info.sh and specifically asked if there's anything amiss with my hardware configuration. Apparently, this is about as good as it gets for my specific motherboard. Anything else would involve either the ALSA team doing something about it on a kernel level or getting further lost in the weeds of user tweaks.After a detailed review of your most recent alsa-info.sh, your setup is healthy and well-configured. Here’s what stands out and confirms your system is working as expected:
Summary:
Your Linux audio setup, routing, and kernel/ALSA state look healthy.
You are running a well-maintained, fully-functional Fedora ALSA stack—with both Realtek and USB audio devices detected, working, and mapped with sane volume/mixer controls. No fix is needed for system errors; any further improvement would require either hardware change or personal tuning.
Core ALSA/Hardware Configuration
- Motherboard: ASUS PRIME B350M-A
- Codec: Realtek ALC887-VD (Subsystem Id: 0x104386c7)
- Kernel: 6.17.8-300.fc43.x86_64, modern (Fedora 43)
- Soundcards recognized:
- 0: Generic [HD-Audio Generic] (your ALC887-VD codec, analog and digital)
- 1: Yeti [USB Advanced Audio Device]
- 2: HyperX [Virtual Surround Sound USB dongle]
- 3: HDMI [HDA ATI HDMI] (your Vega GPU HDMI audio)
- Module Parameters:
- snd_hda_intel is set up cleanly: model=alc887-vd, persistent id, and pin override loaded (via patch=hda-jack-retask.fw,...).
- snd-usb-audio for Yeti/HyperX uses comma syntax, ensuring stable indexing for these USB devices.
Pin Mapping & Mixer Health
- HDA-Jack-Retask patch is applied on boot for all snd_hda_intel, as shown by driver params and dmesg output.
- Your outputs and inputs for the Realtek chip show all relevant jacks detected and assigned (Line Out, Headphone, all Mics, S/PDIF).
- All analog volume controls (Master, Line Out, Headphone) are available and have their full dB ranges exposed.
- Your rear and front outputs (Line Out, Headphone) max at 0 dB, and you can set these up or down from there.
No Critical Errors/Warnings Detected
- ALSA, PipeWire, and all sound modules load cleanly—no codec error, firmware failure, “not found” lines, or silent initialization bugs.
- UCM profiles are found and loaded.
- USB audio devices (Yeti, HyperX) enumerate with correct names and full control ranges; their mixer devices work.
- HDMI/DP devices show up for multi-channel audio as expected on modern systems.
USB Audio Specifics
- Yeti and HyperX dongles are detected with approriate dB and hardware volume controls. All playback and capture paths are functional.
- No duplicate indices, missing controls, or device overlap.
- Playback levels on all cards are in normal, non-muted, non-clashing ranges.
Advanced Observations
- Your user pin configs reflect a working pin remap for better rear jack gain, in line with known Realtek quirks for this board series.
- The script outputs and mixer dumps indicate all ALSA controls are available with no “ghost” devices, bad state, or stuck values.
- No evidence of crashing, repeated enumeration, or system-level ALSA breakage.
In Conclusion
- Your ALSA and sound card environment is healthy, stable, and as optimal as Fedora and your hardware allow.
- No red flags or show-stopper errors are present.
- Any remaining loudness or quality issues are hardware/Electrical limitations—not configuration faults.
Summary:
Your Linux audio setup, routing, and kernel/ALSA state look healthy.
You are running a well-maintained, fully-functional Fedora ALSA stack—with both Realtek and USB audio devices detected, working, and mapped with sane volume/mixer controls. No fix is needed for system errors; any further improvement would require either hardware change or personal tuning.
Last edited:
- Joined
- Dec 17, 2019
- Joined
- May 12, 2017
It's the latest in solo window management faggotry that a noob like you need not worry too much about. Every 5 years or so, there's a window manager that all the sweaty tryhards swear up and down by. First Openbox, then dwm, then i3, now Hyprland. Hyprland is unique in that it's a window manager that requires Wayland, a contentious display server, but it's not like most tranny slop because the author of Hyprland is apparently a chud.
- Joined
- Nov 26, 2018
It's nice but not everybody. Just find something that works for you.