Hello as the title suggests, meteor lake specifically the core ultra 225h which is the brother of 226v didn't get moved to xe drivers instead it uses i915 until you force it using modprobe.

The upsides of using XE drivers instead of the i915 is mainly the power to watt boost as I can literally see and feel the difference between the 2 in both how long can the laptop last and how much larger the margin is between frame rate as to wattage consumption. The core ultra processors mainly use xe drivers instead of i915, so I'm thinking that if I switch to Xe nothing will go wrong right? Well I'm wrong asf, not only it crashes a lot, I also got to introduce my first kernel panic and lost all my work because I don't have auto save.

If anyone is using or having a problem regarding this thing, can you please leave some suggestion on how to fix it in your rig or do I just have to accept that intel did us dirty by not having even those 11th gen use the xe drivers smoothly and force us to use the outdated i915 architectures?

Does anyone know which if any distros are compatible with acer swift air 14, i tried zorin but the current version doesn't work, the os wouldn't recognise any of my keyboard inputs, anyone currently using linux on this laptop? Any advice will help as i want to ditch windows asap thanks

reposting this here cuz i wasnt getting much traction

Hello friends. I've spent months troubleshooting intermittent network failures on my PC, and I'm starting to suspect a defective motherboard.

Specs:

• Gigabyte B850M Gaming X WiFi6E (BIOS F10)

• Ryzen 5 7600, RTX 5060 Ti, 32GB DDR5

• ASRock 850W PSU

• Linux Mint, Fedora, and Nobara (same problems across all three)

Ethernet and Wi-Fi randomly stop working, often during Steam downloads or VPN use. Occasionally USB devices disconnect, applications crash, or the entire system freezes. Rebooting usually restores everything.

Here's what I've tried to fix this: BIOS updates, disabling ASPM/C-states/power saving, different network drivers, kernel updates, and numerous network configuration changes. Memtest86+ passed repeatedly. Nada.

Today I ran a test that prompted me to think this might be a full blown motherboard failure. During a network failure, I discovered that FIVE AMD chipset PCIe downstream ports simultaneously reported Unknown header type 7f. The chipset-connected USB and SATA controllers also returned 7f.

Directly reading PCI configuration space returned all ff bytes. After rebooting, the same devices returned valid configuration data.

Meanwhile, the CPU's chipset-facing PCIe root port and the chipset's upstream switch function remained accessible.

My question: Does this sound like a defective motherboard/chipset, or could a CPU-side PCIe issue, firmware, or power delivery cause this behavior?

I'm leaning toward replacing the motherboard with an MSI B850 Tomahawk MAX WiFi and just washing my hands of the whole thing, but I'd appreciate opinions before spending the money.

I have a Nvidia GT 730 fermi, I want to rice arch + kde, how do I do it? Gt 730 fermi does not run good on wayland and i dont want x11. Also, I get more fps in minecraft in windows than in linux. How can I get the drivers?

WARNING: AI USE

If you have one of these Redragon headphones (specifically H848 in my case), you would know these things are horrifically bad to use on Linux. I've tried many manual fixes but couldn't make anything work, so I got my agent to make this fix. This could possibly work on other headphones but I have only tested it on my H848, and specifically made the script only work on H848 to not break any other untested systems.

Please READ the script before running it, or use the manual fix guide. Only tested on Redragon H848 on CachyOS, I'd welcome anyone who wants to test this and share their experience.

Link: https://github.com/Jijovo/redragon-h848-linux-fix

Setup: Gigabyte B550M K, Ryzen 5 5600GT (iGPU only), TP-Link AX1800 PCIe Wi-Fi (Archer TX20E, Realtek RTL8852BE, rtw89), Kingston NV3 2 TB + a 500 GB NVMe. Omarchy (Arch) and Pop!_OS, same behavior.

Symptom: the monitor on the board's DisplayPort (DP-to-HDMI) flickered whenever Wi-Fi transmitted. The monitor on native HDMI was always fine. rfkill block wifi stopped it. The 500 GB NVMe also unmounted occasionally, and the PC froze once.

