kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card
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/
/dev/snd/
/dev/snd/seq: mikey 4105 F.... pipewire
CasperMD5CheckR
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
NonfreeKernelMo
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 20220329.
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.
dmi.board.name: PRIME Z790-P WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.
dmi.sys.vendor: ASUS
affects: | ubuntu → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in linux-hwe-5.19 (Ubuntu): | |
status: | New → Confirmed |
information type: | Public → Public Security |
information type: | Public Security → Public |
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/ FindRightPackag e. 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.]