kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card

Bug #2009243 reported by Curtiss Clarke
78
This bug affects 16 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned
linux-hwe-5.19 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

2023-03-03
Attempted install of kernel 5.19.0-35 using the Linux Mint package installer LM 21.1 Vera, release 21.1).
Clobbered my Sound Blaster AE-7.
Could not even locate the device using Sound manager utility on Linux Mint Panel (the enumerated device showed up as the embedded sound chip on the mobo which I had previously disabled in the UEFI setup).
Uninstalled kernel and reverted back to 5.19.0-32 using Timeshift restore feature which worked fine before the update to 5.19.0-35.
Tried again to install 5.19.0-35 the same way, just to be sure.
The SB AE-7 got clobbered again.
So restored back to 5.19.0-32 generic one more time, using Timeshift. SB AE-7 works fine now with this lower version kernel.
Current hardware config:
------------------------
Asus Prime Z790-P wifi mobo.
Intel Core i3-13100 processor (with Intel UHD 730 graphics).
Corsair Vengeance DDR5 32gb (2x16) ram, 5200Mhz.
3 x Nvme SSD.
Boot drive is Western Digital Black SN770 500gb.
Asus Nvidia RTX-3050 PCIe graphics card.
Creative Labs Sound Blaster AE-7 audio card (PCIe).
On-board audio chip (Realtek 7.1 Surround Sound High Definition Audio) is disabled in UEFI.
UEFI is AMI/BIOS, revision 0812.
Linux Mint 21.1 is running on barebones hardware, no VM involved.
No other O/S's are installed on the machine.
-----
Running sudo lspci -vnvn > lspci-vnvn.log
gave the following error message...
pcilib: sysfs_read_vpd: read failed: No such device
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: mikey 4106 F.... wireplumber
 /dev/snd/controlC0: mikey 4106 F.... wireplumber
 /dev/snd/seq: mikey 4105 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21.1
InstallationDate: Installed on 2023-01-31 (32 days ago)
InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217
MachineType: ASUS System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=854c280c-7c5c-494d-a304-db66cf592baf ro quiet splash
ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-32-generic N/A
 linux-backports-modules-5.19.0-32-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.10
Tags: vera
Uname: Linux 5.19.0-32-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/24/2023
dmi.bios.release: 8.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0812
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z790-P WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0812:bd02/24/2023:br8.12:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2009243/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Paul White (paulw2u)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 2009243

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected vera
description: updated
Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : CRDA.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : IwConfig.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : Lspci.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : Lspci-vt.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : Lsusb.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : Lsusb-t.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : Lsusb-v.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : PaInfo.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : ProcEnviron.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : ProcModules.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : RfKill.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : UdevDb.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : WifiSyslog.txt

apport information

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote : acpidump.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Oscaruzzo (oscar-lazzarino) wrote :

This happens only after updating kernel to 5.19. It works booting older kernels like 5.15

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote :

Reverted back to kernel version 5.15.0-67-generic in
order to recover correctly functioning Creative S/B AE-7.
2023-03-20

Revision history for this message
George R Lunney (lunney) wrote : Re: [Bug 2009243] Re: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card

Did that a long time ago...but thanks anyway

On 3/21/2023 12:00 AM, Curtiss Clarke wrote:
> Reverted back to kernel version 5.15.0-67-generic in
> order to recover correctly functioning Creative S/B AE-7.
> 2023-03-20
>

Revision history for this message
Oscaruzzo (oscar-lazzarino) wrote :

I tried and the soundcard is detected, but then X doesn't start anymore (Nvidia drivers). Please fix this, I feel like I'm back to slackware 1.0 in the 90s.

Revision history for this message
Rovano (rovano) wrote (last edit ):

With kernel 5.19.0-32 and with Nvidia 515.xx working sound card good. (SB Z)
With 5.19.0-35 not working sound card.

Another mystification could be that this card had to always be overwhelmed after some updates to play. From CMD Alsamixer. Although I think it has not been needed lately.

Those who have the NVIDIA 525 drivers do not run graphic mode? Or do you run with a 515 driver?
Because before installing 525 it was possible to read that it is not easy to return to 515. That is why you may not run graphics mode.

Rovano (rovano)
Changed in linux-hwe-5.19 (Ubuntu):
status: New → Confirmed
Revision history for this message
MRATT (mrmail) wrote :

Hi, same for me and my new Ubuntu Desktop 22.04 64-bit installation and new "Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] (rev 01)" (Sound Blaster Audigy Fx V2 + DBPro daughterboard).

Wondered why it was working when playing around on the USB installation media (kernel 5.15) but not in the actually on the fresh install + dist-upgrade computer.

Thanks folks.

Revision history for this message
George Bardis (crisolivasavatage) wrote :

Same Issue with my Sound Blaster Recon3D / Z-Series
I have tried 5.19.0-35 and 5.19.0-38
Works only for kernel 5.19.0-32

Revision history for this message
Derek Archibald (d-archibald) wrote :
Download full text (7.4 KiB)

Linux Mint 21.1 Cinnamon (vera) NO SOUND OUTPUT