What did NOT help:

• pcie_aspm=off, pcie_port_pm=off, pcie_ports=native

• rtw89 options: disable_ps_mode, disable_aspm_l1/l1ss, disable_clkreq

• amdgpu.sg_display=0, amdgpu.dcdebugmask=0x2

• Another DP-to-HDMI adapter and cable; swapping monitors (flicker followed the DP port)

• 2.4 GHz vs 5 GHz

• Disabling Spread Spectrum in BIOS

• Moving the Wi-Fi card from the chipset x1 slot to the CPU x16 slot

• BIOS Power Supply Idle Control → Typical Current Idle

The clue: after adding the 500 GB SSD, it flickered at idle even with Wi-Fi off. But during a 20 GB dd read from that SSD, the flicker stopped. Constant load = CPU never enters deep idle.

Confirmation (no reboot):

for s in /sys/devices/system/cpu/cpu*/cpuidle/state[2-9]/disable; do echo 1 | sudo tee $s >/dev/null; done

Flicker gone, at idle and during 200 MB Wi-Fi uploads.

Permanent fix: add processor.max_cstate=1 to the kernel command line (Limine: /etc/default/limine + sudo limine-update; GRUB: GRUB_CMDLINE_LINUX_DEFAULT + grub-mkconfig). Verify with grep . /sys/devices/system/cpu/cpu0/cpuidle/state*/name: only POLL and C1.

Takeaway: the Wi-Fi card and SSD weren't faulty. Their bursty activity kept the APU entering and leaving C2/C3, and the DP output couldn't tolerate those transitions. If your iGPU output flickers only under light, bursty load and stops under heavy load, test the C-states first. Cost: somewhat higher idle power.

Posting this in case it helps someone whose Bluetooth mouse or keyboard never appears in the device list, even while it is in pairing mode.

On the same computer running Omarchy (Arch-based), I ran into this with three devices:

• Logitech ERGO M575 trackball

• Logitech K580 keyboard

• Razer Orochi V2 mouse

All three eventually paired and connected. The workaround was to discover their addresses using a direct legacy BLE scan, then initiate pairing by address through btmgmt with a pairing agent running.

This is a workaround, not a confirmed root-cause diagnosis. In particular, I cannot yet say that extended scanning itself is broken.

Environment

• Bluetooth adapter: MediaTek USB, 0e8d:0608

• BlueZ: 5.87-2

• Kernel during the original M575 investigation: 7.2.8-9-omarchy

• Kernel during K580 and Orochi V2 pairing: 7.2.15-1-omarchy

• Firmware build reported by the controller during the latest checks: 20260224111243

Symptoms

Bluetooth was powered on and the service was running. Normal discovery could find some other devices, but not these peripherals. LE-only scanning returned no devices during the M575 and K580 tests:

bluetoothctl --timeout 20 scan le

For the Orochi V2, a normal scan on found other devices but missed the mouse.

During the M575 investigation, my phone could discover it, its USB receiver worked, and the same computer had previously used it over Bluetooth under Debian 13.

What worked

1. Discover the address with a legacy BLE scan

I used a small Python script through the HCI User Channel. It temporarily stops and runtime-masks the Bluetooth service, resets the controller, runs a legacy active BLE scan, then restores the service.

Existing Bluetooth peripherals disconnect temporarily during this step. Have another way to control the computer. The script is included in a separate comment below.

Put the peripheral in pairing mode before scanning:

• M575: use its Bluetooth pairing button until the blue light flashes rapidly.

• K580: hold the chosen Easy-Switch key for about three seconds until its LED flashes rapidly.

• Orochi V2: select Bluetooth on the bottom switch, then hold both side buttons and the DPI button together for about three seconds.

The scanner found all three devices in their respective tests. All three reported an LE random address. Use the actual address and address type returned for your device; do not copy someone else's address.

