@gabe_saltar @david_chisnall There's a reoccurring burst of static anytime I'm playing audio. The fix is actually to switch back to pulseaudio and stop using pipewire & wireplumber. I tried every suggestion you can find out there and nothing worked. Since my problem is on a work laptop I've worked with our internal teams doing the builds and we're all ok with me not using the recommended audio stack that's configured on all machines and removing the culprit packages. It's a stop gap as I suspect I'll end up back on pipewireplumber again in the future.

@gabe_saltar @david_chisnall I'm saying this while laughing and crying that at least someone in this thread has working audio, hahaha. But at least my problem is still with my Linux box and my audio remains perfect on FreeBSD. Great to see people helping one another!

@wyatt Hardware choices are definitely something you can't just do on a whim with FreeBSD. That's always been a struggle, unfortunately. I tend to go through hardware support pages before buying anything.

In the case of this thread though, I have no problems with FreeBSD and the problems lie solely with the Linux pick 'n' mix of audio subsystems which I'm unfortunately stuck with on this machine. If I could rip out pipewire and wireplumber I would.

@wyatt That's sad to hear. We all have different experiences with different hardware. I've been blessed with mostly uncomplicated audio with FreeBSD on desktops, laptops and peripherals so far.

In the last few years I haven't had as much trouble with Linux and pulseaudio as I am having with pipewire and wireplumber this week.

Alsa & Pulse were definitely the bane of my life at one point, thinking maybe early days of their duet. Now it seems that pipewire & wireplumber's foray onto the stage as the dominant audio systems in Linux is creating challenges and a configuration nightmare. At least in my opinion and perception of the streams of people battling with them online.

@zirias Haha. I didn't know it was a thing too until recently. I thought Linux was still muddling around with Alsa and pulseaudio.

What's worse is that there is a package pulsewire-pulse so I can't even tell which layer of abstraction I'm dealing with anymore or where I'm trying to find what's causing my problem.

I another a personal Debian laptop that hasn't been burdened with pipewire or wireplumber yet and the DAC works perfectly there and it goes without saying that It Just Works™ on my FreeBSD desktop. I've used the same DAC since 2016 and no problems until recently and only with this setup.

@david_chisnall FreeBSD audio definitely has some shortcomings as you've mentioned like bluetooth audio. I'm aware of these but all my audio is over wires so it's not something I've run into. But for the most part anything in FreeBSD is usually just a slight adjustment with sysctl. To try and fix my DAC issue on Linux I'm up to my neck in changes to either pipewire config files or wireplumber lua variables and none of it's worked.

Reading people constantly posting "fixes" involving restarting services and restarting their browser or turning an option off in pavucontrol and turning it back on again....................................................................................

Am I really reading people saying that turning it off and on again is the "solution"? I feel like I'm in some comedy sketch where someone has set me up for "Linux Audio I.T. Crowd"

Since this is a corporate laptop I can't just rip either of them out and I'm now at the point where I'm forced to use the built-in speaker and nothing else.

Linux has made the most complicated & broken audio setup I've ever dealt with. For years it has always been an abomination but it's even worse than it ever was today with pipewire and wireplumber.

I have a Linux laptop for work and my DAC is almost unusable because of constant bursts of static. I've spent two days reading the struggles people have gone through with these packages. Configuring conf files and writing Lua. It's ridiculous. People talk about The Year Of The Linux desktop but it will never happen because developers for these systems think everyone can just sudo their way around the problems, ask on forums for help and writing 40 lines of configuration file or Lua or god know what to fix the issue as if it's no thing. It doesn't work in the corporate world.

I say The Year Of The #FreeBSD desktop where I've literally never had any issues or major complications with audio ever in the last 25 years but I've always lost hours to Linux audio problems.

@mjturner Thanks. OpenBSD is fine too but will be my backup choice. I want FreeBSD jails for some services. What hardware are you running?

ucutils (helpers for the Unicorn Emulator) is now published to PyPI: https://pypi.org/project/ucutils/

@pietro395 Great! Looking forward to hearing how it goes. Thanks.

@justine Yeah, excluding switches & wifi APs the fibre router is my only non-BSD system and I want rid of it =)

Anyone running #FreeBSD using PPPoE for 1Gb FTTH? Looking for speed reports. I keep reading about performance problems on FreeBSD with PPPoE and unable to achieve full speeds. I've wanted to replace my current router for a while but not if I won't be able to make full use of the line.

China targeted and might have held for months access to the infrastructure used to do wiretaps on the AT&T and Verizon networks.

This is a huge "told you so" moment for the cryptographic community that has been saying that such infrastructure does present a huge risk to national security. China reportedly used this capability for intelligence collection, obviously without a warrant ...

https://www.wsj.com/tech/cybersecurity/u-s-wiretap-systems-targeted-in-china-linked-hack-327fc63b?st=C5ywbp&reflink=desktopwebshare_permalink

@malwaretech masscan, zmap, custom scanner, etc...? Which would load up my next question of pps for a cloud instance when scanning.

@fishidwardrobe I genuinely can't remember when I last owned a printer and work is different. But the point is also that don't accept all these dependencies when you don't need them. I've made CUPS packages when needed but it shouldn't be the default. This has applied for both personal and professional builds.

#CUPS vuln shall now to referred to from now as "Cupstorm in a Teapot".

@mkj Oh, interesting. Thanks for sharing!

@Viss Indeed. So ridiculous. Was advertised like it was going to rock the Linux kernel or something. But ... f'ing CUPS.

CUPS hasn't exactly had the best security history and it's a dependency shit show, that's why I exclude it.

I'm going to ring everyone I know who questions why I build custom packages to remove things I don't need and laugh down the phone.

Heh, CUPS. I've been building every #FreeBSD box for as long as I can remember without #CUPS.

OPTIONS_UNSET+=CUPS

Vulnerability feels like it was over hyped, IMO.

@mms Can you try setting hw.snd.default_auto=2 and see if disconnecting and reconnecting the USB hub works with setting the DAC as the new default audio device?