Linux issues on various distributions are becoming more common.
Linux issues on various distributions are becoming more common.
I've been attempting to configure a Linux and Windows dual boot setup on my newly assembled computer. The BIOS is set up for UEFI systems, and I've repeatedly installed both Windows and Linux in UEFI mode. However, the issue only emerged recently after a complete reinstall due to previous corruption from user mistakes and a full drive wipe. Now, across several kernel versions (5.2 and above), my audio devices vanish completely after roughly 15 minutes, and applications relying on the GPU cease to function properly or operate very slowly. In Windows, there are no such issues at all. This behavior was consistent before, but now any changes I make or troubleshoot seem ineffective. I've removed Pulse and ASALA cleanly, tried various audio outputs, but the same problem persists. USB devices also cause errors when my Corsair keyboard is connected. I assumed it was a firmware issue and updated the BIOS, which briefly resolved the problem before it reappeared. I'm currently stuck. (EDIT) I should note that I’m using an Arch Linux installation with mostly default KDE and KDE applications, plus some minor adjustments for a more personalized setup. My system specifications are: CPU – AMD Ryzen 7 3800X, Motherboard – Asus Crosshair VII x470 (Wi-Fi), RAM – Corsair Vengeance RGB 3200 MHz, 32GB, GPU – Zotac Gaming 2080 Super, PSU – Corsair RM 850x 80+ Gold, Mouse – Asus ROG Chakram KB, Monitor – Aorus CV27Q-SA 27-inch. Updated October 13, 2020 by Fishpat02 I omitted details that might be relevant.
The results show system messages and configuration checks. The output of "dmesg | grep error" lists kernel-related warnings. "lspci -v" displays updated device information. The grep command for audio drivers indicates they are present. No changes appear in pulseaudio settings. For NVIDIA, drivers from the dkms variant are required. The recommended kernel is 5.8.14-arch1-1. Pulseaudio and ALSA are likely installed. The audio setup matches the Crosshair VI HERO x370 board.
dmesg | grep error: [ 4.669866] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 5.890516] nvidia-gpu 0000:09:00.3: i2c timeout error e0000000 [ 5.890528] ucsi_ccg: probe of 0-0008 failed with error -110 lspci -v: File appears too large to process. dmesg | grep snd(?): [ 4.654575] snd_hda_intel 0000:09:00.1: Disabling MSI [ 4.654584] snd_hda_intel 0000:09:00.1: Managing vga_switcheroo audio client [ 4.657907] snd_hda_intel 0000:0c:00.4: activating device (0000 -> 0002) [ 4.888728] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC1220: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line [ 4.888732] snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 4.888735] snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [ 4.888737] snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0 [ 4.888740] snd_hda_codec_realtek hdaudioC1D0: dig-out=0x1e/0x0 [ 4.888742] snd_hda_codec_realtek hdaudioC1D0: inputs: [ 4.888745] snd_hda_codec_realtek hdaudioC1D0: Front Mic=0x19 [ 4.888747] snd_hda_codec_realtek hdaudioC1D0: Rear Mic=0x18 [ 4.888750] snd_hda_codec_realtek hdaudioC1D0: Line=0x1a [ 5.047912] usbcore: registered new interface driver snd-usb-audio Though to note, while I was observing these logs, audio functioned adequately initially. However, as expected, my Corsair keyboard ceased working shortly after receiving the output and I had to update what I’d seen.]
Still encountering the same issues, though it resolved the keyboard problem somewhat. Worth mentioning, I re-ran dmesg | grep error without audio and the results changed: [ 4.665117] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 831.166758] usb 2-6.1: Failed to suspend device, error -110 [ 929.086706] usb 2-6.1: Failed to suspend device, error -110 [ 993.726735] usb 2-6.1: Failed to suspend device, error -110 [ 1042.533222] threaded-ml[2469]: segfault at 24 ip 000055ec3676ccf9 sp 00007f6c1af345b0 error 4 in vivaldi-bin[55ec35cf3000+7bc4000] [ 1103.952634] threaded-ml[1393]: segfault at 24 ip 00005555b8327149 sp 00007fcba93cc530 error 4 in Discord[5555b7c45000+53b6000]
Are you experiencing any performance issues with your system? A crash or error occurring between two processes might indicate a hardware problem, possibly related to memory or the CPU. Linux tends to detect such instabilities faster than Windows, even if it appears stable on Windows. Regarding USB devices, running "lsusb" will show the list of connected USB ports and their details.
I haven't worked with overclocking, so if it's happening, it's doing so on its own. I've seen the fans increase a bit when I attempt to start something new without audio active. My RAM is rated at 3200MHz, and I set that in BIOS as the standard, which is significantly higher than the default. Regarding lsusb, everything appears normal considering the situation. Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 007 Device 002: ID 045e:0779 Microsoft Corp. LifeCam HD-3000 Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 006: ID 0bda:1100 Realtek Semiconductor Corp. Bus 003 Device 005: ID 048d:8295 Integrated Technology Express, Inc. Bus 003 Device 004: ID 0d8c:01c2 C-Media Electronics, Inc. Bus 003 Device 003: ID 0b05:18e3 ASUSTek Computer, Inc. Bus 003 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 28de:2400 Valve Software Bus 002 Device 002: ID 0424:5744 Microchip Technology, Inc. (formerly SMSC) Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0b05:1872 ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 012: ID 0424:2740 Microchip Technology, Inc. (formerly SMSC) Tablet Monitor Bus 001 Device 011: ID 28de:2102 Valve Software Bus 001 Device 009: ID 28de:2102 Valve Software Bluetooth Radio Bus 001 Device 008: ID 28de:2300 Valve Software Bus 001 Device 006: ID 0424:2744 Microchip Technology, Inc. (formerly SMSC) Hub Bus 001 Device 004: ID 28de:2613 Valve Software Bus 001 Device 003: ID 256c:006e Tablet Monitor Bus 001 Device 002: ID 0b05:185c ASUSTek Computer, Inc. Bluetooth Radio Bus 001 Device 010: ID 1b1c:1b2d Corsair K95 RGB Platinum Keyboard [RGP0056] Bus 001 Device 007: ID 1038:1250 SteelSeries ApS SteelSeries Arctis 5 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Though, remember this observation was made before the issue started (Edit). It hasn't changed much even now.**
Is the profile XMP or manually configured? It should have an XMP profile. If it's manual, let me know the model and settings you used. I might have the same unit—a 2x16GB (CMW32GX4M2C3200C16)—but I managed to apply the XMP profile. You can verify using "sudo dmidecode --type 17 | grep Part." It should list a device, but it isn't showing up. This shouldn't necessarily cause problems if it can't suspend. I'm guessing it might be "06:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter." I've faced issues with it on my x470-i board, which is treated as a USB device. Switching between Windows and Linux often causes strange behavior; usually fixed by removing the CMOS battery and holding the power button for about 30 seconds while unplugged. I've seen it vanish completely. For a quick safety test, run "dmesg | grep xhci" to see if there are any errors.
I'm not sure how to turn on xmp on my board since it isn't clearly labeled or available. I've only adjusted the memory frequency to match the module speeds. The dmesg command with xhci doesn't show any errors, and I've restarted into Linux again without issues after testing. I don't know what changed since the last boot, but I'll check again if it fails. (Edit) Now I'm getting the issue back, but the command still doesn't produce errors.
If you adjusted just the frequency without changing timing or voltage, the issue likely lies there. The segfaults stem from memory access errors. XMP should be set via Ai Tweaker → Ai Overclock Tuner → D.O.C.P Standard (XMP).