2. Keep a pairing agent running

For either mouse, open an interactive session:

bluetoothctl --agent NoInputNoOutput

Then run inside it:

default-agent

Wait for the success response. Leave this session open.

In a second terminal, replacing <DEVICE_ADDRESS> with the scanned address:

sudo btmgmt --timeout 45 pair -c 3 -t 2 <DEVICE_ADDRESS>

When the first terminal asks Accept pairing (yes/no), answer yes promptly.

For the K580, the working combination was different:

bluetoothctl --agent KeyboardDisplay

Run default-agent inside that session, then in another terminal:

sudo btmgmt --timeout 60 pair -c 1 -t 2 <DEVICE_ADDRESS>

Read the passkey displayed by the agent, type it on the K580, and press Enter.

Here, -t 2 means LE Random; -c 3 means NoInputNoOutput and -c 1 means DisplayYesNo. These are the combinations that worked in my tests.

3. Trust and verify

After successful pairing:

bluetoothctl trust <DEVICE_ADDRESS>
bluetoothctl info <DEVICE_ADDRESS>

If it is not already connected, this worked for my Logitech devices:

bluetoothctl --timeout 45 connect <DEVICE_ADDRESS>

The Orochi V2 connected during pairing without a separate connect command.

All three ultimately showed:

Paired: yes
Bonded: yes
Trusted: yes
Connected: yes

Linux also created Bluetooth input devices for all three (Bus=0005 in /proc/bus/input/devices). I confirmed actual pointer movement with the M575; the K580 and Orochi results here are based on pairing, connection and input-device enumeration. This is not a long-term stability test.

What did not fix discovery

During the original M575 investigation, these did not restore normal scanning:

• Restarting Bluetooth, toggling its power, or reloading btusb

• Disabling LE Coded PHY while retaining standard 1M scanning

• Temporarily testing older Debian firmware

• Temporarily running BlueZ 5.82 instead of 5.87

The original firmware and BlueZ were restored afterward. Those tests were on the M575 setup; I did not repeat every test for every peripheral.

Possible explanation — still unconfirmed on my hardware

A relevant report in the BlueZ issue tracker describes a MediaTek 0e8d:0616 controller whose Microsoft advertisement-monitor filter prevented normal LE advertisements from reaching the host. The reporter found that disabling the filter restored both legacy and extended scanning.

My adapter is 0e8d:0608**, not** 0e8d:0616, and I have not performed that filter-on/filter-off comparison. It is a useful lead, not proof of the same cause.

Also, my scanner changes more than just the scan command: it resets the controller and bypasses its normal initialization path. Its success does not isolate extended scanning as the fault. Controller filtering or initialization state could also explain the difference.

For now, the reproducible finding is: normal discovery missed these devices, while a direct legacy BLE scan followed by address-based pairing worked on this machine.

M575 reconnection was tested successfully, though a short timeout was sometimes insufficient. The K580 also reconnected automatically after the Bluetooth service was restored during the later Orochi test. Reconnection after a full reboot has not been verified.

Has anyone with 0e8d:0608 seen the same discovery problem, or traced it to the advertisement-filter path?

Optional first comment: scanner used for Orochi V2

Below is the scanner used successfully for the Orochi V2 test. It requires Linux, Python 3, systemd, btmgmt, and root privileges. It is intended for a single-controller system where the adapter is hci0.

Save it as orochi-v2-legacy-scan.py and run:

sudo python3 orochi-v2-legacy-scan.py

It temporarily disconnects Bluetooth devices. Let it finish normally so its cleanup can restore the service. It prints only matching Orochi advertisements.

For the Logitech tests, equivalent versions used b"k580" in data.lower() or b"ERGO M575" in data as the name filter, with matching output labels. The rest of the scan procedure was the same. A result of address type=1 means an LE random address, which matches btmgmt -t 2.

#!/usr/bin/env python3
"""Run a short legacy BLE scan for Orochi V2, then restore Bluetooth."""
import os
import select
import socket
import struct
import subprocess
import time