Issue on Intel NUC8i7HVK with AMD Radeon chip works OK with kernel 5.19.0-32 but failed SOUND output after kernel upgraded to 5.19.0.38.39 and also earlier kernel 5.19.0.35.36.

alsamixer shows no sign of the HDA ATI HDMI sound card after the kernel upgrade only shows the HDA Intel PCH card.

=====================SYSTEM with working sound card =================================
[code]
System:
  Kernel: 5.19.0-32-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33
    wm: muffin dm: LightDM Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: Intel product: NUC8i7HVK v: J71485-502 serial: <superuser required>
    Chassis: type: 3 v: 2.0 serial: <superuser required>
  Mobo: Intel model: NUC8i7HVB v: J68196-502 serial: <superuser required> UEFI: Intel
    v: HNKBLi70.86A.0067.2021.0528.1339 date: 05/28/2021
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard PID:b309 serial: N/A charge: 50%
    status: Discharging
  Device-2: wacom_battery_0 model: Wacom Intuos BT S serial: N/A charge: 100%
    status: Discharging
CPU:
  Info: quad core model: Intel Core i7-8809G bits: 64 type: MT MCP arch: Kaby Lake rev: 9 cache:
    L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 3596 high: 4199 min/max: 800/8300 cores: 1: 4050 2: 3100 3: 4042 4: 3100
    5: 4199 6: 3100 7: 3100 8: 4079 bogomips: 49599
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel HD Graphics 630 driver: i915 v: kernel ports: active: none
    empty: DP-5, DP-6, HDMI-A-3, HDMI-A-4, HDMI-A-5 bus-ID: 00:02.0 chip-ID: 8086:591b
  Device-2: AMD Polaris 22 XT [Radeon RX Vega M GH] vendor: Intel driver: amdgpu v: kernel pcie:
    speed: 2.5 GT/s lanes: 8 ports: active: DP-3,DP-4 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
    bus-ID: 01:00.0 chip-ID: 1002:694c
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati,modesetting
    unloaded: fbdev,vesa gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: DisplayPort-2 mapped: DP-3 pos: primary,1-1 model: Dell U2718Q res: 1920x1080
    dpi: 80 diag: 702mm (27.6")
  Monitor-2: DisplayPort-3 mapped: DP-4 pos: primary,1-1 model: LG (GoldStar) TV SSCR2
    res: 1920x1080 dpi: 30 diag: 1836mm (72.3")
  OpenGL: renderer: llvmpipe (LLVM 15.0.6 256 bits) v: 4.5 Mesa 22.2.5 direct render: Yes
Audio:
  Device-1: Intel CM238 HD Audio driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
    chip-ID: 8086:a171
  Device-2: AMD Polaris 22 HDMI Audio vendor: Intel driver: snd_hda_intel v: kernel pcie:
    speed: 2.5 GT/s lanes: 8 bus-ID: 01:00.1 chip-ID: 1002:ab08
  Sound Server-1: ALSA v: k5.19.0-32-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
Network:
  Device-1: Intel Ethernet I219-LM driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
    chip-ID: 8086:15b7
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel I210 Gigabit Network driver: igb v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: b000 bus-ID: 05:00.0 chip-ID: 8086:157b
  IF: enp5s0 state: down mac: <filter>
  Device-3: ...

Read more...

Revision history for this message
Rovano (rovano) wrote :
Revision history for this message
Derek Archibald (d-archibald) wrote :

Yesterday I did an Intel update under w10 (dual Boot) for the realtek driver and it failed under Intel's install program. I tried a download version and it repeatedly failed to install properly although it went through the motions. Upon trying VLC it crashed immediately. It looks like it might be a Realtek Issue which has been carried through to Linux in the upgrade process.

Revision history for this message
Oscaruzzo (oscar-lazzarino) wrote :

It still happens with 5.19.0-38-generic. alsa-info says:

!!Soundcards recognised by ALSA
!!-----------------------------

 0 [NVidia ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xa3080000 irq 17

!!PCI Soundcards installed in the system
!!--------------------------------------

01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:228e] (rev a1)
        Subsystem: ASUSTeK Computer Inc. Device [1043:881d]
03:00.0 Audio device [0403]: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] [1102:0012] (rev 01)
        Subsystem: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] [1102:0191]

Revision history for this message
seombre (seombre) wrote :

As a workaround you can try the ubuntu upstream kernels. I installed 6.2.11 from here: https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.2.11/

And sound was working out of the box again (kinda, I still had to open alasmixer and set to Headphones instead of Speakers).

Revision history for this message
Matt Anderson (spagettimonster) wrote :

It still doesn't work on 5.19.0-40-generic. If i revert back to 5.19.0-32 the sound works but the nvidia graphics driver stops working.

Revision history for this message
Rovano (rovano) wrote (last edit ):

Soundcard detected and worked well on 6.0.0 OEM kernel or in U23.04 on kernel 6.2.

On older 5.19.0-41 not detected.

Revision history for this message
MRATT (mrmail) wrote :

Fixed for me in 5.19.0-42 and with Nvidia graphics.

Thanks !!!