if os.geteuid() != 0:
raise SystemExit("Run with sudo or pkexec; this diagnostic temporarily stops Bluetooth.")

def run(*args):
return subprocess.run(args, check=True, capture_output=True, text=True)

was_active = subprocess.run(["systemctl", "is-active", "--quiet", "bluetooth"]).returncode == 0
enabled = subprocess.run(["systemctl", "is-enabled", "bluetooth"], capture_output=True, text=True).stdout.strip()
if enabled in ("masked", "masked-runtime"):
raise SystemExit("Bluetooth was already masked; refusing to alter its existing state.")
radio = None
masked = False

def command(opcode, payload=b""):
radio.send(struct.pack("<BHB", 1, opcode, len(payload)) + payload)
deadline = time.monotonic() + 5
while time.monotonic() < deadline:
if not select.select([radio], [], [], 1)[0]:
continue
packet = radio.recv(4096)
if len(packet) >= 7 and packet[:2] == b"\x04\x0e" and int.from_bytes(packet[4:6], "little") == opcode:
if packet[6]:
raise RuntimeError(f"Controller rejected {opcode:#06x}: status {packet[6]:#04x}")
return
raise TimeoutError(f"Controller did not answer {opcode:#06x}")

try:
run("systemctl", "mask", "--runtime", "--now", "bluetooth.service")
masked = True
run("btmgmt", "--timeout", "5", "power", "off")
radio = socket.socket(socket.AF_BLUETOOTH, socket.SOCK_RAW, socket.BTPROTO_HCI)
radio.bind((0, 1))
command(0x0C03) # Reset before selecting legacy commands.
command(0x0C01, b"\xff\xff\xff\xff\xff\xff\xff\x3f")
command(0x2001, b"\xff" * 8)
command(0x200B, struct.pack("<BHHBB", 1, 0x10, 0x10, 0, 0))
command(0x200C, b"\x01\x00")
print("Scanning for 25 seconds. Put Orochi V2 into rapid blinking.", flush=True)
seen = set()
deadline = time.monotonic() + 25
while time.monotonic() < deadline:
if not select.select([radio], [], [], 1)[0]:
continue
packet = radio.recv(4096)
if len(packet) < 5 or packet[:2] != b"\x04\x3e" or packet[3] != 2:
continue
offset = 5
for _ in range(packet[4]):
if offset + 9 > len(packet):
break
size = packet[offset + 8]
if offset + 10 + size > len(packet):
break
data = packet[offset + 9:offset + 9 + size]
address = ":".join(f"{b:02X}" for b in packet[offset + 2:offset + 8][::-1])
if b"orochi" in data.lower() and address not in seen:
seen.add(address)
print(f"Orochi V2: {address}; address type={packet[offset + 1]} (1 means random)", flush=True)
offset += 10 + size
command(0x200C, b"\x00\x00")
if not seen:
print("No Orochi V2 found during this scan.", flush=True)
finally:
if radio is not None:
radio.close()
if masked:
run("systemctl", "unmask", "--runtime", "bluetooth.service")
if was_active:
run("systemctl", "start", "bluetooth.service")
print("Original Bluetooth service state restored.", flush=True)

First off: don't even TRY to make me reconsider. I will **need** a laptop with a GPU (or very capable iGPU) as i'm going abroad for a full year starting august/september 2027.

So, any recommendations ? I know framework 16 exists but 7700S is a bit old now (tho i reckon AMD didn't do any 90 series portable gpu yet, and will probably never), and framework prices are pretty expensive for what they are hardware wise (though i love the spirit and i wouldn't mind at all supporting them if they're in the best options)

Where to start?

I have a ASUS TUF Gaming B550m Plus (not WiFi). Searching the internet got me the chip set used for the 2.5Gbps Ethernet: RTL8125BG. lspci tells me that it's Rev 04. So I found that it uses the r8125 module instead of r8169, and that explained why I was only getting 100Mbps even with a CAT 6a cable, despite in Win11 getting 1Gbps using a CAT 5a cable with the same router. My distro is CachyOS and while I generally use the lts kernel 6.8, even kernel 7.3.3.1 won't give me anything other than a 100Mbps connection. I have tried to install it 3 ways:

Cachy's repository of r8125 and r8125-lts. Effect: none

DKMS-r8125 through the AUR. Effect: none

Building the latest driver from RealTek. Effect: couldn't build, compiling errors saying some flags didn't exist (I can post the errors later).

I have EEE off and ASPM off. I have tried manually setting the bit rate in NetworkManager with no effect. I have uninstalled each install attempt before moving to the next. I updated this morning at 10am CST and updated any time I went to try things before. I have wireless 7 adapter, but it's mediatek and drops for 10s every once in a while which isn't great for online gaming.

I'm at a loss what to do next. Are there any suggestions for what to try next?

Edit: It turned out to be a bad/dirty port on the router! I have full 2.5Gbps on the 2.5Gbps port of the router.

I am considering buying an Intel-based Thinkpad T16 Gen 5 to use exclusively with Linux, primarily for programming.

I’ve settled on the T16 over the T14 because the T14 doesn't offer the H-series CPUs with a higher core count. Is the T16 Gen 5 as repairable/modular as the T14 Gen 7?

Which CPU should I choose: the 358H or the 366H? These are the two most powerful CPU options available for the T16 Gen 5 on the Lenovo website.

I also have a choice between three displays:

16" WUXGA (1920 x 1200), IPS, anti-glare, non-touch, 45% NTSC, 400 nits, 60 Hz

16" WUXGA (1920 x 1200), IPS, anti-glare, touchscreen, 100% sRGB, 500 nits, 60 Hz, low power consumption

16" 2.8K (2880 x 1800), OLED, anti-glare, non-touch, HDR 600 True Black, 100% DCI-P3, 500 nits, VRR 30–120 Hz

I know the first one is quite poor; should I go with the IPS option? I won’t be using the touchscreen feature, and I’d prefer to avoid an OLED panel—I don’t want to worry about OLED burn-in, especially since this will be used for work rather than gaming.

Thanks!

I guess it needs to be a joint effort from CPU manufacturers and OEMs to make best use of battery, but I particularly want to know if there are laptops out there which have very minimal battery drain when on sleep. Thanks in advance.

so i enabled intel_LPMD and managed to make the battery drain of around 6w average for the duration of my 10 min of web-browsing and that is better than the configuration i managed to pull of on windows which was 8w of average batterydrain (brightness and all other things were min on both instances) what is different is windows didn't feel as slow as how cachyOS is feeling with intel_LPMD on. Also i only have 2 LPE cores

I know LPMD pushes task out to LPE cores which are power efficient but not as powerful as E cores and i feel that

I have Acer Swift Go 14 with Ultra 5 125H and 65Whr battery

i also have 2880x1800@90Hz OLED goes up to 400nits SDR and 500nits HDR and i know HDR and high brightness kills my runtime and on highbrightness on lighter task the display probably takes more power than the CPU itself so i ran the test at 10% brightness cux windows 0% is equivalent to cachyOS 10% 0% is super dim like macOS level super dim so for a fair comparison i did that and i also have TLP and use Lazy_RCU

so what i want to ask is there like a sweetspot for performance and batterylife for Ultra 5 125H devices

I am supposed to see the boot menu where I can chose between Linux or Windows but noi menu appears and Linux boots directly.

How can I access the Windows partition at boot?

I have a laptop with a third-generation i5 processor, 16GB of RAM, and two SSDs: a Samsung 870 EVO and a Kingston KC600.

I use a caddy adapter for a second SSD—currently an 870, which isn't affected by the potential drop in speed—while the KC600 is in the primary slot. That said, if anyone recommends swapping their positions, I’d be open to hearing your suggestions.

I would like a Linux distribution that I can use as my primary operating system, while keeping Windows as a secondary system—perhaps to take advantage of what Windows has to offer (though, currently, I only use it for playing Steam games). Could anyone recommend a capable distribution that is well-suited not just for daily use, but also for multimedia editing, writing, illustration, and programming? My plan is to keep Windows strictly for gaming, but I’m open to any other ideas or advice you might have.

I’ve tried several distros, but none have really won me over.

Linux Mint (XFCE and Cinnamon): These were the most highly recommended, but I didn’t find them all that impressive. I’d recommend them, but only as a starting point while you’re getting used to using Linux.

EndeavourOS: This is probably my favorite distribution; I hold it in high regard, but I’ve never managed to get it configured exactly the way I’d like.

Fedora: This is the one I’ve used the least, mostly because I didn’t really take the time to understand it properly.

Nobara: I tried using it instead of Windows for gaming, and while I’m satisfied, I feel there are certain settings, programs, and games that might run better on Windows; even so, I still recommend it.

Kubuntu: This is what I’m currently using, but it seems to have some issues with internet connections.

Note: I currently use Windows 10 IoT Enterprise LTSC (with ReviOS) and Kubuntu; when idle, one uses less than 3GB of RAM and the other 2GB. I need a distro that uses less than 1.2GB of RAM when idle.

I was able to fix this issue by using AI ... here is the solution (by AI)

If you're running Linux on a new Intel Core Ultra 200H laptop (like the Core Ultra 5 225H on a Lenovo IdeaPad/ThinkPad/Yoga), you might have noticed the CPU package power gets hard-capped at ~21W–22.4W under multi-core load, with clocks pinned around 2.8 GHz and cool temps (60°C). Meanwhile, on Windows, the exact same hardware and charger easily boost and sustain up to 62W+ at 4.1+ GHz.

By inspecting silicon registers under load, I found the CPU was asserting Bit 12 (IccMax / Electrical Design Point current limit) in MSR 0x64f. The Linux kernel's intel_rapl_msr driver was mapping MSR 0x601 (MSR_VR_CURRENT_CONFIG) as Power Limit 4 and defaulting it to 64 (0x200), which enforces an overly restrictive ~64A current ceiling that trips on instantaneous spikes, along with an auxiliary 55W psys board power cap. By clearing the peak constraint on MSR 0x601 and raising psys and package limits, package power jumped from 21.9W straight to 62.6W sustained, with all-core AVX2 clocks increasing from 2.85 GHz to 4.15 GHz (and single-core boosting to 4.61 GHz).

I put together a full technical breakdown, quick one-liner diagnostic commands, and an automated systemd service that persists across reboots and sleep cycles on GitHub: [YOUR_GITHUB_LINK_HERE]. If your Core Ultra laptop feels sluggish or power-capped on Linux, check it out and see if this clears your throttling!

github repo

I'm looking for a low-mid tier tablet which can run Linux. ARM or X86 doesn't really matter at this point, but later down the line I could have requirements for a preference here. Alternatively, a touchscreen + ARM SBC or small x86 computer would be a valid solution as well. I'm building something resembling a user facing kiosk as a personal project.

Requirements:

• I don't know of any specific performance requirements I need as of now, but I feel like 8 GiB of RAM is probably a minimum for today's software.

• A nicer screen would be good, and preferably the larger the better, but ~11 inches would be a hard minimum.

• My only true hard requirement is that I can install Linux on it relatively easily without facing any large hurdles (specifically referring to non-standardized ARM bootloaders, and general hardware related issues).

I've found the PineTab 2 (I'm not a fan of PINE, since they almost always make broken products which aren't even half complete), and it's the only option I've found within the price range which can for sure support Linux.

https://pine64.com/product/pinetab2-10-1-8gb-128gb-linux-tablet-with-detached-backlit-keyboard/

The 8 GiB version is currently not in stock, and I'm not 100% convinced the 4 GiB option would be sufficient for a touchscreen desktop environment + a light program. It probably would be, but I wanted to explore some other options before venturing into it.

Beyond the PineTab 2, I can't really find any options which I know work with Linux without reaching into nearly twice the price range. There's a solid 2-4 options at the ~$1000 price range, but that's quite more than I want to spend here.

There's several tablets or 2 in 1's which I can find at cheaper prices from Lenovo, Dell, etc, but it's really hard to find info on if I can install Linux on them or not. I was hoping to get some guidance and suggestions on what I could look into here. I'm open to used hardware if needed, all I really need is a clean screen.

Alternatively, I could look into a standalone touchscreen if it is relatively cheap and easy to get functional on Linux, but a standalone tablet would be smaller, more power efficient, and likely easier to setup - so I'd like to explore this option first.

Thanks!

Edit: Anyone reading this in the future may find this link and github repo's documentation helpful, it's very thorough and well laid out: https://github.com/linux-surface/linux-surface/wiki/Supported-Devices-and-Features#feature-matrix

My JBL Quantum 360 wireless headset would randomly stop playing audio, especially with multiple apps running, such as Spotify plus Elden Ring, Cyberpunk 2077, or Discord. Unplugging the dongle or switching audio outputs back and forth temporarily fixed it. I've seen reports of the same behavior across the whole Quantum range (350/360/610/810/910 wireless dongles), so this may help those too. Increasing the headset's audio buffering margin fixed it for me. Here's how to try it.

Who This Applies To

This works across Linux distributions using PipeWire with WirePlumber 0.5 or newer. It is not a universal fix for every headset dropout. Check with:

wireplumber --version
wpctl status

If those commands are missing, or WirePlumber is older than 0.5, these instructions may not apply.

1. Create the Configuration Folder

Run this in a terminal:

mkdir -p ~/.config/wireplumber/wireplumber.conf.d

2. Create the Fix File

Open your text editor and create this file inside your home folder:

.config/wireplumber/wireplumber.conf.d/90-jbl-quantum-headroom.conf

Paste in:

monitor.alsa.rules = [
  {
    matches = [
      {
        node.name = "~alsa_output.usb-.*Quantum.*"
      }
    ]
    actions = {
      update-props = {
        api.alsa.headroom = 1024
      }
    }
  }
]

The ~ means the value is a pattern, so this matches any USB output with "Quantum" in the name — not just one model. It should cover the whole wireless Quantum range, including differently-named variants like "JBL Quantum 360 Wireless" or "Harman JBL Quantum810 Wireless". Save the file. No sudo is needed. This targets Quantum playback outputs only; your mic and other devices are untouched.

3. Apply It

Log out and back in, or reboot. On distributions using systemd, you can instead run:

systemctl --user restart wireplumber

This briefly interrupts audio, including voice chat.

4. Check That It Applied

Run:

wpctl status

Find your Quantum headset under Sinks and note its number. Then run this, replacing NUMBER with that number:

wpctl inspect NUMBER

Look for:

api.alsa.headroom = "1024"

If it is missing or shows a different value, the rule hasn't applied. Check the sink's node.name in that same output: if yours doesn't contain "Quantum", replace the pattern in the configuration file with your exact node name and apply it again.

Why It Helps

The headset needs a steady supply of audio. This setting gives Linux more timing margin when feeding the dongle, which can prevent playback failures triggered by games or multiple audio streams. On my headset, it increased the margin from about 3 ms to 21 ms. The tradeoff is a small increase in playback latency. My logs showed repeated errors like:

snd_pcm_avail after recover: Broken pipe

"Broken pipe" here is an audio playback error, not a physically broken cable.

How to Undo It

Delete:

~/.config/wireplumber/wireplumber.conf.d/90-jbl-quantum-headroom.conf

Then log out and back in, reboot, or restart WirePlumber.

This post is mostly generated by AI but it worked for me

Thought i repost this issue of mine here too.
Appreciate any help