Revision history for this message
Oscaruzzo (oscar-lazzarino) wrote :

Can confirm it works with 5.19.0-42

information type: Public → Public Security
information type: Public Security → Public
Revision history for this message
Rovano (rovano) wrote :

Can confirm it works with 5.19.0-42. Thx guys.

Revision history for this message
George R Lunney (lunney) wrote :
Download full text (4.4 KiB)

Can confirm that Creative Sound Blaster Audigy FX works with 5.19.0-42.
Thanks so much!

On Tue, May 23, 2023 at 7:11 AM Rovano <email address hidden> wrote:

> Can confirm it works with 5.19.0-42. Thx guys.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2009224).
> https://bugs.launchpad.net/bugs/2009243
>
> Title:
> kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card
>
> Status in linux package in Ubuntu:
> Confirmed
> Status in linux-hwe-5.19 package in Ubuntu:
> Confirmed
>
> Bug description:
> 2023-03-03
> Attempted install of kernel 5.19.0-35 using the Linux Mint package
> installer LM 21.1 Vera, release 21.1).
> Clobbered my Sound Blaster AE-7.
> Could not even locate the device using Sound manager utility on Linux
> Mint Panel (the enumerated device showed up as the embedded sound chip on
> the mobo which I had previously disabled in the UEFI setup).
> Uninstalled kernel and reverted back to 5.19.0-32 using Timeshift
> restore feature which worked fine before the update to 5.19.0-35.
> Tried again to install 5.19.0-35 the same way, just to be sure.
> The SB AE-7 got clobbered again.
> So restored back to 5.19.0-32 generic one more time, using Timeshift. SB
> AE-7 works fine now with this lower version kernel.
> Current hardware config:
> ------------------------
> Asus Prime Z790-P wifi mobo.
> Intel Core i3-13100 processor (with Intel UHD 730 graphics).
> Corsair Vengeance DDR5 32gb (2x16) ram, 5200Mhz.
> 3 x Nvme SSD.
> Boot drive is Western Digital Black SN770 500gb.
> Asus Nvidia RTX-3050 PCIe graphics card.
> Creative Labs Sound Blaster AE-7 audio card (PCIe).
> On-board audio chip (Realtek 7.1 Surround Sound High Definition Audio)
> is disabled in UEFI.
> UEFI is AMI/BIOS, revision 0812.
> Linux Mint 21.1 is running on barebones hardware, no VM involved.
> No other O/S's are installed on the machine.
> -----
> Running sudo lspci -vnvn > lspci-vnvn.log
> gave the following error message...
> pcilib: sysfs_read_vpd: read failed: No such device
> ---
> ProblemType: Bug
> ApportVersion: 2.20.11-0ubuntu82.3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: mikey 4106 F.... wireplumber
> /dev/snd/controlC0: mikey 4106 F.... wireplumber
> /dev/snd/seq: mikey 4105 F.... pipewire
> CasperMD5CheckResult: unknown
> CurrentDesktop: X-Cinnamon
> DistroRelease: Linux Mint 21.1
> InstallationDate: Installed on 2023-01-31 (32 days ago)
> InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217
> MachineType: ASUS System Product Name
> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
> nvidia_modeset nvidia
> Package: linux (not installed)
> ProcFB: 0 EFI VGA
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic
> root=UUID=854c280c-7c5c-494d-a304-db66cf592baf ro quiet splash
> ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
> PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
> R...

Read more...

Revision history for this message
Curtiss Clarke (centri-fuge-deactivatedaccount) wrote :

I have installed kernel version 5.19.0-42 generic on Linux Mint 21.1 (Vera) now for 5 days, and the Creative S/B AE-7 sound card is functioning normally. Desktop is Cinnamon 5.6.8 tk.

Revision history for this message
Daniel (dkim-b) wrote :

Hmm, while the Sound Blaster can now be seen for me in PulseAudio with kernels 5.19.0-42 and 5.19.0-43, it's still not fully functioning properly. It will not appear as a sink if the profile on the card is set to anything but stereo output or duplex. I need my card to output 5.1 surround sound audio, so the card is still not working.

The kernel log will output the following when the card fails to appear as a sink:
May 31 16:24:49 HX kernel: [ 578.234426] snd_hda_intel 0000:02:00.0: Too many BDL entries: buffer=4194048, period=2097024
May 31 16:24:49 HX kernel: [ 578.237600] snd_hda_intel 0000:02:00.0: Too many BDL entries: buffer=1058304, period=529152
May 31 16:24:49 HX kernel: [ 578.240558] snd_hda_intel 0000:02:00.0: Too many BDL entries: buffer=2116608, period=1058304
May 31 16:24:49 HX kernel: [ 578.242650] snd_hda_intel 0000:02:00.0: Too many BDL entries: buffer=1058304, period=40704

Revision history for this message
Rovano (rovano) wrote :

Daniel (dkim-b) wrote on 2023-05-31:
This will not be a kernel problem, but on another layer. I tested higher kernels up to 6.4 and no change.
But since I have nowhere to connect the 5.1 output, I didn't want to do further research.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.